Carrier i-Vu Pro is a web-based building automation platform that integrates equipment controllers via CCN (Carrier Communications Network) bus protocol. This guide covers common error codes encountered in the i-Vu Pro web interface, CCN-specific communication errors, controller offline conditions, firmware management issues, and trend data collection faults. The i-Vu system logs errors through both controller LED indicators and the built-in event log, accessible via the i-Vu Pro dashboard.
Carrier controllers in i-Vu systems use standard LED patterns to communicate operational state. The exact LED configuration varies by controller type (Infinity Series, LS, LSx) but follows these general principles.
| LED | State | Meaning | Action Required |
|---|---|---|---|
| POWER | Solid Green | 24VAC supply present and within tolerance | None; normal operation |
| POWER | Blinking Green | Power supply fluctuating or low voltage condition | Check 24VAC input voltage; verify transformer secondary is not loaded beyond capacity |
| POWER | Red/Off | 24VAC supply failure or absent | Verify breaker is on; check transformer output; measure voltage at terminal block |
| STATUS | Solid Green | Controller normal, no faults active | None; normal operation |
| STATUS | Amber/Orange | Non-critical warning or device offline | Check i-Vu Pro dashboard; review system alarms; verify device online status |
| STATUS | Red | Critical fault; controller may be in safe mode | Immediately check i-Vu Pro web interface for alarms; access controller locally if web access fails |
| COMMUNICATION | Solid Green | CCN communication healthy, syncing with controller | None; normal operation |
| COMMUNICATION | Blinking Green | CCN activity detected, data transfer in progress | Wait for transfer to complete (typically < 10 seconds) |
| COMMUNICATION | Amber/Orange | No recent CCN communication within timeout window | Check CCN wiring; verify controller address on CCN bus |
| COMMUNICATION | Red | CCN bus error or controller offline to network | See CCN Communication Faults section below |
In systems with multiple connected controllers (typical in large buildings), each controller maintains independent LED status. A "master" controller or gateway typically shows:
The i-Vu Pro web application displays error messages and system alerts through a centralized dashboard. These errors are categorized by severity and logged with timestamps.
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| CONN-001 | "Server Unavailable" | i-Vu Pro server/gateway offline or network unreachable | Check network connectivity to i-Vu server; verify server is powered and running; check firewall rules for port 80 (HTTP) and 443 (HTTPS) |
| CONN-002 | "Gateway Not Responding" | Communications gateway (hardware interface between web server and CCN bus) failed | Power cycle gateway device; check CCN wiring; verify 24VAC supply to gateway; substitute known-good gateway if available |
| CONN-003 | "Database Connection Lost" | i-Vu database (trend data or configuration database) offline or corrupted | Restart i-Vu Pro service/application; verify database service is running (check database admin interface); restore from backup if corrupted |
| CONN-004 | "Session Timeout" | User session expired due to inactivity (typically 30 minutes) | Log out and log back in; if session persistence desired, adjust timeout setting in i-Vu admin panel |
| CONN-005 | "Authentication Failed" | Invalid username/password or user account disabled | Verify username and password are correct; if forgotten, use password reset function or contact system administrator |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| DEV-101 | "Device Offline: Equipment Controller #5" | Controller not responding on CCN bus for > 30 seconds | Check 24VAC power to controller; verify CCN wiring is connected; check CCN bus address in i-Vu configuration matches physical setting on controller |
| DEV-102 | "Device Not Found in Network" | Device configured in i-Vu but not discovered during network scan | Verify device IP/address and communication protocol in i-Vu settings; confirm device firmware version is compatible; perform device discovery/re-import from gateway |
| DEV-103 | "Duplicate Device ID Detected" | Two controllers have identical network address | Access each controller's address settings (usually via local interface or service panel); reassign unique address to one of the devices |
| DEV-104 | "Device Firmware Incompatible" | Controller firmware version not supported by current i-Vu version | Update controller firmware to compatible version (consult Carrier documentation for version compatibility matrix); or update i-Vu Pro to newer version |
| DEV-105 | "Unrecognized Device Type" | Device hardware type not recognized by i-Vu | Verify correct device type is selected in i-Vu configuration; confirm device is Carrier brand and compatible; contact Carrier support if device is new model |
The CCN (Carrier Communications Network) protocol uses a proprietary serial/network bus with address-based device identification.
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| CCN-201 | "CCN Bus Timeout" | No response from device within timeout window (typically 5 seconds) | Check physical CCN wiring for damage or disconnection; verify device power supply; check device CCN address matches configuration; test with loopback plug on gateway if CCN is open-ended |
| CCN-202 | "CCN Protocol Error: Invalid Checksum" | Corrupted data packet received from device | Usually transient; if persistent, check for noise on CCN bus (verify proper shielding and termination); test with shorter CCN cable run if possible |
| CCN-203 | "CCN Bus Collision Detected" | Multiple devices transmitting simultaneously on bus | This indicates faulty device transmitter; isolate each device on bus one at a time to identify failing device; replace device if consistently causing collisions |
| CCN-204 | "CCN Terminator Missing" | CCN bus impedance incorrect due to missing termination resistor | Verify 120Ω terminator resistor is installed at both ends of CCN cable run; install terminator if missing; verify terminator value with multimeter |
| CCN-205 | "Slave Device Not Responding to Master Query" | Subordinate device not responding to requests from master controller | Power cycle slave device; verify slave device address setting; check CCN communication path; reseat CCN connectors on slave device |
For i-Vu systems that integrate external BACnet devices:
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| BNET-301 | "BACnet Foreign Device Registration Failed" | Controller attempted BBMD registration but failed | Verify BBMD (Broadcast Management Device) IP address in i-Vu network settings; confirm BBMD is reachable and accepting registrations; check firewall for UDP port 47808 |
| BNET-302 | "BACnet Device Communication Lost" | BACnet-integrated device offline or unreachable | Check device IP address and port; verify device is powered; ping device IP from i-Vu server to confirm network path; check firewall rules |
| BNET-303 | "BACnet Object Not Found" | Configured BACnet object (point) does not exist on device | Verify object ID and instance number match actual device configuration; re-scan device in i-Vu to discover all available objects; confirm device firmware supports the object type |
| BNET-304 | "Invalid BACnet Property" | BACnet property read or write failed due to unsupported property type | Check BACnet device documentation for supported properties; adjust i-Vu mapping to use supported properties only |
Firmware management is critical for system stability. i-Vu Pro provides built-in firmware update functionality with specific error conditions.
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| FW-401 | "Firmware File Not Found" | Selected firmware file missing or file path incorrect | Verify firmware file is downloaded and stored in i-Vu firmware directory; check file name matches expected format; download fresh firmware from Carrier if file corrupted |
| FW-402 | "Firmware File Checksum Error" | Downloaded firmware file corrupt or incomplete | Re-download firmware file from official Carrier source; verify file integrity using MD5 or SHA checksum if provided; verify browser closed properly during download |
| FW-403 | "Device Not Ready for Firmware Update" | Device is in use or not in idle state required for update | Wait for all active operations to complete; ensure no users are actively controlling equipment through device; retry update after device idle for > 1 minute |
| FW-404 | "Insufficient Flash Memory for Update" | Device storage full; cannot store new firmware | Perform factory reset if firmware is corrupted; delete old firmware versions if multiple stored; check device storage usage in device status page |
| FW-405 | "Firmware Update Failed - Device Offline" | Device disconnected during firmware download | Verify network/CCN stability before retrying; check device power; test with shorter CCN cable if possible; retry update |
| FW-406 | "Firmware Version Mismatch" | Firmware intended for different hardware revision | Verify correct firmware file for specific hardware model; check device model number on physical device label; consult Carrier firmware matrix |
Trend data collection enables historical analysis and reporting. i-Vu manages trend databases with specific failure modes.
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| TREND-501 | "Trend Database Full" | Trend data storage reached maximum capacity | Archive old trend data to SQL Server or external backup; reduce trend sample frequency for lower-priority points; delete unused trend points |
| TREND-502 | "Trend Data Corruption Detected" | Trend database file corrupted or incomplete | Restore trend database from backup if available; recreate trend points and allow re-collection; check hard drive health (SMART status) if errors recur |
| TREND-503 | "Unable to Write Trend Data - Disk Full" | System hard drive or trend storage partition at capacity | Free up disk space by deleting old files or logs; archive/move trend data to external storage; expand disk capacity if storage quota insufficient for building size |
| TREND-504 | "Trend Collection Paused - Controller Offline" | Device offline for extended period; trend logging suspended | Restore device online status (see Device Offline errors); trend collection resumes automatically once device reconnected |
| TREND-505 | "Invalid Trend Configuration" | Trend configuration missing required parameters | Check trend point configuration in i-Vu admin; verify sampling interval is reasonable (typically 1 minute to 1 hour); confirm data type matches device point |
| Error Code | Message | Cause | Solution |
|---|---|---|---|
| BACKUP-601 | "Backup File Not Found" | Specified backup file doesn't exist or wrong path | Verify backup file path and name; list available backups in backup directory; create new manual backup if needed |
| BACKUP-602 | "Backup Restore Failed - Version Incompatible" | Backup created by different i-Vu version | Use backup matching current i-Vu version; update i-Vu Pro to version matching backup; or restore older backup and gradually update |
| BACKUP-603 | "Insufficient Disk Space for Restore" | Not enough free space to restore backup data | Delete old files or backups to free space; move files to external storage; expand disk capacity before retrying restore |
| BACKUP-604 | "Database Locked During Backup" | i-Vu processes using database during backup attempt | Stop i-Vu Pro service, perform backup, then restart service; or use scheduled backup during low-activity period |
Beyond error codes, i-Vu Pro displays human-readable system alarms in the central alarm page.
"High Zone Temperature: Zone A - 78°F (exceeds setpoint 72°F)"
"Equipment Offline: Chiller Unit 1 - Last Response 5 minutes ago"
"Trend Database 95% Full - 2% Remaining Capacity"
"Firmware Update Completed: Building Controller #3 - Success"
"Manual Backup Created: Configuration Database - 2.3 MB"
"User Login: Admin from 192.168.1.100"
ping <server_ip>Cable Management: CCN bus is susceptible to electrical noise. Keep CCN cables away from high-voltage wiring (transformer leads, 480V equipment). Use shielded twisted pair for long runs (> 50 feet). Verify shield grounding at both ends.
Preventive Maintenance: Test all device communication paths monthly by accessing each device in i-Vu. This identifies marginal connections before they cause downtime. Document baseline response times.
Capacity Planning: Track trend data growth rate and database size. Average growth is 1-2 MB per month per 100 devices depending on sample frequency. Plan for database expansion or archiving.
Firmware Strategy: Maintain a library of known-good firmware versions. Before field update, test firmware on non-critical equipment first. Document firmware version on device label for reference.
Temperature Compensation: Analog sensors (especially pressure and humidity) are temperature sensitive. If readings drift seasonally or with outdoor temperature changes, suspect sensor calibration drift. Recalibrate or replace sensor.
Redundancy Testing: If system has redundant controllers or gateways, regularly verify failover by temporarily isolating primary device. Failover should occur within 30 seconds; if longer, investigate network configuration.
Last updated: February 2026. Based on i-Vu Pro versions 7.0 through 7.5 and CCN protocol specification 2.0