NMEA 2000 over WiFi ?

[wholybee]

I contacted Actisence support and was sent these documents. They do not have documentation for the RAW formats completed yet.

These were .docx files that I renamed to .doc.

[bcn]

Originally Posted by wholybee

I contacted Actisence support and was sent these documents. They do not have documentation for the RAW formats completed yet.

These were .docx files that I renamed to .doc.

We are in contact now with the developers of Actisense, so hopefully there will be some interesting debate in the next days.


Hubert

[Corsair63]

did you tried to use NMEArouter? https://arundaleais.github.io/docs/ais/nmearouter.html

with it you can receive from several sources NMEA sentences and distribute on other sources of your setup.
I don't know if it will accept N2K but it does with 0183 very well, with several sources/destinations in the same IP address.

[Antipole]

A blog I subscribe to has just posted this on OneNet. (I do not have a view.)
https://www.navigation-mac.fr/nmea-o...gamme/?lang=en

[wholybee]

Originally Posted by Antipole

A blog I subscribe to has just posted this on OneNet. (I do not have a view.)
https://www.navigation-mac.fr/nmea-o...gamme/?lang=en

That is actually more information about it than I have seen previously. I had mostly assumed it was just NMEA2000 encapsulated in TCP/IP, similar to what several vendors are doing, only as a standard. Apparently, it is not. The bit below is a deal killer, truly closing the system except to large vendors who pay up. I hope it is never widely adopted.

Every OneNet application (running on a physical device) must successfully pass the NMEA certification tool tests in order to obtain a certificate that can be used in a secure OneNet network. If the physical device, such as a tablet or mobile phone, is not NMEA OneNet certified, the OneNet application running on it must be NMEA certified in order to join a secure OneNet network and access the data it contains. However, the OneNet network can possibly be left in an open state (Insecure) to allow the use of non-certified devices if the user wishes.

[cas206]

"However, the OneNet network can possibly be left in an open state (Insecure) to allow the use of non-certified devices if the user wishes."


And hope the major manufacturers actually implement this option.

[rgleason]

https://en.wikipedia.org/wiki/NMEA_OneNet

[bdbcat]

Query to all:


If you are currently using any sort of N2k->Ethernet gateway, please report device and configuration here. This will help us as we begin testing this setup with the various hardware solutions under consideration for OpenCPN.



Thanks
Dave

[bdbcat]

All...
Experimenting with Actisense W2K-1, and YDEN-02 devices.


Good news: the YD "NMEA 2000 (RAW)" format appears to be exactly the same as the Actisense "ASCII RAW" format.
The good news is this: We will not require separate drivers for Actisense and YD.



This format is essentially an ASCII representation of a CANbus frame, and is easily processed by the OCPN N2K comm stack.



I will experiment with other Actisense data formats, and see what we see.


Dave

[wholybee]

Originally Posted by bdbcat

Query to all:


If you are currently using any sort of N2k->Ethernet gateway, please report device and configuration here. This will help us as we begin testing this setup with the various hardware solutions under consideration for OpenCPN.



Thanks
Dave

You know this I think, but I have the YDWG-02, currently configured to convert to 0183.

[bdbcat]

Hello all...

We now have Alpha test builds of OpenCPN supporting N2K<->ethernet interconnect.
If you would like to help with advance testing, here is the info:

1. Install packages of OCPN with N2K/ethernet capability for Win/10/11 and MacOS are available at:
https://dl.cloudsmith.io/public/davi...4818_setup.exe
https://dl.cloudsmith.io/public/davi...06.2df7c8a.pkg

2. Please note we are interested in testing the N2K native modes of the Actisense and Yacht Devices gateways.
3. You will need to use the vendor supplied web access to configure the installed gateway for the correct mode.
4. Yacht Devices YDNU-02 provides only one N2K mode & format, called "NMEA 2000 (RAW)".
5. Actisense provide several compatible N2K modes and formats. The OCPN comm driver will determine the received data format by context, and apply the correct decode algorithm automatically. Actisense NGT format is NOT supported on this interface.
6. You will notice a slight tweak to the OCPN Connections setup page for Network connections. Select data protocol "NMEA2000" in all cases for this test.
7. OPCN supports READ-ONLY access to the gateways today. Bi-directional will come as we verify the data format parsing.



Good Luck
Dave

[wholybee]

Originally Posted by bdbcat

Hello all...

We now have Alpha test builds of OpenCPN supporting N2K<->ethernet interconnect.
If you would like to help with advance testing, here is the info:
<snip>
Dave

The quick 60 second test, and it seems to work fine. Basic Boat Data that I have setup in Dashboard and AIS both work.

This is on the Yacht Devices YDWG-02.

Thank You VERY much for working on this. It is much appreciated.

[bdbcat]

Whollybee...


If possible, can you show a screenshot of Connections->Show NMEA Debug Window?
For my simple N2K network, looks like the attached Pix.


Thanks
Dave

[wholybee]

Here they are.

[Scubacat]

Originally Posted by bdbcat

Hello all...
We now have Alpha test builds of OpenCPN supporting N2K<->ethernet interconnect. snipped)

I missed the alpha tests, but needed today to check (V5.10) out and note that the TCP network works fine with both "N2KASCII" RAW and "$PCDIN" RAW input formats. However, neither format are accepted via UDP.

I presume this failure to accept (raw) 'N2000' UDP is a bug ?? Or are there some subtle settings hidden I have missed?

Slight rant.. it would be very nice if the "port connections" identified which RAW format the "N2000" protocol can accept (or is trying to send!!).

Also some clarity about what OpenCPN can transmit wirelessly in the "N2000" mode would be appreciated. I could not see any "sent" data in the debug window - but would have expected to see a N2KASCII or PCDIN transliteration of sent pgns for eg GOTO or AP button pressing.

Thanks
Dagnall