2021-12-13, 11:35 PM
Dear All,
I would like to seek advices on an issue encountered with signalk NMEA0183 GPSD source.
I am feeding data from tinypilot to openplotter through signalk (version 1.40.0) :
- Some NMEA0183 data (baro, temperature, wind direction and speed) by declaring a NMEA0183 source as TCP Client pointing to tinypilot on port 20220
* 'No data timeout' is set to 10000 (unit is millisecond and not second according to the code found on github: https://github.com/SignalK/signalk-serve...0cb859de38)
- GPS data by declaring a NMEA0183 source as GPSD pointing to tinypilot on port 2947
* GPSD version on tinypilot: 3.23.1
* 'No data timeout' has been set to 10000 (not sure about the time unit, assuming this is ms) and also experimented with 10 (assuming unit is second)
- pypilot data through signalk automatic discovery
This setup works seamlessly until, for tests purpose, I reboot tinypilot :
- The signalk automatic discovery resume properly after some delay (~10 to 12s, time for pypilot code to start)
- The TCP Client source resume almost immediatley after reboot
- The GPSD never resume ; the signalk server has to be restarted
There is no error reported by the GPSD source within 'Connection & Plugin Status' while reconnection retries error populate the NMEA TCP source.
Has someone already experimented with NMEA0183 source as GPSD and found a proper setup to resume the GPSD connection ?
Best regards,
Xavier.
I would like to seek advices on an issue encountered with signalk NMEA0183 GPSD source.
I am feeding data from tinypilot to openplotter through signalk (version 1.40.0) :
- Some NMEA0183 data (baro, temperature, wind direction and speed) by declaring a NMEA0183 source as TCP Client pointing to tinypilot on port 20220
* 'No data timeout' is set to 10000 (unit is millisecond and not second according to the code found on github: https://github.com/SignalK/signalk-serve...0cb859de38)
- GPS data by declaring a NMEA0183 source as GPSD pointing to tinypilot on port 2947
* GPSD version on tinypilot: 3.23.1
* 'No data timeout' has been set to 10000 (not sure about the time unit, assuming this is ms) and also experimented with 10 (assuming unit is second)
- pypilot data through signalk automatic discovery
This setup works seamlessly until, for tests purpose, I reboot tinypilot :
- The signalk automatic discovery resume properly after some delay (~10 to 12s, time for pypilot code to start)
- The TCP Client source resume almost immediatley after reboot
- The GPSD never resume ; the signalk server has to be restarted
There is no error reported by the GPSD source within 'Connection & Plugin Status' while reconnection retries error populate the NMEA TCP source.
Has someone already experimented with NMEA0183 source as GPSD and found a proper setup to resume the GPSD connection ?
Best regards,
Xavier.