SeaTalk NG to NMEA connections

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum jdelarue,

You have been advised incorrectly, when updated with v1.21 or later SeaTalk to SeaTalkng Converter software, the converter will support transmission of a limited set of 4800 BAUD NMEA 0183 GPS sentences (principally targeted at satisfying the requirements of a DSC VHF radio having only a NMEA 0183 interface) when the converter has been interfaced to a SeaTalkng/NMEA 2000 source of GPS data.

Specically, the SeaTalk to SeaTalkng Converter will output / transmit (tx) the following 4800 BAUD NMEA0183 v4.10 sentences:

- GGA - If L/L is present on STng, then GGA will Tx only populating data fields that are available, i.e. time/date etc.
- RMC - If L/L is present then RMC will Tx only populating data fields that are available, i.e. time/date etc.
- VTG - If SOG and/or COG valid in 129026 then VTG will Tx only populating data fields that are available, i.e. variation etc.

In this case, it should have been recommended that a third party SeaTalkng/NMEA 2000 to NMEA 0183 data bridging device (ex. Actisense NGW-1-STNG, etc.) have been interfaced to the SeaTalkng/NMEA 2000 backbone to support bridging SeaTalkng wind data to NMEA 0183.

In order to display AIS data on an i70 MFID, each of the following criteria must be satisfied:
- the SeaTalkng/NMEA 2000 backbone must be interfaced to a source of AIS data (ex. AIS350/650, AIT2000, etc.)
- the SeaTalkng/NMEA 2000 backbone must be interfaced to a source of GPS data
- the SeaTakng/NMEA 2000 backbone must be interfaced to a source of heading data or the vessel must be underway and making way to permit COG to be substituted for heading.