bookending the combo network? Question 2 is, should this combo network of mine pull power from the Axiom MFD or do I add possibly a second power drop onto either the NMEA2000 portion or the SeaTalkNG portion? In my case all of that stuff will be on the bridge but I expect to run a 10m NMEA2000 backbone to the salon to connect to the AV system and possibly tank monitors, etc Anyway, your article is timely and I have at least two questions: If I create a combo network of NMEA2000 via the Ancor 4-Tee and in my case the “Raymarine Seatalk1 To Sea Talk-Ng Converter” (E22158), question 1 is where do the terminations go? One on the end of the NMEA2000 Ancor 4-Tee (or a backbone connected after the 4T) and another termination on the end of the SeaTalk E22158? i.e. I’m thinking of trying to bring it all together and maybe add a second Axiom for the engine data using Yacht Devices J1939 to NMEA2000 adaptors. I just took possession of a boat that has a Raymarine Axiom 12 MFD (NMEA2000 with DeviceNet male cable currently unused), a Raymarine ST60+ Depth finder that doesn’t currently communicate depth to the Axiom, and twin Crusader gas engines whose ECM’s output J1939. I’ve asked Raymarine about their plans and haven’t gotten a clear answer about where the system is headed.īern, thank you for taking the time to document your exploration with these networks. So, is Raymarine sunsetting STng? I thought so for a while but then I’ve seen new products, including their brand new YachtSense boat control system, with STng connectors. Axiom MFDs all have a standard NMEA 2000 DeviceNet connector on the back, not STng. I’ve been trying to figure out if Raymarine is moving away from SeaTalk NG for some time. The new backbone adapters join several other STng adapters Raymarine introduced in January of 2019, and along with the many spur adapters also available, I think that Raymarine now has a range that fits just about any need. SeaTalk NG to DeviceNet adapters introduced in 2019 The use of the spur adapter has never caused any issues on my network, but it’s always bothered me that I had to rely either on this hack or hand-splicing cables to adapt the network. From there I’ve connected an additional tee connector and finally a terminator to provide the appropriate termination to the network. But rather than continuing the network through the other backbone port in the tee, I ran an STng/N2K spur adapter cable to the backbone port of an Ancor 4-device tee.
In the top left of the photo above, note the STng tee with the incoming blue-striped backbone cable. Thus I learned that there’s an alternative to the backbone splicing method, easier though not any more pretty. I know this issue well because I built Have Another Day’s first NMEA 2000 network using SeaTalk NG cabling and since then have converted most of it to standard N2K DeviceNet cabling. One end of Have Another Day’s NMEA 2000 network is adapted from SeaTalk NG to DeviceNet Also, I’d say that Raymarine offering these adapters validates the fact that STng is truly N2K with a different cabling scheme. This never seemed like a good solution, so I’m very happy to (finally) see Raymarine offer these adapters. In fact, on their own forum, Raymarine suggests chopping off one end of STng backbone and standard N2K cables and then splicing the two together. It’s always been a mystery to me that Raymarine didn’t offer an STng backbone to N2K plug adapter even though the spur adaptor was available when SeaTalk NG launched in 2007. I’d love to provide you links to Ray’s web pages for these adapters, I’m guessing they will appear in the adapter cable section of the SeaTalk NG page soon. Backbone cables won’t fit in spur sockets and nor will spur cables fit in backbone sockets. Sockets on STng devices and tee connectors have blue and white locking collars to indicate the cable type. The backbone cables have a blue stripe and blue ends on the connectors while the spur cables have a white stripe and white connector. In a departure from NMEA 2000 standard cabling, SeaTalk NG uses separate backbone and spur cables. Good news! Raymarine now offers cables that adapt STng backbone to male (Raymarine Part number A80674) and female (A80675) N2K connectors. But, until very recently, Raymarine has not offered an adapter to convert the blue-striped SeaTalk NG (STng) backbone cables, only the white-striped spur cables. It’s compatible with NMEA 2000’s standard DeviceNet cabling through the use of adapters. Raymarine’s SeaTalk NG is Raymarine’s proprietary version of NMEA 2000 cabling. A sample SeaTalk NG network with both ends adapted to NMEA 2000 DeviceNet via the new adapters
0 kommentar(er)
