NMEA0183 Data over USB Serial connection is sometimes garbled on Venus OD
Trying to set up an old nmea0183 AIS with my signalk server running on Venus OS on a raspberry pi. I am using the correct baud rate, referencing the device by using the persistent name (/dev/by-id/...). When I cat the same device I get some real sentences (and signalk does too, which it converts sometimes) but also some garbage. When I hooked my AIS to my pc and ran signalk-server in docker it worked great with absolutely no garbage. The settings in signalk were the same.
I think I may have boiled it down to Venus is pinging my serial connection on something like /dev/ttyUSB4, while I am listening to the device on a different symlink. Does anyone have adive or how to fix it, or if I'm barking up the wrong tree?
4 Replies
There’s something you have to make so VenusOS does not try to use it.
What is it that I make? Is there a setting?
Somewhere in VenosOS. I don’t remember the details.
Probably not in the GUI
Would it be something like USB auto discovery?
Also in the future is there a way to have the option for signalk server to exclusively use a serial connection?
I found the problem, and the easy fix is to run /opt/victronenergy/serial-starter/stop-tty.sh /dev/ttyUSB0.
However now this doesn't persist across reboots. Editing serial-starter.rules in /etc/udev/rules.d will make this persist across reboots.
However this may not persist across firmware upgrades, that will have to remain to be seen,.