Hi David,
Ok clear. We’ll look into that. Strange that we couldn’t reproduce it earlier.
What type of Zeus and which software version is it running?
Thank you for all your help!, Matthijs
Hi David,
Ok clear. We’ll look into that. Strange that we couldn’t reproduce it earlier.
What type of Zeus and which software version is it running?
Thank you for all your help!, Matthijs
Hi David,
We have a Simrad NSS12 evo3S, which is (I believe) very similar to the Zeus3. I installed VenusOS v3.64 and after powering up the Simrad, it prompted me to update to the latest version (25.2/71.1.22), which I did. After setting up NMEA2000-out I restarted the Simrad a few times, but could not reproduce the issue you are describing.
Please confirm if this is still an issue.
I actually found a B&G Zeus3 and updated it to the latest version, which is 25.2/71.1.22 (same as the evo3S). I restarted a few times, but still can’t reproduce. All expected devices just appear under Settings → Network → Device list.
Martin,
I am not onboard at the moment, but we are will be going out to Croatia later next week for several weeks of sailing.
I have found that the order of start-up can impact if I can see the Cerbo from the B&G.
If I restart the Cerbo after I have started the Zeus it often works.
From the Cerbo I can normally see other devices on the 2K network OK, They show up in Signal-K, (which I don’t use as it kills the Cerbo) even when the Zeus cannot display the data.
I normally want to keep the Cerbo on-line all the time, while the Zeus is only switched on when I am travelling.
I have updated the Zeus to the latest Beta so I will carry out a full set of tests when I am on board and let you known.
Regards
David
I m now onboard and I have done some testing.
I have a Cerbo GX V2 running Beta V3.65~3.
It is connected to the NMEA bus using the authorised connector. also connected are my Quattro, MPPT and SmartShunt.
The NMEA bus is only powered on when necessary, this powers up the Zeus 3 as well as the rest of the navigation equipment, like the Tritons, depth sounders, while the Cerbo is always powered on.
After updating the the latest Beta and restarting the Cerbo I switched on the navigation equipment and checked the device list on the Zeus, see Photo below, you can see there is no Victron kit showing.
my instrument panel is bare
I tried a scan on the Zeus, but could not find anything new.
I then restarted the Cerbo GX, waited a couple of minutes after the Touch 50 screen had come up before checking the device list on the Zeus again, this now shows the Cerbo GX, and the attached sensors like the tanks levels, Virtual batteries, Ruuvi devices, as well as the Quattro.
I did not need to re-scan for new devices, they appeared automatically on the Zeus.
And my instruments panel shows some data, not sure why my fresh water tank is not showing, it is on the Cerbo.
This is the normal behaviour I have had since I installed the Cerbo to act as the brains of my system and pull the data together.
It is completely repeatable, as a restart of the Cerbo will fix the display every time.
To try to understand what may be happening I have fired up Signal-K, the power to the main navigation instruments is on, but the Zeus is not showing the data.
However Signal-K is showing the current GNNS fix from the Zeus, and this appears to be coming via n2k-on-ve.can-socket, so the connection to the NMEA bus is OK, the Zeus is sending traffic and the Cerbo is handling the data as expected.
Turning off the instrument power and all the N2K traffic disappears, as expected.
Powering the instruments back on and after a few minutes some data, like the GNSS appears again in Signal-K, showing that the Cerbo is capturing data transmitted by the Zeus.
I can also see the data for the sensors I am trying to display on the Zeus, and these are updating in Signal-K OK, but without restarting the Cerbo the Zeus is not detecting them as sources.
This is not a deal breaker, but it is annoying.
Let me know if there is anything else you would like me to test.
Davd
Thank you for the detailed description. We will try to reproduce the issue again, matching your setup as much as possible, including Signal-K.