search

syssi / esphome-jk-bms

ESPHome component to monitor and control a Jikong Battery Management System (JK-BMS) via UART-TTL or BLE
Apache License 2.0
460 stars 154 forks source link

CRC check failed! with JK_B2A8S20P and SW V11.262 #362

Closed Blackforrestpilot closed 11 months ago

Blackforrestpilot commented 1 year ago

Hi, i'm allready using an JK_B2A8S20P with an ESP8266 over UART. It runs since several weeks without any issues on SW V11.17.

Now i'm building a new unit with an other BMS with SW V11.262 and getting several failure messages.

CRC_error

the new ESP8266 runs on my first BMS without issues. I've allready checked the wiring, but without success. jk-bms-kopie.yaml.txt

any ideas, then changing to an ESP32?

Best regards Christoph

Blackforrestpilot commented 1 year ago

additional info: my "old" unit based on version 1.2.0 is running with the new BMS with SW V11.262 without any problems This old unit was build with ESPHome 2022.4.0

regards Christoph

syssi commented 1 year ago

Are you able to downgrade your ESPHome installation? Could you try component version 1.5.0 plus ESPHome 2022.4.0?

Blackforrestpilot commented 1 year ago

i tested on an different PC, which i've used to setup the first unit. Python version is 3.11.0 esphome version is 2022.10.2

unfortunately i get the same result with "CRC check failed!" and "Invalid header" image

I've ordered some new ESP and will test my luck with new hardware. i will keep you informed

Blackforrestpilot commented 1 year ago

I am now completely confused This afternoon I flashed the 2nd ESP8266 with the old program and connected it to my first battery with BMS (SW V11.17). There it works without any errors or abnormalities. Then I flashed the previous ESP with the new program and connected it to the new BMS (SW V11.262). And there it runs without any problems. No CRC or header errors. Only sometimes there is an error message in the log that took a little too long. image

Very confusing. now that I don't know how to narrow down the cause further, I suggest closing here.

regards Christoph

syssi commented 11 months ago

A CRC error every now and then is fine. Let's close this issue.