[CA] [CA11] Axiom 12 not recognizing other MFD as data master

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum shclawson,

In order to share high resources requiring very high bandwidth data (cartography radar, fishfinder, IP video, etc.) the MFDs must be interfaced via Ethernet communications. If operating with the latest available LightHouse 3 software (v3.5.40 at the time of this response), then the reported symptom may be indicative of a problem with the system's Ethernet networking components and/or the Etherne communications circuitry of one or both of the MFDs. It is recommended that you verify that each of the MFD's has been updated with the LightHouse 3 v3.5.40 or later software update and if not, that the software within the MFD's be updated accordingly. Within a system of Axiom/Axiom Pro/Axiom XL MFDs and eS-Series MFDs, it would be recommended that one of the Axiom/Axiom Pro/Axiom XL MFDs be interfaced to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone and that this Axiom/Axiom Pro/Axiom XL MFD be designated as the system's Data Master MFD due to its significantly great processing power and memory.

Should you have addressed the items specified above and should the problem then persist, then it would be recommended that a Factory Reset be performed on each MFD, that the MFD's then be reconfigured (again with the Axiom 12 MFD designated at the system's Data Master MFD), and that the Data Sources feature be executed on the Data Master MFD to manually specify which GPS, Datum, Data Time, and any other data source for which two or more data sources are available for the respective type of data be configured. This action need only ever be performed on the system's Data Master MFD, which will be switched ON whenever the MFDs will be used. Please additionally note that one should not attempt to interact with the system until all MFD's within the system have completed startup initialization.

Should the problem then continue to persist, then it would be recommended that the system be switched OFF, that the eS75 MFD be temporarily unplugged from the backbone, that the system be switched ON again, and that it be verified that the eS75 is able to receive data from the system. If not, then troubleshooting / testing of the system's Ethernet network should ensue.