Query: N2K on Raspberry Pi

[verkerkbr]

It is not always clear how to get the the route data back to the SignaK server.

Open a connection in OpenCPN (only outgoing)

localhost udp and port 2000

Go the the settings ( ..) below and choose only the data items you like to send. RMB, RMC and XTE as an example. This to avoid data "singing round".

Then go to the SignalK server and add a new connection:

NMEA183, give connection a name udp and port 2000.

If you make a route or a waypoint in OpenCPN this data appears in the SignalK server.

Can be displayed in MXTommy Kip with distance and direction.

The OpenCPN data can be transfered with SignaK tot NMEA2000 instruments etc.etc.

Bram

[ALROCHARARI]

Originally Posted by bdbcat

Hi folks....
We are working in the background on some basic N2K support for OpenCPN core. There are lots of issues, but here is one where we need some specific user feedback.


For those using any sort of N2K interface on Raspberry Pi, or other linux systems:
What is your hardware configuration? How are YOU interfacing your OCPN device to the N2K bus. Detail is useful....


Thanks
Dave

This is my personal test configuration:
https://photos.app.goo.gl/y1avEztEWctFe7pdA

- LG 24" screen (28W)
- RPI 4 8Gb (Running Openplotter - Signal-K & OpenCPN) (4W)
- PiCAN-M hat with CAN-Bus Micro-C (NMEA-2000) and RS422 Connector (NMEA-0183) + 3 A SMPS (RPI power supply through NMEA-2000) (<1W)
- MAIANA NMEA-2000 (<1W)
- Linksys WRT54-GL (To allow WIFI remote access, DHCP) (10W)
- 220V-12V 10A transfo (When not connected directly to boat battery)
- Garmin NMEA-2000 backbone with terminators (To plug to the existing network on the boat if existing)

Maximum consumption is less than 4A on 12V

So with this configuration I have:
- Plotter (OpenCPN)
- AIS (Maiana)
- GPS (Maiana)
- Clock (Maiana GPS and signal-k plugin)
- NMEA-0183 / NMEA-2000 network connections

[hans-martijn]

I use the NMEA 2000 USB Gateway from hatlabs (https://hatlabs.github.io/sh-esp32/p...a2000-gateway/). The USB is connected to my signalk-rpi which sends signalk to my maps pi (both rpi 4 with 4GB), which currently crashes.

Coming weekend I'll try the signalk NMEA 0183 connection again, and I will use a plugin in signalk to see the things I cannot see in O.

-Hans

[SerialHobbyist]

Originally Posted by Baikal

Dave
How is the support for n2K gateways YachtDevice and Actisense NGT-1?
Would like support for YachtDevices NMEA 2000 USB Gateway YDNU-02
https://www.yachtd.com/products/usb_gateway.html

I have been using the Yacht Devices YDNU-02 for several years into various Ubuntu linux systems (laptop and now dedicated NUC type computer) with both opencpn and custom software.


It's been a long time so all I can remember is that I had to configure the YDNU-02 to customize the header string first two characters -- but that may have been for the software that wasn't opencpn.


I pull GPS, AIS, and things like wind speed/direction, etc.



Chas Douglass

[WE9V]

I'm using the ShipModul MiniPlex-3Wi-N2K via USB connection (https://www.shipmodul.com/miniplex-3.html). This was purchased before adding the Pi to the system, originally to multiplex our older 0183 instrument data into our newer N2K chartploter and VHF. The ShipModul sends all 0183 and N2K data to the Pi over USB.

[supermarin]

@bdbcat Good to see you're working on a standalone N2K interface!


Using YachtDevices YDEN-02 NMEA2000 -> Ethernet plug.
Plugs into a Netgear switch, that also has Navico Radar and Zeus 3 plugged into.
Raspberry pi is wired with ethernet to the same switch and consumes N2K directly over ethernet. Previously I've used a PiCAN board, but removed it for various reasons.
Used to run SignalK but removed that as well for various reasons.

[ve0hak]

Originally Posted by wholybee

Crossing my fingers it will support wifi adapters as well. The YDWG-2 and actisence w2k-1 both support nmea2000 over wifi.

The YDWG-2 behaviour of batching messages up into UDP frames is a little idiosyncratic, not to mention expensive for what it is... Enough so that I'm waiting on one of these [1] to arrive in the post, to use either on an RPi or one of the pine64 boards with a compatible pinout.

[1] https://www.waveshare.com/2-ch-can-hat.htm

[CyKlop]

This is welcome news. I was just gathering materials and design to create an N2K driver so that people could just configure the driver and programs like OpenCPN would just connect to the driver, a bit like ODBC (but hopefully simpler).

[chris14679]

We have a Vesper XB8000 AIS which has WiFi and an nmea 2000 connector, so NMEA 2000 comes in through that and then over WiFi to the pi pilot and to the laptop and Android tablet running opencpn.

[CarinaPDX]

I have been using an Actisense USB adapter with my laptop, since at the time I bought it (about a decade ago) it was the best-supported alternative. When I buy a Pi 4 of course I could use it there but would be quite happy to use a canbus HAT or generic USB adapter.

While it is not an OCPN problem, updating firmware in N2K devices has devolved into proprietary solutions. It would be very nice if NMEA would agree to a standard for firmware updates over the bus such that a computer, preferably Linux or perhaps multi-OS, could update devices directly over N2K without any intermediate proprietary hardware. I am particularly upset at Maretron, because the electronic compass I bought from them initially supported firmware updates over NMEA 0183 and N2K (I used 0183 into a serial port with their software). They dropped support for 0183 updates and require a proprietary Maretron USB adapter for N2K (instead of the common Actisense or other USB interface). Increasingly an MFD or multi-display from the same vendor is required to do device firmware updates. Kudos to Airmar for supporting the Actisense USB interface for firmware updates - perhaps a good reason to also support Actisense. IIRC Actisense makes available their support libraries to developers.

Greg

[goboatingnow]

Originally Posted by bdbcat

Baikal...
We are not yet ready to announce specific features of the n2k work. So I would rather not get into details of the feature yet.
This thread is only to query what user are doing today, if anything, with n2k. There will be more discussion later as the picture clears.



Teaser: the YDNU-02 is on the proposed list of supported devices.


Dave

in order to get a NMEA certification the reality is OPENCPN would have to use a registered NMEA 2000 gateway product , this really rules out generic interface boards in my view

[CarinaPDX]

Originally Posted by goboatingnow

in order to get a NMEA certification the reality is OPENCPN would have to use a registered NMEA 2000 gateway product , this really rules out generic interface boards in my view

No one anywhere on this thread has suggested that OCPN should get N2K certified. Many marine products are N2K "compatible", not certified. If I understand correctly, using the Actisense libraries and supporting the Actisense USB converter would allow for eventual N2K certification, but considering the cost of NMEA membership, N2K standards, and certification testing I seriously doubt this is under consideration for OCPN or any other open source effort. Of course, this is the intent of the N2K standard.

Greg

[Huskybeer]

Bram Ben geinteresseerd in jouw set-up
Heb je een schema?
Kunnen we verder via e-mail (mijn is oiskoa@pm.me)
Alvast hartelijk bedankt
Teun

[verkerkbr]

See my email

[pa391as]

isn’t that essentially what the TwoCAN plug-in already does ?