I bought one of these https://canable.io/ with the intention of using it to integrate old NMEA 0183 gear with newer N2K gear.
I'm not finding much information out there regarding this particular dongle, so I'm wondering if anyone has any experiences or information they could share.
I am hoping to use SignalK as the multiplexer between the two networks. I use a miniplex 2Wi as a nmea-0183 seatalk 1 multiplexer, which puts everything on Wifi both directions. They do have a 2k version but I don't want or need to spend that much, at least not before I try to do it on the ARM board, and of course help everybody else in the process.
I just received my Canable Pro. Tried to flash the Candlelight firmware as before. However no longer shows the lights on the board. This was done on a Linux system.
Next tried the update utility on a Windows 7 systeem and now the Canable board is working. Also with SignalK in the OpenPlotter software to convert NMEA2000 to NMEA183 and to OpenCPN. See instruction.
Using a Pi 4. and CANable Pro adapter fresh out of the box.
In Serial (v2.1.0) I selected device ttyACM0 gave it the alias of /dev/ttyOP_canable, data type NMEA 2000, and applied.
Everything looks good. Settings shows the device alias and shows it plugged in to the correct physical port on the Pi.
Then in Serial (v2.1.0) /Connections tab I select ttyOP_canable and click on Add to CAN Bus.
Next popup; select the default baud Rate 115200 and press AUTO.
Restart SignalK Server, everything looks good the Connection & Plugin Status shows the connection in green "Connected to /dev/ttyOP_canable".
No connection activity shows up in the Stats window for the canable connection.
(2020-05-25, 06:51 PM)RichFind Wrote: Using a Pi 4. and CANable Pro adapter fresh out of the box.
In Serial (v2.1.0) I selected device ttyACM0 gave it the alias of /dev/ttyOP_canable, data type NMEA 2000, and applied.
Everything looks good. Settings shows the device alias and shows it plugged in to the correct physical port on the Pi.
Then in Serial (v2.1.0) /Connections tab I select ttyOP_canable and click on Add to CAN Bus.
Next popup; select the default baud Rate 115200 and press AUTO.
Restart SignalK Server, everything looks good the Connection & Plugin Status shows the connection in green "Connected to /dev/ttyOP_canable".
No connection activity shows up in the Stats window for the canable connection.
What am I doing wrong? Baud rate?
I'am using the Candlelight firmware. Then you have to activate the Canable board.
With this activating you get can0. Check in SignalK that the port is can0.
The baudrate rate is 250000.
The activating string for the Canable firmware is:
sudo ip link set can0 up type can bitrate 250000
You can automate this at startup in the file:
etc/rc.local
Rights must changed for this file for execute. Is explained earlier.
2020-06-17, 02:20 PM (This post was last modified: 2020-06-17, 02:39 PM by gedass.)
Hi,
I try to use TouCAN Marine NMEA200<=>USB converter from RUSOKU as standard SocketCAN device on Raspberry Pi 4.
In SignalK software I see that converter "Status" is "Connected" but hardware still is not open.Should I use "sudo ip link set can0 up type can bitrate 250000"
before running SignalK server ?
btw SignalK to NMEA0183 "Status" is "Started". Should status of NMEA2000 converter be "Started" too ?
I try to use TouCAN Marine NMEA200<=>USB converter from RUSOKU as standard SocketCAN device on Raspberry Pi 4.
In SignalK software I see that converter "Status" is "Connected" but hardware still is not open.Should I use "sudo ip link set can0 up type can bitrate 250000"
before running SignalK server ?
btw SignalK to NMEA0183 "Status" is "Started". Should status of NMEA2000 converter be "Started" too ?
Ged
It depend on the firmware version. With the candlelight version you need to do the inalisiation string first to get the can0.
This can be done automatic at startup. See my instruction in rc.local
In SignalK the settings must be can0.
Why do you like to use the Toucan convertor ? NMEA2K comes in as SignalK and SiggnalK can be used directly in OpenCPN with the latest version.
Settings: SignalK localhost and port 3000.
Also look at the OpenPlotter application SignalK filter. This show what is coming en out in SignalK.