splash image is in ESPController\include\tft_splash_image.h file
you can use GitHub - sparkfun/BMPtoArray: Python script to convert a bitmap to an Arduino prog_mem array for outputting grayscale images to OLEDs. to generate your own,
That screen looks fine, watch out some don’t have the touch interface!
Thankfully the linked TFT appears to have the touch IC (U2) in the picture. @Jon_Coop make sure U2 is fitted on the TFT you received.
Only the logo is static - the text that is displayed is drawn via the code.
The logo is in the file named “logo.bmp” in the “web_src” folder. It needs to be a 4 bits per pixel BMP file.
speaking of tft is the brightness fixed? it’s very dark.
Is there much difference in turning off the led’s in the modules? Mine will be hidden in boxes.
When I connect some of my v4.21 boards they start to initialize and after a bit the D3 led is getting in red permanently and the board is getting hot … what it this means ? What could be the source of the problem ?
I did change the position on the cells and also the batteries but always got the same problem with those.
the modules need to have their bypass voltage set from the controller. The default as set when programmed would appear to be too low for the batteries they are connected to.
dan
Thanks Dan,
I’m a bit of newbi and lost, so not sure what you mean really, batteries are fully charged, how can set the by pass voltage ?
Jonny
That means the board has started to balance - the voltage in the module is lower than the current voltage of the cell, so balance begins.
Change the voltage level using the controller web interface.
No way to change that unless you alter a resistor on the board - this must be a variance in the way the boards are made - both of mine a quite readable even in bright light.
It can be that I’ve missed it somewhere, how large can the microSD card be?
Does it have to be 2GB or smaller?
64/128 GB cards are available for $1.50.
128/256MB (not GB!!) in $1.75
Obviously I don’t like to buy the small cards, but if there is a problem for the file system…
In the past many devices could not handle above 2GB.
Besides this…
I’m still trying to figure out what does the microSD card do??
My best guess it holds the flash image for cell modules to flash them with the controller board.
Besides this??
Is it optional or mandatory?
Thanks!!
Hi, I would stick to smaller cards for this purpose - 8GB or less.
Currently the SD card allows local logging and can generate log files of events that occur on the BMS.
Going forward it is also there for firmware upgrades, configuration backups and making upgrades more “slick”
Its completely optional at the moment.
2 Likes
Thank you for your clear reply!!
I’ll order some 256gb cards to see if they are really 256 or scam.
If they are real, I’m sure I can replace some older cards in security devices (who can handle over 2gb, and now have 4-16 GB cards) and use those cards for the controller.
For camera, bigger is better.
For the data logging… 2-16 GB is plenty 
Check on a PC and not the ESP32.
Hi.
ESP32 controller problem;
We have 5 banks of 14S LiIon packs.
Each of it connected as single to the new controller design is doing fine.
two connected (28 modules) are also doing fine.
but if connect 3 (42 modules) or more, the controller is doing reboots at random runtime, but mostly when coming from stableizing to running, shortly showing the magic green voltage numbers on the display.
We are using v4.21 modules, latest code on ESP32 and flashed to modules with this.
We have 3 Controllerboards with 3 ESP32, all doing the same way.
Are you using the VERY latest code? There was a change this week to help with more than 28 modules - it was rebooting at random times.
1 Like
Only ESP to flash? or modules also?
Found it.
monitor2.json