EAV15107-EN06

Device object

Your meter has a Device object which describes the meter to the BACnet network.

The following table outlines the properties of the Device object, whether a property is read-only or read-write, and if the value of the property is stored in the meter’s nonvolatile onboard memory.

Device object property R/W Stored Possible values Description

Object_Identifier

R/W

Y

See description

The unique device ID number for the meter, in the format of <device, #>.

The meter ships from the factory with a device ID equal to the last 6 digits of the serial number.

Object_Name

R/W

Y

See description

A configurable name for the meter.

The meter ships from the factory with a name of <model name>_<serial number> (for example, PM5320_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

varies

Device model (for example, PM5320) and serial number in the format <model name>_<serial number> (for example, PM5320_0000000000).

Firmware_Revision

R

varies

BACnet firmware version, stored in an x.x.x format (for example, 1.9.0).

Application_Software_Version

R

varies

Meter firmware version, stored in an x.x.x format (for example, 1.0.305).

Description

R/W

Y

configurable

Optional description of the meter, limited to 64 characters.

Location

R/W

Y

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 14)

Protocol_Services_Supported

R

0000 0100 0000 1011
1100 1000 0000 0000
0110 0000 0

The BACnet services supported by the meter: subscribeCOV, readProperty, readPropertyMultiple, writeProperty, writePropertyMultiple, deviceCommunicationControl, ReinitializeDevice, who-HAS, who-Is

Protocol_Object_Types_Supported

R

1001 0000 1000 0100
0000 0000 0000 0000
0000 0000 0000 0000
0000 000

The BACnet object types supported by the meter: analog input, binary input, multi-state input, device.

Object_list

R

See description

List of objects in the meter.

Max_APDU_Length_Accepted

R

1476

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

varies

Current date on the meter

NOTE: Use the display or ION Setup to set the meter’s date.

Local_Time

R

varies

Current time on the meter

NOTE: Use the display or ION Setup to set the meter’s time.

APDU_Timeout

R/W

Y

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

Y

1 – 10

The number of times the meter tries to resend an unanswered confirmed request.

Device_Address_Binding

R

Device address binding table is always blank because the meter does not initiate the who-Is service.

Database_Revision

R

Y

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-PM5000-PM5320).

QR code for this page

Was this helpful?