When you calibrate voltage on the JK BMS you MUST do it a NO-LOAD: ZERO CURRENT. Open the breaker / disconnector / disable charge and discharge. Let them settle for a while. Then calibrate the voltage measuring with a trustworthy multimeter.
Hi,
Coulomb Counting is only Current. Coulomb = Current x Time [As]
.| 00:37:26 | [D] | [esp32_ble_server:155] | BLE Client connected |
| 00:37:26 | [D] | [esp32_ble_server:164] | BLE Client disconnected |
| 00:37:30 | [D] | [esp-idf:000] | E (185943) BT_HCI: CC evt: op=0x2022, status=0x2 |
?So you are using one ESP32 for each connection or trying to combine into 1?Yesterday I was successful in getting the BLE version to work, but today the cable version is struggling for me.
My hardware = B2A20S20P-Heat-CAN, Atom S3 Lite on the CA-IS3050G.
can_tx_pin: GPIO5
can_rx_pin: GPIO6
tx_pin: GPIO1
rx_pin: GPIO2
All output I can see is more or less this, ( repeating )
00:37:26 [D] [esp32_ble_server:155] BLE Client connected 00:37:26 [D] [esp32_ble_server:164] BLE Client disconnected 00:37:30 [D] [esp-idf:000] E (185943) BT_HCI: CC evt: op=0x2022, status=0x2
Anyone
Are you sure tx/rx is not reversed? Did you connect the GND wire on the jk bms port to somewhere in your esp32?Yesterday I was successful in getting the BLE version to work, but today the cable version is struggling for me.
My hardware = B2A20S20P-Heat-CAN, Atom S3 Lite on the CA-IS3050G.
can_tx_pin: GPIO5
can_rx_pin: GPIO6
tx_pin: GPIO1
rx_pin: GPIO2
All output I can see is more or less this, ( repeating )
00:37:26 [D] [esp32_ble_server:155] BLE Client connected 00:37:26 [D] [esp32_ble_server:164] BLE Client disconnected 00:37:30 [D] [esp-idf:000] E (185943) BT_HCI: CC evt: op=0x2022, status=0x2
Anyone
Yep, connected GND and stayed away from the 48v+ one
I removed the corresponding wire from connector entirely using aYep, connected GND and stayed away from the 48v+ one
It was just worth making sure you double checkedYep, connected GND and stayed away from the 48v+ one
Would you mind pointing me in the right direction on how I can move forward in updating the firmware to v15?
You can check here, he made details guidance and resource included then!
off-grid-garage.com
I have my own DNS Server running so the DNS Record is correctly resolving to the IP Address (Static Lease on the DHCP Server) of the ESP32.
. The only thing that wants to work is a reliable USB cable .I have my own DNS Server running so the DNS Record is correctly resolving to the IP Address (Static Lease on the DHCP Server) of the ESP32.
The problem is that the upload never goes past 10%. Sometimes it fails at 4%. Sometimes it gives up just after starting the upload process.
I also tries to restart the ESP32 in Safe Mode prior to OTA. Nothing
I have my own DNS Server running so the DNS Record is correctly resolving to the IP Address (Static Lease on the DHCP Server) of the ESP32.
The problem is that the upload never goes past 10%. Sometimes it fails at 4%. Sometimes it gives up just after starting the upload process.
I also tries to restart the ESP32 in Safe Mode prior to OTA. Nothing
No 11.43 will not response to request data command as I have mentioned (my version 11.36, 11.42 does not work on wired connection anymore, the "4E:57:00:13:00:00:00:00:06:02:00:00:00:00:00:00:68:00:00:01:28" command does not work! I have not upgraded to V15 as guided by JK-BMS guy as I have not seen any guidance on that and not sure the V15 is supported the upgrading from V11. The only way that seems possible is to use Bluetooth for multiple BMS (my previous pose has the link but I have not tried yet)
Tried on several computers. Ping works. Host file tried previously to no avail...Try to ping the atom and look for potential time outs, or perhaps install esphome on a different computer, and try with a host file ( but yes DNS resolve should be equally good ). Many moving parts here.
A bit side topic but ... How do you manage to get OTA working ?
I tried several approaches and none works so far
a. Using esphome run XXX.yaml -> This results in timeout failure during upload or similar other messages.
GitHub Issues and Home Assistant Forums seem to point to a Network Issue.
I am running this off a Rock 5B using hostapd and an Alpha AWUS1900 USB-Wifi Adapter (RTL8814AU).
b. Running esphome dashboard in a Podman Container (similar to Docker) doesn't really work.
I cannot do anything since autodiscovery doesn't work. If I add devices manually, there really isn't a "Firmware Upload" button or something similar.
c. Running esphome integration for Home Assistant I can see entities etc, but I cannot upload a new firmware.
logger:
level: ERROR
ota:esphome compile .\jk-hybrid-can.yaml
esphome upload .\esp32_hybrid_jk-bms-can.yaml --device 192.168.1.113This is different with the main OTA capability mentioned earlier.
ota:
safe_mode: true
version: 1
password: !secret ota_password
on_begin:
then:
- lambda: id(enable_bluetooth_connection).turn_off();
- logger.log: "BLE shutdown for flashing"esphome:
name: ${name}
platformio_options:
board_build.flash_mode: dio
build_flags:
- -DCONFIG_ARDUINO_LOOP_STACK_SIZE=32768
comment: ${device_description}
project:
name: !secret project_name
version: !secret project_version
on_boot:
then:
- switch.turn_on: can_switch_charging
- switch.turn_on: can_switch_discharging
- switch.turn_on: can_switch_float
- switch.turn_on: can_switch_auto_charge_current
- switch.turn_on: can_switch_auto_discharge_current
- switch.turn_on: can_switch_auto_charge_voltageota:
safe_mode: true
version: 1
password: !secret ota_passwordI have
logger:
hardware_uart: USB_SERIAL_JTAG
# level: DEBUG # For Debugging only
level: INFO # For Production
ota:
safe_mode: true
version: 1
password: !secret ota_password
on_begin:
then:
- lambda: id(enable_bluetooth_connection).turn_off();
- logger.log: "BLE shutdown for flashing"esphome run ./esp32-ble-1.17.5.yamlOTA Version 2 also just failed ...
