Pulse Converter (PC)
- Last UpdatedDec 08, 2020
- 4 minute read
Supported properties of the Pulse Converter object (PC)
|
Property |
Value Format |
Example |
|
OBJECT-IDENTIFIER |
String [ObjectNumber]: [Instance Number] |
24:0 |
|
OBJECT-NAME |
String |
ObjectName:Pulse Converter Object Type(PC) |
|
OBJECT-TYPE |
Integer |
24 |
|
DESCRIPTION |
String |
Description: Pulse Converter Object Type (PC) |
|
INPUT-REFERENCE |
String [OBJECT-IDENTIFIER] | [PROPERTY-IDENTIFIER] | [PROPERTY-ARRAY- INDEX (Optional)] |
This optional property, of type BACnetObjectPropertyReference, indicates the object and property (typically an Accumulator object's Present Value property) representing the actual physical input that is to be measured and presented by the Pulse Converter object. For example: 29,4194303|29|786 |
|
PRESENT-VALUE |
Float |
This property, of type REAL, indicates the accumulated value of the input being measured. It is computed by multiplying the current value of the Count property by the value of the Scale Factor property For example:100 |
|
STATUS-FLAGS EVENT-STATE |
4 Boolean values (1 = true, 0 = false) encoded as string {IN_ALARM, FAULT, OVERRIDDEN, OUT_OF_SERVICE} Integer |
This property, of type BACnetStatusFlags, represents four Boolean flags that indicate the general "health" of a Pulse Converter. For example: 1101 The Event State property, of type BACnetEventState, is included in order to provide a way to determine if this object has an active event state associated with it. If the object supports intrinsic reporting, then the Event State property shall indicate the event state of the object. For example: 1 |
|
RELIABILITY OUT-OF-SERVICE |
Integer Boolean |
The Reliability property, of type BACnetReliability, provides an indication of whether the Present Value and/or Count properties or the operation of the physical input in question is "reliable" as far as the BACnet Device or operator can determine and, if not, why. For example: 5 The Out Of Service property, of type BOOLEAN, is an indication whether (TRUE) or not (FALSE) the input that the object directly represents, if any, is not in service. For example: 1 |
|
UNITS |
Integer |
This property, of type BACnetEngineeringUnits, indicates the measurement units of the Present Value property. See the BACnetEngineeringUnits ASN.1 production in Clause 21 for a list of engineering units defined by this standard. For example: 7 |
|
SCALE-FACTOR ADJUST-VALUE |
Float Float |
This property, of type BACnetStatusFlags, represents four Boolean flags that indicate the general "health" of a Pulse Converter. For example: 1101 The Event State property, of type BACnetEventState, is included in order to provide a way to determine if this object has an active event state associated with it. If the object supports intrinsic reporting, then the Event State property shall indicate the event state of the object. For example: 1 |
|
COUNT |
Integer |
This read-only property, of type Unsigned, indicates the count of the input pulses as acquired from the physical input or the property referenced by the Input Reference property. For example: 20 |
|
UPDATE-TIME |
String |
This read-only property, of type BACnetDateTime, reflects the date and time of the most recent change to the Count property as a result of input pulse accumulation and is updated atomically with the Count property. If no such change has yet occurred, this property shall have wildcard values for all date and time fields. For example: 29-5-2014 17:6:24.78 |
|
COUNT-CHANGE-TIME |
String |
This read-only property, of type BACnetDateTime, represents the date and time of the most recent occurrence of a write to the Adjust Value property. If no such write has yet occurred, this property shall have wildcard values for all date and time fields. For example: 29-5-2014 17:6:24.78 |
|
COUNT-BEFORE-CHANGE |
Integer Float |
This property, of type Unsigned, indicates the value of the Count property just prior to the most recent write to the Adjust Value properties. If no such write has yet occurred, this property shall have the value zero. For example: 0 |
|
COV-INCREMENT |
This property, of type REAL, shall specify the minimum change in Present Value that will cause a COV notification to be issued to subscriber COV-clients. This property is required if COV reporting is supported by this object. For example: 30 |
|
|
NOTIFICATION-CLASS |
Integer |
This property, of type Unsigned, shall specify the notification class to be used when handling and generating event notifications for this object. For example: 25 |
|
LOW-LIMIT DEADBAND |
Float Float |
This property,of type REAL, shall specify a limit below which the Present Value must fall before an event is generated.This property is required if intrinsic reporting is supported by this object. For example:60 This property, of type REAL,shall specify a range between the HighLimit and LowLimit properties,which the Present Value must remain within for a TO- NORMAL event to be generated under these conditions:
|
|
||
|
LIMIT-ENABLE |
2 Boolean values(1=true,0=false) encoded as a string {lowLimitEnable, highLimitEnable} |
This property, of type BACnetLimitEnable, shall convey two flags that separately enable and disable reporting of high limit and low limit offnormal events and their return to normal. This property is required if intrinsic reporting is supported by this object. For example: 10 |
|
EVENT-ENABLE ACKED-TRANSITIONS |
3 Boolean values(1=true,0=false) encoded as a string {to-offnormal, to- fault, to-normal} 3 Boolean values (1=true,0=false) encoded as a string {to-offnormal, to- fault, to-normal} |
This property, of type BACnetEventTransitionBits, shall convey three flags that separately enable and disable reporting of TO-OFFNORMAL, TO-FAULT, and TO- NORMAL events. In the context of Pulse Converter objects, transitions to the High Limit or Low Limit Event States are considered to be "offnormal" events. This property is required if intrinsic reporting is supported by this object. For example: 101 This property, of type BACnetEventTransitionBits, shall convey three flags that separately indicate the receipt of acknowledgements for TO-OFFNORMAL, TO-FAULT, and TO-NORMAL events. For example: 111 |
|
NOTIFY-TYPE EVENT-TIME-STAMPS |
Integer Sequence of time stamps encoded as a string |
This property, of type BACnetNotifyType, shall convey whether the notifications generated by the object should be Events or Alarms. This property is required if intrinsic reporting is supported by this object. For example: 2 This optional property, of type BACnetARRAY[3] of BACnetTimeStamp, shall convey the times of the last event notifications for TO-OFFNORMAL, TO- FAULT, and TO-NORMAL events, respectively. For example: 2|1-1-1970 11:0:0.0;2| 1-1-1970 11:0:0.0;2|1-1-1970 11:0:0.0 |
|
PROFILE-NAME |
String |
Profile Name: Pulse Converter Object Type (PC) |