Device object
Device object property |
R/W |
Stored |
Possible values |
Description |
---|---|---|---|---|
Object_Identifier |
R |
— |
configurable |
The unique device ID number for the meter, in the format of <device, #>. NOTE: You must use the front panel to configure
the device ID number.
|
Object_Name |
R/W |
√ |
configurable |
A configurable name for the meter. The meter ships from the factory with a name of <model name>_<serial number> (for example, _0000000000). |
Object_Type |
R |
— |
Device |
The object type for the meter. |
System_Status |
R |
— |
Operational |
This value of this property is always Operational. |
Vendor_Name |
R |
— |
Schneider Electric |
Meter manufacturer |
Vendor_Identifier |
R |
— |
10 |
The BACnet vendor identifier for Schneider Electric . |
Model_Name |
R |
— |
iEM3X65 |
Device model (for example, iEM3465 ) and serial number in the format <model name>_<serial number> (for example, iEM3465 _0000000000). |
Firmware_Revision |
R |
— |
varies |
BACnet firmware version, stored in an x.x.x format (for example, 1.7.2). |
Application_Software_Version |
R |
— |
varies |
Meter firmware version, stored in an x.x.xxx format (for example, 1.0.305). |
Description |
R/W |
√ |
configurable |
Optional description of the meter, limited to 64 characters. |
Location |
R/W |
√ |
configurable |
Optional description of the meter’s location, limited to 64 characters. |
Protocol_Version |
R |
— |
varies |
BACnet protocol version (for example, version 1) |
Protocol_Revision |
R |
— |
varies |
BACnet protocol revision (for example, revision 6) |
Protocol_Services_Supported |
R |
— |
|
The BACnet services supported by the meter: subscribeCOV, readProperty, readPropertyMultiple, writeProperty, deviceCommunicationControl, who- HAS, who-Is |
Protocol_Object_Types_Supported |
R |
— |
|
The BACnet object types supported by the meter: analog input, binary input, multi-state input, device. |
Object_list |
R |
— |
varies |
|
Max_APDU_Length_Accepted |
R |
— |
480 |
The maximum packet size (or application protocol data unit) that the meter can accept, in bytes. |
Segmentation_Supported |
R |
— |
0x03 |
The meter does not support segmentation. |
Local_Date |
R |
— |
configurable |
Date NOTE: You must use the front panel to set the meter’s
date.
|
Local_Time |
R |
— |
configurable |
Time NOTE: You must use the front panel to set the meter’s
date.
|
APDU_Timeout |
R/W |
√ |
1000 – 30000 |
The amount of time (in milliseconds) before the meter tries to resend a confirmed message that has not been answered. |
Number_Of_APDU_Retries |
R/W |
√ |
1 – 10 |
The number of times the meter tries to resend an unanswered confirmed request. |
Max_Master |
R/W |
√ |
1 – 127 |
The highest master address the meter will try to discover when the next node is unknown. |
Max_Info_Frames |
R/W |
√ |
1 – 14 |
Maximum number of messages the meter can send before it must pass the token. |
Device_Address_Binding |
R |
— |
— |
Device address binding table is always blank because the meter does not initiate the who-Is service. |
Database_Revision |
R |
√ |
varies |
A number that increments when the object database on the meter changes (for example, when an object is created or deleted or the ID of an object changes). |
Active_COV_Subscriptions |
R |
— |
varies |
List of COV subscriptions currently active on the meter. |
Profile_Name |
R |
— |
varies |
Device identifier that records the meter manufacturer, the meter family and the specific meter model (for example, 10_iEM3000 _iEM3465 ). |
ID 800 |
R |
— |
varies |
Date and time of last energy reset |
ID 801 |
R |
— |
varies |
Date and time of last input metering accumulation reset |
ID 802 |
R |
— |
varies |
Date and time of the last alarm (DD/MM/YYYY hh:mm:ss) |