6 EG4 rack batteries SOC issue

[adobopr]

Before updated the EG4 communications hub, my version was 1.5
After the firmware update, it shows as 1.10
This seems weird that the versions would go down?

I see in Zapper's video, he got the same results
He went from 1.6 to 1.10
So, was my previous version actually 1.05

Just curious about these firmware version numbers?

10 > 5 so 1.10 > 1.5

 

[Zapper77]

1.10 > 1.5

Maybe in China. But not in USA or Europe.

 

[NC_hydro]

Maybe in China. But not in USA or Europe.

No that's pretty common with software USA and Europe. Software version numbers are not voltages, or traditional decimal numerical values. Think of the second number almost like build number so it's major version 1 and you went from build 5 to build 10.

 

[Zapper77]

No that's pretty common with software USA and Europe. Software version numbers are not voltages, or traditional decimal numerical values. Think of the second number almost like build number so it's major version 1 and you went from build 5 to build 10.

I'd accept that if it was displayed as 1..6 or 1..5.

Omitting the zero. 1.0.5 or 1.0.6. And the upgrade 1.1.0

 

[n2aws]

I'd accept that if it was displayed as 1..6 or 1..5.

Omitting the zero. 1.0.5 or 1.0.6. And the upgrade 1.1.0

Most software and firmware companies have adopted "semantic versioning" which is what you are describing with the 1.0.5, 1.0.6, (major.minor.patch_or_build) etc. But at the end of the day, in this firmware naming convention In order from lowest version to highest, it's 1.5, 1.6, 1.10

 

[adobopr]

I'd accept that if it was displayed as 1..6 or 1..5.

Omitting the zero. 1.0.5 or 1.0.6. And the upgrade 1.1.0

Most software and firmware companies have adopted "semantic versioning" which is what you are describing with the 1.0.5, 1.0.6, (major.minor.patch_or_build) etc. But at the end of the day, in this firmware naming convention In order from lowest version to highest, it's 1.5, 1.6, 1.10

Yes exactly. The way software is usually built you increase each number individually.

I have plenty of software at work on like version 2.437.0 and you definitely don't need to preallocate zeroes to get to more digits.

 

[ksmithaz1]

Major Version . Minor Version . Release . Sub-Release . Vendor Change . . . As a general rule, a Major version change indicates the entire API may have changed. A minor version change indicates additional features, and/or clarification of the API. A release change is a bugfix. API = Application Programming Interface, the way the code talks to other programs/devices. The numbers are distinct/positional. IP addresses represent a 32 bit unsigned binary number x.x.x.x Each number represents 8 bits with a value between 0-255, 10.8.1.1 < 10.108.1.1 numerically, lexically 1.1.... < 1.8... It can however be confusing. Microsloth sorts ip addresses lexically on it's DNS servers. Effing annoying. 10.1.x.x , 10.10.x.x ,10.100.x.x ,10.2.x.x, sh*t. With most things IT numbers separated by '.' indicate positional order not lexical, so 1.100 > 1.25 unless you are referring to an actual real number. YMMV.

 

[EL34xyz]

Ok, I still have a problem.
Rack battery #2 refuses to charge up to where the other 5 are
It's setting in the 40% SOC now and the other 5 are 90% + SOC
I need to get Signature Solar to have a look at my system.

 

[Zapper77]

Ok, I still have a problem.
Rack battery #2 refuses to charge up to where the other 5 are
It's setting in the 40% SOC now and the other 5 are 90% + SOC
I need to get Signature Solar to have a look at my system.

Check wire torque, check for faulty crimps.

What bulk voltage are you charging the batteries at?

Please post cell data of the batteries when the other batteries are full...but the one is reporting 40%

 

[EL34xyz]

Most software and firmware companies have adopted "semantic versioning" which is what you are describing with the 1.0.5, 1.0.6, (major.minor.patch_or_build) etc. But at the end of the day, in this firmware naming convention In order from lowest version to highest, it's 1.5, 1.6, 1.10

This make more sense to me
1.0.5 or 1.0.6 to 1.1.0

 

[EL34xyz]

Major Version . Minor Version . Release . Sub-Release . Vendor Change . . . As a general rule, a Major version change indicates the entire API may have changed. A minor version change indicates additional features, and/or clarification of the API. A release change is a bugfix. API = Application Programming Interface, the way the code talks to other programs/devices. The numbers are distinct/positional. IP addresses represent a 32 bit unsigned binary number x.x.x.x Each number represents 8 bits with a value between 0-255, 10.8.1.1 < 10.108.1.1 numerically, lexically 1.1.... < 1.8... It can however be confusing. Microsloth sorts ip addresses lexically on it's DNS servers. Effing annoying. 10.1.x.x , 10.10.x.x ,10.100.x.x ,10.2.x.x, sh*t. With most things IT numbers separated by '.' indicate positional order not lexical, so 1.100 > 1.25 unless you are referring to an actual real number. YMMV.

In post #1, I posted the screen shot of BMS test program showing all 6 batteries
Battery #2 is circled in red

I have it set at 57.5 currently
I think it was a 56.5 before?

 

[Zapper77]

This make more sense to me
1.0.5 or 1.0.6 to 1.1.0

Note what other have posted is accurate as well.

Seems that its not uncommon for developers to us 1.10 as a newer version when compared to 1.5

 

[Zapper77]

In post #1, I posted the screen shot of BMS test program showing all 6 batteries
Battery #2 is circled in red

I have it set at 57.5 currently
I think it was a 56.5 before?

That photo shows 53volts. 53 volts isn't even close to being fully charged. 53v is 80% at best.

 

[EL34xyz]

I took a fresh screen shot of BMS Test
The readings have changed to what you see in this screen shot
pack #2 is the one showing a low SOC compared to the other 5

 

[Zapper77]

I took a fresh screen shot of BMS Test
The readings have changed to what you see in this screen shot

Post another screenshot when the batteries reach 56.5v or higher.

Edit, to delete the bulk question...as i see your response above.

 

[EL34xyz]

Post another screenshot when the batteries reach 56.5v or higher.

Edit, to delete the bulk question...as i see your response above.

I'll do that tomorrow morning after the batteries have had a grid charge between at 1am and 6am
There is some solar here today, but not enough to do a full charge

 

[EL34xyz]

Better results this morning after a full grid charge last night
Battery pack #2 has come back up to 100%
One of the changes I made as per one of the suggestions above was raising the charge voltage to 57.5

The overall SOC of the 6 batteries has been going down slowly over the last 4 months

Here is a fresh BMS test screen shot from this morning
Pack 2 has come back up to 100%
Also a screen shot of powerview showing the grid charge last night

 

[Zapper77]

Better results this morning after a full grid charge last night
Battery pack #2 has come back up to 100%
One of the changes I made as per one of the suggestions above was raising the charge voltage to 57.5

The overall SOC of the 6 batteries has been going down slowly over the last 4 months

Here is a fresh BMS test screen shot from this morning
Pack 2 has come back up to 100%
Also a screen shot of powerview showing the grid charge last night

Thank you for the update. I'm glad the batteries are finally reporting full.

I've found that 56.5 or 56.6 is the magic number when the BMS flips to reporting 100%

@Markus_SignatureSolar FYSA

 

[EL34xyz]

Thank you for the update. I'm glad the batteries are finally reporting full.

I've found that 56.5 or 56.6 is the magic number when the BMS flips to reporting 100%

@Markus_SignatureSolar FYSA

Thanks
I think it was set at 56.5 before I started trying to figure out why the SOC was slowly going down over a four month period.
So should I reduce my charge voltage down from 57.5?

 

[DIYrich]

Thanks
I think it was set at 56.5 before I started trying to figure out why the SOC was slowly going down over a four month period.
So should I reduce my charge voltage down from 57.5?

If the "latest recommendation" from the battery manufacturer is 57.1v, then try that number.

Otherwise, the recommendation is up to 58.0v

Recommended Charge Profile for DIY LiFePO4 Batteries *Sticky Post*

12V 4S LiFePO4 Battery w/ BMS: Absorption: 14.5V Float: 13.6V Inverter Cut-off: 10.7V-12V (depending on size of load and voltage drop etc) 24V 8S LiFePO4 Battery w/ BMS Absorption: 29V Float: 27.2V Inverter Cut-off: 21.4V-24V 48V 16S LiFePO4 Battery w/ BMS Absorption: 58V Float: 54.4V...

diysolarforum.com