Remember the tab key ...answer should be red when you hit enter.
Cleve, What are you using on page 3... (-n -?) In a manual configuration I have much success with:
Caps are critical as are spaces. Then to check it I use:
-n and -G were in one of the OPENCPN terminals which makes sense.
Sent from new WattOS/FoxtrotGPS install on CF-19 MK2.
Re-booting is your friend.
From
Manual for GPSD
-F
Create a control socket for device addition and removal commands.
You must specify a valid pathname on your local filesystem; this
will be created as a Unix-domain socket to which you can write
commands that edit the daemon's internal device list.
-S
Set TCP/IP port on which to listen for GPSD clients (default is
2947).
-b
Broken-device-safety mode, otherwise known as read-only mode. A few
bluetooth and USB receivers lock up or become totally inaccessible
when probed or reconfigured; see the hardware compatibility list on
the GPSD project website for details. This switch prevents gpsd
from writing to a receiver. This means that gpsd cannot configure
the receiver for optimal performance, but it also means that gpsd
cannot break the receiver. A better solution would be for Bluetooth
to not be so fragile. A platform independent method to identify
serial-over-Bluetooth devices would also be nice.
-G
This flag causes gpsd to listen on all addresses (INADDR_ANY)
rather than just the loop back (INADDR_LOOPBACK) address. For the
sake of privacy and security, TPV information is now private to the
local machine until the user makes an effort to expose this to the
world.
-l
List all drivers compiled into this gpsd instance. The letters to
the left of each driver name are the gpsd control commands
supported by that driver.
-n
Don't wait for a client to connect before polling whatever GPS is
associated with it. Some RS232 GPSes wait in a standby mode
(drawing less power) when the host machine is not asserting DTR,
I did not use any terminal commands on the last install except xgps to see if things were working. Used Cleve's instructions.
J'd