mt-mrx
commented
8 months ago Ah, I just figured out how to recreate the issue I'm seeing. It has nothing to do with bad communication between the BMS and the Wemos.
I have set my BMS to got to sleep after 5 minutes. I'm only waking it up during the day when there is even a chance to charge it, so if I have a certain amount of power being exported to the grid. If there is a cloudy day and the power changes quickly it's being woken up goes to sleep and is being woken up again.
So, I can recreate the issue, even at night, I have to wait for the BMS to go to sleep and then wake it. When I wake it, the first data that's being sent reports the wrong values.
While the BMS is sleeping I see the "correct"/"old" data in the livejson and MQTT output, so the state and values from when it went to sleep.
Below you see a log and can and see the timing of the wrong messages, I used MQTT to send the Wake_BMS signal:
$ mosquitto_sub -i "clientidsub" -u user -P pw -h brokerip -p 1883 -t 'dalybms/#' -v | ts "%H:%M:%.S" | grep -E "Pack_Status|Pack_Current|Pack_Voltage|Wake_BMS"
22:31:21.113858 dalybms/Pack_Voltage 46.2
22:31:21.114120 dalybms/Pack_Current 0.0
22:31:21.117623 dalybms/Pack_Status Offline
22:32:01.702101 dalybms/Pack_Voltage 46.2
22:32:01.702578 dalybms/Pack_Current 0.0
22:32:01.705811 dalybms/Pack_Status Offline
22:32:07.351963 dalybms/Device_Control/Wake_BMS true
22:32:08.673267 dalybms/Device_Control/Wake_BMS false
22:32:11.963706 dalybms/Pack_Voltage 0.0
22:32:11.964110 dalybms/Pack_Current -3000.0
22:32:11.970878 dalybms/Pack_Status Stationary
22:32:43.908161 dalybms/Pack_Voltage 46.2
22:32:43.908523 dalybms/Pack_Current 0.0
22:32:43.911404 dalybms/Pack_Status Stationary
22:33:15.907124 dalybms/Pack_Voltage 46.2
22:33:15.907873 dalybms/Pack_Current 0.0
22:33:15.916410 dalybms/Pack_Status Stationary
...
22:36:27.662153 dalybms/Pack_Voltage 46.2
22:36:27.662498 dalybms/Pack_Current 0.0
22:36:27.668592 dalybms/Pack_Status Stationary
22:36:59.645788 dalybms/Pack_Voltage 46.2
22:36:59.646747 dalybms/Pack_Current 0.0
22:36:59.658206 dalybms/Pack_Status Stationary
22:37:41.615937 dalybms/Pack_Voltage 46.2
22:37:41.616742 dalybms/Pack_Current 0.0
22:37:41.631586 dalybms/Pack_Status Offline
22:38:22.204224 dalybms/Pack_Voltage 46.2
22:38:22.204480 dalybms/Pack_Current 0.0
22:38:22.208980 dalybms/Pack_Status Offline
22:39:02.797606 dalybms/Pack_Voltage 46.2
22:39:02.798488 dalybms/Pack_Current 0.0
22:39:02.803226 dalybms/Pack_Status Offline
22:39:10.636293 dalybms/Device_Control/Wake_BMS true
22:39:11.038449 dalybms/Device_Control/Wake_BMS false
22:39:14.219997 dalybms/Pack_Voltage 0.0
22:39:14.220526 dalybms/Pack_Current -3000.0
22:39:14.223820 dalybms/Pack_Status Stationary
22:39:46.193061 dalybms/Pack_Voltage 46.1
22:39:46.193258 dalybms/Pack_Current 0.0
22:39:46.195899 dalybms/Pack_Status Stationary
softwarecrash
Is there an existing issue for this?
Used Hardware?
Wemos D1 Mini
What happened?
Since the update to 2.12.0 (debug) I'm seeing unexpected "Pack_DischargeFET" = false messages, "Pack_Current" values of exactly "-3000", "Pack_SOC" = 0, "Pack_Voltage" = 0 and "Pack_Remaining_Ah" = 0 . (Not sure if there are more parameters reporting (wrong) readings)
During the day, when I have surplus PV energy, I keep the BMS awake, to charge it with the surplus energy, by sending every 30s a "Device_Control/Wake_BMS" message.
As already discussed in #132 my BMS sometimes isn't responsive enough and I see the "Pack_Status" changing from "Stationary" to "Offline" and during the next Wake_BMS back to "Stationary". According to my data logging (influxdb) I see the following timestamps:
I'm collecting all MQTT messages coming in in a 2s window and write it with the same timestamp into the DB. I'm converting "Offline" to -1 and "Stationary" to 0. Whenever the "Pack_Status" is "Stationary", "Charge" or "Discharge" I'm writing the data to the DB, otherwise I'm writing ONLY the "Pack_Status" and "Alive".
So to me it looks like the "wrong" data is sent when the pack comes back online or better that's when that data is definitely sent, it could be that it already appears when the "Pack_Status" changes to "Offline" but I'm not writing "Offline" data to the DB, see explanation above.
I have not seen this behavior with firmware version 2.11.0 (and earlier).
If I remember correctly when there are BMS read/communication errors the previous values were reused and not reset. Did anything change in that regard?
Screenshots / Fotos
I'm still using the exact same setup as in #132
Steps To Reproduce
Cannot reproduce it, looks like it happens when the communication between the BMS and the Wemos is unreliable and the BMS is not responding to the Wemos for a while.
Version
2.x.x and above
Relevant livejson output
Which BMS is connected?
Lifepo4 15S 48V 60A UART / Bluetooth
What browsers are you seeing the problem on?
no Issue with the Browser or WebUI