We have two networks onboard both a NMEA2000 and a SealkNG. The reason for this is that the autopilot was an old Autohelm system that we replaced with a Raymarine system (Raymarine bought Autohelm) the reason for that was that the linear drive unit is the same today as it was for the Autohelm system, took half an hour to replace the old drive with the new one (including swapping out the rudder sensor). In my opinion the standard NMEA2000 network is far better then the SeatalkNG (is based on NMEA2000). Why? NMEA2000 uses that same cables for backbone and drop-cables (atleast that is my understanding) while SeatalkNG are using different ones (different colour coded connectors). The price for the SeatalkNG cables are as much as 4 times the cost for NMEA2000 cables. We are using the SeatalkNG only for the autopilot system and NMEA2000 for the rest. The problem with this is that i have to manage the autopilot through the AP-display and not from ex. the plotter.
We are using the plotter (Garmin 721) to display seacharts and other information lika engine temp (we can choose any information which are flowing through the network). We have two smaller display’s (Garmin GMI20 and Garmin GNX20) where we are showing wind and depth on (same with the display’s, can show any NMEA2000 data).
- For depth and speed we have a DST800 NMEA2000 transducers.
- Wind we have the Garmin GMI start pack through NMEA2000.
- Engine data through Engine Gateway YDEG-04 NMEA2000
- AIS Amec Camino 108S through NMEA2000.
- Digital Thermometer (for engine room temp) YDTC-13N NMEA2000
- WI-FI gateway YDWG-02N to se data from sensors on TAB or Phone NMEA2000.
- Autopilot system Raymarine EV-200 through SeatalkNG.