NMEA 2000 support in OpenCPN

[J46Racer]

The new KIP MFD for OpenCPN works great for NMEA2000 data!

https://www.youtube.com/watch?v=uDas858rf6Y

[cas206]

Your screen shot shows NMEA 2000 data being formatted as NMEA 0183 format (not a conversion to "standard" NMEA 0183 engine data). The hex value 01f211 seen in the screen shots is PGN 127505. So that's your engine data. From what I understand of the current replies, none of the methods mentioned can use this data in this form. The string of hex digits at the end contain your data of interest. See https://digitalmarinegauges.com/cont...tocol_RevH.pdf for details to parse it.

[cas206]

https://www.yachtd.com/downloads/ydnr02.pdf


According to page 51 of your device manual, PGN 127505 is only converted to DIN and PGN which according to Note (6): "DIN and PGN are wrap NMEA 2000 messages according SeaSmart (v1.6.0) and MiniPlex (v2.0) specifications. Engine revolutions, boost pressure, coolant temperature, hours, fuel rate, alternator voltage are also transmitted in XDR sentence."



Note that fluid levels isn't listed for conversion to XDR. However, you might check if there is more current firmware or talk to Yacht Devices and request fluid levels in a XDR message for a future firmware update.

[mpuz]

Originally Posted by bdbcat

BellaDonna...


OpeCPN 5.8.x supports NMEA2000 by hard wire connection only.
NMEA2000 by ethernet (WiFi or hardline) is not supported.
Why?
Because there is no generally accepted standard for such transmission. The hardware solutions available follow vendor specific protocols, which are difficult to implement and test.


We have tested and recommend the YDNU-02 hardwire NMEA2000 adapter.


Good Luck
Dave

I fed nmea2000 dump to the can bus with connected esp32 with bluetooth serial forward using Timo's library.. opencpn on ubuntu used it wirelessly perfectly fine over bluetooth serial connection port (/dev/rfcomm0)

[wholybee]

Originally Posted by mpuz

I fed nmea2000 dump to the can bus with connected esp32 with bluetooth serial forward using Timo's library.. opencpn on ubuntu used it wirelessly perfectly fine over bluetooth serial connection port (/dev/rfcomm0)

Can you provide some details? I the esp32 source for that on github?

[mpuz]

Originally Posted by wholybee

Can you provide some details? I the esp32 source for that on github?

mine is not ready for posting yet, but to give you a clue -
take this sketch - https://github.com/ttlappalainen/NME...seListener.ino

add Bluetooth Serial port from arduino ide included samples and replace

  NMEA2000.SetForwardStream(&Serial);  // PC output on due native port

with this

  NMEA2000.SetForwardStream(&SerialBT);

then, if you are on linux you need to map blutooth connection to the serial port, in my case it is a /dev/rfcomm0 , type this in terminal, replacing mac address of esp32 to your own

sudo rfcomm connect rfcomm0 FC:B4:67:4E:EC:52

my setup consist of two raspberry pis with can bus controllers-transcievers terminated by 120omh, between them are two wires imitating can bus.. two raspberry pis let me monitor can bus and to be sure that in is working and on, both has can-utils and canboat installed, first is playing nmea dumps using canplayer and second has

candump can0 | candump2analyzer | analyzer

started to monitor that all messages are passing through
ESP32 is connected using can transciever in the middle (120omh resostor should be peeled off) and has sketch uploaded which explained before
demonstration

https://www.youtube.com/watch?v=KsHPtEo8UNI

[stevead]

I hope you had fun building your ESP32 device and compiling code.

On Linux computers you could have achieved the same result using a combination of netcat and can-utils.

To send live data between two computers:
Machine A:

netcat -l -p 1234 | canplayer -v vcan0=can0

Machine B:

candump -L can0 | netcat -v 192.168.0.109 1234

To send a candump log file for replay on another computer:
Machine A:

netcat -l -p 1234 | canplayer -v vcan0=can0

Machine B:

netcat -v 192.168.0.109 1234 < /mnt/d/logs/seattle.log

Notes:

1. Configure IP address and port as appropriate
2. Machine A does not have a physical CAN bus adapter, it has been configured with a virtual can adapter, in this case named vcan0.

You can kind of achieve the same on Windows or MacOSX using virtual serial devices (com0com and socat respectively) and sending Actisense EBL log files or Actisense data streams.

I fear that many readers may have missed the point, which is that today while there are various proprietary mechanisms for encapsulating or sending NMEA 2000 data over TCP or UDP, OpenCPN does not yet support any of them.

There are however several alternative mechanisms to send data wirelessly, but these are generally only appropriate for the more technical adept users.

[wholybee]

Originally Posted by stevead

I hope you had fun building your ESP32 device and compiling code.

On Linux computers you could have achieved the same result using a combination of netcat and can-utils.

To send live data between two computers:
Machine A:

netcat -l -p 1234 | canplayer -v vcan0=can0

Machine B:

candump -L can0 | netcat -v 192.168.0.109 1234

To send a candump log file for replay on another computer:
Machine A:

netcat -l -p 1234 | canplayer -v vcan0=can0

Machine B:

netcat -v 192.168.0.109 1234 < /mnt/d/logs/seattle.log

Notes:

1. Configure IP address and port as appropriate
2. Machine A does not have a physical CAN bus adapter, it has been configured with a virtual can adapter, in this case named vcan0.

You can kind of achieve the same on Windows or MacOSX using virtual serial devices (com0com and socat respectively) and sending Actisense EBL log files or Actisense data streams.

I fear that many readers may have missed the point, which is that today while there are various proprietary mechanisms for encapsulating or sending NMEA 2000 data over TCP or UDP, OpenCPN does not yet support any of them.

There are however several alternative mechanisms to send data wirelessly, but these are generally only appropriate for the more technical adept users.

My thought was to use the esp32 to connect to the canbus, bridge/encapsulate in TCP/IP, then use a virtual com port to make it available to OpenCPN. It seems it would be easy to do. The ESP32 has built-in wifi, so it would be a tiny device that could be powered by the NMEA2000 bus, and would work with OpenCPN now, with the virtual serial port.

I have too many projects and not enough time...

[PA1PDR]

Originally Posted by wholybee

That is a disappointing position. I'm not going to guess what percentage of opencpn users connect via a wireless gateway, but i imagine its quite large and growing, with wired connections shrinking. The n2k support built into OCPN is useless to us. And anyone using a phone or tablet. I don't think there is anything secret about what yacht devices is doing. Has anyone asked them or actisense for information? Both companies want their products to work with a wide product range.

There is an easy solution in that you install and use SignalK as a broker: it supports virtually all wireless and wired CAN adapters and OpenCPN supports SignalK directly. Other than this protocol conversion it can do a ton of other things. Check it out!

[barcoMeCasa]

Originally Posted by PA1PDR

There is an easy solution in that you install and use SignalK as a broker: it supports virtually all wireless and wired CAN adapters and OpenCPN supports SignalK directly. Other than this protocol conversion it can do a ton of other things. Check it out!

Agreed, signalk does make things so much easier though still not plug a cable into an expensive box from raymarine et al. Windows install file here >
https://github.com/SignalK/signalk-s...ses/tag/v1.1.0

Questions are better asked on discord rather than here, wrong advice not unheard of re signalk on here, better asking the guys who wrote/write it.
https://discord.gg/uuZrwz4dCS

[mpuz]

Originally Posted by wholybee

Can you provide some details? I the esp32 source for that on github?

here is the code:
https://github.com/svplanb/NMEA2000-...rial-Repeater/