When I try to connect to the Cerbo GX using the Victron app on the Raymarine Axiom MFD I get a connection error "no hardware found" and the application does not start.
The Cerbo GX is connected to the NMEA2000 network using a Victron VE.Can to NMEA2000 cable and the Raymarine Axiom MFD is connected to the same NMEA2000 network. The NMEA2000 network works fine and is properly terminated. Since the Axiom is connected to an Quantum 2 rader with cable the Axiom must connect to the Cerbo GX through the NMEA2000 network.
The NMEA network diagnostic screen on the Axion shows not only the Cerbo GX. But also all the devices connected to the Cerbo GX with VE.CAN, VE.Bus or VE.Direct. Attached is the NMEA2000 network diagnostics from the Axiom listing all the NMEA2000 devices as well as the Victron devices that the Axiom can find on the NMEA2000 network.
- The Raymarine Axiom is running the latest lighthouse operating system (v3.13.103 Edgartown)
- The NMEA2000 network is powered separately and the fuse in the VE.Can to NMEA2000 cable is removed
- The Raymarine Axiom can see the Cerbo GX on the NMEA2000 network (and all devices connected to the Cerbo GX, including tanks)
- The Cerbo GX and all connected Victron devices are all running the latest firmware
- All data from the Cerbo GX are visible on the NMEA2000 netowork and can be displayed in other ways such as webguages with yachtdevices wifi gateway
- On the Cerbo GX: one VE.Can port has a VE.Can terminator and the other VE.Can port is connected to the NMEA2000 network using the VE.Can to NMEA2000 cable
- The NMEA2000 network is a Raymarine SeaTalkNG network
- The VE.Can to NMEA2000 cable is connected to a SeaTalkNG<->NMEA2000 cable that is connected to a "white" device port on a Raymarine 5-way
Cerbo VE.Can port settings:
- CAN-bus profile: VE.Can & Lynx Ion BMS 250 kbit/s,
- NMEA2000-out: Enabled
NMEA2000 network diagnostic from Raymarine Axiom
NMEA2000 network diagram