What Deye BMS errors can be stopping inverter?

[denveronly]

Hi all, its been several weeks i am using ESP32 code of Uksa007 to convert JK to Pylontech
Today i tried to make some test failure to see what can shut the inverter from working on errored BMS

1. i tried setting discharge temperature to 35 deg C and heat up my sensor so it reaches the temperature point.
   BMS was giving me the error
   Inverter i saw an error code like this, with a 0x0040
   ESP32 JK_Bitmask error was 2 then 4 i guess, JK Error never changed
   
   Inverter kept working (well it was draining the second battery which doesnt have communication with it, until the test battery got recovered after temperature drop but i guess it was supposed to be stopped)
2. i Tried to change number of cells in JK BMS app, so 14 was edited to 13 with an error
   Inverter got none 0x0000
3. i Tried to change number of cells in JK BMS app, so 14 was edited to 15 with an error
   Inverter got none 0x0000

If i have my BMS disconnected from ESP it shuts the inverter down. with BMS Err.

So the question is : Are the BMS errors suppose to stop the inverter? If yes, maybe there are general errors (like cell overvoltage ie) and secondary errors that doesnt affect normal work and inverter just in wait mode until it gets fine?

[Eumobong]

The code is for single inverter, single battery/dms. Your test scenerio didn't adhere to the above. Test with one battery connected. I don't think it's a nice idea to shutdown the inverter on bms error.

It looks like the code relies on the inverter to take the decision to abort changing/discharging or shutdown when an error occur. However, in BMS communication, I think the bms is expected to instruct the inverter what it should do when error occur.
I would expect it to at least:
stop charging on over voltage,
stop discharging on under voltage,
stop charging or discharging in over temp or under temp,

[Uksa007]

The photo shows the alarm with 0A battery current, how was it draining the other battery?
Also not sure what alarm 0x0040 is, that doesn't seem to map to the CAN alams, Over temp is (0x02 or 0x8 both 0x0A)

Wrong number of cells is not likely to generate an alarm.
CAN protocol Alarms are:
over/under voltage
over/under temp
over current discharge/change

[Uksa007]

I have a beta version for Patreon Beta testers members, that has improved alarm handling
https://www.patreon.com/posts/83113209

• V 1.16

Improved Alarm handling, all alarms will set change/discharge A to 0, set Charging status to Alarm
Captive portal Wifi setup
Web server for local management
Fix inconsistent spaces (code improvement)
Request force charge from mains if battery low, eg if no charge due to weather, snow etc.
Added cycles offset and send correct charge cycles with offset to HA
Send battery SOH to HA including cycles offset when calculating
Add battery protocol selection type for pylon for better compatibility
Stop sending CAN messages if no response (major improvement), code will detect when no inverter/not responding and stop sending CAN messages that resulted in WDT reboot issues. Code should now run without any issues if inverter is not connected.
Deye inverter improvements for better support of this inverter.
Fix daily reboot if HA is not connected.

[denveronly]

logs_jk2_logs (3).txt
logs_jk2_logs (4).txt

(3) is Master+Slave = temp alarm on master
(4) is Master+No Slave = temp alarm on master

[Uksa007]

Please test the Deye firmware provided.