Adapting devices having a NMEA 0183, SeaTalk, or SeaTalkng / NMEA 2000 to Ethernet

[Chuck - Raymarine - Moderator]

Adapting devices having a NMEA 0183, SeaTalk, or SeaTalkng / NMEA 2000 to a Raymarine Ethernet (SeaTalkhs / RayNet) network

Compatible Raymarine, FLIR, and some third party IP cameras having an Ethernet (SeaTalkhs / RayNet) communications interface are designed to communicate with one another via the system's Ethernet network. In support of such networking, Raymarine offers Ethernet Switches and Ethernet networking cabling components having weatherproof couplers (SeaTalkhs and RayNet). Additionally, some of MFDs will feature more than one Ethernet communications interface to reduce or eliminate the need for an Ethernet network switch in systems where all of the system's MFDs will typically be switched ON when the system is in use.

It is not possible to adapt devices lacking an Ethernet interface, but having a NMEA 0183, SeaTalk, or SeaTalkng / NMEA 2000 to a Raymarine Ethernet (SeaTalkhs / RayNet) network. Devices lacking an Ethernet interface, but having a NMEA 0183, SeaTalk, or SeaTalkng / NMEA 2000 must be interfaced as follows to the Raymarine system:

- NMEA 0183: as a best installation practice, devices featuring a NMEA 0183 communications may be interfaced to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone via a NMEA 0183 to NMEA 2000 data bridging device (ex. Actisense NGW-1-ISO-STNG, Actisense NGW-1-ISO-AIS, etc.). Any Raymarine MFD featuring a NMEA 0183 communications interface and a SeaTalkng / NMEA 2000 communications interface may also be used for such purposes. Limitations of using a MFD as a NMEA 0183 to SeaTalkng / NMEA 2000 data bridging device include a requirement that the MFD be switched ON whenever such data bridging is required and that AIS data will not be bridged.

- SeaTalk: As a best installation practice, it is recommended that a SeaTalk to SeaTalkng Converter Kit(s) be used to bridge data from a SeaTalk bus featuring compatible devices having a SeaTalk communications interface to a system's SeaTalkng / NMEA 2000 backbone. Please click here to view a FAQ addressing how to interface products having a SeaTalk interface to a SeaTalkng backbone. Alternatively, should the system's MFDs feature a SeaTalk communications interface and an Ethernet communications interface, then the SeaTalk interface of the system's Data Master MFD may be used to bridge supported data from the SeaTalk devices to the system's Ethernet and/or SeaTalkng / NMEA 2000 network. As with NMEA 0183 data bridging by a MFD, the limitation of using a MFD as a SeaTalk to SeaTalkng / NMEA 2000 data bridging device is that the MFD be switched ON whenever such data bridging is required.

- SeaTalkng / NMEA 2000: These devices are designed to be interfaced as individual spurs (max spur cable length is 6m) to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone. The system's Data Master MFD will also be interfaced as a spur the the system's SeaTalkng / NMEA 2000 backbone. It is the responsibility of the system's Data Master MFD to bridge supported data from the SeaTalkng / NMEA 2000 backbone to the system's Ethernet network. Unlike a MFD's NMEA 0183 communications interface, only the system's Data Master MFD will feature an active SeaTalkng / NMEA 2000 communications interface.


RAYFAQ#