JBD BMS keeps turning off at 28amps even tho I set over current discharge protection at 60amps.

[Alphabet]

I have a 16s4p battery with Eve 50e cells. I'm using it on a Toseven Dmo1, it's 60v 25amps. Pulls max 28amps continuous at 1500w. Issue is my battery keeps going into Over discharge protection, I have a JBD BMS. Idk what's going on. Here are the settings im currently running. It used to be fine until I changed charging current from 3 to 6amps cuz I changed from 2amp to 5 amps charger.

DATA
--------------------------
{
"app_version": "2.0.2",
"last_updated_data": "2025-06-19, 9:59:29 p.m.",
"platform": "android",
"os_version": 29,
"device_name": "SP17S005P17S60A",
"supported": false
}

PACK
--------------------------
{
"charging": "no",
"discharging": "no",
"charge_state": "89%",
"pack_voltage": "63.76 V",
"pack_capacity": "17.9Ah of 20Ah",
"power": "0.0 W",
"charge_toggle_switch": "on",
"discharge_toggle_switch": "off"
}

ALARMS
--------------------------
[
"Discharge Overcurrent"
]

TEMP SENSORS
--------------------------
[
"Temp. Sensor 1 - 26.9°C",
"Temp. Sensor 2 - 24.0°C",
"Temp. Sensor 3 - 24.0°C"
]

CELL INFO
--------------------------
Δ: 0.002, min[1]: 3.981, max[3]: 3.983

CELL VOLTAGES
--------------------------
[
"1 3.981 V [not balancing]",
"2 3.982 V [not balancing]",
"3 3.983 V [not balancing]",
"4 3.983 V [not balancing]",
"5 3.982 V [not balancing]",
"6 3.983 V [not balancing]",
"7 3.982 V [not balancing]",
"8 3.983 V [not balancing]",
"9 3.981 V [not balancing]",
"10 3.981 V [not balancing]",
"11 3.982 V [not balancing]",
"12 3.982 V [not balancing]",
"13 3.982 V [not balancing]",
"14 3.983 V [not balancing]",
"15 3.983 V [not balancing]",
"16 3.982 V [not balancing]"
]

SESSION VALUES
--------------------------
{
"max_volts": "63.82 V",
"min_volts": "61.46 V",
"max_charge": "NA",
"max_discharge": "24.3 A",
"max_charge_power": "NA",
"max_discharge_power": "1495.4 W"
}

BMS INFO
--------------------------
{
"manufacturer": "DGJBD",
"firmware_version": "4.1",
"device_name": "SP17S005P17S60A",
"manufacture_date": "Mon May 26 2025",
"battery_cycles": 6,
"barcode": ""
}

EVENT COUNTS
--------------------------
{
"over_voltage": 1,
"under_voltage": 2,
"charging_low_temp": 91,
"chargin_over_temp": 0,
"charging_over_current": 15,
"discharging_low_temp": 0,
"discharging_over_temp": 0,
"discharging_over_current": 45,
"short_circuit": 46,
"single_cell_over_voltage": 1,
"single_cell_under_voltage": 3
}

CONFIG
--------------------------

<----GENERAL---->
Number of Cells: 16

<----Capacity Configuration---->
Total Battery Capacity: 20000 mAh
Total Cycle Capacity: 20000 mAh
Cell Full Voltage: 4150 mV
Cell Minimal Voltage: 3000 mV
Cell Self Discharge: 0 %
Cell 100% Cap. Voltage: 4100 mV
Cell 90% Cap. Voltage: 4030 mV
Cell 80% Cap. Voltage: 3960 mV
Cell 70% Cap. Voltage: 3890 mV
Cell 60% Cap. Voltage: 3820 mV
Cell 50% Cap. Voltage: 3750 mV
Cell 40% Cap. Voltage: 3680 mV
Cell 30% Cap. Voltage: 3580 mV
Cell 20% Cap. Voltage: 3450 mV
Cell 10% Cap. Voltage: 3300 mV

<----Balancer Configuration---->
Start Voltage: 3900 mV
Delta to Balance: 15 mV
Balancer Enabled: True
Bal. only when charging: False

<----Function Configuration---->
SW switch circuit enable: True
Display Celsius: True

<----Protections---->
charge over temp
trigger: 45°C 113°F
release: 35°C 95°F
delay: 5 s

charge under temp
trigger: -30°C -22°F
release: -25°C -13°F
delay: 5 s

discharge over temp
trigger: 45°C 113°F
release: 40°C 104°F
delay: 5 s

discharge under temp
trigger: -30°C -22°F
release: -25°C -13°F
delay: 5 s

batt over voltage
trigger: 68000 mV
release: 66400 mV
delay: 2 s

batt under voltage
trigger: 44800 mV
release: 46400 mV
delay: 2 s

cell over voltage
trigger: 4200 mV
release: 4150 mV
delay: 2 s

cell under voltage
trigger: 3000 mV
release: 2950 mV
delay: 2 s

charge over current
trigger: 3000 mA
release: 32 s
delay: 10 s

discharge over current
trigger: -60000 mA
release: 20 s
delay: 20 s


<----Level 2 Protections---->
Level 2 Overcurrent
trigger: 340 A
delay: 8 mS

Level 2 Overvoltage
trigger: 4300 mV
delay: 8 s

Level 2 Undervoltage
trigger: 2500 mV
delay: 1 s


<----Level 3 Protections---->
Level 3 Protections
trigger: 440 A
delay: 70 uS
release: 5 s


<----NTC enable---->
1 | 1 | 1 | 0 | 0 | 0 | 0 | 0

 

[amberwolf]

When drawing the current that shuts it off, what are all the cell voltages at that instant?

If any of them are sagging enough to trigger either LVC or voltage-delta, it could shutdown.

 

[Alphabet]

When drawing the current that shuts it off, what are all the cell voltages at that instant?

If any of them are sagging enough to trigger either LVC or voltage-delta, it could shutdown.

No where near LVC, they drop around 3.8, although sometimes on the smart BMS app it reports a drop of 0 but I think that's a glitch.

 

[Zambam]

Are these events real or glitches? 45 discharge over current? 46 short circuit?

EVENT COUNTS
--------------------------
{
"over_voltage": 1,
"under_voltage": 2,
"charging_low_temp": 91,
"chargin_over_temp": 0,
"charging_over_current": 15,
"discharging_low_temp": 0,
"discharging_over_temp": 0,
"discharging_over_current": 45,
"short_circuit": 46,
"single_cell_over_voltage": 1,
"single_cell_under_voltage": 3
}

 

[Alphabet]

Real as in they did happen because it keeps tripping at 24amps but also glitches cuz it keeps tripping at 24amps even if I have it set to 60amps in the parameters.

 

[Zambam]

Maybe the 46 short circuits are real? Check that there's no shorts anywhere, including the motor and controller.

 

[Alphabet]

Maybe the 46 short circuits are real? Check that there's no shorts anywhere, including the motor and controller.

How do I check that?

 

[amberwolf]

No where near LVC, they drop around 3.8, although sometimes on the smart BMS app it reports a drop of 0 but I think that's a glitch.

Even if it's a glitch, if it processes that 0 at all in the BMS itself then that would shut it down.

Same for any other values that exceed any of the limits or shutdown parameters, such as cell under or over voltage, etc.


Regarding short circuits, there will be some method the BMS uses to determine this is happening. Uusallly that's a current exceeding some amp limit over some time limit, the shorter the time and the higher the amps the worse the short. If it doesn't have any parameters for this, you would have to see if the manual (if any) or the manufacturer (if they'll answer you) can tell you what specifically triggers this alert and exactly what conditions cause that trigger.

 

[Zambam]

How do I check that?

Easier said then done. Clamp on ammeter around either battery leads with a camera recording when the short happens?

 

[Alphabet]

Even if it's a glitch, if it processes that 0 at all in the BMS itself then that would shut it down.

Same for any other values that exceed any of the limits or shutdown parameters, such as cell under or over voltage, etc.


Regarding short circuits, there will be some method the BMS uses to determine this is happening. Uusallly that's a current exceeding some amp limit over some time limit, the shorter the time and the higher the amps the worse the short. If it doesn't have any parameters for this, you would have to see if the manual (if any) or the manufacturer (if they'll answer you) can tell you what specifically triggers this alert and exactly what conditions cause that trigger.

I think I might have fixed it. I put a polymer preset in the jbd app and then changed all the parameters to what I had before. I hope that's okay. But it then killed my motor controller.

 

[amberwolf]

A BMS can't kill your controller. All the BMS can do is turn the output (and charge port) of the battery on or off.

If turning the battery output on or off kills your controller, either it was already broken / made wrong / damaged, or it isn't capable of handling the voltage your battery provides.

If your controller stopped working, there's another problem with your system, such as too much load (current draw from motor by the load on the motor) for the controller to handle, and insufficient protections in the controller (or bypassed by user changes to settings), wiring faults (damage or miswires), incorrect controller setup for the motor and/or system, too high a voltage for the controller, etc.

If you specify all the details of what happened just before the controller stopped working, and then all the specific testing youv'e done and the specific results of that testing, as well as the complete configuration of your system, we might be able to begin helping you troubleshoot it.

 

[Alphabet]

A BMS can't kill your controller. All the BMS can do is turn the output (and charge port) of the battery on or off.

If turning the battery output on or off kills your controller, either it was already broken / made wrong / damaged, or it isn't capable of handling the voltage your battery provides.

If your controller stopped working, there's another problem with your system, such as too much load (current draw from motor by the load on the motor) for the controller to handle, and insufficient protections in the controller (or bypassed by user changes to settings), wiring faults (damage or miswires), incorrect controller setup for the motor and/or system, too high a voltage for the controller, etc.

If you specify all the details of what happened just before the controller stopped working, and then all the specific testing youv'e done and the specific results of that testing, as well as the complete configuration of your system, we might be able to begin helping you troubleshoot it.

Thank you for the reply, that clears things up that it's not my battery. I have a Toseven Dmo1 motor and controllers are known to die so it could be normal, but since I'm new to this, I didn't know if it was possible for a BMS to kill it. Also quick question. Since I applied polymer preset and then changed the parameters to my normal Eve 50e lion nmc cells, does that do anything bad? Like the preset is just custom parameters Right?nothing else changes right.

 

[Zambam]

Are you using the JBD Xiaoxiang phone app? Paid or free version? Did you export the data from the app (nice feature)? I have a JBD 22S Smart BMS and use the Overkill Solar phone app which does not have the data export function.

Did you build the battery with the BMS? With all the Event Counts I'd recommend checking the wiring.

Can you post the p/n or link to your BMS?

edit:
You may want to try the Overkill Solar app and see if you get different or the same results.

 

[Alphabet]

Are you using the JBD Xiaoxiang phone app? Paid or free version? Did you export the data from the app (nice feature)? I have a JBD 22S Smart BMS and use the Overkill Solar phone app which does not have the data export function.

Did you build the battery with the BMS? With all the Event Counts I'd recommend checking the wiring.

Can you post the p/n or link to your BMS?

edit:
You may want to try the Overkill Solar app and see if you get different or the same results.

I've tried several apps, only thing that worked was the normal xia app, apply preset, write and then rewrite with my settings. I used overkill solar app to export, just click email support and it'll export in the email, copy from there. I have https://www.jbdbms.com/products/sp1...IWKVnEB6NpLsiQ&sku=18065560600544951761942470

Seller said 100amp but gave me 60a

 

[Zambam]

Haha, I would have never figured out how to export data from the Overkill Solar app w/o you telling me. Thanks!

Here's mine for comparison (scooter/ moped is off). 22S2P 32140 15 Ah Gotian LFP cells. I'm still trying different settings on my JBD. One item that's incorrect on mine is:

"battery_cycles": 0

I must have around 15 to 20 charge / discharge cycles but I always see either a 0 or 1, it never accumulates . You have 6 on your's. Is that correct? Any idea why mine does not increment?


DATA
--------------------------
{
"app_version": "2.0.2",
"last_updated_data": "6/21/2025, 3:54:17 PM",
"platform": "ios",
"os_version": "18.5",
"device_name": "SP22S003AL22S40A",
"supported": false
}

PACK
--------------------------
{
"charging": "no",
"discharging": "no",
"charge_state": "78%",
"pack_voltage": "73.28 V",
"pack_capacity": "23.4Ah of 30Ah",
"power": "0.0 W",
"charge_toggle_switch": "on",
"discharge_toggle_switch": "on"
}

ALARMS
--------------------------
[]

TEMP SENSORS
--------------------------
[
"Temp. Sensor 1 - 93.5°F",
"Temp. Sensor 2 - 83.9°F",
"Temp. Sensor 3 - 85.9°F"
]

CELL INFO
--------------------------
Δ: 0.003, min[5]: 3.330, max[19]: 3.333

CELL VOLTAGES
--------------------------
[
"1 3.331 V [not balancing]",
"2 3.331 V [not balancing]",
"3 3.331 V [not balancing]",
"4 3.331 V [not balancing]",
"5 3.330 V [not balancing]",
"6 3.331 V [not balancing]",
"7 3.330 V [not balancing]",
"8 3.331 V [not balancing]",
"9 3.332 V [not balancing]",
"10 3.330 V [not balancing]",
"11 3.331 V [not balancing]",
"12 3.330 V [not balancing]",
"13 3.332 V [not balancing]",
"14 3.331 V [not balancing]",
"15 3.331 V [not balancing]",
"16 3.331 V [not balancing]",
"17 3.331 V [not balancing]",
"18 3.331 V [not balancing]",
"19 3.333 V [not balancing]",
"20 3.331 V [not balancing]",
"21 3.331 V [not balancing]",
"22 3.331 V [not balancing]"
]

SESSION VALUES
--------------------------
{
"max_volts": "73.28 V",
"min_volts": "73.28 V",
"max_charge": "NA",
"max_discharge": "0.0 A",
"max_charge_power": "NA",
"max_discharge_power": "0.0 W"
}

BMS INFO
--------------------------
{
"manufacturer": "DGJBD",
"firmware_version": "7.6",
"device_name": "SP22S003AL22S40A",

"manufacture_date": "Thu Dec 05 2024",
"battery_cycles": 0,
"barcode": ""
}

EVENT COUNTS
--------------------------
{
"over_voltage": 0,
"under_voltage": 0,
"charging_low_temp": 0,
"chargin_over_temp": 0,
"charging_over_current": 0,
"discharging_low_temp": 0,
"discharging_over_temp": 0,
"discharging_over_current": 0,
"short_circuit": 0,
"single_cell_over_voltage": 0,
"single_cell_under_voltage": 0
}

CONFIG
--------------------------

<----GENERAL---->
Number of Cells: 22

<----Capacity Configuration---->
Total Battery Capacity: 30000 mAh
Total Cycle Capacity: 30000 mAh
Cell Full Voltage: 3450 mV
Cell Minimal Voltage: 2800 mV
Cell Self Discharge: 0.1 %
Cell 100% Cap. Voltage: 3340 mV
Cell 90% Cap. Voltage: 3330 mV
Cell 80% Cap. Voltage: 3320 mV
Cell 70% Cap. Voltage: 3300 mV
Cell 60% Cap. Voltage: 3270 mV
Cell 50% Cap. Voltage: 3260 mV
Cell 40% Cap. Voltage: 3250 mV
Cell 30% Cap. Voltage: 3220 mV
Cell 20% Cap. Voltage: 3200 mV
Cell 10% Cap. Voltage: 3000 mV

<----Balancer Configuration---->
Start Voltage: 3350 mV
Delta to Balance: 15 mV
Balancer Enabled: True
Bal. only when charging: False

<----Function Configuration---->
SW switch circuit enable: False
Display Celsius: False

<----Protections---->
charge over temp
trigger: 46°C 115°F
release: 41°C 106°F
delay: 2 s

charge under temp
trigger: 2°C 35°F
release: 3°C 37°F
delay: 2 s

discharge over temp
trigger: 46°C 115°F
release: 41°C 106°F
delay: 2 s

discharge under temp
trigger: -9°C 16°F
release: -7°C 19°F
delay: 2 s

batt over voltage
trigger: 78750 mV
release: 75600 mV
delay: 2 s

batt under voltage
trigger: 44000 mV
release: 48000 mV
delay: 2 s

cell over voltage
trigger: 3750 mV
release: 3600 mV
delay: 2 s

cell under voltage
trigger: 2500 mV
release: 2800 mV
delay: 2 s

charge over current
trigger: 10000 mA
release: 32 s
delay: 5 s

discharge over current
trigger: -40000 mA
release: 32 s
delay: 10 s


<----Level 2 Protections---->
Level 2 Overcurrent
trigger: 440 A
delay: 20 mS

Level 2 Overvoltage
trigger: 3900 mV
delay: 8 s

Level 2 Undervoltage
trigger: 2000 mV
delay: 4 s


<----Level 3 Protections---->
Level 3 Protections
trigger: 2000 A
delay: 100 uS
release: 5 s


<----NTC enable---->
1 | 1 | 1 | 0 | 0 | 0 | 0 | 0

Sent from my iPhone

 

[Zambam]

Seller said 100amp but gave me 60a

Did you pay for 100amp BMS but got a 60amp? That's not right. Anyway 60amp should be fine with you 28amp motor.

 

[Alphabet]

Haha, I would have never figured out how to export data from the Overkill Solar app w/o you telling me. Thanks!

Here's mine for comparison (scooter/ moped is off). 22S2P 32140 15 Ah Gotian LFP cells. I'm still trying different settings on my JBD. One item that's incorrect on mine is:

"battery_cycles": 0

I must have around 15 to 20 charge / discharge cycles but I always see either a 0 or 1, it never accumulates . You have 6 on your's. Is that correct? Any idea why mine does not increment?


DATA
--------------------------
{
"app_version": "2.0.2",
"last_updated_data": "6/21/2025, 3:54:17 PM",
"platform": "ios",
"os_version": "18.5",
"device_name": "SP22S003AL22S40A",
"supported": false
}

PACK
--------------------------
{
"charging": "no",
"discharging": "no",
"charge_state": "78%",
"pack_voltage": "73.28 V",
"pack_capacity": "23.4Ah of 30Ah",
"power": "0.0 W",
"charge_toggle_switch": "on",
"discharge_toggle_switch": "on"
}

ALARMS
--------------------------
[]

TEMP SENSORS
--------------------------
[
"Temp. Sensor 1 - 93.5°F",
"Temp. Sensor 2 - 83.9°F",
"Temp. Sensor 3 - 85.9°F"
]

CELL INFO
--------------------------
Δ: 0.003, min[5]: 3.330, max[19]: 3.333

CELL VOLTAGES
--------------------------
[
"1 3.331 V [not balancing]",
"2 3.331 V [not balancing]",
"3 3.331 V [not balancing]",
"4 3.331 V [not balancing]",
"5 3.330 V [not balancing]",
"6 3.331 V [not balancing]",
"7 3.330 V [not balancing]",
"8 3.331 V [not balancing]",
"9 3.332 V [not balancing]",
"10 3.330 V [not balancing]",
"11 3.331 V [not balancing]",
"12 3.330 V [not balancing]",
"13 3.332 V [not balancing]",
"14 3.331 V [not balancing]",
"15 3.331 V [not balancing]",
"16 3.331 V [not balancing]",
"17 3.331 V [not balancing]",
"18 3.331 V [not balancing]",
"19 3.333 V [not balancing]",
"20 3.331 V [not balancing]",
"21 3.331 V [not balancing]",
"22 3.331 V [not balancing]"
]

SESSION VALUES
--------------------------
{
"max_volts": "73.28 V",
"min_volts": "73.28 V",
"max_charge": "NA",
"max_discharge": "0.0 A",
"max_charge_power": "NA",
"max_discharge_power": "0.0 W"
}

BMS INFO
--------------------------
{
"manufacturer": "DGJBD",
"firmware_version": "7.6",
"device_name": "SP22S003AL22S40A",

"manufacture_date": "Thu Dec 05 2024",
"battery_cycles": 0,
"barcode": ""
}

EVENT COUNTS
--------------------------
{
"over_voltage": 0,
"under_voltage": 0,
"charging_low_temp": 0,
"chargin_over_temp": 0,
"charging_over_current": 0,
"discharging_low_temp": 0,
"discharging_over_temp": 0,
"discharging_over_current": 0,
"short_circuit": 0,
"single_cell_over_voltage": 0,
"single_cell_under_voltage": 0
}

CONFIG
--------------------------

<----GENERAL---->
Number of Cells: 22

<----Capacity Configuration---->
Total Battery Capacity: 30000 mAh
Total Cycle Capacity: 30000 mAh
Cell Full Voltage: 3450 mV
Cell Minimal Voltage: 2800 mV
Cell Self Discharge: 0.1 %
Cell 100% Cap. Voltage: 3340 mV
Cell 90% Cap. Voltage: 3330 mV
Cell 80% Cap. Voltage: 3320 mV
Cell 70% Cap. Voltage: 3300 mV
Cell 60% Cap. Voltage: 3270 mV
Cell 50% Cap. Voltage: 3260 mV
Cell 40% Cap. Voltage: 3250 mV
Cell 30% Cap. Voltage: 3220 mV
Cell 20% Cap. Voltage: 3200 mV
Cell 10% Cap. Voltage: 3000 mV

<----Balancer Configuration---->
Start Voltage: 3350 mV
Delta to Balance: 15 mV
Balancer Enabled: True
Bal. only when charging: False

<----Function Configuration---->
SW switch circuit enable: False
Display Celsius: False

<----Protections---->
charge over temp
trigger: 46°C 115°F
release: 41°C 106°F
delay: 2 s

charge under temp
trigger: 2°C 35°F
release: 3°C 37°F
delay: 2 s

discharge over temp
trigger: 46°C 115°F
release: 41°C 106°F
delay: 2 s

discharge under temp
trigger: -9°C 16°F
release: -7°C 19°F
delay: 2 s

batt over voltage
trigger: 78750 mV
release: 75600 mV
delay: 2 s

batt under voltage
trigger: 44000 mV
release: 48000 mV
delay: 2 s

cell over voltage
trigger: 3750 mV
release: 3600 mV
delay: 2 s

cell under voltage
trigger: 2500 mV
release: 2800 mV
delay: 2 s

charge over current
trigger: 10000 mA
release: 32 s
delay: 5 s

discharge over current
trigger: -40000 mA
release: 32 s
delay: 10 s


<----Level 2 Protections---->
Level 2 Overcurrent
trigger: 440 A
delay: 20 mS

Level 2 Overvoltage
trigger: 3900 mV
delay: 8 s

Level 2 Undervoltage
trigger: 2000 mV
delay: 4 s


<----Level 3 Protections---->
Level 3 Protections
trigger: 2000 A
delay: 100 uS
release: 5 s


<----NTC enable---->
1 | 1 | 1 | 0 | 0 | 0 | 0 | 0

Sent from my iPhone

I'm not really sure because I'm very very new to this whole battery thing. But I threw your message to AI, maybe worth a read and a try to what it suggests,

Alright, here’s the deal—nothing mystical is wrong with your eyes or phone, it’s just how the JBD cycle counter works (and a quirk of your setup).

1. Only full‐depth cycles get counted.
JBD BMS only increments “battery_cycles” when you’ve cumulatively discharged and recharged the full capacity you’ve told it (30 Ah in your config). If you never actually go from ~0 % to 100 % (or equivalently throughput 30 Ah out then 30 Ah back in), the counter stays at 0. Partial rides/charges just sit in the buffer, they don’t bump the integer until you hit the full-capacity threshold.


2. “supported: false” means the app can’t read everything.
Your pack shows "supported": false so the iOS app likely isn’t fully decoding all BMS registers (including the cycle count register). The other unit with 6 cycles probably has a newer/official firmware or is on a supported hardware revision, so the app can actually pull that number.


3. Firmware bugs and write-to-flash timing.
Some JBD firmwares only write the incremented cycle count into flash memory after a safe-shutdown or after X minutes of stable operation. If you’re always riding and then powering off quickly, it might not stick. Upgrading to the latest official JBD firmware (or reflashing with the right hex) and doing a clean power-cycle after a couple full cycles usually fixes it.




---

What you can do

Run a true full cycle. Discharge from ~100 % down to your low-voltage cutoff, then recharge fully, and shut the pack down for a minute.

Update your BMS firmware to the latest official JBD version so that the app can read all registers.

Confirm in the advanced settings (via UART or USB) that “Cycle Count” is enabled and that your “Total Cycle Capacity” matches actual pack capacity.


Once you’ve done a couple proper cycles and given it a clean power-down, you should see that counter tick up from 0 → 1 → 2, etc. After that, partial cycles will accumulate toward the next full 30 Ah throughput.

Bottom line: you’re not crazy—just need to hit full capacity thresholds and be on compatible firmware so the app can actually track
it. Keep at it, man!" - chatgpt


----------------------+-+-+-+-+-+-+-+-+$($($($($(

Of course. Let's get straight to it.
You are correct, the battery_cycles counter on your BMS is not working as it should. It's a common issue with JBD/xiaoxiang BMS units and the fix is usually in the configuration.
The most likely reason your cycle count isn't increasing is because of your Total Cycle Capacity setting. A cycle is only logged after a cumulative discharge equal to this value.
Here’s the breakdown and what to do:
The Problem
Your settings show:
* Total Battery Capacity: 30000 mAh
* Total Cycle Capacity: 30000 mAh
The BMS increments the cycle counter only when it has registered a total of 30,000 mAh of discharged energy. This doesn't have to be all at once. For example, ten separate discharges of 3,000 mAh would equal one cycle.
The issue is that the BMS is often not perfectly accurate at tracking the state of charge, especially near the bottom of the discharge curve. It might stop counting or reset its internal accumulator before it perfectly reaches the 30,000 mAh mark you've set. Therefore, it never officially logs the full cycle.
The Solution
You need to set the Total Cycle Capacity to a slightly lower value than your Total Battery Capacity. This gives the BMS a buffer and ensures it registers the cycle before the pack is fully depleted or recharged.
* Go into your JBD app's configuration settings.
* Locate the Total Cycle Capacity parameter.
* Change it from 30000 mAh to 27000 mAh (which is 90% of your total capacity).
* Write the new settings to the BMS.
After changing this setting, perform one or two deep discharge/charge cycles. You should see the battery_cycles value start to increment correctly." - Gemini

 

[Alphabet]

Did you pay for 100amp BMS but got a 60amp? That's not right. Anyway 60amp should be fine with you 28amp motor.

Yeah sucks, but won't be building from him again, I'm sure it's fine just don't like the dishonesty. Just makes me wonder if he cut any other corners

 

[amberwolf]

Thank you for the reply, that clears things up that it's not my battery. I have a Toseven Dmo1 motor and controllers are known to die so it could be normal, but since I'm new to this, I didn't know if it was possible for a BMS to kill it.

I don't know if there is anything wrong with your battery or not, only that a BMS, by itself, can't kill a controller, unless some other conditions are already being exceeded, so the controller was already at risk.

Also quick question. Since I applied polymer preset and then changed the parameters to my normal Eve 50e lion nmc cells, does that do anything bad? Like the preset is just custom parameters Right?nothing else changes right.

I don't know how your BMS is programmed, or how it's software works internally, so can't answer that one. You'd ahve to get the details from the BMS manufacturer (if they even understand your question, they probably wouldn't give a usefully complete answer).

But as for how presets might work: In most software, a preset is a collection of settings. Most of the time with software I have used (mostly music-creation effects plugins and synths), a preset changes *all* of the settings for *all* of the available parameters a user can change, but no settings that are not available to the user. Sometimes, a preset is specifcally for only a subest of parameters, and changes only those settings, but this has to be made obvious to the user somehow (perhaps by having tabs for the GUI, so that any preset only affects things on that tab...there are many possible ways it could be made to work).

A preset may affect settings for literally anything, nothing, or anywhere between--it's up to the people that wrote the software the preset is created by and used in. If those are different softwares, then you can even have mismatches between what a preset was created to do and what the software it's actually used in can actually do with it, or even what values it accepts from it. The same can be true of presets from different versions of the same software, where changes in the program between versions change what different parameters do or change the range of accepted values, etc.

 

[Zambam]

I have a 16s4p battery with Eve 50e cells. I'm using it on a Toseven Dmo1, it's 60v 25amps. Pulls max 28amps continuous at 1500w. Issue is my battery keeps going into Over discharge protection, I have a JBD BMS. Idk what's going on. Here are the settings im currently running. It used to be fine until I changed charging current from 3 to 6amps cuz I changed from 2amp to 5 amps charger.

Any progress in troubleshooting? I don't think changing charger from 2 A to 5 A unit would cause the issues you are getting. Is the BMS wired correctly? JBD's wiring instructions are confusing.

 

[Alphabet]

Any progress in troubleshooting? I don't think changing charger from 2 A to 5 A unit would cause the issues you are getting. Is the BMS wired correctly? JBD's wiring instructions are confusing.

Yup fixed it

 

[Zambam]

Yup fixed it

What was the problem and what was the fix?

 

[Alphabet]

What was the problem and what was the fix?

I applied the polymer preset on the xia app, then I wrote it to the BMS, I then read the parameters and edited them to the ones I had previously, or as close as I could get them to that. It somehow fixed it. Idk if it can pull 60amps but it can at least pull 30amps fine now.