Installation guide, Bacnet programming information – Veris Industries E8950 Install User Manual

Page 8

E8950

INSTALLATION GUIDE

ZL0105-0B

PAGE 8

02131

Alta Labs, Enercept, Enspector, Hawkeye, Trustat, Aerospond, Veris, and the Veris ‘V’ logo are trademarks or registered trademarks of Veris Industries, L.L.C. in the USA and/or other countries.

BACNET PROGRAMMING INFORMATION

BACnet PICS (Protocol Implementation Conformance Statement)

Vendor Name: Veris Industries
BACnet Vendor ID 133
Product Name: E8950 Modbus-to-BACnet Protocol Converter
Product Model Number: E8950 w/Modbus Energy Meter
Product Description: Modbus-to-BACnet Protocol Converter
Protocol Conversions: Converts Modbus RTU to BACnet IP and BACnet MS/TP for sup-
ported products from Veris Industries
BACnet Protocol Version: Version 1 Revision 12

BACnet Standardized Device Profile (Annex L) – [Note: E8950 is a gateway device]

• BACnet Application Specific Controller (B‐ASC)

BACnet Interoperability Building Blocks Supported (Annex K):

• K.1.2 BIBB ‐ Data Sharing ‐ ReadProperty‐B (DS‐RP‐B)
• K.1.4 BIBB ‐ Data Sharing ‐ ReadPropertyMultiple‐B (DS‐RPM‐B)
• K.1.8 BIBB ‐ Data Sharing ‐ WriteProperty‐B (DS‐WP‐B)
• K.1.10 BIBB ‐ Data Sharing ‐ WritePropertyMultiple‐B (DS‐WPM‐B)
• K.1.12 BIBB ‐ Data Sharing ‐ COV‐B (DS‐COV‐B)
• K.2.2 BIBB ‐ Alarm and Event‐Notification Internal‐B (AE‐N‐I‐B)
• K.2.5 BIBB ‐ Alarm and Event‐ACK‐B (AE‐ACK‐B)
• K.2.11 BIBB ‐ Alarm and Event‐Information‐B (AE‐INFO‐B)
• K.5.2 BIBB ‐ Device Management ‐ Dynamic Device Binding‐B (DM‐

DDB‐B)

• K.5.4 BIBB ‐ Device Management ‐ Dynamic Object Binding‐B (DM‐DOB‐B)
• K.5.6 BIBB ‐ Device Management ‐ DeviceCommunicationControl‐B (DM‐

DCC‐B)

• K.5.12 BIBB ‐ Device Management ‐ TimeSyncronization‐B (DM‐TS‐B)
• K.5.22 BIBB ‐ Device Management – List Manipulation‐B (DM‐LM‐B)

Standard Object Types Supported

• Device Object
• Analog Input
• Analog Output*
• Analog Value
• Binary Input*
• Binary Output*
• Binary Value*
• Multi State Input*
• Multi State Output*
• Multi State Value*
• Notification Class Object*

* Supported by device driver, but not used by current device profiles

Unsupported Properties and Restrictions

• Does not support BACnet CreateObject
• Does not support BACnet DeleteObject
• Does not support any proprietary properties
• No proprietary properties exist
• No range restrictions exist
• Max_Master is writable, but it reverts to 127 when the E8950 is reset or

powered-up.

Data Link Layer Options:

• BACnet IP, (Annex J)
• MS/TP master (Clause 9), baud rate up to 76.8 kbps

Networking Options:

• BACnet/IP Broadcast Management Device (BBMD)
• Registrations by Foreign Devices

Character Sets Supported:

• ISO 10646 (UTF-8) / ANSI X3.4

General Programming Information

The E8950, in Discovery mode, queries each Modbus address, from 1 to 247 for a slave
ID. For each address queried, if a meter responds with a slave_ID that matches those
supported by the E8950, a BACnet device object and a full set of data objects are
created (see Appendix 1).

The initial Object_Identifier (Device_ID) property value of each device object
discovered is the sum of the Device_ID offset programmed into the E8950 and the
Modbus address of the meter. The factory default value of the offset is 50000; use
the GUI to change this value. The new value will be applied the next time the E8950
is power cycled or reset. Once a device’s Object_Identifier is overwritten, changes
to the ID Offset will no longer affect that Object_Identifier, even in Discovery mode.
Make further changes to the value by writing the Object_Identifier property.

The default Object_Name property value of each device object is an abbreviated
name of the meter series discovered with an underscore and the Modbus address of
the meter appended to it. The Object_Name is a writable property. Once a device’s
Object_Name is overwritten, the Object_Name will not revert to the initial default,
even in Discovery mode. Make further changes to the value by writing the Object_
name property.

The default description property value of each device object is the first 40 characters
of the Modbus slave ID returned by the meter discovered. The description is not a
writable property.

The E8950 supports Subscribe_COV, with default COV increment values assigned
as shown in the data object tables (see Appendix for value tables for each meter).
If these values are not appropriate for a specific application, write them as needed
when they are subscribed. On subsequent power cycles, no subscriptions are active
and the COV increments return to their default values.

With few exceptions, any data values written to AV objects are accepted (without
error) by the data object and passed through to the corresponding Modbus register.
There is no direct indication via the BACnet protocol if invalid values are rejected.
After an invalid value is written to the Present_Value of an AV, subsequent reads
of that property return the new (invalid) value until the next time the E8950 scans
and updates the AV objects (this may take several seconds, depending on the overall
configuration and timing of the scan sequence). The tables in Appendix 1 specify valid
values for AV objects of each supported model.