Batrium: Shunt timeouts

Sean

Member
Joined
Oct 8, 2016
Messages
946
Anyone seeing random behaviour fromthe 500A 650v Batrium shunt ?

Small Leaf test pack to prove some control logic, max current through the shunt not greater than 25A via an Eltek, or 10A via PV.

The pack has been sat connected for a few weeks, probably low three figureAh throughput - randomly,the shunt stops reporting, telemetry shows timeout, long periods at idle.

Rebooting the WM does nothing, red led on but no green traffic led.

The only way to get it talking again seems to be setting shunt hardware to none, turn off any reporting, then add it again - which is far from ideal.

What's theshunt talking to the WM over ? - the only system change has been the addition of the Eltek over canbus, which also seems prone to losingit's ability to talk to the WM. The shunt randomness could be a separate issue to the comms issue with the Eltek.

Again, functional documentation seems sparse.

Picture, just for interest.


image_qrzpbi.jpg
 

rtgunner

Member
Joined
Jan 14, 2018
Messages
101
I had an issue last night. I was top balancing my packs when the shunt readout went out as the last pack went into bypass.

Then the cell level displays all disappeared. Cellmons were in "timeout," no comms and unit was in read only mode. Batrium FAQ said cause could be firmware at wrong level. I updated firmware (was already at the proper level though) and same issue.

As soon as a few of the packs came out of bypass the cell level display came back and so did the shunt monitor.

Weird. I think the longmon wire harnesses are an issue. I have had several with open connections to the pins in the connectors. This has cause similar
canbus coms issues for me in the past.

Then I thought that the ability to alter settings when all the cellmons are in bypass might be a safety feature. not sure. Waiting to hear back from Batrium.
 

Sean

Member
Joined
Oct 8, 2016
Messages
946
Interesting, I also had an unexplained series of read only mode events a few days ago, I didn't look to hard but is how to enable/disable read only documented ?

I put that issue down to switching between USB and WiFi for comms - but didn't find any documentation to detail the expected behaviour.

It appears I have a more recent version than current installed.

 

Sean

Member
Joined
Oct 8, 2016
Messages
946
mike said:
What I was going to ask is... You're using the latest available v31 public release, correct? Did you upgrade to v31 recently?

It appears so, but that's another issue (I've started a new thread for that)
 

Sean

Member
Joined
Oct 8, 2016
Messages
946
Still no official notification that this is an on going issue, Jaron knows about it, so it seems like I'm not the only one seeing random shunt lockups.

Mine stopped reporting towards the end of a 12 hour discharge set overnight, obviously it still passed current, just no reporting, which could have been an issue as I'd set the low shunt voltage to trip the load off via a shunt trip, fortunately other LVDs worked (external to the WM) before any pack damage was no.

The shunt was very reluctant to start reporting, restarts, remove shunt, sync etc = still no data.

Setting the cell type from custom, to Performance Li did bring it back.

Who else is having random shunt lockups and how are you resolving the issue ?
 

Sean

Member
Joined
Oct 8, 2016
Messages
946
mike said:
I am having random shunt lockups but I am using a Batrium-supplied alpha build and wasn't sure if I should comment. I have to restart my Watchmon anywhere from 1-3 times per day. I've been in contact with Batrium and a fix is supposed to be rolled out very soon, though no date estimates were given.

I'd like some official input from Batrium, at least some dialouge or listing of known issues, and the anticipated solution timeframe.

I've two sets, 14 Leafmons, 3 expansion boards, a pair of shunt etc etc, so not just loose change. And having now spent a good few hours evaluating what initially appeared to be marketed as a functional product, its clearly still going through the development cycle, certainly in respect of the remote comms as per a few of my threads.

To now find that reporting from such an integral device as the shunt is flawed isn't encouraging.
 

LithiumSolar

Administrator
Staff member
Joined
Oct 8, 2016
Messages
2,388
Official Input - https://secondlifestorage.com/t-Batrium-software-firmware-update?pid=38218#pid38218

Batrium said:
Currently we are working on 2.0.6 (RC6 for short) with new features and fixes. However it is not quite ready, we are working on a important issue with the shunt lockup reported from 1.0.32RC3, that is taking time to resolve. The Shunt lockups occurs after +30 hours. On our test bench we have several Watchmon supervisors all at different operating durations to ensure we solve this. Once resolved I can push out RC6 for the very early adopters.
 

Sean

Member
Joined
Oct 8, 2016
Messages
946
Yep, seen that, seeing as I started the thread - but that's the first and only acknowledgement I've seen on that issue.

And no input on the issue raised mentioned at the start of that thread.

Given that this forum seems to be the only place where this BMS is being openly discussed I'd have thought we'd be seeing a lot of official content posted, this place is full of potential customers.

The graph and flashing lights do look nice in the dark, I'll grant them that.
 

Batrium

Member
Joined
Feb 17, 2017
Messages
74
Just to update the conversation.

Lessthan a monthago we were made aware of a Shunt Lockup issue from a couple of a beta tester on the 1.0.32.RC3 (beta) release. Hence we startedinvestigatingthe problemand developingafix. Being a intermittent problemthat takes a couple of daysto occur it tooktime toidentify, rectifyand rerun theelapsed testing. We have several(6) systems on our test bench (Watchmon 1 / 4/ 5) to make sure that we can test different scenarios. On Thursday wefinally exceeded the 60 hours with nofaults.

We are now in theprocess of preparing a release RC6 andpreparing ourregiment oftesting scenarioswhilst updated thedocumentation before updatingeveryone.When problems happen we workto resolve them but must also avoid releasingnew unidentified issues. As far as we wereaware this only impacting the beta release. Let us know is there are other problems (ideally via email) with the symptoms, snapshot report file and other items we have listed on our support page.

We only recently discovered a number of people hadadopted our alpha release RC5without our direct request. We recommendpeople onlyadopt the production (live)release that either the toolkit software has notified you is availableor fromour installation instructions. Our small group of beta tester arevery helpful and wecontinue to appreciate their help in prevently a release from being broadly adopted.

This next releaseismorethan a minor patchas there are several newfeatures.At the same time we will be staging another patch to resolve the wifiissuewhen people have poor coverage that mayimpact the bms system. Within RC6 we have added a number of tools to help us identify this wifi scenario.
 

Sean

Member
Joined
Oct 8, 2016
Messages
946
Thank you Jaron.

New features are great, but having the existing ones work as advertised would be advantageous.
 
Top