[CA] E-80 MFD Time issues

[Chuck - Raymarine - Moderator]

Charles,

Per our discussion, please send your SeaTalk to SeaTalkng Converter to me to have its software updated. Please additionally determine which the model of autopilot course computer is presently installed onbooard the vessel.

Should you determine that the model of autopilot course computer is a S1, S1G, S2, S2G, S3, or S3G, then it would be recommended that the MFD be disconnected from the SeaTalk bus (i.e. disconnect the SeaTalk/Alarm Cable from the MFD's SeaTalk/Alarm port) and then connect the MFD's SeaTalk2/NMEA 2000 port to the remaining spur socket of the SeaTalk to SeaTalkng Converter using the adapter cable specified within the previously referenced FAQ. While not considered a best practice, backpowering the SeaTalk to SeaTalkng Converter from the SeaTalk bus will work for the very small SeaTalkng backbone created for you system.

Should you determine that the model of autopilot course computer is a SPX5, SPX10, or SPX 30, then it would likewise be recommended that the MFD be disconnected from the SeaTalk bus (i.e. disconnect the SeaTalk/Alarm Cable from the MFD's SeaTalk/Alarm port) and then connect the MFD's SeaTalk2/NMEA 2000 port to the remaining spur socket of the SeaTalk to SeaTalkng Converter using the adapter cable specified within the previously referenced FAQ.

The information in the following would only be recommended for a vessel which featured a SPX autopilot and where further equipment having a SeaTalkng / NMEA 2000 communications interface was expected to be added. While it would be permissible to stop at this point, it would be considered a best practice, to add three additionally spur sockets to the backbone to permit the ST70 Autopilot Control Head, SPX autopilot course computer, and a SeaTalkng Power Cable (connected to a dedicated switched 12VDC power circuit to be) to each be interfaced as spurs to the SeaTalkng backbone. Finally, the software within the ST70 Autopilot Control Head and SPX autopilot course computer will be updated via the E-Series Classic MFD. Should the SPX autopilot course computer feature a SeaTalkng power switch, it should be configured to the OFF position. The SeaTalk bus will be powered from the SeaTalkng backbone via the SeaTalk to SeaTalkng Converter. Should the SPX autopilot feature a ST6xxx, ST7xxx, or ST8xxx autopilot control head instead of a ST70 Autopilot Control Head, then it would be recommended that it be disconnected from the SeaTalk bus to which the ST60 instrument are connected and and instead that it be connected directly to the SeaTalk port of the SPX autopilot course computer.

Should the MFD have been updated with the final E-Series Classic MFD software update (v5.69) and the Raystar 130 GPS Sensor have been interfaced to the MFD per the FAQ referenced above and should the problem persist, then the source of the problem would be fault isolated by testing the performance again after:
- unplugging the SeaTalk/Alarm Cable and NMEA 0183 from the MFD
- unplugging all devices from the powered and properly terminated SeaTalkng backbone except for the MFD and the GPS sensor

Should the problem persist when so configured, then it would be recommended that the GPS sensor be sent to Raymarine’s Product Repair Center to be bench checked / serviced. Should the problem abate, then it would be recommended that devices be plugged back into the system one by on until the problem reoccurs, thereby identifying the problematic component and/or incorrect method of interfacing the products. Should you need further assistance, then please attach a system diagram of the vessel's marine electronics system identifying each component and how it has been interfaced to the system. Alternatively, the assistance of a Certified Raymarine Installer may be obtained to troubleshoot and correct this issue.