Zeus + Cerbo causing NMEA2000 network to crash


  • Ever since installing the Zeus I have been having issues with NMEA2000 data becoming corrupted and making the whole system crash.  I have many battery monitors, charger info, 5 tanks etc transmittet from Cerbo on the NMEA2000 network. What happens is:

    -Tank data comes and goes.

    -Battery info comes and goes.

    -Cerbo goes in to constant reboot every 10 minutes or so.

    -Autopilot error.

    -Slave MDF looses contact with Master MDF.

     

    When I isolate the Zeus to VE-CAN 2 and use VE-CAN 1 for sending NMEA200 there is no issues.

    This is the data i see from the Zeus, only 4 data points.

    But when I enable NMEA2000 i the Cerbo I get 20 data points all about Zeus data.

     

    I am not blaming the Zeus, this could very well be an Cerbo/Venus OS issue. 

    Any sugestions?  

     

     

     



  • I think I found the problem myself.

    In my system, there is 7 batteri monitors:

    4 Batteries, then there are also 2 pcs MPPT and 1 PCS Multiplus, but the Cerbo sends these data as an battery monitor also.

     

    It turns out that 6 out of these 7 all had the same PGN with same Data instance (0)

    So I adressed them all with different Data Instance and system has been running perfect now also with the Zeus added to the NMEA2000 network. 

    Strange that the Cerbo does not automaticly adress them with different Data Instances.

    It seems to do so when it comes to tank levels. All 5 tanks had different data instances. 

     

    Also, there are TWO "generators" one is the Multiplus and the other is the Zeus.

    These two should not have the same Data Instance. 

     

    Changing the Data Instance is not really an easy thing to do, you cant just change it in the Cerbo menu.

    You need an computer with an USB-NMEA reader like the Actisense NG-1 and correct software. 


Please login to reply this topic!