[CA] [CA11] Proper power config for E22158

[amajamar]

I am attempting to integrate depth and SOW information from my ST60 Tridata, with my third party (Garmin) NMEA 2000 network. Currently, the Tridata, GPS-RN300, and the GPS antenna is powered through an R55006 junction box. My intent is to use the E22158 to convert Seatalk1 to SeatalkNG and interface with already powered NMEA 2000 network. The GPS-RN300 will be eliminated from the system.

My question is do I use the power cable that came with the E22158? Am I correct in thinking that would be feeding the network in two places?

I am inserting a schematic of my intentions, so please review and let me know if you see any issues with my plans.

Thanks,

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum amajamar,

It is recommended that the ST7000+ autopilot control head be disconnected from the ST60 Tridata instrument and that it alone be interfaced to the Type 100 autopilot course computer's SeaTalk port. It is additionally recommended that the R55006 SeaTalk Auxiliary Junction Box not be used to power the SeaTalk bus. Instead, the SeaTalk bus should be powered from the SeaTalkng / NMEA 2000 backbone via the SeaTalk to SeaTalkng Converter. The SeaTalkng / NMEA 2000 backbone may be powered via one of its spur (white) sockets via the SeaTalkng Power Cable supplied with the SeaTalk to SeaTalkng Converter Kit. Finally, a SeaTalkng to DeviceNet Spur Adapter Cable should not be used to join the two backbones. Please click here to view a FAQ addressing how a backbone which has been constructed from SeaTalkng networking components may be interfaced to a NMEA 2000 backbone which has been constructed from third party NMEA 2000 networking components.

[amajamar]

Thank you Chuck for rapid review!

I have attached modified sketch of system layout to ensure that I understand correctly. To confirm, even though there is two connections to power (one at the E22158 and one at the NMEA 2000 backbone) this is not creating a network with two power supplies. Correct?

[Chuck - Raymarine - Moderator]

amajamar,

The diagram appears to be correct in all but possibly one area ... NMEA 0183 connection to the course computer. While connecting the system for one way communications such that the autopilot only receives data from the rest of the system will work, having the autopilot course computer transmit data back to the system may cause a data loop, preventing the chartplotter from cancelling navigation. Accordingly, you may want to try setting up the system as you have diagrammed and if you find that you are unable to cancel navigation (i.e. Go To Cursor / Waypoint or Follow Route) and then command navigation to a new destination, then it would be necessary to disconnect the leads from the autopilot course computer's NMEA 0183 OUT terminals.

[amajamar]

Chuck,

Please clarify the following:

My diagram shows power to both the NMEA 2000 backbone AND the E22158.

That seems to be in conflict with the basic "one power point" NMEA 2000 rules.

A previous thread located here: http://forum.raymarine.com/showthread.php?tid=2327 seems to indicate that the power connection for the E22158 and devices connected to it (ST60 tridata, in my case) will receive power from the existing NMEA 2000 backbone.

Which configuration is correct?

Thanks,

[Chuck - Raymarine - Moderator]

amajamar,

Q. My diagram shows power to both the NMEA 2000 backbone AND the E22158. Which configuration is correct?
A. Apparently I did not see that your existing NMEA 2000 backbone was powered. A system's SeaTalkng / NMEA 2000 backbone should be powered from a single power insertion spur which is located at the approximate midpoint of the backbone's LEN load.

[amajamar]

Chuck,

Following up on your comment, is there anything to be gained from having the NMEA 0183 Output connected? Is there any data from the course computer that any other parts of the rest of the system could use or needs? Which NMEA 0183 output sentences could cause the data loop?

Thanks,

[Chuck - Raymarine - Moderator]

amajamar,

The autopilot course computer transmits heading along with other supported data received by the autopilot. Should a programmable NMEA 0183 multiplexer be installed, between the NMEA 0183 output of the autopilot course computer and the NMEA 0183 to NMEA 2000 data bridge, then the multiplexer could be programmed to pass only heading and rudder angle data back to the system, thereby avoiding a data loop.

The complete list of NMEA 0183 output sentences transmitted by the Type 100/300 course computer may be found within the (NMEA 0183) Output Port table of Chapter 2.12 Interfacing to other manufacturer's equipment (NMEA) of the Autohelm Type 100/300 Autopilot Installation and Set Up.