Binary Output Objects
Showing objects from
Object
 Object Name
 Object Description
Out of
Service
Present Value
Reliability
Status
 Text
1
 Binary Output 1
 BO 1 description goes here
N
Inactive
0
0,0,0,0
 BO 1 is inactive
2
 Binary Output 2
 BO 2 description goes here
N
Inactive
0
0,0,0,0
 BO 2 is inactive
3
 Binary Output 3
 
N
Inactive
0
0,0,0,0
 
4
 Binary Output 4
 
N
Inactive
0
0,0,0,0
 
5
 Binary Output 5
 
N
Inactive
0
0,0,0,0
 
6
 Binary Output 6
 
N
Inactive
0
0,0,0,0
 
7
 Binary Output 7
 
N
Inactive
0
0,0,0,0
 
8
 Binary Output 8
 
N
Inactive
0
0,0,0,0
 
9
 Binary Output 9
 
N
Inactive
0
0,0,0,0
 
 Binary Output 10
 
N
Inactive
0
0,0,0,0
 
 Binary Output 11
 
N
Inactive
0
0,0,0,0
 
 Binary Output 12
 
N
Inactive
0
0,0,0,0
 
 Binary Output 13
 
N
Inactive
0
0,0,0,0
 
 Binary Output 14
 
N
Inactive
0
0,0,0,0
 
 Binary Output 15
 
N
Inactive
0
0,0,0,0
 
Quick Help

The object name, value, and status are shown for a list of objects starting with the number entered at the top of the page. Click Prev/Next to scroll through the list. Click on the object number in the first column to change name or out-of-service state.

The destination of data for a Binary Output object will typically be some other BACnet or Modbus device. Click on the object number in the first column for more detail including the link to any client map receiving data from this object.

The Binary Output object is commandable, meaning the BACnet client must write both a value and a priority level for that value. The highest level value will be the one written to the remote device (if mapped). If all values are relinquished, the relinquish default value will be written to the remote device.

Out of service means the mapped remote device will not be written to. Values written by the BACnet client will be retained, but only applied when this object is placed back in service. At that time, the highest priority value will be written to the remote device.

Reliability codes may be any of the following:
Modbus client/master, no response from slave (64)
Modbus client/master, crc error (65)
Modbus exception, illegal function code (66)
Modbus exception, illegal data address (67)
Modbus exception, illegal data value (68)
Modbus exception, code+65, rarely used (69..79)
Local device, configuration property fault (80)
Faulty Modbus packet(81)
BACnet client, device timeout (82)
BACnet client, error returned by server (83)
Host update timeout (84)

Status flags A,B,C,D indicate the following, 0 meaning not true, 1 meaning true:
A = in alarm
B = fault
C = overridden
D = out of service