I have been able to establish communications with the EG4 6000XP Inverter using the the PylonTech LV CanBus protocol. I have tested the following items on the communication checklist published on Batrium’s website, please see below for items for which I am looking for advice from Batrium:
-
Communication established between the BMS and the inverter (Rx/Tx Communication): Confirmed
-
Battery Temperature: The 6000XP does not appear to track this information from the Batrium.
-
Battery SoC% between the BMS and inverter matches: Confirmed.
-
Shunt Readings (Voltage and Current): Confirmed.
-
Target Limited for Charging (Voltage and Current): Confirmed - Target Limited Current function works, however you must “trick” the system by setting a 1/10th offset. Need some advice from Batrium regarding this setting. In order for the target limited charge function to register properly, the value must be 1/10th of the desired limited value. Example: Desired Charge Current In the 6000XP = 140AMPS, the Batrium Setting = 14AMPS; Is there some scale factor setting? Voltage Limited function not tested due to LiFePo4 chemistry’s flat voltage curve. I have not tested charge voltage limiter.
-
Target Limited for Discharging (Voltage and Current): Confirmed - This function works, however the you must “trick” the system by setting a 1/10th offset. Need some advice from Batrium regarding this setting. In order for the limited discharge function to register properly, the value must be 1/10th of the desired limited value. Example: Discharge AMP Limit in Batrium must be set to 10 in order for the 6000XP to register 100AMPS; Is there some scale factor setting? Voltage Limited function not tested due to LiFePo4 chemistry’s flat voltage curve. I have not tested discharge voltage limiter.
-
Alert and Warnings Codes: Alerts and Warnings Appear To Be Reporting. Not all alert and warning scenarios have been tested. Will continue to test this reporting.
-
Observe if the inverter reacts to the BMS charge stop: Confirmed - This works, however, see Item 5 & 6 for not regarding offset setting required.
-
Observe if the inverter reacts to charge limiting: Confirmed - This works, however, see Item 5 & 6 for not regarding offset setting required.
-
Observe if the inverter reacts to discharge stop: Confirmed - This works, however, see Item 5 & 6 for not regarding offset setting required.
-
Observe if the inverter reacts to discharge limiting: Confirmed - This works, however, see Item 5 & 6 for not regarding offset setting required.
-
Observe how the inverter reacts if the CANbus cable is disconnected or the BMS is switched off: 6000 XP throws a Battery Communication Error Code. Charge & Discharge state changes to forbidden and in my setup, the inverter switches to Grid mode is powering itself and loads from the Grid.
-
Check other fields that may be part of the protocol: 6000XP does not appear to request or know voltage on a cell level. It only seems to care about the overall battery voltage.