Expedition Navigation Software / Instrument type Expedition stopped working with NMEAremote

**Posted by BR29** 8/28/2025 9:51 am

We use NMEAremote to repeat information from Expedition and it has worked just fine until about a month ago. I upgraded to Expedition v12.4.8 at around the time when it stopped working. I have since upgraded to v12.4.15 but it is still not working. I’m not sure whether it has to do with Expedition or something else but that is the only thing I’ve changed in the system setup. The network shows as open in Expedition and I can see data in the Raw data window. In NMEAremote it shows a Read Timeout when we try to connect and no data is displayed.

Has anyone else experienced this? Or any suggestions of how to troubleshoot it?

We use the default settings as suggested by the App setup instructions and they have worked until recently:
- instruments: Expedition
- Connection: UDP
- Adresse: Blank or 0.0.0.0
- Port: 5010
- Boat: 0

The defender firewall is turned off. Any help would be appreciated.

**Posted by rvsail** 8/28/2025 10:18 am

NMEA remote is working for me just fine on 15.

I don’t use 0.0.0.0
I use 192.168.1.255. (My network is 192.168.1.x)
And I use port 5010

Actually NMEA is just picking up the same stream that I use to transmit and receive from the laptop down below (in slave mode) and my Mesa 3 which runs its own EXP copy.

**Posted by Nick** 8/29/2025 4:12 pm

0.0.0.0 is used for unspecified or any local address, but it isn't a valid destination for TCP or UDP.

I think it is only for binding & listening. Sending to it doesn't make sense, so Winsock returns an error.

In this case, 192.168.1.255 is the correct option for a subnet broadcast.

If you intend to send to your local machine, you could use 127.0.0.1.

**Posted by BR29** 8/30/2025 3:59 pm

Thank you both for your replies. I can confirm that it works with a .255 IP address from the local Wifi range.

Strange that it worked with blanks until recently but not sure it matters.