Yacht Devices NMEA wifi to OpenCPN

[TheOffice]

Installed a Yacht Devices NMEA 200 Wifi transmitter. My windows 10 machine gets the data, but apparently I don't have the configuration correct in OpenCPN. I am using the correct IP address and port.

Suggestions?

How many ports can be assigned the same priority? I have 3 assigned priority 1 - GPS, AIS and wifi.

[bcn]

Please post your settings.

[TheOffice]

It is set to 183.168.4.1 port 1456, UDP,

[bcn]

A screenshot from the communication settings of OpenCPN perhaps?

[TheOffice]

if it works

[bcn]

For UDP input no IP is required. Try just going with the port.

0.0.0.0 :1456

More details in the manual under communication settings, just in case.

[TheOffice]

Thanks! I will give it a try!

[transmitterdan]

For UDP NMEA senders if you make the last octet of the IP address 255 then messages should go to all devices on that subnet.

In OpenCPN the address should be 0.0.0.0 (don’t care) and the port number must match the sending port number. Also, any router in between the sender and O must be configured to not block the assigned port number. Sometimes a really high port number (like 10110) will not be blocked.

[rgleason]

Connections - Add a Network Connection - 3 Choices TGP, UDP & GPSD


UDP

[TheOffice]

Did it as TCP. Works great!

[transmitterdan]

Yes, TCP works ok for connecting 2 and only 2 systems to one another. However, most people want to share the NMEA data with multiple devices (tablet, PC, handheld phone, etc.) and TCP is not a good option for that. That is where UDP to a multicast IP address is really handy.

[TheOffice]

Thanks! I was not aware of the limitation on TCP.

[MilesAhead]

Originally Posted by transmitterdan

Yes, TCP works ok for connecting 2 and only 2 systems to one another. However, most people want to share the NMEA data with multiple devices (tablet, PC, handheld phone, etc.) and TCP is not a good option for that. That is where UDP to a multicast IP address is really handy.

Perhaps one of you can help me. I'm going nuts. I just cannot get my Microsoft Surface Pro to read the GPS info from the RPi over wifi using the RPi as a wireless AP. I used the OpenPlotter NOOBS install for the RPi. I have been able to get a Windows 10 desktop to read the GPS multicast from the RPi, but when I use exactly the same setting on my Surface, nada.

RPi connections:
- Type: Network
- Protocol: UDP
- Address: 10.10.10.255
- Data Port: 10110
- Input: No
- Output: Yes

Windows machine connections (desktop and Surface Pro):
- Type: Network
- Protocol: UDP
- Address: 0.0.0.0
- Data Port: 10110
- Input: Yes
- Output: No

[transmitterdan]

Can the RPi ping the surface pro machine?

[MilesAhead]

Originally Posted by transmitterdan

Can the RPi ping the surface pro machine?

No it can't, but what is weird is that I can VNC to the RPi from the Surface Pro.

Just checked that I can ping the desktop from the RPi