Alright update on the whole.. Too much battery capacity for the BMs's to handle problemI am assuming similarly.
It does make a difference, just moves the SOC like crazy between the percentages. I also require to keep the percentage above 4% because the inverter starts force charging the batteries from the Grid or completely disables Backup (aka house electricity).
I will attempt that and see if by chance that manages to fix my issue! So 2/3 of 2354ah is 1,570ah?
May I say, I've learned more math in the past 6 months then I've ever did in school lmao
A trick someone in another thread is doing (in their case adding another battery makes their inverter do weird crap). They have 12 batteries connected in the master/slave bms setup and connected to the inverter (#13 breaks the inverter) and they have 3-4 more batteries that are not part of the master slave but connected to the inverter DC power. Because of the way the bmses track current the extra unconnected batteries pretty much track the connected batteries. The only issue this could cause is if the unconnected battery significantly drifts away from the 2 connected batteries such that it does not fully charge and/or goes into protection. You would have to check the unconnected battery once in a while to make sure it is working right.Alright update on the whole..
Set all 3 BMS reported capacity at 1570ah or 2/3's of the actual capacity.
Previously the breaking point was when all 3 Bms's would reach 74% it would die. Now I had the communication overflow happen at 92%.
At overflow, the Inverter begins reporting 0% (while all 3 BMS's show correctly) which means it kills the power to the Backup (or my whole house to be exact).
So right now I'm thinking either reducing the reported capacity by half of it's whole capacity.. which would be.. 2354 / 2 = 1177.
But I can see that this is not ideal solution, as the reported capacity by the BMS's will reach 0% by the time the batteries are half discharged. So I'm a little bit lost on what to actually do :/
That indeed is an option and more or less will probably be my last resort due to few issues:A trick someone in another thread is doing (in their case adding another battery makes their inverter do weird crap). They have 12 batteries connected in the master/slave bms setup and connected to the inverter (#13 breaks the inverter) and they have 3-4 more batteries that are not part of the master slave but connected to the inverter DC power. Because of the way the bmses track current the extra unconnected batteries pretty much track the connected batteries. The only issue this could cause is if the unconnected battery significantly drifts away from the 2 connected batteries such that it does not fully charge and/or goes into protection. You would have to check the unconnected battery once in a while to make sure it is working right.
arduino
I tried similar using a uno and a megga but they were too slow. I now use teensy's.Question: Can anyone recommend some sort of device or arduino or something of that kind to take information from the BMS's and input that information into the Inverter? Like a middle man approach
Alright I'm curious, what did you mean by too slow and how and why do you use Tennsy? (I honest to dirt know barely anything so please be patient and explain it like to a child)I tried similar using a uno and a megga but they were too slow. I now use teensy's.
![]()
Teensy 4.1 Triple CAN Board with 240x240 LCD and Ethernet
This is a Teensy 4.1 board with triple CAN connections and ethernet magjack. Two CAN 2.0B and one CAN FD. It can be powered by an external +12v DC with reverse voltage protection. Included is also a 240x240 wide angle IPS TFT LCD display. Features Teensy 4.1 (installed) On board voltage...www.skpang.co.uk
SOC in JK BMS has never been and will never be counted correctly. The lower the SOC value, the bigger the difference. This is not changed by voltage calibration, amperage at high load, or other niggles.. Since I use YamBMS to control charging and send SOC 100% to my Deye inverter , all problems are over.
Compare SOC JKBMS 15.38 vs Victron SmartShunt
View attachment 285258
Too slow, as in it wasn't fast enough to read all the CAN messages- ie it would miss some.Alright I'm curious, what did you mean by too slow and how and why do you use Tennsy? (I honest to dirt know barely anything so please be patient and explain it like to a child)
SOC in JK BMS has never been and will never be counted correctly. The lower the SOC value, the bigger the difference. This is not changed by voltage calibration, amperage at high load, or other niggles.. Since I use YamBMS to control charging and send SOC 100% to my Deye inverter , all problems are over.
Compare SOC JKBMS 15.38 vs Victron SmartShunt
View attachment 285258
With no inverter communications, set short RCV timer in BMS and let inverter/charger determine actual absorb time.what would be best settings for early 100% ?
Yes, I confirmCzy używasz wszystkich JK BMS + victron + Can do deye z tylko jednym Atom S3?
How did you do that?I noticed this as well. With the 12000xp. The ik bms needs to reach the RCV before it starts the absorption timer. But the inverter uses it's own internal voltage measurement. And never gets the battery to the RCV. The only way I got the battery to work is to calibrate the bms voltage to read a bit higher. So the absorption timer starts.