Threaded Mode | Linear Mode

***Chuck - Raymarine - Moderator***

Welcome to the Raymarine Forum Swen,

For clarity, some issues with the diagram should be verified:

- Should you not have performed a of the Axiom MFD following its software update to LH3 v3.11.42, then it is recommended that this action be undertaken.

- the connection between a SeaTalk to SeaTalkng Converter and the autopilot components shown is a SeaTalk rather than a NMEA 0183 connection

- the rudder reference transducer and fluxgate compass are connected to the S2G, not to the SeaTalk bus as is shown within the diagram.

- as indicated within the FAQ found [url=http://www.raymarine.com/]here, one of the S2G's SeaTalk ports should be connected to the autopilot control head and the second of its SeaTalk ports will be connected to the SeaTalk to SeaTalkng Converter ... in the latter SeaTalk connection to the autopilot course computer, the SeaTalk Cable's red lead will not be connected to the autopilot course computer's red SeaTalk terminal

- within the diagram, there is no indication regarding where the NMEA 2000 Power insertion spur is located. This power insertion spur should be located at the approximate midpoint of the backbone's LEN load.

- Please note that fast heading data is required in support of many of LightHouse 3 software's heading dependent features. This will not be satisfied by interfacing a S1G/S2G/S3G to the system via SeaTalk alone. Additionally, the NMEA 0183 Port 1 output of these autopilot course computers would need to be interfaced to one of the NMEA 0183 input ports of a MFD within the system. Alternatively, the autopilot course computer's NMEA 0183 Port 1 output may be interfaced to a NMEA 0183 to NMEA 2000 data bridging device (ex. Actisense NGW-1, etc.), which in turn would be interfaced as a spur to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone. In this case, the simplest means of accomplishing this end would be to interface the S2G's NMEA 0183 OUT1 port to the e97 MFD's NMEA 0183 IN2 port and NMEA 0183 Port 2 setting of the e97 MFD should be configured to NMEA 4800.

- verify that the software within each Raymarine product (excluding the autopilot) has been updated with the latest available Raymarine product software update ... the AIS700 is out of date.

- verify that the software within each third party product has been updated with the latest available product software update.

- the e97 MFD's NMEA 0183 Input Port, as it will be interfaced to the NMEA 0183 OUT1 port of the S2G, will be configured as the system's Data Source for Heading data via the MFD's Data Sources feature. The 10Hz heading output of the autopilot will be required for proper operation of Radar application MARPA features as well as for maximum performance of other features requiring/utilizing heading data.

- the GPS sensing device having the best and unobstructed view of the skies overhead will be configured as the system's Data Source for GPS, Date & Time, and Datum data via the MFD's Data Sources feature.

If after having addressed the items listed above should the problem then persist, then it would be recommended a Power ON Factory Reset operation be performed to each of the system's MFDs to correct the problem as I have been unable to duplicate it within our office. Should the problem persist, then it would be recommended that all third party products be temporarily disconnected from the backbone and that the system then be tested. Should the problem not be duplicated when so tested, then the third party devices may be added one by one to the system until the device(s) is identified.