EDE device and point configuration files

Two CSV (Comma Separated Variable) configuration files provide a limited amount of information to identify each device and point:

One or more EDE master configuration files that contain the device and point information
A state texts support file

Both files must conform to the EDE 2.3 specification.

The EDE specification for this utility does not support two additional configuration files: the Unit Text File and Object Type File because unit codes and object types are already defined in the BACnet specification.

The utility supports a single BACnet network instance. Multiple EDE master configuration files for a single BACnet network allow the discovery of devices and points defined in each EDE master configuration file for addition to the current BACnet network instance.

CAUTION: Data security is your responsibility. Store EDE configuration files in a secure location where they cannot be modified by unknown users.

EEDE master configuration file device data specification

The CSV file includes EDE in its name and contains project information as well as the list of data points chosen for inter-operation.

Figure 3. The EDE.csv file

Due to the limited information provided by the EDE format specification, these properties are included for each discovered device:

Property	Required?	Description
Display Name	mandatory	Identifies the device with a system-wide unique name.
Object Name	mandatory	Provides the device address, which must be a unique within a BACnet network. The utility makes exceptions for dynamically-generated objects (for example, for a file to back up and restore data).
Object Type	mandatory	Contains a decimal value to represent the device. For example, an `Object Type` of `Calendar` requires a code number of 06. The utility ignores values that are outside of the BACnet specification. The utility ignores Object Type values that are outside of the BACnet specification because it is not possible to determine what appropriate Niagara object type to use to represent the new Object Type given only an Object Name.
Device Object Instance	mandatory	Identifies the device that contains the data object.
Object Instance	mandatory	Defines a decimal number with which to identify the object. Object Type and Object Instance together provide a unique identifier in each device.
Description	optional	Provides important additional information about the object and its function.
Vendor Specific Address	optional	May identify an address used in the server device, such as a terminal number. This information provides an internal data-point identification or reference.

EDE master configuration file point data specification

The EDE master configuration file for point discovery contains this information:

Property	Required?	Description
Display Name	mandatory	Defines a system-wide unique name for the point.
Object Name	mandatory	Provides the point address, which must be a unique within the device.
Object Type	mandatory	Contains a decimal value to represent engineering units as defined by the BACnet specefication (square-meters, volts, joules, hertz, etc.). The utility supports only unit codes specified in the BACnet specification. The utility ignores `Object Type` values that are outside of the BACnet specification because it is not possible to determine what appropriate Niagara object type to use to represent the new `Object Type` given only an `Object Name`.
Device Object Instance	mandatory	Identifies the parent device that contains this point.
Object Instance	mandatory	Defines a decimal number with which to identify the object. `Object Type` and `Object Instance` together provide a unique identifier in each point.
Description	optional	Provides important additional information about the object and its function.
Present Value	optional	Displays the current value for the point. The default for this value corresponds to a BACnet control point’s `Fallback` value.
Min	optional	Displays the `Present Value` specified as a MIN facets value on the point. It can be obtained from or written to the `Present Value` property.
Max	optional	Displays the `Present Value` specified as a MAX facets value on the point. It can be obtained from or written to the `Present Value` property.
Settable	optional	Indicates if the writable `Present Value` property is controlled by an automated process (device, program) making it a read-only point representation, or if can be set by a client, which makes it a writable point. All BACnet points are writable unless `Settable` is included in the EDE master configuration file and its value is `false`.
Support COV	optional	Defines a Boolean facets value on the point. This value controls if the system supports COV or not.
High Limit	optional	Defines a numeric facets value on the point—the upper alarm limit. Limits imply conditional alarming. The EDE does not include alarm classes. The utility passes this information to Niagara as facet information only.
Low Limit	optional	Defines a numeric facets value on the point—the lower alarm limit. Limits imply conditional alarming. The EDE does not include alarm classes. The utility passes this information to Niagara as facet information only.
State Text	optional	Provides information as an enumeration facets value on the point. It is valid for binary and multistate objects only.
Vendor Address	optional	Provides a string facets value on the point. It may identify an address used in the server device, such as a terminal number. This information provides an internal data-point identification or reference.