smiller11
commented
8 months ago I resolved the problem. The GPSlistener script as written specifically looks for $GPxxx NMEA ('GP' meaning GPS-derived) sentences but my GPS module is outputting GNxxx ('GN' meaning derived from both GPS and other sources, such as GLONASS) sentences. Once this was corrected in GPSlistener the script works properly.
What I don't get is that this is the same GPS dongle I had used in the past so not sure why it now uses the altered format (Was it not receiving GLONASS/Galileo before? Who knows.)
Anyway, hopes this helps anyone who runs into the same issue. A future revision of the script might was to include a provision for this issue.
I'd been using JS8CallUtilities(v2) a year or so ago and it had been working flawlessly, however when I recently re-installed it I find that while the script starts and runs normally I receive a 'No Fix' error when attempting to determine location. In debug mode I can see the NMEA sentences streaming from my GPS module so the GPSlistener routine seems to be working, and looking at the code the specific 'No Fix' error seems to be generated when there is invalid output from the Maidenhead grid lookup. I have made sure that the Python Maidenhead version is >1.5, and even rolled Python back from 3.11 to 3.7 in case something was broken in a newer version, but no joy. I have tried running under both Linux (Mint 21) and Windows 10 and both display the same error. On Windows the problem occurs both when I use the pre-compiled executable (which would seem to indicate that it isn't a versioning issue) or run the Python script. As above, everything worked before and I'm unable to find anything that has changed that would trigger the problem.