2018-11-19, 12:47 AM
Thanks for the speedy advice, abarrow and jim321!
cat output looks like pretty much the same thing I was seeing in the serial terminal, above. The chartplotter is definitely sending messages; I'm just unable to interpret them.
When you suggest looking at the interface, do you mean the USB com port hardware? I'd read people had positive experiences with the FTDI chips, so I thought this would be a good choice.
That was my initial assumption, but the chartplotter has selectable baud rates, and 4800 was the default. I also set 4800 in OpenPilot's serial interfaces manager. I believe 4800 is pretty typical for NMEA 0183, but I also tried other pairs like 38400 to no avail.
(2018-11-18, 05:33 PM)abarrow Wrote: As an initial test, open a terminal and use the "cat" command on the interface. For example, if the interface you are connecting to is ttyUSB0, then open a terminal and type "cat /dev/ttyUSB0". Look at that to see if you are getting recognizable NMEA strings.
If you are seeing good NMEA strings, then it's probably still an issue with speed. If not, then your interface is a good place to start looking.
cat output looks like pretty much the same thing I was seeing in the serial terminal, above. The chartplotter is definitely sending messages; I'm just unable to interpret them.
When you suggest looking at the interface, do you mean the USB com port hardware? I'd read people had positive experiences with the FTDI chips, so I thought this would be a good choice.
(2018-11-18, 06:24 PM)jim321 Wrote: looks like the wrong baud rate
That was my initial assumption, but the chartplotter has selectable baud rates, and 4800 was the default. I also set 4800 in OpenPilot's serial interfaces manager. I believe 4800 is pretty typical for NMEA 0183, but I also tried other pairs like 38400 to no avail.