BYD ESS C648

Plugin

• This plugin reads the BYD ESS C648 Containers

• The Modbus Bus address cannot be anything other than 100

• The Modbus configuration files for the C648 BYD battery have configurations based on specific RTUs (IP Addresses). You MUST find out the IP addresses of the BMS (2 x IP addresses), the PCS (2 x IP addresses) and the ADAS (1 x IP address).

• The following data is collected at the stated intervals.

• MAKE SURE that only the relevant configuration files are run against an RTU.

Source Map

• To remain consistent with other installations of ESS, make sure you have a source map entry installed for ALL scenarios listed below

• These are examples only. You need to replace the IP address to suit the installation site

• For the PCS files

([^/]*)/192.168.1.123/502/100,\1_pcs1
([^/]*)/192.168.1.124/502/100,\1_pcs2

• For the BMS files

([^/]*)/192.168.1.223/502/100,\1_bms1
([^/]*)/192.168.1.224/502/100,\1_bms2

• For the ADAS files

([^/]*)/192.168.1.191/502/100,\1

BMS (RTU1 and RTU2):

• These tasks must be run for PCS RTU1 and RTU2, which is a two different IP addresses

• For each of RTU1 and RTU2, create the following scenarios:

Script Name 	                Type 	    Freq (secs)     IP address      Source map	Changes only
--------------------------------------------------------------------------------------------------
c648_bms_on_change_alarms.txt   Service     300             BMS (RTU1/2)    Yes         true
c648_bms_on_change_alarms.txt   Task        1h              BMS (RTU1/2)    Yes         false
c648_bms_on_change_values.txt   Service     300             BMS (RTU1/2)    Yes         true
c648_bms_on_change_values.txt   Task        1h              BMS (RTU1/2)    Yes         false
c648_bms_120_seconds.txt        Task        120             BMS (RTU1/2)    Yes         false
c648_bms_300_seconds.txt        Task        300             BMS (RTU1/2)    Yes         false

PCS (RTU3 and RTU4):

• These tasks must be run for PCS RTU3 and RTU4, which is a two different IP addresses

• For each of RTU3 and RTU4, create the following scenarios:

Script Name 	                Type 	    Freq (secs)     IP address      Source map	Changes only
--------------------------------------------------------------------------------------------------
c648_pcs_2_seconds.txt          Service     2               PCS (RTU3/4)    Yes         false
c648_pcs_on_change_values.txt   Service     300             PCS (RTU3/4)    Yes         true
c648_pcs_on_change_values.txt   Task        1h              PCS (RTU3/4)    Yes         false
c648_pcs_30_seconds.txt         Task        30              PCS (RTU3/4)    Yes         false
c648_pcs_120_seconds.txt        Task        120             PCS (RTU3/4)    Yes         false
c648_pcs_on_change_alarms.txt   Service     300             PCS (RTU3/4)    Yes         true
c648_pcs_on_change_alarms.txt   Task        1h              PCS (RTU3/4)    Yes         false

ADAS (RTU5):

• These 2 tasks must be run for ADAS RTU5, which is a single IP address

• This data refers to the ADAS Container Modbus server. It is different from the PCS data.

• For the ADAS RTU, create the following scenarios:

Script Name 	                Type 	    Freq (secs)	    IP address      Source map	Changes only
--------------------------------------------------------------------------------------------------
c648_adas_on_change_values      Service     300             ADAS (RTU5)     Yes         true
c648_adas_on_change_values      Task        1h              ADAS (RTU5)     Yes         false