[CA] [CA11] Device net to Seatalk backbone cable

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum Greyharbor,

For the benefit of others who may be viewing this thread, for the e125 MFD to have been interfaced to the ST6001, an [url=SeaTalk1 & SeaTalkng converter Kit]E22158 SeaTalk to SeaTalkng Converter Kit[/url] would have to have been installed. Please click here to view a FAQ addressing this subject. The SeaTalkng / NMEA 2000 socket of the a/c/e/eS/gS-Series MFDs features a SeaTalkng socket, while the SeaTalkng / NMEA 2000 socket of the Axiom/Axiom Pro/Axiom XL MFDs features a DeviceNet (M) socket. As such, if interfacing an Axiom/Axiom Pro/Axiom XL MFDs to the spur socket of SeaTalk to SeaTalkng Converter or SeaTalkng / NMEA 2000 backbone which has been constructed from SeaTalkng networking components, then one of the SeaTalkng to DeviceNet (F) Adapters specified within the FAQ found here may be used.

The Autopilot Controls feature of MFDs running LightHouse 3 software (ex. Axiom/Axiom Pro/Axiom XL MFDs) is only supported in conjunction with Evolution autopilots. This limitation will not prevent use of the autopilot's Track mode feature to track to a waypoint or to follow a route. It simply requires that the autopilot's control head be used to command the autopilot into track mode after navigation (Go To or Follow Route) has been commanded via the MFD's user interface.