Seatalk ng NMEA 2000

Popski

Well-Known Member
Joined
19 Jul 2017
Messages
71
Visit site
Hi everyone and please accept my apologies for this thread. I know similar post are here on the forum and honestly I have looked till my eyes are bloodshot. So please bear with me when I ask......

I have plumped for Simrad GO12 display with Simrad auto pilot, AIS antenna splitter and transceiver.

Installed from new on the boat is RayMarine chart plotter (A70d) + ST70 mfd and thru hull transducer. I have now installed the new GO12 display on the fly bridge and now looking to hook up the NMEA 2000 backbone to the existing seatalk ng with the hope that all will communicate together. I have the adapter cable that allows the NMEA 2000 to connect to the seatalk backbone but now I’m stuck. Can’t get anything to talk with the GO12. (Not yet installed the autopilot so going in stages). Can anyone point me to a typical layout of my intended installation including the connections between backbones. If I could find either a schematic or even a YouTube vid that would be a start at least.

I guess the obvious question is why did I not just buy RayMarine instead of Simrad well it was offered to me at a price I could not refuse.

Any help or advise will be much apreciated.
 
Hi everyone and please accept my apologies for this thread. I know similar post are here on the forum and honestly I have looked till my eyes are bloodshot. So please bear with me when I ask......

I have plumped for Simrad GO12 display with Simrad auto pilot, AIS antenna splitter and transceiver.

Installed from new on the boat is RayMarine chart plotter (A70d) + ST70 mfd and thru hull transducer. I have now installed the new GO12 display on the fly bridge and now looking to hook up the NMEA 2000 backbone to the existing seatalk ng with the hope that all will communicate together. I have the adapter cable that allows the NMEA 2000 to connect to the seatalk backbone but now I’m stuck. Can’t get anything to talk with the GO12. (Not yet installed the autopilot so going in stages). Can anyone point me to a typical layout of my intended installation including the connections between backbones. If I could find either a schematic or even a YouTube vid that would be a start at least.

I guess the obvious question is why did I not just buy RayMarine instead of Simrad well it was offered to me at a price I could not refuse.

Any help or advise will be much apreciated.

I dont know the answer but ....

- not seeking to be picky but you have connected to Seatalk - you dont say sea talk NG - this is important as they are different things and the raymarine unit may well support both.

- I have just had to get involved with Seatalk NG and the bus must be powered. Is it ? Is the power working at 12v?

- I dont know either unit but there will be integration settings or similar on both units and these may well need to be configured. By "talk to" I assume for example that the depth is not showing on the Simrad? The units are unlikely to have a chat at anything more than a superficial level - GPS data, speed, depth etc. they wont share radar images ( will i would be surprised) for example.

- Raymarine ( well mine) has a diagnostic page that let yo see all external interfaces and if they are active. So I can see for example 2 auto helm controllers, 2 depth instruments, autohelm controller etc. etc. If you find this page it may give you some idea of what can see what. Simrad may or may not having something similar.
 
Hi first thanks for the reply. I again visited the boat today and hooked up the NMEA 2000 with the seatalk ng and lo and behold all worked now getting depth sea temp cog & dog from the a70d etc. Just got to install the AIS and ap etc. Will post my progress here. Thanks again
 
It's worth adding that if you're trying to interface Seatalk ng to NMEA 2k you need to attach backbone to backbone. See Q2 and A2 in the linked post: http://forum.raymarine.com/showthread.php?tid=1067

But it sounds like you've got there already.
Nope. Q2 and A2 are talking about connecting seatalk 1 to N2k. That's a completely different thing from interfacing seatalk ng to N2k.
 
Top