Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[TG] [TG11] SeaTalk1 to NMEA 2000
01-05-20, 05:29 PM (This post was last modified: 01-06-20 04:21 PM by Chuck - Raymarine - Moderator.)
Post: #2
RE: [TG11] SeaTalk1 to NMEA 2000
Hello Neil,
  • The NMEA2000 specification says only use 1 power supply point (unless every one is fully isolated which is not usually the case). Since you will already have power coming into your ST1 network (ST60s) which will pass through the ST1-STNG convertor, do not add extra 12V supplies into either the convertor or other NMEA2000 cabling. Doing so can cause network reliability problems. You should also make sure that you connect yellow-shield but not red at the C80, because the C80 is also another point of potential power supply to the network. Incidentally, the C80 only has a single ST1 port rather than the two showing in your drawing.
  • The ST1-STNG convertor cannot convert AIS data. In your system as-drawn, you will not get AIS data on the C80. This is because the ST1 network was designed long before AIS existed and there is no support at all in the ST1 language for AIS data. To get AIS into a C-series or E-series Classic you must use NMEA0183.
  • If your C80's NMEA0183 port is already in use (usually to provide GPS data to a DSC VHF), you will need a multi-speed NMEA0183 multiplexer in order to be able to get AIS data into the C80 at the required 38,400 baud rate and still get standard 4800 NMEA0183 to the VHF (the Classic displays have only a single comms device which operates at a single speed for both input and output.) Raymarine AIS transceivers include a multiplexer to make this connection easy, but third-party may not.
  • You should join your STNG and standard NMEA2000 cabling via a blue (backbone) connector rather than a white spur connector. It appears in your drawing as if you have 3 backbone terminators, 1 in Devicenet/NMEA2000 style and 2 in STNG. If you don't join backbone-backbone (using STNG blue cabling) then you inevitably end up with either too many terminators or an empty blue backbone socket which is prone to a later misconnection, corrosion from condensation, or a short from something contacting the exposed (12V and data) pins in the empty socket.
  • I can't offer any opinion about sharing navigational data over Wifi to other devices, Raymarine no longer offers PC navigational software or interfaces. The gateway manufacturer will be able to advise you.

To simplify the connections, use a Raymarine AIS on NMEA0183 direct to the C80, forget the Devicenet T-pieces/network cabling entirely and connect the NMEA2000-ethernet gateway to a white spur socket on the ST1-STNG convertor via a Devicenet-STNG adaptor cable (Raymarine part A06075 (F Devicenet) or A06076 (M Devicenet)).


Raymarine since 1999.
Interests: Diagnosis of problems in sonar/fishfinders, NMEA2000, ethernet comms, autopilots, thermal cameras
Location: Sydney, Australia.

Please don't PM me asking for direct support, please ask a public question instead so that others can see the question and answer. Forum posts will always be answered before PM requests.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
[TG11] SeaTalk1 to NMEA 2000 - nsmi - 01-03-20, 06:41 PM
RE: [TG11] SeaTalk1 to NMEA 2000 - Tom - Raymarine - Moderator - 01-05-20 05:29 PM
RE: [TG11] SeaTalk1 to NMEA 2000 - nsmi - 01-06-20, 03:51 PM
RE: [TG11] SeaTalk1 to NMEA 2000 - nsmi - 01-07-20, 09:03 AM
RE: [TG11] SeaTalk1 to NMEA 2000 - nsmi - 01-19-20, 06:46 PM
RE: [TG11] SeaTalk1 to NMEA 2000 - nsmi - 01-20-20, 07:17 PM

Forum Jump:

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