Batrium Critical Fault - How to identify?

Agree with customer support and comments / documentation is 'echo the dialog' type (not very helpful). The whole situation is not good!

---------------- from above --------------------
Looking thru your log (1st post) I see these 3 lines....
ShuntSoc 70.0 100.5
Critical Events 3
SoC% 2.6 1.1 5.4 6.1 0.0 0.0 0.0 0.0

They keep claiming that my time out (and ultimately the shunt tripping) is caused by shunt recalibration
---------------------------------------------------


But back to the shunt. It looks like you focused on the 100%+ Soc but my other point is that it also seems to show 0.0% SoC 4 times.

I've experienced 0% SoC a couple of times because the shunt just goes a bit crazy during the cycle. Each time, the unit stopped reporting a bunch of info - went 0 like ShuntV, ShuntA, ShuntW etc. In my case, this did not auto-reset like the comment of 100%+ Soc. I had to manually reboot. I didn't notice the voltage (blue bar) readings as I was so alarmed I immediately went below to fix.

Having all the shunt values go 0 'could' cause a critical event / trip the shunt depending on your settings.
 
The website is a mess, support is a mess, documentation is a mess... Shame, as it is a half decent BMS.
 
I haven’t had any issues since, it’s been running well. At the time I was playing with things. I had been trying to get Victrons DC Feed-in working. (Where it will feed excess DC solar to the grid)

this involved a few settings being mucked with - I did have times where multiple cells were going above 4.1v (my limit) and lots of current going into the batteries.

I gave up on it, and with DC Feed-in disabled and settings back to normal - I haven’t had any issues.

The logs however should make it crystal clear what and when caused faults. Even with the logs, Batrium themselves couldn’t seem to give me a straight answer and wanted a phone consult.

I can understand the reluctance to provide endless free support - however the manual, documentation, UI and importantly the logs need to be readable and make sense.
 
I haven’t had any issues since, it’s been running well. At the time I was playing with things. I had been trying to get Victrons DC Feed-in working. (Where it will feed excess DC solar to the grid)

this involved a few settings being mucked with - I did have times where multiple cells were going above 4.1v (my limit) and lots of current going into the batteries.

I gave up on it, and with DC Feed-in disabled and settings back to normal - I haven’t had any issues.

The logs however should make it crystal clear what and when caused faults. Even with the logs, Batrium themselves couldn’t seem to give me a straight answer and wanted a phone consult.

I can understand the reluctance to provide endless free support - however the manual, documentation, UI and importantly the logs need to be readable and make sense.
I don't understand the reluctance to provide endless free support - you make a complex electronics product and sell it for a tidy sum, you should support it. We (my employer) make a complex, expensive product, we support it for free...
 
I sell very expensive computers - zero support after sales unless it's a product fault. Settings, configuration etc all on the client.
 
zero support after sales unless it's a product fault
Exactly "unless it is a product fault."
I am sure that there is a percentage of "product faults" that do occur even with the highest quality of parts. ;)
I'm thinking longmons................


Pc support is for suckers :p
Hey @slimf I guess I must be a sucker as I make darn good money supporting PC's.
Or maybe it's my clients that are the suckers.🤣

Wolf
 
Back
Top