Schneider Electric's SmartX IP controllers (AS-P series) represent a modern, cloud-native approach to building automation, while their SpaceLogic ecosystem provides tight integration with EcoStruxure Building Operation (EBO). This reference covers SmartX LED diagnostics, EBO workstation errors, AS-B/AS-P communication faults, I/O bus errors, firmware update failures, and BACnet integration issues specific to the Schneider platform. Field technicians must understand both the physical LED indicators and the EBO software error messages to diagnose effectively.
The SmartX controller uses a front-panel LED array (typically 4-6 indicator lights) to convey operational state. Unlike older controllers with simple three-color LEDs, SmartX uses patterned flashing and multiple colors to indicate more granular states.
| LED Label | Color | Status | Meaning | Action |
|---|---|---|---|---|
| Power | Green | Solid ON | 24V DC supply present and stable | Normal; no action |
| Power | Green | OFF | No power detected | Check 24V supply, circuit breaker, and terminal block connections |
| Network | Blue | Solid ON | Ethernet connected and link detected | Normal; BACnet/IP ready |
| Network | Blue | Slow Flash (1/sec) | Ethernet link present, negotiating IP address (DHCP) | Wait 30 seconds for DHCP lease. If persists, check DHCP server availability. |
| Network | Blue | Fast Flash (2/sec) | Active BACnet/IP traffic | Normal during polling and write operations |
| Network | Blue | OFF | No Ethernet link detected | Check network cable, switch port, and RJ45 connector. Verify cable is CAT5e or better. |
| Status | Red/Amber | Solid ON | Fault condition detected | Access EBO workstation and review error log. See section "EBO Workstation Errors." |
| Status | Red/Amber | Slow Flash (1/sec) | Warning condition (non-fatal) | Monitor system. Warning may clear after next poll cycle. |
| Status | Green | Solid ON | All systems operational | Normal operation |
| Status | Green | OFF | Not operational or starting | Wait for startup (up to 60 sec). If persists, power-cycle controller. |
| Comm (optional) | Yellow | Flash | BACnet MSTP or Modbus communication active | Normal if SmartX is on MSTP backbone or Modbus gateway role |
Solid Red/Amber Status LED: A fault has been recorded in the controller's event log and persists until manually cleared or the fault condition resolves. Access the SmartX via EBO workstation (Administration > Devices > Select Controller > View Logs) to identify the fault code and timestamp. Do not ignore this—it indicates a condition that will affect system stability or data integrity.
Fast-Flashing Blue Network LED: Indicates active BACnet/IP traffic. This is normal during normal operation. If the LED continuously flashes even during idle periods (no user commands), check for excessive discovery traffic. A rogue BACnet router or misconfigured scanner may be polling the network too frequently, consuming bandwidth.
Slow-Flashing Blue Network LED (DHCP mode): The controller is attempting to obtain an IP address from a DHCP server. Wait 30–60 seconds. If the LED does not become solid blue, the DHCP server is unreachable:
Power LED OFF: Controller has no 24V power. This is the first and most common failure mode. Verify:
| Power | Network | Status | Startup? | Condition | Next Step |
|---|---|---|---|---|---|
| ON | Flashing Blue | Green | No | Normal DHCP acquisition in progress | Wait 60 sec |
| ON | Solid Blue | Green | No | Operational, no faults | Continue monitoring |
| ON | Solid Blue | Red Solid | No | Fault detected | Review EBO error log |
| ON | Solid Blue | Red Flash | No | Warning (non-critical) | Monitor; may resolve automatically |
| ON | OFF | OFF | Yes | Starting up | Wait up to 60 sec |
| OFF | OFF | OFF | N/A | No power | Check 24V supply and circuit breaker |
| ON | Flashing Blue | Flashing Amber | Yes | Firmware update in progress | Do NOT power-cycle; wait for completion |
| Error Code | Log Message | Root Cause | Field Solution |
|---|---|---|---|
| PSU_FAIL | "Power Supply Fault Detected" | 24V supply unstable or below threshold (typically <20V) | Check 24V transformer output with multimeter. Look for burnt components near power connector. If output is 0V, transformer is dead; replace. If 20-24V but unstable, check for short circuit in controller. |
| CPU_RESET | "Processor Watchdog Reset" | CPU hung or firmware loop | Power-cycle controller. If resets repeatedly within 1 min, firmware is corrupted; reload via EBO firmware update tool. |
| HEAP_OVF | "Memory Exhaustion: Java Heap Full" | Too many active alarms, trends, or subscriptions | Reduce number of simultaneous alarms. Archive old trend data. Simplify point subscriptions in EBO. Restart controller if needed. |
| TEMP_FAULT | "Processor Temperature Exceeded" | Controller mounted in enclosed space without ventilation | Ensure controller has at least 2 inches of clearance on all sides. Install small cooling fan if in hot environment. Check that air vents on controller are not blocked. |
| Error | Indicator | Cause | Resolution |
|---|---|---|---|
| DHCP_TIMEOUT | Network LED flashing, no IP address assigned after 5 min | DHCP server unreachable or not responding | Check network path to DHCP server (ping gateway from workstation). Assign static IP via EBO or mini-serial port on controller. Verify DHCP server is enabled and has available leases. |
| GATEWAY_UNREACHABLE | "No Route to Gateway" in EBO logs | Default route not set or gateway is offline | Check gateway IP in controller network settings. Ping gateway from workstation. Verify gateway device (router/firewall) has power and is connected. |
| DNS_RESOLUTION_FAILED | "Cannot resolve hostname" (if using DNS names) | DNS server unreachable | Assign IP addresses directly instead of hostnames for SmartX and EBO. If hostnames required, verify DNS server IP is correct in controller settings. |
| ARP_CONFLICT | "Duplicate IP Address Detected" | Two devices on same network have same IP | Use EBO to rescan network and identify duplicate IP. Change one device to unique IP. |
| PACKET_LOSS_HIGH | "Network Packet Loss >10%" in diagnostics | Network congestion or poor cable quality | Check for excessive traffic on switch. Test cable with a network cable tester (should show all pairs crimped correctly). Consider separating BAS traffic to dedicated VLAN. |
| BACnet Error | Symptom | Cause | Field Fix |
|---|---|---|---|
| No BACnet IP Port (BVLC) | EBO cannot discover controller over IP | BACnet/IP service not running on controller | Restart controller. Check EBO Devices panel to verify BACnet/IP port is enabled in driver config. |
| Unauthorized BACnet Write | Cannot change point values from EBO | Controller security settings restrict writes | In EBO Administration > Security, add user group with write permissions. Ensure your EBO user account is in correct group. |
| Invalid COV Subscription | Alarms not updating in real-time | COV (Change of Value) not enabled on point | In EBO, select point > Properties > Enable COV Subscription. Also verify controller point configuration has COV threshold set (not infinite). |
| BACnet Routing Loop | "Circular routing detected" in diagnostics | Two BACnet routers creating loop path | Disable redundant router or reconfigure router hierarchy. Use EBO Network Topology tool to visualize path. |
Schneider SmartX controllers can connect to distributed I/O modules via UNC (Unified Network Controller) series and internal I/O slots. Bus faults are among the most common field issues:
| Fault Type | Module Offline | Symptom | Root Cause | Solution |
|---|---|---|---|---|
| UNC Module Offline | Yes | Points on that module show "Unknown" | Module powered down or RS-485 bus disconnected | Check module power (LED should glow). Verify RS-485 cable (twisted pair) is connected at both ends. Check for loose screw terminals. |
| RS-485 Termination | Intermittent | Points flicker or update sporadically | Missing or incorrect termination resistors (should be 120Ω at each end of RS-485 bus) | Measure resistance across RS-485 pair at module. If >200Ω, termination is missing. Add 120Ω resistor across + and - at each end of the backbone. |
| Address Conflict | Module offline | Two UNC modules with same RS-485 address | During module installation, unique address not assigned | Use UNC module's local commissioning tool (usually a keypad) to change address. Verify each module has unique address (e.g., 1, 2, 3). Restart controller after changes. |
| Cable Break | All modules on bus offline | No communication on entire I/O bus | Physical break in RS-485 cabling (e.g., cut by installer) | Inspect cable path. Look for cuts, kinks, or pinches. Use continuity tester on cable. Splice or replace cable if damaged. Test again. |
| Baud Rate Mismatch | Module intermittently online/offline | Module connects, then disconnects (cycling) | Controller and module configured for different baud rates | Check SmartX I/O bus settings (typically 9600 or 19200 baud). Verify all UNC modules are set to same rate. Change one side to match the other. |
| Onboard I/O Slot Error | Onboard analog inputs not reading | Sensor signal present but point shows "Unknown" in EBO | I/O module not detected by main CPU | Power-cycle controller. Check that I/O module is fully seated in slot and latch is engaged. If still offline, module may be failed; swap with spare. |
SpaceLogic is Schneider's native controls engine (software) that runs on SmartX hardware. Errors here are software-related:
| Error | Message in EBO | Cause | Resolution |
|---|---|---|---|
| Logic Compile Error | "Application failed to load: Syntax error in logic block XYZ" | Error in SpaceLogic program | In EBO, go to Logic Editor > Review block XYZ for typos or invalid connections. Recompile and reload. |
| Insufficient Memory | "Logic heap exhausted; unable to allocate 1024 bytes" | Too many function blocks or large data arrays | Simplify logic program. Remove unused blocks. Split into multiple controllers if necessary. |
| Scheduler Overrun | "Logic cycle time exceeded (expected 1000ms, took 1200ms)" | Logic program taking too long to execute | Optimize logic blocks (remove redundant calculations). Increase scan cycle time if critical timing not required. Reduce number of simultaneous computations. |
| Script Execution Error | "BQL Script error: Undefined variable 'OutdoorTemp' at line 42" | Programming error in BQL (Schneider's scripting language) | Review BQL script for variable typos. Ensure point reference paths are correct. Use EBO script editor's syntax checker. |
| Recursive Block Loop | "Detected circular reference: Block A→B→A" | Function block connected to itself indirectly | Review block connections in logic editor. Break circular reference by removing one connection or adding a delay block. |
EBO is Schneider's web-based SCADA/HMI interface. Errors here are workstation-side and affect visualization, not field controller operation.
| Error | Log Location | Root Cause | Field Fix |
|---|---|---|---|
| Database Connection Failed | EBO Administrator > System Logs > Database | PostgreSQL service not running or credentials incorrect | Check if PostgreSQL service is running (Windows Services > postgresql). Verify database username/password in EBO Administrator > System Configuration. Restart EBO service. |
| Archive Data Expired | Graphics show "Data Not Available" for trends | Historical trend data deleted by retention policy (default 90 days) | Enable long-term archival in EBO Administrator > Data Retention. Consider external database backup. |
| Session Timeout | User logged out while editing | Session idle timeout exceeded (default 30 min) | Increase session timeout in Administrator > Security > Session Management. Not a fault; expected behavior. |
| SSL Certificate Expired | EBO will not start; HTTPS errors in browser | HTTPS certificate for EBO workstation past expiration date | Generate new certificate in EBO Administrator > Security > HTTPS Configuration. Redeploy to all users. |
| Backup Corruption | "Cannot restore from backup" | Backup file was not written completely | Manually trigger new backup in EBO Administrator > Maintenance > Backup. Verify backup file has size >100MB (if much smaller, incomplete). |
| Problem | Symptom | Cause | Solution |
|---|---|---|---|
| Points Show "Unknown" | All points on a particular controller appear gray/unknown in graphics | EBO lost communication with SmartX controller | Check SmartX Network LED (should be solid blue). Ping SmartX IP from workstation. If unreachable, verify network path. Restart EBO device driver for that controller. |
| Trend Graph Missing Data | Trend display shows gaps or blank sections | Controller lost power or connectivity during that period, so no data was recorded | This is expected behavior. Data gaps indicate loss of connectivity. Restore power to controller and wait for real-time data to resume. |
| Setpoint Changes Not Sticking | User changes a setpoint via EBO, but it reverts after 1 second | Controller prioritization preventing write (point locked at higher priority) | Check controller point configuration. If output is at "Manual" or "Override" priority, local override is preventing remote writes. Clear override at controller or increase EBO write priority. |
| Animation Not Updating | Graphical elements (gauges, colors) not responding to point changes | COV subscription not active on that point | In EBO point settings, enable "Subscribe to Changes." Restart controller. Refresh EBO graphics view. |
| Report Generation Failed | Scheduler cannot generate daily PDF reports | Report template has invalid point references | In EBO Reports > Templates, verify all point paths are correct and points exist. If point was deleted, update template. Regenerate report. |
| Log Entry | Meaning | Action |
|---|---|---|
| "Controller offline for 5 minutes" | SmartX controller lost Ethernet connectivity | Investigate network issue. Ping controller IP. Check switch port. Review SmartX Network LED. Restart if needed. |
| "Point occupancy override active" | Point has been manually overridden at controller or via priority scheme | To clear override: In EBO, find point > release override. Or at controller keypad, clear manual mode. |
| "Database transaction timeout" | A write operation to a point took too long to complete | Usually transient. If repeated, indicates network latency. Check network performance. May need to move EBO and controllers to lower-latency network segment. |
| "Duplicate equipment detected: SmartX-01 and SmartX-04 have same Device ID" | Two controllers configured with same unique ID | Change Device ID of one controller in EBO Administration > Devices. Restart controller. |
| "License validation failed" | SmartX or EBO license has expired or is invalid | Contact Schneider Electric for license renewal or activation key. Workstation will operate in demo/degraded mode until license restored. |
Updating SmartX controller firmware or EBO workstation software can fail at various stages. Failure recovery depends on the stage where it stopped.
| Stage | Error Message | Cause | Recovery |
|---|---|---|---|
| Download | "Firmware download from server failed (HTTP 404)" | Server unreachable or file path incorrect | Check internet connectivity from EBO workstation. Verify correct firmware version URL in EBO Administrator. Retry from browser directly if possible. |
| Verification | "Checksum mismatch: expected AABBCC, got 112233" | Corrupted download | Delete partial download file. Retry update. If persists, try different network path (different switch/route). |
| Pre-Flash | "Insufficient flash memory: 2MB available, 5MB required" | Controller memory full (too many stored alarms/trends) | Clear event log and archived trends on controller. Reduce stored history. Retry update. |
| Flash Write | "Flash write timeout after 45 seconds" | Network interruption during upload, or controller too slow | Ensure network is stable (no VPN, busy switch). Disable any antivirus scanning on EBO workstation. Retry. If persists, try via wired Ethernet (not WiFi). |
| Post-Flash Validation | "Firmware validation failed" | Corrupted firmware file written | Reload firmware immediately. If validation fails again, check controller power supply (may be sagging under load). Use external bench PSU at exactly 24V. |
| Startup After Update | Controller boots but EBO cannot discover it (driver error) | Driver incompatibility with new firmware version | Check EBO manufacturer for driver update. Update EBO system software first, then retry controller firmware update. |
When SmartX controllers integrate with non-Schneider BACnet devices:
| Problem | Error Indicator | Cause | Solution |
|---|---|---|---|
| Cannot discover remote BACnet device | Device not appearing in EBO network scan | Device not responding to BACnet I-Am messages, or on different BACnet router segment | Manually add device IP in EBO BACnet Configuration. Verify device is powered and has BACnet/IP enabled. Ping device IP from EBO workstation. Check firewall rules allow port 47808 (BACnet BBMD). |
| Read from remote device always returns 0 | BACnet reads succeed but value stuck at 0 | Property index or object ID incorrect in SmartX BACnet read subscription | In EBO, verify BACnet object instance number (e.g., Analog Input 50) matches remote device. Use BACnet explorer tool to browse remote device and confirm correct object ID. |
| Writes to remote device rejected | "Write Access Denied" BACnet error | Remote BACnet device has security or priority locks | Check remote device permissions (many devices default to read-only for remote access). Adjust write priority on SmartX to match remote device's allowed write level. |
| Intermittent BACnet communication | Reads/writes work sometimes, fail other times | BACnet router congestion or BBMD timeout | Reduce BACnet polling rate in EBO (increase interval). Verify BBMD (Broadcast/Multicast Distribution Model) is configured if crossing subnets. Test with smaller data requests first. |
When a SmartX system exhibits faults, follow this diagnostic sequence:
Observe all LED states on the SmartX controller: