NMEA 0183 output gateway

Send selected BoatKit GPS, depth, and AIS output to specific TCP or UDP targets, or broadcast it over UDP on the vessel network.

NMEA 0183 output paths

Connection checklist

What you need

Tablet

Available. Enable the gateway in the hosted vessel's settings; it behaves the same when BoatKit is hosted by the mobile app.

Dedicated BoatKit device

Available. Enable the same gateway setting; its configuration and behavior are identical when BoatKit is hosted by a device.

Hardware and network

A local TCP or UDP destination for the selected NMEA 0183 sentences
A documented selection of GPS, depth, and AIS output categories, destination IPs, and ports
A network design that prevents generated output from looping back into an input

Account or license

No BoatKit Cloud account or third-party service license is required for the local gateway. Downstream applications may have their own licensing.

Every hosted BoatKit vessel includes the NMEA 0183 output gateway. Enable it in settings and select which BoatKit GPS, depth, and AIS categories should become local sentences for compatible applications and displays.

Output can go to a specific TCP IP and port, a specific UDP IP and port, or a UDP broadcast address for listeners across the vessel LAN. Targeted output suits a known charting or instrument application; broadcast suits several connectionless listeners.

Input is configured separately through NMEA 0183 input integrations. As with any protocol bridge, the network design must prevent BoatKit’s generated output from returning through an input and recreating the same data. The direction and port of each connection should be documented during installation.

The gateway setting and behavior are the same whether the hosted vessel runs in the mobile app or on a BoatKit device.

Explore other integrations