You have a battery temperature sensor on the inverter? Connected to the inverter or the cerbo?
Where is the temp sensor connected?
Ohms law is not new.
The ve bus voltage is on the graph is deselected. Is there a reason for that?
I do see a current spike at rhe same time as a temperature spike and a voltage spike. Know why or what that means is the next step.
Does it happen with the inverter in the on state and the off state?
no reason i made it clicked on it screen shotted it.. i’ll do it again… and im out of posts but can edit.. 22 a day apparently.. cut off again. IDN looks ok to me the power is being pulled either side of chain neg end battery pos 1st batt interconnects were custom made by professional installer.. pos goes to fuse to lynx bus bar, neg to busbar different lengths there certainly but that would not cause spies, what you saaid would if pos and neg were on one battery and they were chained from there with a back battery but not here?
the battery bank currently is new out of box at set status. previously this has hppened batteries were fully charged 4 times drained. Battery is configured to the link you provided neg and pos each end of chain example 3.
It’s not the power cables either the thickness means the bms probably gives more resistance there could be a 20cm difference in length it’s would be so minute a resistance difference it’;s pointless. according to AI. but makes sense. it migbht pull stronger on neg but it isn’t going to cause spikes says ai
I’ll turn inv off tonight good idea.
accordinbg to ai
The issue is circulating currents in the bank instead of in and out to the system.
When a BMS trips and disconnects abruptly, the current through the bus inductance has nowhere to go — V = L·di/dt produces a spike that can be several times the nominal bus voltage.
You have a large loop area on your cables. If you can get positive and negative closer together. Ir get rid of the daisy chain.
Thans LX, I’ll loo at rerouting or maybe install to a bus bar way, I am pretyy sure Lukas and the install team measured resistances and balanced it but i’ll ch again. Remember a so called professional installers who’s done yachts buses house and does the grid for fiji did it. He waas not a novice..the second installer redid it all. The whole install becausse no 1 installed munted it so badly the victron agent got in a pro.
But problems iu thinb are left over from originl install are possibly he actually shorted something, he blew the whole bus 12v by assumin the solar previously installed was 24 not 12..it’s a long storry of stupid retailer hiring a guy who never did a MH/RV install. His faul;t his issues he’s abandoned when it went pear shaped with s toen gesture..aeppacific have lent me there engineer to fix the system. He has admin now and is looking at it. Thanks AEPPacific for coming aboard to ressolve this.. He got admin asked for 24b hours so just waiting on the graph results..
voltage on 279 and 276 are fine they don’t see the volt spike, but 279 does see the temp spike, ..it’s only 512 sees v spike and temp spike i set svs and sts off .
Thats why i asked what is measuring that for the ve bus? Is it the ASS000001000 that comes with the inverter and then connected to the inverter? I don’t see it in any of the pictures and it doesn’t look like it is connected to the battery bank?
Remove the device to eliminate issues there.if it is installed.
Although it looks like the spikes is also on the green line which is the battery as well?
in the picture i posted it says what it is it’s colour coded and relates to the readings displayed if you look where I had the timeline by the verticle line you can see at that moment only one reading was abnormal ve-bus battery temp on 276 all other had nornmal readings, then you get it on 512 and ve or you now it just all over the place.. how can i fix something thats giving me spies in all devices bar the mppt..at different moments.. like gremlins have eaten and it 12.01
1 step at a time 1 fix at a time I know..it’s just agonizing
the victron tech asked me about my alternateor charging and said he’s close and will be back in touch tomorrow.. I went and checked all fittings on the 12-12 they had the diesel heater lug against the fuse and positive lead after it, I swapped that around and realized, it’s the 24-12 thats for the alternator.. went sat down obviously i need a break.
Yeah. Eventually you can’t see the woods for the trees.
Lug stacking is always an issue. Labelling helps as well. And torque on the lugs. Especially in mobile.
it’s in the firmware Victron and SOK are working on a fix.. had someone contacted them earlier describing the issue others wouldn’t be in same boat, second person has same issue.
3.75 firmware issues of spikes have stopped. Thx to everyone victron aeppacific new zealand and SOK batteries, Especially Brendon of SOK batteries and ARIE victron engineer at AEOPPACIFIC you guys were absolutely awesome!
LX: i came to this thread researching a customer’s issue that sounded very very similar and imagine my surprise when i recognised the exact same SOK batteries. /s
My guess is that Victron’s update in v3.7.5 is actually just handling the bad data from SOK, when SOK should really be fixing the problem. There are thousands of brands of batteries talking CAN to Victron Cerbo and we don’t see this problem with any other vendor (that i know of), so it comes down to probabilities, which IMO point directly at SOK.
The system i’m troubleshooting also never gets to 100% SOC, even when voltage and current suggest that its tailed already, so the data is pointing to the SOK BMS being the cause there too.
Also a note to @ifixit ; you can’t swap a bms (or battery), observe the same behaviour, and conclude that therefore the bms is not the issue, that’s not how binary troubleshooting works. Consider the example where a simple house light won’t go, it could be the bulb, the cabling, the switch, the breaker, or the grid is down, but swapping the bulb with a different bulb and seeing the same result (ie no light) only means that either the problem is elsewhere, or both your bulbs are blown, or both your bulbs are working and the problem is elsewhere, and you are still no closer to knowing what state the bulbs are in.
Swapping the bulb and getting a different result does tell you something; that there is a difference between the bulbs, and the first bulb was the fault.
Also swapping things for brand new doesn’t really mean much; there is very little difference between the probability of a fault in something brand new and something fairly new. Swapping something for another that has been tested and verified recently has value, but it gets very complex with things like a BMS where its mostly a black box.
In your case, both the batteries work in the same (broken) way, sending bad data in some cases. I expect that all Victron’s engineers have done is put in some sanity guards that say “if the reported temperature is above 3 times the previous value, ignore it” or similar. And if the SOK batteries are using PACE BMS,
============================
UPDATE
============================
In the case I was assisting with; the BMS in at least one SOK battery (out of 3) has been proven (among other faults such as reporting invalid voltages) to be requesting a charging voltage that is too low to allow it to reach the voltage/current required to reset the SOC to 100%. In this particular case the owner has no problem with turning off DVCC and using the MPPT’s algorithm to provide a fixed charging, absorb, and float voltage. This seems to resolve the issue
I’m a PC engineer we swap KNOWN good and have previously be known to work together out as easy repair option. I was under the impression someone whoi contracted a written contract for a 2 day install had used common business sense and used nown compatable certified parts..not the 150 ah 24v sok batteries that certainly are not.
Issue is not resolved under 3.75 as you say it’s occurring but now not as often between silly fits. LOL. SOK and VIctron still working on it.
I actually asked..This gear is known to work together.. right.. yeah millions sold worlwide. just slap some crap together in china and we’ll BS our way through..i’ve been so blatantly lied to I just laughed. I asked that as an engineer i need to knopw 1 first and foremost does this gear work together and is known to be good before i start looking at the problem Period. Thanks wasted 5 months chasing a sompatability issue with firmware fix.. that is the worst thing to find after 5 months.. worst it could have been resolved day 1 as the manufacturers should have test rigged the setup.
we sold over 100,000 pc’s in NZ, we rolled out known com[patable hardware because i was a microsoft OEM manufacturer and i presonally did the hardware certification for Microsoft and ISO cert.. I mean i just made an assumption people who opperated at that business lever have iso cert and hardware compatability certification processes. Apparently you (taling to resellers and installers) in the solar industry just chuck stuff together and hope it all just works out.. awesome lads that’s so 1900’s. nice to see you keeping up tadition.
Issue is BMS comms confirmed by Engineer, 3.75 no fix, They are working on it. Last suggestion fromm Brendon involved cable and terminator position in the Cerbo but alas I didn’t want to tell him I did extensive cable swapping nterm swapping blue term port swapping basically I ran through the config, when you change something on the cabling it will settle for up to 24 hours then revert. Also new batts are self terms my old 150ah were not. They I thin are struggling it’s been over 3 days. It’s on BMS they really should have isolated the issue by nowe and already have released code. ..firmware update..could be hardware fault.. I’ve seen that With ALI motherboard chipset once, had to refab and bring out a new revision of the IC.
they have my old hardware testrigged it’s doing it still. The new cerbo and self terminating new revision of the 24v 150ah SO batteries are doing it. Which would require new firmware writes in the battery itself, so 2 models of same battery 2 revisions both same issue with Cerbo GX. interesting bloody nightmare for some engineer I do know that.. shouldn’t happen.
aka test rig and my bus are both exhibiting mirror faults. it went nuts after 24 hours of the firmware write here so no didn’t fix.
Wonders when they will just write a few lines of code that say if battery is model xxx..Rdeplace bms data with another reading channel 279 or 276 smartsolar or invertors data and walk away quietly..