Actual battery capacity sensor not accurate

Question

Actual battery capacity sensor not accurate

trippfam07 opened this issue 2 years ago · comments

trippfam07 commented 2 years ago

Talking to BMS and getting Data back but some stuff does not come back correct.

Sebastian Muszynski · Answer 1 · Sun Jan 23 2022 03:04:15 GMT+0800 (China Standard Time)

Could you provide the model number, hardware version and software version of your BMS?
Could you name the sensors which doesn't provide correct measurements/values? Please try to be explicit by using the config values f.e. capacity_remaining.
Do you use an ESP8266 or ESP32 to talk to the BMS?

trippfam07 · Answer 2 · Sun Jan 23 2022 03:15:10 GMT+0800 (China Standard Time)

Model JK-B1A20S15P
Hardware V =8.x
Software V=8.14U
ESP8266

trippfam07 · Answer 3 · Sun Jan 23 2022 03:17:56 GMT+0800 (China Standard Time)

I am not sure what you mean by using the config values f.e.

Sebastian Muszynski · Answer 4 · Sun Jan 23 2022 03:19:33 GMT+0800 (China Standard Time)

Could you provide your configuration.yaml and mark the "faulty" sensors somehow?

For example:

sensor:
  - platform: jk_bms
    min_cell_voltage: # <-- is empty
      name: "${name} min cell voltage"
    max_cell_voltage: # <-- should be 5 is 10
      name: "${name} max cell voltage"
    delta_cell_voltage:
      name: "${name} delta cell voltage"
    cell_voltage_1:
      name: "${name} cell voltage 1"
    cell_voltage_2:

trippfam07 · Answer 5 · Sun Jan 23 2022 03:21:53 GMT+0800 (China Standard Time)

actual_battery_capacity:
name: "${name} actual battery capacity"

Should be 560 and it is showing 512

trippfam07 · Answer 6 · Sun Jan 23 2022 03:25:44 GMT+0800 (China Standard Time)

I can send you a copy of the logs if you like?

Sebastian Muszynski · Answer 7 · Sun Jan 23 2022 03:32:05 GMT+0800 (China Standard Time)

Please enable the debug mode of the uart component by adding:

uart:
  ...
  debug:
    direction: BOTH

The full uart section will look like this:

uart:
  id: uart0
  baud_rate: 115200
  rx_buffer_size: 384
  tx_pin: GPIO14
  rx_pin: GPIO4
  debug:
    direction: BOTH

Please flash again and check the logs of the esphome node by:

esphome logs your-device.yaml

Esphome prints the log after flashing automatically:

esphome run your-device.yaml

I'm interested in these lines / the raw traffic between the ESP and your BMS:

[20:29:14][D][uart_debug:114]: >>> 4E:57:00:13:00:00:00:00:06:03:00:00:00:00:00:00:68:00:00:01:29
[20:29:19][D][uart_debug:114]: >>> 4E:57:00:13:00:00:00:00:06:03:00:00:00:00:00:00:68:00:00:01:29

Sebastian Muszynski · Answer 8 · Sun Jan 23 2022 03:35:12 GMT+0800 (China Standard Time)

Let's first focus on actual_battery_capacity: https://github.com/syssi/esphome-jk-bms/blob/main/components/jk_bms/jk_bms.cpp#L331-L332

trippfam07 · Answer 9 · Sun Jan 23 2022 03:49:10 GMT+0800 (China Standard Time)

[13:43:12][D][uart_debug:114]: >>> 4E:57:00:13:00:00:00:00:06:03:00:00:00:00:00:00:68:00:00:01:29
[13:43:12][D][uart_debug:114]: <<< 4E:57:01:21:00:00:00:00:06:00:01:79:30:01:0D:38:02:0D:2F:03:0D:34:04:0D:31:05:0D:2F:06:0D:2C:07:0D:3C:08:0D:2C:09:0D:33:0A:0D:2A:0B:0D:3C:0C:0D:2A:0D:0D:3E:0E:0D:2D:58:58:33:AC:18:19:00:15:81:00:11:82:00:08:83:15:1A:84:85:A5:85:4F:86:02:87:00:00:89:00:00:00:00:8A:00:10:8B:00:00:8C:00:03:8E:16:D0:8F:10:40:90:0E:42:91:0D:DE:92:00:05:93:0A:28:94:0B:B8:95:00:05:96:01:2C:97:00:96:98:01:2C:99:00:64:9A:00:1E:9B:0D:48:9C:00:07:9D:01:9E:00:5A:9F:00:46:A0
[13:43:12][D][uart_debug:114]: <<< 00:64:A1:00:64:A2:00:14:A3:00:46:A4:00:46:A5:FF:EC:A6:FF:F6:A7:FF:EC:A8:FF:F6:A9:10:AA:00:00:02:30:AB:01:AC:01:AD:04:C9:AE:01:AF:01:D8:00:0A:B1:14:B2:31:32:33:34:35:36:00:00:00:00:B3:C0:BB:9A:1B:AB:A3:20:55:73:B5:32:31:31:30:B6:00:01:F6:00:B7:48:38:2E:58:5F:5F:53:38:2E:31:34:55:5F:5F:5F:B8:00:B9:00:00:02:00:BA:42:54:33:30:37:32:30:32:30:31:32:30:30:30:30:32:30:30:35:32:31:30:30:31:C0:01:00:00:00:00:68:00:00:4B:68

trippfam07 · Answer 10 · Sun Jan 23 2022 03:53:54 GMT+0800 (China Standard Time)

Is that what you wanted?

trippfam07 · Answer 11 · Sun Jan 23 2022 03:57:12 GMT+0800 (China Standard Time)

I looked at the logs and also found this.

[13:55:32][D][uart_debug:114]: >>> 4E:57:00:13:00:00:00:00:06:03:00:00:00:00:00:00:68:00:00:01:29
[13:55:32][D][uart_debug:114]: <<< 4E:57:01:21:00:00:00:00:06:00:01:79:30:01:0D:2A:02:0D:2D:03:0D:2D:04:0D:2A:05:0D:37:06:0D:28:07:0D:37:08:0D:29:09:0D:27:0A:0D:2D:0B:0D:2E:0C:0D:2A:0D:0D:37:0E:0D:2A:0F:0D:32:10:0D:25:80:00:15:81:00:11:82:00:11:83:15:15:84:93:86:85:50:86:02:87:00:00:89:00:00:00:00:8A:00:10:8B:00:00:8C:00:03:8E:16:D0:8F:10:40:90:0E:42:91:0D:DE:92:00:05:93:0A:28:94:0B:B8:95:00:05:96:01:2C:97:00:96:98:01:2C:99:00:64:9A:00:1E:9B:0D:48:9C:00:07:9D:01:9E:80:5A:9F:00:46
[13:55:32][W][jk_modbus:073]: JkModbus CRC Check failed! 4B8A!=4B0A
[13:55:32][D][uart_debug:114]: <<< A0:00:64:A1:00:64:A2:00:14:A3:00:46:A4:00:46:A5:FF:EC:A6:FF:F6:A7:FF:EC:A8:FF:F6:A9:10:AA:00:00:02:30:AB:01:AC:01:AD:04:C9:AE:01:AF:01:B0:00:0A:B1:14:B2:31:32:33:34:35:36:00:00:00:00:B3:00:B4:49:6E:70:75:74:20:55:73:B5:32:31:31:30:B6:00:01:F6:00:B7:48:38:2E:58:5F:5F:53:38:2E:31:34:55:5F:5F:5F:B8:00:B9:00:00:02:00:BA:42:54:33:30:37:32:30:32:30:31:32:30:30:30:30:32:30:30:35:32:31:30:30:31:C0:01:00:00:00:00:68:00:00:4B:0A

Sebastian Muszynski · Answer 12 · Sun Jan 23 2022 03:59:21 GMT+0800 (China Standard Time)

The first line is the request (TX). Line 2 and 3 is the response from the BMS. If we add some linebreaks the response is better readable:

4E:57:01:21:00:00:00:00:06:00:01:
79:30:
01:0D:38:
02:0D:2F:
03:0D:34:
04:0D:31:
05:0D:2F:
06:0D:2C:
07:0D:3C:
08:0D:2C:
09:0D:33:
0A:0D:2A:
0B:0D:3C:
0C:0D:2A:
0D:0D:3E:
0E:0D:2D:
58:58:33:AC:18:19:00:15:
81:00:11:
82:00:08:
83:15:1A:
84:85:A5:
85:4F:
86:02:
87:00:00:
89:00:00:00:00:
8A:00:10:
8B:00:00:
8C:00:03:
8E:16:D0:
8F:10:40:
90:0E:42:
91:0D:DE:
92:00:05:
93:0A:28:
94:0B:B8:
95:00:05:
96:01:2C:
97:00:96:
98:01:2C:
99:00:64:
9A:00:1E:
9B:0D:48:
9C:00:07:
9D:01:
9E:00:5A:
9F:00:46:
A0:00:64:
A1:00:64:
A2:00:14:
A3:00:46:
A4:00:46:
A5:FF:EC:
A6:FF:F6:
A7:FF:EC:
A8:FF:F6:
A9:10:
AA:00:00:02:30:
AB:01:
AC:01:
AD:04:C9:
AE:01:
AF:01:D8:00:0A:
B1:14:
B2:31:32:33:34:35:36:00:00:00:00:
B3:C0:BB:9A:1B:AB:A3:20:55:73:
B5:32:31:31:30:
B6:00:01:F6:00:
B7:48:38:2E:58:5F:5F:53:38:2E:31:34:55:5F:5F:5F:
B8:00:
B9:00:00:02:00:   # <-- this is the actual_battery_capacity sensor value 0x00 0x00 0x20 0x00 = 0x200 = 512 decimal
BA:42:54:33:30:37:32:30:32:30:31:32:30:30:30:30:32:30:30:35:32:31:30:30:31:
C0:01:
00:00:00:00:68:00:00:4B:68

The first hex value of every line is the register. See https://github.com/syssi/esphome-jk-bms/#registers

Register 0xB9 is the "actual battery capacity". The next 4 bytes is the value provided by the BMS. If we convert the value 0x00 0x00 0x20 0x00 = 0x0200 to decimal the value is 512. This is the sensor value published by this component. I don't see much room to improve here.

Sebastian Muszynski · Answer 13 · Sun Jan 23 2022 04:06:25 GMT+0800 (China Standard Time)

Please don't care about the CRC error. Some frames/responses are dropped because of CRC errors. The next reading will be fine again and will update the sensor measurements properly.

trippfam07 · Answer 14 · Sun Jan 23 2022 04:08:46 GMT+0800 (China Standard Time)

Ok so on my bluetooth app There is a value for remain battery and it equals 81%
and there is a value for remain capacity and it equals 457.3 ah
Is there a way to make the remain capacity show up?

Sebastian Muszynski · Answer 15 · Sun Jan 23 2022 04:13:55 GMT+0800 (China Standard Time)

Could you tell me the value of the capacity_remaining sensor? May be please provide the full log of sensor measurements.

Sebastian Muszynski · Answer 16 · Sun Jan 23 2022 04:15:12 GMT+0800 (China Standard Time)

https://github.com/syssi/esphome-jk-bms/blob/main/components/jk_bms/jk_bms.cpp#L127-L128

85:4F:  # Register 0x85, value 0x4F = 79%

trippfam07 · Answer 17 · Sun Jan 23 2022 04:16:21 GMT+0800 (China Standard Time)

[14:15:27][I][jk_bms:061]: Status frame received
[14:15:27][D][sensor:125]: '${name} cell voltage 1': Sending state 3.37400 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 2': Sending state 3.36500 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 3': Sending state 3.38000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 4': Sending state 3.36900 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 5': Sending state 3.36400 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 6': Sending state 3.36800 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 7': Sending state 3.36800 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 8': Sending state 3.36300 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 9': Sending state 3.37200 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 10': Sending state 3.36300 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 11': Sending state 3.37900 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 12': Sending state 3.36100 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 13': Sending state 3.38000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 14': Sending state 3.36400 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 15': Sending state 3.37800 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage 16': Sending state 3.35900 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} min cell voltage': Sending state 3.35900 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} max cell voltage': Sending state 3.38000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} delta cell voltage': Sending state 0.02100 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} power tube temperature': Sending state 20.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} temperature sensor 1': Sending state 17.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} temperature sensor 2': Sending state 16.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} total voltage': Sending state 53.89000 V with 2 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} current': Sending state -45.81000 A with 2 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} capacity remaining': Sending state 82.00000 % with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} temperature sensors': Sending state 2.00000  with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} total charging cycle capacity': Sending state 0.00000  with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} battery strings': Sending state 16.00000  with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} errors bitmask': Sending state 0.00000  with 0 decimals of accuracy
[14:15:27][D][text_sensor:067]: '${name} errors': Sending state ''
[14:15:27][D][sensor:125]: '${name} operation mode bitmask': Sending state 3.00000  with 0 decimals of accuracy
[14:15:27][D][text_sensor:067]: '${name} operation mode': Sending state 'Charging enabled;Discharging enabled'
[14:15:27][D][sensor:125]: '${name} total voltage overvoltage protection': Sending state 58.40000 V with 2 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} total voltage undervoltage protection': Sending state 41.60000 V with 2 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage overvoltage protection': Sending state 3.65000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage overvoltage recovery': Sending state 3.55000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage overvoltage delay': Sending state 5.00000 s with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage undervoltage protection': Sending state 2.60000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage undervoltage recovery': Sending state 3.00000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell voltage undervoltage delay': Sending state 5.00000 s with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} cell pressure difference protection': Sending state 0.30000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} discharging overcurrent protection': Sending state 150.00000 A with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} discharging overcurrent delay': Sending state 300.00000 s with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} charging overcurrent protection': Sending state 100.00000 A with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} charging overcurrent delay': Sending state 30.00000 s with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} balance starting voltage': Sending state 3.40000 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} balance opening pressure difference': Sending state 0.00700 V with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} power tube temperature protection': Sending state 90.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} power tube temperature recovery': Sending state 70.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} temperature sensor temperature protection': Sending state 100.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} temperature sensor temperature recovery': Sending state 100.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} temperature sensor temperature difference protection': Sending state 20.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} charging high temperature protection': Sending state 70.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} discharging high temperature protection': Sending state 70.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} charging low temperature protection': Sending state -20.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} charging low temperature recovery': Sending state -10.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} discharging low temperature protection': Sending state -20.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} discharging low temperature recovery': Sending state -10.00000 °C with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} current calibration': Sending state 1.22500 A with 3 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} device address': Sending state 1.00000  with 0 decimals of accuracy
[14:15:27][D][text_sensor:067]: '${name} battery type': Sending state 'Ternary Lithium'
[14:15:27][D][sensor:125]: '${name} sleep wait time': Sending state 10.00000 s with 0 decimals of accuracy
[14:15:27][D][sensor:125]: '${name} alarm low volume': Sending state 20.00000 % with 0 decimals of accuracy
[14:15:27][D][text_sensor:067]: '${name} password': Sending state '123456'
[14:15:27][D][text_sensor:067]: '${name} device type': Sending state 'Input Us'
[14:15:27][D][sensor:125]: '${name} total runtime': Sending state 2141.86670 h with 0 decimals of accuracy
[14:15:27][D][text_sensor:067]: '${name} software version': Sending state 'H8.X__S8.14U___'
[14:15:27][D][sensor:125]: '${name} actual battery capacity': Sending state 512.00000 Ah with 0 decimals of accuracy
[14:15:27][D][text_sensor:067]: '${name} manufacturer': Sending state 'BT3072020120000200521001'

Sebastian Muszynski · Answer 18 · Sun Jan 23 2022 04:21:19 GMT+0800 (China Standard Time)

Another minor thing: Esphome wasn't able to replace the variable ${name}. I assume it wasn't defined. Please add this to the top of your configuration:

substitutions:
  name: jk-bms

Sebastian Muszynski · Answer 19 · Sun Jan 23 2022 04:22:56 GMT+0800 (China Standard Time)

May be I didn't understand what you are looking for. This value is available

[14:15:27][D][sensor:125]: '${name} capacity remaining': Sending state 82.00000 % with 0 decimals of accuracy

and looks good to me. Are you looking for the remaining capacity in Ah? Could you tell me the total capacity of your battery?

trippfam07 · Answer 20 · Sun Jan 23 2022 04:27:34 GMT+0800 (China Standard Time)

Yes but on my bluetooth app there is 2 sections for the battery

Remain Battery = 82%
Remain Capacity = 463.4 ah
My total capacity is 560 ah

trippfam07 · Answer 21 · Sun Jan 23 2022 04:30:44 GMT+0800 (China Standard Time)

trippfam07 commented 2 years ago

Sebastian Muszynski · Answer 22 · Sun Jan 23 2022 04:37:04 GMT+0800 (China Standard Time)

The total_capacity sensor isn't supported yet:

https://github.com/syssi/esphome-jk-bms/blob/main/components/jk_bms/jk_bms.cpp#L280-L281

But it looks like your BMS returns the proper value here:

AA:00:00:02:30: # Register 0xAA, value 0x0230 = 560 decimal

It looks like the actual_battery_capacity sensor is useless. I assume the value will drop at some point from 512 to 256 or something. Could you monitor the actual_battery_capacity value for some days and provide some updates? I assume the resolution is super bad here.

But we could introduce a new calculated sensor by doing something like this: 560 * 82% = 459,2 Ah

What do you think?

trippfam07 · Answer 23 · Sun Jan 23 2022 04:46:54 GMT+0800 (China Standard Time)

So how would i program that? for the 560 decimal?

And yes the other would be good to

Sebastian Muszynski · Answer 24 · Sun Jan 23 2022 05:02:53 GMT+0800 (China Standard Time)

I will care about it. It will take a few days.

trippfam07 · Answer 25 · Sun Jan 23 2022 05:05:02 GMT+0800 (China Standard Time)

when I add the substitutions name to the config, do I have to flash again? And if yes can I do it while its connected to the bms?

Sebastian Muszynski · Answer 26 · Sun Jan 23 2022 05:07:39 GMT+0800 (China Standard Time)

Yes. You have to flash the new version but the ESP doesn't need to be attached to the USB port anymore. You can use OTA now.

trippfam07 · Answer 27 · Sun Jan 23 2022 05:15:45 GMT+0800 (China Standard Time)

Ok thank you very much for you help!!!!!
I look forward to hearing from you when you are done.

Sebastian Muszynski · Answer 28 · Sun Jan 23 2022 17:13:22 GMT+0800 (China Standard Time)

I've improved the component. Please extend your configuration by the two new sensors:

    capacity_remaining_derived:
      name: "${name} capacity remaining derived"
    total_battery_capacity_setting:
      name: "${name} total battery capacity setting"

And try/flash again.

Sebastian Muszynski · Answer 29 · Sun Jan 23 2022 17:15:08 GMT+0800 (China Standard Time)

Feel free to create a new issue if you are missing something else.