Peripheral Device object (PrphDev)

"Present value" indicates the present value of the field device status. Values include:

• Operational
• Device halted
• Device not assigned
• Device missing
• Configuring device
• Device not assignable
• Missing or wrong configuration

'Tracking value' represents the uncorrected value as measured by the subsystem. It has the same data type as the 'Present value'.

• It is not limited by 'Present minimum value' and 'Present maximum value'.
• It is not corrected by the correction factor and offset.
• It is updated, even if "Out of service" = 'True' applies.

Property ID: 5107

"State flag" represents four boolean flags ("Out of service", "Overridden", "Fault", "In-Alarm") that indicate the general status of an object.

'Reliability' indicates whether the property value 'Present value' is reliable. If the 'Present value' is not reliable, the property 'Reliability' indicates the cause of the fault and the bit "Fault" of the state indication is set to 'True'. In a normal case, the property 'Reliability' is set to "No fault".

Property ID: 103

"Out of service" allows decoupling the object from being modified by a control program, system program or peripheral device.

• If "Out of service" is TRUE, the properties "Present value" and "Reliability" will no longer be updated by the respective control program, system program or peripheral device.
• If "Out of service" is TRUE, the properties "Present value" and "Reliability" can be modified for simulating and testing purposes.
• If "Out of service" will be changed from FALSE to TRUE, the properties "Present value" and "Reliability" keep their values. Nevertheless, they can be individually modified afterwards.
• If "Out of service" will be changed from TRUE to FALSE, the properties "Present value" and "Reliability" keep their values. They will be modified by the next update of the producer.

Property ID: 81

"I/O address" identifies and documents the data source, and facilitates configuring, modifying, and querying the assignment in a standardized way.

The content of "I/O address" is technology-specific and includes:

• Unique selector to identify and document the respective data acquisition. For example, TX-I/O or KNX PL-Link.
• Unique address to identify the peripheral data source. For example, TX-I/O 3.4.
• Blank until assigned to a Module.

'State text' specifies the enumeration of the multistate value. Preconfigured enumerations can be selected or set to a project-specific enumeration.

Property ID: 110

"Field device type" is a text description of the physical peripheral device connected to the input or output. Typically contains the product part number of the connected device. To be completed by the engineer. Is not used by the data acquisition.

Example: QAX3.P84 (room unit) - Entrance

"Device info" represents pieces of information about the respective networked peripheral device. The property can be empty if a peripheral device does not provide a respective piece of information.

"Network address" contains a network or physical address of the respective networked peripheral device.

"Serial number" shows the unique serial number of the device as shipped from the factory.

• Data acquisition will read "Serial number" from the device and set the respective property value.
• If "Out of service" is TRUE, "Serial number" will not be setup by the data acquisition.
• "Serial number" will be modeled as a string because it depends on a particular technology:
  KNX PL-Link (KNX Serial Number) 48-bit,
  DALI (CIN as used by Osram devices) 128 bit
• "Serial number" can be empty if not available.

"Commissioning state" is an enumerated value representing the commissioning state (Not checked, Check failed, Check successful) of the BACnet object.

Typically set during commissioning by means of engineering and commissioning function (for example, Automation Building Tool or installer tool). It can be inspected by engineering and commissioning, or operation and monitoring functions, and used in commissioning reports.

"Commissioning information" indicates additional, human-readable information about the BACnet object's commissioning state. For example, "cable defect".

Typically set during commissioning by means of engineering and commissioning function (for example, Automation Building Tool or installer tool). It can be inspected by engineering and commissioning, or operation and monitoring functions, and used in commissioning reports.

"Error list" allows indicating multiple reliability error codes in parallel.

"Subsystem" uniquely identifies the respective BACnet object type extension of a BACnet object type.

Several BACnet object type extensions might be available for Engineering thus proposed for selection. None or one extension might be selected, thus be supported at runtime.

"Object access level" defines the instance-specific object access level. "Object access level" is used for generic filtering and processing an object by a client application.

• "Object access level" is a configuration property which can only be set up offline (ABT, application configuration).
• "Object access level" is evaluated by client applications such as Technical Operator, DB-Import, and APOGEE Point Team mapping.

Access level

Name

Description

7

Basic operation

Access to BACnet objects and properties for a room user e.g. data points visible on a room unit.

6

Standard operation

Access to BACnet objects and properties for standard operation and monitoring (daily business), .e.g. room and plant information on a management station.

5

Extended operation

Access to BACnet objects and properties for extended operation and monitoring such as network and device objects. All I/Os are visible

4

Administrator

Not used by HQ solutions yet.

3

Basic service

Access to BACnet objects and properties used for commissioning, e.g. configuration value extensions, I/O extensions, etc.

2

Extended service

Not used by HQ solutions yet.

1

Internal

Access to all BACnet objects and properties for very specialized actions e.g. during development.

"Object usage" indicates whether the object is used or unused. The "Object usage" property can hide or display respective objects and their functionality in a client. For example, room functionality can be marked for flexible room arrangements as used/unused. An object that is marked as unused behaves as if the object does not exist.

Property ID: 4930

"Description" is a string of printable characters whose content is not restricted.

"Object name" represents a name for the object that is unique internetwork-wide. The minimum length of the string is one character. The set of characters used in the "Object name" are restricted to printable characters.

A string of printable characters whose content is not restricted.