2024-04-04, 05:24 AM
I tend to think it is best to let gpsd handle the gps and signalk or pypilot to get gps from that, but.. we probably should make it easier for users to completely disable gpsd and eliminate it's presence because that is also a valid configuration and frustrating to achieve.
Consider for example some buggy gps that gpsd has issues dealing with but wont let go of, but the nmea output is "good enough"
Finally, ideally openplotter script that does disable any gps would detect if it is in binary mode and use gpsctl -f -n on the device to ensure it can be used as gpsd does often put these devices in binary mode and the gps will remember this even if unplugged or not powered.
So I guess what I am saying is some sort of gui to allow users to specify what process directly manages the gps, what do you think?
Consider for example some buggy gps that gpsd has issues dealing with but wont let go of, but the nmea output is "good enough"
Finally, ideally openplotter script that does disable any gps would detect if it is in binary mode and use gpsctl -f -n on the device to ensure it can be used as gpsd does often put these devices in binary mode and the gps will remember this even if unplugged or not powered.
So I guess what I am saying is some sort of gui to allow users to specify what process directly manages the gps, what do you think?