Batrium: software & firmware update

Status
Not open for further replies.
I have also been running it for a while without anything major. Alot more stable than last release for sure.
 
I'm using the new Beta version now. Can't connect WiFi. Still fiddling with it. I'm probably missing something
 
Well more fool me, I've just done the update.

I've had the shunt lockup issue intermittently since original installation, but the test system has been fine for a week.

But it stopped reporting today, and I've found a few spare hours, so having updated the toolkit and firmware the shunt still is in timeout, and I keep getting told I'm not authorised to b in setp mode, so it's looking like another factory reset - which is the only way I've found previously of waking the shunt up.
 
Sean said:
Well more fool me, I've just done the update.

I've had the shunt lockup issue intermittently since original installation, but the test system has been fine for a week.

But it stopped reporting today, and I've found a few spare hours, so having updated the toolkit and firmware the shunt still is in timeout, and I keep getting told I'm not authorised to b in setp mode, so it's looking like another factory reset - which is the only way I've found previously of waking the shunt up.

It sounds like your lockup issue is different. Mine away always resolved by clicking "Reboot System" on the hardware page.
 
mike said:
Sean said:
Well more fool me, I've just done the update.

I've had the shunt lockup issue intermittently since original installation, but the test system has been fine for a week.

But it stopped reporting today, and I've found a few spare hours, so having updated the toolkit and firmware the shunt still is in timeout, and I keep getting told I'm not authorised to b in setp mode, so it's looking like another factory reset - which is the only way I've found previously of waking the shunt up.

It sounds like your lockup issue is different. Mine away always resolved by clicking "Reboot System" on the hardware page.

Great ....

It's not allowing me into system setup now.

I can't even run the wizard.
 
mike said:
Does it look like the Watchmon is stuck in a reboot loop?

No, its awake and it's seeing all the mons, but not the shunt, which is still in timeout.

And it's not allowing any changes, as if the auth code is wrong.

"Not authorised to be in setup mode"


Well that feels like an hour wasted.

Back to .31 in an attempt to roll everything back to where it was, so the shunt still is in timeout, but I'm now in some odd no man's land where the auth code isn't working.

So I'm now looking for an explanation as to what the Authorisation options do, and if there's any differences between connecting using USB or WiFi to make changes.

Brownie points to anyone who can link to where it's officially documented.


image_mshktq.jpg
 
Sean: My suggestion is that you get in contact with Batrium and get a session where Jaron directly look at your system so he can figure out whats going on. Instead of working around and so that you can get it solved once and for all!
 
daromer said:
Sean: My suggestion is that you get in contact with Batrium and get a session where Jaron directly look at your system so he can figure out whats going on. Instead of working around and so that you can get it solved once and for all!

I might,I've got two complete systems, neither work fully as advertised, butI'm getting very reluctant to spend any more time on it.

The REC systems have been faultless.
 
If its not running then contact them. Have you reached out to get help with it ie the problems or just added threads here on the forum? As said by many other of us our systems run without issues. Mine have been running like a champ for 1.5 year now. I got 3 different systems up and running without issues.

So i recommend to take contact and let them take a look at the software.
 
daromer said:
I have also been running it for a while without anything major. Alot more stable than last release for sure.

daromer said:
Mine have been running like a champ for 1.5 year now. I got 3 different systems up and running without issues.

You say "It's been running like a champ for 1.5 years now" - but just a few hours prior you indicatedstability issues, and how this new RC is running "without anything major" ....... your commentsarecontradictory and not what I would expect to be said about areliable system.

Just to clarify, I didn't purchase the Batrium BMS to be part of a development process, given it's apparent popularity I expected it to work as advertised, and bereliable enough to leave in remote locations attached to very expensive battery banks.

As an aside, a few days ago I was pleased to see a new, seemingly more logicallook had been introduced to the support page, along with some form of "book time with Jaron" feature - where has that gone ?
 
My main system have been running like a champ for 1.5 years that's correct.
Also note I'm in the early beta group so I do see issues.

No I did not have anything major with the new release and that's how I express myself when it works just as it should The release installed fine. The system worked fine after the upgrade and as of now no issues. And most of the things i have encountered have been UI issues and such. So perhaps have I been lucky or? Neither less Im happy with it from my end.

I basically have 3 different systems. 2 are for the main system and its up and running. The test system i could emulate the Wifi problem atleast but not the Shunt in my case. I also have another 2 systems but they are beta test systems

I once again suggest that you contact them? Have you contacted them for getting help to sort it out? Have you had Jaron to look at your install via Teamviewer so you can get it sorted yet?

I think you saw the new support page that was put live to early before it was done?
 
No I've not formally approached Jaron directly for support, but he has seen and responded to a number of the public threads and comments I have made here and elsewhere, I have been awaiting the release of their solution.

I'm not raising any issues that are unknown to Batrium or unique to me, I'm trying to implementa fairly simple setup, including a CANbus connected supportedcharger.

Take specifically the shunt locking up, this RC was supposed to have resolved it - for me it hasn't, the only thing it has done is tomess up the auth code, so I'm now not even able to roll back to previous production releases, nor am I able to factory reset the unit such that I can start again. Reliable operation of the shunt is vital in even the most basic BMSs, yet there are still ongoing issues with it.

I might make a formal direct approach to Batrium, but I'm more inclined to send the units back - again, I didn't pay 1400 to join a development project.
 
Sean said:
No I've not formally approached Jaron directly for support, but he has seen and responded to a number of the public threads and comments I have made here and elsewhere, I have been awaiting the release of their solution.

This forum is not the official means for support. Jaron browses here routinely, but often doesn't reply BECAUSE this is not the official support channel. You should not wait for him to do so to avoid an official support request

Sean said:
I'm not raising any issues that are unknown to Batrium or unique to me, I'm trying to implementa fairly simple setup, including a CANbus connected supportedcharger. Take specifically the shunt locking up, this RC was supposed to have resolved it

Yes, you do have unique issues. The issue you're reporting sounds different than the shunt lockup issue that others have had, the issue I had, and the issue that was fixed in this release.

Sean said:
I might make a formal direct approach to Batrium, but I'm more inclined to send the units back - again, I didn't pay 1400 to join a development project.

Please open a support request by emailing info@batrium.com. If you don't hear back in a day or two, please let me know and I can follow up with him.
 
As said by Mike, Jaron generaly browse here when we ask him to take a look at a thread where we think he might be able to answer.

For all outstanding issues the proper way is to contact their support to get him to directly take a look. Your system seem to have an issue, that us who participate in the dev/test group havent been able to replicate as of now.

Buyback is possible if im not mistaken but they do require that you talk to him directly.

Edit: Beware of that its important that all people using Batrium should be happy. Yes its not for everyone and Im on your side Sean that it gets resolved to the best for sure!
 
Mike, with respect, I don't have unique issues, hence my comment specifically about the shunt time out.

This RC has not resolved it, but it has created another issue.

My CANbus functionality concerns are a separate issue, I'm simply trying to get a system that is basically, and reliably functional - I can manage with the CANbus functionality as we've built a standalone controller for the Elteks.

And to reiterate, I don't just have the one Batrium system.

Public support negates the need to repeatedly give the same to individuals via the "system" - I may well use the new "system" when it comes out from wherever it has been hidden.

I will watch with interest to see how others fair, I've allready spent to much time trying to make productive use of this BMS.

Thanks for your assistance :)


daromer said:
Buyback is possible if im not mistaken but they do require that you talk to him directly.

Just for clarity, I'm not overly bothered in a refund, I'm happy if they just took the units back to analyse - I've 50 RECCs to fit over the next few months, perhaps there will be a further production release by then.

Thanks Mike/Daniel.
 
Saw an update come through in the tool over the weekend. Anyone know if this is resolved now?
 
JohnAllen said:
Saw an update come through in the tool over the weekend. Anyone know if this is resolved now?

I applied the update expecting it would resolve one of the issues it was intended to resolve - the shunt timeout - but it didn't.

It did however do something whereby the pin code no longer works, so I'm now unable to make any setting changes, I can't even factory reset it.

Rolling back to the production release of the toolkit and associated Fw has not resolved the new pin code issue, but Mike & Daniel should be pleased to note I've raised it via Batrium support.
 
Status
Not open for further replies.
Back
Top