Connecting the NMEA multiplexer in Wi-Fi client mode to the Starlink router
Principle
In Wi-Fi "client mode", the multiplexer connects to the Starlink router's Wi-Fi network like any other device. It obtains a local IP address and exposes its NMEA stream over TCP on that network.
NMEA 0183 instruments → NMEA multiplexer (Wi-Fi client mode) → Wi-Fi → Starlink router (192.168.100.1 by default)
- Internet (Starlink WAN)
- Multiplexer → example: 192.168.100.x:10110
- iPad/iPhone with NavimetriX
Step-by-step configuration
1. Switch the multiplexer to Wi-Fi client mode
Depending on the model, via its web interface (often 192.168.1.1 or 192.168.4.1, set to access point mode by default):
- Yacht Devices YDNM-02: menu "Network → Wi-Fi → Station mode"
- Actisense W2K-1: menu "Wireless → Client mode"
- Vesper XB-8000: menu "Network → Join existing network"
Enter the SSID and password of the Starlink network.
2. Find the IP assigned to the multiplexer
Once connected, look up the IP in the Starlink router's admin interface:
- Starlink app → Network → Connected devices
3. Give the multiplexer a fixed IP (recommended)
To prevent the IP from changing at every restart:
- either via the Starlink router: a "static DHCP lease" tied to the multiplexer's MAC address;
- or via the multiplexer itself: assign it a fixed IP within its range.
4. Configure NavimetriX
Open Settings by tapping the chevron handle (‹) on the right edge of the screen, then GPS & NMEA:
- turn the NMEA switch on (Premium subscription);
- NMEA Protocol: TCP;
- Server IP address: the multiplexer's IP (example: 192.168.100.42);
- Server port: the multiplexer's port (example: 10110, the standard NMEA 0183 port; check for your device).
Over TCP, the Scan NMEA devices button only tries the default addresses of common gateways: it will not find a multiplexer that received a different address from the Starlink router, which is why you should note its IP. However, if the multiplexer also transmits over UDP on a common port (10110, for example), the scan finds it without knowing its address.
Precautions
- The Starlink router uses "double NAT". This is no problem for local use: everything stays on the local network.
- "AP isolation" enabled on the Starlink: it must be turned off, as it prevents Wi-Fi devices from seeing each other.
- The multiplexer's IP changes: set a static DHCP lease by MAC address (in the Starlink app).
Checking that it works
Once the TCP connection is up (example: 192.168.100.42:10110), NMEA sentences ($GPGGA, $GPRMC, !AIVDM…) should scroll in the Incoming NMEA sentences console at the bottom of the GPS & NMEA page.
The NMEA stream and the Internet coexist perfectly: they use the same Wi-Fi network, but the traffic stays separate by nature (local on one side, Internet on the other).