IEEE 2030.5 DER Agent¶
The IEEE 2030.5 Agent (IEEE2030_5 in the VOLTTRON repository) implements a IEEE 2030.5 server that receives HTTP POST/PUT requests from IEEE 2030.5 devices. The requests are routed to the IEEE 2030.5 Agent over the VOLTTRON message bus by VOLTTRON’s Master Web Service. The IEEE 2030.5 Agent returns an appropriate HTTP response. In some cases (e.g., DERControl requests), this response includes a data payload.
The IEEE 2030.5 Agent maps IEEE 2030.5 resource data to a VOLTTRON IEEE 2030.5 data model based on SunSpec, using block numbers and point names as defined in the SunSpec Information Model, which in turn is harmonized with 61850. The data model is given in detail below.
Each device’s data is stored by the IEEE 2030.5 Agent in an EndDevice memory structure. This structure is not persisted to a database. Each EndDevice retains only the most recently received value for each field.
The IEEE2030_5 Agent exposes RPC calls for getting and setting EndDevice data.
VOLTTRON IEEE 2030.5 Device Driver¶
The IEEE 2030.5 device driver is a new addition to VOLTTRON Platform Driver Agent’s
family of standard device drivers. It exposes get_point
/set_point calls
for IEEE 2030.5 EndDevice fields.
The IEEE 2030.5 device driver periodically issues IEEE2030_5 Agent RPC calls to refresh its cached representation of
EndDevice data. It issues RPC calls to IEEE2030_5Agent as needed when responding to get_point
, set_point
and
scrape_all
calls.
Field Definitions¶
These field IDs correspond to the ones in the IEEE 2030.5 device driver’s configuration file, ieee2030_5.csv
.
They have been used in that file’s “Volttron Point Name” column and also in its “Point Name” column.
Field ID |
IEEE 2030.5 Resource/Property |
Description |
Units |
Type |
---|---|---|---|---|
b1_Md |
|
Model (32 char lim). |
string |
|
b1_Opt |
|
Long-form device identifier (32 char lim). |
string |
|
b1_SN |
|
Short-form device identifier (32 char lim). |
string |
|
b1_Vr |
|
Version (16 char lim). |
string |
|
b113_A |
|
AC current. |
A |
float |
b113_DCA |
|
DC current. |
A |
float |
b113_DCV |
|
DC voltage. |
V |
float |
b113_DCW |
|
DC power. |
W |
float |
b113_PF |
|
AC power factor. |
% |
float |
b113_WH |
|
AC energy. |
Wh |
float |
b120_AhrRtg |
|
Usable capacity of the battery. Maximum charge minus minimum charge. |
Ah |
float |
b120_ARtg |
|
Maximum RMS AC current level capability of the inverter. |
A |
float |
b120_MaxChaRte |
|
Maximum rate of energy transfer into the device. |
W |
float |
b120_MaxDisChaRte |
|
Maximum rate of energy transfer out of the device. |
W |
float |
b120_WHRtg |
|
Nominal energy rating of the storage device. |
Wh |
float |
b120_WRtg |
|
Continuous power output capability of the inverter. |
W |
float |
b121_WMax |
|
Maximum power output. Default to WRtg. |
W |
float |
b122_ActWh |
|
AC lifetime active (real) energy output. |
Wh |
float |
b122_StorConn |
|
CONNECTED=0, AVAILABLE=1, OPERATING=2, TEST=3. |
enum |
|
b124_WChaMax |
|
Setpoint for maximum charge. This is the only field that is writable with a set_point call. |
W |
float |
b403_Tmp |
|
Pack temperature. |
C |
float |
b404_DCW |
|
Power flow in or out of the inverter. |
W |
float |
b404_DCWh |
|
Output energy (absolute SOC). Calculated as (availabilityDuration / 3600) * WMax. |
Wh |
float |
b802_LocRemCtl |
|
Control Mode: REMOTE=0, LOCAL=1. |
enum |
|
b802_SoC |
|
State of Charge %. |
% WHRtg |
float |
b802_State |
|
DISCONNECTED=1, INITIALIZING=2, CONNECTED=3, STANDBY=4, SOC PROTECTION=5, FAULT=99. |
enum |
Revising and Expanding the Field Definitions¶
The IEEE 2030.5-to-SunSpec field mappings in this implementation are a relatively thin subset of all possible field definitions. Developers are encouraged to expand the definitions.
The procedure for expanding the field mappings requires you to make changes in two places:
Update the driver’s point definitions in
services/core/PlatformDriverAgent/platform_driver/ieee2030_5.csv
Update the IEEE 2030.5-to-SunSpec field mappings in
services/core/IEEE2030_5Agent/ieee2030_5/end_device.py
and__init__.py
When updating VOLTTRON’s IEEE 2030.5 data model, please use field IDs that conform to the SunSpec block-number-and-field-name model outlined in the SunSpec Information Model Reference (see the link below).
View the IEEE 2030.5 agent specification document to learn more about IEEE 2030.5 and the IEEE 2030.5 agent and driver.