mstrpo
Member
- Joined
- Aug 27, 2021
- Messages
- 66
- Reaction score
- 2
- Location
- Battle Ground
- C Dory Year
- 2007
- C Dory Model
- 255 Tomcat
- Vessel Name
- C-Otter
Hi All,
I didn't see this topic in the archives via search so thought I'd add what I know from recent activities on my tomcat. Sorry for the long note but I think the context helps.
Some context: I recently added the Garmin Reactor AP system to my boat for cruising and slow trolling while fishing. The AP works very well at speed but the 'slow speed mode' would not work with my setup. FWIW, slow speed mode is supposed to react 'better' when going very slow. I don't yet know what 'better' means as I haven't had the boat out since recent changes. What I learned online is that using GPS for the AP speed source isn't precise enough for the AP system to know the boat is under power when going sub 1.5 mph (troll speed for me!) and so you need to reconfig the AP to use engine RPMs. To accomplish this, you need at least the engine tach info on the NMEA2000 network, which meant I needed to add at least one engine to the network.
To add the Honda outboards to the NMEA2000 network, you need a Honda cable that plugs into an existing connector on the motor (~2010 and newer Hondas have this). Then you need to add your motor(s) to the existing NMEA2000 network. Some research online led me to believe my 2019 and 2020 motors would provide power to the NMEA2000 network and that I would need power isolator connections on the NMEA2000 network as multiple power sources can cause intermittent and undesired behavior. This was bad info! My engines to not power the network so I had to remove these connectors. One last tidbit on adding multiple Hondas to the same NMEA2000 network: The engines will show up an a scan of devices on the network, but my Garmin MFD will only use of them on the 'engine' display! This is due to an element in the NMEA2000 data set called "Instance Id". Understandably, Honda delivers all engines with the same value (1 I think). Garmin is clearly using this element to enumerate the engines. I understand the fix to this issue requires use of a special diag tool (sw) that only dealers have called Dr. H. to set one of the enginese to a different value. I'm working now to find a local dealer who can/will do this.
I'll update this thread once I get the boat on the water and test the slow speed mode.
I didn't see this topic in the archives via search so thought I'd add what I know from recent activities on my tomcat. Sorry for the long note but I think the context helps.
Some context: I recently added the Garmin Reactor AP system to my boat for cruising and slow trolling while fishing. The AP works very well at speed but the 'slow speed mode' would not work with my setup. FWIW, slow speed mode is supposed to react 'better' when going very slow. I don't yet know what 'better' means as I haven't had the boat out since recent changes. What I learned online is that using GPS for the AP speed source isn't precise enough for the AP system to know the boat is under power when going sub 1.5 mph (troll speed for me!) and so you need to reconfig the AP to use engine RPMs. To accomplish this, you need at least the engine tach info on the NMEA2000 network, which meant I needed to add at least one engine to the network.
To add the Honda outboards to the NMEA2000 network, you need a Honda cable that plugs into an existing connector on the motor (~2010 and newer Hondas have this). Then you need to add your motor(s) to the existing NMEA2000 network. Some research online led me to believe my 2019 and 2020 motors would provide power to the NMEA2000 network and that I would need power isolator connections on the NMEA2000 network as multiple power sources can cause intermittent and undesired behavior. This was bad info! My engines to not power the network so I had to remove these connectors. One last tidbit on adding multiple Hondas to the same NMEA2000 network: The engines will show up an a scan of devices on the network, but my Garmin MFD will only use of them on the 'engine' display! This is due to an element in the NMEA2000 data set called "Instance Id". Understandably, Honda delivers all engines with the same value (1 I think). Garmin is clearly using this element to enumerate the engines. I understand the fix to this issue requires use of a special diag tool (sw) that only dealers have called Dr. H. to set one of the enginese to a different value. I'm working now to find a local dealer who can/will do this.
I'll update this thread once I get the boat on the water and test the slow speed mode.