V3.60 N2K out issue?

Matthijs,

I have ungraded by Cerbo GX to v3.60~84 and it is not being detected anymore on my B&G MFD device, I can see my SmartShunt and MPPT devices and read data from them, but I cannot now read any of the data from my Quattro, like shore power V and A, Generator, Inverter status etc.

I started Signal K and it can see the values from my NMEA2000 system as normal, depths, GPS speed, wind etc.

Looks like the Cerbo is not publishing the data onto the NMEA bus correctly.

This was working on the release V3.60~80 which I had loaded previously.

Hi @dpritt thanks for the report!

So to be 100% clear: this is concerning the N2K-out feature, and then only the data from rhe Quattro, right?

You still have data from other devices available on your N2K network?

And this is not about the Marine HTML5 app, ie the Victron logo on your B&G MFD?

It is the N2K data from the Quattro via the Cerbo Gx I cannot see anymore in my B&G, the marine HTML 5 screen does not work as it requires an ethernet connection, so I created a dashboard that shows some of the Victron data, I can see the SOC, battery voltage and current from my Smartshunt, as well as data from the solar blue, but the Quattro data such as status, and the inputs are missing. I have rescanned the devices in the Zeus 3 but the Cerbo or Quattro are not showing, the other Victron devices do.

All devices are on the latest software level, and this was working with the release I installed in early May, I skipped the last one, or two, as I am sailing and have limited internet access.

I don’t use Signal K but started it to see if the Quattro’s data was available, which it was, I can see the data on the Cerbo’s touch screen anyway.

My VRM site ID is 4200058.

David
Alma Sofia

Matthias,

Sorry a further update, the water and diesel tanks are not showing either.

I have attached a photo of the instrument screen I created to display the values from the Victron kit.

I don’t have shore power connected, but I do have the generator running, nothing shows.

The second screen is part of the device list on the Zeus 3, it shows the two Victron devices detected, the Cerbo was device 0000501.

David

(attachments)


Hi again, thanks. We’ll try and reproduce it.

If we can’t, is it then ok if we login to see more details?

System is Alma … I suppose?

Thanks, Matthijs

I am happy for you to login, but I am sailing around the Croatian Islands, so I may not have access to the internet all the time.

Happy to help in any way I can.

Yes it is Alma … The home system is down at the moment as we are away.

David

Hi David,

We can’t reproduce it here, data from Multis/Quattros is transmitted properly on our test systems.

And we briefly looked into it remotely on your system, where after some restarting the data came out properly.

For any further diagnosis, this is probably best done when not under sail, and you’ll then have to disable all modifications, including signalk.

And actually that is something you’ll have to try anyway yourself: disable all modifications, make sure the rootfs is reported as being “clean” in the Settings → General → Modifications checks menu.

Best regards, Matthijs

Thank you for looking at this.

I will do a rebuild of the Cerbo once I am in a suitable location, or at the weekend when we will be back at our base near Pula.

I don’t use SignalK but do have a few NodeRed flows and a dashboard to show voltage values from the two starter batteries, I cannot find a way of displaying these via the Cerbo.

I will let you know how I get on.

David

When V3.60 is released you can create a virtual battery in Node-RED, which the Cerbo sees the same as any other battery monitor. I am using the beta version helping out with testing and have 2 virtual batteries set up for easy display on the battery page, “Cell Variance” is the min/ max cell voltage difference on the lithium house bank and the starter battery is also a virtual battery. The voltage source is the aux voltage measurement from a SmartShunt in DC Load service which is not reported as a battery voltage.

Thank you for the update.

I already use the additional sensor of my Smartshunt for one starter battery, but I have additional monitors using a Esp32 device with an ADC to monitor the other starter battery, the generator battery and bow thruster batteries, currently this sends MQTT messages which i decode in Node Red and show on a dashboard.

These are not part of the main Victron setup which manages my domestic batteries, but I would like to be able to show each battery state on a separate screen on my Cerbo screen, VRM etc, similarly to the tanks and my Ruuvi devices, ideally by using the MQTT messages.

Not sure this is possible without buying more SmartShunts, my ESP32 and ADC device cost about £20 and is connected to my boat’s ethernet network, no contest on price performance ratio.

David

As you already have them in Node-RED then I was just pointing out a way to get them into the Cerbo and VRM as mainstream batteries so no need to use the Node-RED dashboard.

Matthias,

I reinstalled v3.55 from a backup I had via a USB stick, then downloaded the latest beta.
This appears to have worked, I now have the Cerbo device showing again in the device list of the Zeus and instrument dashboard shows the state of the fuel and water tank etc using the Victrkn data.
Many thanks for you help.

Now to see if I can get the extra 3 battery states I monitor from Node Red into the Cerbo as suggested by pwfarnell, it would be nice to have them showing on my Touch Display, instead of having to use my tablet or mobile to check them.

Regards all

David

Alma Sofia

1 Like

Create a virtual node of type battery then add a battery control node linked to the voltage of the virtual battery which receives the source of the voltage.

Many thanks, I will try that later when we are anchored again.

David

BUT you will either need to load V3.60 beta version or wait until official release.

good! thank you for the feedback.

At one point all the N2K data via the Cerbo was missing, this included tanks and Ruuvi devices, if I did a device search on the Zeus the Cerbo was missing.

Once I rebuilt the Cerbo I did a device search in on the Zeus and the Cerbo appeared again as did the Quattro. See pictures of the device list when all is working.

If I am understanding the system correctly the Cerbo GX acts as a gateway between the N2K network and the Victron networks, so if this is not detected after a restart of the Zeus, and all the rest of the B&G kit, I loose access to the Victron data.

I cannot get the web page up, it is working if I check using a web browser, but this appears to be an issue with the Zeus not your system, it keeps dropping the ethernet IP address from my router, I think it wants to be the DHCP server and if not goes into a sulk. Other users have had similar conflicts from comments on forums.

Most of the time the web page is not even presented, when it is the page times out with a server not found message.

All the non-Victron devices show via N2K.

David

(attachments)


OK, I have now been able to do some more testing.

I had everything running as per my previous email and all Victron devices were showing in the Zeus device list as expected.

I then powered off my navigation equipment, and powered it back on, the Victron devices had gone, and a scan on the Zeus found nothing.

I restarted the Cerbo Gx, and a few minutes after it had come back up the Zeus reported them again. I did not have to rescanned on the Zeus, they automatically reappeared.

Ran this test a couple of times, consistent results.

So it seems that the Zeus cannot see the Victron devices until the Cerbo sends out suitable ‘I am here’ messages.

I don’t have the kit to trap the N2K messages on board to see what gets sent to update the Zeus.

Hope this helps.

David

Thanks! We’ll check.

And for completeness: can you double check that this happens both with v3.55 and latest v3.60-beta?

Matthijs,

OK next set of tests.

Reverted back to V3.55.

On restart no data on the Zeus, but after restarting the Cerbo the data appeared as normal.

I then shut down the Zeus, waited a few minutes and restarted it several times, in each case the data was present.

I shut down the Zeus and left it for about 45 minutes, powered it on, data present.

So it looks like the system was a lot more stable under V3.55

I then installed Beta V3.60~85.

On reboot of the Cerbo after install the data appeared OK.

I then shut down the Zeus and restarted it, no data.

Restarted the Zeus several times, including a delay of over 30 minutes, still no data.

Something has changed between the releases.

David