Schneider Electric iEM3200 Manuale Utente

iEM3100 / iEM3200 / iEM3300 series user manual 

Communications via BACnet

DOCA0005EN-04

91

Make sure that the Mac Address is unique on the serial loop and the Device ID is unique in your 
BACnet network.

The LED indicates the status of the meter’s communications with the network.

The meter supports up to 14 COV subscriptions. You can add COV subscriptions to Analog Input and 
Binary Input objects using your BACnet-compatible software.

•

•

See “Device configuration” on page 38 for information on configuring the meter using the front 
panel.

The following sections outline the supported objects and properties available on the meter.

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 non-volatile onboard memory.

The LED is off

Communication is not active.

The LED is flashing

Communication is active.
NOTE: The LED flashes even if there is a communications error.

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, iEM3265_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

—

iEM3165, iEM3265, 
iEM3365

Device model (for example, iEM3265) and serial number in the format <model 
name>_<serial number> (for example, iEM3265_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

—

0000 0100 0000 1011 
0100 0000 0000 0000 
0110 0000

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

Protocol_Object_Types_Supported R

—

1011 0000 1000 0000 
0000 0000 0000 0000

The BACnet object types supported by the meter: analog input, analog value, 
binary input, device

Object_list

R

—

varies

List of objects in the meter:
iEM3165 / iEM3365: DE1, AI0-AI48, AV0, BI0-BI6
iEM3265: DE1, AI0-AI55, AV0, BI0-BI6

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.