Venus OS 3.70 – Generator runtime frozen when /Engine/OperatingHours is static (Fischer Panda CAN)

Beta testing Venus OS beta testing
1

Hello,

After upgrading from Venus OS 3.54 to 3.70 on a Cerbo GX, I am observing a change in generator runtime behaviour.

System

  • Cerbo GX

  • Venus OS 3.70

  • Fischer Panda i8000 connected via CAN

  • Digital genset (NMEA2000 / CAN)

Behaviour in 3.54

Generator runtime increased correctly while the generator was running.

root@Cerbo-GX:~# dbus -y com.victronenergy.genset.socketcan_can0_vi0_uc303662 /Engine/OperatingHours GetValue

value = 2288880

Behaviour in 3.70

Generator runtime is frozen.

DBus investigation shows:

dbus -y com.victronenergy.genset.socketcan_can0_vi0_uc303662 /Engine/OperatingHours GetValue
value = 32400

dbus -y com.victronenergy.genset.socketcan_can0_vi0_uc303662 /Engine/Speed GetValue
value = 2997.0

  • Engine speed updates correctly while running (~3000 rpm)

  • /Engine/OperatingHours remains static at 32400 seconds

  • Runtime in the UI does not increase

There is no internal accumulation visible in:

com.victronenergy.system

Observation

It appears that Venus OS 3.70 now relies exclusively on /Engine/OperatingHours for digital gensets and no longer accumulates runtime internally.

However, in this specific Fischer Panda implementation, /Engine/OperatingHours is static and does not increment in real time.

As a result, generator runtime becomes frozen.

Question

  • Is this intended behaviour?

  • Was internal runtime accumulation removed for digital gensets?

  • Should there be a fallback mechanism if /Engine/OperatingHours is static?

This behaviour change did not occur in 3.54. I tried rolling back and it works back as expected.

Thank you.

2

Thanks @Stefano, confirmed, will be solved.

1 Like
3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.