BAS Controls Fault Codes
Building automation alarms, BACnet faults, and Modbus exceptions for Johnson Controls Metasys, Honeywell / Tridium Niagara, Distech, Schneider EcoStruxure, Siemens Desigo, Automated Logic, KMC, and more.
NAE CPU utilization exceeds factory-set alarm threshold. Diagnostic attribute on Device object generates an event.
- Too many field devices on trunk
- High scan-rate polling
- Excessive COV subscriptions
- Heavy reporting workload
- 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
CPU die temperature on NAE exceeds factory alarm limit. Built-in diagnostic.
- Inadequate ventilation in control panel
- Ambient temperature above spec
- Fan failure in enclosure
- Controller mounted in direct sunlight
- Verify panel ambient temperature
- Check enclosure ventilation
- Inspect for heat sources near controller
- Consider relocating controller
NAE RAM usage exceeds alarm threshold.
- Too many objects in engine database
- Excessive trending configuration
- Large audit log backlog
- Software memory leak
- Review total object count in SCT
- Check trend log configuration
- Verify ADS/ADX is online and forwarding events
- Consider engine firmware update
Non-volatile flash storage on NAE approaching capacity.
- Large number of stored events not forwarded
- Accumulated firmware update files
- Log data overflow
- ADS/ADX offline preventing event forwarding
- Verify ADS/ADX connectivity
- Check event repository settings
- Review flash usage on Diagnostic tab
- Delete old firmware update files if applicable
Rate of audit events (operator actions) exceeds alarm threshold.
- Automated scripts performing frequent commands
- Mass override operations
- Integration polling with write-backs
- Security testing or scanning
- Review operator activity logs
- Disable automation scripts if unexpected
- Check third-party integrations for excessive writes
Rate of alarm/event generation exceeds alarm threshold.
- Rapidly oscillating analog value around alarm limit
- Mass communication loss on trunk
- Misconfigured alarm deadband (too narrow)
- Sensor noise or input instability
- Identify highest-frequency alarm sources in Event Viewer
- Widen deadband on oscillating points
- Check SA bus or FC trunk for communication issues
NAE event repository became full and events were discarded before forwarding to ADS/ADX.
- 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
- Verify ADS/ADX server online status
- Check Ethernet connectivity to site director
- Review repository settings in engine properties
- Acknowledge and clear backlog of alarms
Trend log samples were lost due to buffer overflow.
- ADS/ADX offline preventing trend upload
- Very short sampling interval with many trend objects
- Network congestion
- Trend buffer undersized for interval
- Verify ADS/ADX connectivity
- Review trend sample intervals
- Check 'Transfer Buffer Full' diagnostic
Trend sampling rate exceeds the engine's processing capacity.
- Too many trend objects with very short intervals
- Combined sample rate too high for CPU
- Excessive COV-triggered trends
- Review all trend object intervals
- Reduce sample rate on non-critical trends
- Stagger trend intervals to distribute load
The buffer used to transfer trend data to ADS/ADX is full.
- ADS/ADX temporarily offline
- Network outage between NAE and server
- High trend sample volume
- Check ADS/ADX server status
- Verify LAN path to server
- Reduce trend frequency during outage
BACnet I-Am or Who-Is broadcast traffic on the IP network exceeds threshold.
- Misconfigured BBMD creating broadcast storm
- Many devices restarting simultaneously
- Third-party device constantly broadcasting
- Network misconfiguration causing loop
- Capture BACnet/IP traffic with Wireshark
- Identify source of broadcasts
- Check BBMD configuration
- Verify BACnet network numbers are unique
Rate of Change-of-Value (COV) notifications received by NAE exceeds threshold.
- COV increment set too low causing frequent notifications
- Many active COV subscriptions
- Field device sending COV for every scan cycle
- Review COV increment values on high-traffic points
- Check number of active COV subscriptions
- Increase COV increment on non-critical AI objects
SNE/SNC alarm event buffer for offline Metasys Server exceeded 1,000 events and is discarding new events.
- Metasys Server offline for extended period
- Network outage
- Server overloaded or crashed
- License issue preventing server operation
- Verify Metasys Server status
- Check network path between SNE and server
- Review server event logs
- Restart server if frozen
Analog point Present Value has exceeded the configured High Alarm Limit for at least the Time Delay period.
- Process variable genuinely high
- Sensor out of calibration reading high
- Input wiring fault causing erroneous high signal
- Setpoint reference misconfigured
- Verify actual process value independently
- Check sensor calibration and offset
- Review High Alarm Limit configuration
- Inspect input wiring for shorts or grounds
Analog point Present Value has dropped below the configured Low Alarm Limit.
- Process variable genuinely low
- Sensor failure or open circuit reading low
- Power loss to transmitter
- Low Alarm Limit set too close to normal range
- Verify actual process value
- Check sensor power and signal
- Review Low Alarm Limit value
- Test with known input source
Analog point Present Value exceeded the High Warning threshold (offset above High Warning Reference), but not yet the High Alarm Limit.
- Process approaching high alarm condition
- Gradual drift in controlled variable
- Seasonal load change
- Review trend data for the point
- Check setpoint and control loop performance
- Verify High Warning Offset value
Analog point Present Value dropped below the Low Warning threshold.
- Process approaching low alarm condition
- Gradual drift in controlled variable
- Seasonal load change
- Review trend data
- Check control loop
- Verify Low Warning Offset value
Multistate or binary point entered a configured Fault Value (Fault Values list) — a state that indicates a fault condition distinct from normal off-normal.
- Field device reporting a fault state via multistate object
- Equipment fault relay closed
- VFD reporting fault via network status point
- Identify what state value the object entered
- Investigate the field device's own fault indicators
- Check Fault Values configuration in alarm extension
An object or field device has gone offline/unreachable as detected by the alarm monitoring system.
- Field device powered down
- SA bus or FC trunk communication failure
- Device address conflict on network
- Cable fault or termination issue
- Check LED indicators on field device
- Verify power to device
- Inspect bus wiring and terminations
- Check for address conflicts in SCT
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.
- Sensor disconnected (NoSensor)
- Signal over range (OverRange)
- Signal under range (UnderRange)
- Open loop or short circuit on input
- Communication failure with remote object
- Read the Reliability attribute of the object
- Check sensor wiring
- Verify signal within expected range
- Test sensor with multimeter
A commanded output state did not match the feedback status within the Reference Delay Time — indicating a failed actuator or contactor.
- Actuator or relay failed
- Fan or pump motor tripped
- Wiring fault between controller output and load
- Feedback point wired incorrectly
- 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
Object or equipment is in a Shutdown alarm state — a critical alarm requiring intervention.
- Life safety condition triggered
- Equipment protective shutdown
- Manual shutdown command
- Loss of critical input
- Identify alarm source object
- Check equipment for fault indicators
- Review alarm history for sequence of events
- Restore safe conditions before reset
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).
- Field device powered down
- N2 bus wiring fault
- Incorrect termination resistor placement
- Bus address conflict
- Failed N2 device
- 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
NCE25 lost communication on the SA Bus (Sensor/Actuator bus). LED shows no blinking.
- SA bus device offline
- Wiring break on SA bus
- End-of-line resistor missing
- SA bus device address conflict
- 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
NAE BACnet MS/TP trunk unable to pass token — no controllers communicating. FC LED shows steady green.
- All MS/TP controllers offline or unpowered
- Bad termination causing token loss
- Duplicate MAC address on MS/TP segment
- Wiring open circuit
- 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
NAE Ethernet port has no link — ETHERNET LED is steady off.
- Ethernet cable disconnected or failed
- Network switch port disabled or failed
- IP address conflict causing NIC to disable
- Physical port on NAE damaged
- 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
BACnet object's Event_State is set to FAULT (value=1) indicating the object Reliability property has reported a non-normal state.
- Reliability = NoSensor, OverRange, UnderRange, OpenLoop, ShortedLoop, or CommunicationFailure
- Sensor wiring issue
- Remote object communication lost
- Read object Reliability attribute in SCT
- Check sensor wiring and signal range
- Verify BACnet network connectivity
Binary or multistate object's Present Value entered a configured Alarm Value state.
- Equipment fault bit active
- Safety input tripped
- Binary status indicating abnormal state
- Identify which Alarm Value was triggered
- Check physical equipment status
- Review alarm value configuration
Analog object Present Value exceeded High Limit threshold set in BACnet intrinsic alarming.
- Process variable too high
- Sensor calibration drift high
- High Limit set too low in configuration
- Check actual physical value
- Calibrate sensor
- Review High Limit setting
Analog object Present Value dropped below Low Limit threshold set in BACnet intrinsic alarming.
- Process variable too low
- Sensor failure
- Low Limit too high in configuration
- Check actual physical value
- Verify sensor signal
- Review Low Limit setting
A BACnet Life Safety object (e.g., smoke detector, sprinkler flow) has transitioned to an alarm state.
- Smoke/fire condition detected
- Sprinkler flow activated
- Life safety device fault
- Manual pull station activated
- Immediately investigate life safety condition
- Check physical life safety device status
- Confirm with fire alarm panel
- Do not reset until cause is identified
Metasys internal Alarm Value Enumeration value 1 = FAU indicating a fault condition on the point.
- Object reliability issue
- Input out of range
- Communication loss to source
- Read Reliability attribute
- Check physical wiring
- Verify communication path
Metasys internal Alarm Value Enumeration value 2 = OFN — object is in Off-Normal alarm state.
- Binary alarm point in active/alarm state
- Multistate value in alarm state
- Process variable outside normal range
- Identify which point triggered OFN
- Check physical equipment status
Metasys internal enum value 3 = HL — analog point is in High Limit alarm state.
- Process variable above high limit
- Sensor reading high
- Review actual process value
- Check sensor calibration
Metasys internal enum value 4 = LL — analog point is in Low Limit alarm state.
- Process variable below low limit
- Sensor failure
- Review actual process value
- Check sensor wiring
Generic alarm state (enum 68) for binary alarm objects.
- Equipment alarm state active
- Binary sensor in alarm position
- Identify source point and check physical equipment
Object alarm state indicates equipment shutdown (enum 72 = SHT).
- Equipment protective shutdown activated
- Safety interlock tripped
- Check equipment fault indicators
- Verify safety interlock status
Object alarm state is Unreliable (enum 73 = UNR) — sensor or communication issue.
- BACnet Reliability not NO_FAULT_DETECTED
- Sensor disconnected
- Communication failure
- Read Reliability attribute
- Check sensor wiring
- Verify network path
Object alarm state is Offline (enum 71 = OFL) — device or object is unreachable.
- Field device communication loss
- Device powered down
- Bus wiring failure
- Check device power and communication LEDs
- Inspect bus wiring
Output object performed an unexpected or irregular action relative to command.
- Output wiring fault
- Actuator slipping or seized
- Control logic error
- Check output wiring
- Verify actuator operation
- Review control logic
NAE not receiving 24 VAC power or battery backup — unit is shut down.
- 24 VAC transformer failure
- Power supply wiring fault
- Tripped circuit breaker
- Battery backup depleted
- Check 24 VAC at power terminals
- Verify transformer output
- Check circuit breaker
- Replace battery if applicable
A Field Equipment Controller or Modular Equipment Controller is not responding on the FC bus (MS/TP or N2).
- FEC/MEC unpowered
- Bus wiring fault
- Incorrect EOL termination
- FEC address conflict
- Failed controller
- Check FEC/MEC power LED
- Inspect FC bus wiring
- Verify EOL switch positions
- Check for duplicate addresses in SCT
NAE/SNE cannot reach the site's ADS/ADX server — event forwarding suspended.
- ADS/ADX server offline or rebooting
- Network switch failure
- IP address misconfiguration
- Firewall blocking BACnet/TCP port
- Ping ADS/ADX server from NAE subnet
- Check ADS/ADX Windows service status
- Review network firewall rules
- Verify ADS/ADX IP in NAE configuration
Metasys BACnet local device object ID is invalid — BACnet server shows {fault} status above the Object Id field.
- Device instance number set to default/invalid value (-1)
- Duplicate device instance on BACnet network
- Configuration not saved after IP setup
- Set Device Instance to a unique positive value
- Confirm no duplicate device IDs on network
- Save configuration and verify Status changes to {ok}
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'.
- BACnet server license not purchased or installed
- License server unreachable
- License expired
- Check Metasys software license inventory
- Verify license server connectivity
- Contact JCI for license activation
Metasys Data Delivery Agent (DDA) failed to send SNMP trap to configured SNMP management system.
- SNMP server IP address incorrect
- UDP 162 blocked by firewall
- SNMP community string mismatch
- SNMP server offline
- 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
Metasys email notification failed to send via SMTP.
- SMTP server address incorrect
- Port 25/587 blocked by firewall
- Authentication credentials wrong
- Recipient email address invalid
- 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
Two or more devices on the BACnet internetwork share the same Device Object Instance number.
- New device added with default or copied ID
- Controller cloned without changing ID
- Integration of devices with pre-configured IDs
- Use SCT or Workbench to scan for duplicate IDs
- Identify both devices and change one
- Verify all device IDs are unique site-wide
Two network ports on the same BACnet internetwork have the same Network Number, causing routing failures.
- Multiple MS/TP trunks assigned Network Number 1 by default
- New NAE added with same network number as existing
- BBMD configuration error
- Verify all BACnet network numbers are unique across site
- Check Bacnet Comm Network Number in NAE configuration
- Valid range is 1-65534
Token was lost on an MS/TP segment. The device with the lowest MAC address regenerates the token.
- Transient noise on RS-485 bus
- Bad termination resistor
- Failing device dropping off bus momentarily
- Long cable run exceeding spec
- Check cable length and routing
- Verify termination at both ends
- Inspect for EMI sources near cable run
- Test each device individually