Today I saw an update of v3.52 with reference to Batrium BMS:
• Autoconfiguration for Batrium BMS “0xB038” profile, BatriumD. This includes enforcing DVCC on, and SVS on, and STS off.
When I check my Vitron system, it mentions 0xB037.
What are the differences and advantages of 0xB038?
John
Hi John,
This will be in our next software release. We have been collaborating with Victron the past few weeks, and held off on releasing ours until 3.52 was out of beta.
Could you confirm for us that 3.52 was released on the normal Victron update channel?
Yes. I have it installed last evening.
I just installed that VenusOS 3.52 update and have some issues with it:
Before (3.51 VenusOS) I saw in the device details “Batrium (Victron profile)” or similar and Product ID 0xB038.
After the upgrade I see there “Batrium-BMS batters” and Product ID 0xB037. In DVCC nothing is forced on. What can be the cause of that? I am running 2.17.55.
Btw. with VenusOS 3.52 the serial number is not displayed. Screenshot is without serial number.
James, I just saw this pop up in my email and checked my system and my Cerbo GX did a auto firmware update and installed 3.52 and my battery balance. was. awful. I checked and the bms can buss bit rate settings were wrong since the update. I changed the settings to the correct values and then ran out of sun for. the day. I am watching this morning as I get close to 95 percent to see if that fixed the issue.
I am so glad batrium wiki. sent out this notice.
I noticed the firmware mismatch as well:
0xB037. vs 0xB038
Looking forward to the next version of watchmon with this support 
Hi Guys,
I’m disappointed to hear that the Victron update may not be totally backward compatible.
I’ve pushed forward the corresponding update on our side. Keep in mind this is a preview release for this problem:
WatchMonToolkitInstaller_2.17.56g.msi
https://link.batrium.com/s56giv
As usual, make sure you update your firmware:
Let me know if this fixes your issues, and please post screenshots of your Victron device pages to confirm the Batrium-BMS (Victron Profile) appears as it should.
The update from Victron should not affect your bitrate settings. BMS-Can defaults to 500kbps which we adopt. 250k is usually on a different port on newer devices, but doubles up on older ones. Not sure what is going on there but we can dig in after you install the update.
Unfortunately, I have to report, that it does not work for me.
With Batrium 2.17.55 I saw Product ID 0xB038 and “Batrium-BMS (Victron profile)” in VenusOS 3.51.
I will go back to VenusOS 3.51 and keep Batrium 2.17.56. Is there anything I can investigate, why the “Victron profile” gets lost? I already tried to redect the battery in VenusOS and changing settings in WatchMonToolkit.
HI Kleini,
Thanks for the screenshots and info. Here’s what I can say for sure from what you’ve said
Could you confirm whether you need to change the bitrate? Or does it remain working?
I’m just piecing together the story to go to Victron with, thank you for your testing and your patience, we won’t be leaving this in a broken state.
Hi James,
I did not touch the bitrate at all, neither on Batrium side nor on Victron side. I use a Cerbo GX device and the BMS-Can port is configured to 500kbit/s.
Could you please elaborate a little bit on when Batrium will send Product ID 0xB037 or 38 and when it will send Product “Batrium-BMS battery” or “Batrium-BMS (Victron profile)”? My experience is, currently, both values are tied together. Are they not?
Victron release notes contains this statement:
Thank you very much for further improving the Batrium software and all your support.
Kind regards,
Kleini
I installed the new version today - 2.17.56
DVCC is now forced on in the Victron UI
Here are some screenshots:
First up showing how the Batrium is detected - including the new Product ID 0xB038
and this screen shot showing how the DVCC settings look now (forced on):
James, apart from forcing DVCC on, what else does this update to? Can you possibly update the KB here: Victron GX | Batrium Knowledge / Wiki - it would be helpful for this to be kept uptodate.
Today I updated Batrium to 2.17.56g by using the link.
I have had updated Victron allready to V3.52.
I have rebooted Batrium (disconnect power supply for 10sec)
I have rebooted the Victron GX.
Result:
Still showing product ID 0xB037
and no forced DVCC settings:
I do have communication between Batrum and Victron as detailed battery details are updated on the Batrium-BMS screen:
I do not see any advantage or disadvantage of this update at this moment .
I had the same behavior as John and Kleini, but got it fixed today by updating the Cerbo to latest 3.60~4 release. Now the settings were forced and ID is on 0xB038! Happy with this and already noticing good results today (sunny day with 100% SOC).
My update with the latest Victron (beta) did not make any improvements.
John
Ok, that is strange! Something else must be triggering it. I will update another system tomorrow and see if it behaves the same, hoping to find the detail that makes the difference.
Hi Guys,
OK, I’ve been in touch with Victron and we are both confident that in Venus OS 3.52 and Batrium 2.17.56:
If you aren’t getting 0xB038, you may have a setting misconfigured. PM me your serial number and I can check (make sure your device is provisioned)
