Coverage
codes
Filter by brand / controller
Browse codes (429 in current scope) , All codes in scope , Johnson Controls Metasys · MET-ALM-001, NAE CPU Usage High Johnson Controls Metasys · MET-ALM-002, NAE CPU Temperature High Johnson Controls Metasys · MET-ALM-003, NAE Memory Usage High Johnson Controls Metasys · MET-ALM-004, NAE Flash Usage High Johnson Controls Metasys · MET-ALM-005, NAE Audit Rate High Johnson Controls Metasys · MET-ALM-006, NAE Event Rate High Johnson Controls Metasys · MET-ALM-007, NAE Events Lost Johnson Controls Metasys · MET-ALM-008, NAE Samples Lost Johnson Controls Metasys · MET-ALM-009, NAE Sample Rate High Johnson Controls Metasys · MET-ALM-010, NAE Transfer Buffer Full Johnson Controls Metasys · MET-ALM-011, NAE BACnet Broadcast Receive Rate High Johnson Controls Metasys · MET-ALM-012, NAE COV Receive Rate High Johnson Controls Metasys · MET-ALM-013, SNE/SNC Events Lost Counter Incrementing Johnson Controls Metasys · MET-ALM-014, Analog Alarm – High Alarm Johnson Controls Metasys · MET-ALM-015, Analog Alarm – Low Alarm Johnson Controls Metasys · MET-ALM-016, Analog Alarm – High Warning Johnson Controls Metasys · MET-ALM-017, Analog Alarm – Low Warning Johnson Controls Metasys · MET-ALM-018, Binary/Multistate Alarm – Trouble Johnson Controls Metasys · MET-ALM-019, Alarm State – Offline Johnson Controls Metasys · MET-ALM-020, Alarm State – Unreliable Johnson Controls Metasys · MET-ALM-021, Alarm State – Command Failure (OnOff Action Failure) Johnson Controls Metasys · MET-ALM-022, Alarm State – Shutdown Johnson Controls Metasys · MET-ALM-023, N2 Bus Communication Loss Johnson Controls Metasys · MET-ALM-024, SA Bus Communication Loss Johnson Controls Metasys · MET-ALM-025, MS/TP Token Pass Failure Johnson Controls Metasys · MET-ALM-026, Ethernet Link Down Johnson Controls Metasys · MET-ALM-027, BACnet Object Event State – Fault Johnson Controls Metasys · MET-ALM-028, BACnet Object Event State – OffNormal Johnson Controls Metasys · MET-ALM-029, BACnet Object Event State – High Limit Johnson Controls Metasys · MET-ALM-030, BACnet Object Event State – Low Limit Johnson Controls Metasys · MET-ALM-031, Life Safety Alarm Johnson Controls Metasys · MET-ALM-032, Metasys Alarm Value Enum – FAU (Fault) Johnson Controls Metasys · MET-ALM-033, Metasys Alarm Value Enum – OFN (Off Normal) Johnson Controls Metasys · MET-ALM-034, Metasys Alarm Value Enum – HL (High Limit) Johnson Controls Metasys · MET-ALM-035, Metasys Alarm Value Enum – LL (Low Limit) Johnson Controls Metasys · MET-ALM-036, Metasys Alarm Value Enum – ALM (Alarm) Johnson Controls Metasys · MET-ALM-037, Metasys Alarm Value Enum – SHT (Shutdown) Johnson Controls Metasys · MET-ALM-038, Metasys Alarm Value Enum – UNR (Unreliable) Johnson Controls Metasys · MET-ALM-039, Metasys Alarm Value Enum – OFL (Offline) Johnson Controls Metasys · MET-ALM-040, Alarm Flags Enum – Irregular Action (1) Johnson Controls Metasys · MET-DIAG-001, NAE Power LED Off Johnson Controls Metasys · MET-DIAG-002, FEC/MEC Communication Fault on FC Trunk Johnson Controls Metasys · MET-DIAG-003, ADX/ADS Communication Failure Johnson Controls Metasys · MET-DIAG-004, Invalid Object ID (BACnet Server Fault Cause) Johnson Controls Metasys · MET-DIAG-005, BACnet Server Capability Not Licensed Johnson Controls Metasys · MET-NET-001, SNMP Trap Send Failure (DDA) Johnson Controls Metasys · MET-NET-002, Email DDA Send Failure Johnson Controls Metasys · MET-BAC-001, BACnet Duplicate Device ID Detected Johnson Controls Metasys · MET-BAC-002, BACnet Network Number Conflict Johnson Controls Metasys · MET-BAC-003, MS/TP Lost Token Johnson Controls Metasys · MET-BAC-004, BACnet Device Discovered in Fault (orange) Johnson Controls Metasys · MET-BAC-005, COV StatusFlags Reporting Change Johnson Controls Metasys · MET-BAC-006, Proxy Point Disabled by Default (Commandable Object) Johnson Controls Metasys · MET-BAC-007, Bacnet Port Status Fault Johnson Controls Metasys · MET-SEC-001, Metasys Hardening – Default Password Warning Johnson Controls Metasys · MET-ALM-041, Alarm State – Low Warning Johnson Controls Metasys · MET-ALM-042, Alarm State – High Warning Johnson Controls Metasys · MET-ALM-043, Alarm State – Low Alarm Johnson Controls Metasys · MET-ALM-044, Alarm State – High Alarm Johnson Controls Metasys · MET-ALM-045, Alarm State – Fault Johnson Controls Metasys · MET-ALM-046, Alarm State – Trouble Johnson Controls Metasys · MET-ALM-047, Alarm State – Offline Johnson Controls Metasys · MET-ALM-048, Alarm State – Shutdown Johnson Controls Metasys · MET-ALM-049, Alarm State – Unreliable Johnson Controls Metasys · MET-ALM-050, Alarm State – Above Setpoint Johnson Controls Metasys · MET-ALM-051, Alarm State – Below Setpoint Johnson Controls Metasys · MET-ALM-052, Alarm State – Unoccupied Johnson Controls Metasys · MET-ALM-053, Metasys BACnet Event Type – To Offnormal Johnson Controls Metasys · MET-ALM-054, Metasys BACnet Event Type – To Fault Johnson Controls Metasys · MET-ALM-055, Metasys BACnet Event Type – To Normal Johnson Controls Metasys · MET-OBJ-001, Analog Input – Out of Range (OverRange) Johnson Controls Metasys · MET-OBJ-002, Analog Input – Under Range (UnderRange) Johnson Controls Metasys · MET-OBJ-003, Binary Input – Open Circuit Johnson Controls Metasys · MET-OBJ-004, Binary Input – Short Circuit Johnson Controls Metasys · MET-OBJ-005, Analog Output – Feedback Deviation Johnson Controls Metasys · MET-OBJ-006, Binary Output – Supervision Failure Johnson Controls Metasys · MET-OBJ-007, Trend Log – Buffer Full Johnson Controls Metasys · MET-OBJ-008, Command Priority – Override Active Johnson Controls Metasys · MET-FEC-001, FEC – SA Bus Communication Failure Johnson Controls Metasys · MET-FEC-002, FEC – FC Bus Communication Failure Johnson Controls Metasys · MET-FEC-003, FEC – Application Program Stopped Johnson Controls Metasys · MET-FEC-004, FEC – Memory Backup Battery Low Johnson Controls Metasys · MET-SNE-001, SNE – CPU Usage Alarm Johnson Controls Metasys · MET-SNE-002, SNE – Events Lost Johnson Controls Metasys · MET-SNE-003, SNE – Transfer Buffer Full Johnson Controls Metasys · MET-SNE-004, SNE – BACnet Broadcast Receive Rate High Johnson Controls Metasys · MET-ADX-001, ADX – Archive Failure Johnson Controls Metasys · MET-ADX-002, ADX – Database Connection Failure Johnson Controls Metasys · MET-ENUM-001, Reliability – No Sensor Johnson Controls Metasys · MET-ENUM-002, Reliability – Over Range Johnson Controls Metasys · MET-ENUM-003, Reliability – Under Range Johnson Controls Metasys · MET-ENUM-004, Reliability – Open Loop Johnson Controls Metasys · MET-ENUM-005, Reliability – Short Circuit Johnson Controls Metasys · MET-ENUM-006, Reliability – Communication Failure Johnson Controls Metasys · MET-MALM-001, M-Alarm – Zone Intrusion Detected Johnson Controls Metasys · MET-MALM-002, M-Alarm – Panel Offline / Communication Fault Honeywell / Tridium Niagara · N4-COM-001, Platform Daemon Not Running (niagarad failure) Honeywell / Tridium Niagara · N4-COM-002, Workbench Connection Refused / Timeout Honeywell / Tridium Niagara · N4-COM-003, Invalid RTC Date After Clean/Restore Honeywell / Tridium Niagara · N4-COM-004, SD Card Missing / Host ID Mismatch (JACE-9000) Honeywell / Tridium Niagara · N4-COM-005, Dual Default Gateway Misconfiguration (JACE-9000) Honeywell / Tridium Niagara · N4-COM-006, First Boot Long Delay (JACE-9000) Honeywell / Tridium Niagara · N4-COM-007, Commissioning Not Completed Before Station Copy Honeywell / Tridium Niagara · N4-BAC-001, BACnet Proxy Point Fault – Invalid Object ID Honeywell / Tridium Niagara · N4-BAC-002, BACnet Proxy Point Status – {stale} Honeywell / Tridium Niagara · N4-BAC-003, BACnet Worker Pool Overload Honeywell / Tridium Niagara · N4-BAC-004, BACnet Upload On Start Timeout Honeywell / Tridium Niagara · N4-BAC-005, Deadlock – FoxDispatcher and Bacnet WriteWorker Honeywell / Tridium Niagara · N4-BAC-006, MSTP Does Not Exit Wait-For-Reply State Honeywell / Tridium Niagara · N4-BAC-007, Bacnet Event Handler – AE-AVN-A Ack Required Flag Wrong Honeywell / Tridium Niagara · N4-ALM-001, Alarm Service – AlarmClass Deleted, Alarms Disappearing Honeywell / Tridium Niagara · N4-ALM-002, Alarm Class – Change of State (COS) Alarm Honeywell / Tridium Niagara · N4-ALM-003, BACnet Alarm – Out of Range Honeywell / Tridium Niagara · N4-ALM-004, BACnet Alarm – Change of State Honeywell / Tridium Niagara · N4-ALM-005, BACnet Alarm – Command Failure Honeywell / Tridium Niagara · N4-ALM-006, BACnet Alarm – Floating Limit Honeywell / Tridium Niagara · N4-ALM-007, BACnet Alarm – Change of Life Safety Honeywell / Tridium Niagara · N4-ALM-008, BACnet Alarm – Buffer Ready Honeywell / Tridium Niagara · N4-ALM-009, BACnet Fault Type – Fault State Honeywell / Tridium Niagara · N4-ALM-010, BACnet Fault Type – Fault Status Flags Honeywell / Tridium Niagara · N4-ALM-011, Out of Memory Error on Supervisor Start Honeywell / Tridium Niagara · N4-BAC-008, BACnet Network Number -1 (Inoperative) Honeywell / Tridium Niagara · N4-PLAT-001, Niagara License Missing or Invalid Honeywell / Tridium Niagara · N4-PLAT-002, Policy File Verification Error Honeywell / Tridium Niagara · N4-MOD-001, Modbus Driver – Device Not Responding Honeywell / Tridium Niagara · N4-PLAT-003, Java Security Failed Signing Verification Honeywell / Tridium Niagara · N4-BAC-009, Niagara AX Proxy Points Poll 'Additional Properties' Missing Honeywell / Tridium Niagara · N4-ALM-012, BACnet Program Error – LoadFailed Honeywell / Tridium Niagara · N4-ALM-013, BACnet Backup State – Backup Failure Honeywell / Tridium Niagara · N4-ALM-014, Ping Failure Alarm Honeywell / Tridium Niagara · N4-ALM-015, BACnet Event State – Life Safety Alarm Honeywell / Tridium Niagara · N4-PLAT-004, 8.x Release – Niagara 4.8 AckedTransitions ToNormal Fix Honeywell / Tridium Niagara · N4-ALM-016, FDD Fault – Sensor Failure (Niagara Analytics) Honeywell / Tridium Niagara · N4-ALM-017, FDD Fault – Blind/Shade Opening Failure Honeywell / Tridium Niagara · N4-ALM-018, FDD Fault – Bad Energy Data Honeywell / Tridium Niagara · N4-ALM-019, FDD Fault – Fire Pump Operation Honeywell / Tridium Niagara · N4-ALM-020, FDD Fault – Double Dipping Data Honeywell / Tridium Niagara · N4-JACE-001, JACE SD Card Not Detected Honeywell / Tridium Niagara · N4-JACE-002, JACE RTC Clock Not Set Honeywell / Tridium Niagara · N4-JACE-003, JACE Dual-Port Gateway Configuration Error Honeywell / Tridium Niagara · N4-JACE-004, JACE niagarad Service Failed to Start Honeywell / Tridium Niagara · N4-JACE-005, JACE License File Missing or Corrupted Honeywell / Tridium Niagara · N4-DRIVER-001, BACnet Network Driver – Ping Failed Honeywell / Tridium Niagara · N4-DRIVER-002, BACnet Proxy Point – Stale Data Honeywell / Tridium Niagara · N4-DRIVER-003, Niagara Modbus TCP Driver – Connection Refused Honeywell / Tridium Niagara · N4-DRIVER-004, Niagara Modbus RTU Driver – Bus Error Honeywell / Tridium Niagara · N4-SEC-001, Niagara – Invalid Certificate (TLS) Honeywell / Tridium Niagara · N4-SEC-002, Niagara – User Account Locked Honeywell / Tridium Niagara · N4-SYS-001, Niagara Station – Out of Heap Memory Honeywell / Tridium Niagara · N4-SYS-002, Niagara Station – Database Load Error Honeywell / Tridium Niagara · N4-SYS-003, Niagara – Module Install Failed Honeywell / Tridium Niagara · N4-SYS-004, Niagara – Workbench Connection Refused Honeywell / Tridium Niagara · N4-ANALYTICS-001, Niagara Analytics – Fault Detection Rule Triggered Honeywell / Tridium Niagara · N4-ANALYTICS-002, Niagara Analytics – Missing History Data Distech Controls · DC-SYS-1000, General System Exception Distech Controls · DC-SYS-1001, Missing Hardware Element Distech Controls · DC-SYS-1002, Internal Error Distech Controls · DC-SYS-1003, Permission Denied Distech Controls · DC-SYS-1004, Resource Not Found Distech Controls · DC-REQ-1100, Decoding Error Distech Controls · DC-REQ-1101, Encoding Error Distech Controls · DC-REQ-1102, Unsupported Content Type Distech Controls · DC-REQ-1103, Unsupported Media Type Distech Controls · DC-REQ-1104, Required Value Missing Distech Controls · DC-REQ-1105, Method Not Supported Distech Controls · DC-REQ-1106, Missing Request Header Attribute Distech Controls · DC-REQ-1107, Invalid URL Value Distech Controls · DC-REQ-1108, File Upload Exception Distech Controls · DC-REQ-1109, Invalid Request Header Entity Distech Controls · DC-REQ-1110, Invalid or Malformed Request Distech Controls · DC-REQ-1111, Incomplete Data Distech Controls · DC-REQ-1112, Invalid Value Distech Controls · DC-BAC-1200, BACnet Property Issue Distech Controls · DC-NET-1300, Bad Network Data / Network Configuration Error Distech Controls · DC-FILE-1400, File or Directory Not Found Distech Controls · DC-FILE-1401, File or Directory Locked Distech Controls · DC-FILE-1402, Delete Processing Error Distech Controls · DC-FILE-1403, Insufficient File Permissions Distech Controls · DC-FILE-1404, Directory Already Exists Distech Controls · DC-FILE-1405, File Creation Error Distech Controls · DC-AUTH-1500, Radius Authentication Test Failed Distech Controls · DC-ECB-ALM-001, ECB-400/450/453 – Active Alarm State Distech Controls · DC-ECB-ALM-002, ECB/ECx BACnet Intrinsic Alarm – Object Reliability Fault Distech Controls · DC-ECB-ALM-003, ECLYPSE HTTP 500 – Internal Server Error Distech Controls · DC-ECB-ALM-004, ECLYPSE HTTP 503 – Service Unavailable Distech Controls · DC-JACE-001, EC-Net JACE Commissioning Failure Distech Controls · DC-BAC-1201, BACnet Read Property Failed Distech Controls · DC-BAC-1202, BACnet Write Property Rejected Distech Controls · DC-BAC-1203, BACnet Device Not Found Distech Controls · DC-NET-1301, ECLYPSE Network Timeout Distech Controls · DC-USER-1501, User Account Not Found Distech Controls · DC-USER-1502, Insufficient User Privileges Distech Controls · DC-ECB-ALM-005, ECB/ECx – Room Temperature Out of Range Distech Controls · DC-ECB-ALM-006, ECB/ECx – CO2 High Alarm Distech Controls · DC-ECB-ALM-007, ECB/ECx – Fan Overload / Motor Protection Distech Controls · DC-ECB-ALM-008, ECB/ECx – Freeze Protection Alarm Distech Controls · DC-SYS-1005, ECLYPSE System – Watchdog Reboot Distech Controls · DC-ECBOS-001, EC-BOS – BACnet Router Initialization Failed Distech Controls · DC-ECBOS-002, EC-BOS – Alarm Notification Email Failed Schneider Electric EcoStruxure Building Operation · EBO-A-001, BACnet Did Not Start Schneider Electric EcoStruxure Building Operation · EBO-A-002, BACnet Server Failure Schneider Electric EcoStruxure Building Operation · EBO-A-003, A Configuration Error During Startup Schneider Electric EcoStruxure Building Operation · EBO-A-004, Log Data Transfer Missed Schneider Electric EcoStruxure Building Operation · EBO-A-005, Log Sample Missed Schneider Electric EcoStruxure Building Operation · EBO-A-006, Alarm Signal Trigger Buffer Full Schneider Electric EcoStruxure Building Operation · EBO-A-007, Archive Directory Does Not Exist Schneider Electric EcoStruxure Building Operation · EBO-A-008, Archiving Failed – Ongoing Operation Schneider Electric EcoStruxure Building Operation · EBO-A-009, Blacklisted Device Detected Schneider Electric EcoStruxure Building Operation · EBO-C-001, Communication Failed Schneider Electric EcoStruxure Building Operation · EBO-C-002, Communication Failed – Authentication Error Schneider Electric EcoStruxure Building Operation · EBO-C-003, Communication Failed – Authorization Error Schneider Electric EcoStruxure Building Operation · EBO-C-004, Communication Failed – Configuration Error Schneider Electric EcoStruxure Building Operation · EBO-C-005, Communication Failed – Domain Not Available Schneider Electric EcoStruxure Building Operation · EBO-C-006, Communication Failed – Hostname Invalid Schneider Electric EcoStruxure Building Operation · EBO-C-007, Communication Failed – Version Mismatch Schneider Electric EcoStruxure Building Operation · EBO-C-008, Communication Failed – Unexpected Server Fullpath Schneider Electric EcoStruxure Building Operation · EBO-C-009, Communication Failed – Unexpected Server Type Schneider Electric EcoStruxure Building Operation · EBO-C-010, Corrupt Backup Set Detected Schneider Electric EcoStruxure Building Operation · EBO-CWS-001, CWS Alarm Poll Failed Schneider Electric EcoStruxure Building Operation · EBO-CWS-002, CWS Browse Failed Schneider Electric EcoStruxure Building Operation · EBO-CWS-003, CWS Get History Failed Schneider Electric EcoStruxure Building Operation · EBO-CWS-004, CWS Get Object Failed Schneider Electric EcoStruxure Building Operation · EBO-CWS-005, CWS Method Error Schneider Electric EcoStruxure Building Operation · EBO-CWS-006, CWS Value Poll Failed Schneider Electric EcoStruxure Building Operation · EBO-D-001, Database File Is Corrupt Schneider Electric EcoStruxure Building Operation · EBO-D-002, Database Update Failed Schneider Electric EcoStruxure Building Operation · EBO-D-003, Device Address Changed Schneider Electric EcoStruxure Building Operation · EBO-D-004, Device Offline Schneider Electric EcoStruxure Building Operation · EBO-D-005, Driver Loading Disabled Schneider Electric EcoStruxure Building Operation · EBO-D-006, Driver Unexpectedly Timed Out Schneider Electric EcoStruxure Building Operation · EBO-D-007, Duplicate Device Address Schneider Electric EcoStruxure Building Operation · EBO-D-008, Duplicate Device Identifier Schneider Electric EcoStruxure Building Operation · EBO-D-009, Duplicate Device Name Schneider Electric EcoStruxure Building Operation · EBO-D-010, Duplicate Network Identifier Schneider Electric EcoStruxure Building Operation · EBO-D-011, Duplicate of Local Network Schneider Electric EcoStruxure Building Operation · EBO-E-001, Email Service Configuration Error Schneider Electric EcoStruxure Building Operation · EBO-E-002, Email Service Failed to Connect to SMTP Server Schneider Electric EcoStruxure Building Operation · EBO-E-003, Email Service Failed to Login to SMTP Server Schneider Electric EcoStruxure Building Operation · EBO-E-004, Email Service Failed to Send Message Schneider Electric EcoStruxure Building Operation · EBO-E-005, Error in Log Definition Schneider Electric EcoStruxure Building Operation · EBO-E-006, Error Retrieving Xenta Device Trend Log Data Schneider Electric EcoStruxure Building Operation · EBO-E-007, Error – Upgrade Using DFU Mode Schneider Electric EcoStruxure Building Operation · EBO-F-001, Failed to Create Object Schneider Electric EcoStruxure Building Operation · EBO-F-002, Failed to Initialize References Schneider Electric EcoStruxure Building Operation · EBO-F-003, Failure Backing Up Server Database Schneider Electric EcoStruxure Building Operation · EBO-F-004, Failure Restoring Server Database Schneider Electric EcoStruxure Building Operation · EBO-I-001, Invalid Archive Path Schneider Electric EcoStruxure Building Operation · EBO-I-002, Invalid Device Address Schneider Electric EcoStruxure Building Operation · EBO-I-003, Invalid Device Identifier Schneider Electric EcoStruxure Building Operation · EBO-I-004, IO Error – Archive Directory Not Enough Space Schneider Electric EcoStruxure Building Operation · EBO-I-005, IP Connection Offline – Modbus TCP Schneider Electric EcoStruxure Building Operation · EBO-L-001, License Violation Schneider Electric EcoStruxure Building Operation · EBO-L-002, Local Administrator Account Has Empty or Default Password Schneider Electric EcoStruxure Building Operation · EBO-L-003, Log Full – Xenta Trend Log Schneider Electric EcoStruxure Building Operation · EBO-M-001, Module Type Mismatch Schneider Electric EcoStruxure Building Operation · EBO-M-002, More Than One Server With Same Name Schneider Electric EcoStruxure Building Operation · EBO-NET-001, Network Offline Schneider Electric EcoStruxure Building Operation · EBO-NW8-001, NW8 Application Error 1 – Pressure Sensor Failure (MnFlo) Schneider Electric EcoStruxure Building Operation · EBO-NW8-002, NW8 Application Error 2 – Large Negative Pressure (MnFlo) Schneider Electric EcoStruxure Building Operation · EBO-NW8-003, NW8 Application Error 4 – Large Positive Pressure (MnFlo) Schneider Electric EcoStruxure Building Operation · EBO-NW8-004, NW8 Application Error 16 – Heat Setpoint Exceeds Cool Setpoint (MnHpfc) Schneider Electric EcoStruxure Building Operation · EBO-NW8-005, NW8 Cold Reset – RAM Contents Lost Schneider Electric EcoStruxure Building Operation · EBO-NW8-006, NW8 EEprom Checksum Error Schneider Electric EcoStruxure Building Operation · EBO-NW8-007, NW8 Freeze Error Schneider Electric EcoStruxure Building Operation · EBO-NW8-008, NW8 RAM Failure Schneider Electric EcoStruxure Building Operation · EBO-NW8-009, NW8 ROM Failure Schneider Electric EcoStruxure Building Operation · EBO-NW8-010, NW8 Relay Failure Schneider Electric EcoStruxure Building Operation · EBO-NW8-011, NW8 Sensor Input Failure Schneider Electric EcoStruxure Building Operation · EBO-NW8-012, NW8 Pressure Error – Velocity Pressure Out of Range Schneider Electric EcoStruxure Building Operation · EBO-NW8-013, NW8 Damper Range Error Schneider Electric EcoStruxure Building Operation · EBO-NW8-014, NW8 No U-Link Communication Schneider Electric EcoStruxure Building Operation · EBO-NW8-015, NW8 Missing Changeover Input (Fan Coil) Schneider Electric EcoStruxure Building Operation · EBO-P-001, Port Offline – LON Interface Schneider Electric EcoStruxure Building Operation · EBO-S-001, Server Offline Schneider Electric EcoStruxure Building Operation · EBO-S-002, System Cold Start Schneider Electric EcoStruxure Building Operation · EBO-S-003, System Factory Reset Schneider Electric EcoStruxure Building Operation · EBO-T-001, Task CPU Limit Reached – Real Time Priority Disabled Schneider Electric EcoStruxure Building Operation · EBO-U-001, Unhandled BACnet Buffer Ready Notification Schneider Electric EcoStruxure Building Operation · EBO-W-001, Web Server Failure Schneider Electric EcoStruxure Building Operation · EBO-X-001, X509 Certificate Error Schneider Electric EcoStruxure Building Operation · EBO-X-002, Xenta Central Schedule Update Failure Schneider Electric EcoStruxure Building Operation · EBO-X-003, Xenta Schedule Update Failure – Communication Siemens Desigo / APOGEE · DSG-ERR-0, No Fault Siemens Desigo / APOGEE · DSG-ERR-1, No Sensor Connected Siemens Desigo / APOGEE · DSG-ERR-2, Over Range Siemens Desigo / APOGEE · DSG-ERR-3, Under Range Siemens Desigo / APOGEE · DSG-ERR-4, Line Break Siemens Desigo / APOGEE · DSG-ERR-5, Short Circuit Siemens Desigo / APOGEE · DSG-ERR-6, No Field Device Connected Siemens Desigo / APOGEE · DSG-ERR-7, Unknown Cause of Fault Siemens Desigo / APOGEE · DSG-ERR-8, Processing Error Siemens Desigo / APOGEE · DSG-ERR-9, Present Value Defined as Fault Siemens Desigo / APOGEE · DSG-ERR-10, Configuration Error Siemens Desigo / APOGEE · DSG-ERR-12, Communication Failure Siemens Desigo / APOGEE · DSG-ERR-20, Object Not Accessible Siemens Desigo / APOGEE · DSG-ERR-21, Missing Match of Object Types Siemens Desigo / APOGEE · DSG-ERR-22, Object Reference Being Resolved Siemens Desigo / APOGEE · DSG-ERR-23, Invalid Object Reference Siemens Desigo / APOGEE · DSG-ERR-24, Object Not Updated Siemens Desigo / APOGEE · DSG-ERR-25, Property Not Accessible Siemens Desigo / APOGEE · DSG-ERR-26, No Valid Present Value Found Siemens Desigo / APOGEE · DSG-ERR-28, Configuration Parameter Out of Range Siemens Desigo / APOGEE · DSG-ERR-29, Evaluation Function Not Supported Siemens Desigo / APOGEE · DSG-ERR-30, Internal Error Siemens Desigo / APOGEE · DSG-ERR-31, Unknown Group Data Tag Siemens Desigo / APOGEE · DSG-ERR-32, Group Data List Error Siemens Desigo / APOGEE · DSG-ERR-33, Group Member Overflow Siemens Desigo / APOGEE · DSG-ERR-40, No Property Defined Siemens Desigo / APOGEE · DSG-ERR-41, Properties Do Not Match Siemens Desigo / APOGEE · DSG-ERR-256, Loss of Remote Communication Siemens Desigo / APOGEE · DSG-ERR-257, Group Members Missing or Not Assigned Siemens Desigo / APOGEE · DSG-ERR-258, Device – General Fault Siemens Desigo / APOGEE · DSG-ERR-259, General Output Failure Siemens Desigo / APOGEE · DSG-ERR-260, Electrical Protection – Power Off Siemens Desigo / APOGEE · DSG-ERR-261, Thermal Shutdown Siemens Desigo / APOGEE · DSG-ERR-262, Battery Fault Siemens Desigo / APOGEE · DSG-ERR-268, Lamp Cycle Fault Siemens Desigo / APOGEE · DSG-ERR-269, Thermal Overload Siemens Desigo / APOGEE · DSG-ERR-272, Calibration Error Siemens Desigo / APOGEE · DSG-ERR-274, Configuration Error in I/O Extension Siemens Desigo / APOGEE · DSG-ERR-276, Erroneous Restart Siemens Desigo / APOGEE · DSG-LED-001, PXC FAULT LED – Steady Red Siemens Desigo / APOGEE · DSG-LED-002, PXC FAULT LED – Quick Flash Siemens Desigo / APOGEE · DSG-LED-003, PXC LOW BATT LED – Steady Red Siemens Desigo / APOGEE · DSG-LED-004, PXC SERVICE LED (Ethernet) – Steady Red Siemens Desigo / APOGEE · DSG-LED-005, PXC SERVICE LED (LON) – Steady Red Siemens Desigo / APOGEE · DSG-CC-001, Desigo CC – Event Category Fault Siemens Desigo / APOGEE · DSG-OOR-001, PXC Out-of-Range – High Limit Exceeded Siemens Desigo / APOGEE · DSG-OOR-002, PXC Out-of-Range – Low Limit Exceeded Siemens Desigo / APOGEE · DSG-OOR-003, PXC EEO – Object Name Reference Not Resolved Siemens Desigo / APOGEE · DSG-APOGEE-001, APOGEE BACnet Communication Fault Siemens Desigo / APOGEE · DSG-APOGEE-002, APOGEE Alarm Priority Level 1 (Critical) Siemens Desigo / APOGEE · DSG-APOGEE-003, APOGEE Alarm Priority Level 6 (Informational) Automated Logic / Carrier WebCTRL · ALC-STAT-0, Status Code 0 – Purple – Non-Operational / No Communications Automated Logic / Carrier WebCTRL · ALC-STAT-13, Status Code 13 – Coral – Control Program Error Automated Logic / Carrier WebCTRL · ALC-STAT-14, Status Code 14 – Charcoal – Download Required Automated Logic / Carrier WebCTRL · ALC-STAT-15, Status Code 15 – Purple – Hardware or Software Error Automated Logic / Carrier WebCTRL · ALC-STAT-2, Status Code 2 – Red – Heating or Cooling Alarm Automated Logic / Carrier WebCTRL · ALC-STAT-9, Status Code 9 – Red – Heating or Cooling Alarm (secondary) Automated Logic / Carrier WebCTRL · ALC-STAT-1, Status Code 1 – Orange – Unoccupied Heating or Cooling Alarm Automated Logic / Carrier WebCTRL · ALC-STAT-3, Status Code 3 – Yellow – Occupied Heating Automated Logic / Carrier WebCTRL · ALC-STAT-4, Status Code 4 – Blue – Occupied Cooling Automated Logic / Carrier WebCTRL · ALC-STAT-5, Status Code 5 – Dark Green – Occupied Standby Automated Logic / Carrier WebCTRL · ALC-STAT-6, Status Code 6 – Light Green – Occupied / No Conditioning Automated Logic / Carrier WebCTRL · ALC-STAT-7, Status Code 7 – Dark Blue – Unoccupied Cooling Automated Logic / Carrier WebCTRL · ALC-STAT-8, Status Code 8 – Tan – Unoccupied Heating Automated Logic / Carrier WebCTRL · ALC-STAT-10, Status Code 10 – Blue – Free Cooling Automated Logic / Carrier WebCTRL · ALC-STAT-12, Status Code 12 – Gray – Optimum Start Automated Logic / Carrier WebCTRL · ALC-FDD-001, WebCTRL FDD – Simultaneous Heating and Cooling Automated Logic / Carrier WebCTRL · ALC-FDD-002, WebCTRL FDD – Economizer Not Opening Automated Logic / Carrier WebCTRL · ALC-FDD-003, WebCTRL FDD – VAV Box Not Responding to Control Automated Logic / Carrier WebCTRL · ALC-FDD-004, WebCTRL FDD – Supply Air Temperature Reset Failure Automated Logic / Carrier WebCTRL · ALC-COM-001, WebCTRL – Controller Communication Loss Automated Logic / Carrier WebCTRL · ALC-COM-002, WebCTRL – Server Service Not Running Automated Logic / Carrier WebCTRL · ALC-OPTIFLEX-001, OptiFlex 580 – Field Device Communication Failure KMC Controls · KMC-BAC-001, KMC BACnet Device – Offline / No Response KMC Controls · KMC-BAC-002, KMC Conquest – MS/TP Communication Failure KMC Controls · KMC-BAC-003, KMC Conquest – BACnet Intrinsic Alarm – Out of Range KMC Controls · KMC-BAC-004, KMC Conquest – BACnet Command Priority Override KMC Controls · KMC-COMMANDER-001, KMC Commander – Controller Offline KMC Controls · KMC-COMMANDER-002, KMC Commander – Cloud Gateway Connection Failure KMC Controls · KMC-COMMANDER-003, KMC Commander – Invalid Credentials KMC Controls · KMC-CONNECT-001, KMC Connect – Database Connection Error KMC Controls · KMC-CONNECT-002, KMC Connect – Communication Error with BAC-9000 KMC Controls · KMC-FLEXSTAT-001, FlexStat – Communication Bus Fault KMC Controls · KMC-FLEXSTAT-002, FlexStat – Sensor Failure KMC Controls · KMC-LED-001, KMC Controller – LED Fault Pattern KMC Controls · KMC-BAC-005, KMC – BACnet MSTP Bus Error (Excessive Retries) KMC Controls · KMC-BAC-006, KMC – BACnet Device Duplicate Instance BACnet Standard (ASHRAE 135) · BAC-REL-0, Reliability – No Fault Detected BACnet Standard (ASHRAE 135) · BAC-REL-1, Reliability – No Sensor BACnet Standard (ASHRAE 135) · BAC-REL-2, Reliability – Over Range BACnet Standard (ASHRAE 135) · BAC-REL-3, Reliability – Under Range BACnet Standard (ASHRAE 135) · BAC-REL-4, Reliability – Open Loop BACnet Standard (ASHRAE 135) · BAC-REL-5, Reliability – Shorted Loop BACnet Standard (ASHRAE 135) · BAC-REL-6, Reliability – No Output BACnet Standard (ASHRAE 135) · BAC-REL-7, Reliability – Communication Failure BACnet Standard (ASHRAE 135) · BAC-REL-8, Reliability – Member Fault BACnet Standard (ASHRAE 135) · BAC-REL-9, Reliability – Configuration Error BACnet Standard (ASHRAE 135) · BAC-REL-10, Reliability – Tripped (formerly Process Error) BACnet Standard (ASHRAE 135) · BAC-REL-11, Reliability – Multi-State Fault BACnet Standard (ASHRAE 135) · BAC-REL-12, Reliability – Tripped (BACnet value 12) BACnet Standard (ASHRAE 135) · BAC-EVT-001, BACnet Event – ChangeOfValue (COV) BACnet Standard (ASHRAE 135) · BAC-EVT-002, BACnet Event – ChangeOfState (Binary/Multistate) BACnet Standard (ASHRAE 135) · BAC-EVT-003, BACnet Event – To-OffNormal (Threshold Exceeded) BACnet Standard (ASHRAE 135) · BAC-EVT-004, BACnet Event – To-Normal (Alarm Cleared) BACnet Standard (ASHRAE 135) · BAC-EVT-005, BACnet Event – To-Fault (Reliability Changed) BACnet Standard (ASHRAE 135) · BAC-NET-001, BACnet – Duplicate Device Instance BACnet Standard (ASHRAE 135) · BAC-NET-002, BACnet MS/TP – Lost Token BACnet Standard (ASHRAE 135) · BAC-NET-003, BACnet IP – BBMD Registration Failure BACnet Standard (ASHRAE 135) · BAC-NET-004, BACnet – Network Broadcast Storm BACnet Standard (ASHRAE 135) · BAC-OBJ-001, BACnet – Read Property Error BACnet Standard (ASHRAE 135) · BAC-OBJ-002, BACnet – Write Property Error BACnet Standard (ASHRAE 135) · BAC-OBJ-003, BACnet – Unknown Object Modbus Protocol · MOD-EX-01, Exception Code 0x01 – Illegal Function Modbus Protocol · MOD-EX-02, Exception Code 0x02 – Illegal Data Address Modbus Protocol · MOD-EX-03, Exception Code 0x03 – Illegal Data Value Modbus Protocol · MOD-EX-04, Exception Code 0x04 – Slave Device Failure Modbus Protocol · MOD-EX-05, Exception Code 0x05 – Acknowledge (Long-Latency Request) Modbus Protocol · MOD-EX-06, Exception Code 0x06 – Slave Device Busy Modbus Protocol · MOD-EX-07, Exception Code 0x07 – Negative Acknowledge Modbus Protocol · MOD-EX-08, Exception Code 0x08 – Memory Parity Error Modbus Protocol · MOD-EX-0A, Exception Code 0x0A – Gateway Path Unavailable Modbus Protocol · MOD-EX-0B, Exception Code 0x0B – Gateway Target Failed to Respond Modbus Protocol · MOD-COM-001, Modbus RTU – CRC Error Modbus Protocol · MOD-COM-002, Modbus TCP – Connection Timeout Modbus Protocol · MOD-COM-003, Modbus – No Response (Timeout) Reliable Controls MACH-System · RC-MACH-001, MACH-ProAir – Controller Offline Reliable Controls MACH-System · RC-MACH-002, MACH-ProAir – Sensor Failure Reliable Controls MACH-System · RC-MACH-003, MACH-ProAir – Output Override Active Reliable Controls MACH-System · RC-MACH-004, MACH-ProAir – Alarm Active (BACnet Intrinsic) Reliable Controls MACH-System · RC-MACH-005, RC-Studio – Database Load Error Reliable Controls MACH-System · RC-MACH-006, MACH-System – BACnet Network Unreachable Reliable Controls MACH-System · RC-MACH-007, MACH-ProView – Communication Fault with Field Devices Reliable Controls MACH-System · RC-MACH-008, MACH-ProAir – Freeze Protect Alarm Delta Controls · DC-ENTELI-001, enteliWEB – Server Connection Failed Delta Controls · DC-ENTELI-002, enteliWEB – Controller Offline Delta Controls · DC-ENTELI-003, enteliWEB – Alarm Not Acknowledged Delta Controls · DC-ENTELI-004, enteliWEB – Trend Data Export Failure Delta Controls · DC-ENTELI-005, enteliWEB – License Validation Failure Delta Controls · DC-ORC-001, ORCAview – BACnet Router Fault Delta Controls · DC-ORC-002, ORCAview – Database Synchronization Error Delta Controls · DC-BAS-001, Delta Controls BACnet Device – Communication Failure Lynxspring JENEsys / ONYXX · LYNX-JENE-001, JENEsys – BACnet Driver Communication Failure Lynxspring JENEsys / ONYXX · LYNX-JENE-002, JENEsys – License Feature Not Enabled Lynxspring JENEsys / ONYXX · LYNX-JENE-003, JENEsys – Station Startup Failure Lynxspring JENEsys / ONYXX · LYNX-ONYXX-001, ONYXX – Cloud Service Connection Failure Lynxspring JENEsys / ONYXX · LYNX-ONYXX-002, ONYXX – Device Discovery Failure Lynxspring JENEsys / ONYXX · LYNX-JENE-004, JENEsys – Modbus Driver Poll Failure
Or search by code, name, or symptom Browsing all 429 codes · page 1 of 9 Prev Next
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-001 , NAE CPU Usage High
Warning NAE CPU utilization exceeds factory-set alarm threshold. Diagnostic attribute on Device object generates an event.
Likely Causes
Too many field devices on trunk High scan-rate polling Excessive COV subscriptions Heavy reporting workload First Checks
Check NAE Diagnostic tab for CPU Usage value Reduce polling frequency on large device lists Review COV increment settings Check number of active event subscriptions Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – Alarms and events, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-002 , NAE CPU Temperature High
Warning CPU die temperature on NAE exceeds factory alarm limit. Built-in diagnostic.
Likely Causes
Inadequate ventilation in control panel Ambient temperature above spec Fan failure in enclosure Controller mounted in direct sunlight First Checks
Verify panel ambient temperature Check enclosure ventilation Inspect for heat sources near controller Consider relocating controller Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – Device diagnostic features table, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-003 , NAE Memory Usage High
Warning NAE RAM usage exceeds alarm threshold.
Likely Causes
Too many objects in engine database Excessive trending configuration Large audit log backlog Software memory leak First Checks
Review total object count in SCT Check trend log configuration Verify ADS/ADX is online and forwarding events Consider engine firmware update Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-004 , NAE Flash Usage High
Warning Non-volatile flash storage on NAE approaching capacity.
Likely Causes
Large number of stored events not forwarded Accumulated firmware update files Log data overflow ADS/ADX offline preventing event forwarding First Checks
Verify ADS/ADX connectivity Check event repository settings Review flash usage on Diagnostic tab Delete old firmware update files if applicable Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-005 , NAE Audit Rate High
Information Rate of audit events (operator actions) exceeds alarm threshold.
Likely Causes
Automated scripts performing frequent commands Mass override operations Integration polling with write-backs Security testing or scanning First Checks
Review operator activity logs Disable automation scripts if unexpected Check third-party integrations for excessive writes Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-006 , NAE Event Rate High
Warning Rate of alarm/event generation exceeds alarm threshold.
Likely Causes
Rapidly oscillating analog value around alarm limit Mass communication loss on trunk Misconfigured alarm deadband (too narrow) Sensor noise or input instability First Checks
Identify highest-frequency alarm sources in Event Viewer Widen deadband on oscillating points Check SA bus or FC trunk for communication issues Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-007 , NAE Events Lost
Warning NAE event repository became full and events were discarded before forwarding to ADS/ADX.
Likely Causes
ADS/ADX server offline for extended period Network path to ADS/ADX unavailable Repository size too small for site alarm volume Alarms not being acknowledged/cleared First Checks
Verify ADS/ADX server online status Check Ethernet connectivity to site director Review repository settings in engine properties Acknowledge and clear backlog of alarms Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-008 , NAE Samples Lost
Warning Trend log samples were lost due to buffer overflow.
Likely Causes
ADS/ADX offline preventing trend upload Very short sampling interval with many trend objects Network congestion Trend buffer undersized for interval First Checks
Verify ADS/ADX connectivity Review trend sample intervals Check 'Transfer Buffer Full' diagnostic Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-009 , NAE Sample Rate High
Warning Trend sampling rate exceeds the engine's processing capacity.
Likely Causes
Too many trend objects with very short intervals Combined sample rate too high for CPU Excessive COV-triggered trends First Checks
Review all trend object intervals Reduce sample rate on non-critical trends Stagger trend intervals to distribute load Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-010 , NAE Transfer Buffer Full
Warning The buffer used to transfer trend data to ADS/ADX is full.
Likely Causes
ADS/ADX temporarily offline Network outage between NAE and server High trend sample volume First Checks
Check ADS/ADX server status Verify LAN path to server Reduce trend frequency during outage Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-011 , NAE BACnet Broadcast Receive Rate High
Warning BACnet I-Am or Who-Is broadcast traffic on the IP network exceeds threshold.
Likely Causes
Misconfigured BBMD creating broadcast storm Many devices restarting simultaneously Third-party device constantly broadcasting Network misconfiguration causing loop First Checks
Capture BACnet/IP traffic with Wireshark Identify source of broadcasts Check BBMD configuration Verify BACnet network numbers are unique Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-012 , NAE COV Receive Rate High
Warning Rate of Change-of-Value (COV) notifications received by NAE exceeds threshold.
Likely Causes
COV increment set too low causing frequent notifications Many active COV subscriptions Field device sending COV for every scan cycle First Checks
Review COV increment values on high-traffic points Check number of active COV subscriptions Increase COV increment on non-critical AI objects Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-013 , SNE/SNC Events Lost Counter Incrementing
Warning SNE/SNC alarm event buffer for offline Metasys Server exceeded 1,000 events and is discarding new events.
Likely Causes
Metasys Server offline for extended period Network outage Server overloaded or crashed License issue preventing server operation First Checks
Verify Metasys Server status Check network path between SNE and server Review server event logs Restart server if frozen Source: Metasys SNE Commissioning Guide LIT-12013352 v15.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-014 , Analog Alarm – High Alarm
Warning Analog point Present Value has exceeded the configured High Alarm Limit for at least the Time Delay period.
Likely Causes
Process variable genuinely high Sensor out of calibration reading high Input wiring fault causing erroneous high signal Setpoint reference misconfigured First Checks
Verify actual process value independently Check sensor calibration and offset Review High Alarm Limit configuration Inspect input wiring for shorts or grounds Source: Metasys SMP Help LIT-1201793 v11.0 – Alarm Extensions, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-015 , Analog Alarm – Low Alarm
Warning Analog point Present Value has dropped below the configured Low Alarm Limit.
Likely Causes
Process variable genuinely low Sensor failure or open circuit reading low Power loss to transmitter Low Alarm Limit set too close to normal range First Checks
Verify actual process value Check sensor power and signal Review Low Alarm Limit value Test with known input source Source: Metasys SMP Help LIT-1201793 v11.0 – Alarm Extensions, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-016 , Analog Alarm – High Warning
Information Analog point Present Value exceeded the High Warning threshold (offset above High Warning Reference), but not yet the High Alarm Limit.
Likely Causes
Process approaching high alarm condition Gradual drift in controlled variable Seasonal load change First Checks
Review trend data for the point Check setpoint and control loop performance Verify High Warning Offset value Source: Metasys UI Help LIT-12011953 v8.0 – Analog alarm attributes, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-017 , Analog Alarm – Low Warning
Information Analog point Present Value dropped below the Low Warning threshold.
Likely Causes
Process approaching low alarm condition Gradual drift in controlled variable Seasonal load change First Checks
Review trend data Check control loop Verify Low Warning Offset value Source: Metasys UI Help LIT-12011953 v8.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-018 , Binary/Multistate Alarm – Trouble
Warning Multistate or binary point entered a configured Fault Value (Fault Values list), a state that indicates a fault condition distinct from normal off-normal.
Likely Causes
Field device reporting a fault state via multistate object Equipment fault relay closed VFD reporting fault via network status point First Checks
Identify what state value the object entered Investigate the field device's own fault indicators Check Fault Values configuration in alarm extension Source: Metasys SMP Help LIT-1201793 v14.0 – BACnet Alarm Tab, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-019 , Alarm State – Offline
Warning An object or field device has gone offline/unreachable as detected by the alarm monitoring system.
Likely Causes
Field device powered down SA bus or FC trunk communication failure Device address conflict on network Cable fault or termination issue First Checks
Check LED indicators on field device Verify power to device Inspect bus wiring and terminations Check for address conflicts in SCT Source: Metasys UI Help LIT-12011953 v8.0 – Alarm Manager alarm types, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-020 , Alarm State – Unreliable
Warning A BACnet object's Reliability property is not NO_FAULT_DETECTED, indicating a sensor or communication issue. The Fault flag in Status_Flags is set TRUE.
Likely Causes
Sensor disconnected (NoSensor) Signal over range (OverRange) Signal under range (UnderRange) Open loop or short circuit on input Communication failure with remote object First Checks
Read the Reliability attribute of the object Check sensor wiring Verify signal within expected range Test sensor with multimeter Source: Metasys SMP Help LIT-1201793 v14.0 – BACnet Alarm Tab, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-021 , Alarm State – Command Failure (OnOff Action Failure)
Warning A commanded output state did not match the feedback status within the Reference Delay Time, indicating a failed actuator or contactor.
Likely Causes
Actuator or relay failed Fan or pump motor tripped Wiring fault between controller output and load Feedback point wired incorrectly First Checks
Verify commanded state vs. actual status at device Check motor starter/contactor Test feedback wiring continuity Review Command Reference and Reference Delay in alarm extension Source: Metasys YouTube LIT-12011953 – Programming a Command Status Alarm Extension; Metasys SMP Help v14.0
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-022 , Alarm State – Shutdown
Shutdown Object or equipment is in a Shutdown alarm state, a critical alarm requiring intervention.
Likely Causes
Life safety condition triggered Equipment protective shutdown Manual shutdown command Loss of critical input First Checks
Identify alarm source object Check equipment for fault indicators Review alarm history for sequence of events Restore safe conditions before reset Source: Metasys UI Help LIT-12011953 v8.0 – Alarm Manager alarm type list, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-023 , N2 Bus Communication Loss
Warning NAE55 lost communication with one or more N2 field devices on the FC Bus (N2 Trunk). FCA or FCB LED shows steady green (transmitting only, no reply).
Likely Causes
Field device powered down N2 bus wiring fault Incorrect termination resistor placement Bus address conflict Failed N2 device First Checks
Check FCA/FCB LED state on NAE55 Verify field device power Inspect N2 wiring at both ends Confirm 120-ohm termination at bus endpoints Check for duplicate N2 addresses Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – NAE LED status indicators table, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-024 , SA Bus Communication Loss
Warning NCE25 lost communication on the SA Bus (Sensor/Actuator bus). LED shows no blinking.
Likely Causes
SA bus device offline Wiring break on SA bus End-of-line resistor missing SA bus device address conflict First Checks
Check SA Bus LED on NCE25 (5 Hz blink = normal) Verify SA bus power and wiring Check EOL resistor placement Inspect for duplicate SA addresses Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – NAE LED status indicators, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-025 , MS/TP Token Pass Failure
Warning NAE BACnet MS/TP trunk unable to pass token, no controllers communicating. FC LED shows steady green.
Likely Causes
All MS/TP controllers offline or unpowered Bad termination causing token loss Duplicate MAC address on MS/TP segment Wiring open circuit First Checks
Check MS/TP wiring continuity Verify 120-ohm terminators at ends Confirm all controllers powered Check for duplicate MS/TP addresses Use NAE diagnostic tab to view trunk status Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – FCA LED descriptions, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-026 , Ethernet Link Down
Shutdown NAE Ethernet port has no link, ETHERNET LED is steady off.
Likely Causes
Ethernet cable disconnected or failed Network switch port disabled or failed IP address conflict causing NIC to disable Physical port on NAE damaged First Checks
Verify Ethernet cable connection at both ends Check switch port LED Try a different cable or switch port Ping NAE from PC on same subnet Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – ETHERNET LED status, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-027 , BACnet Object Event State – Fault
Warning BACnet object's Event_State is set to FAULT (value=1) indicating the object Reliability property has reported a non-normal state.
Likely Causes
Reliability = NoSensor, OverRange, UnderRange, OpenLoop, ShortedLoop, or CommunicationFailure Sensor wiring issue Remote object communication lost First Checks
Read object Reliability attribute in SCT Check sensor wiring and signal range Verify BACnet network connectivity Source: Metasys SMP Help LIT-1201793 v14.0 – BACnet Alarm Tab / Event State, docs.johnsoncontrols.com; BACnet ASHRAE 135
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-028 , BACnet Object Event State – OffNormal
Warning Binary or multistate object's Present Value entered a configured Alarm Value state.
Likely Causes
Equipment fault bit active Safety input tripped Binary status indicating abnormal state First Checks
Identify which Alarm Value was triggered Check physical equipment status Review alarm value configuration Source: Metasys SMP Help LIT-1201793 v14.0 – BACnet Alarm Tab, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-029 , BACnet Object Event State – High Limit
Warning Analog object Present Value exceeded High Limit threshold set in BACnet intrinsic alarming.
Likely Causes
Process variable too high Sensor calibration drift high High Limit set too low in configuration First Checks
Check actual physical value Calibrate sensor Review High Limit setting Source: Metasys SMP Help LIT-1201793 v14.0 – BACnet Alarm Tab / Event State options, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-030 , BACnet Object Event State – Low Limit
Warning Analog object Present Value dropped below Low Limit threshold set in BACnet intrinsic alarming.
Likely Causes
Process variable too low Sensor failure Low Limit too high in configuration First Checks
Check actual physical value Verify sensor signal Review Low Limit setting Source: Metasys SMP Help LIT-1201793 v14.0 – BACnet Alarm Tab, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-031 , Life Safety Alarm
Shutdown A BACnet Life Safety object (e.g., smoke detector, sprinkler flow) has transitioned to an alarm state.
Likely Causes
Smoke/fire condition detected Sprinkler flow activated Life safety device fault Manual pull station activated First Checks
Immediately investigate life safety condition Check physical life safety device status Confirm with fire alarm panel Do not reset until cause is identified Source: Metasys SMP Help LIT-1201793 v14.0 – Alarm Type Life Safety Alarm, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-032 , Metasys Alarm Value Enum – FAU (Fault)
Warning Metasys internal Alarm Value Enumeration value 1 = FAU indicating a fault condition on the point.
Likely Causes
Object reliability issue Input out of range Communication loss to source First Checks
Read Reliability attribute Check physical wiring Verify communication path Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-033 , Metasys Alarm Value Enum – OFN (Off Normal)
Warning Metasys internal Alarm Value Enumeration value 2 = OFN, object is in Off-Normal alarm state.
Likely Causes
Binary alarm point in active/alarm state Multistate value in alarm state Process variable outside normal range First Checks
Identify which point triggered OFN Check physical equipment status Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-034 , Metasys Alarm Value Enum – HL (High Limit)
Warning Metasys internal enum value 3 = HL, analog point is in High Limit alarm state.
Likely Causes
Process variable above high limit Sensor reading high First Checks
Review actual process value Check sensor calibration Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-035 , Metasys Alarm Value Enum – LL (Low Limit)
Warning Metasys internal enum value 4 = LL, analog point is in Low Limit alarm state.
Likely Causes
Process variable below low limit Sensor failure First Checks
Review actual process value Check sensor wiring Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-036 , Metasys Alarm Value Enum – ALM (Alarm)
Warning Generic alarm state (enum 68) for binary alarm objects.
Likely Causes
Equipment alarm state active Binary sensor in alarm position First Checks
Identify source point and check physical equipment Review recent change log, parameter, firmware, or point-add Compare configuration against OEM commissioning template Restore last known-good backup and re-apply changes one at a time Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-037 , Metasys Alarm Value Enum – SHT (Shutdown)
Shutdown Object alarm state indicates equipment shutdown (enum 72 = SHT).
Likely Causes
Equipment protective shutdown activated Safety interlock tripped First Checks
Check equipment fault indicators Verify safety interlock status Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-038 , Metasys Alarm Value Enum – UNR (Unreliable)
Warning Object alarm state is Unreliable (enum 73 = UNR), sensor or communication issue.
Likely Causes
BACnet Reliability not NO_FAULT_DETECTED Sensor disconnected Communication failure First Checks
Read Reliability attribute Check sensor wiring Verify network path Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-039 , Metasys Alarm Value Enum – OFL (Offline)
Warning Object alarm state is Offline (enum 71 = OFL), device or object is unreachable.
Likely Causes
Field device communication loss Device powered down Bus wiring failure First Checks
Check device power and communication LEDs Inspect bus wiring Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-16, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-ALM-040 , Alarm Flags Enum – Irregular Action (1)
Warning Output object performed an unexpected or irregular action relative to command.
Likely Causes
Output wiring fault Actuator slipping or seized Control logic error First Checks
Check output wiring Verify actuator operation Review control logic Source: Metasys Appendix A Object Enumeration Sets LIT-694980 Table A-14 – Alarm Flags Enumeration Set, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-DIAG-001 , NAE Power LED Off
Shutdown NAE not receiving 24 VAC power or battery backup, unit is shut down.
Likely Causes
24 VAC transformer failure Power supply wiring fault Tripped circuit breaker Battery backup depleted First Checks
Check 24 VAC at power terminals Verify transformer output Check circuit breaker Replace battery if applicable Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – POWER LED table, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-DIAG-002 , FEC/MEC Communication Fault on FC Trunk
Warning A Field Equipment Controller or Modular Equipment Controller is not responding on the FC bus (MS/TP or N2).
Likely Causes
FEC/MEC unpowered Bus wiring fault Incorrect EOL termination FEC address conflict Failed controller First Checks
Check FEC/MEC power LED Inspect FC bus wiring Verify EOL switch positions Check for duplicate addresses in SCT Source: Metasys Field Equipment Controllers Product Bulletin, Johnson Controls; NAE Commissioning Guide LIT-1201519
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-DIAG-003 , ADX/ADS Communication Failure
Warning NAE/SNE cannot reach the site's ADS/ADX server, event forwarding suspended.
Likely Causes
ADS/ADX server offline or rebooting Network switch failure IP address misconfiguration Firewall blocking BACnet/TCP port First Checks
Ping ADS/ADX server from NAE subnet Check ADS/ADX Windows service status Review network firewall rules Verify ADS/ADX IP in NAE configuration Source: Metasys SNE Commissioning Guide LIT-12013352 v15.0, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-DIAG-004 , Invalid Object ID (BACnet Server Fault Cause)
Warning Metasys BACnet local device object ID is invalid, BACnet server shows {fault} status above the Object Id field.
Likely Causes
Device instance number set to default/invalid value (-1) Duplicate device instance on BACnet network Configuration not saved after IP setup First Checks
Set Device Instance to a unique positive value Confirm no duplicate device IDs on network Save configuration and verify Status changes to {ok} Source: NiagaraAX-3.x BACnet Guide, Cochrane Supply (Tridium); applicable to Metasys BACnet server setup
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-DIAG-005 , BACnet Server Capability Not Licensed
Warning Metasys device is attempting to export BACnet objects but BACnet server license is not installed or enabled. Export descriptors show 'fault status' with cause 'Server capability not licensed'.
Likely Causes
BACnet server license not purchased or installed License server unreachable License expired First Checks
Check Metasys software license inventory Verify license server connectivity Contact JCI for license activation Source: NiagaraAX-3.x BACnet Guide (applies to Metasys BACnet server export), Cochrane Supply
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-NET-001 , SNMP Trap Send Failure (DDA)
Warning Metasys Data Delivery Agent (DDA) failed to send SNMP trap to configured SNMP management system.
Likely Causes
SNMP server IP address incorrect UDP 162 blocked by firewall SNMP community string mismatch SNMP server offline First Checks
Verify SNMP destination IP in NAE configuration Check network firewall for UDP 162 Confirm SNMP community string matches server Ping SNMP server from NAE subnet Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – DDAs overview, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-NET-002 , Email DDA Send Failure
Information Metasys email notification failed to send via SMTP.
Likely Causes
SMTP server address incorrect Port 25/587 blocked by firewall Authentication credentials wrong Recipient email address invalid First Checks
Verify SMTP server address and port in NAE DDA Check firewall rules for outbound SMTP Test credentials on SMTP server directly Confirm recipient email validity Source: Metasys NAE Commissioning Guide LIT-1201519 v11.0 – DDAs, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-BAC-001 , BACnet Duplicate Device ID Detected
Warning Two or more devices on the BACnet internetwork share the same Device Object Instance number.
Likely Causes
New device added with default or copied ID Controller cloned without changing ID Integration of devices with pre-configured IDs First Checks
Use SCT or Workbench to scan for duplicate IDs Identify both devices and change one Verify all device IDs are unique site-wide Source: NiagaraAX-3.x BACnet Guide – Bacnet Device Find; Metasys SCT Help LIT-12011964, docs.johnsoncontrols.com
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-BAC-002 , BACnet Network Number Conflict
Warning Two network ports on the same BACnet internetwork have the same Network Number, causing routing failures.
Likely Causes
Multiple MS/TP trunks assigned Network Number 1 by default New NAE added with same network number as existing BBMD configuration error First Checks
Verify all BACnet network numbers are unique across site Check Bacnet Comm Network Number in NAE configuration Valid range is 1-65534 Source: NiagaraAX-3.x BACnet Guide – About Bacnet Comm, Cochrane Supply; Metasys BACnet implementation
Johnson Controls Metasys · NAE35/45/55/85, NCE25, SNC, SNE, ADX/ADS Server, FEC/MEC/FAC
MET-BAC-003 , MS/TP Lost Token
Information Token was lost on an MS/TP segment. The device with the lowest MAC address regenerates the token.
Likely Causes
Transient noise on RS-485 bus Bad termination resistor Failing device dropping off bus momentarily Long cable run exceeding spec First Checks
Check cable length and routing Verify termination at both ends Inspect for EMI sources near cable run Test each device individually Source: NiagaraAX-3.x BACnet Guide – MS/TP Address note, Cochrane Supply
Prev Page 1 of 9 Next