The Trane Tracer SC and SC+ controllers are core building automation platforms that manage HVAC equipment, lighting, and tenant comfort systems. This reference guide covers LED diagnostic patterns, BACnet communication errors, controller initialization failures, and network configuration issues you'll encounter in the field. The Tracer controllers use multi-color LED indicators and event logging to communicate system health—understanding these signals is critical for rapid diagnostics.
The front panel of Tracer SC/SC+ controllers features three primary indicator LEDs that reveal the system state without requiring terminal access.
| LED | Location | Solid Green | Blinking Green | Solid Amber | Blinking Amber | Red | Off |
|---|---|---|---|---|---|---|---|
| POWER | Top left | AC power present and stable | N/A | Low voltage condition | AC voltage unstable (fluctuating input) | Power failure | No power input |
| STATUS | Center | Controller running normally, all checks passed | Self-test in progress | Non-critical warning active | Configuration pending or minor fault | Critical fault detected | Standby/bootup |
| COMM | Right | BACnet comms active and healthy | BACnet traffic present (normal) | No recent comm traffic | Attempting to connect to network | Comm timeout or BACnet error | Network disconnected |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| E001 | Database Initialization Failed | Corrupted flash memory or corrupted database file | Power cycle controller; if persists, perform factory reset using hardware reset button (hold 15 seconds during bootup) |
| E002 | Invalid Configuration File | Configuration file syntax error or missing required parameters | Re-save controller configuration from Tracer SC configuration tool; verify all mandatory fields are populated |
| E003 | Memory Test Failed | DRAM failure or memory corruption | Replace controller; data may be lost |
| E004 | Real-Time Clock Error | RTC battery depleted or hardware failure | Replace RTC battery (CR2032, typically on main board); if error persists, replace controller |
| E005 | Boot Timeout | Controller stuck in initialization loop | Hard power cycle (remove 24VAC for 30 seconds); check for configuration loops or excessive point database |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| B101 | BACnet Stack Initialization Failed | Ethernet driver not responding or MAC address conflict | Verify Ethernet cable is connected; check for IP address conflicts on network using ipconfig or arp commands from a workstation |
| B102 | Invalid BACnet Object Definition | Object points defined with conflicting properties (e.g., two inputs with same object ID) | Open Tracer SC database, search for duplicate Object IDs; use Find/Replace to rename conflicting points |
| B103 | BACnet Binding Timeout | Controller unable to bind to network segment or gateway timeout | Verify network connectivity; ping controller IP from workstation; check gateway/router for DHCP or network isolation issues |
| B104 | No Response from Foreign Device Registrar | SC+ attempting to register with BBMD but BBMD unreachable | Verify BBMD IP address in SC+ network settings matches actual BBMD; check firewall rules on BBMD server for UDP port 47808 |
| B105 | BACnet Device Communication Lost | Network interface down or cable disconnected | Check Ethernet LED on network interface; reseat Ethernet connector; test with patch cable if using structured cabling |
| B201 | Unit Controller Offline (Unit ID: XX) | Subordinate controller not responding on BACnet | Check power and Ethernet to subordinate unit controller; verify IP addressing; cycle subordinate controller if necessary |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| D101 | Database Sync Failed | Tracer SC unable to synchronize with primary controller (in redundant setup) | Check network connectivity between primary and backup SC controllers; verify both have same configuration version; manually trigger sync from primary using WebTOP menu |
| D102 | Point Trend Database Full | Trend buffer reached maximum capacity (default 50,000 samples per point) | Archive old trend data to SQL Server; reduce trend sample interval; or delete low-priority trend points |
| D103 | Configuration Database Exceeds Limits | Point count exceeds maximum (typically 8,000 points for SC, 12,000 for SC+) | Remove unused points; consolidate redundant logic; if essential to grow beyond limit, upgrade to SC+ or implement multiple controllers |
| D201 | Checksum Mismatch on Load | Downloaded configuration file corrupt during transfer | Re-download configuration from engineering workstation; verify file integrity using available checksum tools |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| N101 | DHCP Request Failed | DHCP server unreachable or not responding within timeout | Configure static IP address via terminal menu; or verify DHCP server is operational and controller can reach it on network |
| N102 | Invalid IP Address Configuration | IP address conflicts with existing device on network | Use ipconfig or subnet calculator to identify conflict; reassign controller to different IP in available range; verify no duplicate MAC addresses |
| N103 | Gateway/Router Unreachable | Network gateway not responding to ARP requests | Check physical cable to network; ping gateway IP from workstation to confirm it is online; verify controller gateway setting matches network gateway |
| N201 | DNS Resolution Failed | Unable to resolve hostname to IP (if using DNS) | Verify DNS server IP is correct in network settings; use nslookup from workstation to test DNS; consider using static IP instead of DHCP if DNS is unstable |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| U101 | Modbus RTU Timeout | Serial communication to unit controller failed (typically 5+ second response timeout) | Check serial cable between SC and unit controller; verify Modbus address matches configuration; test serial port with loopback connector |
| U102 | Unit Controller Program Checksum Error | Unit controller detected corrupted firmware or program memory | Download latest firmware to unit controller using Trane programming tool; if download fails, unit controller memory may be damaged |
| U201 | Device Not Found at Address (Modbus Addr: XX) | Unit controller not responding or configured with wrong Modbus address | Verify Modbus address setting in unit controller; check that unit controller is powered and in normal mode; physically locate controller and verify it is the correct device |
| U301 | Multiple Devices on Same Modbus Address | Two or more unit controllers configured with identical Modbus address | Use hand-held scanner or Trane configuration tool to identify all Modbus addresses on network; reconfigure duplicate addresses to unique values |
Tracer SC controllers populate a circular event log that captures runtime warnings and informational messages. Access via WebTOP then System then Event Log or via terminal menu.
BACnet Connection Lost to Device XXXX
Database Synchronization Pending
Trend Data Collection Halted - Storage Full
Point Value Out of Range (Point: XX)
Watchdog Reset - System Recovered
Prevention: Maintain clean, dry environment around controller. Dust on Ethernet connectors can cause intermittent comm faults. Clean connectors with compressed air and isopropyl alcohol if suspicious of intermittent behavior.
Redundancy Testing: If running redundant SC controllers, periodically test failover by powering down primary while monitoring secondary takeover. Should occur within 30 seconds; if longer, investigate sync configuration.
Firmware Updates: Before updating controller firmware, export current configuration and save to workstation. Firmware updates can occasionally cause compatibility issues with older unit controllers.
Database Backup: Regularly export configuration to file and store off-device. If controller fails, configuration can be quickly restored to replacement hardware without re-engineering.
Serial Debugging: For persistent issues, enable debug logging in terminal menu (System then Debug Settings) and capture console output. Debug logs reveal underlying issues not visible in standard Event Log.
Last updated: February 2026. Based on Tracer SC/SC+ firmware versions 8.5 through 9.2 and WebTOP 8.0+