[CA] [CA11] Axiom 12 and Axiom 9 Networking

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum vacantid,

Q1. I have an Axiom 12 (no sonar) and will be adding an Axiom 9 (basic no sonar) to my network. If I understand the user manuals and other forum information correctly the Axiom 9 on my flybridge should be a repeater display connected to the HS network via my 8 channel HS Switch and should not be connected to the Raynet / 2000 serial network. Both Axioms are running 3.2.97.
A1. In order for both Axiom / Axiom Pro MFDs to share all system data, each MFD would need to be networked to one another via an Ethernet network. Such networking may be accomplished via any of the following means:
- connecting each Axiom / Axiom Pro MFD to an Ethernet network switch (ex. HS5 RayNet Network Switch, SR6 Sirius Satellite Weather / Network Switch (retired), or SeaTalkhs Network Switch (retired)).
- The Axiom / Axiom Pro MFDs would be [url=https://en.wikipedia.org/wiki/Network_topology#Daisy_chain
]daisy chained[/url] to one another via appropriate length of RayNet (F) to RayNet (F) Cable.

In systems featuring more than one compatible MFD which have been interfaced to one another via an Ethernet network, only the Data Master MFD would need to be interfaced as a spur to the system's powered and properly terminated SeaTalkng / NMEA 2000 backbone to which the systems other peripherals having a SeaTalkng / NMEA 2000 communications interface have been connected.

Q2. Is this correct and if so will ALL data present on the Axiom 12 at the pilot house console be replicated on the Axiom 9 via HS?
A2. More correctly all data available to the Data Master MFD will be available to the non-Data Master MFDs. Each MFD may then be independently configured to display whichever supported features are desired.

Q3. Should I disable the local GPS capability of the Axiom 9 or can it be used locally?
A3. Within a networked system, only one source of each type of data (GPS, wind, speed, etc. ) will be supported at any time by the system. To this end, the Data Master MFD will support a Data Sources feature through which the operator will select which source of each type of data will be used by the system. Data Source selection is only necessary in conjunction with types of data for which more than one instance is present within the system.

Q4. Please let me know if I can expect this dual Axiom 12 / 9 system to function normally with HS and Raynet working side by side.
A4. Please note that Ethernet, SeaTalkhs, and RayNet are all the same networking protocol. The proprietary names SeaTalkhs and RayNet are simply Raymarine proprietary branding alternatives to Ethernet and reflect cabling connectors and sockets which are designed to protect the product's interfaces from exposure to the marine environment. You may also be confusing RayNet (Ethernet) with SeaTalkng / NMEA 2000 networking. As indicated above, only the system's Data Master MFD need be interfaced to the SeaTalkng / NMEA 2000 backbone which is presently networking the Axiom 9 MFD, Evolution autopilot components, i60 instruments, and AIS receiver/transceiver to one another.

Q5. I have a full new suite of EVO Autopilot, 2 P70R displays / autopilot control, Ray Sirius XM receiver (HS interface), Quantum Radar (HS), CP 370 depth sounder (HS) and WindSpeed / Direction I-60 based, ACU and rudder indicator all updated. I have a 2nd party AIS transponder that is connected via NMEA 2000 adapter cable to Raynet and works very well.
A5. The MFDs, Quantum radome, and CP370 will each be interface to the system's Ethernet Network Switch. The Data Master MFD, Evolution autopilot components, i60 Instruments, and third party AIS transponder will each be interfaced as an individual spur to the powered and properly terminated SeaTalkng / NMEA 2000 backbone.


Q6. I attempted to use a Raynet to SeaTalk network adapter to connect one last Seatalk display (depth) to the Raynet network but my Axiom 12 gave me serious errors for data master and would not function with the adapter connected to the Raynet bus.
A6. Again you may be confusing Ethernet (RayNet) with SeaTalkng communications. It is not possible to adapt SeaTalk, SeaTalkng, NMEA 2000, or NMEA 0183 to Ethernet. Bridging of data from SeaTalk, SeaTalkng, NMEA 2000, or NMEA 0183 to Ethernet may only be accomplished via MFD.

Q7. Help with properly networking my new Axiom 9 with my existing Axiom 12, any data display limitations, reason for the failure of my Seatalk to Raynet adapter (5 connectors) would be appreciated. I have also previously reported CP 370 depth display problems with my Axiom 12 - no depth displayed if fish finder app is not running.
A7. Please refer to the information provided above addressing how the equipment should be interfaced. Please additionally note that should the system currently feature a SeaTalkhs Network Switch (retired), that Raymarine offers adapter cable to permit a SeaTalkhs Cable to be mated devices featuring a RayNet (M) socket (ex. Axiom MFDs and CP370). Raymarine additionally offers adapter cables to permit a Quantum Data Cables (feature a RayNet (F) plug) to be adapted to mate to a SeaTalkhs Network Switch (retired). Please note that there were some early software issues within LightHouse 3 software which may be responsible for communications with a CP370 sounder module. Accordingly, please ensure that your Axiom MFD(s) and CP370 have each been updated with the latest available Raymarine product software updates.