Documentation issues…
Quote from mikes on August 12, 2026, 8:05 pmThanks for your efforts, I can tell you put a LOT of work into the WiFi SmartBMS DATA EXTRACTOR. I just got a NodeMCU OLED so I can play around with it. No wiring done yet, but I wanted to program it to take a look.
Trying to program by following the instructions in “ScanLabs BMS data extractor for JK and DALY BMS – The Bible v 3.6.1_01.pdf”, page 45.
There are some problems with the instructions.
First, there is no “SolarEnergyECUMulti-x.x.x.mklittlefs” in “SolarEnergyECUMulti-3.6.1.zip”. There is also no mklittlefs in the post with 3.6.0. Using “SolarEnergyECUMulti.mklittlefs-3.5.2.bin” seems to work (it boots), but it’s not clear if that’s correct and there won’t be issues later. Should “web-3.6.0.all” be uploaded after?
Also, the instructions say to program mklittlefs at offset 0x20000. “SolarEnergyECUMulti.JK-OLED-3.6.1.bin” is 987920 bytes, which would place the end at 0xF130F. So programming mklittlefs @0x20000 like the instructions say overwrites the end of it. It should be 0x200000, as shown in the picture on page 45.
To connect to the web server, 192.168.0.1 doesn’t work. An address in 8.8.8.0/24 is assigned, with 8.8.8.8 as the default gateway. The web server is accessed at 8.8.8.8. You really should not use a public IP like 8.8.8.8. 192.168.0.1 is OK, but commonly used. Something less common, like 172.31.255.0/24 and 172.31.255.1 would be better.
HOW DO YOU CHANGE THE DEFAULT USER/PASS (admin/admin!)???
Thanks for your efforts, I can tell you put a LOT of work into the WiFi SmartBMS DATA EXTRACTOR. I just got a NodeMCU OLED so I can play around with it. No wiring done yet, but I wanted to program it to take a look.
Trying to program by following the instructions in “ScanLabs BMS data extractor for JK and DALY BMS – The Bible v 3.6.1_01.pdf”, page 45.
There are some problems with the instructions.
First, there is no “SolarEnergyECUMulti-x.x.x.mklittlefs” in “SolarEnergyECUMulti-3.6.1.zip”. There is also no mklittlefs in the post with 3.6.0. Using “SolarEnergyECUMulti.mklittlefs-3.5.2.bin” seems to work (it boots), but it’s not clear if that’s correct and there won’t be issues later. Should “web-3.6.0.all” be uploaded after?
Also, the instructions say to program mklittlefs at offset 0x20000. “SolarEnergyECUMulti.JK-OLED-3.6.1.bin” is 987920 bytes, which would place the end at 0xF130F. So programming mklittlefs @0x20000 like the instructions say overwrites the end of it. It should be 0x200000, as shown in the picture on page 45.
To connect to the web server, 192.168.0.1 doesn’t work. An address in 8.8.8.0/24 is assigned, with 8.8.8.8 as the default gateway. The web server is accessed at 8.8.8.8. You really should not use a public IP like 8.8.8.8. 192.168.0.1 is OK, but commonly used. Something less common, like 172.31.255.0/24 and 172.31.255.1 would be better.
HOW DO YOU CHANGE THE DEFAULT USER/PASS (admin/admin!)???
Quote from ScanLabs on August 13, 2026, 2:41 pmCiao Mikes,
Thanks for challenging and testing the project đ1-
First, there is no âSolarEnergyECUMulti-x.x.x.mklittlefsâ in âSolarEnergyECUMulti-3.6.1.zipâ. There is also no mklittlefs in the post with 3.6.0. Using âSolarEnergyECUMulti.mklittlefs-3.5.2.binâ seems to work (it boots), but itâs not clear if thatâs correct and there wonât be issues later. Should âweb-3.6.0.allâ be uploaded after?You are definetively right â script generating the multiple files needed failed but I did not notice.
Indeed , release 3.6.2 is already deployed ( but not shared ) where I already fix the script and the missing file â I will go directly to release 3.6.3 where you will have the mklittlefs file.
The good news is you donât need it anylonger ⌠since a while indeed.
In fact when the SW starts for the first time, it reaches the server looking for new fw releases, whether the filesystem is empy , the dongle simply download all the webpages and extra files.
So in short you will have extaclty the same filesystem after the first run.
I will fix the manual as well.2-
Also, the instructions say to program mklittlefs at offset 0x20000. âSolarEnergyECUMulti.JK-OLED-3.6.1.binâ is 987920 bytes, which would place the end at 0xF130F. So programming mklittlefs @0x20000 like the instructions say overwrites the end of it. It should be 0x200000, as shown in the picture on page 45.ooohh YES 0x200000 â
The 4MB flash is split into 2 parts, 2MB firmware image, 2MB filesystem. On 2MB fw image, I need to accomodate current fw image and backup/new fw â so max fw image size is 1MB ⌠we are very close to the limit đ3-
To connect to the web server, 192.168.0.1 doesnât work. An address in 8.8.8.0/24 is assigned, with 8.8.8.8 as the default gateway. The web server is accessed at 8.8.8.8. You really should not use a public IP like 8.8.8.8. 192.168.0.1 is OK, but commonly used. Something less common, like 172.31.255.0/24 and 172.31.255.1 would be better.I donât like it as well , but it is the dirty&easiest way to have a captive portal working 95% of the cases.
8.8.8.8 is used only once after Restore to factory, after that, 192.168.0.1 is used as default IP address in AP mode.ScanLabs
Ciao Mikes,
Thanks for challenging and testing the project đ
1-
First, there is no âSolarEnergyECUMulti-x.x.x.mklittlefsâ in âSolarEnergyECUMulti-3.6.1.zipâ. There is also no mklittlefs in the post with 3.6.0. Using âSolarEnergyECUMulti.mklittlefs-3.5.2.binâ seems to work (it boots), but itâs not clear if thatâs correct and there wonât be issues later. Should âweb-3.6.0.allâ be uploaded after?
You are definetively right â script generating the multiple files needed failed but I did not notice.
Indeed , release 3.6.2 is already deployed ( but not shared ) where I already fix the script and the missing file â I will go directly to release 3.6.3 where you will have the mklittlefs file.
The good news is you donât need it anylonger ⌠since a while indeed.
In fact when the SW starts for the first time, it reaches the server looking for new fw releases, whether the filesystem is empy , the dongle simply download all the webpages and extra files.
So in short you will have extaclty the same filesystem after the first run.
I will fix the manual as well.
2-
Also, the instructions say to program mklittlefs at offset 0x20000. âSolarEnergyECUMulti.JK-OLED-3.6.1.binâ is 987920 bytes, which would place the end at 0xF130F. So programming mklittlefs @0x20000 like the instructions say overwrites the end of it. It should be 0x200000, as shown in the picture on page 45.
ooohh YES 0x200000 â
The 4MB flash is split into 2 parts, 2MB firmware image, 2MB filesystem. On 2MB fw image, I need to accomodate current fw image and backup/new fw â so max fw image size is 1MB ⌠we are very close to the limit đ
3-
To connect to the web server, 192.168.0.1 doesnât work. An address in 8.8.8.0/24 is assigned, with 8.8.8.8 as the default gateway. The web server is accessed at 8.8.8.8. You really should not use a public IP like 8.8.8.8. 192.168.0.1 is OK, but commonly used. Something less common, like 172.31.255.0/24 and 172.31.255.1 would be better.
I donât like it as well , but it is the dirty&easiest way to have a captive portal working 95% of the cases.
8.8.8.8 is used only once after Restore to factory, after that, 192.168.0.1 is used as default IP address in AP mode.
ScanLabs