-
I have my nmea2K network available on a can interface on one computer. I have Signal K on an other computer, on the same network. I tried differents TCP NMEA2K sources from SignalK : NavLink2, Yacht Devices RAW TCP, W2K-1 N2K ASCII/Actisense, but couldn't get any of them to work. To make the can0 available on TCP, I use canboatjs and a convert file with matching filter : pgnToActisenseSerialFormat, pgnToiKonvertSerialFormat, pgnToYdgwRawFormat. I can see output from the TCP server that seems to be OK : with pgnToActisenseSerialFormat for W2K-1 N2K ASCII/Actisense I also tried most of other combinasion, without success. I can see SignalK connect to the TCP server, but it couldn't read any data from it. my test command : candump can0 | candumpanalyzerjs | node convert.js | nc -kl 6000 How to solve this ? Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Have you considered piping raw can over UDP or TCP and do N2K only on the receiving host? https://agill.xyz/tunneling-can seems like a pretty good summary of options. |
Beta Was this translation helpful? Give feedback.
-
I think this would work if you convert to the correct W2K-2 format. That is not N2K ASCII above, what you converting to is different. Also adding a tcp option for canbus would probably make sense. |
Beta Was this translation helpful? Give feedback.
I think this would work if you convert to the correct W2K-2 format. That is not N2K ASCII above, what you converting to is different.
Also adding a tcp option for canbus would probably make sense.