CCR Controller
A dedicated control unit that manages the operation of one or more constant current regulators. Provides local or remote control of brightness steps, monitors system status, and interfaces with the ALCMS for centralised airfield lighting management.
Image disclaimer: For identification and illustration only. It may show a product by another manufacturer and may not depict the exact item described; it is not a statement of any product’s quality, approval or performance. Third-party image and trademark rights belong to their owners. See full notice.
What Is It?
A CCR Controller is a dedicated microprocessor‑based unit that provides local or remote control and monitoring of constant current regulators (CCRs). It typically interfaces with one or multiple CCRs, allowing operators to select brightness steps (intensity levels), monitor output current and voltage, and receive fault alarms. The controller can be a standalone panel with physical push‑buttons, indicators, and a small display, or a more advanced unit with a touchscreen HMI. It communicates with the CCRs via a serial link (RS‑485) or Ethernet and often interfaces with the Airfield Lighting Control and Monitoring System (ALCMS) for centralised operation. The CCR Controller is an essential component for systems where the CCRs themselves do not have an integrated operator interface or where remote control from a central location is required.
Purpose & Function
The CCR Controller exists to give operators command and visibility over a CCR that has no built-in operator interface of its own, or to consolidate control of multiple CCRs from a single point rather than requiring someone to interact with each unit individually at its physical location. Its monitoring function — output current, voltage, and fault status — serves the specific purpose of catching a developing problem (a fault, an unexpected current deviation) before it escalates into a lighting outage, giving maintenance staff the chance to intervene proactively. By bridging communication between the CCR and the broader ALCMS, the controller's purpose extends beyond local control: it makes an individual CCR's status and behaviour visible and controllable from the centralized control room where airfield-wide operational decisions are actually made.
Where Is It Used?
CCR Controllers are deployed in various airfield environments where centralised or remote control of AGL brightness is needed:
- Control Towers: For quick manual override of lighting intensity based on weather or operational needs.
- Electrical Equipment Rooms: Adjacent to CCR banks for local control during maintenance or commissioning.
- Central Control Rooms: As a backup or supplement to the ALCMS workstation, providing dedicated hardware control.
- Remote Substations: Where CCRs are located far from the main control room, a local controller allows on‑site adjustment.
- Legacy System Upgrades: Retrofitted to older CCRs to add modern control and monitoring capabilities.
Installation & Location
The controller is fitted into a 19″ rack or wall-mounted enclosure, most often in the electrical equipment room adjacent to the CCR bank it manages, with a duplicate or supervisory unit sometimes built into the tower cab or central control room desk. Communication cabling — RS-485, Ethernet, or fibre depending on the model — is daisy-chained or home-run from the controller to each CCR's communication port, routed separately from power cabling to limit induced noise. The unit is fed from the same 24V DC or 230V AC control supply as the CCRs it monitors, with a battery-backed real-time clock retaining settings through a power interruption. Where controllers serve a remote substation, they are mounted close to the CCR bank so a technician can access local control during commissioning or maintenance without needing the central workstation.
How Does It Work?
The CCR Controller communicates with each CCR over a dedicated communication link (RS‑485 Modbus, Ethernet, or fibre). It sends command messages to set the desired brightness step (e.g., Step 1‑5) and receives status responses containing the actual current, voltage, alarm flags, and internal temperature. The controller processes this data and presents it to the operator via a user interface — either a small LCD with push‑buttons, a touchscreen, or indicator lamps. The controller also logs events and can generate alarms for faults such as overcurrent, loss of regulation, or communication failure. Many CCR Controllers include a real‑time clock for time‑stamped logging and can be configured with multiple control modes (manual, automatic, or scheduled). In automatic mode, the controller may adjust brightness based on ambient light sensors or a pre‑programmed schedule. The controller typically provides both local and remote access, with remote access via the ALCMS or a web interface.
System Architecture & Control Logic
Physical Construction
The CCR Controller is generally built into a 19-inch rack-mount chassis or a wall-mounted enclosure for installation within the equipment room alongside the CCRs it serves. The front face carries an operator interface — physical push-buttons and LED step/fault indicators on basic units, or a touchscreen HMI on advanced models — set into a powder-coated steel or aluminium fascia. Internally, a microprocessor or PLC-based control board handles the RS-485 or Ethernet communication with each CCR, with isolated I/O modules and surge-protected terminal blocks along the rear or base for field wiring. A separate low-voltage power supply module, often with battery backup for settings retention, feeds the electronics, and the enclosure includes cable glands or a gland plate for control and communication cable entry. Units intended for equipment shelters rather than air-conditioned rooms may add a sealed, fan-cooled enclosure rated for a wider temperature range.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| Number of Controlled CCRs | 1 to 32 (expandable) |
| Communication Protocols | Modbus RTU (RS‑485), Modbus TCP, Ethernet/IP |
| User Interface | Push‑buttons + 4‑line LCD, or 7″–10″ touchscreen |
| Brightness Steps | 5 steps (2.8A, 3.4A, 4.1A, 5.2A, 6.6A) |
| Power Supply | 24V DC or 230V AC |
| Alarm Outputs | Relay contacts (Form C), audible buzzer |
| Data Logging | Internal memory for 1000+ events |
| Real‑Time Clock | Yes, battery‑backed |
| Control Modes | Manual, automatic (light sensor), scheduled |
| Enclosure | Panel‑mount or free‑standing, IP54 front |
| Standards | IEC 61822, FAA AC 150/5345-10 |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Supply Voltage | 24V DC (nominal) or 230V AC, model dependent |
| Backup Power | Battery-backed supply for real-time clock and settings retention |
| Communication Wiring | Shielded twisted pair (RS-485) or structured Ethernet cabling to each CCR |
| Cable Run Length | Up to 1200m per RS-485 segment (repeaters/hubs for longer or larger CCR counts) |
| Alarm Wiring | Form C relay contacts plus audible buzzer output to annunciator/ALCMS |
| Isolation | Isolated I/O modules between control logic and field/CCR wiring |
| Surge Protection | Surge-protected terminal blocks on communication and control lines |
| Earthing/Grounding | Rack/enclosure bonded to equipment-room earth bus |
| Power Source | Equipment-room mains supply, ideally UPS-backed |
Applicable Standards
IEC 61822
Electrical installation and performance requirements for AGL constant current regulators and associated controllers
FAA AC 150/5345-10
Specification for Constant Current Regulators and Regulator Monitors (includes control interfaces)
ICAO Annex 14
General requirements for AGL control and monitoring systems
EN 61822
European harmonised standard for AGL CCRs and control equipment
Installation Requirements
Enclosure Mounting
MechanicalFit the rack-mount chassis or wall enclosure in the equipment room within cable reach of the CCRs it serves, allowing clearance for door opening and rear cable access.
RS-485/Ethernet Cabling to CCRs
ElectricalRun and terminate the communication cabling to each CCR at the surge-protected terminal blocks, keeping runs within the cable length and topology limits of the protocol.
Power Supply Connection
ElectricalTerminate the 24V DC or 230V AC supply feeding the low-voltage power supply module, confirming the battery-backed section for settings retention is fitted and charged.
I/O & Alarm Wiring
ElectricalWire the isolated I/O modules and alarm relay outputs through to the monitoring system, confirming each channel maps to the correct CCR or fault condition.
CCR Address & Network Configuration
SystemsAssign a unique communication address to each connected CCR and configure the controller's network parameters before the link is tested end to end.
Cable Entry Sealing
MechanicalSeal the gland plate or cable glands at the control and communication cable entry points, keeping the enclosure rated to its intended environment.
Pre-Energisation Sign-off
DocumentationRecord cabling terminations, CCR addresses, and configuration settings as-built before the controller is first energised.
Testing & Commissioning
Control Wiring & Addressing Check
Pre-EnergisationVerify wiring and communication addressing between the controller and each CCR it manages, confirming no cross-wired or duplicate addresses before energisation.
Communication Link Verification
EnergisationEstablish the communication link (serial, Modbus, or Ethernet) to every connected CCR and confirm live data exchange before relying on the controller for control.
Step Command & Response Test
EnergisationCommand each brightness step through the controller and confirm every connected CCR responds at the correct current, ruling out addressing or protocol errors.
Monitoring & Alarm Accuracy
EnergisationCross-check the controller's displayed current, voltage, and fault status against direct CCR readings, confirming no discrepancy in the monitored values.
Local/Remote Handover Test
Final AcceptanceVerify switchover between the controller's local panel and remote/ALCMS control produces no conflicting commands to the CCRs.
Comms Loss Fail-Safe Test
Final AcceptanceDisconnect the communication link and confirm each CCR holds its last commanded state safely rather than reverting unpredictably.
Documentation & As-Built Sign-off
Final AcceptanceRecord link verification, step-response, and fail-safe test results in the commissioning dossier for handover.
Inspection & Maintenance
Communication Cable Check
AnnualInspect RS-485 or Ethernet cabling, connectors, and termination for damage or corrosion, a common cause of lost communication with CCRs.
Backup Power Test
AnnualTest the UPS or dedicated battery backup supplying the controller so power dips don't cause reboots that lose unsaved settings or event logs.
Firmware Compatibility Review
As neededCoordinate and test any firmware update against connected CCR versions before deployment to prevent register-mapping mismatches.
User Interface Check
AnnualInspect push-buttons, membrane keypad, or touchscreen for wear, scratches, or delamination, and keep spare parts on hand.
Ambient Environment Check
Semi-annualVerify the equipment shelter's climate control keeps the controller within its rated operating temperature range for reliable operation and display readability.
Event Log Backup
QuarterlyExport and archive event logs and configuration settings so a fault or reboot doesn't result in lost operational history.
Common Field Issues
Communication Cable Faults
RS‑485 or Ethernet cable damage, loose connections, or incorrect termination are common causes of loss of communication between the controller and CCRs. Regular cable inspection and use of proper shielded cables with correct grounding are essential.
Power Supply Failure
The controller may be powered from the same source as the CCRs. Power dips or interruptions can cause the controller to reboot, losing unsaved settings or event logs. A UPS or dedicated power supply with battery backup is recommended.
Firmware Incompatibility
Updates to the CCR firmware may change the communication protocol or register mapping, causing the controller to misinterpret data. Coordinated firmware updates and thorough testing are necessary.
User Interface Wear
Physical push‑buttons and membrane keypads can wear out over time due to frequent use. Touchscreens can suffer from scratches or delamination. Spare parts and regular maintenance are recommended.
Ambient Temperature Effects
Controllers installed in unheated equipment shelters may experience extreme temperatures that affect LCD readability or electronic reliability. Climate control or selecting controllers with wide operating temperature ranges is advisable.
Troubleshooting Guide
Loss of Communication with One or More CCRs
Device Reboots or Loses Settings on Power Dip
Controller Misreads or Misdisplays CCR Data
Unresponsive Push-Buttons, Keypad, or Touchscreen
Display Unreadable or Controller Unreliable in Extreme Temperature
Failure Modes & Root Causes
Communication Interface Failure
Backup Battery / Memory Retention Failure
Display Degradation
Keypad / Touchscreen Wear
Surge Damage to I/O Ports
Firmware Corruption
Enclosure Thermal Extremes
Safety & Operational Notes
Isolate the CCR Before Internal Work
Electrical SafetyThe controller's own electronics are low-voltage, but they interface directly with the CCR's high-voltage output stage; isolate and lock out the associated CCR and verify zero energy before opening the controller enclosure or working on interconnecting wiring.
ESD-Sensitive Electronics
OperationalUse anti-static precautions when handling the controller's microprocessor board, display module, or communication interface cards.
Physical Lockout Over Software Disable
Electrical SafetyWhere the controller is networked or ALCMS-integrated, use a physical lockout on the CCR during hands-on work rather than relying on a software-disabled or local-only mode, which a remote command could still override.
Coordinate Step and Fault Overrides with ATC
OperationalManual brightness overrides or fault-acknowledgement actions at the controller directly affect live circuit behaviour; coordinate significant changes with ATC rather than treating them as routine local adjustments.
Verify Readback Against Actual Circuit State
OperationalTreat controller readouts as an aid, not proof, of circuit status; confirm output current, voltage, and fault status at the CCR itself before relying on the controller display alone for a safety-relevant decision.
Restore to Compliant State
ComplianceConfirm all brightness steps, alarms, and communication links are correctly functioning before closing out the work and returning the controller to unattended operation.
Engineering & Expert Notes
A Comms Fault Can Look Exactly Like a CCR Fault
DiagnosticsWhen the controller loses its RS-485/Ethernet link to a CCR, the operator often sees the same "no response" symptom as an actual CCR failure, and chasing the wrong end first wastes a dispatch. Verify the communication link itself, cable and address configuration included, before assuming the CCR being polled has actually failed.
Test the Fail-Safe, Not Just the Normal Path
TestingA controller that switches steps correctly under normal operation can still fail to fall back safely if it loses comms with the ALCMS mid-command. Run an actual comms-loss fail-safe test as part of commissioning and periodic checks, rather than inferring safe behaviour from normal-mode function alone.
Firmware Compatibility Deserves a Check Before Any CCR Swap
MaintenanceReplacing one CCR in a mixed-age fleet with a newer unit can silently break the controller's addressing or command set if firmware versions have drifted apart over years of piecemeal replacement. Confirm firmware compatibility across the fleet before swapping in a new or refurbished CCR rather than assuming plug-and-play compatibility.
Local/Remote Handover Needs Re-Testing After Any Panel Change
CommissioningA local/remote handover that worked correctly at original commissioning can be quietly broken by a later HMI firmware update or ALCMS integration change, and the fault often only surfaces the next time an operator actually needs to take local control during an incident. Re-verify the handover function after any related system update, not only at initial installation.
Back Up the Event Log Before Troubleshooting, Not After
TroubleshootingAn intermittent fault's only real evidence is often buried in the controller's own event log, and a power cycle or reset performed as a first troubleshooting step can overwrite or clear exactly the history needed to diagnose it. Pull and archive the event log before any reset when chasing an intermittent issue.
Ambient Environment Affects Controller Life More Than Its Datasheet Suggests
ReliabilityA controller rated for a wide operating temperature range can still see accelerated display or touchscreen degradation in a poorly ventilated equipment room that runs hotter than the room's design intent. Include an ambient environment check in routine maintenance, not just the controller's own internal diagnostics.
Frequently Asked Questions
Short answers about CCR controllers: what they control, interfaces, brightness steps, standards, maintenance and common faults.
Q1What is a CCR controller?
A CCR controller is a dedicated microprocessor-based unit that provides local or remote control and monitoring of constant current regulators. It lets operators select brightness steps, monitor output current and voltage and receive fault alarms, and it often interfaces with the Airfield Lighting Control and Monitoring System (ALCMS).
Q2What does a CCR controller do?
It sends commands to each CCR to set the brightness step and receives status data such as actual current, voltage, alarm flags and internal temperature. It shows this on a push-button and LCD panel or a touchscreen, logs events and raises alarms for faults like overcurrent, loss of regulation or communication failure.
Q3What brightness steps does a CCR controller select?
Five steps, corresponding to CCR output currents of 2.8 A, 3.4 A, 4.1 A, 5.2 A and 6.6 A. Control modes are manual, automatic from a light sensor, or scheduled.
Q4How does a CCR controller communicate with CCRs?
Over a serial or network link such as RS-485 Modbus RTU, Modbus TCP, Ethernet/IP or fibre, depending on the model. A single RS-485 segment can run up to about 1,200 m, and shielded twisted pair or structured Ethernet cabling should be routed separately from power cabling.
Q5How many CCRs can one controller manage?
Typically 1 to 32, expandable, so a single point can consolidate control of several regulators instead of operating each unit at its own location.
Q6Where is a CCR controller installed?
Usually in a 19-inch rack or wall-mounted enclosure in the electrical equipment room next to the CCR bank. Duplicate or supervisory units may sit in the tower cab or central control room, and remote substations may have a local controller for on-site adjustment.
Q7What power supply does a CCR controller need?
Typically 24 V DC or 230 V AC depending on the model, ideally from a UPS-backed equipment-room supply. A battery keeps the real-time clock and settings, and surge-protected terminal blocks protect the communication and control lines.
Q8Which standards apply to CCR controllers?
The main references are IEC 61822 and its European equivalent EN 61822, FAA AC 150/5345-10 (constant current regulators and regulator monitors, including control interfaces) and ICAO Annex 14. Always verify the current edition and your approved requirements.
Q9How often should a CCR controller be maintained?
Typical intervals are quarterly for event log backup, semi-annual for ambient environment checks, and annual for communication cable checks, backup power tests and user interface checks. Firmware updates should be tested against connected CCR versions first. Your approved maintenance programme takes precedence.
Q10Why has my CCR controller lost communication with a CCR?
Common causes are damaged or poorly terminated RS-485 or Ethernet cabling, connector corrosion, or a configuration mismatch such as baud rate, parity or IP addressing. Check cable continuity and shielding, confirm termination resistors are correctly placed and verify matching settings at both ends.
Related Components
Go Beyond the Component. Understand the Complete AGL System.
You have explored the component. Now understand how it works within the complete Airfield Ground Lighting system.
Learn AGL from fundamentals to design, installation, testing, photometry, commissioning, maintenance and troubleshooting through structured technical training at Precision AGL Academy.
Build practical knowledge. Understand the circuit. Read the standards. Troubleshoot with confidence.
Your next step in AGL starts here.
Need expert guidance on CCR controller selection, integration, or troubleshooting?
Precision AGL Academy provides advice on control system architecture, communication protocols, and integration with ALCMS for reliable AGL management.
Follow the Academy
Important Notice, Disclaimer & Limitation of Liability
Please read before relying on any content on this page.
- Purpose and intended users. This page on CCR Controller is an independent educational and informational reference for competent, suitably trained and authorised airfield ground lighting (AGL) and aerodrome electrical personnel. It is not professional engineering, legal or regulatory advice, and using it does not create any professional or client relationship.
- Safety. Work on series circuits, constant current regulators (CCRs), isolating transformers, cables, connectors and lighting equipment can be fatal. Always apply the aerodrome’s permit-to-work and isolation/LOTO procedures, prove dead, use correctly rated instruments and PPE, and follow the manufacturer’s instructions. Nothing here authorises work on live equipment or the bypassing of any safety device or interlock.
- Aviation operations. Nothing here authorises installation, modification, energisation, adjustment, return to service, a change of operating category (CAT I/II/III), a NOTAM or any aerodrome certification or approval decision. These rest with the aerodrome operator, the air navigation service provider and the competent regulator.
- Specifications, ratings and typical values. Descriptions, parameters, ratings, dimensions, photometric values, wattages, service lives, maintenance tasks and intervals, failure modes, certifications (for example CE, FCC, UL or IEC marks) and part or type designations are general, typical and indicative. They may not match any particular product, make, model or version, and they are not a datasheet, design, specification, selection, sizing, procurement or acceptance criterion. The manufacturer’s current documents, the approved design and the project specification prevail.
- Standards and regulations. References to ICAO, FAA, IEC, IEEE, ISO, BIS, DGCA and other standards are paraphrased summaries for orientation only. They may be incomplete or out of date, and standards are revised from time to time. Consult the current official editions. Following this content does not guarantee compliance with any law, standard or regulatory approval, and the regulator’s requirements always prevail.
- No warranty. Content is provided “as is” and “as available”, without warranty of any kind, express or implied, including accuracy, completeness, currency or fitness for a particular purpose. Real installations differ in design, equipment make and model, age and condition.
- Limitation of liability. To the fullest extent permitted by applicable law, Precision AGL Academy, Precision AGL Solutions and their owners, authors and contributors are not liable for any injury, death, loss, damage, downtime, penalty or regulatory consequence, whether direct or indirect, arising from the use of, reliance on, or inability to use this content. Nothing in this notice excludes or limits any liability that cannot lawfully be excluded or limited.
- Independence, brands and no endorsement. This is an independent publication. It is not affiliated with, sponsored by or endorsed by ICAO, the FAA, the IEC, DGCA, AAI, any airport, regulator, supplier or equipment manufacturer. Third-party names, product designations, standard designations and trademarks (including Megger®, Siemens, Eaton, Crouse-Hinds, ADB SAFEGATE, Fluke, ABB and Honeywell) belong to their respective owners and are used only for identification and description. Mention of a brand, product or supplier is not a recommendation, and we do not sell, supply or quote for any component described.
- Images and third-party content. Images and illustrations are shown to help identify the type of component. They may show products of various manufacturers, may not depict the exact item described, and are not a statement about any product’s quality, approval or performance. Copyright and trademarks in third-party images, logos and photographs belong to their respective owners and are not claimed as ours. If you are a rights holder and want an image removed, replaced or credited, email precisionaglsolutions@gmail.com with the page address and we will act promptly.
- Training and services. Mentions of training, courses, consultation, advice, selection, installation, calibration or other support, including the “Learn…Certify” pathway, describe learning stages and are not an offer, quotation, tender or promise of any result. Contacting us or our replying creates no engagement or duty of care; an engagement exists only under a written agreement. We are not a regulator or certification body, and completing any course or reading this content is not a certification, accreditation or authorisation to work on any aerodrome.
- Copyright, privacy and corrections. © 2026 Precision AGL Academy. All rights reserved. Text, structure, compilations and diagrams may be viewed for personal reference and internal training only; any other copying, republication or commercial use needs our written permission. If you email, telephone or message us, we use your details only to respond and handle your matter, in line with applicable Indian law including the Digital Personal Data Protection Act, 2023; please do not send confidential or security-sensitive information. To display this page your browser requests fonts, icons and images from third-party servers, which receive your IP address and browser details under their own policies. Content is reviewed periodically with no obligation to update. To report an error, safety concern or rights issue, write to precisionaglsolutions@gmail.com.