Skip to content
Industrial Error Code Fixes
Go back

More industrial fault codes

Automated Logic WebCTRL Fault Codes List: BAS Alarms, Causes and Fixes

⚡ Quick Answer

Automated Logic WebCTRL fault codes explained: offline controllers, BACnet comm faults, server errors and sensor alarms, with the checks that clear each one.

⚡ AT A GLANCEScroll down for full repair guide
What it meansAutomated Logic WebCTRL faults usually point to a BACnet controller, BAS network, server service, sensor, actuator, or authorized-login recovery problem.
Most likely causeOffline controllers, failed power supplies, MS/TP trunk wiring, BACnet/IP switch issues, sensor drift, actuator feedback faults, WebCTRL service errors, or expired credentials.
First checkCapture the Alarm Manager text, affected controller, controller LEDs, trunk scope, server status, and whether an authorized account can log in before acknowledging alarms.
⏱Repair time15-45 minutes for controller or network triage; longer for WebCTRL database, server, or dealer credential recovery.
🔧Part neededAutomated Logic zone sensor BACnet actuator controller power supply industrial Ethernet switch

Parts to price first

Check the part before you book service.

Automated Logic zone sensor

Match the sensor family, display type, thermistor curve, and communication wiring before replacing a sensor out-of-range alarm.

$35-$180Check price

BACnet damper actuator

Use for damper or valve faults only after confirming signal voltage, rotation direction, torque, and fail-safe position.

$60-$250Check price

Building automation controller power supply

Check output voltage, load, grounding, and shorted field wiring before replacing a power supply behind offline controllers.

$25-$120Check price

Industrial Ethernet switch for BAS

Use for repeated BACnet/IP dropouts after confirming cabling, port speed, VLAN, and switch power.

$45-$220Check price

Equipment service manual download (eManualOnline)

The full OEM-style workshop manual has the wiring diagram, test values, and the fault table this guide summarizes. Instant PDF download.

Repair intent

Need this fixed instead of diagnosed?

Automated Logic WebCTRL fault codes explained: offline controllers, BACnet comm faults, server errors and sensor alarms, with the checks that clear each one.

Automated Logic WebCTRL Fault Codes and BAS Alarms

Automated Logic (Carrier subsidiary) WebCTRL uses BACnet controllers (MCB, LGR, VMA, ZN series) and SiteBuilder software. Alarms display in the WebCTRL Alarm Manager and via e-mail/SMS notification.

If the search is really for an Automated Logic WebCTRL default login or password, use the Automated Logic WebCTRL default login recovery guide before trying to acknowledge alarms. It covers owner verification, dealer recovery, password rotation, and safe BAS access without publishing shared credentials.

AlarmDeviceMeaningQuick Fix
Controller OfflineMCB/LGRController not respondingCheck power and network
Sensor Out of RangeVMA/ZNSensor reading exceeds limitsCheck sensor and wiring
Communication FaultAllBACnet communication lostCheck MS/TP or BACnet IP
Fan Status AlarmAHUFan command/status mismatchCheck fan and status input
Discharge Air FaultAHUDischarge air out of rangeCheck coil valves and economizer
Freeze AlarmAHULow temperature detectedCheck heating coil and OA damper
Override ActiveAnyManual override in effectClear override via WebCTRL
Valve FaultAHUActuator position faultCheck actuator wiring
Occupancy FaultZoneOccupancy schedule errorCheck schedule configuration
WebCTRL Server FaultServerServer application errorCheck service, database, and access recovery

Safety Before You Start

BAS controller troubleshooting is mostly low-voltage electronics work, but a few risks still apply.

Tools You Will Need

Most Common Faults

Controller Offline

An ALC controller going offline in WebCTRL typically indicates a network issue or a power problem. Work through this sequence rather than assuming a controller failure:

  1. Check the controller’s status LED at the device itself. A powered, healthy controller usually shows a steady or slow-blinking pattern per the manufacturer’s LED reference; an unlit LED points to a power problem before anything else.
  2. Ping the controller’s IP address from the WebCTRL server for BACnet/IP devices. A failed ping with confirmed power points to a network switch, cable, or IP configuration issue rather than the controller itself.
  3. For BACnet MS/TP devices, check the trunk wiring for a break, a loose terminal, or incorrect termination resistors at the ends of the trunk. One damaged wire run can cause cascading offline alarms for every device downstream of the break.
  4. Confirm no other controller on the same MS/TP trunk was recently added or reconfigured with a duplicate MAC address, since that can knock devices offline intermittently.
  5. If the controller has power and the network path checks out but it still will not come online, the controller’s onboard processor may have failed and requires replacement.

Sensor Out of Range

ALC controllers accept UI (universal input) configured as thermistor, 0-10V, 4-20mA, or dry contact. A sensor out of range alarm means the raw input is outside the calibrated range.

  1. In SiteBuilder or the WebCTRL client, check that the input type configuration matches the physical sensor installed. A mismatched configuration will show an out-of-range reading even on a perfectly good sensor.
  2. With power off to the input circuit where practical, measure resistance across the sensor leads with a multimeter and compare to the sensor’s published thermistor curve or resistance table for the current temperature.
  3. Inspect the wiring run for a broken conductor, corroded terminal, or moisture intrusion. A broken thermistor wire reads the same as an open sensor and will show out of range.
  4. If the sensor and wiring test good but the reading still looks wrong, verify the controller’s analog input calibration settings have not drifted from the factory default.
  5. Replace the sensor only after wiring and configuration are confirmed correct, matching the exact sensor family and thermistor curve for the application.

Freeze Alarm

WebCTRL freeze alarms from AHU applications latch and require acknowledgment plus reset at the controller. Treat every freeze alarm as a real safety event until proven otherwise, since a frozen coil can burst and cause significant water damage.

  1. Confirm the actual air temperature at the freeze stat location using an independent thermometer if practical, since a failed sensor can trigger a false freeze alarm.
  2. Check that the outside air damper closed and the heating coil valve opened as commanded by the freeze strategy configured for that program.
  3. Inspect the heating coil and hot water supply for adequate flow and temperature if the freeze condition appears to be real rather than a sensor fault.
  4. After resolving the freeze condition, reset the alarm in WebCTRL and verify the OA damper returns to its normal controlled position rather than staying locked in the failsafe state.
  5. If freeze alarms recur in cold weather without an actual freeze risk, review the freeze stat’s setpoint and location, since a stat placed in a direct cold air stream can trip prematurely.

WebCTRL Server Fault

WebCTRL runs as a Windows service. If the service crashes or fails to start after an update, check the WebCTRL log files in the install directory before resetting credentials.

  1. Open the WebCTRL install directory’s log folder and review the most recent log file for error messages timestamped near the failure.
  2. Check Windows Event Viewer’s Application log for related service crash or exception entries.
  3. Common causes include Java heap size configured too small for the database size, a SQL database connection failure, a corrupt WebCTRL database, or an expired security certificate that presents as a login problem rather than a server crash.
  4. Confirm the SQL Server or embedded database service (depending on installation type) is running before restarting the WebCTRL service itself.
  5. If the log points to a corrupted database and no recent backup exists, contact Automated Logic support before attempting repair operations that could make data recovery harder.

WebCTRL Access and Password Safety

Do not put factory or inherited WebCTRL credentials into a live building automation server. If a facility does not have a valid login, use the owner credential record, the installing contractor, or the Automated Logic dealer recovery path. For the full safe recovery workflow, use the WebCTRL default login recovery guide. After access is restored, disable shared accounts, rotate temporary passwords, and confirm remote access is protected before reconnecting the server to a broader network.

If the search started because a technician is locked out during an active fault, keep the troubleshooting work separate from credential recovery. Verify controller power, network reachability, and alarm history with an authorized account instead of trying random default passwords.

Parts Often Needed

PartNotes
MCB/LGR controllerMatch controller family and I/O count
VMA VAV controllerReplace only after power and bus checks
Zone sensor (ZS)Match sensor type and thermistor curve
Damper actuatorMatch torque, signal, and fail-safe action
BAS network switchCheck on repeated BACnet/IP dropouts

Need Replacement Parts?

Before ordering, match the building automation part to the controller family, electrical rating, input/output count, network type, and failure symptom. Check current prices on Amazon - prices and availability change frequently.

When to Call a Pro

WebCTRL server administration, database management, and BACnet network configuration require Automated Logic-certified technicians. Call one when:

Quick FAQ

Where should I start with Automated Logic WebCTRL alarms?

Start with the WebCTRL Alarm Manager message, affected controller, recent schedule or network changes, and whether the fault is isolated to one device or an entire BACnet trunk.

Why is my Automated Logic controller offline in WebCTRL?

Check controller power, status LEDs, BACnet IP or MS/TP wiring, trunk termination, and the WebCTRL server network before replacing a controller.

What parts are commonly needed for Automated Logic fault codes?

Common service items include zone sensors, damper actuators, controller power supplies, network switches, and replacement ALC controllers. Match the exact controller family and input/output count before ordering.

Does this page include the Automated Logic WebCTRL default login?

No. For WebCTRL login or password recovery, use the linked default-login recovery guide and verify ownership through the facility record, installing contractor, or Automated Logic dealer instead of trying public credentials.


Share this post on:

Previous Post
Atlas Copco Error Codes and Fault Codes List (Elektronikon)
Next Post
Automated Logic WebCTRL Default Login and Password Recovery