Interfacing a SeaTalkng backbone to a third party backbone - Printable Version +- Raymarine forum (http://forum.raymarine.com) +-- Forum: Raymarine Forums (/forumdisplay.php?fid=1) +--- Forum: Networking / System Integration (/forumdisplay.php?fid=21) +--- Thread: Interfacing a SeaTalkng backbone to a third party backbone (/showthread.php?tid=2330) |
Interfacing a SeaTalkng backbone to a third party backbone - Chuck - Raymarine - Moderator - 01-09-17 11:29 AM Interfacing a SeaTalkng backbone to a third party backbone For simplicity and reliability, it is considered to be a best practice that the NMEA 2000 backbone be constructed from SeaTalkng / NMEA 2000 networking components of a single manufacturer. Spur adapters may then be used to adapt products to be mated as spurs to the backbone. Please click here to view a FAQ addressing this subject. Should one desire to mate a SeaTalkng backbone to an existing third party backbone, then the backbone cables may simply be spliced together. Raymarine's SeaTalkng Backbone Cables have been constructed of color coded leads matching those specified within the NMEA 2000 standard ... click here to view a related FAQ. Should one desire to mate a SeaTalkng backbone to an existing third party backbone which has been constructed of cables terminating in DeviceNet plugs and sockets, then it would be recommended that a field installable DeviceNet (M) or DeviceNet (F) connector (ex. Maretron Micro/Mid Field Attachable Connectors, etc.) be used to replace one of the backbone plugs of a SeaTalkng Backbone Cable. Care must be taken to ensure that the backbone is being powered from a single 12VDC power insertion spur which is located at the approximate midpoint of the backbone's LEN load. RAYFAQ# |