Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[CA] E120 data feed, move from Seatalk 1 to Seatalk ng
11-02-17, 03:40 PM (This post was last modified: 11-02-17 03:41 PM by Chuck - Raymarine - Moderator.)
Post: #8
RE: E120 data feed, move from Seatalk 1 to Seatalk ng
Lothar,

The E-Series Classic MFDs are exclusively designed to support AIS features when interfaced via NMEA 0183 to the AIS receiver / transceiver. The MFD will not process any AIS data from a SeaTalkng / NMEA 2000 source of AIS data.

Autopilot course computers are not designed to function as complete NMEA 0183 to SeaTalk data bridging devices. Should you desire to add GPS data to the SeaTalk bus, then the RS125 should be interfaced to the SeaTalk bus rather than to the NMEA 0183 port of the autopilot course computer, as your diagram currently shows. To do so, the red and green leads of the RS125's cable would be interfaced to the red lead of a SeaTalk Cable, the brown and black/shield leads of the RS125's cable would be interfaced to the shield lead of the SeaTalk Cable, and finally, the yellow lead of the RS125's would be interfaced to the yellow lead of a SeaTalk Cable.

Your SeaTalkng backbone within your diagram does not include a 12V power insertion spur socket. The diagram does not appear to show an autopilot control head within the system. Additionally, it is unclear from the diagram whether the red power lead of the SeaTalk cable connected to the S3G's SeaTalk terminal has been disconnected. Should this red lead remain connected, then it may cause communications problems.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: E120 data feed, move from Seatalk 1 to Seatalk ng - Chuck - Raymarine - Moderator - 11-02-17 03:40 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)