Integration with Victron

I have a Watchmon Core with the latest version (2.17.55) of software and BlockMon 8, the system is integrated (CANBus) with Victron Cerbo. Everything works correctly included dynamic Voltage Charge but the Cerbo does not receive all the data from Batrium. The following data does not appear to be being received:

The remaining battery time until its discharge or is its charge:

  1. Info/ChargeRequest
  2. Info/FullchargeRequest

The alarms I’m not sure if they are being received. Can you confirm that they are sent and are functional?

Alarms/CellImbalance

Alarms/HighTemperature

Alarms/HighVoltage

Alarms/LowChargeTemperature

Alarms/LowVoltage

etc…

I have doubts as to whether the implementation that Batrium has carried out with Victron is total or only a part.
Can you please clarify my doubts?

Where is Info/ChargeRequest and Info/FullchargeRequest displayed in the Victron system? I never saw it anywhere there.

1 Like

In the DBUS, in VenusOS, all the data appears there and you can see the data that Batrium sends via CANBUS to the Cerbo, specifically in:

com.victronenergy.battery.socketcan_canX

And as you can see in the image, the ChargeRequest and FullChargeRequest data are blank…

Hi Javier,

Our Victron implementation is complete and based on extensive talks with Victron engineers over the years. We send warnings when the battery enters a critical state and no sooner, as these will shut down the inverter and take out the power to your house.

We used to send warnings, but got endless emails from customers concerned about them, when they are intended to be just that, warnings.

We don’t have anything in our logic currently about requesting charge - we are more about allowing/disallowing charge, but good spot, we may think about including this functionality to force balancing. This does have the potential to cause confusion, we get a lot of emails about “why did my system do X” and this would make that question harder to answer.

Please let me know if you have any more questions, and thanks for endeavouring to know more about how your system works :slight_smile:

According to the alarm information, so far I have been lucky and have never had a critical condition and that is why I have never seen an alarm. What I don’t understand is why the system is not capable of sending information on the remaining battery life. Any BMS sends or publishes that information, which will be more or less reliable but helps to know an approximation of the remaining capacity of a battery. depending on its discharge level or on the other hand the time remaining until a full state of charge occurs depending on the current charge. I think it’s something obvious…

Hi Javier,

I think we have different interpretations of that Victron field?

To me, it seems like a value that the BMS can set to True to ask the charger to charge regardless of solar - i.e. “pull from the grid now, the battery is too low!”

Remaining time is something we calculate based on Ah remaining and A being drawn (see below), but if Victron don’t have somewhere we can put that value, we can’t send it.

Si, tienes toda la razón, me he liado yo con el traductor. Lo que yo quiero es conocer la autonomía restante de la batería, ya se que Batrium tiene esa información pero no se envía o no se puede enviar a Victron por lo que sea.

Quizás el parámetro en DBUS. es:

/TimeToGo

Yes, you are absolutely right, I have gotten involved with the translator. What I want is to know the remaining battery life, I know that Batrium has that information but it is not sent or cannot be sent to Victron for whatever reason. Maybe the parameter in DBUS. is: /TimeToGo