V3.60 battery charge/discharge enabled details missing

I am not really sure since when the following issue has popped up, but I do remember it working on v3.5.
I have 9 batteries, all using the JK Inverter BMS, connected via CAN with Victron Type B Cable.
All is working well, however I noticed that the cerbo does not display the number of batteries that have charge or discharge disabled anymore:

I have three different systems build and one of them is still on 3.60~74 and the issue is already present in that version.

Same problem here. (JK V15.41, 3.60_83)
Parameters DCL & CCL seems to work fine.

Hello.
Same issue for me.

  • Venus OS 3.60~78 and 3.60~84 on Cerbo GX MK1
  • JK BMS Inverter 200A/2A/16S , fw. 15.38

As far as I remember, the number of “blocking charge” / “blocking discharge” modules was showed correctly in the early versions of 3.60~xx (when the bug for the Cerbo MK2 CANbus was not fixed yet).

Please note : in case the battery is blocking discharge, the Cerbo reports a “low battery voltage” error.

Rgds.

Same here on v3.60~68, v3.60~80 and v3.60~84.

Thanks all three - noted

2 Likes

Also upgraded to v3.60~85 and have the same problem. The 2nd battery is not seen.

Also noticed that the parameters are not correct. 95A for charging/discharging is for 1 battery, it should be 190A for two batteries! It is probably linked to the fact only one battery is seen, but still reporting it for completeness.

I think your problem has a different cause, all my batteries are reporting correctly and also DCL and CCL are correct.
For me it is just missing the “change/discharge blocked by number of modules’” that is not reporting anything.

Ok, thanks @vaursechs for responding/sharing this view. However, before I upgraded it was working great, the DCL/CCL as well as the battery modules where correctly displayed. The only change was upgrading the Gerbo GX and Multi RS Solar. Suggesties on where to search? Open for suggestion.

Upgraded to version v3.60~86 and this problem is not yet fixed. Same situation.

@mpvader would this be on the fix list for the next beta release?

I have three systems running and all are reporting the correct number of modules (batteries) and DCL/CCL.

I suspect something went wrong with the communication between your JK BMS-es.
Try to switch the master BMS and see if it report to victron cerbo GX, if not, there is something wrong with one of the BMS-es (or communication boards)

The Cerbo GX either shows a connection with the bms or no connection at all, it doesn’t detect multiple batteries, that is all handled by the JK BMS.

1 Like

Good suggestion to do the master/slave switch. It didn’t turn out to be the solution, but, I discovered when I removed the network cable from the RS485 port which was connected to a laptop for monitoring, suddenly the two batteries are seen from the Gerbo menu! And the DCL/CCL are not set to 190 (instead of 95). So the issue was the laptop monitoring cable in the RS485 port. Problem solved. Thanks.

Yes, being worked on!

Fixed per v3.60~87.

At least it is according to our code & test systems :innocent:: would be great if you can confirm.

Thanks!

Confirmed!

1 Like

Fix Confirmed!

1 Like

Confirmed

1 Like

May I ask in this discussion item where the “Number of modules blocking charge / discharge” is being used for? What is it indicating?

If you turn off discharge or charge in the bms (JK in my case) you can see that here. So if you turn off discharge of 2 batteries it says here that 2 modules block discharge. I think that if the BMS for safety reasons blocks charge or discharge this is also visible here.

1 Like

If you have more than one battery-pack and one is having a problem, it will shut itself off for the direction the battery has a problem with.
e.g when battery-pack 1 has a cell that is hitting the max voltage per cell and battery-pack nr 2 has no problem. To prevent overcharging that one cell in battery-pack 1 your BMS of that pack will interrupt the powersupply to it. This leaves you with one pack less. The max chargecurrent will also drop with it.

1 Like

Excellent, thanks for the clarification @idobuiter and @rvdh. Appreciated.