JKBMS auslesen über BLE (Bluetooth) oder RS485 Adapter mittels EPS, ioBroker

Hey @phil999

hattest du das schonmal zum laufen bekommen egal mit welcher Version?

Den wenn ich mir die Trap Info so anschaue passiert das in der BLE libary ...

kannst du mal Prüfen ob du die selben Libarys und Versionen nutzt wie "ich" ?
sorry wenn das ggf dumme Fragen sind aber manchmal ist es echt im Detail 😉

Arduino IDE 1.8.13 oder 1.8.16
dann Einstellungen für das ESO32 vorgenommen ? -> https://randomnerdtutorials.com/installing-the-esp32-board-in-arduino-ide-windows-instructions/
und dann folgendes Bibliotheken installiert ?
3.PNG
2.PNG
1.PNG

Hi @Scotty89. Benutze Arduino unter Linux und hatte die Version 1.8.15 aus dem SNAP installiert.
Also für Linux Nutzer, arduino IDE aus 'Ubuntu Software"/SNAP desinstallieren, Version 1.8.16 downloaden und manuell installieren, danach
sudo usermod -a -G dialout $USER
pip install pyserial
pip3 install pyserial
Dann logout, login, arduino ide starten, library ArduinoOTA und Wifi installieren, Partition scheme: minimal SPIFFS nicht vergessen. Jetzt geht's, VIELEN DANK Scotty89 für deine Mühe!

So, bei mir auch über Nacht ausgefallen V2.00
Log habe ich leider nicht. Mit Ping nicht erreichbar
Mache Update auf 2.2 mit log jetzt.

hier LOG der 2.2

macht ein reboot und dann bleibt der Prozess stehen.
Ping geht!

Daten anerkannt !
Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 128
data: 0, 0, 41, 0, 45, 0, 5B, 0, 0, 0, 0, 0, 0, 56, 16, 53, 1, 0, A0, 86, 1, 0, 0, 0, 0, 0, C8, 10, 0, 0, 64, 0, F7, 3, 34, E9, 10, 0, 1, 1, 75, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 0, 1, 0, 0, 0, BD, 8, 0, 0, 0, 0, A3, 2, 40, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 4, 0, 0, CA, 19, A9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 44
data: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3C,
New Data for Analyse Complete...
Cell Voltages = 3.338V, 3.340V, 3.338V, 3.338V, 3.338V, 3.338V, 3.338V, 3.338V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V
unbekant 1 = 0, 0, 0, FF,
Average Cell Voltage = 3.339V,
Delta Cell Voltage = 0.000V,
Current Balancer = 0.000V,
unbekant 2 = 0, 0, 0, 0, 0, 0,
Battery Voltage = 26.709V,
Battery Power = 0.000W,
Charge Current = 0.000A,
Analyse = 0, 0, 55, 68, 0, 0, 0, 0
unbekant 3 = 0, 0, 0, 0, 0, 0,
Battery T1 = 6.500°C,
Battery T2 = 6.900°C,
MOS Temp = 9.100°C,
Balance_Curr = 0.000A,
unbekant 4 = 0, 0,
Percent Remain = 86%,
Capacity Remain = 86.806,
Nominal Capacity = 100.000,
Cycle Count = 0,
unbekant 5 = 0, 64, 0, 0, 10, C8,
Capacity Cycle = 1.015,
Tage: 12 Stunden: 19 Minuten: 51 Sekunden: 16
unbekant 5 = 0,
Charge on? = on,
Discharge on? = on,
unbekant 7 = 75, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 0, 1, 0, 0, 0, BD, 8, 0, 0, 0, 0, A3, 2, 40, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 4, 0, 0, CA, 19, A9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 128
data: 55, AA, EB, 90, 2, BE, C, D, A, D, A, D, A, D, A, D, A, D, A, D, A, D, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, FF, 0, 0, 0, B, D, 0, 0, 0, 0, A8, 0, A8, 0, AA, 0, AA, 0, A9, 0, A9, 0, AA, 0, AA, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 55, 68, 0, 0, 0, 0, 0, 0, 0, 0,
Daten anerkannt !
Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 128
data: 0, 0, 41, 0, 44, 0, 5B, 0, 0, 0, 0, 0, 0, 56, 16, 53, 1, 0, A0, 86, 1, 0, 0, 0, 0, 0, C8, 10, 0, 0, 64, 0, F7, 3, 35, E9, 10, 0, 1, 1, 75, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 0, 1, 0, 0, 0, BD, 8, 0, 0, 0, 0, A3, 2, 40, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 4, 0, 0, CF, 19, A9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 44
data: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 42,
New Data for Analyse Complete...
Cell Voltages = 3.340V, 3.338V, 3.338V, 3.338V, 3.338V, 3.338V, 3.338V, 3.338V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V, 0.000V
unbekant 1 = 0, 0, 0, FF,
Average Cell Voltage = 3.339V,
Delta Cell Voltage = 0.000V,
Current Balancer = 0.000V,
unbekant 2 = 0, 0, 0, 0, 0, 0,
Battery Voltage = 26.709V,
Battery Power = 0.000W,
Charge Current = 0.000A,
Analyse = 0, 0, 55, 68, 0, 0, 0, 0
unbekant 3 = 0, 0, 0, 0, 0, 0,
Battery T1 = 6.500°C,
Battery T2 = 6.800°C,
MOS Temp = 9.100°C,
Balance_Curr = 0.000A,
unbekant 4 = 0, 0,
Percent Remain = 86%,
Capacity Remain = 86.806,
Nominal Capacity = 100.000,
Cycle Count = 0,
unbekant 5 = 0, 64, 0, 0, 10, C8,
Capacity Cycle = 1.015,
Tage: 12 Stunden: 19 Minuten: 51 Sekunden: 17
unbekant 5 = 0,
Charge on? = on,
Discharge on? = on,
unbekant 7 = 75, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 0, 1, 0, 0, 0, BD, 8, 0, 0, 0, 0, A3, 2, 40, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 4, 0, 0, CF, 19, A9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 128
data: 55, AA, EB, 90, 2, BF, C, D, A, D, C, D, A, D, A, D, A, D, A, D, A, D, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, FF, 0, 0, 0, B, D, 0, 0, 0, 0, A8, 0, A8, 0, AA, 0, AA, 0, A9, 0, A9, 0, AA, 0, AA, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 56, 68, 0, 0, 0, 0, 0, 0, 0, 0,
Daten anerkannt !
Notify callback for characteristic 0000ffe1-0000-1000-8000-00805f9b34fb of data length 128
data: 0, 0, 41, 0, 45, 0, 5B, 0, 0, 0, 0, 0, 0, 56, 16, 53, 1, 0, A0, 86, 1, 0, 0, 0, 0, 0, C8, 10, 0, 0, 64, 0, F7, 3, 35, E9, 10, 0, 1, 1, 75, 6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 0, 1, 0, 0, 0, BD, 8, 0, 0, 0, 0, A3, 2, 40, 40, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 4, 0, 0, D3, 19, A9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, abort() was called at PC 0x401cc247 on core 1

ELF file SHA256: 0000000000000000

Backtrace: 0x4008f648:0x3ffcd410 0x4008f8c5:0x3ffcd430 0x401cc247:0x3ffcd450 0x401cc28e:0x3ffcd470 0x401cb963:0x3ffcd490 0x401cbc9e:0x3ffcd4b0 0x401cba01:0x3ffcd4d0 0x400d9db3:0x3ffcd4f0 0x400db8fa:0x3ffcd530 0x400d315e:0x3ffcd550 0x400dd0bc:0x3ffcd590 0x4009093a:0x3ffcd5b0

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:10944
load:0x40080400,len:6388
entry 0x400806b4
BMS Watchdog V 2.2
Booting
Connecting to WiFi ...Ready
IP address: 192.168.2.20
- Created client
MQTT Client not connected
MQTT time for reconnect
MQTT reconnected!
BLE -> Reconnecting!
BLE Advertised Device found: Name: , Address: 74:1f:88:4f:25:d5, manufacturer data: 4c0010060f1d5d18a618, txPower: 7
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 1b:4c:a0:17:0e:2b, manufacturer data: 4c00090603b9c0a802fb
BLE Advertised Device found: Name: , Address: 66:6f:29:24:8b:12, manufacturer data: 4c001005321ce421b9, txPower: 8
BLE Advertised Device found: Name: , Address: d8:6a:30:a3:32:bd, manufacturer data: 5900d86a30a332bd, serviceUUID: cba20d00-224d-11e6-9fb8-0002a5d5c51b
BLE Advertised Device found: Name: SmartBatterySense HQ2044GHUUG, Address: fc:75:ee:96:c6:3e, manufacturer data: e1021000a4a3, serviceUUID: cd54a3a4-880b-425b-b167-81ed6a15e913
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 1b:4c:a0:17:0e:2b, manufacturer data: 4c00090603b9c0a802fb
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5970547b4248135a4649141bba6d6e2a45adc676aee30
BLE Advertised Device found: Name: , Address: 04:4b:ed:a1:bf:62, manufacturer data: 4c0010050914c7358a, txPower: 12
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10202c868ae05991399b41cdd0803b883527e714248601c3c3c163218
BLE Advertised Device found: Name: , Address: 5c:bc:8d:1a:d5:48, manufacturer data: 4c0010050d18f32963, txPower: 24
BLE Advertised Device found: Name: SmartSolar HQ20464MT7S, Address: ff:de:65:11:ec:06, manufacturer data: e102100256a0, serviceUUID: cd55a056-880b-425b-b167-81ed6a15e913
BLE Advertised Device found: Name: , Address: 74:1f:88:4f:25:d5, manufacturer data: 4c0010060f1d5d18a618, txPower: 7
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5970647b4248b5c5fc816bb0cf85eff77e1a04a84e8dd
BLE Advertised Device found: Name: , Address: 76:7b:dc:a0:5b:6e, manufacturer data: 4c000f059000abcd6a10022304, txPower: 26
BLE Advertised Device found: Name: , Address: 4b:d8:fe:3e:21:bf, manufacturer data: 4c001005091c4adbae, txPower: 12
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10202c868ae05991499b41c647e512aaf44ac9c32bc0b8d267b7ade9c
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5971147b424a8be574d20daf333292b6682a4fc77c698
BLE Advertised Device found: Name: , Address: 22:68:cf:3d:09:81, manufacturer data: 4c00090603c0c0a802f9
BLE Advertised Device found: Name: SmartBatterySense HQ2044GHUUG, Address: fc:75:ee:96:c6:3e, manufacturer data: e1021000a4a3, serviceUUID: cd54a3a4-880b-425b-b167-81ed6a15e913
BLE Advertised Device found: Name: , Address: 04:4b:ed:a1:bf:62, manufacturer data: 4c0010050914c7358a, txPower: 12
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 1b:4c:a0:17:0e:2b, manufacturer data: 4c00090603b9c0a802fb
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10202c868ae05991f99b41c4c70acbb5c7ed1d555f11cf2e199110df4
BLE Advertised Device found: Name: , Address: 4b:d8:fe:3e:21:bf, manufacturer data: 4c001005091c4adbae, txPower: 12
BLE Advertised Device found: Name: , Address: d8:6a:30:a3:32:bd, manufacturer data: 5900d86a30a332bd, serviceUUID: cba20d00-224d-11e6-9fb8-0002a5d5c51b
BLE Advertised Device found: Name: , Address: 71:02:54:37:de:70, manufacturer data: 4c001005229874f550, txPower: 26
BLE Advertised Device found: Name: , Address: 22:68:cf:3d:09:81, manufacturer data: 4c00090603c0c0a802f9
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 40:0d:55:5e:a8:28, manufacturer data: 4c000f059000a8b64410022304, txPower: 26
BLE Advertised Device found: Name: , Address: 74:1f:88:4f:25:d5, manufacturer data: 4c0010060f1d5d18a618, txPower: 7
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5971547b424b0657f8ad0d294a1fe62e3e64bfbe8a3c6
BLE Advertised Device found: Name: , Address: 22:68:cf:3d:09:81, manufacturer data: 4c00090603c0c0a802f9
BLE Advertised Device found: Name: , Address: 4b:d8:fe:3e:21:bf, manufacturer data: 4c001005091c4adbae, txPower: 12
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 1b:4c:a0:17:0e:2b, manufacturer data: 4c00090603b9c0a802fb
BLE Advertised Device found: Name: , Address: 04:4b:ed:a1:bf:62, manufacturer data: 4c0010050914c7358a, txPower: 12
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10201c868ae05992d99b41c020046bc6529
BLE Advertised Device found: Name: SmartBatterySense HQ2044GHUUG, Address: fc:75:ee:96:c6:3e, manufacturer data: e1021000a4a3, serviceUUID: cd54a3a4-880b-425b-b167-81ed6a15e913
BLE Advertised Device found: Name: , Address: 74:1f:88:4f:25:d5, manufacturer data: 4c0010060f1d5d18a618, txPower: 7
BLE Advertised Device found: Name: , Address: 76:7b:dc:a0:5b:6e, manufacturer data: 4c000f059000abcd6a10022304, txPower: 26
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10202c868ae05992e99b41c9339d76b922ebf380b2beb58c6c7d52684
BLE Advertised Device found: Name: , Address: 22:68:cf:3d:09:81, manufacturer data: 4c00090603c0c0a802f9
BLE Advertised Device found: Name: , Address: 74:c4:19:0b:71:43, manufacturer data: 4c00100526142ecf6b, txPower: 26
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5972147b424264c9ae470eb1d430c5b493ee03a95afb0
BLE Advertised Device found: Name: , Address: 4b:d8:fe:3e:21:bf, manufacturer data: 4c001005091c4adbae, txPower: 12
BLE Advertised Device found: Name: SmartSolar HQ20464MT7S, Address: ff:de:65:11:ec:06, manufacturer data: e102100256a0, serviceUUID: cd55a056-880b-425b-b167-81ed6a15e913
BLE Advertised Device found: Name: , Address: 76:7b:dc:a0:5b:6e, manufacturer data: 4c000f059000abcd6a10022304, txPower: 26
BLE Advertised Device found: Name: , Address: 04:4b:ed:a1:bf:62, manufacturer data: 4c0010050914c7358a, txPower: 12
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10201c868ae05993099b41c02004c08050f
BLE Advertised Device found: Name: , Address: 22:68:cf:3d:09:81, manufacturer data: 4c00090603c0c0a802f9
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5972347b4246c48b7d91dc25a33b938a5ca427ba032a7
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: , Address: 1b:4c:a0:17:0e:2b, manufacturer data: 4c00090603b9c0a802fb
BLE Advertised Device found: Name: , Address: 74:1f:88:4f:25:d5, manufacturer data: 4c0010060f1d5d18a618, txPower: 7
BLE Advertised Device found: Name: SmartBatterySense HQ2044GHUUG, Address: fc:75:ee:96:c6:3e, manufacturer data: e1021000a4a3, serviceUUID: cd54a3a4-880b-425b-b167-81ed6a15e913
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10202c868ae05993199b41c1c3a1023e86bc2f8c554d75226e7528ffd
BLE Advertised Device found: Name: , Address: fd:ea:1a:ee:9a:d1, manufacturer data: 4c0012020001
BLE Advertised Device found: Name: , Address: 22:68:cf:3d:09:81, manufacturer data: 4c00090603c0c0a802f9
BLE Advertised Device found: Name: , Address: fc:75:ee:96:c6:3e, manufacturer data: e10201c868ae05993c99b41c02002667013a
BLE Advertised Device found: Name: , Address: ff:de:65:11:ec:06, manufacturer data: e10202c868a9d5972f47b424fb3b96b2e74830f8c80e13e53d7d7add88
BLE Advertised Device found: Name: , Address: 07:74:a8:b9:ed:9c, manufacturer data: 4c000906037cc0a802fa130c0a0471010ee4ee010401030c
BLE Advertised Device found: Name: JK-BD6A17S8P, Address: c8:47:8c:f3:5a:0d, manufacturer data: 650b88a0c8478cf35a0d, serviceUUID: 0000ffe0-0000-1000-8000-00805f9b34fb, serviceUUID: 0000fee7-0000-1000-8000-00805f9b34fb
Forming a connection to c8:47:8c:f3:5a:0d
lld_pdu_get_tx_flush_nb HCI packet count mismatch (0, 1)
- Connected to server

Hier das ganze LOG vom neu Flashen bis stehenbleiben.

Und wäre es nicht auch sinnvoll date und time zu setzen?
hier aus dem Tarce: Jun 8 2016 00:22:57
Also bei WiFi noch ein Feld für NTP?

Grüße

Hey

@JUF

Vielen Dank für den log ist sehr interessant was da bei dir passiert. Das habe ich so bei mir noch nie gesehen ...
Du kommst in eine "Lücke" rein da sich dein BMS irgendwie nicht finden lässt oder finden lassen möchte innerhalb der ersten paar Sek und meist immer an ende meines Scans ... und somit er am Ende sich verbinden wollte aber ich dann "zu schnell" einen neue Scan gestaret hatte..

ich habe nun versucht das mal abzufangen und nun sollte sich das alles gegenseitig "Blockieren"... Sprich wenn ein Device gefunden wird sollte nun auch kein weiterer Scan gestartet werden.
zudem habe ich mal versucht das BLE weiter zu optimieren in sachen Scan und Speicherfreigeben wenn was gefunden wurde.

kannst du bitte die Version 2.3 wieder mit log laufen 😉

Danke.......

@scotty89
mache ich gerne, flashe gleich mal um.
Und Morgen hänge ich den Rechner ran..

27.11
:thumbup: :thumbup:
Ist durchgelaufen, WLAN nachtschaltung sauber überstanden.

Danke

guten Morgen @JUF

kannst du mir trotzdem mal ein Log erstellen ??
Auch wenn es jetzt geht 😉 (hoffentlich ...) dann hätte ich trotzdem gern mal ein Log ....
Mich würde mal interessieren wie es jetzt bei dir aussieht 😉

Klasse Pojekt!

Ich hatte gerade gelesen, daß die Setups auf 14S und 16S verfügbar sind. Könntest du eventuell auch gleich dies als 15S mit anbieten?

Hintergedanke: arbeite zur Zeit mit einem Pylontech US3000C und bin aber noch am Überlegen ob ich dass alles erweitere.... Dann würde ich quasie ein 15S System mit diesem BMS aufbauen wollen und kann die Pylontech weiter in dem 48V Bereich fahren.... oder man könnte defeke Pylontech mit diesen BMS ausrüsten...

Grüsse

Hey,

Ich meine das ich den Code ab der 2er Version so gemacht habe das er automatisch erkennt wo werte vorhanden sind und nur diese Überträgt. Also von 8s bis 16s 😉
Sollte also schon gehen für dein use case.

guten Morgen @JUF

kannst du mir trotzdem mal ein Log erstellen ??
Auch wenn es jetzt geht 😉 (hoffentlich ...) dann hätte ich trotzdem gern mal ein Log ....
Mich würde mal interessieren wie es jetzt bei dir aussieht 😉

Hi,

also 🙁 nachdem ich den ESP zum loggen an den Rechner gehangen habe, haben wir wieder ein Ausfall.
Gestern lief es am Rechner den ganzen Tag durch.
Ping geht noch, aber BLE und MQTT stehen.

und das ganze LOG.

und jetzt bekommt der esp32 keine Verbindung mehr zum Server aufgebaut, siehe LOG

Mit der APP geht es.

HIer noch langes LOG vom Tage ohne Ausfall.

Grüße

@all
Ich habe mal noch eine ganz andere Frage.
Das JK BMS habe ich erst seit zwei Wochen und heute wird der Akku das erstmal entladen, ist halt Herbst.. 😉
Dabei fällt mir auf, das der angezeigte Strom ständig zwischen Fantasiewerten hin und her hüpft in der Anzeige sowohl der APP wie auch natürlich hier im MQTT.
Laut Messzange sind es stabile 7,2 A, im BMS sollten es -7,2A sein.

Kalibrieren in der APP auf -7.2A wird mit einem Fehler quitiert.
Irgend eine Idee?

Danke

Was hast du für eine Last dran?
Häng mal eine ohmsche Last dran und schau was dann passiert.
Die WR sind getaktet und ziehen unterschiedliche Ströme.
Beim kalibrien nur ohmsche Lasten verwenden.

@Scotty89
ist es möglich etwas im Sript einzubauen, damit wir die serielen Daten OTA logen können?

Was hast du für eine Last dran?
Häng mal eine ohmsche Last dran und schau was dann passiert.
Die WR sind getaktet und ziehen unterschiedliche Ströme.
Beim kalibrien nur ohmsche Lasten verwenden.

Hmm, technisch sicher richtig das mit der Last.
Aber 😉 das "alte"BMS JBD hat soetwas nicht gemacht.
Weiterhin wird der IQ7 hier unterhalb der MPPT Schwelle betreiben, sollte somit nicht "regeln" und die Messzange zeigt konstant 7.2A an.
Ergo Bug im JK BMS?

Grüße

Nicht ganz, kommt auf das Mess-Abtastintervall an und ob gemittelt wird.
Würde mit ohmsche last mal testen um sicher zu sein.

Nicht ganz, kommt auf das Mess-Abtastintervall an und ob gemittelt wird.
Würde mit ohmsche last mal testen um sicher zu sein.

Versuch ist es Wert.
150W Halogenlampe 24v ist bestellt.:-) echt schwer sowas bei den ganzen LED's zu Hause zu finden...