Property | Type | Description |
Analog Input 1[1] | Numeric | Value of linear input (0–10 VDC, 0–20 mA, or 100 to 100,000 ohms) connected to Universal Input 1 on the BCU. |
Analog Input 1[2] | Numeric | Value of Thermistor sensor (-20 F to 250 F) connected to Universal Input 1 on the BCU. |
Analog Input 1[3] | Numeric | Value of Platinum RTD sensor (-90 F to 250 F) connected to Universal Input 1 on the BCU. |
Analog Input 1[4] | Numeric | Value of Balco RTD sensor (-64 F to 250 F) connected to Universal Input 1 on the BCU. |
Analog Input 2[1] | Numeric | Value of linear input (0–10 VDC, 0–20 mA, or 100 to 100,000 ohms) connected to Universal Input 2 on the BCU. |
Analog Input 2[2] | Numeric | Value of Thermistor sensor (-20 F to 250 F) connected to Universal Input 2 on the BCU. |
Analog Input 2[3] | Numeric | Value of Platinum RTD sensor (-90 F to 250 F) connected to Universal Input 2 on the BCU. |
Analog Input 2[4] | Numeric | Value of Balco RTD sensor (-64 F to 250 F) connected to Universal Input 2 on the BCU. |
APDU Segment Timeout | Binary | Application Layer Protocol Data Units (APDUs) represent requests and results of applications communicating over BACnet. Some APDUs are so large they must be broken into multiple "segments." This property indicates the status of the timeout. |
APDU Timeout | Numeric | This property indicates the number of milliseconds for an APDU timeout. A timed out APDU is a failed APDU and is retried by the number of times defined by the "Number of APDU Retries" property. |
Application Software Revision | Character | Version number of BCU software saved at the workstation, not necessarily the version in the BCU. To read the actual version number in the BCU, refer to the "Firmware Revision" property |
BACnet Vendor ID | Numeric | This property indicates the vendor ID assigned by ASHRAE (used in BACnet communications). |
BCU Database Status | Multi-State | Indicates whether BCU’s database is Normal, Under Construction, or Cleared. |
BCU System Diagnostics[01] | Numeric | Number of BCU restarts since RAM was last cleared. |
BCU System Diagnostics[02] | Numeric | Number of interrupted Power Critical Regions. |
BCU System Diagnostics[03] | Numeric | ARCNET: Number of reconfigurations. A high or increasing number may indicate cable problems, or two nodes at the same address. |
BCU System Diagnostics[04] |
Numeric |
Number of ARCNET/Ethernet aborted transmissions. |
BCU System Diagnostics[05] |
Numeric |
Number of ARCNET/Ethernet receive out of buffers. |
BCU System Diagnostics[06] | Numeric | Number of ARCNET/Ethernet messages retransmitted. |
BCU System Diagnostics[07] | Numeric | Number of ARCNET/Ethernet good transmissions, low 16 bits. |
BCU System Diagnostics[08] | Numeric | Number of ARCNET/Ethernet good transmissions, high 16 bits. |
BCU System Diagnostics[09] | Numeric | Number of ARCNET/Ethernet good receives, low 16 bits |
BCU System Diagnostics[10] |
Numeric |
Number of ARCNET/Ethernet good receives, high 16 bits. |
BCU System Diagnostics[11] |
Numeric |
Number of EEPROM re-tried writes. A non-zero value may indicate a bad or failing EEPROM. |
BCU System Diagnostics[12] |
Numeric |
Number of unexpected BACnet replies. A high or increasing value may indicate problems with a Workstation or remote BACnet device. |
BCU System Diagnostics[13] |
Numeric |
Number of BACnet Reject PDUs sent. A high or increasing value may indicate problems with a Workstation or remote BACnet device. |
BCU System Diagnostics[14] |
Numeric |
Number of UCM channel 1 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[15] |
Numeric |
Number of UCM channel 2 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[16] |
Numeric |
Number of UCM channel 3 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[17] |
Numeric |
Number of memory blocks outstanding. |
BCU System Diagnostics[18] |
Numeric |
Paragraphs of memory remaining. |
BCU System Diagnostics[19] |
Numeric |
Minimum paragraphs of memory encountered. |
BCU System Diagnostics[20] |
Numeric |
Number of failing memory requests. A non-zero value is a warning of memory problems. |
BCU System Diagnostics[21] |
Numeric |
Maximum number of paragraphs. |
BCU System Diagnostics[22] |
Numeric |
Number of VM (database RAM) memory blocks outstanding. |
BCU System Diagnostics[23] |
Numeric |
Paragraphs of VM (database RAM) memory remaining. |
BCU System Diagnostics[24] |
Numeric |
Minimum paragraphs of VM (database RAM) memory encountered. |
BCU System Diagnostics[25] |
Numeric |
Number of failing VM (database RAM) memory requests. A non-zero value is a warning of memory problems. |
BCU System Diagnostics[26] |
Numeric |
Maximum number of VM (database RAM) memory paragraphs. |
BCU System Diagnostics[27] |
Numeric |
Analog channel 0 (raw value of Universal input 1) |
BCU System Diagnostics[28] |
Numeric |
Analog channel 1 (raw value of Universal input 2) |
BCU System Diagnostics[29] |
Numeric |
Analog channel 2 (+5 ANAVCC, 2504 to 3064, nominal 2784) |
BCU System Diagnostics[30] |
Numeric |
Analog channel 3 (+5 VCC, 2504 to 3064, nominal 2784) |
BCU System Diagnostics[31] |
Numeric |
Analog channel 4 (Vunreg+, 2636 to 3164, nominal 2644) |
BCU System Diagnostics[32] |
Numeric |
Analog channel 5 (Vunreg+, 2636 to 3164, nominal 2644) |
BCU System Diagnostics[33] |
Numeric |
Analog channel 6 (-5, 2104 to 2432, nominal 3892) |
BCU System Diagnostics[34] |
Numeric |
Analog channel 7 (-12, 3100 to 3240, nominal 3532) |
BCU System Diagnostics[35] |
Numeric |
Analog channel 8 (Vunreg-, 3576 to 3908, nominal 3800) |
BCU System Diagnostics[36] |
Numeric |
Analog channel 9 (+12, 3132 to 3404, nominal 3265) |
BCU System Diagnostics[37] |
Numeric |
Analog channel 10 (VPP, 0000 to 1496, nominal 136) |
BCU System Diagnostics[38] |
Numeric |
Analog channel 11 (ref/2, 2028 to 2068, nominal 2048) |
BCU System Diagnostics[39] |
Numeric |
Number of UCM channel 1 NAKs. A high or increasing value may indicate problems with the UCM plugin card |
BCU System Diagnostics[40] |
Numeric |
Number of UCM channel 2 NAKs. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[41] |
Numeric |
Number of UCM channel 3 NAKS. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[42] |
Numeric |
Number of COM1 false interrupts. A high value may indicate a faulty IBM-bus serial card or modem. |
BCU System Diagnostics[43] |
Numeric |
Number of COM1 bytes in FIFO. |
BCU System Diagnostics[44] |
Numeric |
Number of DCD transitions. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[45] |
Numeric |
Number of NO DCD transitions. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[46] |
Numeric |
Any other Async related errors from Rx handler. A high or increasing value may indicate an incorrect serial cable. |
Binary Input 1[1] |
Binary |
Status of analog timed override switch if an analog input is connected to Universal Input 1 on the BCU. |
Binary Input 1[2] |
Binary |
Status of analog input failure if an analog input is connected to Universal Input 1 on the BCU. |
Binary Input 1[3] |
Binary |
Status of a normally open momentary binary input connected to Universal Input 1 on the BCU. |
Binary Input 1[4] |
Binary |
Status of a continuous binary input connected to Universal Input 1 on the BCU. |
Binary Input 2[1] |
Binary |
Status of analog timed override switch if an analog input is connected to Universal Input 2 on the BCU. |
Binary Input 2[2] |
Binary |
Status of analog input failure if an analog input is connected to Universal Input 2 on the BCU. |
Binary Input 2[3] |
Binary |
Status of a normally open momentary binary input connected to Universal Input 2 on the BCU. |
Binary Input 2[4] |
Binary |
Status of a continuous binary input connected to Universal Input 2 on the BCU. |
Firmware Revision |
Character |
Version number and date of factory software in the BCU. |
Local Date |
Date/Time Numeric |
Current Date in the BCU. |
Local Time |
Date/Time Numeric |
Current Time in the BCU. |
Max Message Length Supported |
Numeric |
Longest message the BCU can transmit or receive over the LAN. |
Mode: System Status |
Character |
This property indicates the BACnet defined device status. OPERATIONAL, OPERATIONAL READ ONLY, DOWNLOAD REQUIRED, DOWNLOAD IN PROGRESS, NON OPERATIONAL. |
Model Name |
Character |
Tracer Building Control Unit. |
Network Number |
Numeric |
The property indicates the unique numeric value of the comfort system (for example, network) or grouping to which the current BCU is connected. |
Number of APDU Retries |
Numeric |
This property indicates the number of times an APDU segment communication attempt will be made. |
Object Identifier |
Object ID |
Unique hexadecimal ID of this object. This ID is used internally to identify the object. |
Object Name |
Character |
This property is the name of the BCU object. |
Object Type |
Multi-State |
Designates object’s type (i.e., analog input, binary output, TCM, PCM, etc.). |
Percent BCU NVM Available |
Numeric |
This property indicates the percent of nonvolatile memory storage left for database use. |
Percent BCU VM Available |
Numeric |
This property indicates the percent of volatile memory storage left for database use. |
Percent Processor Idle Time |
Numeric |
Indicates the average idle time (%) of the processor for the first 5 minutes. |
Protocol Conformance Class |
Numeric |
Protocol class to which the BCU conforms. |
Protocol Version |
Character |
Protocol version the BCU is using. |
Segmentation Supported |
Binary |
Some APDUs are so large they must be broken into multiple "segments." This property indicates whether the segmentation is supported. |
Update Tag |
Numeric |
Value indicating last edit change of this object. |
Vendor Name |
Character |
Trane |
Property | Type | Description |
Analog Input 1[1] |
Numeric |
Value of linear input (0–10 VDC, 0–20 mA, or 100 to 100,000 ohms) connected to Universal Input 1 on the BCU. |
Analog Input 1[2] |
Numeric |
Value of Thermistor sensor (-20 F to 250 F) connected to Universal Input 1 on the BCU. |
Analog Input 1[3] |
Numeric |
Value of Platinum RTD sensor (-90 F to 250 F) connected to Universal Input 1 on the BCU. |
Analog Input 1[4] |
Numeric |
Value of Balco RTD sensor (-64 F to 250 F) connected to Universal Input 1 on the BCU. |
Analog Input 2[1] |
Numeric |
Value of linear input (0–10 VDC, 0–20 mA, or 100 to 100,000 ohms) connected to Universal Input 2 on the BCU. |
Analog Input 2[2] |
Numeric |
Value of Thermistor sensor (-20 F to 250 F) connected to Universal Input 2 on the BCU. |
Analog Input 2[3] |
Numeric |
Value of Platinum RTD sensor (-90 F to 250 F) connected to Universal Input 2 on the BCU. |
Analog Input 2[4] |
Numeric |
Value of Balco RTD sensor (-64 F to 250 F) connected to Universal Input 2 on the BCU. |
APDU Segment Timeout |
Binary |
Application Layer Protocol Data Units (APDUs) represent requests and results of applications communicating over BACnet. Some APDUs are so large they must be broken into multiple "segments." This property indicates the status of the timeout. |
APDU Timeout |
Numeric |
This property indicates the number of milliseconds for an APDU timeout. A timed out APDU is a failed APDU and is retried by the number of times defined by the "Number of APDU Retries" property. |
Application Software Revision |
Character |
Version number of BCU software saved at the workstation, not necessarily the version in the BCU. To read the actual version number in the BCU refer to the "Firmware Revision" property. |
BACnet Vendor ID |
Numeric |
This property indicates the vendor ID assigned by ASHRAE (used in BACnet communications). |
BCU Database Status |
Multi-State |
Indicates whether BCU’s database is Normal, Under Construction, or Cleared. |
BCU System Diagnostics[01] |
Numeric |
Number of BCU restarts since RAM was last cleared. |
BCU System Diagnostics[02] |
Numeric |
Number of interrupted Power Critical Regions. |
BCU System Diagnostics[03] |
Numeric |
ARCNET: Number of reconfigurations. A high or increasing number may indicate cable problems, or two nodes at the same address. Ethernet: Number of receive errors. A high or increasing number may indicate cable problems or too much traffic on the network. |
BCU System Diagnostics[04] |
Numeric |
Number of ARCNET/Ethernet aborted transmissions. |
BCU System Diagnostics[05] |
Numeric |
Number of ARCNET/Ethernet receive out of buffers. |
BCU System Diagnostics[06] |
Numeric |
Number of ARCNET/Ethernet messages retransmitted. |
BCU System Diagnostics[07] |
Numeric |
Number of ARCNET/Ethernet good transmissions, low 16 bits. |
BCU System Diagnostics[08] |
Numeric |
Number of ARCNET/Ethernet good transmissions, high 16 bits. |
BCU System Diagnostics[09] |
Numeric |
Number of ARCNET/Ethernet good receives, low 16 bits |
BCU System Diagnostics[10] |
Numeric |
Number of ARCNET/Ethernet good receives, high 16 bits. |
BCU System Diagnostics[11] |
Numeric |
Number of EEPROM re-tried writes. A non-zero value may indicate a bad or failing EEPROM. |
BCU System Diagnostics[12] |
Numeric |
Number of unexpected BACnet replies. A high or increasing value may indicate problems with a Workstation or remote BACnet device. |
BCU System Diagnostics[13] |
Numeric |
Number of BACnet Reject PDUs sent. A high or increasing value may indicate problems with a Workstation or remote BACnet device. |
BCU System Diagnostics[14] |
Numeric |
Number of UCM channel 1 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[15] |
Numeric |
Number of UCM channel 2 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[16] |
Numeric |
Number of UCM channel 3 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[17] |
Numeric |
Number of UCM channel 4 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[18] |
Numeric |
Number of memory blocks outstanding. |
BCU System Diagnostics[19] |
Numeric |
Paragraphs of memory remaining. |
BCU System Diagnostics[20] |
Numeric |
Minimum paragraphs of memory encountered. |
BCU System Diagnostics[21] |
Numeric |
Number of failing memory requests. A non-zero value is a warning of memory problems. |
BCU System Diagnostics[22] |
Numeric |
Maximum number of paragraphs. |
BCU System Diagnostics[23] |
Numeric |
Number of VM (database RAM) memory blocks outstanding. |
BCU System Diagnostics[24] |
Numeric |
Paragraphs of VM (database RAM) memory remaining. |
BCU System Diagnostics[25] |
Numeric |
Minimum paragraphs of VM (database RAM) memory encountered. |
BCU System Diagnostics[26] |
Numeric |
Number of failing VM (database RAM) memory requests. A non-zero value is a warning of memory problems. |
BCU System Diagnostics[27] |
Numeric |
Maximum number of VM (database RAM) memory paragraphs. |
BCU System Diagnostics[28] |
Numeric |
Number of CCBs allocated from heap. |
BCU System Diagnostics[29] |
Numeric |
Number of CCBs released to heap. |
BCU System Diagnostics[30] |
Numeric |
Number of CCBs gotten. |
BCU System Diagnostics[31] |
Numeric |
Number of CCBs released. |
BCU System Diagnostics[32] |
Numeric |
Number of BACnet devices marked down. A high or increasing value may indicate problems with BACnet communications. |
BCU System Diagnostics[33] |
Numeric |
Number of BACnet retries. A high or increasing value may indicate problems with BACnet communications. |
BCU System Diagnostics[34] |
Numeric |
Number of failed sendto in BACnet/IP. |
BCU System Diagnostics[35] |
Numeric |
Last error return from failed sendto. |
BCU System Diagnostics[36] |
Numeric |
No DCU available. A high or increasing value may indicate problems with BACnet/IP communications. |
BCU System Diagnostics[40] |
Numeric |
Number of UCM channel 1 NAKs. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[41] |
Numeric |
Number of UCM channel 2 NAKs. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[42] |
Numeric |
Number of UCM channel 3 NAKS. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[43] |
Numeric |
Number of UCM channel 4 NAKS. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[44] |
Numeric |
Number of COM1 false interrupts. A high value may indicate a faulty IBM-bus serial card or modem. |
BCU System Diagnostics[45] |
Numeric |
Number of COM1 bytes in FIFO. |
BCU System Diagnostics[46] |
Numeric |
Number of DCD transitions. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[47] |
Numeric |
Number of NO DCD transitions. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[48] |
Numeric |
Any other Async related errors from Rx handler. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[49] |
Numeric |
PTP messages dumped due to queue overflow. A high or increasing value may indicate problems with BACnet communications. |
Binary Input 1[1] |
Binary |
Status of analog timed override switch if an analog input is connected to Universal Input 1 on the BCU. |
Binary Input 1[2] |
Binary |
Status of analog input failure if an analog input is connected to Universal Input 1 on the BCU. |
Binary Input 1[3] |
Binary |
Status of a normally open momentary binary input connected to Universal Input 1 on the BCU. |
Binary Input 1[4] |
Binary |
Status of a continuous binary input connected to Universal Input 1 on the BCU. |
Binary Input 2[1] |
Binary |
Status of analog timed override switch if an analog input is connected to Universal Input 2 on the BCU. |
Binary Input 2[2] |
Binary |
Status of analog input failure if an analog input is connected to Universal Input 2 on the BCU. |
Binary Input 2[3] |
Binary |
Status of a normally open momentary binary input connected to Universal Input 2 on the BCU. |
Binary Input 2[4] |
Binary |
Status of a continuous binary input connected to Universal Input 2 on the BCU. |
Firmware Revision |
Character |
Version number and date of factory software in the BCU. |
Local Date |
Date/Time Numeric |
Current Date in the BCU. |
Local Time |
Date/Time Numeric |
Current Time in the BCU. |
Max Message Length Supported |
Numeric |
Longest message the BCU can transmit or receive over the LAN. |
Mode: System Status |
Character |
This property indicates the BACnet defined device status. OPERATIONAL, OPERATIONAL READ ONLY, DOWNLOAD REQUIRED, DOWNLOAD IN PROGRESS, NON OPERATIONAL. |
Model Name |
Character |
Tracer Building Control Unit. |
Network Number |
Numeric |
The property indicates the unique numeric value of the comfort system (for example, network) or grouping to which the current BCU is connected. |
Number of APDU Retries |
Numeric |
This property indicates the number of times an APDU segment communication attempt will be made. |
Object Identifier |
Object ID |
Unique hexadecimal ID of this object. This ID is used internally to identify the object. |
Object Name |
Character |
This property is the name of the BCU object. |
Object Type |
Multi-State |
Designates object’s type (i.e., analog input, binary output, TCM, PCM, etc.). |
Percent BCU NVM Available |
Numeric |
This property indicates the percent of nonvolatile memory storage left for database use. |
Percent BCU VM Available |
Numeric |
This property indicates the percent of volatile memory storage left for database use. |
Percent Processor Idle Time |
Numeric |
Indicates the average idle time (%) of the processor for the first 5 minutes. |
Protocol Conformance Class |
Numeric |
Protocol class to which the BCU conforms. |
Protocol Version |
Character |
Protocol version the BCU is using. |
Segmentation Supported |
Binary |
Some APDUs are so large they must be broken into multiple "segments." This property indicates the whether segmentation is supported. |
Update Tag |
Numeric |
Value indicating last edit change of this object. |
Vendor Name |
Character |
Trane |
Property | Type | Description |
Analog Input 1[1] |
Numeric |
When Binary Input 1 on the BMTX is used as a pulse meter this property indicates the rate in pulses per minute. (This rate is calculated by looking at the last ten pulses and averaging the time between pulses for all of the pulses that occurred within the last minute. Pulses older than 1 minute are discarded.) |
Analog Input 1[2] |
Numeric |
When Binary Input 1 on the BMTX is used as a pulse meter this property indicates the number of pulse counts since the last read. (Each time this is read, the value is returned and the stored value is zeroed. If this value gets to 999,999,999, it is rolled over to 0. |
Analog Input 1[3] |
Numeric |
When Binary Input 1 on the BMTX is used as a pulse meter this property indicates the number of pulse counts since the BCU last had a power reset. (If this value gets to 999,999,999, it is rolled over to 0.) |
Analog Input 1[4] |
Numeric |
Not Used. This index does nothing and will always return 0.0. It will not return a property read error. |
Analog Input 2[1] |
Numeric |
When Binary Input 2 on the BMTX is used as a pulse meter this property indicates the rate in pulses per minute. (This rate is calculated by looking at the last ten pulses and averaging the time between pulses for all of the pulses that occurred within the last minute. Pulses older than 1 minute are discarded.) |
Analog Input 2[2] |
Numeric |
When Binary Input 2 on the BMTX is used as a pulse meter this property indicates the number of pulse counts since the last read. (Each time this is read, the value is returned and the stored value is zeroed. If this value gets to 999,999,999, it is rolled over to 0. |
Analog Input 2[3] |
Numeric |
When Binary Input 2 on the BMTX is used as a pulse meter this property indicates the number of pulse counts since the BCU last had a power reset. (If this value gets to 999,999,999, it is rolled over to 0.) |
Analog Input 2[4] |
Numeric |
Not Used. This index does nothing and will always return 0.0. It will not return a property read error. |
APDU Segment Timeout |
Binary |
Application Layer Protocol Data Units (APDUs) represent requests and results of applications communicating over BACnet. Some APDUs are so large they must be broken into multiple "segments." This property indicates the status of the timeout. |
APDU Timeout |
Numeric |
This property indicates the number of milliseconds for an APDU timeout. A timed out APDU is a failed APDU and is retried by the number of times defined by the "Number of APDU Retries" property. |
Application Software Revision |
Character |
Version number of BCU software saved at the workstation, not necessarily the version in the BCU. To read the actual version number in the BCU refer to the "Firmware Revision" property. |
BACnet Vendor ID |
Numeric |
This property indicates the vendor ID assigned by ASHRAE (used in BACnet communications). |
BCU Database Status |
Multi-State |
Indicates whether BCU’s database is Normal, Under Construction, or Cleared. |
BCU System Diagnostics[01] |
Numeric |
Number of BCU restarts since RAM was last cleared. |
BCU System Diagnostics[02] |
Numeric |
Number of interrupted Power Critical Regions. |
BCU System Diagnostics[03] |
Numeric |
Ethernet: Number of receive errors. A high or increasing number may indicate cable problems or too much traffic on the network |
BCU System Diagnostics[04] |
Numeric |
Number of Ethernet aborted transmissions. |
BCU System Diagnostics[05] |
Numeric |
Number of Ethernet receive out of buffers. |
BCU System Diagnostics[06] |
Numeric |
Number of Ethernet messages retransmitted. |
BCU System Diagnostics[07] |
Numeric |
Number of Ethernet good transmissions, low 16 bits. |
BCU System Diagnostics[08] |
Numeric |
Number of Ethernet good transmissions, high 16 bits. |
BCU System Diagnostics[09] |
Numeric |
Number of Ethernet good receives, low 16 bits |
BCU System Diagnostics[10] |
Numeric |
Number of Ethernet good receives, high 16 bits. |
BCU System Diagnostics[11] |
Numeric |
Number of EEPROM re-tried writes. A non-zero value may indicate a bad or failing EEPROM. |
BCU System Diagnostics[12] |
Numeric |
Number of unexpected BACnet replies. A high or increasing value may indicate problems with a Workstation or remote BACnet device. |
BCU System Diagnostics[13] |
Numeric |
Number of BACnet Reject PDUs sent. A high or increasing value may indicate problems with a Workstation or remote BACnet device. |
BCU System Diagnostics[14] |
Numeric |
Number of UCM channel 1 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[15] |
Numeric |
Number of UCM channel 2 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[16] |
Numeric |
Number of UCM channel 3 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[17] |
Numeric |
Number of UCM channel 4 reinits. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[18] |
Numeric |
Number of memory blocks outstanding. |
BCU System Diagnostics[19] |
Numeric |
Paragraphs of memory remaining. |
BCU System Diagnostics[20] |
Numeric |
Minimum paragraphs of memory encountered. |
BCU System Diagnostics[21] |
Numeric |
Number of failing memory requests. A non-zero value is a warning of memory problems. |
BCU System Diagnostics[22] |
Numeric |
Maximum number of paragraphs. |
BCU System Diagnostics[23] |
Numeric |
Number of VM (database RAM) memory blocks outstanding. |
BCU System Diagnostics[24] |
Numeric |
Paragraphs of VM (database RAM) memory remaining. |
BCU System Diagnostics[25] |
Numeric |
Minimum paragraphs of VM (database RAM) memory encountered. |
BCU System Diagnostics[26] |
Numeric |
Number of failing VM (database RAM) memory requests. A non-zero value is a warning of memory problems. |
BCU System Diagnostics[27] |
Numeric |
Maximum number of VM (database RAM) memory paragraphs. |
BCU System Diagnostics[28] |
Numeric |
Number of CCBs allocated from heap. |
BCU System Diagnostics[29] |
Numeric |
Number of CCBs released to heap. |
BCU System Diagnostics[30] |
Numeric |
Number of CCBs gotten. |
BCU System Diagnostics[31] |
Numeric |
Number of CCBs released. |
BCU System Diagnostics[32] |
Numeric |
Number of BACnet devices marked down. A high or increasing value may indicate problems with BACnet communications. |
BCU System Diagnostics[33] |
Numeric |
Number of BACnet retries. A high or increasing value may indicate problems with BACnet communications. |
BCU System Diagnostics[34] |
Numeric |
Number of failed sendto in BACnet/IP. |
BCU System Diagnostics[35] |
Numeric |
Last error return from failed sendto. |
BCU System Diagnostics[36] |
Numeric |
No DCU available. A high or increasing value may indicate problems with BACnet/IP communications. |
BCU System Diagnostics[40] |
Numeric |
Number of UCM channel 1 NAKs. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[41] |
Numeric |
Number of UCM channel 2 NAKs. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[42] |
Numeric |
Number of UCM channel 3 NAKS. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[43] |
Numeric |
Number of UCM channel 4 NAKS. A high or increasing value may indicate problems with the UCM plugin card. |
BCU System Diagnostics[44] |
Numeric |
Number of COM1 false interrupts. A high value may indicate a faulty IBM-bus serial card or modem. |
BCU System Diagnostics[45] |
Numeric |
Number of COM1 bytes in FIFO. |
BCU System Diagnostics[46] |
Numeric |
Number of DCD transitions. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[47] |
Numeric |
Number of NO DCD transitions. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[48] |
Numeric |
Any other Async related errors from Rx handler. A high or increasing value may indicate an incorrect serial cable. |
BCU System Diagnostics[49] |
Numeric |
PTP messages dumped due to queue overflow. A high or increasing value may indicate problems with BACnet communications. |
Binary Input 1[1] |
Binary |
Status of analog timed override switch if an analog input is connected to Binary Input 1 on the BCU. True if the binary input has been closed any time in the last two minutes. Otherwise, false. |
Binary Input 1[2] |
Binary |
Status of analog input failure if an analog input is connected to Binary Input 1 on the BCU. True if the binary input has not been closed at any time in the last two minutes. Otherwise, false. |
Binary Input 1[3] |
Binary |
Status of a normally open momentary binary input connected to Binary Input 1 on the BCU. True if the binary input has been closed any time in the last two minutes. Otherwise, false. |
Binary Input 1[4] |
Binary |
Status of a continuous binary input connected to Binary Input 1 on the BCU. |
Binary Input 2[1] |
Binary |
Status of analog timed override switch if an analog input is connected to Binary Input 2 on the BCU. True if the binary input has been closed any time in the last two minutes. Otherwise, false. |
Binary Input 2[2] |
Binary |
Status of analog input failure if an analog input is connected to Binary Input 2 on the BCU. True if the binary input has not been closed at any time in the last two minutes. Otherwise, false. |
Binary Input 2[3] |
Binary |
Status of a normally open momentary binary input connected to Binary Input 2 on the BCU. True if the binary input has been closed any time in the last two minutes. Otherwise, false. |
Binary Input 2[4] |
Binary |
Status of a continuous binary input connected to Binary Input 2 on the BCU. |
Firmware Revision |
Character |
Version number and date of factory software in the BCU. |
Local Date |
Date/Time Numeric |
Current Date in the BCU. |
Local Time |
Date/Time Numeric |
Current Time in the BCU. |
Max Message Length Supported |
Numeric |
Longest message the BCU can transmit or receive over the LAN. |
Mode: System Status |
Character |
This property indicates the BACnet defined device status. OPERATIONAL, OPERATIONAL READ ONLY, DOWNLOAD REQUIRED, DOWNLOAD IN PROGRESS, NON OPERATIONAL. |
Model Name |
Character |
Tracer Building Control Unit. |
Network Number |
Numeric |
The property indicates the unique numeric value of the comfort system (for example, network) or grouping to which the current BCU is connected. |
Number of APDU Retries |
Numeric |
This property indicates the number of times an APDU segment communication attempt will be made. |
Object Identifier |
Object ID |
Unique hexadecimal ID of this object. This ID is used internally to identify the object. |
Object Name |
Character |
This property is the name of the BCU object. |
Object Type |
Multi-State |
Designates object’s type (i.e., analog input, binary output, TCM, PCM, etc.). |
Percent BCU NVM Available |
Numeric |
This property indicates the percent of nonvolatile memory storage left for database use. |
Percent BCU VM Available |
Numeric |
This property indicates the percent of volatile memory storage left for database use. |
Percent Processor Idle Time |
Numeric |
Indicates the average idle time (%) of the processor for the first 5 minutes. |
Protocol Conformance Class |
Numeric |
Protocol class to which the BCU conforms. |
Protocol Version |
Character |
Protocol version the BCU is using. |
Segmentation Supported |
Binary |
Some APDUs are so large they must be broken into multiple "segments." This property indicates whether the segmentation is supported. |
Update Tag |
Numeric |
Value indicating last edit change of this object. |
Vendor Name |
Character |
Trane |