Command Control object (CmdObj)
The Command Control object (CmdObj) type is used to command a set of BACnet objects with configured values that depend upon a particular mode of operation. The Command Control object is based on the BACnet Standard and includes proprietary properties.
The Command object type defines a standardized object whose properties represent the externally visible characteristics of a multi-action command procedure. You can use a Command object to write a set of values to a group of object properties, based on the action code that is written to the "Present value" of the Command object. Whenever the "Present value" property of the Command object is written to, it triggers the Command object to take a set of actions that change the values of a set of other object’s properties.
When a large number of BACnet objects need to be commanded, Grouping and Group Communications can be used. Also, when process values and unconfigured values need to be commanded, Grouping and Group Communications or directly commanding the BACnet objects by a control program can be used.
The CmdObj properties are:
✳ Indicates a Siemens proprietary property.
Command value |
|
|
|---|---|---|
"Command value" allows triggering the running of an "ActionList" by writing an action number (scene-number) corresponding to the "Action table" index of the requested "ActionList" to "Command value".
| ||
Memorize scene ✳ |
|
|
|---|---|---|
"Memorize scene" allows memorizing the property values of an "ActionList" by writing an action number (scene number) corresponding to the "Action table" index of the requested "ActionList" to "Memorize scene".
| ||
In progress ✳ |
|
| |
|---|---|---|---|
"In progress" indicates whether a command is being processed (i.e. the blind is moving, the light is changing). | |||
No | No command is being performed. | ||
Yes | A target state or control command is being performed. | ||
All write cmds successful |
|
|
|---|---|---|
"All write cmds successful" indicates whether all Action-Items of the last Action-List were run successfully.
| ||
Cancel command ✳ |
|
|
|---|---|---|
"Cancel command" allows ending the "Action table" currently running. The "Cancel command" property is:
| ||
Action table |
|
|
|---|---|---|
"Action table" shows an array of actions. These action lists are indexed by the value that is written to the "Present value" property. | ||
Action text |
|
|
|---|---|---|
"Action text" is an array of CharacterString used to indicate a text string description for each of the possible values of the "Present value" property. The content of these strings is not restricted. If the size of this array is changed, the size of the array is changed to the same size. | ||
Enable memorize ✳ |
|
|
|---|---|---|
"Enable memorize" allows enabling/disabling of the memorize function. | ||
State flag ✳ |
|
|
|---|---|---|
"State flag" represents four boolean flags ("Out of service", "Overridden", "Fault", "In-Alarm") that indicate the general status of an object. | ||
Reliability |
|
|
|---|---|---|
'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 | ||
Object access level ✳ |
|
| ||
|---|---|---|---|---|
"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.
| ||||
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 ✳ |
|
|
|---|---|---|
"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 |
|
|
|---|---|---|
"Description" is a string of printable characters whose content is not restricted. | ||
Object name |
|
|
|---|---|---|
"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. | ||
Object identifier |
|
|
|---|---|---|
"Object identifier" is a numeric code that is used to identify the object. It must be unique internetwork-wide. | ||
Object type |
|
|
|---|---|---|
"Object type " indicates membership in a particular object type class. E.g. "Analog input", "Binary output", "Event enrollment", "Trend log", etc. | ||
Building automation profile ✳ |
|
|
|---|---|---|
"Building automation profile" is an enumeration that indicates a particular type of Siemens proprietary object. Siemens objects are based on standard BACnet objects. For example, Siemens Analog Input, Analog Output, Analog Calculated Value, and Analog Configuration Value are based on standard Analog Input, Analog Output, and Analog Value BACnet objects. | ||
Profile name |
|
|
|---|---|---|
"Profile name" indicates the name of an object profile to which this object conforms. To ensure uniqueness, a profile name must begin with a vendor identifier code followed by a dash. All subsequent characters are administered by the organization registered with that vendor identifier code. The vendor identifier code that prefixes the profile name indicates the organization that publishes and maintains the profile document named by the remainder of the profile name. | ||
Comment |
|
|
|---|---|---|
A string of printable characters whose content is not restricted. | ||