Hi everyone, looking for some advice from the community. I have the Watchmon 4 with 2 x CellMate K9 units connected to 32 300Ah cells running 16S2P config for a 48V setup connected to 2 x Deye SUN-8K-SG05LP1-AU units in parallel configuration running my completely off-Grid Home.
The Deye inverters are new to my setup (1.5 weeks) and i used to use the Batteries and BMS with a pair of paralleled Sako inverters that whilst had a BMS port, I was advised by the manufacturer that it was not supported, so i never had the BMS Canbus connected to the old SAKO’s.
The Deye’s support Canbus, so all good there, i have them set to Pylon and am using the Pylon LV protocol setting in the Watchmon setup as this was what was suggested in the official Wiki.
When i connect the inverter to the BMS, all seems good, i have data present at the inverter and it appears to communicate charging values and temp, etc.
the problem is after 24-48hrs with the BMS connected to the inverter via the CANBUS, i get an error F14 DC_over_current and the inverters shutdown all power to my house. If i run the inverters not connected to the BMS, I can go all week, no disruption. Also after the first error and shutdown, if i leave the BMS connected, same error within minutes. I have to wait a day or so to reconnect and run for 24hrs before error. I can see the inverter logs, but not the Batrium logs to see what the watchmon told the inverter to initiate an error state shutdown.
Any idea why the inverter thinks it is over current?
Thanks for any helpl you can give.
Deye is having a lot of issues with its system behaviour and the CAN protocols. From Batrium side all relevant BMS data is sent via CAN but the Deye is not working stable and efficient. That is what I can approve and say with the experience of high voltage variant SG01HP3.
So, I contacted email support and have been emailing with James at Batrium and he advised the following:
- Deye inverters don’t like being sent a zero current limit for change or discharge. You need to turn on the setting “Remote Amp - Off = Non-Zero” on both the Control > Charging >Extra page and the Control > Discharging > Extra page.
doing this seems to have stabilised my setup and I have not had a shutdown in 4 days, fingers crossed this continues.
Thanks to James and the Batrium email support team for helping with this setting, I thought I would post it here as i could not find this documented anywhere in the Batrium Wiki.
Good day. Please show how deye behaves with these parameters when the battery is fully charged.
I am interested in the “autonomous use” mode of deye and without exporting electricity on a sunny day with a fully charged battery
also pay attention to the BMS settings, taking into account that deye cannot work with float variables in the area of charging current - only integers (if you have one deye input connected to the battery, then it is 1A, if the port is dual, then 2A)
this concerns limited modes at the start of balancing, for example, or any other
I can only recommend you to replace the Deye or to force the Deye team to introduce a working firmware. With a simple CAN frame error the Deye ignored all his limits, including the HW limit. On the hardware port it discharged on one battery port with over 60A. Keep in mind that one battery port only supports 50A according to data sheet. The inverter also made strange noises then which come from the filter inductors that are going into saturation.
I returned my Deye after the latest problems which you can see here:
Deye SG01HP3 ignores HW SW and BMS limits on battery port