NMEA 2000 RAW network gateway

Send BoatKit's physical NMEA 2000 traffic to specific RAW TCP or UDP targets, or broadcast it over UDP on the vessel network.

NMEA 2000 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 configured physical NMEA 2000 input on the BoatKit host
  • A local application that understands Yacht Devices-compatible RAW TCP or UDP
  • The destination IP and port, or a vessel LAN that permits UDP broadcast

Account or license

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

Every hosted BoatKit vessel includes the RAW gateway. Enable it in settings to share frames from the vessel’s configured physical NMEA 2000 input with compatible applications. Output can go to a specific TCP destination, a specific UDP destination, or a UDP broadcast address; each targeted path names the destination IP and port explicitly.

Targeted connections are useful when one known charting or diagnostic application should receive the feed. UDP broadcast makes the same traffic discoverable to compatible listeners across the local network without configuring every listener separately. Standard and proprietary frames are forwarded without a PGN allow/deny filter, so the destination and network scope should be chosen deliberately.

This integration shares raw traffic rather than decoding it for BoatKit. One or more NMEA 2000 input integrations still need to be configured when BoatKit itself should claim an address, decode data, and participate on each independent physical network. The gateway setting and behavior are the same whether the hosted vessel runs in the mobile app or on a BoatKit device.