I’ve just finished connecting my second 14s to the controller and assigned each to the second bank (bank 1) and for some reason the last cell on the second bank has invalid voltage. I’ve substituted a different module for that cell and it also has the same issue. If I assign that module back to the first bank (bank 0) it reads a voltage correctly. I therefore think the issue is in the controller code rather than with the module.

Is it possible to add a setting to the MQTT choice of what to send (voltage, inttemp, exttemp,bypass)?

Should a module hang or the watchdog fires, we should reset the serial port comms to clear any potential issues and help with self recovery

In relation to stuartpittaway/diyBMSv4#31 provide a way for the controller to stay in access point mode for offline applications

Hi Stuart, in order to save one pin in wemos, you can use double reset detector library instead of D3 pin.

After deleting Wifi settings by pushing D3 at boot during a 3 seconds delay and with the "risky" of bounce buttons you finally restart ESP8266.

So there is no problem to use doble reset detector library, it resets the ESP8266, but is the same, finally you get what you want by only by pusing twice reset button. After detecting that, you can run the SoftAP module.

I hope you can implement this in future, a pin in an ESP8266 is like petrol !!!

ESP8266 version: https://github.com/datacute/DoubleResetDetector
(I have used it in several projects, works fine)

ESP8266 and ESP32 "new version for another guy": https://github.com/khoih-prog/ESP_DoubleResetDetector
(I have never use it with ESP32, but may you you prefer it for future migration to ESP32)
It even has an example of how to use it with WifiManager library. Think also that wifimanager will be ready for ESP32 soon, (it is almost). https://github.com/tzapu/WiFiManager/tree/development

Bye.

Any input? Cloned the code per the video but only the 32 compiles, the minipro always fails.

:\Users\MadDog.platformio\packages\framework-arduinoespressif8266\cores\esp8266/Arduino.h:238:21: fatal error: algorithm: No such file or directory
#include
^
In file included from src\main.cpp:38:0:
C:\Users\MadDog.platformio\packages\framework-arduinoespressif8266\cores\esp8266/Arduino.h:238:21: fatal error: algorithm: No such file or directory
#include
^
compilation terminated.
compilation terminated.
*** [.pio\build\esp8266_d1minipro\libf31\ESP8266TrueRandom\ESP8266TrueRandom.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\libb8f\ESP8266WiFi\BearSSLHelpers.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\src\PacketRequestGenerator.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\src\PacketReceiveProcessor.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\src\main.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\src\SoftAP.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\src\DIYBMSServer.cpp.o] Error 1
xtensa-lx106-elf-g++: error: CreateProcess: No such file or directory
*** [.pio\build\esp8266_d1minipro\lib0ae\Queue\cppQueue.cpp.o] Error 1
======================================================== [FAILED] Took 2.54 seconds ========================================================

Environment Status Duration

esp8266_d1minipro FAILED 00:00:02.542
=================================================== 1 failed, 0 succeeded in 00:00:02.542 ===================================================
The terminal process "C:\Users\MadDog.platformio\penv\Scripts\platformio.exe 'run', '--target', 'upload', '--environment', 'esp8266_d1minipro'" terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

#It would be great if there would be an adjustable time delay for the realy rules, so there is no endless loop in certain cases.

Now I will describe how it actually works (Firmware HysteresisRules, All rules X):
Relay default - OFF -> On the corresponding output, logic 1
Relay default - ON -> On the corresponding output, logic 0
Logically correct to do the opposite.

need a simple INVERT option on the configuration screen.

As it says in the title!

Hi
Thanks for your work

Is their a way to monitor more than 4 banks ?

Maybe 4 per controller and then a master controller to control the controllers?

WIFIMANAGER is external library and removes need to roll own WIFI configuration pages

Rule fires on bank 0 only

Hello, I have a problem with communication, the esp8266 "4MB" can not connect to cell models. All cell modules seems to work fine in standby mode the blue LED double flash every 8 second and bypass work when cells voltage exceed 4.1V. But when I connect the TX from ESP to RX in cell model all LEDs turn off in the Module and nothing happen after. I am getting this error from ESP: "The controller is having difficulty communicating with the cell monitoring modules." I have double checked the connection everything seems fine and I tried to connect only one model it did not work too. Any ideas to make it work??

If you have an ESP8266 with only 4MB flash memory the controller will enter a loop when configuring the wifi setup - it appears like the password isn't stored (its not!) so the controller attempts to go into a setup loop.

The recommended ESP8266 is the D1 Mini Pro - this has 16MB Flash by default.

buy from here https://amzn.to/2OF7Mzn

To make DIYBMS work on 4MB flash - change the option in platformio.ini

build_flags = -Wl,-Tesp8266.flash.16m15m.ld

to

build_flags = -Wl,-Tesp8266.flash.4m1m.ld

Note that future versions of the controller code may require larger flash sizes to store other information, historic logging etc.

I get this error :

Building in release mode
Compiling .pio\build\esp8266_d1minipro\src\DIYBMSServer.cpp.o
Compiling .pio\build\esp8266_d1minipro\src\PacketRequestGenerator.cpp.o
Compiling .pio\build\esp8266_d1minipro\src\SoftAP.cpp.o
Compiling .pio\build\esp8266_d1minipro\src\main.cpp.o
In file included from .pio\libdeps\esp8266_d1minipro\ESP Async WebServer\src/WebHandlerImpl.h:30:0,
                 from .pio\libdeps\esp8266_d1minipro\ESP Async WebServer\src/ESPAsyncWebServer.h:467,
                 from src\DIYBMSServer.cpp:26:
.pio\libdeps\esp8266_d1minipro\Time@src-012c38ce3e6dbfbcfc0f0e65ff7ff9e7/time.h:1:2: warning: #warning "Please include TimeLib.h, not Time.h.  Future versions will remove Time.h" [-Wcpp]
 #warning "Please include TimeLib.h, not Time.h.  Future versions will remove Time.h"
  ^
In file included from .pio\libdeps\esp8266_d1minipro\ESP Async WebServer\src/WebHandlerImpl.h:30:0,
                 from .pio\libdeps\esp8266_d1minipro\ESP Async WebServer\src/ESPAsyncWebServer.h:467,
                 from include/SoftAP.h:15,
                 from src\SoftAP.cpp:2:
.pio\libdeps\esp8266_d1minipro\Time@src-012c38ce3e6dbfbcfc0f0e65ff7ff9e7/time.h:1:2: warning: #warning "Please include TimeLib.h, not Time.h.  Future versions will remove Time.h" [-Wcpp]
 #warning "Please include TimeLib.h, not Time.h.  Future versions will remove Time.h"
  ^
Compiling .pio\build\esp8266_d1minipro\liba99\ESP8266WiFi\WiFiServer.cpp.o
Compiling .pio\build\esp8266_d1minipro\liba99\ESP8266WiFi\WiFiServerSecureAxTLS.cpp.o
Compiling .pio\build\esp8266_d1minipro\liba99\ESP8266WiFi\WiFiServerSecureBearSSL.cpp.o
Compiling .pio\build\esp8266_d1minipro\liba99\ESP8266WiFi\WiFiUdp.cpp.o
In file included from .pio\libdeps\esp8266_d1minipro\ESP Async WebServer\src/WebHandlerImpl.h:30:0,
                 from .pio\libdeps\esp8266_d1minipro\ESP Async WebServer\src/ESPAsyncWebServer.h:467,
                 from src\main.cpp:71:
.pio\libdeps\esp8266_d1minipro\Time@src-012c38ce3e6dbfbcfc0f0e65ff7ff9e7/time.h:1:2: warning: #warning "Please include TimeLib.h, not Time.h.  Future versions will remove Time.h" [-Wcpp]
 #warning "Please include TimeLib.h, not Time.h.  Future versions will remove Time.h"
  ^
In file included from src\PacketRequestGenerator.cpp:1:0:
include/PacketRequestGenerator.h:25:35: error: expected ')' before '*' token
   PacketRequestGenerator(cppQueue *requestQ) { _requestq = requestQ; }
                                   ^
include/PacketRequestGenerator.h:48:3: error: 'cppQueue' does not name a type
   cppQueue *_requestq;
   ^
src\PacketRequestGenerator.cpp: In member function 'void PacketRequestGenerator::pushPacketToQueue(PacketStruct*)':
src\PacketRequestGenerator.cpp:157:3: error: '_requestq' was not declared in this scope
   _requestq->push(_packetbuffer);
   ^
*** [.pio\build\esp8266_d1minipro\src\PacketRequestGenerator.cpp.o] Error 1
In file included from include/DIYBMSServer.h:24:0,
                 from src\DIYBMSServer.cpp:42:
include/PacketRequestGenerator.h:25:35: error: expected ')' before '*' token
   PacketRequestGenerator(cppQueue *requestQ) { _requestq = requestQ; }
                                   ^
include/PacketRequestGenerator.h:48:3: error: 'cppQueue' does not name a type
   cppQueue *_requestq;
   ^
In file included from include/DIYBMSServer.h:24:0,
                 from src\main.cpp:227:
include/PacketRequestGenerator.h:25:35: error: expected ')' before '*' token
   PacketRequestGenerator(cppQueue *requestQ) { _requestq = requestQ; }
                                   ^
include/PacketRequestGenerator.h:48:3: error: 'cppQueue' does not name a type
   cppQueue *_requestq;
   ^
src\main.cpp:232:1: error: 'cppQueue' does not name a type
 cppQueue requestQueue(sizeof(PacketStruct), 16, FIFO);
 ^
src\main.cpp:234:1: error: 'cppQueue' does not name a type
 cppQueue replyQueue(sizeof(PacketStruct), 8, FIFO);
 ^
src\main.cpp:236:54: error: 'requestQueue' was not declared in this scope
 PacketRequestGenerator prg = PacketRequestGenerator(&requestQueue);
                                                      ^
src\main.cpp: In function 'void serviceReplyQueue()':
src\main.cpp:406:11: error: 'replyQueue' was not declared in this scope
   while (!replyQueue.isEmpty())
           ^
src\main.cpp: In function 'void onPacketReceived()':
src\main.cpp:454:8: error: 'replyQueue' was not declared in this scope
   if (!replyQueue.push(&ps))
        ^
src\main.cpp: In function 'void timerTransmitCallback()':
src\main.cpp:475:7: error: 'requestQueue' was not declared in this scope
   if (requestQueue.isEmpty())
       ^
src\main.cpp:483:3: error: 'requestQueue' was not declared in this scope
   requestQueue.pop(&transmitBuffer);
   ^
src\main.cpp: In function 'void timerLazyCallback()':
src\main.cpp:1249:11: error: 'requestQueue' was not declared in this scope
       if (requestQueue.getRemainingCount() < 6)
           ^
*** [.pio\build\esp8266_d1minipro\src\main.cpp.o] Error 1
*** [.pio\build\esp8266_d1minipro\src\DIYBMSServer.cpp.o] Error 1
======================================================================================================== [FAILED] Took 5.15 seconds ========================================================================================================
Environment        Status    Duration
-----------------  --------  ------------
esp8266_d1minipro  FAILED    00:00:05.152
================================================================================================== 1 failed, 0 succeeded in 00:00:05.152 ================================================================================================== 

See attached image. I figured a pic is worth a thousand words, in this instance.

I work with cells that use different kinds of chemistry, and they have some voltage ranges that don't precisely fit into the "Lithium Ion" template of voltage ranges. e.g.)

• Lead Acid : 1.8 to 2.27 ( 2V nominal )
• LiFeMnPo (Valence) : 2.5 to 3.65-4.2V ( 3.3V nominal )
• LiPo : 3 to 4.2V hard cutoff ( 3.7V nominal )
• LiCoO2 : 3.0 to 4.2V hard cutoff ( 3.6V nominal )

As an enhancement, and since people don't tend to use mixed-chemistries ... I would like to propose an enhancement where the graph's voltage range fits the chemistry of the batteries being used and that the high/low/nominal voltages be shown across the graph as perhaps faint colored/dashed lines.

When I am monitoring LiFeMnPo cells and (top and bottom) balancing them -- the graph really never extends more than about halfway up. It's very hard to see small differences in charge between the cells when the voltage range is so small graphically.

It's even more difficult with lead acid cells for example, since the voltage range on them is only 0.47V... everything is compressed into a tiny range.

As reported in this forum post.
https://community.openenergymonitor.org/t/diybms-publishing-mqtt-to-emoncms/15557/13

ESP8266 seems to run out of power/steam after about 13 modules. Look to split into lower packet sizes/batch sizes.

Expected: When setting callibration value on cell XX then cell XX should have that callibration voltage setting

Current: If i change on cell 10 still cell 0 is changed and i can see that cell go to NA and then back in the dashboards.

This is for the 256module branch. I will take a look at hte code later on what could be wrong unless fixed before that and submitt a pull request.

I use the 4 channel relay board as recommended.
On relay channel 2 I have two rules active:

• Individual cell under voltage: 2900, on
• Pack under voltage: 42000, on
  Relay default is: off

Some times my esp controller restarts on its own. I guess some sort of overflow (many packets get los and I also have some CRC errors) or in generell some noise problem. But anyway, after the controller restarts the relay 2 gets fired up for some short time. Thus, my battery inverter gets the open circuit signal and thinks that my pack is critical low. As consequence it starts charging (from the grid). The same happens if I restart the esp on purpose (by software and by unplugin/plugin).

Maybe the esp controller doesn't calculate the total pack voltage in the first secondes correctly as it doesn't have the feedback of all modules. If this is true we need some sort of delay for the relays.

I tried changing to relay channel 3 with the same setting and the same issue happens. So I think it is not a relay board based problem.

SPIFFS has been deprecated. Please consider moving to LittleFS or other filesystems. [-Wdeprecated-declarations]

When compiling controller code

I think it'd be helpful and reduce some confusion, at least on my part, to have a controller code version number somewhere on the web interface page.

Is there any sourcecode available for the current sensing? You you have any plans for that? Can I help?

Hi @stuartpittaway ,
Here are my suggestions about extending the rules functionality (move here from the community on your request).

Long story short:

1. Add "Individual cell module over temperature (internal) °C"
2. Add second "Individual cell over temperature (external) °C" for High and High High signals
3. "Pack under voltage (mV)" - divide into 2 set points: under voltage + recover set point
4. "Pack over voltage (mV)" - divide into 2 set points: over voltage + recover set point

Detailed description with examples:

1. Add an internal over temperature rule to start cooling fan for the bms. Example: cells modules are installed separately from cells, all together, lets say in a box. With such installation it is easy to organize a cooling for them to make top balancing more efficient for large packs. Also in such case the interface/communication wires are as short as possible to minimize interference. A rule to start cooling would be nice to have in this case.

2. Individual cell over temperature (external) °C - it would be great to have this rule 2 times to configure HIGH and HIGH HIGH limits. HIGH limit would be used to switch on cooling fans in the battery compartment and HIGH HIGH - as a main trip signal to disconnect the battery from all devices.

3. Pack under voltage. The most reasonable use for this rule is disconnecting and connecting back to the battery inverters. I saw somebody already suggested to put a time delay for rules, but I would like to extend this subject. Normally for such application 2 set points are used: switch off set point and recover set point. Time delay would also be great (to cover start loads) but not enough, from my point of view. Example: 14s battery + grid tie inverter with limiter - the inverter itself will normally have a battery discharge protection, however it make no sense to “dry run” an inverter if the battery is discharged, because it will only consume power from grid (yes, not much, but still); so, it would be nice to switch off the inverter lets say at 44V and connect it back only after battery is recharged to lets say 49V. Using this rule “as it is” with only one set point make for me little sense, because it would be jumping back and forth all the time.

4. Pack over voltage (mV) - similar thing as case 3 but for burning the excess energy (to heat the water for example). We can switch on the relay to turn on the water heater at Lets say 57,5V and switch it off at 56V. A time delay would also be nice here.

It would be nice to have these features in new releases.
Thanks

Found a software limitation “Pack over voltage (mV)” 65500. I have 20 cells 18650 = 84000 mV
When you enter a larger value, it writes what has been saved, when the page is refreshed, it writes other different numbers.

https://community.openenergymonitor.org/t/diybms-v4/11292/2528?u=stuart

Dear all,

I have been running with the DIYBMS for 3 weeks now. Running flawless, till I did a configuration change that crashed every single one of my 14 cell modules which began to go smoking hot.

Running the current release version of the code.

I wanted to balance my power wall down to 3.8v/cell to do some charge testing with my solar tomorrow. The stack was at 3.9v/cell. Here is what happened.

1. I updated the global settings to 65 Celsius, 3800 mV,
2. drank a cup of coffee,
3. went down to my power wall, and noticed that the balance indicator LEDs were all solid on. Not “PID flickering”
4. pulled up the web interface. Each module was at 120 Celsius and rising.
5. in a panic, increased the bypass voltage to 4100 mV and did a global update.
6. all cell modules cut out now that the bypass voltage was set higher than what the cell voltage. The boards began to cool. LED went off for every single module.

This was reproducible. Each time I changed back the bypass voltage to any value below the cell voltage, the PID did not kick in. The LEDs just went solid on and the dump resistors was driven constantly on.

Everything else appeared normal. I could read out the configuration of each module. No bogus values, no bad data packages.

It was first when I physically unplugged and thus rebooted each cell module that I could get rid of the dangerous and odd behavior. After having cycled power to all 14 modules I could set the global parameters to 65 Celsius and 3800 mV and all cell modules have since operates as intended.

I do not dare to keep the system on without active supervision now. Has anything like this been seen/reported before?

PS. I am using the 4mb WEMOS on the ESPController. Do not know if this can be related to my issues.

When using 256modules branch the softap doesnt work properly. It crashes the ESP after 2 seconds. I tried both the master branch right now that works fine and boots up and start debugging messages properly meanwhile 256 modules look like this:

As can bee seen it crashes and doesnt show the AP.

Also why is the debugging ofsetted on the 256modules version compare to the master that looks nice?

Currently we read the voltage without looking into if the balancing is running.
When balancing there is a significant voltage drop over the wires. Either we need to calculate this during voltage reading or we should just stop the balancing during this time

The drop itself do trigger the pwm to engage rather early. (I have to dig into the code a bit more to understand how it all works)

I could probably take a look but the code for the cell modules arent what im used to (Im not a coder) :)

Brilliant BMS system and I am definitely going to build and use the v4 for an upcoming DIY electric boat conversion to a 16s 300Ah LIFEPO4 powered system.

I am only missing a rule to switch off the (solar) charger when a cell or pack temperature is below 0 celcius (<5 celcius is safer) as a lithium battery will be permanently damaged when charged in low temperature state.

Timer2 is used to drive the balancing circuit via PWM.

After the first cycle of balancing, the PWM appears to not enable fully and causes the balance to not fully work.

It would be nice to have option to make "force balance", for which you would enter mV value of biggest difference, and than modules would balance themselves regardless that cell is not in overvoltage state.
This would help in case that you have one cell with lower voltage, and not getting them all to "charge state".
Thank you.

Hi Stuart,

Can you extend the MQTT messages for the whole pack/bank?

• pack voltage
• relay status
• voltage range

Another wish, if possible, can you make a field for the cell modules to give the pack individual names?

What happens:
The current code keep sending same data even when comms is down or stale.

Expected:
It should revert to 0 values if not valid data in them or just not send the data at all.

Perhaps do something like this: (main.cpp)
if ((!mysettings.mqtt_enabled && !mqttClient.connected()) || receiveProc.HasCommsTimedOut())

Hi!
I try to get this debug code up running, but after cloning the git, the compiler ask for some missing libs: sdkconfig.h, freertos/semphr.h, esp_task_wdt.h. I tried to install the libs manually, without success.

In file included from .pio\libdeps\nodemcuv2\AsyncTCP_ID1826\src\AsyncTCP.cpp:24:0: .pio\libdeps\nodemcuv2\AsyncTCP_ID1826\src\AsyncTCP.h:26:23: fatal error: sdkconfig.h: No such file or directory

How can I install the right libs?
Thanks!

Hi,
I have been using your bms for a while and I noticed that when undervoltage or overvoltage events are triggered bms sends signal to turn off load/charging but as soon as device turns off voltage on the cells bounces back a little and bms sends signal to turn on the device.

It would be great if You could add some sort of hysteresis, so when discharging the cells voltage reaches for example 3V/cell bms sends signal to turn off discharging device, but turning it back on would be possible when cells reach for example 3.2V/cell. Of course overvoltage situation working on the same principle.

It would eliminate constant turning on and off
of peripheral devices.

Hi,
I'm trying to compile the ESPController software but am getting errors regarding git from the file buildscript_versioning.py.
When compiling from the downloaded Zip:
"fatal: Not a git repository (or any of the parent directories) .git"
When compiling from a cloned directory:
"fatal: your current branch 'master' does not have any commits yet"
Why does it want me to set up a git repository?

Feel free to delete this if it's off-topic, however i am wondering if the ESP used in the controller board can have Mongoose OS loaded with the default diybmsv4 code working in tandem.

My reason, i have the diybms setup and working, and i turned a raspberrypi into an MQTT Broker. I also have a Flask-based Apache webpage that i have turned into a webapp. Currently it uses a 433MHz communication system. I want to reconfigure the webpage/webapp to communicate with the diybms main console. The reason? I have a home automation setup that allows me to control and monitor my home and workspace remotely. I already have the UI and homeautomation setup, i'd simply like to integrate the diybms into the system.

Any cell modules moved away from bank 0 do not initiate balance mode. Red LED does not light and resistors do not heat up. This happened on banks 1, 2, and 3. I lowered global bypass voltage threshold below my lowest cell, save settings and cells only on bank 0 did what they should.

Just as a quicker reference from https://community.openenergymonitor.org/t/diybms-v4/11292/110
If your controller arrives with PCF8574T from JLCPCB and not PCF8574AT it needs the code to be changed In Main.cpp:

//PCF857x pcf8574 (0x38, &Wire) ; //For AT version
PCF857x pcf8574 (0x20, &Wire) ; //For T version

A lot of inverters (Goodwe, Growatt, SMA, Sungrow, etc) have the capability to communicate with a battery over CAN. I even suspect they refuse to function without communication being present. Maybe it would be a nice addition to support communication over CAN replicating the LG RESU message protocol (best supported in the industry it seems).

I have 3 banks (14s) attached to my controller. When watching the monitor page from the web browser, periodically (when charging mostly) bank 0 will disappear from the display but bank 1 and 2 will remain. On the next refresh it will reappear but it will have lost it's min and max voltage values. I've attached a couple of screen shots showing the data missing from the monitor.json file and when a bank is missing (not that banks are not renumbered, bank 1 and 2 remain as 1 and 2 not changed to 0 and 1).

Enable BOD detection and also write EEPROM values multiple times to prevent loss of EEPROM contents in BOD conditions

hi stuartpittaway
i dont have lm4040, can i just leave it blank? and just change this line to 1024.0?
//2mV per ADC resolution
myConfig.mVPerADC = 2.0; //2048.0/1024.0;

Since recent release only first 10 modules data are sent over MQTT

Hi,

sad to see you moved away from open licenses and are now using a more restrictive one - especially since "non-commercial" isn't really a well defined concept and a lot of uses might be considered "commercial". As such things like paying companies to fabricate boards instead of etching them at home, using boards to run a solar system connected to the grid (some countries require owners to start a "company" to get the necessary permits) or even talking about the system on websites containing ads might put users into a position where lawyers might write nasty letters. It would be great if you could add a little clarification on where your interpretation of "NC" starts and what uses are explicitly allowed.

Global Settings - Bypass threshold mV - does not work for other banks, except 0
firmware: hysteresisrules

The hostname of the DIYBMS controller should be set to diyBMS_ESP8266 but it is not.

Seems to relate to ESP8266 bug esp8266/Arduino#2826

I am only missing a rule to switch off the (solar) charger when a cell or pack temperature is below 0 celcius (<5 celsius is safer) as a lithium battery will be permanently damaged when charged in low temperature state.

Hi,
I ran into some problems when programming my D1 Mini:
First i had to remove the line "upload_speed=921600". Otherwise the upload would fail.
Then after flashing i can connect to the Wifi but only see an empty page (http://192.168.4.1/softap.htm).
What's wrong here?