BAS and BACnet troubleshooting works best when the symptom is separated into power, field bus, IP network, controller configuration, supervisory software, and equipment sequence. This hub organizes BuildingOpsLab field guides by the failure pattern technicians and facility teams actually see.
Start With the Failure Pattern
One device, several devices, or the entire trunk is offline
- BACnet MS/TP Devices Keep Going Offline
- One Bad BACnet Controller Can Disrupt an Entire MS/TP Trunk
- BACnet MS/TP Complete Field Guide
- BACnet Router Problems
- How to Troubleshoot an Offline JACE
Devices are discovered incorrectly or disappear after integration
- BACnet Device Instance vs MAC Address vs Network Number
- Duplicate BACnet Network Numbers
- VFD BACnet Integration: Start/Stop Commands Do Not Work
- Niagara AX vs Niagara 4
The BAS command, graphic, and equipment state disagree
- BAS Graphic Says ON but the Equipment Is OFF
- VFD Running but BAS Says Off
- 0–10 V vs 2–10 V Actuator Control
- BAS Controller Replacement Checklist
Schedules, timestamps, trends, or sensor values are wrong
- BAS Schedule Not Working
- BAS Time Sync Problems
- What BAS Points Should You Trend?
- BAS Sensor Reading Wrong
Find the Failure Boundary Before Changing Settings
| Boundary | Questions to Answer | Evidence |
|---|---|---|
| Power | Is every controller and router powered continuously under load? | Measured voltage, transformer loading, reboot history |
| MS/TP physical layer | Is the bus continuous, correctly polarized, terminated, and free of damaging branches? | Wiring inspection, isolation results, router errors |
| BACnet configuration | Are MAC addresses, Device Instances, network numbers, baud rates, and routing unique and correct? | Approved network schedule and device configuration |
| IP and supervisory layer | Is the correct network interface, route, BBMD, firewall path, and station service being used? | NIC binding, route, service, port, and connection tests |
| Control sequence | Does the effective command match the intended sequence and safety state? | Program logic, priority array, command, status, and proof |
A Repeatable BAS Troubleshooting Workflow
- Capture the exact symptom, time, affected devices, and operating condition.
- Check power before treating an offline controller as a network failure.
- Determine whether the boundary is one device, one physical section, one network, or the supervisor.
- Record current settings before changing baud rate, addressing, routes, priorities, or programs.
- Make one controlled change at a time and document the result.
- Verify every expected device, command path, alarm, trend, and recovery state after correction.
Field rule: An online icon is not proof that the network is healthy, and a BAS command is not proof that equipment moved. Use measured power, diagnostics, field status, and physical verification together.
Safety and change control: BAS networks can control critical equipment and protective sequences. Follow site authorization, backups, manufacturer instructions, cybersecurity requirements, and qualified-person procedures before disconnecting networks or changing programs.