[CA] [CA11] Swapping out (2) E95's for (2) Axiom 12's?

[Chuck - Raymarine - Moderator]

Grady330,

The CP470 and HD Radar are designed to support Ethernet communications and as such would not be interfaced to a backbone as shown within your diagram. As indicated within my initial response, unlike the Axiom Pro MFDs and e95 MFDs, the Axiom MFD feature only one Ethernet communications interface. Should you elect to proceed with Axiom MFDs rather than Axiom Pro MFDs, then it will be necessary to install a HS5 RayNet Network Switch. The Ethernet communications interface of each Axiom MFD and CP470 will be interfaced to the HS5 RayNet Network Switch via an appropriate length of RayNet (F) to RayNet (F) Cable. The Digital Radar Cable will also be connected to the HS5 RayNet Network Switch. Should you elect to install a pair of Axiom Pro MFDs and should the system not presently feature a HS5 RayNet Network Switch, then the RayNet (F) to RayNet (F) Cables and Digital Radar Cable may simply be unplugged from the e9x MFDs and will instead be interfaced to the Axiom Pro MFDs.

Finally, the diagram does not accurately represent how an EV400 Power Pilot would be interfaced to a backbone. The EV400 Power Pilot is essentially comprised of an EV-1 CCU, ACU400, a drive unit, and possibly an p70R/p70RS/p70/p70S autopilot control head. The system's data Master MFD, EV-1 CCU, ACU400, and p70R/p70RS/p70/p70S autopilot control head should each be interfaced as individual spurs to a powered and properly terminated SeaTalkng / NMEA 2000 backbone. Unlike the SeaTalkng / NMEA 2000 port of an e95 MFD, the NMEA 2000 port of an Axiom/Axiom Pro/Axiom XL MFD features a DeviceNet (M) socket rather than a SeaTalkng spur socket. Accordingly, any of the 3 solutions provided within the FAQ found here may be used to adapt Axiom/Axiom Pro/Axiom XL MFD's DeviceNet (M) socket to permit the MFD to be interfaced to a SeaTalkng spur socket within the aforementioned backbone.