Overview
Distech Controls ECLYPSE Connected System Controllers and EC-BOS-8/6 supervisory servers form cloud-connected building automation systems. This guide covers ECLYPSE ECY series controller errors, EC-BOS supervisor faults, BACnet communication issues, controller LED diagnostics, Envysion configuration errors, firmware management failures, I/O module detection problems, and cloud connectivity faults. ECLYPSE systems log errors through multi-channel LED indicators and comprehensive cloud-based logging accessible through the Envysion platform.
ECLYPSE Controller LED Pattern Reference
ECLYPSE controllers use a two-LED system (Power and Status) with specific color and blink patterns indicating operational state and fault conditions.
| LED | Color | Blink Pattern | Status | Meaning |
|---|
| POWER | Green | Solid | Normal | 24VDC supply present and stable |
| POWER | Green | Slow blink (1 sec on/off) | Warning | 24VDC supply voltage fluctuating; check transformer capacity |
| POWER | Amber | Solid | Warning | Low 24VDC voltage (below 22V); verify supply transformer rating |
| POWER | Amber | Slow blink | Warning | 24VDC unstable with sag/surge events; check for high inrush loads |
| POWER | Red | Any | Critical | 24VDC supply failure or fuse blown; check input power and transformer |
| POWER | Off | N/A | Critical | No power or main fuse open; verify 120/240VAC input and circuit breaker |
| STATUS | Green | Solid | Normal | Controller running normally; all systems operational |
| STATUS | Green | Slow blink (1 sec on/off) | Normal | Bootup sequence in progress; wait 2-3 minutes |
| STATUS | Green | Fast blink (500ms on/off) | Normal | Firmware update in progress; do not power cycle |
| STATUS | Amber | Solid | Warning | Non-critical warning; cloud connection issue or pending configuration |
| STATUS | Amber | Slow blink | Warning | Network connectivity degraded; communication retries active |
| STATUS | Amber | Fast blink | Warning | Configuration mismatch with Envysion; re-download configuration |
| STATUS | Red | Solid | Critical | Critical fault; controller in safe mode or watchdog triggered |
| STATUS | Red | Slow blink | Critical | Firmware corrupted or boot failure; perform factory reset |
| STATUS | Red | Fast blink | Critical | Hardware failure detected; controller requires replacement |
| STATUS | Off | N/A | Critical | Controller powered down or not responding |
Two-LED Coordination
The Power and Status LEDs work together to communicate overall system health:
- Both Green (solid): All systems normal, full operation
- Power Green, Status Amber: Non-critical warning; device operational but degraded
- Power Green, Status Red: Critical fault; device non-operational
- Power Red/Amber, Status any: Power supply problem; status LED may not illuminate correctly
ECLYPSE ECY Controller Error Codes
ECLYPSE controllers log errors in onboard flash memory and cloud log. Access via Envysion dashboard or local diagnostic port.
Power and Hardware Faults
| Code | Error | Cause | Solution |
|---|
| E0001 | Power Supply Out of Range | 24VDC < 19V or > 29V | Check 24VDC at controller terminal; measure transformer secondary; verify load is within rating; replace PSU if voltage erratic |
| E0002 | Main Fuse Blown | Fuse current exceeded (typically 10A fuse) | Identify short circuit in wiring; test with multimeter in ohms mode (should read high impedance); replace fuse; if blows again, address root cause |
| E0003 | DRAM Failure | DRAM self-test failed | Perform cold power cycle; if error persists, DRAM is faulty—replace controller |
| E0004 | Flash Memory Error | Flash write failed or corruption detected | Attempt factory reset; if unsuccessful, flash memory is damaged—replace controller |
| E0005 | Processor Fault | CPU self-test detected hardware failure | Unrecoverable hardware fault; replace controller |
| E0010 | Real-Time Clock Battery Low | RTC battery < 2.5V | Replace RTC battery; if battery fails immediately, check for short on RTC circuit |
Bootup and Initialization Errors
| Code | Error | Cause | Solution |
|---|
| E1001 | Configuration Load Failed | Configuration file corrupted or incomplete during boot | Power cycle controller; if persists, perform factory reset and re-download from Envysion |
| E1002 | Firmware Integrity Check Failed | Firmware checksum mismatch; firmware corrupted or incomplete | Perform firmware re-flash using Envysion firmware update tool; verify stable network during update |
| E1003 | I/O Module Detection Failed | One or more I/O modules not responding during initialization | Verify I/O modules are properly seated; reseat connectors; check power to modules; test each module individually |
| E1004 | Database Initialization Error | Controller unable to initialize onboard database | Perform factory reset and re-download configuration; if error persists, replace controller |
| E1010 | Boot Timeout | Controller exceeded boot timeout (> 10 minutes) | Check for infinite loops or corrupted startup program; review configuration size; perform factory reset if necessary |
Network and Connectivity Faults
| Code | Error | Cause | Solution |
|---|
| E2001 | BACnet Network Initialization Failed | BACnet stack or Ethernet driver failed to initialize | Verify Ethernet cable is connected; check network card is detected; test with known-good cable; restart controller |
| E2002 | Duplicate BACnet Device ID | Duplicate BACnet Device ID detected on network | Use Envysion network scanner; identify device with conflicting ID; reconfigure one device with unique ID |
| E2003 | Invalid Network Configuration | IP address, gateway, or netmask incorrect | Verify network settings in Envysion controller properties; confirm IP is unique on network; restart networking |
| E2010 | Ethernet Link Down | Physical network connection lost | Check Ethernet cable connection; test with known-good cable; verify network switch port is active; reseat RJ45 connector |
| E2020 | BACnet Bus Timeout | No response from BACnet device within timeout window | Verify device is powered and online; check network path; ping device from workstation; verify firewall allows BACnet traffic |
| E2030 | Foreign Device Registration Failed | BBMD registration failed (for ECLYPSE-to-remote-network integration) | Verify BBMD IP address is correct; confirm BBMD is accepting registrations; check firewall UDP port 47808 |
| E2100 | Cloud Connection Lost | Controller unable to reach Envysion cloud platform | Check internet connectivity from controller; verify firewall allows cloud connection; check Envysion platform status page |
| E2101 | Cloud Authentication Failed | Controller credentials invalid or expired | Re-authenticate controller in Envysion; verify controller serial number matches assigned device; check for credential expiration |
| E2102 | Cloud Sync Timeout | Configuration sync with cloud took > 30 seconds | Retry sync from Envysion; check internet bandwidth; reduce configuration size if very large; verify cloud server is responsive |
I/O and Point Configuration Errors
| Code | Error | Cause | Solution |
|---|
| E3001 | Analog Input Module Not Detected | Analog module not responding at startup | Verify module is properly inserted; check module power supply; test module in different slot if possible; replace if faulty |
| E3010 | Digital Input Read Timeout | Digital input not responding | Check input wiring; verify 24VDC signal presence; test with multimeter; replace input module if wiring verified |
| E3020 | Analog Output Overload | Analog output driving excessive load or shorted | Disconnect load; test with resistor load; verify load specifications; replace output module if faulty |
| E3030 | Digital Output Short Detected | Digital output detected excessive current draw (short circuit) | Disconnect load from output; measure load resistance; repair shorted load or verify wiring; test with known-good load |
| E3040 | Point Engineering Value Out of Range | Calculated value exceeds configured min/max limits | Verify sensor reading is correct; adjust engineering limits in Envysion if sensor is operating correctly; recalibrate sensor if drifted |
| E3050 | I/O Module Address Conflict | Multiple I/O modules assigned same address | Verify each I/O module has unique address; reconfigure duplicates using DIP switches or module software; re-download configuration |
| E3060 | I/O Database Exceeds Limit | Total I/O point count exceeds module capacity | Count all I/O points in Envysion; remove unused points; consolidate logic; upgrade to larger module if necessary |
Firmware and Software Errors
| Code | Error | Cause | Solution |
|---|
| E4001 | Firmware Update Failed - Network Error | Network connectivity lost during firmware download | Verify network is stable; restart firmware update process; check firewall allows firmware download port; retry with wired connection |
| E4002 | Firmware File Checksum Error | Downloaded firmware file corrupted | Re-download firmware from Envysion; verify file integrity; clear browser cache and retry download |
| E4003 | Insufficient Flash Space for Update | Controller flash storage full; no space for firmware | Perform factory reset to clear old firmware; or remove configuration and retry update; verify flash is not damaged |
| E4010 | Program Syntax Error | Downloaded program contains invalid syntax | Review Envysion program compiler output for error line; correct syntax; re-download program |
| E4020 | Program Exceeds Memory Limit | Program size larger than available controller memory | Optimize program logic; remove unused function blocks; split program across multiple controllers; upgrade controller type |
| E4030 | Circular Logic Detected | Program contains circular dependency | Review program block connections; identify circular reference; restructure logic to break cycle; re-download |
Cloud and Envysion Integration Errors
| Code | Error | Cause | Solution |
|---|
| E5001 | Envysion Configuration Mismatch | Downloaded configuration version doesn't match Envysion database | Re-download current configuration from Envysion; verify no conflicting downloads in progress; refresh Envysion browser cache |
| E5010 | Cloud Data Sync Failed | Trend data or event log unable to upload to cloud | Check internet connection; verify Envysion cloud is accepting data; retry sync manually; check cloud storage quota |
| E5020 | Trend Upload Timeout | Trend data upload to cloud exceeded timeout | Reduce trend data volume; increase upload frequency; check cloud bandwidth; verify cloud server is responsive |
| E5030 | Point Definition Mismatch | Point definitions in controller don't match Envysion definitions | Re-download configuration from Envysion; verify points were downloaded successfully; perform configuration verify/repair in Envysion |
Watchdog and Recovery Errors
| Code | Error | Cause | Solution |
|---|
| E6001 | Watchdog Timer Triggered - System Reset | Firmware hung or infinite loop; watchdog forced reset | Check Event Log for events preceding watchdog; review program logic for infinite loops; verify CPU isn't overloaded |
| E6010 | Watchdog Recovery Successful | Controller recovered from watchdog reset; system re-initialized | Informational; monitor for recurring watchdog resets; investigate root cause if resets persist |
EC-BOS Supervisor Error Messages
EC-BOS-8 and EC-BOS-6 supervisory servers are cloud-connected gateways managing multiple ECLYPSE controllers. Errors appear in EC-BOS web interface and cloud dashboard.
EC-BOS System Errors
| Message | Severity | Cause | Resolution |
|---|
| "Database Connection Lost - Check Server Status" | Critical | Database service crashed or became unreachable | Restart EC-BOS database service from server admin console; check disk space on database drive; verify database server network connectivity |
| "EC-BOS Licensing Expired - System Disabled" | Critical | License key has expired | Renew license through Distech Controls portal; apply new license key in EC-BOS admin settings; contact vendor for extension |
| "Backup Storage Full - Archive Disabled" | High | Backup partition or external storage at capacity | Move archived data to larger storage; expand backup partition; delete old backups if necessary |
| "System Time Out of Sync - Please Correct" | Medium | EC-BOS system clock drifted significantly (> 60 seconds) | Manually set correct time in EC-BOS system settings; or enable NTP time synchronization; verify network time server is reachable |
EC-BOS Controller Management Errors
| Message | Severity | Cause | Resolution |
|---|
| "Controller Offline - Last Seen 2 Hours Ago" | High | ECLYPSE controller not communicating with EC-BOS | Verify controller is powered and online; check network/cloud connectivity; check controller firmware version matches EC-BOS expectations; restart controller if necessary |
| "Configuration Download Failed - Timeout" | High | Configuration failed to download to controller | Retry download; verify controller network connectivity is stable; reduce configuration size if very large; check for network congestion |
| "Controller Firmware Incompatible with EC-BOS" | Medium | Controller firmware version not compatible with EC-BOS version | Update controller firmware to compatible version; or update EC-BOS to version supporting controller firmware; consult compatibility matrix |
| "Device Not Responding to Configuration Sync" | Medium | Controller not acknowledging configuration sync request | Cycle controller power; verify controller is online; check controller Event Log for sync errors; manually trigger configuration download |
Data and Logging Errors
| Message | Severity | Cause | Resolution |
|---|
| "Trend Database Approaching Capacity (85% Full)" | Medium | Trend storage is filling up | Archive old trend data to external storage; reduce trend sample frequency; delete low-priority trends; expand database storage |
| "Event Log Corruption Detected - Some Entries Lost" | Medium | Event log database corrupted; some historical entries unrecoverable | Restore event log from backup if available; accept loss of corrupted entries; export remaining log for archival |
| "Cloud Trend Upload Failed - Retry Queued" | Medium | Unable to upload trend data to cloud; will retry automatically | Check internet connectivity; verify cloud service is accepting uploads; monitor for auto-retry completion |
Envysion Platform Configuration Errors
Beyond controller and EC-BOS errors, Envysion platform generates configuration-level errors visible in the web interface.
Configuration Validation Errors
"Invalid Point Engineering Range: Min > Max"
- Cause: Engineering minimum value configured larger than maximum
- Action: Open point properties in Envysion; correct engineering limits so Min < Max
"Unresolved Device Reference in Logic"
- Cause: Program block references device/controller that is offline or deleted
- Action: Identify offline device; bring online or remove reference; re-download configuration
"Duplicate Point Name Detected"
- Cause: Two points configured with identical name
- Action: Rename one of the points to unique name; best practice uses hierarchical naming (e.g., "AHU1.Supply_Temp")
"Cloud Storage Quota Exceeded"
- Cause: Trend data or backup files have exceeded cloud storage limit
- Action: Archive old data to local storage; delete unnecessary backup copies; upgrade cloud storage plan if needed
Field Troubleshooting Workflow
Phase 1: Quick Assessment
- Check Power LED (should be green)
- Check Status LED pattern
- Verify Ethernet cable is connected
- Check that Envysion shows controller as "Online"
Phase 2: LED Pattern Diagnosis
- Refer to LED Pattern Reference table
- Note LED color and blink pattern
- If LED is red, check power supply voltage immediately
- If LED is amber, access Envysion to see what warning is active
Phase 3: Network Connectivity
- Ping controller IP from workstation:
ping <eclypse_ip>
- Check Ethernet LED on controller (should indicate link)
- Verify controller is on same subnet as workstation
- Test cloud connectivity by checking Envysion status page
Phase 4: Access Diagnostic Logs
- Log into Envysion platform
- Navigate to controller details page
- Open "Event Log" or "Diagnostics" tab
- Filter for errors with timestamps matching the issue
Phase 5: Perform Soft Reset
- Power cycle controller by removing 24VDC for 30 seconds
- Restore power and observe LED sequence
- Wait 3-5 minutes for complete boot