S2/SHS Problem

[Chuck - Raymarine - Moderator]

danderer,

Q1: Is the S2 in fact the power source in my existing network?
A2: Within the present system, it appears that the autopilot course computer is indeed the source of power for the SeaTalk bus. SeaTalk instruments, autopilot components, GPS sensors, and chartplotters featuring a 1st generation SeaTalk communications interface which do not additionally feature a SeaTalkng communications interface (ex. ST40/60 Instrument Displays, Wireless AP Controller, Raystar 125 GPS Sensor, etc.) may be interfaced to one another, in any order, using standard SeaTalk Cables. SeaTalk Cables can be joined using D244 SeaTalk Junction Blocks, splices, marine grade terminal strips, or R55006 SeaTalk Auxiliary Junction Boxes. SeaTalk Cable is available in 15", 1m, 3m, 5m, and 9m lengths. This method of interfacing is referred to as a SeaTalk bus.

A SeaTalk to SeaTalkng Converter will be added as a backbone component to the SeaTalkng backbone. The SeaTalk to SeaTalkng Converter will be used to bridge data from the SeaTalk bus to SeaTalkng as well as to supply power to the SeaTalk bus. The Data Master E-Series Classic MFD will be disconnected from the SeaTalk bus and will instead be interfaced to as a spur to the SeaTalkng backbone. The SeaTalk bus will in turn be connected to the yellow SeaTalk port of the SeaTalk to SeaTalkng Converter. The SeaTalk to SeaTalkng Converter may be interfaced to the SeaTalkng backbone 5-Way Connector or T-Piece via an appropriate length of SeaTalkng Backbone Cable. The SeaTalk bus will need to be branched or extended and connected to the yellow (SeaTalk) port of a SeaTalk to SeaTalkng Converter which has been upgraded with v2.01 or later SeaTalk to SeaTalkng Converter software.

SeaTalkng devices (ex. Data Master E-Series Classic MFD, SPX/Evolution autopilots, ST70/ST70+ MFIDs, ST70/p70/p70R Autopilot Control Heads, i50/i60/i70 Instrument Displays, etc.) will in turn each be interfaced to the white SeaTalkng spur sockets within the SeaTalkng T-Pieces, 5-Way Connectors, or SeaTalkng Converter networking components of the SeaTalkng backbone using appropriate lengths of SeaTalkng Spur Cable. Additional SeaTalk spur ports may be created within the backbone by connecting additional SeaTalkng 5-Way Connectors and/or SeaTalkng T-Pieces to the SeaTalkng backbone / SeaTalk to SeaTalkng Converter(s) using appropriate lengths of SeaTalkng Backbone Cable. Up to three devices having a SeaTalkng communications interface may be daisy chained to one another using SeaTalkng Spur Cable to create a single spur having a maximum total length of no more than 5m. Daisy chaining SeaTalkng devices rather than connecting each SeaTalkng device individually to the backbone has the advantage of reducing the amount of cable which may otherwise need be chased throughout the boat.

The SeaTalk bus will be to be disconnected from its present power source ... in your system's case, this was the S2 autopilot course computer's SeaTalk ports. As a best practice, the SeaTalk bus will instead be powered via the SeaTalk to SeaTalkng Converter. The SeaTalkng power cable supplied with the SeaTalk to SeaTalkng Converter Kit will be connected to a switched 5A 12VDC power circuit and will be interfaced to the other white SeaTalkng spur ports of a SeaTalk to SeaTalkng Converter at the approximate midpoint of the LEN load of the SeaTalkng/NMEA 2000 backbone which is being created.

Finally, the blue SeaTalkng Termination Plugs will need to be installed within in the remaining two blue SeaTalkng backbone ports of the SeaTalkng backbone.

Q2: Once the S2 is removed, can/should the E80 Classic power the network if the red wire from it was connected?
A2: Negative. See the response to Q1.

Q3: Is an alternate/better solution to just to use a spare ST1 cable to provide the power (red & grey wires) from a 12V source?
A3: Negative. See the response to Q1 addressing how the devices having a SeaTalk communications interface and no SeaTalkng communications interface (i.e. your system's GPS sensor and wireless autopilot base station) should be interfaced to the system via a SeaTalk to SeaTalkng Converter.