Raymarine forum

Full Version: Interfacing a SeaTalkng backbone to a third party NMEA 2000 backbone
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Interfacing a SeaTalkng backbone to a third party NMEA 2000 backbone

While there is no standard for coupling components used to construct the physical layer of a NMEA 2000 backbone, there is a standard for the colors of the leads within a backbone' cable. The most commonly used NMEA 2000 coupling components are the DeviceNet Micro-C couplings shown below:

[Image: attachment.php?aid=140]

At the time that this thread was posted, Raymarine did not offer SeaTalkng to DeviceNet (F) and SeaTalkng to DeviceNet (M) Backbone Cable Adapters. When slicing backbone cables together, the information below may aid in understanding the function of each color lead of a SeaTalkng Backbone Cable (5-pin blue/black cable below).

[Image: attachment.php?aid=141]

While it is is possible to splice a SeaTalkng backbone cable to a third party manufacturer's NMEA 2000 backbone cable, plug and socket connections are generally preferred. Accordingly, some third party manufacturers of NMEA 2000 networking components (ex. Maretron, etc.) offer DeviceNet Micro-C Male and Female plugs. These DeviceNet Micro-C plugs may in turn be installed onto one end of a SeaTalkng Backbone Cable to create a SeaTalkng to DeviceNet Micro-C Backbone Adapter Cable.

NOTE: A SeaTalkng backbone must not be joined to an engine manufacturer's backbone using the methods described above. Instead, the engine manufacturer's backbone must be bridged to the marine electronics backbone using NMEA 2000 engine gateway. Please click here to view a FAQ addressing this subject.

Reference URL's