How AIS Transceivers Integrate with NMEA 2000 (and Where Things Go Wrong with Older NMEA 0183 Gear)

AIS has become one of the most important safety tools aboard a cruising yacht, and modern AIS transceivers are built with NMEA 2000 in mind. When everything on board speaks the same protocol, integration is almost effortless: plug the transceiver into the backbone, and your MFD immediately receives all AIS data in the correct PGNs.

The complications begin when older NMEA 0183 equipment is added to the mix. AIS pushes a lot of data, and 0183 simply wasn’t designed for that volume. The result is often missing targets, lagging updates, or partial information on the display — all of which undermine the very purpose of AIS.

This article explains how AIS behaves on a clean NMEA 2000 network, what goes wrong when 0183 devices are involved, and how to design a hybrid system that remains reliable offshore.

How AIS Works on a Modern NMEA 2000 Network
Why Integration Is So Much Easier on NMEA 2000
The Problems That Start When You Add NMEA 0183 Devices
Common 0183–to–2000 Conversion Issues
How to Build a Stable Hybrid Network
Recommended Sentence Mapping for Hybrid Installations
Summary: The Cleanest Path to a Reliable AIS Network

How AIS Works on a Modern NMEA 2000 Network

NMEA 2000 is a high‑speed, multi‑talker, multi‑listener network running at 250 kbps. AIS fits into it perfectly because all AIS‑related data is standardised into PGNs that every modern MFD understands.

Key AIS PGNs include:

129038 — Class A Position Report
129039 — Class B Position Report
129040 — Class B Extended
129041 — AtoN Report
129793 — UTC and Date
129794 — Class A Static and Voyage Data
129809/129810 — Class B “SO” Static Data

Once connected:

The MFD auto‑discovers the AIS transceiver
Targets appear instantly
No sentence mapping or baud‑rate configuration is required
AIS GPS can be used as a high‑integrity position source
DSC calling from AIS targets becomes available on compatible systems

In short, NMEA 2000 is plug‑and‑play for AIS.

Why Integration Is So Much Easier on NMEA 2000

Three reasons stand out:

1. Standardisation

Every AIS device outputs the same PGNs, and every modern MFD knows how to interpret them.

2. Bandwidth

NMEA 2000’s 250 kbps is more than enough for dense AIS traffic, even in busy shipping lanes.

3. Automatic data management

The network handles multiple talkers, prioritises data, and resolves conflicts without user intervention.

This is why AIS installations on NMEA 2000 are so straightforward compared to the 0183 era.

The Problems That Start When You Add NMEA 0183 Devices

NMEA 0183 was designed for simple GPS sentences at 4,800 baud. AIS requires 38,400 baud, and even then the pipe is narrow. When you mix 0183 equipment into a modern AIS setup, several issues appear.

1. Baud‑rate mismatches

If an older plotter only accepts 4,800 baud, it simply cannot display AIS. No workaround exists.

2. Missing or incomplete AIS sentences

AIS over 0183 uses sentences such as:

!AIVDM / !AIVDO — AIS target and own‑vessel data
RMC, GGA, VTG — GPS position
HDG/HDT — heading

Legacy plotters often understand only a subset, leading to:

Targets with no names
No CPA/TCPA
Missing vessel dimensions
No static data for Class B units

3. Multiplexer overload

AIS sentences are large and frequent. When combined with GPS, wind, depth, and heading on a single 0183 input:

Data gets dropped
Updates lag
Targets jump or vanish

4. Older plotters that cannot process AIS at all

Some legacy MFDs were never designed for AIS and will not display targets even when fed correct data.

5. Grounding and isolation issues

0183 requires isolated inputs and outputs. Many older devices are not isolated, causing:

Ground loops
Intermittent data
Total communication failure

Need help choosing the right AIS unit for your boat and your budget? Click here to see my recommended models and comparison table.

Common 0183–to–2000 Conversion Issues

If you bridge AIS between 0183 and NMEA 2000 using a gateway (Actisense NGW‑1, Yacht Devices YDNG‑02, etc.), you must configure it correctly.

Typical problems include:

Incorrect sentence mapping (e.g., VDM disabled)
Gateways that don’t support all AIS message types
0183 ports limited to 4,800 baud
Multiple GPS sources causing conflicts
Static AIS data not being passed through

A gateway can only convert what it receives — and only at the speed the 0183 device can output.

How to Build a Stable Hybrid Network

If you must mix NMEA 2000 and 0183 equipment, the goal is to keep AIS on NMEA 2000 and use 0183 only where necessary.

Best‑practice architecture

Put the AIS transceiver on NMEA 2000
Feed the MFD via NMEA 2000
Send only essential data to 0183 devices (e.g., GPS to a DSC VHF)
Avoid routing AIS targets through 0183 unless unavoidable
Use a properly configured gateway
Disable redundant GPS outputs to prevent conflicts

This keeps AIS traffic on the fast network and prevents 0183 bottlenecks.

Recommended Sentence Mapping for Hybrid Installations

Below is a practical mapping guide for a cruiser running AIS on NMEA 2000 with a legacy 0183 VHF or plotter.

Function	NMEA 2000 PGN	NMEA 0183 Sentence	Notes
AIS Targets	129038, 129039, 129040	!AIVDM / !AIVDO	Send via 0183 only if the legacy device supports AIS.
Own‑Vessel GPS	129029	RMC, GGA, VTG	Required for DSC VHFs and older autopilots.
Static AIS Data	129794, 129809	VDM (Type 5/24)	Often lost during 0183 conversion.
Heading	127250	HDG, HDT	Needed for CPA/TCPA and MARPA.
Depth/Speed/Wind	128259, 128267, 130306	DPT, VHW, MWV	Low‑bandwidth; safe to pass through 0183.

Summary: The Cleanest Path to a Reliable AIS Network

AIS works flawlessly on NMEA 2000 because the protocol was designed for high‑speed, high‑volume data. The moment older NMEA 0183 devices enter the picture, you introduce:

Baud‑rate mismatches
Missing AIS sentences
Multiplexer overload
Legacy plotters that cannot process AIS
Conversion losses and GPS conflicts

If you’re running a hybrid network, the key is to keep AIS on NMEA 2000 and use 0183 only where absolutely necessary. With correct wiring, sentence mapping, and data prioritisation, even a mixed system can be made reliable — but it requires deliberate design rather than plug‑and‑play assumptions.

This article was written by Dick McClary, RYA Yachtmaster and author of the RYA publications 'Offshore Sailing' and 'Fishing Afloat', member of The Yachting Journalists Association (YJA), erstwhile member of the Ocean Cruising Club (OCC) and owner/administrator of 'Liveaboard Sailboats for Sale'.