I take it from your last post that this is not a known problem!
I have tried various gpsd command line options and still experience the same problem. The current
# /usr/sbin/gpsd -G -D3 -F /var/run/gpsd.sock -P /var/run/gpsd.pid /dev/ttyS2
As mentioned in a previous post, I am not using gpsd's '-n' option. This allows me to close all clients, wait, and then reconnect OpenCPN after gpsd has dropped DTR and cycled the gps serial
My OpenCPN client is running on a different host than gpsd, hence the '-G' option for gpsd. Without -G gpsd only listens on the loopback address.
- - -
When initially researching my problem, I came across the following thread in the forum:
In cray's first post it sounded like a similar problem to the one that I am having, but then cray changed his configuration to a direct serial connection and the intermittent connection issue using libgps was never resolved.
Before I realized that allowing gpsd to reset the serial port would result in a successful OpenCPN connection to gpsd, I too (like cray) was repeatedly connecting/disconnecting OpenCPN hoping for a random success.
- - -
From my understanding, gpsd is supposed to smooth over any differences between gps hardware
to provide the client a standardized bunch of JSON. I have tried multiple versions of gpsd/libgps/opencpn on multiple host and client operating systems with the same result. I am beginning to wonder if the one piece of the puzzle that has not changed, namely my _gps_ could be at fault. It is an internal gps receiver in a Panasonic Toughbook CF-19 internally connected somehow to ttyS2. I am not sure of the make or model of the gps receiver.
On my boat
the Toughbook is used strictly as a front-end at my helm
, the internal gps is not used. My actual working gps is a Lowrance NMEA-2000 model. The Lowrance output is pulled from the NMEA-2000 backbone by a Linksys router that combines NMEA-2000, RS422, and RS232
inputs into one gpsd bundle. This weekend I will hook everything up on the boat
and see if the problem persists.
In the mean time let me know if there is anything else you would like me to check on my testing system.