[CA] [CA11] Autopilot Control eS127 / S3G / ST8001

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum hynespa,

General Comments:

MFDs running LightHouse II software will support use of LightHouse II's autopilot feature if the following each of the criteria below have been met:
- the MFD is running LightHouse II v19.03 software ... your system has met this criteria
- the autopilot must be a Raymarine design
- the autopilot must be compatible with the SeaTalk to SeaTalkng Converter or must feature a SeaTalkng/NMEA 2000 ... S1/S1G/S2/S2G/S3/S3G autopilot course computers are compatible with the SeaTalk to SeaTalkng Converter
- autopilot must be interfaced to the system via the SeaTalk to SeaTalkng Converter or as a spur to the SeaTalkng / NMEA 2000 backbone. The Autopilot Controls feature is not supported by Raymarine autopilots which have been interface via a direct NMEA 0183 connection to MFD, via an E85001 PC/SeaTalkng/NMEA 2000 Interface Module, or via a NMEA 0183 to SeaTalkng / NMEA 2000 data bridging device (ex. Actisense NGW-1-ISO-STng, etc.)
- the LightHouse II software's Autopilot Control feature must be enabled within the software's settings
- all SeaTalk and SeaTalkng communications circuitry within the devices and networking components must be operational and properly interfaced.


Based upon the description of the installation below, photos and descriptions of splices (always suspect), the following is recommended:

- Only one cable should be connected to the ST8001 ... a SeaTalk cable connecting it to either one of the autopilot course computer's two SeaTalk ports. The SeaTalk to SeaTalkng Converter Cable supplied with the ST-STng Converter should be connected to a the SeaTalk (yellow) socket of the SeaTalk to SeaTalk Converter adn to a D244 SeaTalk Junction Block. The D244 SeaTalk Junction Block should then be connected to the remaining SeaTalk port of the autopilot course computer with an appropriate length of SeaTalk Cable. When connecting this cable to the autopilot's SeaTalk port, the cable's red lead will not be connected to the SeaTalk port's red terminal. Instead, this red lead should be insulated to prevent shorting

- The circuit supplying power to the SeaTalkng Power Cable should be protected with a 5A fuse. This will function as the only means of powering the SeaTalkng backbone and must not be modified in any way which would cause it to provide power to a device which was not intended to be powered via the device's SeaTalkng / NMEA 2000 communications interface.

- The SeaTalkng / NMEA 2000 backbone (includes the SeaTalk to SeaTalkng Converter) should be constructed entirely of SeaTalkng networking components. This backbone must be properly terminated (i.e. two and only two termination plugs in the backbone and they should be installed within open backbone socket located at the terminus of both ends of the backbone. The backbone should feature sufficient spur sockets such that each device having a SeaTalkng / NMEA 2000 communications interface may be installed as an individual spur to the backbone.

- any third party devices having a NMEA 2000 communications interface (ex. Fusion stereo head unit, Fusion remote, etc.) should be interfaced to the backbone via an A06075 39.4in (1.0m) DeviceNet Female to SeaTalkng Spur Cable.

- The MFD's NMEA 0183 output port should not be interfaced to the autopilot course computer's NMEA 0183 input port. All command and control of the autopilot will be accomplished via SeaTalkng / NMEA 2000 communications via the SeaTalk to SeaTalkng Converter.

- Should the autopilot support stabilized 10Hz heading output, as does the S3G, then its NMEA 0183 output port should be interfaced to one of the MFD's NMEA 0183 input ports, and that input port should be configured for 4800 BAUD NMEA 0183 communications.

QUESTIONS:
Q1) Can the S3G Autopilot Computer / ST8001 Autopilot Controller be controlled from the eS127?
A1) Yes. See my opening comments regarding how to properly interface the equipment.

Q2) If yes, is there anything wrong with how this is wired that would let the MFD send messages to the autopilot via 0183 but not via SeaTalk?
A2) See my opening comments regarding how to properly interface the equipment ... specifically the last two items.

Q3) If no, do I need to upgrade both the computer and controller to something that the MFD can control?
A3) Negative. When properly interfaced and satisfying the criteria specified above, then the red X over the autopilot icon should be extinguished.