Thanks to Andrew, I learned:
"
Probably because gpsmon on the Pi works with the gpsd daemon, which will switch an identified GPS model to the model-specific binary mode instead of the NEMA-0183 ASCII sentence format. And YAAC only understands NEMA-0183 format (and gpsd's JSON format). So once gpsd on the Pi switched the BU-354S4 GPS to proprietary binary mode, there was no way for YAAC on Windows to understand it.
?
Were you using the GPSD port type in YAAC on the Pi??
?
Note that the authors of gpsd have clearly stated their intentions of _not_ supporting Microsoft Windows.?
?
Also, it is possible to "brick" the BU-353S4 GPS if the wrong commands are sent to it. I use the -b option on gpsd to prevent the GPS from getting bricked. Does the BU-353S4 still work when you plug it back into the Pi?
?
Hope this helps.
?
Andrew, KA2DDO
author of YAAC"
My GPS still worked on the Pi.
I found this:
which described how to switch the GPS back to NEMA format.? I tried it, and it worked.? I noticed in the log that the GPS for some reason switched to 9600 baud.? Why, I don't know.
I moved my GPS to Windows and ran YAAC,? I reconfigured the GPS to serial_GPS at 9600 baud and clicked Test Port.? I saw the GPS output, so I now have my GPS working on Windows.
I ran?
$ sudo nano /etc/default/gpsd
and change the last line to:
GPSD_OPTIONS="-n -b"
so that gpsd won't change the GPS configuration.
I tested moving the GPS to the Pi and then to Windows, and both now have GPS signals!
