How do you troubleshoot an ALCMS problem?
Work through the layers in order: communication, CCR selector, CCR, then circuit, telling ATC first and confirming status at the equipment.
An ALCMS troubleshooting flow traces a control problem layer by layer, starting with the simplest causes. First check whether the screen shows a communication alarm or out-of-date status, which points to the server, network or field controller. Next check the CCR selector: a CCR in Local or Off ignores remote commands, which is not a fault. Then check the CCR itself for an alarm or no output current (an open-circuit trip means the break is in the field circuit, not the regulator), and finally the circuit and fixtures if the CCR output is normal but the lights are wrong.
The failure flow entry shows what the system does when something fails. This entry shows how a person works toward where it failed. Throughout, ATC is told first, only authorised engineers work on the equipment, and status is checked at the CCR or in the field because a failed link can leave the screen out of date. After repair and test, the selector is returned to Remote and status is confirmed before ATC is told control is restored. Alarm codes and the exact checks come from the manufacturer and project documents.
Frequently Asked Questions
Q1Where do you start when an ALCMS command does not work?
Tell ATC if the lighting is affected, then work through the layers in order: the screen status and any communication alarm, the CCR selector, the CCR itself and finally the circuit. Starting with the simple causes saves time.
Q2Why check the CCR selector early?
A CCR left in Local or Off will ignore remote commands, which looks like a fault but is not one. It is a quick check at the CCR and a common cause of commands that seem not to work.
Q3What does a communication alarm point to?
It points to the path between the screen and the CCR: the server, the network, the field controller or its link. The alarm and the system documents say which part has lost contact, and a failed link can leave status out of date.
Q4Why not rely on the screen alone?
The screen shows what the system last reported. If a link has failed it can be blank or stale, so the real status is checked at the CCR or in the field before any conclusion is drawn.
Q5What if the CCR is healthy but the lights are wrong?
The fault is then likely in the circuit or the fixtures: an earth fault, a poor cable or connector joint, a failed lamp, or an isolating transformer or fixture fault on part of the circuit. A break in the main series loop would instead drop the output current to zero and show at the CCR. Authorised engineers test and repair it under the airport's procedure and safety rules.
Q6When can the system go back to remote control?
Only after the fault is repaired and tested, the selector is back in Remote, and the status is confirmed at the equipment and on the screen. ATC is then told that remote control is restored.
See It. Understand It. Then Learn How to Engineer It.
Recognising an AGL system visually is the first step. The next step is knowing how to design, install, test, commission and maintain them correctly.
Build Practical AGL Engineering Skills
Go deeper with structured training from Precision AGL Academy, covering:
Learn how each light, sign and circuit works as part of a complete airport lighting system, not just as an isolated diagram.