I made my own firmware from the new sources and found a few bugs.
We have two Axpert Max hanging at home and one in the holiday home.
I also use “Solar Assistant” to control and set various functions so that I don’t always have to run to the inverter.
The AXPERT MAX inverter is set to priority solar/battery/utility
Charger source priority is set to Solar and Utility simultaneously
However, the BMS seems to prevent the battery from charging.
Example:
1200W are needed in the house, 2900 are currently available from the PV modules. But only 50w is charged into the battery.
The BMS then shows -0.02A and a few watts. I then used a measuring terminal to determine whether current was flowing. That was not the case.
Solar Assistant also displayed very incorrect voltage and SOC. In “emulated BMS” mode and also with “use inverter values”.
Serial logging didn't really work either, it just resulted in garbage data.
Then I flashed the firmware from 6/30/23 back onto the controller and immediately after restarting the BMS everything was as you would expect.
A friend has a similar system with an Axpert Max, 15KWh LFP battery and a diybms 4.6
He experienced exactly the same thing. After the firmware downgrade, everything was as it should be.
The colleague also has an EEL BMS (Seplos BMS) that he can activate for testing. This is then connected to the inverter via RS485 and also uses the pylontech protocol.
The inverter behaves differently, changes mode less often, etc.
Something got stuck functionally when changing from CAN to RS484.
Unfortunately I cannot log the EEL BMS for you.
I have a CANUSB adapter that I bought for Solar Assistant.
When I flash the BMS with the CANBUS firmware, the DIYBMS is recognized by Solar Assistant as a Pylontech battery. If that helps you, I would lend you the adapter for logging. There are no problems with shipping within the EU.
If you need help I can also log something here for you. I have a test system that I can "play" with.
Just say what would be helpful for you.
I made my own firmware from the new sources and found a few bugs. We have two Axpert Max hanging at home and one in the holiday home. I also use “Solar Assistant” to control and set various functions so that I don’t always have to run to the inverter.
The AXPERT MAX inverter is set to priority solar/battery/utility Charger source priority is set to Solar and Utility simultaneously However, the BMS seems to prevent the battery from charging.
Example: 1200W are needed in the house, 2900 are currently available from the PV modules. But only 50w is charged into the battery. The BMS then shows -0.02A and a few watts. I then used a measuring terminal to determine whether current was flowing. That was not the case. Solar Assistant also displayed very incorrect voltage and SOC. In “emulated BMS” mode and also with “use inverter values”. Serial logging didn't really work either, it just resulted in garbage data.
Then I flashed the firmware from 6/30/23 back onto the controller and immediately after restarting the BMS everything was as you would expect. A friend has a similar system with an Axpert Max, 15KWh LFP battery and a diybms 4.6 He experienced exactly the same thing. After the firmware downgrade, everything was as it should be. The colleague also has an EEL BMS (Seplos BMS) that he can activate for testing. This is then connected to the inverter via RS485 and also uses the pylontech protocol. The inverter behaves differently, changes mode less often, etc. Something got stuck functionally when changing from CAN to RS484. Unfortunately I cannot log the EEL BMS for you. I have a CANUSB adapter that I bought for Solar Assistant. When I flash the BMS with the CANBUS firmware, the DIYBMS is recognized by Solar Assistant as a Pylontech battery. If that helps you, I would lend you the adapter for logging. There are no problems with shipping within the EU.
If you need help I can also log something here for you. I have a test system that I can "play" with. Just say what would be helpful for you.