Identifies the object (point, export folder, etc.) including an Object Id and Instance Number or property identifier, which ensures a unique name.

This name is in the format: objectType_<instance number> For example and Event State may be named: AHU1–Frz_Stat-eventState.

Refer also to Object Id, Instance Number.

Identifies a BACnet object. This name should be unique within this specific device.

For components, this name includes the entire component path under the station’s Config using period (.) delimiters between parent.child levels. This enforces (externally) the BACnet requirement for unique names for all objects in a device.

For a proxy point, this is the default name in the station.

You can shorten or edit Object Name, however, each Object Name must be unique among all server descriptors under the Export Table.

Identifies the type of BACnet object, for example, Analog Input, Analog Output, Calendar, Schedule, Structured View, File, Trend Log, BooleanWritable or other.

Writable components typically offer more type selections than read-only points, such as:

Reports the type of object.

Provides a unique number to combine with a device’s Object Id. Together, these properties form the Device Id.

The Instance Number must be unique within the BACnet internetwork for each entity: components, devices, points, schedules, analog inputs, files, groups, multi state inputs, trend logs, SVO (Structured View Object), etc.

The driver automatically increments this value when adding multiple entities.

Refer to Object Id.

Defines the location of the source component or file using standard file Ord notation. In an Edit window, you can access a more meaningful ord by clicking the right-side folder control. This produces a popup Select Ord window, showing the component’s location in the station’s component tree hierarchy.

Provides additional information, which could include the camera’s geographical location or other unique information.