battery parameters

[madtatu-development]

Hi,

I was so excited when I found Smart BMS utility iOS app, as after purchasing my BMS with BLE module, I thought there would be only Android apps out there. But I got lost, and I am sure it is 100% me, being dummy, so I would like to ask your kind help in my battery configuration question:

Battery Specs:

• 10S17P Battery Pack (custom built by myself)
• Cells type: LG INR18650-MJ1
• So in total: 59.5Ah, 170A, 36V
• BMS type: LH-SP15S008 with BLE module and 2 temp sensor (all attached)

Single cell specs:

• Voltage charge max.: 4.20 V
• Voltage, nominal: 3.65 V
• Voltage, discharge end: 2.50 V
• Capacity, max.: 3500.00 mAh
• Constant charge current, max.: 3.40 A
• Charge constant standard: 1.7 A
• Discharge standard: 680 mA
• Max. continuous discharge current: 10.00 A
• Peak discharge theoretic, 4 sec: 17.5 A
• C-rate (charge, max.): 0.97 C
• C-rate (discharge, max.): 2.86 C

Status:

• Battery is fully charged (each separate cells were measured too for countercheck)
• Smart BMS utility can find the BMS and connect to it perfectly.
• The basic data its read from BMS are:

• The configuration data:

---- The PROBLEM ----

• I am UNABLE to TURN ON the "Discharge" button, because it triggers the following error: "Warning battery Undervoltage!"

---- QUESTION ----

• Triple checked setup, cables, cells, etc, and confirmed to be perfect.
• So, I assume, this problem comes form the fact, that the BMS have to be configured.
  - I searched a lot on Google and also read the Overkill Solar doc, but still as I am not 100% sure, to be "better safe then sorry", may I ask your kind help what's the best value to write into these config fields (based on specs above) to ensure that I am able to use my battery ? :

Number of cells:

Total battery capacity:
Total cycle capacity:
Cell selfdischarge rate:
Cell full voltage:
Cell 80% charge voltage:
Cell 60% charge voltage:
Cell 40% charge voltage:
Cell 20% charge voltage:
Cell empty voltage:

Balancing start voltage:
Cell delta target:
Enable balancing : ON/OFF
Balancing only whilst charging: ON/OFF

Cell overvoltage
--Trigger:
--Release:
--Delay:

Cell undervoltage
--Trigger:
--Release:
--Delay:

Pack overvoltage:
--Trigger:
--Release:
--Delay:

Pack undervoltage
--Trigger:
--Release:
--Delay:

Charge overtemperature
--Trigger:
--Release:
--Delay:

Charge undertemperature
--Trigger:
--Release:
--Delay:

Discharge overtemperature
--Trigger:
--Release:
--Delay:

Discharge undertemperature
--Trigger:
--Release:
--Delay:

**I know I am asking a lot of data help here, which should be logically come from specs data, but I promise, I am not asking this help because I am lazy or such. I am just desperately need a professional help to confirm a good setup to fully understand all fields.

Many many many many many many BIG thanks for your time and help,**

Andras

[NeariX67]

i really really appreciate your detailed list. It makes helping people like you much much easier.

So you have a 10S battery pack. So the lower battery voltage (assuming you use 3000mV instead of the cell cutoff voltage of 2500mV) would be at 10*3000mV = 30000mV and your full battery voltage should be 10*4200mV, so 42000mV.
You currently have it set to 42000mV/64000mV so 1. in the wrong order and 2. wrong values

This should resolve your issues:
Pack overvoltage:
--Trigger: 42500mV (just a little bit over the calculated 42000mV)
--Release: 42000mV (just right what we calculated)
--Delay: (whatever you want - or keep default)

Pack undervoltage
--Trigger: 29500mV (a little bit under the calculated 30000mV, you might go as low as 25000mV)
--Release: 30000mV
--Delay: (whatever you want - or keep default)

If you experience any other issues i'll gladly help you.

[madtatu-development]

Hello Sir, May I ask if you received my post above ?

[NeariX67]

If you mean your post from 4 days ago, yes, otherwise no

[madtatu-development]

Yeah I mean that. :) Sorry for asking, just you usually respond pretty fast, so I just wanted to be sure.

[NeariX67]

Yeah, i just didn't want to publish a new update just for this very very small issue. But i've got a message from another user that found another small issue that might be worth an update. So i'd fix that if the other issue is actually an issue.

[madtatu-development]

Absolutely Sir, no rush at all. Evenmore I should be more precise and use the "Issues" tab here on Github, instead of the discussion part. You are awesome, I oove your app!