[CA] [CA11] Seatalk and NMEA data crossover on S2 autopilot - Printable Version +- Raymarine forum (http://forum.raymarine.com) +-- Forum: Raymarine Forums (/forumdisplay.php?fid=1) +--- Forum: Autopilots (/forumdisplay.php?fid=23) +--- Thread: [CA] [CA11] Seatalk and NMEA data crossover on S2 autopilot (/showthread.php?tid=9178) |
[CA11] Seatalk and NMEA data crossover on S2 autopilot - chopin.georgesand - 08-06-19 03:24 PM I use a S2 autopilot and a e7 MFD connected to the autopilot through the NMEA 0182 ports. Seatalk is not connected to the e7. I would like to know if any data coming in from the NMEA input port on the S2 will be converted and transmitted on the Seatalk network by the S2 and conversely, if any data coming in from the Seatalk network on the S2 if it will be converted and transmitted on the NMEA port on the S2. Thx. RE: [CA11] Seatalk and NMEA data crossover on S2 autopilot - Chuck - Raymarine - Moderator - 08-07-19 04:00 PM Welcome to the Raymarine Forum, It would generally be recommended that an E22158 SeaTalk to SeaTalkng Converter Kit be installed for such purposes. Doing so would not only ensure that each device has access to data from the SeaTalk bus and SeaTalkng backbone, but doing so may also avoid potential creation of a NMEA 0183 data loop. The latter may be created when data received via a devices NMEA 0183 communications interface is re-transmitted (via its NMEA 0183 output port) back to the original transmitter. For this reason, those electing to interface via NMEA 0183 will do so in a manner which would support one way communications or will install a programmable NMEA 0183 multiplexer (ex. Actisense NDC-4-USB, etc.) to filter out re-transmitted NMEA 0183 sentences sent from the MFD to the autopilot. Please click here to view a FAQ addressing this subject. |