For the complete documentation index, see llms.txt. This page is also available as Markdown.

Engineering Data Exchange file structure

The EDE file serves to integrate the Aranet PRO BACnet service into third-party systems through offline import. This file defines the structure of BACnet project data for a device. When changes are made to the object list in the Aranet PRO base, the outdated EDE file, which contains information about available objects, is removed. Users can then request the base to generate a new EDE file, which is in CSV format. The first six rows of the file provide descriptions about the BACnet project that generated it. The EDE file structural components is in the table below.

Column name
Requirement
Description

Keyname

Mandatory

BACnet specific object type combined with instance identifier

Device object instance

Mandatory

Device object instance ID which owns this object

Object name

Mandatory

Name of the object

Object type

Mandatory

BACnet specific identifier used to identify object type

Object instance

Mandatory

Object instance identifier

Description

Optional

Object description auto-generated by BACnet upon object creation

State text reference

Optional

Not used

Present value default

Optional

Not used

Supports CoV

Optional

Does object supports Cange-of-Value

Commandable

Optional

Is commandable (using priority array)

Min. present value

Optional

Not used

Max. present value

Optional

Not used

High limit

Optional

Not used

Low limit

Optional

Not used

Unit-code

Optional

BACnet specific identifier used to identify the measurement unit

Vendor specific address

Optional

Not used

Element

Optional

Additional field which contains object description

Last updated