[CA] [CA11] nmea to seatalkng
|
09-20-18, 02:45 PM
Post: #2
|
|||
|
|||
RE: [CA11] nmea to seatalkng
Welcome to the Raymarine Forum Bejasus,
The specified VHF radio / AIS receiver appears to have a NMEA 2000 communications interface featuring a DeviceNet (M) plug. Raymarine offers the A06075 / 39.4in (1.0m) DeviceNet (F) to SeaTalkng Spur Cable to facilitated interfacing such devices to a SeaTalkng spur socket. Unlike SeaTalkng networking protocol which had permitted up to three devices to be daisy chained within a single spur (maximum total spur length = 6m), the NMEA 2000 networking protocol permits only one device per spur. As Raymarine is seeking NMEA 2000 Certification for its products, most current and all future Raymarine product designs having a SeaTalkng / NMEA 2000 communications interface will feature one spur socket instead of two spur sockets. This will thereby prevent such daisy chains. As third party devices having a NMEA 2000 communications interface have not been designed with the daisy chaining which had been supported by the SeaTalkng networking protocol, it is recommended that third party devices be interfaced to the backbone via a dedicated spur. Accordingly, should the current backbone feature 5-Way Connector, T-Piece, SeaTalk to SeaTalkng Converter, or iTC-5 having an unused SeaTalkng Spur socket, then it would be recommended that the third party device be interfaced to that spur socket. Should the spur socket not be located within 1m of the third party product, then the backbone will need to be extended to within 1m of the third party product. Please click here to view a FAQ addressing how a backbone may be extended to add spur sockets. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
[CA11] nmea to seatalkng - Bejasus - 09-20-18, 12:10 PM
RE: [CA11] nmea to seatalkng - Chuck - Raymarine - Moderator - 09-20-18 02:45 PM
|
User(s) browsing this thread: 1 Guest(s)