I changed the controller from 4.2 to 4.4 with new ESP32 and latest software.
Github release 44.
I changed because I want to use the dipswitches and put it under a clear cover.
I managed to program it. The AP mode did not appear. ( Or I was to stupid… )
But managed to connect it via putty to my WIFI.
Good news: The CAN BUS did immediately work. I had not to change anything.
The Victron did recognize it.
Then I set all the settings like in the controller 4.2.
Got no connection to the modules.
Then I found a new setting: inter-packet gap.
Set it to 2000. Then I had communication to the modules.
Then I wanted to set the rules.
But here I coudnt change any settings.
When I tried to change anything I got the message: Failed to save settings.
The overvoltage is set in the Rules to 33600.
It seems this triggers an overvoltage warning through CAN to the Victron.
And when this is triggert there cant be performed any changes in Rules.
I took the controller off from the system and restarted.
As soon there is no battery and no Victron on the controller all settings are settable.
And when I set the language to german I have two times settings for Timer 1 and Timer 2.
The ESP with SW from 4.2 can’t work.
I tried it. No function.
Expect the reasons are diffrend chips on 4.4.
The SW I use on 4.4 is the last release from GitHub.
The solution that works for me is:
Setting Rules before connecting to Victron.
Then there is no Alarm and Rules can be changed.
The strange thing is:
I do not use any relays in the moment.
So there is no reason to block anything.
But when there is an OV alarm triggert by Rules the Victron does not charge.
Although in Victron settings were set max V to 56.5V.
By the way: it is interesting which SW version is the latest for controller V4.2 with the older chipset.
I have not yet seen that there is an extra SW for the revision 4.4.
I used the last software release 44 on my ESP32 with the board diyBMSv4ESP32 Rev. 4.2
Here is an excerpt from “about”:
Processor: ESP32
Version: 4d240d0120df636fbe0bf136d1db2aa3e0a35694
Compiled: 2022-09-06T10:32:56.505Z
Language: en
SDK Version:v4.4.1-1-gb8050b365e
Min free Heap:74940
Free heap:131248
Heap size:294096
Does this help you?
Do you have any CAN errors or drops?
The picture of the rules looks funny. 2x Timer 1 and 2x Timer 2 that is definitely not so with me.
Can you flash for software once again on the ESP.
With what software you actually flashes?
is there an extra Erase flag that I would try.
First delete the whole flash from ESP then program.
Yes okay, in your picture from above Timer1 is green.
This timer should actually be “Pack over Voltage”,
you have 33,6V in there. That seems to be too little with a 16S battery.
Max would be 16 x 3,65 = 58,4V
What is the current voltage of the battery pack?
Change it to english and restart the controller again
Set the voltage higher!
Chris, please read my topic.
It’s all already done.
But the bug is:
You put all together and start the system.
Default setting for alarms under rules is 33600mV.
The battery is a 16S. Means when it’s empty it has still 40000mV.
So the OV is immediately triggert.
The the problem: you can’t change anything because the alarm is triggert.
The only solution: put of the CAN an the data cables.
The the system does not measure any voltage.
No alarm. Now you can change the values in rules.
Then you connect the cables and it is running.
But I’m sure it can’t be the in the sense of the designer that you can’t adjust
the values when you first start the system.
