OK Due to the fact, I have re-done the extension cable a couple of times, and even I tried to move it while the system was running to eliminate cold joints, I was pretty sceptic to try to move the two Leaf mons on the left hand side, closer to each other to get rid of the extended cable. But I've done it. So far it is running seamlessly (third day started) even I have removed the access point from the room.I have a 3 1/2 year old Watchmon 4 w/112 longmons - e.g. a pretty long (~60ft) longmon network. And a 1.5yr old Watchmon Core w/14 longmons in a camper trailer.
In the begining, I used some random wire and twisted it myself to reach the 1st longmon and last longmon... and I had occasional freezing. Had to manually reboot. I eventually replaced it with CAT-6 twisted pair wire stripped from CAT-6 internet wire AND skipped their 24"? thing to help you connect and went directly to Batrium terminal block and all my issues went away.
The symptom of monitor freezing / restarting reminds me of this. I think I read 7 x leafmons... but maybe use CAT-6 twisted pair wire directly from 1st leafmon and last leafmon -> Batrium? Just dragging the bottom of the barrel here....
Here's a pic to try to illustrate what I'm talking about. Did the same thing (but shorter) in the trailer 14s. No problems with network/monitoring since doing this.
View attachment 114956
The reason they say don't run USB is that USB voltage is on the low side of voltage or power needed to sustain the core. It has worked for me for extended periods, but it's just what they say - especially if you have external services hooked in the core.
-----------------
Have gotten some valuable tech support in early years (free) but the last round (couple of months ago) was annoying. It was a simple question on their toolkit software update dialog unrelated to my hardware... but they refused to answer unless I sent logs/complete-specs of my system. After 3 back/forth they lectured me on being a bad customer for refusing my details BUT.... they actually answered the question. Just weird.
I can't help it though, the product has really worked for my situation personally.
You know... it reminds me that early this year I had a mon network freeze and it seemed like wiggling the plug-in cable on 1 particular longmon seemed to help ??!??. That longmon also seem to be a bit more extreme thru the charge/discharge voltage readings during a daily cycle.OK Due to the fact, I have re-done the extension cable a couple of times, and even I tried to move it while the system was running to eliminate cold joints, I was pretty sceptic to try to move the two Leaf mons on the left hand side, closer to each other to get rid of the extended cable. But I've done it. So far it is running seamlessly (third day started) even I have removed the access point from the room.
To be clear, the extended cable is 100%, joins are fine, I used identical cable as the original...
I'll keep you guys posted, and thanks OffgidInTheCity for remind me, "whatever I've done, it could be bad, even if it looks good". (I can't remember who said that, me perhaps)
Batrium has not responded after I refuted their claims I was at fault. I told them it never worked and forwarded emails and data pulled from the core where I worked with Maxine. Maxine was always great to work with but the new person not so much.I was too quick to be happy... "Lock ups" are still present. Still no solution yet...
It's must be annoying, but is this phenomena isn't stops your entire system I presume. Also to be very honest, I never noticed the precision of auto levelling is adjustable. My cells always within 0.02V, unless I discharge it down to 3.5V ish. In that range it goes off by 0.12-0.15V. I guess because of the top balancing. I did not notice any spikes as it wasn't my concern. It still shows the entire "firmware business" is probably out of there league... I'm back to "other battery" option to avoid inconvenience. Leaf batteries are so robust I don't think it would hurt...Just another gripe. My issue seems to be worsening.
View attachment 115675
These voltage spikes always happen on #14. I've quadruple checked the terminal block. I'm using BMS sensing leads and premium ring terminals that were extracted from the same PHEV as the NMC cells.
Normally, my autolevel is set to .08V to hit only the top .01V, and that minimizes this - hitting it with a balance current seems to drop it.
This time, on the way down, it was below my SoC threshold, so I've dropped that as well.
This is also getting worse. 0.2V jump vs. 0.1V prior.
They claim it's related to their balancing algorithm, and they plan to eventually patch it, but I'm dubious.
Even showed up in the 5 minute snapshot:
View attachment 115676
Apparently they went pretty "cold" in communication when I mentioned I would expect more result, and had a few short sentence regarding how I can return the package I bought... Obviously based on your experience, I will not force the replacement...Batrium has not responded after I refuted their claims I was at fault. I told them it never worked and forwarded emails and data pulled from the core where I worked with Maxine. Maxine was always great to work with but the new person not so much.
It's must be annoying, but is this phenomena isn't stops your entire system I presume. Also to be very honest, I never noticed the precision of auto levelling is adjustable. My cells always within 0.02V, unless I discharge it down to 3.5V ish. In that range it goes off by 0.12-0.15V. I guess because of the top balancing. I did not notice any spikes as it wasn't my concern. It still shows the entire "firmware business" is probably out of there league... I'm back to "other battery" option to avoid inconvenience. Leaf batteries are so robust I don't think it would hurt...
Thanks for posting your issues. You’d think they would have a employee monitor these forums to jump on this shit lickity split. My company monitors FB and Google and other forums in a different industry to get ahead of issues before they get out of control.Another FW upgrade, lockups are still present...