About Knowledge Hub Troubleshooting SOP Library Components Contact Get in Touch
Division 01 of 30

CCR Troubleshooting

Constant Current Regulator fault diagnosis — start-up and power, output current/voltage behaviour, intensity step control, protection and alarms, cooling and internal components, and monitoring/communication. Each topic follows the full engineering diagnostic record: symptom → observation → measurement → decision → fault location → root cause → verification → corrective action → preventive action.

95 / 95
Topics Published
06
of 6 Subsections Complete
11
Fields per Topic
01 · Start-Up & Power (20) 02 · CCR Output (20) 03 · Intensity Control (15) 04 · Protection & Alarms (15) 05 · Cooling & Internal Components (10) 06 · Monitoring & Communication (15)

01 · CCR Start-Up & Power

20 of 20 topics published
CCR-001 CCR Not Starting

Symptom — CCR does not enter run state when a start command is issued (local or remote/ALCMS). Front panel remains in standby/OFF; no output current is generated at the series circuit.

Equipment / System

Constant Current Regulator (CCR) — series circuit lighting control unit, thyristor or IGBT-regulated, rated 4–100 kW, 6.6A (or 20A/30A legacy) constant-current output, 5-step or stepless intensity control.

Possible Causes
HighEmergency stop or door interlock active — cabinet door open, E-stop latched, or interlock switch misaligned
HighStart command not received — faulty local start switch, broken control wiring, or ALCMS/PLC output not energized
HighInput supply fault — upstream MCB/breaker tripped, phase loss, or input voltage below undervoltage threshold
MediumControl circuit fuse blown — F1/F2 control fuse open, isolating the 24VDC or 230VAC control rail
MediumMain contactor not energizing — failed coil, mechanically stuck contactor, or auxiliary contact feedback mismatch
Medium24VDC control power supply failure — internal SMPS module has failed or is out of regulation
LowerPLC/controller fault or firmware lock-up — controller unresponsive, requires power-cycle or firmware reset
LowerProtection relay latched from a prior trip — earth fault, overcurrent, or overtemperature trip not yet reset
LowerMechanical/key interlock misaligned — key switch not in RUN/REMOTE position, or MCB handle interlock not engaged
Required Tools
True-RMS digital multimeter (CAT III)Clamp meterInsulation resistance tester (500V/1000V)CCR wiring diagram / O&M manualInsulated torque screwdriver setContinuity/probe test leads
Safety Precautions
  • CCR output can reach several kV under load depending on circuit length — never work on output terminals while the CCR is running or capacitors are charged.
  • Apply lock-out/tag-out (LOTO) on the CCR input isolator before any internal inspection. Treat all terminals as live until proven de-energized with a tested meter.
  • Follow site electrical safety procedure and the two-person rule for HV isolation. Use appropriate PPE.
Diagnostic Procedure
  1. ObservationCheck CCR front panel/HMI: is the power-on lamp lit? Is a fault/alarm indicator active? Note the exact displayed status and any alarm code before touching anything.
  2. ObservationInspect the E-stop button and cabinet door interlock switch. Confirm E-stop is released and the door is fully closed and latched.
  3. MeasurementWith power isolated and verified dead, or per LOTO procedure, measure incoming 3-phase supply voltage at CCR input terminals L1-L2-L3.
  4. MeasurementCheck continuity of control circuit fuses (F1/F2).
  5. MeasurementMeasure the 24VDC control supply output terminals.
  6. MeasurementMeasure contactor coil terminals A1-A2 for correct coil voltage when a start command is issued.
  7. MeasurementVerify the start command signal at the PLC/ALCMS digital input terminal, toggling the local start switch and confirming the state change.
  8. ObservationReview the CCR controller's alarm/event log for any latched fault blocking a fresh start.
  9. DecisionBranch based on findings: no input supply → upstream distribution. Supply present but no 24VDC → control power supply fault. 24VDC present but no start signal → control wiring/ALCMS fault. Start signal present but contactor doesn't pull in → contactor/coil fault. Contactor pulls in but CCR still doesn't run → controller/PLC fault or latched alarm.
  10. Fault LocationIsolate the fault to one subsystem: incoming supply, control circuit, contactor, PLC/controller, or interlock chain.
  11. Root CauseConfirm the specific failed component within the isolated subsystem rather than stopping at the subsystem level.
Test Points
Input terminals L1/L2/L3 (3-phase supply)
Control fuse F1/F2 continuity
24VDC control supply output
Contactor coil terminals A1-A2
Start command digital input (PLC/ALCMS)
E-stop loop continuity
Door interlock switch continuity
Controller alarm/event log
Root Cause Verification

Confirm the identified root cause by isolating the suspect component and re-testing in isolation before reassembly. Do not close out on a single successful start — verify stability across at least one full intensity-step cycle.

Corrective Action
  • Reset E-stop and confirm door interlock is fully latched before re-attempting start.
  • Restore upstream input supply / reset tripped distribution breaker after confirming no downstream fault caused the trip.
  • Replace blown control fuse with correct rating and type — do not upsize.
  • Repair or replace faulty start-command wiring, terminal, or ALCMS/PLC output card.
  • Replace failed contactor coil or contactor assembly if mechanically seized.
  • Replace the 24VDC control power supply module if out of regulation.
  • Power-cycle and, if required, reflash/reset the PLC controller per manufacturer procedure.
  • Clear the latched protection alarm only after the underlying trip cause has been independently confirmed resolved.
Preventive Action
  • Include monthly functional testing of E-stop and door interlock circuits in the CCR PM schedule.
  • Perform periodic insulation/megger testing of control wiring during scheduled maintenance windows.
  • Track contactor duty cycles and replace preventively based on manufacturer MTBF data.
  • Maintain a current firmware/configuration backup for each CCR controller.
  • Document the CCR start sequence and interlock chain in the site SOP.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist), SOP-CCR-04 (CCR Isolation & LOTO Procedure)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic, CCR Single Line Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-002 CCR Completely Dead

Symptom — No response at all from the CCR — no display, no indicator lights, no contactor activity, completely unresponsive to any command.

Equipment / System

Constant Current Regulator, all ratings — total loss-of-function condition at the unit level.

Possible Causes
HighTotal loss of input supply — upstream breaker fully open/tripped
HighMain input isolator open or contact-failed
MediumBlown main incoming fuse on all phases
MediumCatastrophic failure of internal control power supply
LowerRodent/insect damage to control wiring
LowerWater ingress causing an internal short that has tripped upstream protection
Required Tools
MultimeterClamp meterInsulation resistance testerInspection torchMain isolator key
Safety Precautions
  • Verify zero energy state with a proven meter before opening the cabinet.
  • Assume possible internal short or water ingress — inspect visually before re-energizing to avoid re-faulting the circuit.
  • If water ingress is suspected, do not re-energize until the cabinet is dried and inspected by qualified personnel.
Diagnostic Procedure
  1. ObservationConfirm the complete absence of all indications — display, LEDs, and cooling fan noise.
  2. MeasurementCheck the upstream distribution panel: is the dedicated CCR breaker/isolator ON and supply present at the panel?
  3. MeasurementTest at the CCR main input terminals — if the upstream breaker is on but no voltage reaches the CCR, suspect an open link or isolator fault in between.
  4. ObservationVisually inspect the CCR cabinet interior (after LOTO and a verified-dead check) for water ingress, burning, rodent damage, or loose main terminal connections.
  5. MeasurementCheck the main incoming fuses on all phases for continuity.
  6. DecisionNo supply at the panel → escalate to upstream distribution fault (see CCR-003). Supply present at panel but not at CCR → isolator/cabling fault. Supply present at CCR terminals but CCR still dead → internal catastrophic failure.
  7. Fault LocationIsolate to upstream distribution, the interconnecting cable/isolator, or an internal CCR failure.
  8. Root CauseIdentify the specific failed link — isolator contact, blown fuse element, corroded terminal, or internal component.
Test Points
Upstream distribution panel output
CCR main isolator, both sides
Main incoming fuses
CCR main input terminals
Root Cause Verification

After repair, re-energize under supervision starting from the isolator and confirm a normal power-up sequence before restoring the connected load.

Corrective Action
  • Restore or repair the upstream supply.
  • Replace the failed isolator or fuse.
  • Repair or replace the damaged interconnecting cable.
  • Dry and inspect the cabinet after water ingress before re-energizing.
  • Engage qualified repair support for a confirmed internal catastrophic failure.
Preventive Action
  • Verify upstream breaker/isolator condition during scheduled PM.
  • Seal cable entries and cabinet gaskets against water ingress.
  • Rodent-proof cabinet cable entries.
  • Include periodic thermal imaging of main terminals in the PM programme.
Related References

SOP: SOP-CCR-01, SOP-CCR-04

Standards: ICAO Annex 14, FAA AC 150/5345-10, IEC 61439

Diagram: CCR Single Line Diagram, Cabinet Layout Drawing

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-003 CCR Main Power Not Available

Symptom — The upstream feeder to the CCR shows no voltage — the CCR itself is not at fault, the source supply is de-energized.

Equipment / System

Constant Current Regulator and its dedicated upstream feeder/distribution path.

Possible Causes
HighUpstream substation/transformer outage
HighMain LV panel breaker for this feeder tripped or left open
MediumGenerator/UPS failure on standby supply
MediumCable fault between substation and the CCR feeder panel
LowerScheduled maintenance isolation not restored
LowerFuse blown at the upstream distribution board
Required Tools
MultimeterClamp meterDistribution panel keys and PPEAirport electrical single line diagram
Safety Precautions
  • Coordinate with the airport electrical control room before working on main distribution.
  • Verify correct feeder identification before any isolation work, to avoid affecting other live circuits.
Diagnostic Procedure
  1. ObservationCheck the main distribution board/substation status — alarms and breaker position indicators.
  2. MeasurementMeasure voltage at the LV panel busbar feeding the CCR circuit.
  3. MeasurementTrace the dedicated feeder breaker for this CCR and confirm its position and load-side voltage.
  4. DecisionBusbar itself dead → upstream supply/generator issue, escalate to the power engineering team. Busbar live but feeder breaker open/tripped → breaker-specific fault.
  5. Fault LocationIsolate to the substation/transformer, the main busbar, or the dedicated feeder breaker.
  6. Root CauseConfirm the exact failure — breaker trip cause (overload/fault), cable fault, or a genuine supply outage.
Test Points
Substation output
Main LV busbar
Dedicated CCR feeder breaker, load side
Feeder cable at the CCR end
Root Cause Verification

Confirm stable voltage over a minimum monitoring period before reconnecting the CCR load, and check for no repeat trip once load is restored.

Corrective Action
  • Restore upstream supply per the utility/generator procedure.
  • Reset the feeder breaker only after confirming there is no downstream fault.
  • Repair the faulty feeder cable.
  • Switch to standby/generator supply per the site contingency plan if required.
Preventive Action
  • Maintain the standby generator/UPS testing schedule.
  • Include periodic thermal imaging of main distribution.
  • Keep the single line diagram current and feeder labelling accurate.
Related References

SOP: SOP-ELEC-02 (Main Distribution Isolation Procedure)

Standards: ICAO Annex 14 (secondary power supply requirements), IEC 60364

Diagram: Airport Electrical Single Line Diagram

Case Study: Division 24 — Complete Runway Lighting Failure

Rev 0 — Initial issue
CCR-004 CCR Input Voltage Low

Symptom — CCR input terminals show voltage below rated tolerance (commonly below −10% of nominal); the CCR may run with reduced output, raise an undervoltage alarm, or fail to start depending on the configured threshold.

Equipment / System

Constant Current Regulator input supply and its feeder cable path.

Possible Causes
HighLong feeder cable run with excessive voltage drop
HighUndersized feeder cable for the connected load
MediumOverloaded upstream transformer or distribution circuit
MediumLoose or high-resistance connection upstream
LowerIncorrect transformer tap-changer setting
LowerSimultaneous heavy load on a shared feeder (e.g., coincident lighting start-up surge)
Required Tools
Multimeter with min/max holdClamp meterPower quality analyzer / voltage loggerCable sizing/voltage-drop calculation reference
Safety Precautions
  • Standard LV measurement precautions apply.
  • Be cautious of fluctuating readings, which may indicate an active fault condition rather than a steady-state drop.
Diagnostic Procedure
  1. MeasurementLog input voltage at the CCR terminals over a representative period, including at load switch-on, using a power quality analyzer or logging multimeter.
  2. MeasurementCompare against upstream distribution panel voltage at the same time to isolate whether the drop originates at source or along the feeder.
  3. ObservationCheck the feeder cable size and length against the original design/voltage-drop calculation.
  4. MeasurementInspect and torque-check all connections along the feeder path — terminals, joints, isolator contacts — looking for discoloration indicating overheating.
  5. DecisionDrop present at the panel too → upstream supply/transformer issue. Panel voltage normal but CCR terminal voltage low → feeder cable/connection issue.
  6. Fault LocationIsolate to the specific cable section or connection point using sequential voltage-drop measurement.
Test Points
Upstream panel busbar
Mid-run feeder junction (if accessible)
CCR input terminals
All load-side connections, for thermal/visual check
Root Cause Verification

After remedial work, re-log voltage under full load, including the peak intensity step, to confirm it stays within tolerance.

Corrective Action
  • Rectify loose or high-resistance connections.
  • Upgrade an undersized cable.
  • Rebalance loads across feeders where the drop originates from shared loading.
  • Coordinate with the utility on transformer tap setting if the drop originates upstream.
Preventive Action
  • Include a periodic voltage-drop survey in the PM programme.
  • Perform annual thermal imaging of feeder connections.
  • Review load management as airport lighting load grows over time.
Related References

SOP: SOP-CCR-02 (Periodic Electrical Testing)

Standards: IEC 60364 (voltage drop limits), FAA AC 150/5345-10

Diagram: Feeder Cable Route Drawing, Voltage Drop Calculation Sheet

Case Study: —

Rev 0 — Initial issue
CCR-005 CCR Input Voltage High

Symptom — Input voltage exceeds rated tolerance (commonly above +10%); this may trigger overvoltage protection or accelerate component wear even if no alarm is raised.

Equipment / System

Constant Current Regulator input supply.

Possible Causes
HighTransformer tap setting too high for actual site loading
HighLight loading on the distribution transformer causing voltage rise
MediumFaulty automatic voltage regulator (AVR) upstream
MediumIncorrect generator output voltage during standby operation
LowerCapacitor bank over-compensation on the network
Required Tools
Multimeter with min/max holdPower quality analyzerGenerator/AVR manual
Safety Precautions
  • Sustained overvoltage can stress and damage CCR components — do not repeatedly force-start against an active overvoltage alarm.
Diagnostic Procedure
  1. MeasurementLog input voltage over a representative period, noting peak values and their time of occurrence.
  2. ObservationCorrelate high-voltage periods with system loading — for example, overnight low-load periods — or with generator/standby operation.
  3. MeasurementCheck the upstream transformer tap position against the design record.
  4. DecisionOvervoltage correlates with light network loading → transformer tap/AVR issue. Overvoltage correlates with generator operation → generator AVR fault.
  5. Fault LocationIsolate to the transformer tap setting, the network AVR, or generator regulation.
Test Points
Transformer secondary
Upstream distribution panel
CCR input terminals
Generator output (if applicable)
Root Cause Verification

Re-log voltage after correction across varying load conditions, including a generator changeover test if standby power is involved.

Corrective Action
  • Adjust the transformer tap setting.
  • Repair or recalibrate the AVR.
  • Adjust the generator voltage regulator setting.
Preventive Action
  • Perform a periodic voltage survey across the full day/night load cycle.
  • Include an overvoltage check in the generator test schedule.
Related References

SOP: SOP-CCR-02, SOP-GEN-01 (Generator Test Procedure)

Standards: IEC 60364, FAA AC 150/5345-10

Diagram: Airport Electrical Single Line Diagram

Case Study: —

Rev 0 — Initial issue
CCR-006 CCR Input Phase Failure

Symptom — One or more input phases are missing or significantly unbalanced; the CCR protection trips on a phase-failure/unbalance alarm, or the CCR fails to start.

Equipment / System

Constant Current Regulator 3-phase input supply.

Possible Causes
HighBlown fuse on one phase upstream
HighSingle-pole breaker trip where a common-trip 3-phase breaker should be used
MediumLoose or burnt phase connection at a terminal
MediumBroken conductor in one phase of the feeder cable
LowerUpstream isolator contact failure on one pole
Required Tools
MultimeterClamp meterPhase rotation/sequence meterThermal camera (optional)
Safety Precautions
  • A missing-phase fault can leave equipment partially live while appearing mechanically off — verify all three phases are individually dead before working on the circuit.
Diagnostic Procedure
  1. MeasurementMeasure phase-to-neutral (or phase-to-phase) voltage on all three phases at the CCR input terminals individually.
  2. ObservationNote which specific phase or phases show zero or abnormal voltage.
  3. MeasurementTrace the affected phase back through the isolator, fuse, and feeder to locate the break point using sequential voltage checks.
  4. ObservationInspect the affected phase's fuse, breaker pole, and terminal connections for visible damage or burning.
  5. DecisionThe fault lies between the two consecutive test points where voltage transitions from present to absent.
  6. Fault LocationIsolate to the specific fuse, breaker pole, terminal, or cable conductor.
Test Points
Upstream panel, all 3 phases
Isolator load side, all 3 phases
Fuse output, all 3 phases
CCR input terminals, all 3 phases
Root Cause Verification

Confirm balanced 3-phase voltage under load after repair; check phase sequence is correct if any conductor was reterminated.

Corrective Action
  • Replace the blown fuse.
  • Repair or replace the faulty breaker pole.
  • Repair the broken conductor or terminal connection.
  • Retorque all phase terminals.
Preventive Action
  • Include a 3-phase balance check in routine PM.
  • Use thermal imaging to catch developing high-resistance phase connections before failure.
Related References

SOP: SOP-CCR-02

Standards: FAA AC 150/5345-10, IEC 60364

Diagram: CCR Single Line Diagram

Case Study: —

Rev 0 — Initial issue
CCR-007 CCR Control Supply Failure

Symptom — Main 3-phase power is present at the CCR input, but the internal control circuit (24VDC or 230VAC control rail) has no power, so the CCR cannot process a start command even though it is electrically live.

Equipment / System

Constant Current Regulator internal control power circuit.

Possible Causes
HighFailed control transformer
HighBlown control circuit fuse
MediumFailed internal SMPS/24VDC power supply module
MediumLoose control transformer wiring
LowerInternal control PCB fault
Required Tools
MultimeterSpare control fuse of correct ratingSpare SMPS module, if available
Safety Precautions
  • Control circuit failure does not mean the CCR is de-energized — main input remains live. Follow full LOTO before internal inspection.
Diagnostic Procedure
  1. ObservationConfirm main input voltage is present (per CCR-004/005/006) while display and control functions remain unresponsive.
  2. MeasurementCheck control transformer primary and secondary voltage.
  3. MeasurementCheck control circuit fuse continuity.
  4. MeasurementCheck the 24VDC (or applicable) output of the internal control power supply module.
  5. DecisionControl transformer output absent → transformer or its fuse. Transformer output present but 24VDC absent → SMPS module fault.
  6. Fault LocationIsolate to the control transformer, control fuse, or SMPS module.
Test Points
Control transformer primary
Control transformer secondary
Control fuse output
SMPS 24VDC output
Root Cause Verification

Confirm stable 24VDC (within ±5%) under full control load — all relays and indicators active — before returning to service.

Corrective Action
  • Replace the blown control fuse.
  • Replace the failed control transformer.
  • Replace the SMPS/control power supply module.
  • Re-terminate loose control wiring.
Preventive Action
  • Include a control supply voltage check in routine PM.
  • Keep critical spares — fuse, SMPS module — in site stores.
Related References

SOP: SOP-CCR-02, SOP-CCR-05 (Spares Management)

Standards: FAA AC 150/5345-10

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-008 CCR Auxiliary Supply Failure

Symptom — Auxiliary supply feeding non-critical CCR accessories — cabinet heater, cabinet lighting, socket outlet, auxiliary cooling fan — has failed while main CCR control and output functions remain normal.

Equipment / System

Constant Current Regulator auxiliary/accessory supply circuit.

Possible Causes
HighBlown auxiliary circuit fuse/MCB
MediumFailed auxiliary supply transformer
MediumTripped RCD on the auxiliary socket circuit
LowerFailed heater element causing circuit protection to trip
LowerMoisture ingress at auxiliary wiring
Required Tools
MultimeterClamp meterSpare fuse/MCB
Safety Precautions
  • Auxiliary circuits are often on separate protective devices — confirm which specific circuit is isolated before working, as the main CCR circuit may remain live.
Diagnostic Procedure
  1. ObservationIdentify which auxiliary function has failed — heater, lighting, socket, aux fan — and confirm main CCR operation is otherwise normal.
  2. MeasurementCheck the dedicated auxiliary fuse/MCB/RCD for trip status and continuity.
  3. MeasurementMeasure voltage at the auxiliary supply transformer output, if a separate transformer is used.
  4. ObservationInspect auxiliary wiring and the heater element for signs of moisture ingress or insulation damage that may have caused an RCD trip.
  5. DecisionProtective device trips again on reset → downstream fault (heater/wiring). Device holds after reset → likely a transient cause.
Test Points
Auxiliary fuse/MCB/RCD
Auxiliary transformer output
Heater element resistance
Auxiliary wiring insulation resistance
Root Cause Verification

Confirm the auxiliary circuit holds under load for an extended period, particularly through a heater cycling test, before closing out.

Corrective Action
  • Replace the blown fuse/MCB.
  • Reset the RCD only after the fault has been cleared and confirmed.
  • Replace the failed heater element.
  • Repair moisture-damaged wiring.
Preventive Action
  • Include the auxiliary circuit in routine PM checks.
  • Verify cabinet heater operation before onset of the monsoon/humid season.
Related References

SOP: SOP-CCR-02

Standards: FAA AC 150/5345-10

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-009 CCR Fuse Failure

Symptom — A specific fuse within the CCR — main input, control, or output-side — has blown, isolating its associated circuit; the failure mode depends on which fuse is affected.

Equipment / System

Constant Current Regulator internal fuse protection, any position.

Possible Causes
HighGenuine overcurrent/short-circuit fault downstream of the fuse
MediumFuse rating too low for the circuit's normal transient (e.g., inrush)
MediumAged or degraded fuse element
LowerIncorrect fuse type/rating installed at a previous replacement
LowerMoisture-induced fuse holder corrosion causing nuisance opening
Required Tools
MultimeterInsulation resistance testerSpare fuses of correct rating/typeFuse puller
Safety Precautions
  • Never replace a blown fuse without first checking for a downstream short circuit. Always test insulation resistance of the protected circuit before re-energizing. Never substitute a higher-rated fuse.
Diagnostic Procedure
  1. ObservationIdentify exactly which fuse has blown — main, control, or output — from its position and visual inspection/indicator.
  2. MeasurementBefore replacing, test insulation resistance and continuity of the circuit downstream of the blown fuse to check for a genuine short circuit.
  3. DecisionInsulation resistance low or a short found → locate and repair the downstream fault before replacing the fuse. Downstream circuit tests healthy → likely a nuisance blow (age, transient, or incorrect rating).
  4. Root CauseConfirm fuse rating and type match the CCR manufacturer's specification for that position.
Test Points
Fuse holder, both sides
Downstream circuit insulation resistance
Downstream circuit continuity
Root Cause Verification

After fitting a correctly rated fuse, monitor the circuit under normal load for repeat failure before closing out.

Corrective Action
  • Repair the downstream short/overload fault first.
  • Replace the fuse with the correct type and rating.
  • Replace a corroded fuse holder if applicable.
Preventive Action
  • Standardize fuse rating/type per manufacturer specification across all CCRs.
  • Maintain adequate correctly-rated spares.
  • Inspect fuse holders for corrosion during PM.
Related References

SOP: SOP-CCR-02, SOP-CCR-05

Standards: FAA AC 150/5345-10, IEC 60269

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-010 CCR MCB/Breaker Tripping

Symptom — An internal or dedicated feeder MCB/breaker trips, either on attempted start or during operation, cutting supply to the CCR or a CCR subsystem.

Equipment / System

Constant Current Regulator internal or dedicated feeder circuit breaker.

Possible Causes
HighGenuine overload on the protected circuit
HighShort-circuit fault downstream
MediumEarth leakage tripping an RCBO
MediumBreaker itself degraded and nuisance tripping
LowerAmbient temperature affecting the thermal-magnetic trip curve
LowerInrush current at start exceeding the breaker's instantaneous trip setting
Required Tools
MultimeterClamp meter (for load current)Insulation resistance testerBreaker curve reference/datasheet
Safety Precautions
  • Do not repeatedly reset a tripping breaker without investigation — repeated fault-current interruption can degrade the breaker and pose an arc-flash/fire risk.
Diagnostic Procedure
  1. ObservationNote whether the trip occurs immediately on closing (suggests short circuit/instantaneous trip) or after a delay under load (suggests thermal/overload trip).
  2. MeasurementMeasure load current on the protected circuit and compare against the breaker rating.
  3. MeasurementTest insulation resistance and continuity of the downstream circuit to rule out a short or earth fault.
  4. DecisionImmediate trip on closing with healthy downstream insulation → possible breaker fault or inrush exceeding the instantaneous setting. Delayed trip under a measured overload → genuine overload, review circuit sizing.
  5. Root CauseConfirm whether the breaker's trip curve/rating matches the circuit's design load and inrush characteristics.
Test Points
Breaker load-side current under normal operation
Downstream insulation resistance
Downstream continuity/earth fault loop
Root Cause Verification

After remedial action, monitor the circuit through several start/stop cycles, including the peak intensity step, before closing out.

Corrective Action
  • Repair the downstream short/earth fault.
  • Replace a degraded breaker.
  • Resize the breaker/circuit if genuinely overloaded.
  • Adjust breaker curve type if inrush-related and permitted by the manufacturer.
Preventive Action
  • Verify breaker selection against actual load/inrush data during design review.
  • Include breaker trip testing in periodic maintenance.
Related References

SOP: SOP-CCR-02

Standards: IEC 60947-2, FAA AC 150/5345-10

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-011 CCR Contactor Not Energizing

Symptom — Start command and control supply are both confirmed present, but the main contactor fails to pull in, so the CCR does not proceed to the output stage.

Equipment / System

Constant Current Regulator main contactor and its coil circuit.

Possible Causes
HighFailed contactor coil — open circuit
HighCoil voltage present but the contactor is mechanically seized
MediumIncorrect or mismatched coil voltage rating
MediumLoose coil wiring connection
LowerAn interlocking auxiliary contact (from a protection relay) preventing energization
LowerContactor coil overheated or damaged
Required Tools
MultimeterClamp meterReplacement contactor/coilMechanical operation check tool
Safety Precautions
  • The contactor may control a high-current output circuit — fully isolate before mechanical inspection or replacement.
Diagnostic Procedure
  1. MeasurementConfirm coil voltage is present at the contactor coil terminals (A1-A2) when start is commanded.
  2. ObservationIf voltage is present but the contactor doesn't pull in, with power isolated, gently attempt to move the contactor armature to check for mechanical seizure.
  3. MeasurementIf no coil voltage is present despite a confirmed start command, check for an open interlock — a protection relay auxiliary contact — in series with the coil circuit.
  4. DecisionVoltage present, mechanically free, but no pull-in → failed coil. Voltage present and seized → mechanical fault. No voltage → upstream interlock or wiring fault.
  5. Root CauseConfirm the exact cause via coil resistance measurement (open circuit = infinite resistance), or identify which interlock contact is open.
Test Points
Contactor coil terminals A1-A2
Coil circuit interlock contacts
Coil resistance, with power isolated
Root Cause Verification

After correction, cycle the contactor several times under no-load, then confirm normal pull-in and drop-out under load.

Corrective Action
  • Replace the failed coil/contactor.
  • Free and lubricate a mechanically seized contactor per manufacturer guidance, or replace it.
  • Clear the interlocking protection condition.
  • Retighten loose coil wiring.
Preventive Action
  • Include contactor mechanical/electrical checks in PM.
  • Track contactor operation count against rated mechanical life.
Related References

SOP: SOP-CCR-02

Standards: IEC 60947-4-1

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-012 CCR Emergency Stop Active

Symptom — CCR will not start because the emergency stop circuit is in a tripped/latched state, shown by an E-stop or safety circuit fault indication.

Equipment / System

Constant Current Regulator emergency stop / safety circuit.

Possible Causes
HighE-stop pushbutton physically latched, not released after a previous activation
MediumE-stop circuit wiring fault — an open loop
MediumSafety relay in the E-stop chain not reset
LowerA second E-stop station elsewhere in the loop (e.g., a remote panel) still latched
LowerDamaged E-stop button/contact block
Required Tools
MultimeterSafety relay reset procedure/manual
Safety Precautions
  • Never bypass or defeat an E-stop circuit to force a start. Always investigate and resolve the actual condition, and confirm no personnel are at risk before resetting.
Diagnostic Procedure
  1. ObservationPhysically inspect all E-stop stations in the circuit — CCR local, remote panel, associated equipment — for a latched/pressed button.
  2. MeasurementIf all buttons appear released, measure continuity across the full E-stop loop to identify an open section.
  3. ObservationCheck the safety relay/monitoring module status indicator for a fault or not-reset condition.
  4. DecisionLatched button found → release and reset. Loop open with all buttons released → wiring fault between stations. Safety relay shows a fault → relay or its wiring.
  5. Fault LocationIsolate to the specific E-stop station, wiring segment, or safety relay.
Test Points
Each E-stop station individually
E-stop loop continuity end-to-end
Safety relay status/reset input
Root Cause Verification

After reset, functionally test the E-stop circuit by deliberately activating and releasing it to confirm correct trip/reset behaviour before returning to service.

Corrective Action
  • Release the latched button.
  • Repair open wiring in the E-stop loop.
  • Replace a damaged E-stop button/contact block.
  • Reset or replace a faulty safety relay.
Preventive Action
  • Include an E-stop functional test in monthly PM.
  • Label all E-stop stations clearly.
  • Protect wiring runs from mechanical damage.
Related References

SOP: SOP-CCR-01, SOP-SAFETY-03 (E-Stop Functional Test)

Standards: IEC 60204-1 (Safety of machinery — electrical equipment)

Diagram: CCR Control Schematic, Safety Circuit Diagram

Case Study: —

Rev 0 — Initial issue
CCR-013 CCR Start Command Not Received

Symptom — All internal CCR conditions are healthy — supply, control power, and interlocks are clear — but the CCR does not start because no start signal arrives at its command input.

Equipment / System

Constant Current Regulator start-command interface, local switch through to ALCMS/PLC.

Possible Causes
HighFaulty local start pushbutton/selector switch
HighBroken or disconnected control wiring between the command source and the CCR
MediumALCMS/PLC output card fault, or the output not configured/energized
MediumIncorrect wiring at the terminal — wrong terminal number
LowerRemote/local selector switch in the wrong position
Required Tools
MultimeterALCMS/PLC diagnostic accessWiring diagram
Safety Precautions
  • Standard LV control circuit precautions apply. Coordinate with the control room before testing ALCMS outputs, to avoid unintended commands to other circuits.
Diagnostic Procedure
  1. ObservationConfirm the local/remote selector switch position matches the source from which the start command is being issued.
  2. MeasurementToggle the start command and measure at the CCR's command input terminal for a state change.
  3. MeasurementIf no change is seen at the CCR terminal, trace back toward the source, checking at intermediate terminals/junction boxes.
  4. ObservationAt the ALCMS/PLC end, confirm the relevant output point is being commanded and is physically energized — check the status LED on the output card, if available.
  5. DecisionSignal confirmed present at the source but not at the CCR → wiring fault in between. Signal absent even at the source output → ALCMS/PLC configuration or output card fault. Selector switch in the wrong position → operator/configuration error.
  6. Fault LocationIsolate to the specific wiring segment, terminal, selector switch, or ALCMS output point.
Test Points
Local start switch
Remote/local selector switch
Intermediate junction box terminals
CCR command input terminal
ALCMS/PLC output card status
Root Cause Verification

Confirm a clean, repeatable state change at the CCR terminal correlating exactly with the operator's command before closing out.

Corrective Action
  • Repair or replace the faulty pushbutton/selector switch.
  • Repair the broken wiring.
  • Correct the ALCMS/PLC output configuration.
  • Replace a faulty output card.
  • Correct the terminal wiring error.
Preventive Action
  • Include start-command path verification in commissioning and periodic PM.
  • Maintain accurate as-built wiring/IO schedule documentation.
Related References

SOP: SOP-CCR-01, SOP-ALCMS-02

Standards: FAA AC 150/5345-10

Diagram: CCR Control Schematic, ALCMS I/O Schedule

Case Study: —

Rev 0 — Initial issue
CCR-014 CCR Start Command Received but CCR Not Starting

Symptom — The start command is confirmed present at the CCR's input terminal by direct measurement, yet the CCR does not proceed to run — the fault lies internal to the CCR beyond the command interface.

Equipment / System

Constant Current Regulator internal controller and command-processing path.

Possible Causes
HighInternal controller/PLC fault preventing command processing
HighA latched internal alarm blocking start despite a valid command
MediumContactor circuit fault downstream of the confirmed command (see CCR-011)
MediumFirmware/logic requiring a specific command sequence — e.g., stop-then-start — that isn't being met
LowerInternal command relay/opto-isolator failure
Required Tools
MultimeterCCR controller diagnostic/service toolWiring diagram
Safety Precautions
  • Standard LV control circuit precautions apply. Internal diagnostics may require accessing live control circuitry — follow safe working practice.
Diagnostic Procedure
  1. ObservationRe-confirm, independently of the earlier check, that the start signal reaches the correct internal terminal with correct polarity/logic level.
  2. ObservationCheck the controller's alarm/status log for any latched condition blocking the start.
  3. MeasurementTrace the command signal internally from the input terminal through any interposing relay or opto-isolator to the controller's logic input.
  4. DecisionCommand confirmed reaching the controller cleanly with no latched alarm → controller/firmware fault. Command lost internally → interposing relay/isolator fault. Latched alarm present → resolve the specific alarm first via its own topic.
  5. Fault LocationIsolate to the controller itself, an internal interposing component, or a latched protection condition.
Test Points
CCR command input terminal
Interposing relay/opto-isolator, input and output
Controller logic input
Controller alarm/status log
Root Cause Verification

After correction, confirm the CCR starts reliably across multiple consecutive start commands, including after a controlled stop.

Corrective Action
  • Clear the specific latched alarm per its own topic.
  • Repair or replace the faulty interposing relay or opto-isolator.
  • Reset or update controller firmware per manufacturer guidance.
  • Replace the controller if a core fault is confirmed.
Preventive Action
  • Keep controller firmware version documented and current.
  • Include internal command-path verification in commissioning tests.
Related References

SOP: SOP-CCR-02

Standards: FAA AC 150/5345-10

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-015 CCR Repeated Start Failure

Symptom — The CCR fails to start on multiple consecutive attempts, whether from a specific recurring cause or an unresolved intermittent condition, rather than a single isolated no-start event.

Equipment / System

Constant Current Regulator, all subsystems — investigation spans the full start-up chain.

Possible Causes
HighAn underlying cause from CCR-001 through CCR-014 that has only been symptomatically reset, not resolved
HighA genuinely intermittent fault — loose connection or marginal component — that passes isolated testing
MediumProtection system re-latching immediately after each reset due to a persistent downstream fault
MediumControl power supply marginal/degrading under load
LowerOperator repeatedly attempting a start against an unresolved safety interlock
Required Tools
MultimeterData logger for repeated-attempt trendingCCR event log export tool
Safety Precautions
  • Repeated forced start attempts against an unresolved fault can cause component damage or a safety risk. Do not simply keep resetting and retrying without investigation.
Diagnostic Procedure
  1. ObservationExport and review the CCR event/alarm log across all recent failed start attempts to identify whether the same fault code recurs each time.
  2. DecisionSame specific fault code repeats → treat as that specific topic's fault not yet fully resolved; re-open the relevant investigation with more rigorous root cause verification. Fault codes vary or none is logged → treat as an intermittent fault per Division 22 methodology.
  3. MeasurementWhere an intermittent connection is suspected, perform a wiggle test — with power isolated — on suspect connectors/terminals while monitoring continuity.
  4. Root CauseConfirm root cause with a sustained multi-cycle test rather than a single successful start.
Test Points
As per the specific recurring fault code identified in the event log
Root Cause Verification

Require a minimum of five consecutive successful start/stop cycles, including under realistic field conditions (e.g., after an overnight cold soak), before closing out.

Corrective Action
  • Apply the specific recurring fault's corrective action, with emphasis on thorough root cause verification rather than a quick reset.
Preventive Action
  • Make event log review a standing part of any repeated-failure investigation.
  • Track recurring fault codes in the site failure database to catch developing problems early.
Related References

SOP: SOP-CCR-06 (Repeated Fault Investigation Procedure)

Standards: —

Diagram: —

Case Study: Division 23 — Root Cause Analysis; Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
CCR-016 CCR Unexpected Shutdown

Symptom — CCR was running normally and then shuts down without an operator-issued stop command, output current dropping to zero.

Equipment / System

Constant Current Regulator, running state — protection, supply, and command systems all in scope.

Possible Causes
HighA protection trip — overcurrent, earth fault, overtemperature (see the Protection & Alarms subsection)
HighA genuine loss of input supply
MediumAn unintended stop command from ALCMS/PLC
MediumControl power supply momentary failure/brownout
LowerInternal controller watchdog reset
Required Tools
MultimeterCCR event log export toolPower quality logger
Safety Precautions
  • Standard LV precautions apply. Treat an unexpected shutdown as a potential protection event until proven otherwise — do not force a restart without reviewing the cause.
Diagnostic Procedure
  1. ObservationImmediately review the CCR event/alarm log for the exact timestamp and logged cause of the shutdown.
  2. DecisionSpecific protection alarm logged → proceed to that alarm's specific topic in the Protection & Alarms subsection. No alarm logged → investigate the supply/command path.
  3. MeasurementIf no protection alarm, check for a logged loss of input supply at the shutdown timestamp, cross-referenced against site power monitoring if available.
  4. ObservationCheck the ALCMS/PLC command history for an unintended or scheduled stop command issued at that time.
  5. Fault LocationIsolate to the protection system, a supply interruption, the command system, or control power stability.
Test Points
CCR event/alarm log
Input supply logger
ALCMS/PLC command history
Control power supply stability
Root Cause Verification

Monitor the CCR through a full operating cycle, including peak-load periods, to confirm the shutdown does not recur.

Corrective Action
  • Address the specific protection cause identified.
  • Restore or stabilize input supply.
  • Correct ALCMS/PLC command logic.
  • Replace an unstable control power supply component.
Preventive Action
  • Ensure event logging is active and reviewed regularly.
  • Ensure ALCMS command logic includes safeguards against unintended stop commands.
Related References

SOP: SOP-CCR-02

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
CCR-017 CCR Restarting Automatically

Symptom — CCR restarts on its own after a stop/trip without an operator command — this may be an auto-restart function operating as designed, or a fault causing unintended cycling.

Equipment / System

Constant Current Regulator restart logic — internal configuration and/or ALCMS/PLC command sequencing.

Possible Causes
HighAuto-restart/auto-reclose function intentionally configured, operating after a transient trip — verify against design intent
MediumALCMS/PLC sending a repeated/looping start command due to a logic fault
MediumA marginal protection setting causing rapid trip-reset-trip cycling
LowerControl relay contact bouncing/chattering
Required Tools
MultimeterCCR configuration/parameter accessALCMS/PLC logic review access
Safety Precautions
  • Uncommanded restart of high-voltage output equipment poses a risk to personnel working nearby. Treat any circuit with unexplained auto-restart as potentially live at all times and apply LOTO before any physical work, regardless of its apparent OFF state.
Diagnostic Procedure
  1. ObservationCheck CCR configuration parameters for an enabled auto-restart/auto-reclose function and its configured delay/attempt count.
  2. DecisionAuto-restart intentionally configured → confirm this matches the design intent and site operating philosophy; if not, treat as a configuration error to correct. Auto-restart not configured in the CCR → review ALCMS/PLC command logic for a repeating or looping start command.
  3. MeasurementIf relay chattering/bouncing is suspected, physically inspect and test the specific control relay.
Test Points
CCR auto-restart configuration parameter
ALCMS/PLC command sequence log
Suspect control relay contacts
Root Cause Verification

Confirm the CCR behaves per the intended design — either staying off after a manual stop, or auto-restarting only per documented design logic — across several test cycles.

Corrective Action
  • Correct the auto-restart configuration to match design intent.
  • Fix the ALCMS/PLC repeating command logic.
  • Replace a chattering relay.
Preventive Action
  • Document the intended auto-restart philosophy clearly in the O&M manual and site SOP.
  • Review ALCMS logic changes through a formal change control process.
Related References

SOP: SOP-CCR-01, SOP-ALCMS-02

Standards: —

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-018 CCR Power-On Self-Test Failure

Symptom — CCR controller runs an internal power-on self-test (POST) at start-up and reports a failure, halting the start sequence before reaching run state.

Equipment / System

Constant Current Regulator controller and its monitored internal subsystems.

Possible Causes
HighInternal memory/firmware checksum failure
MediumA monitored internal sensor — current, voltage, or temperature — reading out of expected range at power-on
MediumAn internal communication bus fault between controller sub-modules
LowerA genuine internal hardware fault detected by the self-test
Required Tools
CCR controller diagnostic/service toolMultimeterManufacturer POST fault code reference
Safety Precautions
  • Standard LV/control circuit precautions apply. Do not attempt to bypass a POST failure — it exists specifically to prevent starting with a detected fault.
Diagnostic Procedure
  1. ObservationRecord the exact POST fault code or message displayed.
  2. ObservationCross-reference the fault code against the manufacturer's service manual to identify the specific flagged subsystem.
  3. MeasurementTest the specific flagged subsystem — sensor, module, or bus — per the manufacturer's guidance.
  4. DecisionConfirmed hardware fault in the flagged subsystem → component-level repair/replacement. Fault clears after a power cycle and does not recur → likely a transient condition; monitor closely.
Test Points
As specified by the manufacturer's POST fault code reference for the flagged subsystem
Root Cause Verification

After remedial action, power-cycle the CCR and confirm POST completes successfully across at least three consecutive power-up cycles.

Corrective Action
  • Replace or repair the specific faulty sensor/module identified.
  • Reflash/restore controller firmware if a checksum fault is confirmed.
  • Replace the controller if a core hardware fault is confirmed.
Preventive Action
  • Keep firmware backups current.
  • Avoid uncontrolled power interruptions during firmware updates.
  • Include POST result review in commissioning records.
Related References

SOP: SOP-CCR-02

Standards: —

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-019 CCR Internal Fault at Start-Up

Symptom — CCR displays a generic internal fault indication specifically during the start-up sequence — after POST, before reaching stable run state — distinct from a POST failure or a specific named protection alarm.

Equipment / System

Constant Current Regulator power electronics and start-sequence control logic.

Possible Causes
HighA transient internal fault detected during the soft-start/ramp-up sequence, e.g. a current spike beyond the expected start-up profile
MediumA control logic fault in the start sequencing itself
MediumAn internal component — thyristor/IGBT module, driver board — failing specifically under start-up electrical stress rather than at steady state
LowerA marginal internal connection that only fails under the inrush condition of starting
Required Tools
MultimeterClamp meter with inrush/peak captureCCR controller diagnostic toolManufacturer internal fault code reference
Safety Precautions
  • Internal fault conditions during start-up may indicate a partially failed power semiconductor. Treat with caution and fully isolate before any internal inspection — damaged components can retain unexpected charge or present a short-circuit hazard.
Diagnostic Procedure
  1. ObservationRecord the exact internal fault code/message and the precise point in the start sequence at which it occurs.
  2. MeasurementWhere possible, capture the current/voltage waveform during a start attempt to observe the fault's electrical signature.
  3. ObservationCross-reference the fault code against the manufacturer's internal fault code reference to identify the flagged internal subsystem.
  4. DecisionFault consistently occurs at the same point in the sequence → likely a specific component or logic fault at that stage. Fault occurs inconsistently → intermittent internal connection or marginal component, refer to Division 22 methodology.
  5. Fault LocationIsolate to the specific internal module/board flagged by the fault code.
Test Points
Thyristor/IGBT module gate signals
Driver board supply
Internal current sensor output during ramp-up (plus manufacturer-specific test points per fault code)
Root Cause Verification

After component-level repair, perform multiple start cycles under representative load, including at the highest intensity step used on site, to confirm the fault does not recur.

Corrective Action
  • Replace the specific faulty internal component/module identified.
  • Repair the marginal internal connection.
  • Update start-sequence control logic if a genuine logic fault is confirmed by the manufacturer.
Preventive Action
  • Schedule periodic internal inspection and connection torque-checks per the manufacturer PM schedule.
  • Monitor start-up current signature trends over time to catch developing component degradation.
Related References

SOP: SOP-CCR-02, SOP-CCR-05

Standards: —

Diagram: CCR Internal Power Circuit Schematic

Case Study: —

Rev 0 — Initial issue
CCR-020 CCR Display Not Initializing

Symptom — CCR powers up — contactor energizes, output may even be present — but the front panel display/HMI remains blank or does not complete its initialization sequence, leaving the operator without local status indication.

Equipment / System

Constant Current Regulator front panel display/HMI module.

Possible Causes
HighDisplay module power supply fault
HighDamaged or loose display ribbon/data cable
MediumDisplay module itself has failed
MediumController not sending display initialization data due to a communication fault
LowerDisplay firmware corruption
Required Tools
MultimeterCCR controller diagnostic toolSpare display module, if available
Safety Precautions
  • Standard LV/control circuit precautions apply. A blank display does not confirm the CCR is off — verify actual run/output status independently, e.g. via clamp meter on the output, before assuming a safe state.
Diagnostic Procedure
  1. ObservationConfirm whether the CCR is otherwise operating normally — contactor energized, output present — despite the blank display, to distinguish a display-only fault from a broader control fault.
  2. MeasurementCheck the display module's power supply voltage.
  3. ObservationInspect the display ribbon/data cable connection at both the display and controller ends for looseness or damage.
  4. MeasurementIf accessible, check for communication activity between the controller and display module, e.g. via diagnostic tool or activity LED.
  5. DecisionDisplay power absent → power supply/wiring fault. Display power present but no initialization → data cable or communication fault. Both confirmed healthy → the display module itself has failed.
Test Points
Display module power supply
Display ribbon/data cable connections
Controller-to-display communication link
Root Cause Verification

After remedial action, power-cycle the CCR and confirm the display completes full initialization and shows correct live status.

Corrective Action
  • Reseat or replace the display ribbon/data cable.
  • Replace the display module power supply.
  • Replace the display module.
  • Reflash display firmware if corruption is confirmed.
Preventive Action
  • Include display initialization check in routine PM start-up verification.
  • Keep a spare display module in site stores given its role in local diagnostics.
Related References

SOP: SOP-CCR-01, SOP-CCR-05

Standards: —

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
No topics match that search.

02 · CCR Output

20 of 20 topics published
CCR-021 CCR Output Current Zero

Symptom — CCR is in RUN with a commanded intensity step above 0% and no active alarm is displayed, but the output current feedback reads zero and the series circuit is completely dark.

Equipment / System

CCR power stage — thyristor/IGBT firing bridge, output (step-up) transformer, output current feedback sensor, and the series circuit loop to the isolating transformers.

Possible Causes
HighFiring/gate drive circuit not triggering the thyristor or IGBT bridge despite a valid run command
HighOutput-side fuse or output circuit breaker open
MediumOutput transformer primary or secondary winding open-circuited
MediumCurrent feedback sensor (shunt/CT) failed or its signal wiring to the controller broken, causing the controller to hold firing at a null point
LowerController firmware/logic fault holding the firing angle at zero despite a valid step command
LowerSeries circuit loop broken (open isolating transformer primary or damaged L-823 connector) — usually accompanied by an open-circuit alarm, but not always on older controllers
Required Tools
True-RMS clamp meter (loop-rated)Oscilloscope (for gate drive pulses)Insulation resistance tester (5kV)MultimeterCCR power stage schematicLoop continuity tester
Safety Precautions
  • Do not open the series circuit loop while the CCR is energized — an open loop under load can develop several kV at the break point.
  • Apply LOTO on the CCR input isolator before any internal inspection of the bridge or output transformer.
  • Confirm zero energy with a proven meter before handling output transformer or fuse terminals.
Diagnostic Procedure
  1. ObservationConfirm the CCR is in RUN with a commanded step above 0% and check specifically whether an open-circuit/no-load alarm is present — its absence points toward an internal firing or transformer fault rather than a loop break.
  2. MeasurementWith the unit isolated and LOTO applied, inspect the output fuse/breaker for continuity.
  3. MeasurementUsing an oscilloscope, check for gate drive pulses at the thyristor/IGBT bridge during a commanded run.
  4. MeasurementCheck output transformer primary and secondary winding continuity and insulation resistance.
  5. MeasurementVerify the current feedback sensor output and its wiring back to the controller.
  6. DecisionNo gate pulses → firing circuit fault. Gate pulses present but no output → bridge device or transformer failure. Output present internally but zero at the loop → loop break, escalate to circuit isolation resistance testing.
  7. Fault LocationIsolate to the firing circuit, the bridge device, the output transformer, the output fuse, or the series circuit loop.
  8. Root CauseConfirm the specific failed component by substitution or isolated component testing.
Test Points
Thyristor/IGBT gate drive signals
Output transformer primary terminals
Output transformer secondary/series circuit terminals
Output fuse/breaker continuity
Current feedback sensor signal
Root Cause Verification

After repair, run the CCR through its full intensity step range and confirm the clamp-meter reading at the output terminals matches each commanded step within tolerance, with no open-circuit alarm.

Corrective Action
  • Repair or replace the failed firing/gate drive circuit board.
  • Replace the failed thyristor or IGBT module.
  • Replace the blown output fuse or reset the output breaker after confirming no downstream fault.
  • Replace the failed output transformer.
  • Repair or replace the current feedback sensor and its wiring.
Preventive Action
  • Include a gate drive pulse check and output transformer megger test in scheduled PM.
  • Keep spare thyristor/IGBT modules and output fuses in site stores.
  • Verify current feedback sensor calibration during annual photometric testing.
Related References

SOP: SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-022 CCR Output Current Too Low

Symptom — CCR output current reads consistently below the value required for the commanded intensity step — lights are dim across the series circuit rather than fully off.

Equipment / System

CCR power stage and closed-loop current regulation circuit, series circuit with isolating transformers and lamps/LED fixtures.

Possible Causes
HighThyristor/IGBT bridge partially firing — one or more devices in the bridge degraded, reducing effective conduction angle
HighInput supply voltage below nominal, limiting the maximum current the regulator can develop
MediumCurrent feedback sensor reading high (over-reporting), causing the closed loop to under-drive the output
MediumExcessive series circuit loop resistance/impedance — corroded L-823 connectors, degraded cable, or a partially failed isolating transformer increasing loop losses
MediumOutput transformer tap set incorrectly or transformer partially shorted turns reducing available output
LowerCooling fan/thermal derate active, limiting maximum firing angle to protect the bridge
Required Tools
True-RMS clamp meterInsulation resistance tester (5kV)MultimeterInput power quality analyzerCCR wiring diagramThermal imaging camera
Safety Precautions
  • Treat series circuit terminals as live and potentially at several kV while the CCR is running — do not probe the loop directly; use a clamp meter externally.
  • Apply LOTO before accessing the bridge, transformer taps, or fuses.
  • Use insulated tools when working near the output stage even when isolated, in case of stored capacitor charge.
Diagnostic Procedure
  1. MeasurementClamp-meter the actual output current at each commanded step and compare against the rated value for that step.
  2. MeasurementCheck the incoming 3-phase supply voltage for undervoltage or single-phasing.
  3. ObservationCheck the CCR HMI for any active thermal derate or power-limiting indication.
  4. MeasurementWith the unit isolated, verify the output transformer tap setting against the O&M manual for the installed circuit length/load.
  5. MeasurementMegger the series circuit loop and compare against baseline commissioning values to check for elevated loop resistance.
  6. DecisionLow current with normal input voltage and correct tap → bridge device degradation or feedback sensor drift. Low current with confirmed undervoltage → escalate to upstream supply quality. Elevated loop resistance → circuit-side fault, not a CCR fault.
  7. Fault LocationIsolate to the CCR bridge/feedback loop, the input supply, or the external series circuit.
  8. Root CauseConfirm the specific failed or degraded component through targeted testing.
Test Points
CCR output terminals (clamp meter)
3-phase input supply voltage
Output transformer tap terminals
Current feedback sensor output
Series circuit loop resistance
Root Cause Verification

Confirm output current matches the rated value within tolerance at every intensity step after correction, and that the reading remains stable over a sustained run period.

Corrective Action
  • Replace degraded thyristor/IGBT devices in the bridge.
  • Correct the output transformer tap setting for the actual circuit length.
  • Recalibrate or replace the current feedback sensor.
  • Repair or replace corroded connectors/damaged cable sections in the series circuit.
  • Report and escalate a confirmed upstream undervoltage condition.
Preventive Action
  • Verify transformer tap setting whenever the series circuit length or fixture count changes.
  • Include loop resistance trending in the annual megger test record.
  • Schedule periodic thermal imaging of the bridge to catch device degradation early.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IS 12290, FAA AC 150/5345-10

Diagram: CCR Power Stage Schematic, Series Circuit Single Line Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-023 CCR Output Current Too High

Symptom — CCR output current reads above the value required for the commanded intensity step, with lamps running brighter than expected or premature lamp/LED driver failures occurring on the circuit.

Equipment / System

CCR closed-loop current regulation circuit, output transformer, current feedback sensor.

Possible Causes
HighCurrent feedback sensor under-reporting (drifted low), causing the closed loop to over-drive the bridge to compensate
HighFeedback signal wiring open or intermittent, with the controller defaulting toward maximum firing to seek the setpoint
MediumController regulation loop parameters (gain) incorrectly configured after a firmware update or parameter reset
MediumOutput transformer tap set for a shorter circuit than actually installed, over-driving the loop
LowerBridge firing circuit fault causing an uncontrolled higher conduction angle regardless of feedback
Required Tools
True-RMS clamp meterMultimeterOscilloscopeCCR configuration/parameter toolCCR wiring diagram
Safety Precautions
  • An overcurrent condition can overheat isolating transformers and lamp bases — do not leave the circuit running unattended once overcurrent is confirmed.
  • Apply LOTO before accessing the feedback sensor wiring or transformer taps.
  • Verify zero energy state before disconnecting the current feedback sensor for testing.
Diagnostic Procedure
  1. MeasurementClamp-meter the actual output current at each commanded step and compare against the rated value.
  2. ObservationCheck the CCR HMI displayed current against the independently clamp-metered value — a mismatch points to a feedback sensor fault rather than a true overcurrent.
  3. MeasurementInspect the current feedback sensor wiring for looseness, corrosion, or an open connection.
  4. MeasurementVerify the output transformer tap setting against the documented circuit length.
  5. ObservationReview the controller's regulation loop configuration/parameters against the commissioned baseline.
  6. DecisionHMI and clamp-meter agree and both read high → true overcurrent, check transformer tap and loop configuration. HMI reads normal but clamp-meter reads high → feedback sensor/wiring fault causing the loop to over-correct.
  7. Fault LocationIsolate to the feedback sensor/wiring, the transformer tap setting, or the controller regulation parameters.
  8. Root CauseConfirm the specific cause through sensor substitution or parameter comparison against baseline.
Test Points
CCR output terminals (independent clamp meter)
Current feedback sensor output
Output transformer tap terminals
Controller regulation loop parameters
Root Cause Verification

Confirm the HMI-displayed current and an independent clamp-meter reading agree and both track the rated value at every step, sustained over a full run cycle.

Corrective Action
  • Replace or recalibrate the current feedback sensor.
  • Repair the feedback sensor wiring.
  • Correct the output transformer tap setting.
  • Restore regulation loop parameters to the commissioned baseline.
  • Repair the firing circuit if confirmed as the root cause.
Preventive Action
  • Cross-check HMI current display against an independent clamp-meter reading during routine PM.
  • Lock configuration parameters after commissioning and log any authorized changes.
  • Include feedback sensor calibration in the annual photometric test cycle.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-07 (Controller Parameter Management)

Standards: ICAO Annex 14 Vol I, IS 12290

Diagram: CCR Power Stage Schematic

Case Study: —

Rev 0 — Initial issue
CCR-024 CCR Output Current Unstable

Symptom — Output current reading jumps erratically between values rather than settling on the commanded setpoint, with no clear periodic pattern — distinct from a steady hunting oscillation.

Equipment / System

Current feedback sensor and its signal path, controller ADC input, firing circuit.

Possible Causes
HighLoose or corroded current feedback sensor wiring/terminal introducing an intermittent signal
HighElectrical noise/interference coupling into the feedback signal wiring, e.g. routed alongside power cabling without shielding
MediumPoor or corroded connection at an L-823 connector in the series circuit causing an intermittent high-resistance point
MediumDegraded thyristor/IGBT device with intermittent firing failure on individual half-cycles
LowerController ADC or feedback conditioning circuit fault
Required Tools
OscilloscopeTrue-RMS clamp meter (with data logging if available)Insulation resistance testerContact cleaner and torque screwdriverCCR wiring diagram
Safety Precautions
  • Do not assume an intermittent reading is a display artifact — treat it as a genuine electrical fault until proven otherwise.
  • Apply LOTO before tightening or cleaning any current-carrying terminal.
  • Be alert for arcing/heat discoloration at loose connections, which indicates an active fire risk.
Diagnostic Procedure
  1. ObservationLog the CCR output current over a sustained period (or review controller trend/event log) to characterise the pattern — random spikes versus a steady periodic oscillation (see CCR-035 for hunting).
  2. MeasurementInspect and re-torque the current feedback sensor wiring and terminal block.
  3. MeasurementWith the unit isolated, inspect all series circuit L-823 connectors accessible without excavation for corrosion or looseness.
  4. MeasurementCheck feedback signal cable routing for proximity to power cabling without adequate separation or shielding.
  5. ObservationUse an oscilloscope on the feedback signal to identify noise spikes correlating with the instability.
  6. DecisionInstability correlates with cable routing/noise → shielding/routing fix. Instability traced to a specific loose terminal → mechanical repair. Neither found → suspect a degraded bridge device or controller feedback circuit.
  7. Fault LocationIsolate to the feedback wiring, a series circuit connector, or an internal bridge/controller fault.
  8. Root CauseConfirm the specific cause by reproducing and then eliminating the instability after each corrective step.
Test Points
Current feedback sensor terminal block
Feedback signal cable at controller input
Accessible series circuit L-823 connectors
Controller ADC input signal
Root Cause Verification

Log output current over a minimum 30-minute sustained run after repair and confirm the reading remains within normal tolerance with no unexplained excursions.

Corrective Action
  • Clean, re-terminate, and torque the feedback sensor connection.
  • Repair or reroute the feedback signal cable with proper shielding and separation from power cabling.
  • Repair or replace the affected L-823 connector.
  • Replace the degraded bridge device or controller feedback conditioning circuit.
Preventive Action
  • Include torque-check of feedback wiring terminals in the PM schedule.
  • Verify signal cable segregation from power cabling during any circuit rework.
  • Trend output current data where the controller/ALCMS supports logging, to catch intermittent faults early.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic, Series Circuit Single Line Diagram

Case Study: —

Rev 0 — Initial issue
CCR-025 CCR Output Current Fluctuating

Symptom — Output current shows a slow, repeating rise-and-fall pattern over several seconds to minutes, distinct from rapid random noise — a gradual periodic drift rather than a sharp oscillation.

Equipment / System

Closed-loop current regulation circuit, input supply, cooling/thermal management system.

Possible Causes
HighInput supply voltage fluctuating (e.g. from a generator or a heavily loaded distribution feeder), with the regulation loop tracking the disturbance
MediumThermal cycling of the bridge causing gain drift as component temperature varies with cooling fan cycling
MediumRegulation loop gain set too low, causing sluggish correction that manifests as a slow drift rather than tight regulation
LowerA partially loose series circuit connection heating and cooling under load, changing loop resistance cyclically
Required Tools
Power quality analyzerTrue-RMS clamp meter with data loggingThermal imaging cameraCCR configuration toolCCR wiring diagram
Safety Precautions
  • Apply LOTO before any internal inspection.
  • If a cyclically heating connection is suspected, treat it as a potential fire risk and inspect promptly rather than deferring to the next scheduled PM.
Diagnostic Procedure
  1. MeasurementLog input supply voltage over the same period as the observed output fluctuation to check for correlation.
  2. ObservationCheck whether the fluctuation period correlates with cooling fan on/off cycling.
  3. MeasurementThermal-image the bridge and series circuit connectors during a sustained run to identify any point with cyclical heating.
  4. ObservationReview the controller's regulation loop gain setting against the commissioned baseline.
  5. DecisionFluctuation correlates with input supply → upstream power quality issue, not a CCR fault. Fluctuation correlates with fan cycling/thermal drift → bridge thermal stability issue. A hot spot found on a connector → mechanical/connection fault.
  6. Fault LocationIsolate to the upstream supply, the bridge thermal behaviour, the regulation loop tuning, or a specific series circuit connection.
  7. Root CauseConfirm the specific cause by eliminating each candidate through targeted correction and retest.
Test Points
Input supply voltage (logged)
Bridge heatsink temperature
Series circuit connector temperature (thermal image)
Regulation loop gain parameter
Root Cause Verification

Log output current over a sustained run after correction and confirm the fluctuation amplitude is within normal tolerance with no correlation to fan cycling or supply variation.

Corrective Action
  • Report and address the upstream supply quality issue where confirmed.
  • Improve bridge cooling/ventilation to reduce thermal-driven gain drift.
  • Re-tune the regulation loop gain per manufacturer guidance.
  • Repair the cyclically heating series circuit connection.
Preventive Action
  • Include a power quality check in commissioning and periodic audits for sites on generator or weak feeders.
  • Trend bridge temperature alongside output current where data logging is available.
  • Include thermal imaging of series circuit connectors in the annual PM.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-07 (Controller Parameter Management)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: —

Rev 0 — Initial issue
CCR-026 CCR Output Current Not Matching Selected Step

Symptom — The commanded intensity step (local, remote, or ALCMS-selected) does not correspond to the actual measured output current — e.g. Step 3 commanded but Step 5 current delivered, or the step changes but current does not follow.

Equipment / System

Controller intensity-step logic, step-selection input (local switch, remote/ALCMS command), step reference table/configuration.

Possible Causes
HighStep reference table/configuration incorrectly programmed — commanded step mapped to the wrong current setpoint
HighLocal/remote selector switch in the wrong position, or local override active without operator awareness
MediumCommand signal from ALCMS/PLC to the CCR corrupted or mismatched (e.g. wrong step code on a serial/analog interface)
MediumController stuck on a previous step due to a communication or logic fault, not updating on new commands
LowerStep relay/contactor (on non-digital step-relay-type CCRs) failed to switch to the commanded tap
Required Tools
MultimeterCCR configuration/parameter toolProtocol analyzer or serial monitor (for ALCMS link)CCR wiring diagramTrue-RMS clamp meter
Safety Precautions
  • Confirm actual delivered current independently with a clamp meter before relying on the HMI display, since the fault may be a display/logic mismatch rather than a true output fault.
  • Apply LOTO before accessing step relay contacts on step-relay-type CCRs.
Diagnostic Procedure
  1. ObservationConfirm the exact command issued (local switch position, or the specific step code sent by ALCMS/PLC) and compare it to what the CCR HMI displays as the received command.
  2. MeasurementClamp-meter the actual output current and compare it against both the commanded step and the step the HMI claims to be running.
  3. ObservationCheck the local/remote selector switch position and any local override status.
  4. MeasurementVerify the step reference table/configuration in the controller against the design intensity schedule.
  5. ObservationIf ALCMS-commanded, monitor the communication link for the actual step code being transmitted and received.
  6. DecisionHMI-received command matches operator intent but output current doesn't match → step table misconfiguration or step relay fault. HMI-received command differs from what was sent → communication/wiring fault on the command path.
  7. Fault LocationIsolate to the step configuration table, the local/remote selection path, the ALCMS communication link, or a step relay.
  8. Root CauseConfirm the specific misconfiguration or failed component.
Test Points
Local/remote selector switch
ALCMS/PLC command signal at CCR input
Controller step reference table
Step relay contacts (if applicable)
CCR output terminals (clamp meter)
Root Cause Verification

Command each intensity step in turn from the intended control source and confirm the clamp-metered output current matches the design value for that step every time.

Corrective Action
  • Correct the step reference table/configuration.
  • Correct the local/remote selector position and clarify override procedures with operations staff.
  • Repair the ALCMS/PLC communication wiring or resolve the protocol mismatch.
  • Replace the failed step relay/contactor.
Preventive Action
  • Verify the step reference table against the design intensity schedule at every commissioning and after any firmware update.
  • Include an end-to-end step command verification (ALCMS to measured output) in periodic PM.
  • Label and periodically audit local/remote selector switch positions.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-08 (Intensity Step Commissioning)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, ALCMS Interface Diagram

Case Study: —

Rev 0 — Initial issue
CCR-027 CCR Output Voltage Abnormally High

Symptom — Output (series circuit loop) voltage reads significantly above the expected value for the connected load and commanded step, with no corresponding increase in current — the regulator is working harder than the circuit should require.

Equipment / System

CCR output transformer, series circuit loop and isolating transformers, insulation condition of the loop.

Possible Causes
HighElevated series circuit loop impedance — degraded cable insulation-to-earth is not the driver here, but increased conductor/joint resistance or a partially open isolating transformer primary increases the voltage the CCR must develop to maintain rated current
HighOne or more isolating transformers open-circuited (primary winding failed), forcing the CCR to raise voltage trying to maintain current through the remaining loop resistance
MediumOutput transformer tap set for a longer circuit than actually connected
LowerVoltage sensing/feedback circuit fault causing a false high reading rather than a true condition
Required Tools
High-voltage-rated multimeter/meggerInsulation resistance tester (5kV)True-RMS clamp meterCCR wiring diagramSeries circuit as-built drawing
Safety Precautions
  • An abnormally high loop voltage significantly increases shock and flashover risk at every isolating transformer and connector along the circuit — treat the entire loop as elevated-hazard until the cause is resolved.
  • Apply LOTO on the CCR before any loop testing.
  • Do not attempt to trace an open isolating transformer by working on live fixtures.
Diagnostic Procedure
  1. ObservationConfirm the CCR is delivering rated current at the commanded step despite the high voltage reading — this indicates the loop, not the CCR, is the primary driver.
  2. MeasurementWith the CCR isolated, megger the series circuit loop insulation and measure loop resistance, comparing against baseline commissioning values.
  3. MeasurementSystematically segment-test the loop (if pull boxes/junctions allow) to localise a section with abnormally high resistance.
  4. ObservationVerify the output transformer tap setting against the actual documented circuit length.
  5. DecisionLoop resistance significantly above baseline → open or degraded isolating transformer/connector somewhere in the loop, proceed to segment isolation. Loop resistance normal but voltage still reads high → feedback/sensing circuit fault or transformer tap mismatch.
  6. Fault LocationIsolate to a specific loop segment, a specific isolating transformer, or the CCR's own voltage sensing/tap configuration.
  7. Root CauseConfirm the specific failed isolating transformer or connector by direct inspection once the segment is localised.
Test Points
Series circuit loop insulation resistance
Series circuit loop resistance (segment by segment)
Output transformer tap terminals
CCR output voltage sensing circuit
Root Cause Verification

After repair, confirm output voltage returns to the expected range for rated current at each step, and re-megger the loop to confirm insulation and resistance are within baseline.

Corrective Action
  • Replace the failed isolating transformer identified during segment testing.
  • Repair or replace the degraded cable section or L-823 connector.
  • Correct the output transformer tap setting.
  • Repair the voltage sensing circuit if confirmed faulty.
Preventive Action
  • Maintain a baseline loop resistance and insulation record from commissioning for future comparison.
  • Include periodic segment-wise loop testing in the PM programme for long circuits.
  • Track isolating transformer replacement history to identify circuits prone to repeat failures.
Related References

SOP: SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IS 12290, IS 7785

Diagram: Series Circuit Single Line Diagram, Isolating Transformer Layout

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-028 CCR Output Voltage Abnormally Low

Symptom — Output (series circuit loop) voltage reads well below the expected value for the connected load and commanded step, while current remains close to normal.

Equipment / System

CCR output transformer, series circuit loop, voltage sensing/feedback circuit.

Possible Causes
HighOutput transformer tap set for a much shorter circuit than actually connected, understating available voltage headroom
MediumA section of the series circuit has been shortened or bypassed (e.g. temporary jumper left in place after fixture removal) reducing loop impedance and therefore required voltage
MediumVoltage sensing/feedback circuit fault causing a false low reading
LowerPartial short or reduced insulation resistance to earth on the loop, reducing the effective circuit impedance the CCR sees
Required Tools
Insulation resistance tester (5kV)True-RMS clamp meterMultimeterSeries circuit as-built drawingCCR wiring diagram
Safety Precautions
  • A low measured voltage with normal current can mask a partial insulation fault or an unauthorised bypass — do not assume it is benign.
  • Apply LOTO before loop testing.
Diagnostic Procedure
  1. ObservationConfirm output current is at or near the rated value for the commanded step — if current is also low, redirect to CCR-022.
  2. MeasurementVerify the output transformer tap setting against the documented, as-built circuit length and fixture count.
  3. ObservationCheck as-built records against current field configuration for any fixtures added or removed, or temporary jumpers installed.
  4. MeasurementMegger the loop insulation resistance to earth and compare against baseline.
  5. DecisionTap mismatch found → correct tap. As-built discrepancy found → investigate and formalise or remove the unauthorised change. Reduced insulation resistance found → escalate as a developing insulation fault even though current appears normal.
  6. Fault LocationIsolate to the transformer tap setting, an unrecorded circuit modification, or a developing insulation fault.
  7. Root CauseConfirm the specific cause through physical circuit verification against as-built records.
Test Points
Output transformer tap terminals
Series circuit loop insulation resistance
Voltage sensing/feedback circuit
Root Cause Verification

After correction, confirm output voltage is consistent with the documented circuit length at rated current, and update as-built records if a physical change is confirmed as the cause.

Corrective Action
  • Correct the output transformer tap setting.
  • Remove unauthorised jumpers/bypasses and restore the circuit to its designed configuration, or formally update records if the change is intentional.
  • Repair the voltage sensing circuit if confirmed faulty.
  • Investigate and repair any confirmed reduction in insulation resistance.
Preventive Action
  • Enforce as-built record updates for any series circuit modification.
  • Include tap setting verification whenever fixture counts change.
  • Trend loop insulation resistance over successive PM cycles to catch gradual degradation.
Related References

SOP: SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IS 7785

Diagram: Series Circuit Single Line Diagram

Case Study: —

Rev 0 — Initial issue
CCR-029 CCR Output Voltage Unstable

Symptom — Output voltage reading swings noticeably while current remains comparatively steady — the regulation loop is not settling on a stable voltage operating point even though current control appears to be holding.

Equipment / System

Voltage sensing/feedback circuit, series circuit loop connections, regulation loop control logic.

Possible Causes
HighIntermittent high-resistance connection somewhere in the series circuit loop, with contact resistance varying as the connection heats and cools
MediumVoltage sensing circuit wiring loose or subject to electrical noise
MediumRegulation loop attempting to maintain constant current against a marginal/borderline loop impedance near the transformer's tap limit, causing voltage to hunt around the ceiling
LowerPartial intermittent insulation fault to earth on the loop
Required Tools
OscilloscopeTrue-RMS clamp meter with loggingInsulation resistance testerThermal imaging cameraCCR wiring diagram
Safety Precautions
  • Treat an intermittent high-resistance connection as a fire and flashover risk — do not defer investigation.
  • Apply LOTO before loop inspection.
Diagnostic Procedure
  1. MeasurementLog output voltage and current together over a sustained period to confirm current is stable while voltage varies.
  2. MeasurementThermal-image accessible series circuit connectors during a sustained run to identify a cyclically heating joint.
  3. MeasurementInspect and re-torque the voltage sensing circuit wiring at the controller.
  4. ObservationCompare the operating voltage against the transformer tap's rated ceiling to check whether the loop is near the tap limit.
  5. DecisionA hot, cyclically-varying connector found → intermittent connection fault. Voltage instability with no thermal anomaly and near the tap ceiling → tap undersized for the actual loop impedance, consider re-tapping. Neither found → sensing circuit fault.
  6. Fault LocationIsolate to a specific series circuit connection, the transformer tap margin, or the voltage sensing circuit.
  7. Root CauseConfirm the specific cause by physical repair and retest.
Test Points
Series circuit connectors (thermal imaging)
Voltage sensing circuit wiring at controller
Output transformer tap setting versus loop impedance
Root Cause Verification

Log output voltage and current over a sustained run after repair and confirm both remain stable within normal tolerance.

Corrective Action
  • Repair the intermittent high-resistance connection.
  • Re-terminate and secure the voltage sensing circuit wiring.
  • Re-tap the output transformer to provide adequate voltage margin for the loop impedance.
  • Repair any confirmed intermittent insulation fault.
Preventive Action
  • Include thermal imaging of series circuit connectors in the annual PM.
  • Verify tap margin against loop impedance whenever the circuit configuration changes.
  • Torque-check sensing circuit terminals during scheduled maintenance.
Related References

SOP: SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IS 7785

Diagram: Series Circuit Single Line Diagram

Case Study: —

Rev 0 — Initial issue
CCR-030 CCR No Output Despite Healthy Input

Symptom — Input supply and internal control power are confirmed healthy, and the CCR appears to accept the start/run command, but no output current is delivered and no fault alarm is raised — the unit appears to be running normally on the HMI while producing nothing.

Equipment / System

CCR controller run-logic and firing enable path, output contactor (where fitted between the bridge and the output transformer), bridge firing circuit.

Possible Causes
HighOutput enable contactor/relay (separate from the main input contactor) not energizing, physically disconnecting the bridge from the output transformer despite the controller believing it is running
HighController run-state logic satisfied internally but the firing enable signal to the bridge gate driver not actually asserted — a software/logic fault
MediumA latched soft-alarm that is suppressing firing internally without surfacing as a visible fault code (e.g. a self-test failure not mapped to a display message)
MediumOutput contactor auxiliary contact feedback mismatch — controller reads a false 'closed' status from a stuck-open auxiliary contact
LowerFirmware fault causing the run state and the firing subroutine to become desynchronised
Required Tools
MultimeterTrue-RMS clamp meterOscilloscopeCCR event/alarm log toolCCR wiring diagram
Safety Precautions
  • Confirm zero energy at the output stage with a proven meter before assuming the unit is safe to touch, even though it is 'not producing output' — a partially engaged contactor can still present a hazard.
  • Apply LOTO before internal inspection.
Diagnostic Procedure
  1. ObservationConfirm input supply, control power, and run-state indication are all genuinely healthy (cross-check with independent meters, not just the HMI).
  2. ObservationPull the full controller event/alarm log, including suppressed or low-priority events, not just the currently displayed status.
  3. MeasurementCheck the output enable contactor/relay coil voltage and its mechanical state directly.
  4. MeasurementVerify the auxiliary contact feedback from the output contactor against its actual physical position.
  5. MeasurementUsing an oscilloscope, confirm whether a firing enable signal is actually present at the gate driver during the run state.
  6. DecisionOutput contactor not energizing despite a valid command → contactor/coil/wiring fault. Contactor confirmed closed but no firing enable signal present → controller logic/firmware fault. Auxiliary contact mismatch found → feedback wiring fault masking the true contactor position.
  7. Fault LocationIsolate to the output contactor circuit, the firing enable logic, or the auxiliary feedback wiring.
  8. Root CauseConfirm the specific fault by direct measurement at each stage of the run/firing chain.
Test Points
Output enable contactor coil terminals
Output contactor auxiliary contact
Firing enable signal at gate driver
Controller full event/alarm log
Root Cause Verification

After repair, confirm output current is delivered immediately on a run command and that the auxiliary contact feedback matches the true physical contactor state across several start/stop cycles.

Corrective Action
  • Repair or replace the failed output contactor/relay.
  • Correct the auxiliary contact wiring or replace the failed contact.
  • Reflash/reset controller firmware if a logic desynchronisation is confirmed.
  • Escalate to the manufacturer for a suppressed self-test fault not visible on the standard display.
Preventive Action
  • Include a full output verification (not just run-state confirmation) as a mandatory step after every start-up in the PM checklist.
  • Periodically review the complete event/alarm log, not only currently active alarms, during PM.
  • Keep firmware documentation and revision history for each controller.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-031 CCR Output Present but Lights Not Operating

Symptom — CCR confirms it is delivering rated current at the output terminals, but some or all fixtures on the series circuit are not illuminated.

Equipment / System

Series circuit isolating transformers, lamp/LED fixtures and their internal drivers, secondary circuit wiring within each fixture.

Possible Causes
HighOne or more isolating transformer secondaries open-circuited or the fixture's internal wiring/lamp base connection failed
HighLamp filament failed (incandescent fixtures) or LED driver failed (LED fixtures) at the affected location(s)
MediumIsolating transformer primary-to-secondary insulation failure causing the transformer to pass current in the loop without delivering usable secondary voltage
MediumPhotometric/optical issue mistaken for an electrical fault — lens heavily contaminated or physically obstructed
LowerFixture-level surge protection device failed in a mode that opens the secondary circuit
Required Tools
True-RMS clamp meterInsulation resistance tester (5kV)MultimeterFixture-specific test set/lamp testerTorque screwdriver set
Safety Precautions
  • Do not open or work on isolating transformers or fixtures while the CCR is running — isolate the CCR and apply LOTO first, since the series loop can induce hazardous secondary voltage.
  • Follow airside work permit and NOTAM procedures before accessing runway/taxiway fixtures.
Diagnostic Procedure
  1. ObservationIdentify exactly which fixture(s) on the circuit are affected — a single fixture points to a local fault, multiple scattered fixtures suggest a batch lamp/driver failure, and a contiguous group suggests a shared cable/transformer issue.
  2. MeasurementWith the CCR isolated, check the affected isolating transformer's secondary output using an appropriate low-voltage test method or fixture tester.
  3. MeasurementCheck the isolating transformer primary-to-secondary insulation resistance.
  4. ObservationInspect the fixture for lamp/LED driver condition, secondary wiring integrity, and lens contamination.
  5. DecisionTransformer secondary confirmed dead with healthy primary loop current → transformer or secondary wiring fault. Transformer secondary healthy but fixture still dark → lamp/LED driver failure at the fixture. Lens heavily contaminated → not an electrical fault, redirect to cleaning/maintenance.
  6. Fault LocationIsolate to the isolating transformer, the fixture wiring, or the lamp/LED driver.
  7. Root CauseConfirm the specific failed component by direct replacement/substitution testing.
Test Points
Isolating transformer secondary output
Isolating transformer primary-to-secondary insulation
Fixture lamp base/driver input terminals
Root Cause Verification

After replacement, re-energize the circuit and visually confirm the repaired fixture(s) illuminate correctly at each commanded intensity step alongside the rest of the circuit.

Corrective Action
  • Replace the failed lamp or LED driver.
  • Replace the failed isolating transformer.
  • Repair the fixture secondary wiring or connector.
  • Clean the fixture lens if contamination was the actual cause of perceived non-operation.
Preventive Action
  • Track lamp/LED driver and isolating transformer replacement history per fixture to identify recurring failure points.
  • Include lens cleaning in the routine airfield lighting maintenance schedule.
  • Batch-test isolating transformers periodically rather than only on failure.
Related References

SOP: SOP-AGL-03 (Fixture Isolation Transformer Testing), SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IS 7785

Diagram: Series Circuit Single Line Diagram, Fixture Wiring Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-032 CCR Output Present but Circuit Current Abnormal

Symptom — CCR confirms it is producing an output at the commanded step, but the current actually flowing in the series circuit loop (measured with an independent clamp meter at a point downstream of the CCR) does not match the CCR's own displayed/regulated value.

Equipment / System

CCR current feedback sensor location relative to the actual load path, series circuit loop.

Possible Causes
HighA parallel leakage path to earth on the loop is diverting a portion of the current before it reaches the CCR's feedback sensor location, if the sensor is positioned such that this is possible
HighCurrent feedback sensor sensing a different point in the circuit than the actual load path due to an internal wiring or CT-orientation fault
MediumA partial short between the series circuit loop and an adjacent circuit or structure, providing an unintended alternate current path
LowerInstrument/clamp meter measurement error — miscounted turns through the clamp, wrong meter range, or interference
Required Tools
True-RMS clamp meter (verify against a second reference meter)Insulation resistance tester (5kV)MultimeterCCR wiring diagramSeries circuit as-built drawing
Safety Precautions
  • A leakage or partial short to earth is a serious safety hazard — treat this as high priority and do not leave the circuit energized pending investigation once confirmed.
  • Apply LOTO before any loop segment testing.
Diagnostic Procedure
  1. MeasurementRe-verify the discrepancy using a second, calibrated clamp meter at the same measurement point to rule out an instrument error.
  2. MeasurementWith the CCR isolated, megger the full loop insulation resistance to earth and to any adjacent circuits.
  3. MeasurementIf insulation resistance is low, segment-test the loop to localise the leakage/short.
  4. ObservationVerify the current feedback sensor's physical installation and CT orientation against the wiring diagram.
  5. DecisionDiscrepancy confirmed with a second meter and low insulation resistance found → genuine leakage/short fault, proceed to segment isolation. Discrepancy not reproducible with a second meter → original measurement error. Insulation resistance normal but discrepancy persists → feedback sensor installation/wiring fault.
  6. Fault LocationIsolate to a specific loop segment with a confirmed leakage/short, or to the CCR's own feedback sensor installation.
  7. Root CauseConfirm the specific cable, connector, or transformer responsible for the leakage path.
Test Points
Series circuit loop insulation resistance to earth
Series circuit loop insulation resistance to adjacent circuits
Current feedback sensor installation/orientation
Root Cause Verification

After repair, confirm the CCR's regulated current and an independent downstream clamp-meter reading agree, and re-megger the loop to confirm insulation resistance is within baseline.

Corrective Action
  • Repair or replace the cable/connector/transformer responsible for the leakage or short path.
  • Correct the current feedback sensor installation/orientation.
  • Recalibrate or replace the field clamp meter if an instrument error was confirmed.
Preventive Action
  • Maintain a baseline insulation resistance record and re-test after any circuit disturbance.
  • Cross-check CCR displayed current against an independent clamp meter during routine PM as standard practice.
  • Verify feedback sensor installation whenever the controller or sensor is replaced.
Related References

SOP: SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IS 7785

Diagram: Series Circuit Single Line Diagram

Case Study: —

Rev 0 — Initial issue
CCR-033 CCR Output Drops Under Load

Symptom — Output current is correct immediately after start-up or at light load, but sags below the commanded value once the full series circuit load (all fixtures) is drawing current, or after the circuit has been running for some time.

Equipment / System

CCR power stage thermal capacity, output transformer, bridge current rating margin.

Possible Causes
HighBridge thermal derate/foldback engaging as internal temperature rises under sustained full load, due to a cooling fault or undersized cooling for the actual ambient conditions
HighOutput transformer thermally derating or saturating under sustained full load due to a cooling or sizing issue
MediumMarginal supply voltage that sags further under the CCR's own full-load input current draw, reducing available headroom for the regulator
MediumA loose high-current connection within the CCR (bus bar, output terminal) heating and increasing resistance under load, which the regulator cannot fully compensate for once it reaches its voltage ceiling
LowerRegulation loop response too slow to correctly track the load transition from light to full
Required Tools
Thermal imaging cameraTrue-RMS clamp meter with loggingPower quality analyzerTorque screwdriver setCCR wiring diagram
Safety Precautions
  • Do not touch internal bus bars or terminals to check for heat by hand — use a thermal imaging camera or a non-contact method with the unit running, or isolate first.
  • Apply LOTO before tightening any internal high-current connection.
Diagnostic Procedure
  1. MeasurementLog output current from start-up through to full sustained load to characterise the drop's timing and magnitude.
  2. MeasurementThermal-image the bridge heatsink and output transformer during the load period when the drop occurs.
  3. ObservationCheck cooling fan operation and airflow/filter condition.
  4. MeasurementLog input supply voltage through the same period to check for supply sag correlating with the CCR's own load.
  5. MeasurementWith the unit isolated, torque-check internal high-current bus bar and terminal connections.
  6. DecisionThermal derate confirmed via imaging correlating with the drop → cooling deficiency, address ventilation/fan first. Loose internal connection found hot under load → mechanical repair. Supply sag confirmed independent of CCR load → upstream supply issue.
  7. Fault LocationIsolate to the CCR's internal thermal management, a loose internal connection, or the upstream supply.
  8. Root CauseConfirm the specific cause and verify the drop no longer occurs once corrected.
Test Points
Bridge heatsink temperature under sustained load
Output transformer temperature under sustained load
Internal high-current bus bar/terminal connections
Input supply voltage under CCR full load
Root Cause Verification

Run the CCR at full commanded step for a minimum of one hour and confirm output current remains stable within tolerance throughout, with no thermal derate triggered.

Corrective Action
  • Clean/repair the cooling fan and ventilation path, or upgrade cooling if undersized for site ambient conditions.
  • Re-torque or replace the loose internal high-current connection.
  • Report and address the upstream supply sag.
  • Adjust regulation loop response tuning if a slow tracking response is confirmed as contributory.
Preventive Action
  • Include a sustained full-load thermal check in the annual PM, not just a spot-check at start-up.
  • Keep cooling fans and filters on a defined cleaning/replacement schedule.
  • Torque-check internal high-current connections at each major PM.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-09 (Cooling System Maintenance)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-034 CCR Output Rises Without Load

Symptom — Output voltage climbs toward the transformer's maximum limit and/or an open-circuit alarm threatens to trip when the series circuit load is reduced or removed (e.g. during isolation testing), even though the commanded current step has not changed.

Equipment / System

Closed-loop constant-current regulation behaviour, output transformer voltage limit/protection.

Possible Causes
HighExpected constant-current behaviour — as load (loop impedance) decreases, a true constant-current source naturally increases voltage to maintain current; this is normal operation being misread as a fault, unless the rise is uncontrolled
HighOne or more fixtures/transformers genuinely disconnected from the loop (e.g. during maintenance) without first reducing the CCR to a lower step or isolating it, causing the regulator to chase full open-circuit voltage
MediumOpen-circuit/no-load protection threshold set incorrectly, tripping prematurely on a load reduction that should be within normal tolerance
LowerVoltage limit protection circuit fault failing to cap the rise at the designed ceiling
Required Tools
True-RMS clamp meterInsulation resistance tester (5kV)CCR configuration toolCCR wiring diagram
Safety Precautions
  • Never reduce or remove series circuit load without first reducing the CCR to a low step or isolating it — an unloaded constant-current regulator will attempt to develop full open-circuit voltage, which is a serious shock/flashover hazard.
  • Apply LOTO before working on any part of the loop, including for planned load reduction during maintenance.
Diagnostic Procedure
  1. ObservationConfirm whether the load reduction was planned (e.g. maintenance disconnecting fixtures) or unplanned, and whether the CCR was correctly stepped down or isolated beforehand per procedure.
  2. MeasurementIf the rise is unplanned, verify actual loop continuity to identify which section is now open-circuit or under-loaded, per CCR-027/030 procedures as applicable.
  3. ObservationReview the open-circuit/no-load protection threshold configuration against the manufacturer's recommended setting.
  4. DecisionRise correlates with a known, planned load change and stays within the transformer's designed ceiling → normal constant-current behaviour, procedural reminder only. Rise is unplanned or protection fails to limit it → genuine protection or loop fault requiring correction.
  5. Fault LocationIsolate to a procedural gap (load changed without stepping down the CCR), a genuine loop disconnection, or a protection threshold/circuit fault.
  6. Root CauseConfirm whether the event was a procedural violation or an equipment fault.
Test Points
Series circuit loop continuity
Open-circuit/no-load protection threshold setting
Output voltage limit circuit
Root Cause Verification

Confirm the open-circuit/no-load protection reliably trips within its designed threshold and time when the loop is genuinely opened during a controlled test, and that operations staff correctly step down the CCR before any planned disconnection.

Corrective Action
  • Reinforce the procedure requiring the CCR to be stepped down or isolated before any planned load disconnection.
  • Correct the open-circuit/no-load protection threshold configuration.
  • Repair the voltage limit protection circuit if confirmed faulty.
  • Restore the loop continuity if an unplanned disconnection is found.
Preventive Action
  • Include a mandatory 'step down before disconnect' step in every maintenance work instruction touching the series circuit.
  • Verify open-circuit protection function as part of the annual protection test (see Division 04).
  • Brief operations and maintenance staff on constant-current source behaviour during induction/refresher training.
Related References

SOP: SOP-CCR-04 (CCR Isolation & LOTO Procedure), SOP-CCR-06 (Series Circuit Loop Testing)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: —

Rev 0 — Initial issue
CCR-035 CCR Output Hunting

Symptom — Output current oscillates in a regular, repeating pattern around the setpoint — rising and falling in a consistent cycle rather than settling, often visible as a rhythmic flicker in lamp brightness.

Equipment / System

Closed-loop current regulation control algorithm — proportional/integral/derivative (PID) or equivalent gain settings, feedback sensor response time.

Possible Causes
HighRegulation loop gain (proportional/integral) set too high for the actual loop dynamics, causing the control loop to overcorrect each cycle
HighFeedback sensor or signal path introducing a delay or lag that the control loop's tuning does not account for
MediumLoop tuning parameters left at generic factory defaults rather than tuned for the specific installed circuit length/impedance
MediumA firmware update changed default control parameters without re-verification against the site's circuit characteristics
LowerMechanical/relay-based step switching (on step-relay-type CCRs) chattering due to a marginal relay/contactor
Required Tools
OscilloscopeTrue-RMS clamp meter with loggingCCR configuration/parameter toolCCR wiring diagram
Safety Precautions
  • Sustained hunting can cause repeated thermal cycling stress on the bridge and output transformer — do not leave a hunting condition unaddressed for extended periods.
  • Apply LOTO before any internal parameter or wiring changes; parameter changes via the configuration tool can typically be made with the unit running under supervision per manufacturer procedure.
Diagnostic Procedure
  1. MeasurementLog/oscilloscope the output current to characterise the hunting period and amplitude precisely.
  2. ObservationReview the current regulation loop gain (P/I/D or equivalent) settings against the manufacturer's recommended range and the commissioned baseline.
  3. MeasurementCheck the feedback sensor signal for excessive lag or filtering delay relative to actual current changes.
  4. ObservationIf step-relay-type, inspect the step relay/contactor for chatter or marginal pull-in during a step-hold condition.
  5. DecisionGain settings found outside the recommended range or altered from baseline → re-tune. Feedback lag confirmed as the dominant factor → address sensor/signal path first before re-tuning gain. Relay chatter confirmed → mechanical relay fault, not a control loop issue.
  6. Fault LocationIsolate to the control loop gain tuning, the feedback sensor response, or a step relay.
  7. Root CauseConfirm the specific tuning or component correction that eliminates the oscillation.
Test Points
Output current waveform (oscilloscope/logger)
Regulation loop gain parameters
Feedback sensor signal timing
Step relay/contactor condition
Root Cause Verification

After adjustment, run the CCR at each intensity step for a minimum of 15 minutes and confirm output current settles within normal tolerance with no repeating oscillation.

Corrective Action
  • Re-tune the regulation loop gain per manufacturer guidance for the actual installed circuit characteristics.
  • Correct or replace the feedback sensor/signal path causing excessive lag.
  • Replace the marginal step relay/contactor.
  • Revert to previously verified firmware/parameter settings if a recent update introduced the issue.
Preventive Action
  • Document and preserve the tuned regulation loop parameters at commissioning as the site baseline.
  • Re-verify loop tuning after any firmware update or controller replacement.
  • Include a hunting check (visual and measured) as a standard PM test.
Related References

SOP: SOP-CCR-07 (Controller Parameter Management), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-036 CCR Current Overshoot

Symptom — On a step change (start-up or intensity step increase), output current briefly spikes above the new commanded setpoint before settling — a transient excursion rather than a sustained overcurrent (see CCR-023 for sustained high current).

Equipment / System

Closed-loop regulation transient response, step-change ramp/soft-start logic.

Possible Causes
HighRegulation loop gain tuned too aggressively for a fast transient response, trading overshoot for speed
MediumStep-change ramp/soft-start function disabled or configured with too short a ramp time
MediumFeedback sensor response lag causing the loop to overdrive briefly before the true current value is registered
LowerLoad impedance changing abruptly at the step transition (e.g. a large fixture count) exceeding the loop's designed transient handling range
Required Tools
OscilloscopeTrue-RMS clamp meter with logging (fast sample rate)CCR configuration toolCCR wiring diagram
Safety Precautions
  • Repeated current overshoot stresses lamp filaments and LED driver components — do not dismiss as cosmetic if it is causing premature fixture failures.
  • Apply LOTO before any wiring-level intervention; parameter/ramp adjustments are typically made via the configuration tool under manufacturer procedure.
Diagnostic Procedure
  1. MeasurementCapture the output current transient on an oscilloscope or fast-sampling logger during a deliberate step change, measuring overshoot magnitude and duration.
  2. ObservationCheck whether a step-change ramp/soft-start function exists on this controller model and whether it is enabled and correctly configured.
  3. ObservationReview regulation loop gain settings against the manufacturer's recommended range.
  4. DecisionRamp function disabled or too aggressive → enable/lengthen the ramp first, as the simplest correction. Ramp already correctly configured but overshoot persists → loop gain re-tuning required.
  5. Fault LocationIsolate to the step-change ramp configuration or the underlying regulation loop gain tuning.
  6. Root CauseConfirm the specific parameter correction that brings overshoot within acceptable limits.
Test Points
Output current transient waveform at step change
Step-change ramp/soft-start configuration
Regulation loop gain parameters
Root Cause Verification

Repeat a deliberate step change after adjustment and confirm the overshoot magnitude is within the manufacturer's specified tolerance and settles promptly.

Corrective Action
  • Enable or lengthen the step-change ramp/soft-start function.
  • Re-tune the regulation loop gain to reduce transient overshoot within an acceptable settling time.
  • Address feedback sensor lag if confirmed as a contributing factor.
Preventive Action
  • Verify step-change ramp configuration at commissioning and after any parameter reset.
  • Include a step-change transient check in periodic PM for circuits with a history of premature fixture failure.
  • Document the tuned transient response parameters as part of the site baseline.
Related References

SOP: SOP-CCR-07 (Controller Parameter Management)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-037 CCR Current Undershoot

Symptom — On a step change, output current briefly dips below the new commanded setpoint before settling, or momentarily drops noticeably below setpoint after a step decrease — a transient dip rather than a sustained low current (see CCR-022 for sustained low current).

Equipment / System

Closed-loop regulation transient response, step-change ramp/soft-start logic.

Possible Causes
HighRegulation loop response too slow (excessively conservative gain/ramp) causing a lag before the loop catches up to the new setpoint
MediumFeedback sensor or signal filtering introducing excessive smoothing/delay
MediumStep-change ramp/soft-start function configured with too long a ramp time for the operational requirement, perceived as an undershoot/slow response by pilots or ATC
LowerBridge thermal foldback momentarily engaging at the step transition, briefly limiting available current
Required Tools
OscilloscopeTrue-RMS clamp meter with logging (fast sample rate)CCR configuration toolCCR wiring diagram
Safety Precautions
  • A significant, operationally noticeable dip in runway/approach lighting intensity during a step change can affect pilot visual reference during critical phases — treat reports of a perceptible dip as an operational priority, not just a technical curiosity.
  • Apply LOTO before any wiring-level intervention.
Diagnostic Procedure
  1. MeasurementCapture the output current transient on an oscilloscope or fast-sampling logger during a deliberate step change, measuring undershoot magnitude and duration.
  2. ObservationReview the step-change ramp/soft-start configuration — an overly long ramp on a step decrease can present as a slow, undershoot-like response.
  3. ObservationReview regulation loop gain settings against the manufacturer's recommended range for responsiveness.
  4. DecisionRamp configured too long for the operational need → shorten within manufacturer limits. Ramp already appropriate but undershoot persists → loop gain or feedback lag issue requiring further tuning.
  5. Fault LocationIsolate to the step-change ramp configuration or the underlying regulation loop response tuning.
  6. Root CauseConfirm the specific parameter correction that brings the transient response within acceptable limits.
Test Points
Output current transient waveform at step change
Step-change ramp/soft-start configuration
Regulation loop gain parameters
Root Cause Verification

Repeat a deliberate step change after adjustment and confirm the undershoot magnitude and settling time are within the manufacturer's specified tolerance.

Corrective Action
  • Shorten the step-change ramp time within manufacturer-permitted limits.
  • Re-tune the regulation loop gain for a faster, still-stable transient response.
  • Address feedback sensor filtering/lag if confirmed as a contributing factor.
Preventive Action
  • Balance ramp/soft-start settings against operational responsiveness requirements at commissioning, not just equipment protection.
  • Include a step-change transient check in periodic PM.
  • Document the tuned transient response parameters as part of the site baseline.
Related References

SOP: SOP-CCR-07 (Controller Parameter Management)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-038 CCR Current Regulation Failure

Symptom — The CCR no longer maintains a constant current regardless of load or supply variation — output current tracks changes in loop impedance or input voltage directly, as if the unit were operating open-loop rather than closed-loop.

Equipment / System

Complete closed-loop current regulation chain — feedback sensor, controller control algorithm, and firing circuit acting on that feedback.

Possible Causes
HighCurrent feedback signal path completely broken (sensor failed open or wiring severed), with the controller unable to close the loop and defaulting to a fixed or uncontrolled firing angle
HighController regulation algorithm fault/crash — the control task is not executing even though the unit otherwise appears to be running
MediumFeedback sensor calibration grossly out of range, effectively removing meaningful control authority even though a signal is present
LowerA configuration error has placed the controller in an open-loop/manual firing test mode and it was not returned to closed-loop automatic operation
Required Tools
OscilloscopeTrue-RMS clamp meterCCR configuration/parameter toolCCR wiring diagramManufacturer diagnostic software (if available)
Safety Precautions
  • A regulation failure means the CCR is no longer providing its core safety function of limiting current — treat this as a priority fault and reduce risk by not leaving the circuit running unattended until the cause is identified.
  • Apply LOTO before internal wiring inspection.
Diagnostic Procedure
  1. ObservationVary the load or input condition in a controlled way (e.g. compare readings across two different commanded steps, or note input voltage change) and confirm output current does not respond to closed-loop correction as expected.
  2. MeasurementCheck for a valid, in-range current feedback signal reaching the controller.
  3. ObservationCheck the controller's operating mode configuration to confirm it is set to closed-loop/automatic rather than an open-loop or manual test mode.
  4. MeasurementIf the manufacturer provides diagnostic software, check for a control algorithm fault/exception logged internally.
  5. DecisionNo valid feedback signal reaching the controller → sensor/wiring fault, proceed as CCR-021/030. Valid feedback present but no closed-loop correction happening → controller algorithm fault or mode misconfiguration.
  6. Fault LocationIsolate to the feedback sensor/wiring, the controller's operating mode setting, or the control algorithm itself.
  7. Root CauseConfirm the specific cause and verify closed-loop regulation is restored.
Test Points
Current feedback signal at controller input
Controller operating mode configuration
Controller diagnostic/exception log
Root Cause Verification

After correction, deliberately vary loop impedance or input voltage within a safe test procedure and confirm output current is actively held constant, demonstrating genuine closed-loop regulation rather than coincidental stability.

Corrective Action
  • Repair or replace the failed feedback sensor and wiring.
  • Return the controller to closed-loop/automatic operating mode.
  • Reset, reflash, or replace the controller if a persistent algorithm fault is confirmed.
  • Recalibrate the feedback sensor if grossly out of range.
Preventive Action
  • Verify and lock the controller's operating mode after any diagnostic/test session before returning it to service.
  • Include a genuine closed-loop response check — not just a static current reading — in periodic PM.
  • Maintain manufacturer diagnostic software access for controller-level fault investigation.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-07 (Controller Parameter Management)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic, CCR Power Stage Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-039 CCR Output Transformer Overheating

Symptom — Output transformer runs at an abnormally high temperature (by thermal imaging, thermal sensor alarm, or a burning smell) during normal or sustained operation, distinct from an internal cabinet-wide overtemperature (see Division 05 for cabinet cooling).

Equipment / System

CCR output (step-up) transformer, its cooling path, and its loading condition.

Possible Causes
HighSustained overcurrent or a marginal overvoltage condition on the loop causing the transformer to operate beyond its rated duty (see CCR-023/027)
HighBlocked or degraded transformer cooling — dust accumulation, blocked ventilation, or a failed dedicated cooling fan if fitted
MediumTransformer winding insulation degrading with age, increasing losses and heat generation at a given load
MediumTransformer tap set incorrectly for the circuit, causing it to operate consistently near or beyond its rated voltage/current combination
LowerLoose internal transformer connection increasing localized resistive heating
Required Tools
Thermal imaging cameraTrue-RMS clamp meterInsulation resistance tester (5kV)Torque screwdriver setCCR wiring diagram
Safety Precautions
  • An overheating transformer is a fire risk — if temperature is significantly above normal or a burning smell is present, de-energize immediately rather than continuing to monitor.
  • Allow the transformer to cool before physical inspection; apply LOTO throughout.
Diagnostic Procedure
  1. MeasurementThermal-image the transformer during sustained operation and compare against the manufacturer's normal operating temperature range.
  2. MeasurementClamp-meter the actual output current and voltage to check for a sustained overcurrent/overvoltage condition (cross-reference CCR-023/CCR-027).
  3. ObservationInspect the transformer's ventilation path and any dedicated cooling fan for blockage or failure.
  4. MeasurementWith the unit isolated and cooled, megger the transformer winding insulation resistance and compare against baseline.
  5. ObservationVerify the tap setting against the documented circuit length and load.
  6. DecisionConfirmed sustained overcurrent/overvoltage → address the root loop or configuration cause first, per CCR-023/027. Cooling path blocked → clean/repair ventilation. Insulation resistance degraded from baseline with load/tap confirmed normal → ageing transformer, plan replacement.
  7. Fault LocationIsolate to a loop-side overcurrent/overvoltage condition, a blocked cooling path, an incorrect tap setting, or transformer winding degradation.
  8. Root CauseConfirm the specific cause and verify operating temperature returns to normal after correction.
Test Points
Transformer surface/winding temperature (thermal imaging)
Output current and voltage under sustained load
Transformer ventilation path/cooling fan
Transformer winding insulation resistance
Root Cause Verification

After correction, run the CCR at the normal commanded step for a minimum of one hour and confirm transformer temperature stabilises within the manufacturer's normal range.

Corrective Action
  • Correct the sustained overcurrent/overvoltage root cause per CCR-023/027.
  • Clean or repair the transformer's ventilation path or cooling fan.
  • Correct the transformer tap setting.
  • Replace the transformer if winding insulation is confirmed degraded beyond acceptable limits.
  • Re-torque any loose internal transformer connection.
Preventive Action
  • Include transformer thermal imaging under sustained load in the annual PM.
  • Keep transformer ventilation paths and filters on a defined cleaning schedule.
  • Trend transformer insulation resistance year over year to plan replacement proactively.
Related References

SOP: SOP-CCR-09 (Cooling System Maintenance), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: —

Rev 0 — Initial issue
CCR-040 CCR Internal Output Connection Failure

Symptom — Intermittent or total loss of output traced to a specific internal wiring, bus bar, or terminal connection within the CCR cabinet between the bridge, output transformer, output fuse, and output terminal block — rather than an external loop or component fault.

Equipment / System

Internal high-current wiring, bus bars, and terminal connections within the CCR power stage.

Possible Causes
HighLoose high-current terminal or bus bar connection due to inadequate original torque or vibration-induced loosening over time
HighCorroded or oxidised connection, particularly in coastal or high-humidity airport environments
MediumConnector or lug damaged during a previous maintenance intervention (e.g. over-torqued, cross-threaded, or a crimp lug improperly applied)
MediumThermal cycling fatigue at a connection carrying high current over an extended service life
LowerManufacturing defect at a factory-made internal connection, surfacing after a period of service
Required Tools
Thermal imaging cameraTorque screwdriver/wrench set (calibrated)True-RMS clamp meterInsulation resistance tester (5kV)Contact cleanerCCR wiring diagram
Safety Precautions
  • Internal high-current connections can carry lethal voltage/current — apply LOTO and verify zero energy state with a proven meter before touching any internal terminal.
  • A connection showing heat discoloration or arcing damage should be treated as an active fire risk; do not re-energize until repaired.
Diagnostic Procedure
  1. ObservationThermal-image the full internal power path (bridge to output transformer to output terminal block) during sustained operation to localise any abnormally hot connection.
  2. MeasurementWith the unit isolated and LOTO applied, visually inspect the identified connection for looseness, corrosion, discoloration, or physical damage.
  3. MeasurementCheck the connection's resistance/continuity and compare against an equivalent healthy connection elsewhere in the same unit.
  4. DecisionA specific hot, loose, or corroded connection identified → direct mechanical repair. No single hot spot found despite a confirmed intermittent fault → widen the thermal survey and consider a load-cycling test to reproduce the fault under controlled conditions.
  5. Fault LocationIsolate to the specific bus bar, terminal, or connector responsible.
  6. Root CauseConfirm the connection is the true root cause by repairing it and verifying the fault does not recur under sustained load.
Test Points
Bridge output terminals
Output transformer primary and secondary terminals
Output fuse/breaker terminals
Output terminal block connections
Root Cause Verification

After repair, thermal-image the same connection points during a sustained full-load run and confirm no abnormal temperature rise, with output current stable throughout.

Corrective Action
  • Clean, re-terminate, and torque the affected connection to the manufacturer's specified value using a calibrated tool.
  • Replace a damaged lug, connector, or bus bar section.
  • Apply approved anti-oxidant compound on connections in corrosive environments per manufacturer guidance.
Preventive Action
  • Include torque-verification of internal high-current connections in the periodic PM schedule, using a calibrated torque tool rather than by feel.
  • Include internal thermal imaging under load as a standard PM test, not only during fault investigation.
  • Use anti-oxidant compound on internal connections as standard practice in coastal/high-humidity installations.
Related References

SOP: SOP-CCR-09 (Cooling System Maintenance), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, IEC 61439

Diagram: CCR Power Stage Schematic, Cabinet Layout Drawing

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue

03 · CCR Intensity Control

15 of 15 topics published
CCR-041 Brightness Step 1 Not Working

Symptom — Commanding intensity Step 1 (locally, remotely, or via ALCMS) does not produce the expected brightness level on the series circuit — either no current change occurs, or the delivered current does not match the value defined for Step 1.

Equipment / System

CCR intensity-step control path — step relay/contactor or digital step reference, controller step configuration table, output transformer tap (on step-relay-type CCRs) or current setpoint table (on digital/thyristor CCRs).

Possible Causes
HighStep relay/contactor for Step 1 failed to pull in — coil open, mechanically stuck, or contact worn
HighStep 1 reference/tap wiring open or disconnected between the controller and the output transformer tap or step relay
MediumController's Step 1 configuration parameter corrupted or set to zero/disabled
MediumStep 1 selection signal (local switch position or ALCMS command code) not reaching the controller
LowerStep 1 indication only is faulty while the actual current step is correct — a display/feedback fault rather than a true step failure
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagramInsulated torque screwdriver set
Safety Precautions
  • Confirm actual output current independently with a clamp meter before concluding the step itself has failed — the fault may be indication-only.
  • Apply LOTO before accessing step relay contacts or transformer tap terminals.
Diagnostic Procedure
  1. ObservationCommand Step 1 from the intended control source and note both the HMI-displayed step and the actual clamp-metered output current.
  2. MeasurementOn step-relay-type CCRs, check the Step 1 relay/contactor coil voltage and contact continuity when commanded.
  3. MeasurementOn digital/thyristor CCRs, verify the Step 1 current setpoint value in the controller configuration table against the design intensity schedule.
  4. MeasurementCheck the Step 1 selection signal path — local switch contact or the specific ALCMS/PLC command code — reaches the controller correctly.
  5. DecisionHMI shows Step 1 accepted but current does not change → relay/tap/setpoint fault, isolate within the step hardware or configuration. Step 1 command itself not reaching the controller → upstream selection/communication fault.
  6. Fault LocationIsolate to the Step 1 relay/contactor, its tap wiring, the controller's Step 1 configuration entry, or the step selection signal path.
  7. Root CauseConfirm the specific failed relay, wiring point, or configuration entry through direct testing.
Test Points
Step 1 relay/contactor coil and contacts
Step 1 tap wiring at output transformer (if applicable)
Step 1 setpoint value in controller configuration
Step selection signal at controller input
Root Cause Verification

Command Step 1 repeatedly from each control source and confirm the clamp-metered output current matches the design value every time, with the HMI indication agreeing.

Corrective Action
  • Replace the failed Step 1 relay/contactor.
  • Repair the Step 1 tap wiring or connection.
  • Correct the Step 1 setpoint value in the controller configuration.
  • Repair the step selection signal wiring or resolve the command code mismatch.
Preventive Action
  • Include a full 5-step verification (not just the commonly used steps) in every routine PM.
  • Track step relay duty cycles/switching counts and replace preventively per manufacturer MTBF data.
  • Lock configuration parameters after commissioning and log any authorized changes.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: —

Rev 0 — Initial issue
CCR-042 Brightness Step 2 Not Working

Symptom — Commanding intensity Step 2 (locally, remotely, or via ALCMS) does not produce the expected brightness level on the series circuit — either no current change occurs, or the delivered current does not match the value defined for Step 2.

Equipment / System

CCR intensity-step control path — step relay/contactor or digital step reference, controller step configuration table, output transformer tap (on step-relay-type CCRs) or current setpoint table (on digital/thyristor CCRs).

Possible Causes
HighStep relay/contactor for Step 2 failed to pull in — coil open, mechanically stuck, or contact worn
HighStep 2 reference/tap wiring open or disconnected between the controller and the output transformer tap or step relay
MediumController's Step 2 configuration parameter corrupted or set to zero/disabled
MediumStep 2 selection signal (local switch position or ALCMS command code) not reaching the controller
LowerStep 2 indication only is faulty while the actual current step is correct — a display/feedback fault rather than a true step failure
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagramInsulated torque screwdriver set
Safety Precautions
  • Confirm actual output current independently with a clamp meter before concluding the step itself has failed — the fault may be indication-only.
  • Apply LOTO before accessing step relay contacts or transformer tap terminals.
Diagnostic Procedure
  1. ObservationCommand Step 2 from the intended control source and note both the HMI-displayed step and the actual clamp-metered output current.
  2. MeasurementOn step-relay-type CCRs, check the Step 2 relay/contactor coil voltage and contact continuity when commanded.
  3. MeasurementOn digital/thyristor CCRs, verify the Step 2 current setpoint value in the controller configuration table against the design intensity schedule.
  4. MeasurementCheck the Step 2 selection signal path — local switch contact or the specific ALCMS/PLC command code — reaches the controller correctly.
  5. DecisionHMI shows Step 2 accepted but current does not change → relay/tap/setpoint fault, isolate within the step hardware or configuration. Step 2 command itself not reaching the controller → upstream selection/communication fault.
  6. Fault LocationIsolate to the Step 2 relay/contactor, its tap wiring, the controller's Step 2 configuration entry, or the step selection signal path.
  7. Root CauseConfirm the specific failed relay, wiring point, or configuration entry through direct testing.
Test Points
Step 2 relay/contactor coil and contacts
Step 2 tap wiring at output transformer (if applicable)
Step 2 setpoint value in controller configuration
Step selection signal at controller input
Root Cause Verification

Command Step 2 repeatedly from each control source and confirm the clamp-metered output current matches the design value every time, with the HMI indication agreeing.

Corrective Action
  • Replace the failed Step 2 relay/contactor.
  • Repair the Step 2 tap wiring or connection.
  • Correct the Step 2 setpoint value in the controller configuration.
  • Repair the step selection signal wiring or resolve the command code mismatch.
Preventive Action
  • Include a full 5-step verification (not just the commonly used steps) in every routine PM.
  • Track step relay duty cycles/switching counts and replace preventively per manufacturer MTBF data.
  • Lock configuration parameters after commissioning and log any authorized changes.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: —

Rev 0 — Initial issue
CCR-043 Brightness Step 3 Not Working

Symptom — Commanding intensity Step 3 (locally, remotely, or via ALCMS) does not produce the expected brightness level on the series circuit — either no current change occurs, or the delivered current does not match the value defined for Step 3.

Equipment / System

CCR intensity-step control path — step relay/contactor or digital step reference, controller step configuration table, output transformer tap (on step-relay-type CCRs) or current setpoint table (on digital/thyristor CCRs).

Possible Causes
HighStep relay/contactor for Step 3 failed to pull in — coil open, mechanically stuck, or contact worn
HighStep 3 reference/tap wiring open or disconnected between the controller and the output transformer tap or step relay
MediumController's Step 3 configuration parameter corrupted or set to zero/disabled
MediumStep 3 selection signal (local switch position or ALCMS command code) not reaching the controller
LowerStep 3 indication only is faulty while the actual current step is correct — a display/feedback fault rather than a true step failure
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagramInsulated torque screwdriver set
Safety Precautions
  • Confirm actual output current independently with a clamp meter before concluding the step itself has failed — the fault may be indication-only.
  • Apply LOTO before accessing step relay contacts or transformer tap terminals.
Diagnostic Procedure
  1. ObservationCommand Step 3 from the intended control source and note both the HMI-displayed step and the actual clamp-metered output current.
  2. MeasurementOn step-relay-type CCRs, check the Step 3 relay/contactor coil voltage and contact continuity when commanded.
  3. MeasurementOn digital/thyristor CCRs, verify the Step 3 current setpoint value in the controller configuration table against the design intensity schedule.
  4. MeasurementCheck the Step 3 selection signal path — local switch contact or the specific ALCMS/PLC command code — reaches the controller correctly.
  5. DecisionHMI shows Step 3 accepted but current does not change → relay/tap/setpoint fault, isolate within the step hardware or configuration. Step 3 command itself not reaching the controller → upstream selection/communication fault.
  6. Fault LocationIsolate to the Step 3 relay/contactor, its tap wiring, the controller's Step 3 configuration entry, or the step selection signal path.
  7. Root CauseConfirm the specific failed relay, wiring point, or configuration entry through direct testing.
Test Points
Step 3 relay/contactor coil and contacts
Step 3 tap wiring at output transformer (if applicable)
Step 3 setpoint value in controller configuration
Step selection signal at controller input
Root Cause Verification

Command Step 3 repeatedly from each control source and confirm the clamp-metered output current matches the design value every time, with the HMI indication agreeing.

Corrective Action
  • Replace the failed Step 3 relay/contactor.
  • Repair the Step 3 tap wiring or connection.
  • Correct the Step 3 setpoint value in the controller configuration.
  • Repair the step selection signal wiring or resolve the command code mismatch.
Preventive Action
  • Include a full 5-step verification (not just the commonly used steps) in every routine PM.
  • Track step relay duty cycles/switching counts and replace preventively per manufacturer MTBF data.
  • Lock configuration parameters after commissioning and log any authorized changes.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: —

Rev 0 — Initial issue
CCR-044 Brightness Step 4 Not Working

Symptom — Commanding intensity Step 4 (locally, remotely, or via ALCMS) does not produce the expected brightness level on the series circuit — either no current change occurs, or the delivered current does not match the value defined for Step 4.

Equipment / System

CCR intensity-step control path — step relay/contactor or digital step reference, controller step configuration table, output transformer tap (on step-relay-type CCRs) or current setpoint table (on digital/thyristor CCRs).

Possible Causes
HighStep relay/contactor for Step 4 failed to pull in — coil open, mechanically stuck, or contact worn
HighStep 4 reference/tap wiring open or disconnected between the controller and the output transformer tap or step relay
MediumController's Step 4 configuration parameter corrupted or set to zero/disabled
MediumStep 4 selection signal (local switch position or ALCMS command code) not reaching the controller
LowerStep 4 indication only is faulty while the actual current step is correct — a display/feedback fault rather than a true step failure
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagramInsulated torque screwdriver set
Safety Precautions
  • Confirm actual output current independently with a clamp meter before concluding the step itself has failed — the fault may be indication-only.
  • Apply LOTO before accessing step relay contacts or transformer tap terminals.
Diagnostic Procedure
  1. ObservationCommand Step 4 from the intended control source and note both the HMI-displayed step and the actual clamp-metered output current.
  2. MeasurementOn step-relay-type CCRs, check the Step 4 relay/contactor coil voltage and contact continuity when commanded.
  3. MeasurementOn digital/thyristor CCRs, verify the Step 4 current setpoint value in the controller configuration table against the design intensity schedule.
  4. MeasurementCheck the Step 4 selection signal path — local switch contact or the specific ALCMS/PLC command code — reaches the controller correctly.
  5. DecisionHMI shows Step 4 accepted but current does not change → relay/tap/setpoint fault, isolate within the step hardware or configuration. Step 4 command itself not reaching the controller → upstream selection/communication fault.
  6. Fault LocationIsolate to the Step 4 relay/contactor, its tap wiring, the controller's Step 4 configuration entry, or the step selection signal path.
  7. Root CauseConfirm the specific failed relay, wiring point, or configuration entry through direct testing.
Test Points
Step 4 relay/contactor coil and contacts
Step 4 tap wiring at output transformer (if applicable)
Step 4 setpoint value in controller configuration
Step selection signal at controller input
Root Cause Verification

Command Step 4 repeatedly from each control source and confirm the clamp-metered output current matches the design value every time, with the HMI indication agreeing.

Corrective Action
  • Replace the failed Step 4 relay/contactor.
  • Repair the Step 4 tap wiring or connection.
  • Correct the Step 4 setpoint value in the controller configuration.
  • Repair the step selection signal wiring or resolve the command code mismatch.
Preventive Action
  • Include a full 5-step verification (not just the commonly used steps) in every routine PM.
  • Track step relay duty cycles/switching counts and replace preventively per manufacturer MTBF data.
  • Lock configuration parameters after commissioning and log any authorized changes.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: —

Rev 0 — Initial issue
CCR-045 Brightness Step 5 Not Working

Symptom — Commanding intensity Step 5 (locally, remotely, or via ALCMS) does not produce the expected brightness level on the series circuit — either no current change occurs, or the delivered current does not match the value defined for Step 5.

Equipment / System

CCR intensity-step control path — step relay/contactor or digital step reference, controller step configuration table, output transformer tap (on step-relay-type CCRs) or current setpoint table (on digital/thyristor CCRs).

Possible Causes
HighStep relay/contactor for Step 5 failed to pull in — coil open, mechanically stuck, or contact worn
HighStep 5 reference/tap wiring open or disconnected between the controller and the output transformer tap or step relay
MediumController's Step 5 configuration parameter corrupted or set to zero/disabled
MediumStep 5 selection signal (local switch position or ALCMS command code) not reaching the controller
LowerStep 5 indication only is faulty while the actual current step is correct — a display/feedback fault rather than a true step failure
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagramInsulated torque screwdriver set
Safety Precautions
  • Confirm actual output current independently with a clamp meter before concluding the step itself has failed — the fault may be indication-only.
  • Apply LOTO before accessing step relay contacts or transformer tap terminals.
Diagnostic Procedure
  1. ObservationCommand Step 5 from the intended control source and note both the HMI-displayed step and the actual clamp-metered output current.
  2. MeasurementOn step-relay-type CCRs, check the Step 5 relay/contactor coil voltage and contact continuity when commanded.
  3. MeasurementOn digital/thyristor CCRs, verify the Step 5 current setpoint value in the controller configuration table against the design intensity schedule.
  4. MeasurementCheck the Step 5 selection signal path — local switch contact or the specific ALCMS/PLC command code — reaches the controller correctly.
  5. DecisionHMI shows Step 5 accepted but current does not change → relay/tap/setpoint fault, isolate within the step hardware or configuration. Step 5 command itself not reaching the controller → upstream selection/communication fault.
  6. Fault LocationIsolate to the Step 5 relay/contactor, its tap wiring, the controller's Step 5 configuration entry, or the step selection signal path.
  7. Root CauseConfirm the specific failed relay, wiring point, or configuration entry through direct testing.
Test Points
Step 5 relay/contactor coil and contacts
Step 5 tap wiring at output transformer (if applicable)
Step 5 setpoint value in controller configuration
Step selection signal at controller input
Root Cause Verification

Command Step 5 repeatedly from each control source and confirm the clamp-metered output current matches the design value every time, with the HMI indication agreeing.

Corrective Action
  • Replace the failed Step 5 relay/contactor.
  • Repair the Step 5 tap wiring or connection.
  • Correct the Step 5 setpoint value in the controller configuration.
  • Repair the step selection signal wiring or resolve the command code mismatch.
Preventive Action
  • Include a full 5-step verification (not just the commonly used steps) in every routine PM.
  • Track step relay duty cycles/switching counts and replace preventively per manufacturer MTBF data.
  • Lock configuration parameters after commissioning and log any authorized changes.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-CCR-02 (CCR Output Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: —

Rev 0 — Initial issue
CCR-046 One Intensity Step Missing

Symptom — Exactly one intensity step in the 5-step (or configured) schedule is unavailable or produces no change from the adjacent step, while all other steps operate correctly.

Equipment / System

Single step relay/tap or a single controller step configuration entry, isolated from the rest of the step schedule.

Possible Causes
HighThe specific step relay/contactor for the affected step has failed (see CCR-041 through CCR-045 for step-specific diagnostics)
HighThe controller configuration entry for that one step was altered, disabled, or set equal to an adjacent step's value
MediumA single tap connection on the output transformer for that step is loose or broken
LowerThe physical local selector switch has a worn or missing detent/contact position for that one step only
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagram
Safety Precautions
  • Apply LOTO before inspecting relay contacts or transformer tap connections.
  • Verify zero energy state before handling any internal tap or relay terminal.
Diagnostic Procedure
  1. ObservationIdentify precisely which single step is affected and confirm all other steps operate correctly, to rule out a general controller or feedback fault.
  2. MeasurementCommand the affected step and clamp-meter the actual output current against its design value.
  3. MeasurementCheck that specific step's relay/contactor and tap wiring per the single-step diagnostic procedure (CCR-041 to CCR-045).
  4. ObservationReview the controller's configuration table entry for that specific step against the commissioned baseline.
  5. DecisionConfiguration entry found altered/duplicated → correct the configuration. Physical relay/tap fault confirmed → proceed with mechanical repair.
  6. Fault LocationIsolate to the single affected step's relay, tap connection, or configuration entry.
  7. Root CauseConfirm the specific cause through direct testing of the isolated step.
Test Points
Affected step relay/contactor
Affected step transformer tap connection
Affected step's configuration table entry
Root Cause Verification

Command all steps in sequence, including the previously affected one, and confirm every step delivers its design current value.

Corrective Action
  • Replace the failed step relay/contactor.
  • Correct the controller configuration entry for the affected step.
  • Repair the loose or broken tap connection.
  • Replace a worn local selector switch position/detent.
Preventive Action
  • Verify all steps individually — not just spot-checking the commonly used ones — during every PM.
  • Lock and periodically audit the step configuration table against the commissioned baseline.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning)

Standards: ICAO Annex 14 Vol I

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: —

Rev 0 — Initial issue
CCR-047 Multiple Intensity Steps Missing

Symptom — Two or more intensity steps are unavailable or produce incorrect current, while at least one step (commonly the lowest or highest) still operates — distinct from a total loss of step control.

Equipment / System

Controller step configuration table as a whole, shared step-relay control wiring/bus, or a shared portion of the tap winding.

Possible Causes
HighA shared control wiring fault (e.g. a common bus feeding several step relay coils) affecting a contiguous group of steps
HighA controller firmware update or configuration reset partially overwrote the step schedule, leaving some entries correct and others reset to default/zero
MediumA section of the output transformer's multi-tap winding failed, affecting every step that depends on that winding section
MediumA shared step-selection relay/multiplexer upstream of the individual step relays has failed
LowerProgressive relay/contactor wear affecting several of the more frequently used steps first
Required Tools
True-RMS clamp meterMultimeterCCR configuration/parameter toolCCR wiring diagramInsulation resistance tester (5kV)
Safety Precautions
  • Apply LOTO before internal inspection of shared wiring, tap windings, or relay assemblies.
  • Treat a partial configuration overwrite as a signal to verify the entire step schedule, not just the reported steps, before returning the unit to service.
Diagnostic Procedure
  1. ObservationCommand every step in sequence and record which specific steps are affected, looking for a pattern (contiguous steps, alternating steps, or steps sharing a common relay/wiring group).
  2. ObservationReview the complete controller step configuration table against the commissioned baseline for all steps, not only the reported ones.
  3. MeasurementTrace the shared control wiring/bus feeding the affected group of step relays for a common fault point.
  4. MeasurementWith the unit isolated, check the output transformer's multi-tap winding continuity and insulation resistance section by section.
  5. DecisionConfiguration table shows multiple altered/reset entries → configuration corruption, restore from backup. A shared wiring fault traced to a common point → repair that shared connection. Winding section fault confirmed → transformer replacement required.
  6. Fault LocationIsolate to the controller configuration table, a shared wiring/bus fault, or a specific transformer winding section.
  7. Root CauseConfirm the specific cause and verify all previously affected steps are restored.
Test Points
Full controller step configuration table
Shared step relay control wiring/bus
Output transformer multi-tap winding sections
Root Cause Verification

Command every step in sequence and confirm all steps, including the previously affected group, deliver their design current values consistently.

Corrective Action
  • Restore the controller configuration from a verified backup or re-enter the correct step schedule.
  • Repair the shared control wiring/bus fault.
  • Replace the failed shared step-selection relay/multiplexer.
  • Replace the output transformer if a winding section is confirmed failed.
Preventive Action
  • Maintain a current, verified configuration backup for every controller and restore from it after any firmware update.
  • Verify the complete step schedule after any configuration or firmware change, not just the steps that were reportedly modified.
  • Include multi-tap winding insulation testing in the annual PM.
Related References

SOP: SOP-CCR-07 (Controller Parameter Management), SOP-CCR-08 (Intensity Step Commissioning)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic, Intensity Step Reference Table

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-048 Incorrect Intensity Selection

Symptom — The CCR delivers a valid, stable current output, but it does not correspond to the step that was actually commanded — the unit runs a step other than the one requested, without an error being flagged.

Equipment / System

Controller step command interpretation logic, local/remote selector, ALCMS/PLC command mapping.

Possible Causes
HighStep command mapping table incorrectly configured — e.g. the ALCMS sends a code intended for Step 3 but the controller has that code mapped to Step 4
HighLocal/remote selector switch left in the wrong position, causing local commands to be ignored while a stale remote step remains active, or vice versa
MediumA prior local override was never cleared, so new remote commands are being accepted but not acted upon
MediumALCMS-side configuration error sending the wrong step code for the intended runway/taxiway lighting circuit
LowerController display bug showing the previous step while actually running the new one, or the reverse (see CCR-053 for indication-only faults)
Required Tools
MultimeterTrue-RMS clamp meterCCR configuration/parameter toolProtocol analyzer or serial monitor (for ALCMS link)CCR wiring diagram
Safety Precautions
  • An incorrect intensity level on approach/runway lighting has direct flight-safety implications — treat any confirmed mismatch as an operational priority and notify air traffic services per local procedure while it is being resolved.
Diagnostic Procedure
  1. ObservationConfirm the exact step actually commanded (by the pilot-controller, tower, or ALCMS schedule) versus the step the CCR is actually running, verified by clamp meter, not just the HMI.
  2. ObservationCheck the local/remote selector switch position and whether a local override is active.
  3. MeasurementIf ALCMS-commanded, monitor the communication link to confirm the exact step code transmitted by the ALCMS and received by the CCR.
  4. ObservationReview the controller's step command mapping table against the design intent.
  5. DecisionMapping table found incorrect → correct the mapping. Selector switch in the wrong position or an uncleared override found → correct switch position and clear override, and review operating procedure with staff. Correct code confirmed sent and received but wrong step still runs → controller logic fault, escalate to manufacturer.
  6. Fault LocationIsolate to the step command mapping table, the local/remote selection state, or the ALCMS communication link.
  7. Root CauseConfirm the specific misconfiguration or procedural gap responsible.
Test Points
Local/remote selector switch position
ALCMS/PLC command code at CCR input
Controller step command mapping table
CCR output terminals (clamp meter)
Root Cause Verification

Command each step from the intended control source in turn and confirm the clamp-metered output current matches the intended step exactly, every time, across both local and remote control paths.

Corrective Action
  • Correct the controller's step command mapping table.
  • Correct the local/remote selector switch position and clear any stale override.
  • Correct the ALCMS-side step code configuration.
  • Escalate a confirmed controller logic fault to the manufacturer.
Preventive Action
  • Verify the step command mapping table against the design intensity schedule at commissioning and after any configuration change.
  • Brief operations staff on correctly clearing local overrides before returning control to ALCMS.
  • Include an end-to-end step verification (ALCMS command to measured output) in periodic PM.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-ALCMS-02 (Lighting Command Verification)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, ALCMS Interface Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-049 Intensity Changes Automatically

Symptom — The CCR's output intensity step changes on its own, without a corresponding operator, ALCMS, or scheduled command — an unexplained step-up, step-down, or repeated cycling between steps.

Equipment / System

Controller command input monitoring, ALCMS scheduling/automation logic, local control wiring.

Possible Causes
HighAn unintended ALCMS automation rule or schedule (e.g. an astronomical/time-based dimming schedule) is active and changing the step as designed, but was not communicated to site staff
HighElectrical noise or a faulty contact on the local step-selection wiring intermittently simulating a step-change command
MediumA protection function (e.g. thermal derate) automatically reducing the step, which is a designed safety response rather than a fault (cross-reference CCR-033/039)
MediumALCMS communication link fault causing spurious/corrupted step commands to be received and acted upon
LowerController firmware fault causing an internal, unintended step change
Required Tools
MultimeterProtocol analyzer or serial monitor (for ALCMS link)CCR event/alarm log toolCCR configuration toolCCR wiring diagram
Safety Precautions
  • An unexplained automatic intensity change during active operations should be reported to air traffic services immediately, since it directly affects visual reference for pilots.
  • Do not disable a protection-driven automatic step reduction (e.g. thermal derate) without first understanding and addressing its underlying cause.
Diagnostic Procedure
  1. ObservationPull the controller's full event/alarm log and the ALCMS command history for the time window of the unexplained change, to determine whether a legitimate automated command (e.g. a dimming schedule) or protection trip actually caused it.
  2. DecisionA legitimate scheduled/automated command found → not an equipment fault; align site procedures and staff awareness with the automation schedule.
  3. MeasurementIf no legitimate command is found in the logs, inspect the local step-selection wiring for a noise source or intermittent contact.
  4. MeasurementCheck the ALCMS communication link for error rates or corrupted message events around the time of each unexplained change.
  5. DecisionIntermittent local wiring fault confirmed → repair wiring. Communication link errors correlate with each event → address the communication link. Neither found → escalate as a possible controller firmware fault.
  6. Fault LocationIsolate to an ALCMS automation/scheduling configuration, the local control wiring, the ALCMS communication link, or controller firmware.
  7. Root CauseConfirm the specific cause by correlating each occurrence against logged events.
Test Points
Controller full event/alarm log
ALCMS command history
Local step-selection wiring
ALCMS communication link error log
Root Cause Verification

Monitor the CCR over a period spanning at least one full operational cycle after correction and confirm the intensity step changes only in response to legitimate, logged commands.

Corrective Action
  • Align site procedures and staff awareness with a confirmed legitimate ALCMS automation schedule.
  • Repair the intermittent local step-selection wiring fault.
  • Repair or replace the faulty ALCMS communication link hardware.
  • Reflash/reset controller firmware if a confirmed internal fault.
Preventive Action
  • Document all active ALCMS automation/dimming schedules and brief maintenance and ATC staff.
  • Include a communication link error-rate check in periodic PM.
  • Log and review all automatic step changes as part of routine system health monitoring.
Related References

SOP: SOP-ALCMS-02 (Lighting Command Verification), SOP-CCR-07 (Controller Parameter Management)

Standards: ICAO Annex 14 Vol I

Diagram: CCR Control Schematic, ALCMS Interface Diagram

Case Study: —

Rev 0 — Initial issue
CCR-050 Intensity Command Not Accepted

Symptom — A step-change command issued locally, remotely, or via ALCMS is not acted upon at all — the CCR continues running its previous step and does not respond, though it remains otherwise healthy with no active alarm.

Equipment / System

Controller command input path — local switch, remote/ALCMS communication interface, command validation logic.

Possible Causes
HighController is in local mode while the command was sent remotely, or vice versa, with the selector position not matching the command source
HighA latched fault or safety interlock is silently blocking step changes without raising a visible alarm (see CCR-030 for a similar unannounced-fault pattern)
MediumALCMS/PLC command signal wiring or communication link fault preventing the command from reaching the controller
MediumThe requested step is outside a configured minimum/maximum limit and is being rejected by validation logic without a clear operator-facing message
LowerController command-processing task locked up (partial firmware fault) while other functions remain responsive
Required Tools
MultimeterProtocol analyzer or serial monitorCCR event/alarm log toolCCR configuration toolCCR wiring diagram
Safety Precautions
  • Do not repeatedly re-send a command as the only troubleshooting step — investigate the root cause, since a masked interlock or logic fault could recur at a critical moment.
Diagnostic Procedure
  1. ObservationConfirm the local/remote selector position matches the source the command was actually sent from.
  2. ObservationPull the controller's full event/alarm log to check for a latched interlock or fault silently blocking step changes.
  3. MeasurementVerify the command signal/communication link is actually reaching the controller (correct wiring continuity or communication link activity).
  4. ObservationCheck whether the requested step falls within any configured minimum/maximum limit in the controller.
  5. DecisionSelector position mismatch found → correct operator procedure/switch position. Latched interlock found → resolve the underlying interlock condition per its specific fault topic. Command confirmed reaching the controller with no interlock or limit issue → escalate as a controller command-processing fault.
  6. Fault LocationIsolate to the local/remote selection, a latched interlock, the command signal path, a configured limit, or controller command processing.
  7. Root CauseConfirm the specific blocking condition and verify commands are accepted once cleared.
Test Points
Local/remote selector switch
Controller full event/alarm log
Command signal/communication link
Configured step minimum/maximum limits
Root Cause Verification

Issue step-change commands from both local and remote/ALCMS sources across the full step range and confirm each is accepted and acted upon promptly.

Corrective Action
  • Correct the local/remote selector position and clarify command-source procedures with operators.
  • Resolve the underlying latched interlock condition.
  • Repair the command signal wiring or communication link.
  • Correct the configured step limits if set incorrectly.
  • Reset/reflash the controller if a command-processing lock-up is confirmed.
Preventive Action
  • Review the complete event/alarm log periodically, not only currently active alarms, to catch silently latched conditions early.
  • Include a full-range command acceptance test in periodic PM.
  • Document configured step limits clearly in the site commissioning record.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-ALCMS-02 (Lighting Command Verification)

Standards: ICAO Annex 14 Vol I

Diagram: CCR Control Schematic, ALCMS Interface Diagram

Case Study: —

Rev 0 — Initial issue
CCR-051 Local Intensity Control Failure

Symptom — Intensity step commands issued from the CCR's local control panel/switch are not acted upon, while remote/ALCMS-issued commands (or vice versa) continue to work normally.

Equipment / System

Local control panel step-selector switch, its wiring to the controller, and the controller's local-mode command interpretation.

Possible Causes
HighLocal selector switch itself failed — worn contacts, broken shaft, or a position not making contact
HighWiring between the local selector switch and the controller's local command input broken or loose
MediumController not actually in local mode despite the local/remote switch appearing to be positioned there — a mode-selection contact fault
MediumA local control panel lock/key switch left in a disabled position
LowerController's local command input circuit (opto-isolator or input card) failed
Required Tools
MultimeterCCR wiring diagramContinuity/probe test leadsInsulated torque screwdriver set
Safety Precautions
  • Apply LOTO before internal inspection of the local control wiring or input card, unless the manufacturer's procedure permits live testing with appropriate precautions.
Diagnostic Procedure
  1. ObservationConfirm the local/remote mode switch position and any key/lock switch status at the local control panel.
  2. MeasurementOperate the local step-selector switch through each position and check for correct contact closure/output at the switch itself.
  3. MeasurementCheck continuity of the wiring between the local selector switch and the controller's local command input terminals.
  4. MeasurementVerify the controller is actually registering local mode internally (via HMI status or diagnostic tool), not just switch position.
  5. DecisionSelector switch itself fails to make contact → replace switch. Switch operates correctly but signal doesn't reach the controller → wiring fault. Wiring confirmed intact but controller doesn't register local mode → controller input circuit fault.
  6. Fault LocationIsolate to the local selector switch, its wiring, or the controller's local command input circuit.
  7. Root CauseConfirm the specific failed component through direct testing.
Test Points
Local step-selector switch contacts
Local control wiring at controller terminals
Controller local-mode status/registration
Local control panel key/lock switch
Root Cause Verification

Operate the local selector through every step position and confirm the CCR responds correctly and promptly to each, with the controller correctly registering local mode.

Corrective Action
  • Replace the failed local selector switch.
  • Repair or replace the local control wiring.
  • Repair the controller's local command input circuit/card.
  • Correct the local control panel key/lock switch position.
Preventive Action
  • Include a full local-control functional test in periodic PM, exercising every step position.
  • Keep the local control panel key/lock switch procedure documented and enforced.
  • Track local selector switch wear and replace preventively based on operating history.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning)

Standards: ICAO Annex 14 Vol I

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-052 Remote Intensity Control Failure

Symptom — Intensity step commands issued from ALCMS/remote tower control are not acted upon, while local control panel commands continue to work normally.

Equipment / System

ALCMS/PLC communication link, the controller's remote command interface, and remote-mode command interpretation.

Possible Causes
HighALCMS/PLC communication link down or degraded — cable fault, network switch failure, or a fibre/media converter fault on the link to this CCR
HighController not registering remote mode despite the local/remote switch being positioned for remote operation
MediumCommunication protocol mismatch or address/ID misconfiguration after a controller or ALCMS-side change
MediumRemote command input circuit (opto-isolator, communication card) on the controller failed
LowerALCMS-side configuration for this specific CCR removed or altered, so it is no longer being addressed correctly
Required Tools
MultimeterProtocol analyzer or serial monitorNetwork/fibre test equipment (as applicable)CCR configuration toolCCR wiring diagram
Safety Precautions
  • Loss of remote control removes ATC's ability to adjust runway/approach lighting intensity in real time — treat this as an operationally significant fault and notify air traffic services promptly per local procedure while resolving it.
  • Apply LOTO before internal inspection of the communication card.
Diagnostic Procedure
  1. ObservationConfirm the local/remote mode switch is correctly positioned for remote operation and that the controller registers remote mode internally.
  2. MeasurementCheck the ALCMS/PLC communication link status — link/activity indicators, cable continuity, or network/fibre diagnostics as applicable.
  3. ObservationVerify the CCR's address/ID and communication protocol configuration matches what the ALCMS expects to see.
  4. MeasurementIf link and configuration appear correct, monitor actual command traffic to confirm whether commands are reaching the controller's communication port at all.
  5. DecisionCommunication link confirmed down → repair cable/network hardware. Link up but address/protocol mismatch found → correct configuration on the CCR or ALCMS side. Link and configuration correct but commands still not registering → controller communication card fault.
  6. Fault LocationIsolate to the communication link, the address/protocol configuration, or the controller's communication card.
  7. Root CauseConfirm the specific cause and verify remote commands are accepted end-to-end.
Test Points
Local/remote mode switch and controller mode status
ALCMS/PLC communication link (cable, network, or fibre)
Controller address/ID and protocol configuration
Controller communication card
Root Cause Verification

Issue step-change commands from ALCMS/remote tower control across the full step range and confirm each is accepted and acted upon promptly, with the correct step reflected back to ALCMS.

Corrective Action
  • Repair or replace the faulty communication cable, network switch, or media converter.
  • Correct the CCR's address/ID or protocol configuration to match the ALCMS.
  • Replace the controller's failed communication card.
  • Restore or correct the ALCMS-side configuration for this CCR.
Preventive Action
  • Include a communication link health check (error rates, link status) in periodic PM.
  • Maintain a documented, current record of every CCR's ALCMS address/protocol configuration.
  • Test remote control functionality end-to-end after any ALCMS or network change, not just locally at the CCR.
Related References

SOP: SOP-ALCMS-02 (Lighting Command Verification), SOP-CCR-08 (Intensity Step Commissioning)

Standards: ICAO Annex 14 Vol I, FAA AC 150/5345-10

Diagram: CCR Control Schematic, ALCMS Interface Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-053 Step Indication Incorrect

Symptom — The CCR's HMI, local indicator, or ALCMS status display shows a different intensity step than what is actually being delivered at the output — a display/feedback mismatch rather than a true control fault (verify against CCR-048 which covers a genuine wrong-step delivery).

Equipment / System

Controller step status feedback/display logic, HMI, and any status reporting to ALCMS.

Possible Causes
HighStep feedback signal used for display purposes (separate from the actual control setpoint) failed or reads incorrectly
MediumHMI display firmware fault showing a stale or cached step value rather than the live one
MediumStep status reporting to ALCMS uses a different data point or mapping than the local HMI, and one of the two is misconfigured
LowerA momentary display glitch that clears on its own but was not investigated at the time
Required Tools
True-RMS clamp meterMultimeterCCR configuration toolProtocol analyzer or serial monitor
Safety Precautions
  • Do not assume the discrepancy is purely cosmetic — always verify actual delivered current independently before ruling out a genuine control fault, since an indication fault can mask a real problem.
Diagnostic Procedure
  1. MeasurementIndependently clamp-meter the actual output current for the currently commanded step and confirm it matches the design value for that step (ruling out CCR-048).
  2. ObservationCompare the local HMI step indication, any physical indicator lights, and the ALCMS-reported step status against the confirmed actual output.
  3. ObservationCommand a deliberate step change and observe whether each display updates promptly and correctly.
  4. DecisionActual output confirmed correct for the commanded step but one or more displays disagree → indication/feedback fault, isolate to the specific display path that is wrong. Actual output also incorrect → redirect to CCR-048.
  5. Fault LocationIsolate to the specific step feedback signal, the HMI firmware, or the ALCMS status reporting configuration.
  6. Root CauseConfirm the specific faulty indication path through step changes and cross-verification.
Test Points
CCR output terminals (clamp meter, ground truth)
Local HMI step display
Physical step indicator lights (if fitted)
ALCMS-reported step status
Root Cause Verification

Command a full sequence of step changes and confirm the local HMI, physical indicators, and ALCMS status all correctly and promptly reflect the true output current at every step.

Corrective Action
  • Repair or replace the failed step feedback signal/sensor.
  • Update or reset the HMI firmware if a display caching fault is confirmed.
  • Correct the ALCMS status reporting configuration/mapping.
Preventive Action
  • Cross-check local HMI, physical indicators, and ALCMS status against actual clamp-metered output during routine PM.
  • Include display/indication verification as a distinct checklist item, separate from output verification, in commissioning.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-ALCMS-02 (Lighting Command Verification)

Standards: ICAO Annex 14 Vol I

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-054 Step Relay Failure

Symptom — A specific step relay/contactor within the CCR's step-switching assembly fails mechanically or electrically — confirmed by direct inspection as the root cause underlying one or more of the step-fault symptoms (CCR-041 to CCR-047), documented here as the component-level fault record.

Equipment / System

Step relay/contactor assembly used to switch output transformer taps or current reference points for each intensity step (on relay-switched CCR designs).

Possible Causes
HighRelay coil open or burnt out from repeated switching duty or an overvoltage condition on the coil circuit
HighRelay contacts welded closed, worn, or pitted from repeated switching under load, preventing reliable make/break
MediumMechanical linkage or armature binding due to age, contamination, or corrosion
MediumRelay coil driver circuit on the controller board failed, unable to energize the coil even though the relay itself is healthy
LowerIncorrect replacement relay fitted at a previous repair, with a coil voltage or contact rating mismatch
Required Tools
MultimeterTrue-RMS clamp meterInsulated torque screwdriver setContact cleanerManufacturer relay specification sheet
Safety Precautions
  • Apply LOTO before removing or testing any step relay — contacts may be switching high current at line voltage.
  • Do not clean or file welded/pitted contacts as a permanent fix — replace the relay.
Diagnostic Procedure
  1. ObservationConfirm which step(s) are affected by the suspected relay and cross-reference against CCR-041 to CCR-047 for the step-specific symptom.
  2. MeasurementWith the unit isolated, check relay coil resistance/continuity against the manufacturer's specification.
  3. MeasurementInspect relay contacts for welding, pitting, or excessive wear.
  4. MeasurementCheck the coil driver circuit on the controller board for correct output voltage to the relay coil when the step is commanded.
  5. DecisionCoil open or contacts confirmed welded/worn → replace the relay. Relay itself tests healthy but coil driver circuit shows no output → controller board fault, not the relay.
  6. Fault LocationIsolate to the specific relay or the controller's coil driver circuit.
  7. Root CauseConfirm the specific failure mode — coil, contacts, or driver circuit.
Test Points
Relay coil resistance/continuity
Relay contact condition
Coil driver circuit output at controller board
Root Cause Verification

After replacement, cycle the affected step relay through multiple commanded operations and confirm reliable, clean make/break switching with the correct output current delivered each time.

Corrective Action
  • Replace the failed step relay/contactor with the manufacturer-specified part (correct coil voltage and contact rating).
  • Repair the controller's coil driver circuit if confirmed faulty.
  • Clean and inspect the mechanical linkage/armature; replace if binding persists after cleaning.
Preventive Action
  • Track step relay switching counts/duty cycles and replace preventively based on manufacturer MTBF data, rather than waiting for failure.
  • Verify replacement relay specifications match the original before fitting.
  • Include contact resistance testing of step relays in the annual PM.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic, Step Relay Assembly Drawing

Case Study: —

Rev 0 — Initial issue
CCR-055 Intensity Control Relay Sticking

Symptom — A step relay/contactor is mechanically slow to release or occasionally remains latched in its previous position after a step-change command, causing a delayed, intermittent, or momentarily incorrect step transition rather than a complete failure.

Equipment / System

Step relay/contactor mechanical assembly, armature and contact return spring, ambient/internal cabinet conditions.

Possible Causes
HighContamination, dust, or corrosion buildup on the relay armature or guide surfaces increasing mechanical friction
HighWeakened or fatigued return spring no longer providing reliable release force
MediumExcessive heat in the cabinet softening or degrading relay materials, increasing friction or slowing mechanical response
MediumContact surfaces lightly welded/tacked from repeated switching, releasing only under vibration or a subsequent switching event rather than cleanly
LowerRelay nearing end of rated mechanical life with general wear across all moving parts
Required Tools
MultimeterTrue-RMS clamp meter with loggingContact cleanerThermal imaging cameraManufacturer relay specification sheet
Safety Precautions
  • A sticking relay can momentarily deliver an unintended intensity level during a transition — treat repeated occurrences as an operational concern and prioritise correction.
  • Apply LOTO before physical inspection or cleaning of the relay.
Diagnostic Procedure
  1. ObservationLog step-change events and the corresponding output current transition to characterise the sticking behaviour — delayed release, intermittent, or occurring only after multiple operations.
  2. MeasurementWith the unit isolated, physically inspect the relay armature and contacts for contamination, corrosion, or surface damage.
  3. MeasurementCheck the return spring condition and free movement of the armature by hand (unit isolated) against the manufacturer's expected resistance.
  4. MeasurementThermal-image the cabinet area around the relay during sustained operation to check for excessive ambient heat contributing to the condition.
  5. DecisionContamination/corrosion found → clean and verify free movement. Return spring confirmed weak → replace the relay. Excessive cabinet heat found with no other relay defect → address cabinet cooling (see Division 05) as the underlying cause.
  6. Fault LocationIsolate to relay contamination, a weakened return spring, contact tacking, or excessive ambient heat.
  7. Root CauseConfirm the specific mechanical cause and verify clean, prompt switching after correction.
Test Points
Relay armature and contact surfaces
Return spring condition
Cabinet ambient temperature near the relay
Step-change transition timing (logged)
Root Cause Verification

Cycle the affected relay through repeated step-change commands after correction and confirm prompt, clean, and consistent release and re-engagement with no delayed or intermittent transitions.

Corrective Action
  • Clean and inspect the relay armature and contact surfaces; verify free mechanical movement.
  • Replace the relay if the return spring or contacts are confirmed degraded.
  • Improve cabinet cooling/ventilation if excessive ambient heat is a contributing factor.
  • Replace the relay if nearing end of rated mechanical life.
Preventive Action
  • Include a mechanical free-movement check of step relays in the annual PM.
  • Track relay age/switching count against manufacturer rated mechanical life.
  • Address cabinet cooling deficiencies proactively rather than only after a relay-sticking event.
Related References

SOP: SOP-CCR-08 (Intensity Step Commissioning), SOP-CCR-09 (Cooling System Maintenance)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Control Schematic, Step Relay Assembly Drawing

Case Study: —

Rev 0 — Initial issue

04 · CCR Protection & Alarms

15 of 15 topics published
CCR-056 CCR Earth Fault Alarm

Symptom — CCR raises an earth fault (ground fault) alarm and trips output, indicating leakage current from the series circuit or internal wiring to earth has exceeded the protection threshold.

Equipment / System

CCR earth fault protection relay/sensor (core balance CT or internal earth leakage monitor), series circuit loop, internal wiring.

Possible Causes
HighDegraded insulation on the series circuit cable or an isolating transformer allowing leakage current to earth
HighWater ingress at a cable joint, pull box, or fixture allowing a conductive path to earth
MediumDamaged or pinched cable insulation from installation or excavation work
MediumInternal CCR wiring insulation breakdown or moisture in the cabinet
LowerEarth fault relay/sensor itself drifted or miscalibrated, giving a false trip
LowerA minor transient switching surge tripping a tightly set threshold
Required Tools
Insulation resistance tester (5kV megger)Earth fault locator/loop testerTrue-RMS clamp meterMultimeterSeries circuit as-built drawing
Safety Precautions
  • Treat an earth fault trip as a genuine safety event until proven otherwise — do not repeatedly reset without investigation, as it may indicate a live conductor in contact with a person-accessible surface.
  • Apply LOTO before loop testing.
  • Use insulated tools and PPE rated for the loop's potential voltage.
Diagnostic Procedure
  1. ObservationRecord the earth fault alarm/trip and any fault-current magnitude reported by the controller.
  2. MeasurementWith the CCR isolated, megger the full series circuit loop insulation resistance to earth and compare against baseline commissioning values.
  3. MeasurementIf insulation resistance is low, segment-test the loop (pull boxes/junctions) to localise the affected section.
  4. ObservationInspect suspect sections for visible water ingress, cable damage, or fixture/isolating transformer failure.
  5. MeasurementVerify the earth fault relay/sensor calibration and threshold setting against the design spec.
  6. DecisionLow insulation resistance confirmed in a specific segment → genuine earth fault, proceed to repair. Insulation resistance normal across the loop → relay/sensor calibration issue or nuisance trip, investigate threshold setting and sensor health.
  7. Fault LocationIsolate to the specific cable segment, connector, isolating transformer, or the earth fault relay/sensor itself.
  8. Root CauseConfirm the precise point of insulation breakdown by physical inspection once localised.
Test Points
Series circuit loop insulation resistance to earth (segment by segment)
Earth fault relay/sensor threshold and calibration
Suspect pull boxes/junctions
Isolating transformer insulation
Root Cause Verification

After repair, re-megger the full loop and confirm insulation resistance meets or exceeds the design minimum; run the CCR through a full load cycle with no repeat trip.

Corrective Action
  • Repair or replace the damaged cable/connector/isolating transformer.
  • Dry and reseal a water-ingress point.
  • Recalibrate or replace the earth fault relay/sensor.
  • Adjust the threshold only within manufacturer-approved limits and with documented justification.
Preventive Action
  • Include loop insulation resistance testing (megger) in the annual PM, trended against baseline.
  • Seal cable joints and pull boxes to industry standard to prevent water ingress.
  • Verify earth fault relay calibration during scheduled maintenance.
Related References

SOP: SOP-CCR-06 (Series Circuit Loop Testing), SOP-CCR-10 (Protection Relay Calibration)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822), IS 7785

Diagram: Series Circuit Single Line Diagram, CCR Protection Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-057 CCR Overcurrent Alarm

Symptom — CCR trips on an overcurrent alarm, with output current exceeding the protection threshold before the controller shuts down the bridge.

Equipment / System

CCR power stage, current feedback sensor, overcurrent protection relay/logic.

Possible Causes
HighGenuine short-circuit or low-impedance fault on the series circuit loop causing an actual overcurrent
HighCurrent feedback sensor faulty/miscalibrated, causing the controller to over-drive the bridge trying to reach a falsely-low reading, resulting in true overcurrent
MediumOvercurrent threshold set too tight for the circuit's normal inrush/startup profile
MediumBridge firing circuit fault causing an uncontrolled conduction angle
LowerTransient surge/lightning-induced current spike tripping protection correctly
Required Tools
True-RMS clamp meterOscilloscopeInsulation resistance testerMultimeterCCR configuration/parameter tool
Safety Precautions
  • An overcurrent trip may indicate an active short circuit — do not reset without investigation, as repeated fault-current interruption can damage protection devices and pose a fire risk.
  • Apply LOTO before loop or bridge inspection.
Diagnostic Procedure
  1. ObservationReview the event log for the exact trip current value, timestamp, and whether the trip occurred at start-up or under steady-state run.
  2. MeasurementWith the unit isolated, megger and continuity-test the series circuit loop to check for a genuine short/low-impedance fault.
  3. MeasurementClamp-meter the actual output current on a controlled restart attempt (if safe) and compare against the HMI-reported value.
  4. MeasurementCheck current feedback sensor output and wiring against expected values.
  5. ObservationReview the overcurrent threshold setting against the manufacturer's recommended value for the installed circuit.
  6. DecisionLow loop insulation/resistance confirmed → genuine short circuit, proceed to segment isolation. Loop tests healthy but sensor/HMI mismatch found → feedback sensor fault. Loop and sensor both healthy → threshold too tight or a genuine transient event.
  7. Fault LocationIsolate to the series circuit loop, the current feedback sensor, or the protection threshold configuration.
  8. Root CauseConfirm the specific failed component or configuration error.
Test Points
Series circuit loop insulation resistance and continuity
Current feedback sensor output
Overcurrent threshold parameter
Bridge firing signals
Root Cause Verification

After repair, run the CCR through several start/stop cycles and confirm output current tracks the commanded step with no repeat trip.

Corrective Action
  • Repair the short-circuit fault on the loop.
  • Replace or recalibrate the current feedback sensor.
  • Adjust the overcurrent threshold only within manufacturer limits with documented justification.
  • Repair the firing circuit if confirmed faulty.
Preventive Action
  • Include loop insulation/continuity testing in the PM programme.
  • Verify current feedback sensor calibration annually.
  • Document any threshold changes through change control.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-10 (Protection Relay Calibration)

Standards: ICAO Annex 14 Vol I, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic, CCR Protection Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-058 CCR Overvoltage Alarm

Symptom — CCR trips on an internal overvoltage protection alarm, with the controller detecting a voltage (input, DC bus, or output) above the protection threshold and shutting down the output.

Equipment / System

CCR internal overvoltage protection relay/monitoring circuit, DC bus/output voltage sensing.

Possible Causes
HighA genuine sustained input overvoltage condition (see CCR-005) reaching the internal protection threshold
HighVoltage sensing circuit fault causing a false high reading
MediumTransient voltage spike/surge event (lightning-induced or switching transient) exceeding the instantaneous threshold
MediumOutput transformer tap set incorrectly, causing developed voltage to exceed the protection ceiling under normal load
LowerOvervoltage threshold configured incorrectly for the installed equipment rating
Required Tools
Multimeter with min/max holdPower quality analyzerOscilloscopeCCR configuration/parameter toolCCR wiring diagram
Safety Precautions
  • Do not repeatedly reset an overvoltage trip without investigation — sustained overvoltage can damage internal components and reduce insulation life.
  • Apply LOTO before internal inspection.
Diagnostic Procedure
  1. ObservationReview the event log for the exact trip voltage, timestamp, and whether it correlates with a known switching or supply event.
  2. MeasurementIndependently measure input voltage at the CCR terminals over a representative period to confirm whether a genuine input overvoltage exists (cross-reference CCR-005).
  3. MeasurementVerify the internal voltage sensing circuit reading against an independent meter at the same point.
  4. ObservationCheck for correlation with known transient events (nearby switching, thunderstorm activity, generator changeover).
  5. MeasurementVerify the overvoltage threshold and output transformer tap setting against design documentation.
  6. DecisionIndependent measurement confirms genuine sustained overvoltage → escalate to upstream supply/generator issue (CCR-005). Independent measurement normal but relay trips → sensing circuit fault or threshold misconfiguration. Isolated transient correlating with a known event → protection operated correctly on a real transient.
  7. Fault LocationIsolate to the upstream supply, the internal voltage sensing circuit, or the threshold/tap configuration.
  8. Root CauseConfirm the specific cause through comparative measurement.
Test Points
CCR input terminals (independent meter)
Internal voltage sensing circuit output
Overvoltage threshold parameter
Output transformer tap setting
Root Cause Verification

After correction, monitor voltage over a representative operating period, including any known transient-prone conditions, and confirm no repeat trip.

Corrective Action
  • Address the upstream overvoltage cause per CCR-005.
  • Repair or recalibrate the internal voltage sensing circuit.
  • Correct the transformer tap setting.
  • Adjust the threshold only within manufacturer-approved limits.
Preventive Action
  • Include a voltage sensing accuracy check in periodic PM.
  • Ensure surge protection is installed and maintained per CCR-063.
  • Document threshold settings and any changes through change control.
Related References

SOP: SOP-CCR-02, SOP-CCR-10 (Protection Relay Calibration)

Standards: IEC 60364, IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Protection Schematic, CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-059 CCR Undervoltage Alarm

Symptom — CCR raises an undervoltage alarm and trips or derates output while running, with input or internal supply voltage falling below the protection threshold during operation rather than at start-up.

Equipment / System

CCR undervoltage protection relay/monitoring circuit, input supply, control power supply.

Possible Causes
HighA genuine sag/dip on the input supply during operation, e.g. from a large coincident load starting elsewhere on the feeder
HighVoltage sensing circuit fault causing a false low reading
MediumLoose or degrading input terminal connection developing resistance and dropping voltage under load
MediumUndervoltage threshold set too tight relative to the site's normal supply variation
LowerGenerator/standby supply voltage sagging during a load transfer or under generator loading
Required Tools
Multimeter with min/max holdPower quality analyzer/voltage loggerClamp meterCCR wiring diagram
Safety Precautions
  • Standard LV measurement precautions apply.
  • Do not force-restart repeatedly against an active undervoltage condition, as running at reduced voltage can stress the regulator and connected fixtures.
Diagnostic Procedure
  1. ObservationReview the event log for the exact trip voltage, duration, and timestamp.
  2. MeasurementLog input voltage independently at the CCR terminals over a representative period, including the timestamp of the trip.
  3. MeasurementCompare against the upstream distribution panel voltage logged at the same time to isolate source versus feeder-side sag.
  4. MeasurementInspect and torque-check input terminal connections for looseness/heating.
  5. ObservationVerify the undervoltage threshold setting against the manufacturer's recommended value and the site's documented supply tolerance.
  6. DecisionSag confirmed at the panel too → upstream supply issue, escalate per CCR-004 methodology. Panel voltage normal but CCR terminal voltage sags → loose connection/feeder-side issue. Independently logged voltage stays normal despite a trip → sensing circuit fault or threshold too tight.
  7. Fault LocationIsolate to the upstream supply, a loose terminal connection, or the internal sensing/threshold configuration.
  8. Root CauseConfirm the specific cause through comparative logging.
Test Points
Upstream distribution panel voltage
CCR input terminals (independent logger)
Input terminal connections
Undervoltage threshold parameter
Root Cause Verification

Re-log voltage under full load, including peak-demand periods, after correction and confirm it stays within tolerance with no repeat trip.

Corrective Action
  • Rectify loose/high-resistance connections.
  • Escalate and address a confirmed upstream sag.
  • Repair or recalibrate the sensing circuit.
  • Adjust the threshold only within manufacturer-approved limits with documented justification.
Preventive Action
  • Include a voltage-drop/logging survey in the PM programme.
  • Perform periodic thermal imaging of input terminals.
  • Coordinate with the utility/generator team on known load-shedding or transfer events.
Related References

SOP: SOP-CCR-02, SOP-CCR-10

Standards: IEC 60364, FAA AC 150/5345-10

Diagram: Feeder Cable Route Drawing, CCR Protection Schematic

Case Study: —

Rev 0 — Initial issue
CCR-060 CCR Overtemperature Alarm

Symptom — CCR raises an overtemperature alarm and derates or trips output, with an internal temperature sensor (heatsink, bridge, or cabinet) reporting a value above the protection threshold.

Equipment / System

CCR power stage heatsink, internal temperature sensor(s), cooling system.

Possible Causes
HighCooling fan failure or degraded airflow reducing heat dissipation (see CCR-066)
HighBlocked/dirty ventilation filters or vents restricting airflow
MediumAmbient temperature at the installation location exceeding the CCR's rated operating range
MediumTemperature sensor faulty/miscalibrated, giving a false high reading
LowerBridge device degradation increasing internal power dissipation/heat generation for a given output
LowerOvertemperature threshold set too conservatively relative to the manufacturer's actual rating
Required Tools
Thermal imaging cameraMultimeterSensor calibration referenceCooling system inspection tools
Safety Precautions
  • Do not repeatedly reset an overtemperature trip and continue running — this risks accelerated component degradation or fire.
  • Allow the unit to cool and investigate before restarting.
  • Apply LOTO before internal cooling system inspection.
Diagnostic Procedure
  1. ObservationReview the event log for the exact trip temperature, sensor location, and timestamp.
  2. ObservationConfirm cooling fan operation and airflow at the intake/exhaust.
  3. MeasurementInspect and clean/replace ventilation filters and check for blocked vents.
  4. MeasurementThermal-image the heatsink/bridge and cabinet during a sustained run (where safe) to confirm the actual temperature distribution.
  5. MeasurementIndependently verify the temperature sensor reading against a calibrated reference where practical.
  6. DecisionFan not running or airflow blocked → cooling system fault (see CCR-066/067). Cooling confirmed healthy but temperature still high → ambient conditions or bridge device degradation. Thermal imaging shows normal temperature but the alarm persists → sensor fault.
  7. Fault LocationIsolate to the cooling system, ambient/installation conditions, the bridge devices, or the temperature sensor.
  8. Root CauseConfirm the specific cause and verify temperature returns to normal operating range after correction.
Test Points
Cooling fan operation
Ventilation filter/vent condition
Heatsink/bridge temperature (thermal image)
Temperature sensor calibration
Root Cause Verification

Run the CCR at full commanded step for a minimum of one hour after correction and confirm temperature remains within the normal operating range with no repeat alarm.

Corrective Action
  • Repair or replace the failed cooling fan.
  • Clean or replace blocked filters/vents.
  • Improve cabinet ventilation/installation conditions if ambient is a factor.
  • Recalibrate or replace the temperature sensor.
  • Replace degraded bridge devices if confirmed as the heat source.
Preventive Action
  • Include cooling fan and filter inspection/cleaning in routine PM.
  • Schedule periodic thermal imaging of the power stage.
  • Verify temperature sensor calibration annually.
Related References

SOP: SOP-CCR-09 (Cooling System Maintenance), SOP-CCR-10 (Protection Relay Calibration)

Standards: IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic, Cooling System Layout

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-061 CCR Transformer Temperature Alarm

Symptom — CCR raises a transformer (output/isolation) temperature alarm, with a dedicated winding or oil/air temperature sensor on the output transformer reporting a value above the protection threshold.

Equipment / System

CCR output transformer, embedded winding temperature sensor (RTD/thermocouple/thermostat), transformer cooling (natural or forced air).

Possible Causes
HighTransformer overloaded relative to its rated capacity for the connected circuit length/load
HighTransformer cooling airflow restricted (dust, blocked vents, failed cooling fan where fitted)
MediumTransformer winding insulation degrading, increasing internal losses and heat generation
MediumTemperature sensor/RTD faulty or its wiring to the controller damaged, giving a false reading
LowerAmbient temperature in the transformer compartment exceeding design conditions
LowerTransformer tap set incorrectly, causing it to operate outside its optimal efficiency point and generate excess heat
Required Tools
Thermal imaging cameraInsulation resistance tester (5kV)MultimeterTransformer nameplate/rating referenceRTD/sensor test tool
Safety Precautions
  • A genuinely overheating transformer is a fire risk — do not defer investigation or repeatedly reset the alarm.
  • Apply LOTO before any transformer inspection.
  • Allow adequate cooling time before physical inspection.
Diagnostic Procedure
  1. ObservationReview the event log for the exact trip temperature, sensor location, and duration of the condition before trip.
  2. MeasurementThermal-image the transformer housing/compartment during a sustained run (where safe) to confirm actual temperature and identify hot spots.
  3. MeasurementWith the unit isolated, verify the transformer tap setting against the documented circuit length/load and megger the winding insulation.
  4. MeasurementCheck the temperature sensor/RTD and its wiring for correct resistance/output against the manufacturer's reference table.
  5. ObservationInspect the transformer compartment for dust accumulation or restricted airflow.
  6. DecisionThermal imaging confirms genuine elevated temperature correlating with load/tap mismatch → transformer overload or tap misconfiguration. Thermal imaging normal but alarm persists → sensor/wiring fault. Insulation resistance below baseline → developing transformer insulation fault, escalate for transformer replacement.
  7. Fault LocationIsolate to transformer loading/tap configuration, restricted cooling, degrading insulation, or the sensor circuit.
  8. Root CauseConfirm the specific cause through direct thermal and insulation testing.
Test Points
Transformer winding temperature sensor output
Transformer housing (thermal image)
Transformer tap terminals
Winding insulation resistance
Root Cause Verification

Run the CCR at full commanded step for a sustained period after correction and confirm transformer temperature stabilizes within the normal operating range with no repeat alarm.

Corrective Action
  • Correct the transformer tap setting for the actual load.
  • Clean/restore transformer compartment airflow.
  • Replace the transformer if insulation degradation is confirmed.
  • Repair or replace the faulty sensor/RTD and wiring.
Preventive Action
  • Include transformer thermal imaging and insulation testing in the annual PM.
  • Verify tap setting whenever circuit configuration changes.
  • Keep the transformer compartment clean and ventilated.
Related References

SOP: SOP-CCR-06 (Series Circuit Loop Testing), SOP-CCR-09 (Cooling System Maintenance)

Standards: IEC 61820-3-2 (supersedes IEC 61822), IS 12290

Diagram: CCR Power Stage Schematic, Transformer Nameplate/Rating Sheet

Case Study: —

Rev 0 — Initial issue
CCR-062 CCR Door Interlock Alarm

Symptom — CCR raises a door interlock alarm — either preventing/tripping a run because a cabinet door is open or the interlock switch is faulty, or, less commonly, falsely indicating an open door while the door is actually closed and latched.

Equipment / System

CCR cabinet door interlock switch(es), interlock wiring, controller interlock input.

Possible Causes
HighCabinet door genuinely open or not fully latched
HighInterlock switch misaligned, worn, or physically damaged, failing to make contact even with the door closed
MediumInterlock switch wiring loose, broken, or corroded
MediumDoor hinge/latch mechanism worn, preventing the door from seating correctly against the switch actuator
LowerController interlock input circuit fault, ignoring or misreading a healthy switch signal
Required Tools
MultimeterContinuity testerReplacement interlock switchAlignment/adjustment toolsTorque screwdriver set
Safety Precautions
  • Never bypass or defeat a door interlock to force a start — it exists to prevent access to live high-voltage components.
  • Confirm the actual physical door/switch condition before any electrical testing.
Diagnostic Procedure
  1. ObservationPhysically inspect the door, latch, and interlock switch alignment with the door closed.
  2. MeasurementWith power isolated, check continuity across the interlock switch in both the door-open and door-closed positions.
  3. MeasurementInspect interlock wiring from the switch to the controller for looseness, damage, or corrosion.
  4. ObservationCheck for physical wear on the door hinge/latch preventing correct seating against the switch actuator.
  5. DecisionSwitch fails continuity test when door is closed → switch/alignment fault. Switch tests correctly but the controller still shows the alarm → wiring or controller input fault. Door genuinely not closing/latching → mechanical door/latch fault.
  6. Fault LocationIsolate to the interlock switch, its wiring, the controller input, or the door/latch mechanism.
  7. Root CauseConfirm the specific failed component by direct testing and physical inspection.
Test Points
Interlock switch contacts (door open/closed)
Interlock wiring continuity
Controller interlock input
Door latch/hinge alignment
Root Cause Verification

After repair, cycle the door open and closed several times and confirm the interlock reliably and correctly reflects the door state with no false alarms.

Corrective Action
  • Realign or replace the faulty interlock switch.
  • Repair the interlock wiring.
  • Adjust or repair the door hinge/latch mechanism.
  • Repair the controller interlock input if confirmed faulty.
Preventive Action
  • Include a door interlock functional test in the monthly PM.
  • Lubricate and inspect door hinges/latches periodically.
  • Keep a spare interlock switch in site stores.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist), SOP-SAFETY-03 (E-Stop Functional Test)

Standards: IEC 60204-1

Diagram: CCR Control Schematic, Cabinet Layout Drawing

Case Study: —

Rev 0 — Initial issue
CCR-063 CCR Surge Protection Alarm

Symptom — CCR raises a surge protection device (SPD) alarm/fault indication, typically showing the SPD has operated or reached end-of-life, or the SPD status monitoring circuit reports a fault.

Equipment / System

CCR input/output surge protection devices (SPDs), SPD status monitoring circuit.

Possible Causes
HighSPD has absorbed a genuine surge event (lightning-induced or switching transient) and reached end-of-life, opening its status contact
HighSPD degraded over time from repeated smaller transients, triggering an end-of-life indication
MediumSPD status monitoring wiring loose or damaged, giving a false fault indication
MediumSPD module not correctly seated/installed after a previous replacement
LowerController SPD status input circuit fault
Required Tools
MultimeterSPD manufacturer test/status referenceReplacement SPD moduleTorque screwdriver set
Safety Precautions
  • A tripped/failed SPD leaves the equipment without transient protection — treat as a priority repair rather than deferring, particularly ahead of lightning season.
  • Apply LOTO before replacing an SPD module.
  • Verify zero energy before removing an SPD, as some designs retain charge.
Diagnostic Procedure
  1. ObservationCheck the SPD's visual status indicator (if fitted) for a green/healthy or red/failed condition.
  2. MeasurementWith power isolated, verify the SPD status monitoring contact/circuit continuity.
  3. ObservationReview the site's recent lightning/surge activity or switching event history to correlate with the alarm.
  4. MeasurementConfirm the SPD module is correctly seated and its connections are secure.
  5. DecisionSPD visual indicator confirms failed/end-of-life → replace the SPD module. Indicator shows healthy but the controller still alarms → monitoring wiring/controller input fault. Loose/unseated module found → reseat and re-test.
  6. Fault LocationIsolate to the SPD module itself, its status monitoring wiring, or the controller input circuit.
  7. Root CauseConfirm the specific cause by direct inspection and testing.
Test Points
SPD visual status indicator
SPD status monitoring contact
SPD module seating/connections
Controller SPD status input
Root Cause Verification

After replacement/repair, confirm the SPD status indicates healthy and the controller alarm clears and does not recur across a monitoring period.

Corrective Action
  • Replace the failed/end-of-life SPD module with the correct manufacturer-specified type and rating.
  • Repair the status monitoring wiring.
  • Reseat a loose SPD module.
  • Repair the controller SPD status input if confirmed faulty.
Preventive Action
  • Include SPD visual/status inspection in routine PM, particularly before monsoon/lightning season.
  • Maintain SPD replacement spares in site stores.
  • Track SPD replacement history to identify sites prone to repeated surge events.
Related References

SOP: SOP-CCR-05 (Spares Management), SOP-CCR-10 (Protection Relay Calibration)

Standards: IEC 61643, IEC 62305

Diagram: CCR Control Schematic

Case Study: —

Rev 0 — Initial issue
CCR-064 CCR Internal Fault Alarm

Symptom — CCR raises a generic internal fault alarm during steady-state run (not specifically at start-up), indicating a detected fault condition within the controller or power stage that isn't mapped to one of the more specific named alarms.

Equipment / System

CCR controller and internal monitored subsystems, generic fault detection logic.

Possible Causes
HighA monitored internal parameter (voltage, current, or temperature at an internal test point) briefly excursing outside its expected range during run
HighInternal communication bus fault between controller sub-modules during operation
MediumFirmware fault/exception triggering a generic fault flag without a specific mapped cause
MediumA marginal/intermittent internal component developing a fault under sustained operating stress
LowerElectrical noise/interference affecting internal monitoring circuits
Required Tools
CCR controller diagnostic/service toolMultimeterManufacturer internal fault code referenceOscilloscope
Safety Precautions
  • Standard LV/control circuit precautions apply.
  • Do not bypass a generic internal fault alarm — it exists to flag a detected abnormal condition even if not individually named.
Diagnostic Procedure
  1. ObservationRecord the exact internal fault code/message and the time/operating condition at which it occurred.
  2. ObservationCross-reference the fault code against the manufacturer's internal fault code reference to identify the flagged subsystem.
  3. MeasurementTest the specific flagged subsystem per manufacturer guidance.
  4. MeasurementReview the controller's internal diagnostic/communication logs for correlating events.
  5. DecisionConfirmed fault in a specific flagged subsystem → component-level repair/replacement. Fault clears after a power cycle and does not recur → likely a transient/intermittent condition, monitor closely and escalate if it recurs.
  6. Fault LocationIsolate to the specific internal module/subsystem flagged by the fault code.
  7. Root CauseConfirm the specific cause through targeted subsystem testing rather than accepting a generic fault code at face value.
Test Points
As specified by the manufacturer's internal fault code reference for the flagged subsystem
Internal communication bus signals
Root Cause Verification

After remedial action, run the CCR through multiple sustained operating cycles and confirm the fault does not recur.

Corrective Action
  • Replace or repair the specific faulty internal component/module identified.
  • Reflash/update controller firmware if a firmware fault is confirmed.
  • Escalate to the manufacturer for an unresolved or recurring generic fault code.
Preventive Action
  • Keep firmware documentation and fault code references current.
  • Track recurring generic fault codes in the site failure database to catch developing problems early.
  • Include internal diagnostic log review in periodic PM.
Related References

SOP: SOP-CCR-02, SOP-CCR-06 (Repeated Fault Investigation Procedure — cross-reference CCR-015)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-065 CCR Communication Alarm

Symptom — CCR raises a communication alarm indicating loss of, or fault in, its data link to ALCMS/PLC or another monitoring system, while the CCR itself may continue operating locally.

Equipment / System

CCR communication interface (serial/Ethernet/fieldbus), ALCMS/PLC link, associated cabling and network infrastructure.

Possible Causes
HighCommunication cable disconnected, damaged, or degraded between the CCR and ALCMS/PLC
HighALCMS/PLC-side communication port, card, or software fault
MediumIncorrect communication parameters (baud rate, address, protocol settings) after a configuration change
MediumNetwork switch/media converter fault on an Ethernet-based link
LowerElectrical noise/interference on the communication cable, especially if not properly shielded/segregated from power cabling
LowerCCR-side communication interface/card hardware fault
Required Tools
MultimeterProtocol analyzer/serial monitorCable testerNetwork diagnostic tool (for Ethernet links)CCR wiring/network diagram
Safety Precautions
  • Standard LV/control circuit precautions apply.
  • Confirm the CCR's actual local run/output status independently before assuming a communication alarm reflects a broader operational fault.
Diagnostic Procedure
  1. ObservationConfirm the CCR is otherwise operating normally locally, to distinguish a communication-only fault from a broader control fault.
  2. MeasurementCheck the physical communication cable/connector at both the CCR and ALCMS/PLC ends for damage or disconnection.
  3. MeasurementVerify communication parameters (address, baud rate, protocol) match on both ends.
  4. ObservationCheck the status of intermediate network equipment (switches, media converters) on the link.
  5. MeasurementWhere possible, monitor the communication link directly for traffic/errors.
  6. DecisionPhysical cable/connector fault found → repair/replace. Parameters mismatched → correct configuration on the appropriate end. Intermediate network equipment faulty → repair/replace. Link tests healthy at the physical/protocol level but the alarm persists → CCR or ALCMS-side interface card fault.
  7. Fault LocationIsolate to the communication cable, network equipment, configuration mismatch, or an interface card at either end.
  8. Root CauseConfirm the specific cause through targeted link testing.
Test Points
CCR communication port/connector
ALCMS/PLC communication port/connector
Intermediate network equipment
Communication parameter configuration on both ends
Root Cause Verification

After repair, confirm stable, error-free communication over a sustained monitoring period and correct data exchange between the CCR and ALCMS/PLC.

Corrective Action
  • Repair or replace the damaged communication cable/connector.
  • Correct communication parameter configuration.
  • Replace faulty network equipment.
  • Replace a faulty communication interface card.
Preventive Action
  • Include communication link testing in routine PM.
  • Ensure communication cabling is properly shielded and segregated from power cabling.
  • Document and version-control communication configuration settings.
Related References

SOP: SOP-ALCMS-02, SOP-CCR-11 (Communication Link Testing)

Standards: FAA AC 150/5345-10

Diagram: CCR Control Schematic, ALCMS I/O Schedule, Network Architecture Diagram

Case Study: —

Rev 0 — Initial issue
CCR-066 CCR Fan Failure Alarm

Symptom — CCR raises a cooling fan failure alarm, indicating one or more cooling fans have stopped, are running below expected speed, or their status feedback is not confirming operation.

Equipment / System

CCR internal/cabinet cooling fan(s), fan status feedback circuit (tachometer or airflow sensor).

Possible Causes
HighFan motor failed (bearing seizure, winding failure) and stopped completely
HighFan blocked by debris/dust preventing rotation despite a healthy motor
MediumFan power supply/wiring fault, cutting power to the fan
MediumFan status feedback sensor/wiring faulty, giving a false failure indication despite the fan actually running
LowerFan speed controller (if variable-speed) fault, causing the fan to run below the threshold needed to clear the alarm
Required Tools
MultimeterClamp meterReplacement fan of correct ratingTachometer/anemometerCleaning tools
Safety Precautions
  • Apply LOTO before accessing or replacing a fan — fan blades can cause injury and internal components may remain live.
  • Allow the cabinet to cool if overtemperature is also present before extended internal work.
Diagnostic Procedure
  1. ObservationVisually/audibly confirm whether the fan is actually rotating.
  2. MeasurementWith power isolated, check fan motor winding resistance/continuity.
  3. MeasurementVerify supply voltage is present at the fan connector when commanded to run.
  4. MeasurementIf the fan appears to run normally, check the fan status feedback sensor and its wiring for a fault causing a false alarm.
  5. ObservationInspect for physical blockage/debris preventing rotation.
  6. DecisionFan not rotating with confirmed supply present → motor/mechanical fault. No supply reaching the fan → wiring/power supply fault. Fan confirmed running normally but the alarm persists → feedback sensor/wiring fault.
  7. Fault LocationIsolate to the fan motor, its power supply/wiring, or the status feedback circuit.
  8. Root CauseConfirm the specific failed component.
Test Points
Fan power supply/connector
Fan motor winding resistance
Fan status feedback sensor output
Fan mounting/blockage
Root Cause Verification

After replacement/repair, confirm the fan runs reliably and the status feedback correctly clears the alarm across a power-cycle test and a sustained run period.

Corrective Action
  • Replace the failed fan.
  • Clear a physical blockage.
  • Repair the fan power supply/wiring.
  • Repair or replace the faulty status feedback sensor.
Preventive Action
  • Include fan operation and cleaning in routine PM.
  • Track fan run-hours and replace preventively based on manufacturer MTBF data.
  • Keep spare fans in site stores.
Related References

SOP: SOP-CCR-09 (Cooling System Maintenance), SOP-CCR-05 (Spares Management)

Standards: —

Diagram: CCR Cooling System Layout

Case Study: —

Rev 0 — Initial issue
CCR-067 CCR Cooling Failure

Symptom — CCR's overall cooling system is confirmed inadequate — internal temperatures trend upward under load despite fans appearing to run, indicating a broader cooling deficiency rather than a single fan failure.

Equipment / System

CCR cabinet cooling system as a whole — fans, filters, vents, ducting, and (where fitted) heat exchanger.

Possible Causes
HighVentilation filters/vents heavily blocked with dust/debris, restricting airflow despite functioning fans
HighCabinet installed in a location with inadequate clearance for airflow, or in direct sun/high ambient without adequate mitigation
MediumFan(s) running but undersized/degraded output insufficient for the actual heat load
MediumInternal air recirculation due to a damaged or missing baffle/duct, causing hot exhaust air to be redrawn into the intake
LowerHeat exchanger (on liquid or forced-air designs) fouled or degraded, reducing heat rejection capacity
Required Tools
Thermal imaging cameraAnemometer/airflow meterCleaning toolsClamp meterManufacturer cooling system specification
Safety Precautions
  • Apply LOTO before internal inspection or cleaning.
  • Allow adequate cooling time before extended internal work following a cooling failure event.
Diagnostic Procedure
  1. ObservationConfirm all fans are individually running and check their airflow output with an anemometer.
  2. MeasurementInspect and clean/replace filters and check all vents/ducts for blockage.
  3. MeasurementThermal-image the cabinet interior during a sustained run to identify areas of poor airflow or recirculation.
  4. ObservationCheck cabinet installation clearances and exposure against manufacturer siting requirements.
  5. MeasurementIf fitted, inspect the heat exchanger for fouling or degraded performance.
  6. DecisionFans individually healthy but overall airflow low → blocked filters/vents or ducting fault. Recirculation confirmed by thermal imaging → baffle/duct repair needed. Installation clearance/siting inadequate → site modification required.
  7. Fault LocationIsolate to filters/vents, ducting/baffles, fan capacity, siting, or the heat exchanger.
  8. Root CauseConfirm the specific deficiency through airflow and thermal measurement.
Test Points
Filter/vent condition
Fan airflow output (individually)
Cabinet internal air temperature distribution (thermal image)
Installation clearances
Heat exchanger condition (if fitted)
Root Cause Verification

Run the CCR at full commanded step for a sustained period after correction and confirm internal temperatures stabilize within the normal operating range with adequate margin.

Corrective Action
  • Clean/replace filters and clear blocked vents/ducts.
  • Repair or install baffles to prevent recirculation.
  • Improve cabinet siting/clearance per manufacturer requirements.
  • Clean or repair the heat exchanger.
  • Upgrade fan capacity if confirmed undersized.
Preventive Action
  • Include a comprehensive cooling system inspection (not just fan check) in the PM programme.
  • Review siting during any relocation or nearby construction.
  • Trend internal temperature over time to catch gradual cooling degradation.
Related References

SOP: SOP-CCR-09 (Cooling System Maintenance)

Standards: IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Cooling System Layout, Cabinet Installation Drawing

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-068 CCR Protection Relay Failure

Symptom — A specific CCR protection relay (earth fault, overcurrent, overvoltage, etc.) is confirmed to have failed — either failing to trip under a genuine fault condition, or tripping/latching with no measurable fault present and not responding correctly to reset or test.

Equipment / System

CCR protection relay(s) — electromechanical or electronic — and their associated sensors/wiring.

Possible Causes
HighInternal relay electronic/mechanical failure — component degradation or a failed output contact
HighRelay firmware/configuration corrupted, causing incorrect trip behaviour
MediumRelay power supply fault, causing erratic or no operation
MediumInput sensor (CT, VT, or transducer) feeding the relay has failed, causing the relay to act on incorrect data
LowerRelay test/reset function itself faulty, masking an otherwise healthy relay
Required Tools
Relay test set (secondary injection where available)MultimeterManufacturer relay test procedureCCR configuration/parameter tool
Safety Precautions
  • A relay that fails to trip under a genuine fault is a serious safety risk — treat any confirmed relay malfunction as high priority.
  • Apply LOTO before relay testing or replacement.
  • Do not rely on a suspect relay to protect personnel during other testing.
Diagnostic Procedure
  1. ObservationDocument the specific relay function affected and the exact nature of the malfunction (fails to trip, false trip, fails to reset).
  2. MeasurementPerform a manufacturer-specified functional/injection test on the relay to confirm actual trip behaviour against its rated setpoint.
  3. MeasurementVerify the relay's input sensor (CT/VT/transducer) is providing correct, healthy signals.
  4. MeasurementCheck the relay's power supply and configuration/firmware against the commissioned baseline.
  5. DecisionRelay fails a proper functional/injection test → confirmed relay fault, replace. Relay passes functional test but the field symptom persists → input sensor or wiring fault, not the relay itself. Configuration found altered from baseline → correct configuration and re-test.
  6. Fault LocationIsolate to the relay itself, its input sensor, its power supply, or its configuration.
  7. Root CauseConfirm the specific cause through direct functional testing rather than assumption.
Test Points
Relay trip output under injected test condition
Relay input sensor (CT/VT/transducer) signal
Relay power supply
Relay configuration/firmware version
Root Cause Verification

After replacement/repair, perform a full functional/injection test confirming correct trip and reset behaviour at the rated setpoint before returning the CCR to service.

Corrective Action
  • Replace the failed protection relay.
  • Repair the relay power supply.
  • Replace the faulty input sensor.
  • Restore relay configuration to the commissioned baseline.
Preventive Action
  • Include protection relay functional/injection testing in the annual PM — do not rely solely on the absence of trips as confirmation of health.
  • Lock relay configuration after commissioning and log any authorized changes.
  • Maintain relay test records for trending.
Related References

SOP: SOP-CCR-10 (Protection Relay Calibration)

Standards: IEC 60255

Diagram: CCR Protection Schematic

Case Study: —

Rev 0 — Initial issue
CCR-069 False CCR Alarm

Symptom — CCR displays an active alarm (of any protection type) with no corresponding real-world fault condition found on thorough investigation — the alarm does not correlate with any measurable abnormal parameter.

Equipment / System

CCR alarm/protection logic broadly — sensors, wiring, and controller logic across all protection functions.

Possible Causes
HighA specific sensor (current, voltage, temperature, etc.) has drifted out of calibration, reporting an incorrect value that crosses the alarm threshold
HighSensor wiring loose, corroded, or picking up electrical noise, producing spurious readings
MediumAlarm threshold set too tight relative to normal operating variation, causing legitimate but nuisance trips
MediumController software/firmware bug misinterpreting a healthy signal as a fault condition
LowerElectromagnetic interference from nearby equipment affecting sensor or signal wiring
Required Tools
Calibrated reference meter/instrument matching the alarmed parameterOscilloscopeMultimeterCCR configuration/parameter toolManufacturer alarm code reference
Safety Precautions
  • Do not simply mask or disable an alarm believed to be false without confirming this through proper investigation — a genuinely intermittent real fault can mimic a false alarm.
  • Apply LOTO before sensor/wiring inspection.
Diagnostic Procedure
  1. ObservationIdentify the specific alarm raised and the exact parameter/threshold that triggered it, from the event log.
  2. MeasurementIndependently and simultaneously measure the actual parameter (voltage, current, temperature, etc.) using a calibrated reference instrument at the same point the sensor monitors.
  3. MeasurementInspect the relevant sensor wiring for looseness, corrosion, or routing near noise sources.
  4. ObservationReview whether the alarm threshold is appropriately set relative to the site's normal operating variation, per manufacturer guidance.
  5. DecisionIndependent measurement confirms the parameter was genuinely at the alarmed value → not a false alarm, investigate as a real fault per the relevant specific topic. Independent measurement shows the parameter was normal → confirmed false alarm, proceed to isolate sensor/wiring/threshold/firmware cause.
  6. Fault LocationIsolate to the specific sensor, its wiring, the alarm threshold configuration, or a controller firmware issue.
  7. Root CauseConfirm the specific cause through calibrated comparative measurement — never conclude "false alarm" without independent verification.
Test Points
The specific sensor relevant to the alarmed parameter
Sensor wiring at both ends
Alarm threshold configuration
Controller firmware version
Root Cause Verification

After correction, monitor the CCR through a representative operating period and confirm the specific alarm does not recur while genuine fault detection remains intact (verified by controlled test if appropriate).

Corrective Action
  • Recalibrate or replace the drifted sensor.
  • Repair the sensor wiring.
  • Adjust the threshold only within manufacturer-approved limits with documented justification.
  • Update controller firmware if a software bug is confirmed by the manufacturer.
Preventive Action
  • Include sensor calibration checks across all protection functions in the annual PM.
  • Document threshold settings and require change control for any adjustment.
  • Investigate every alarm occurrence — do not develop a habit of dismissing alarms as "probably false."
Related References

SOP: SOP-CCR-10 (Protection Relay Calibration)

Standards: —

Diagram: CCR Protection Schematic

Case Study: Division 23 — Root Cause Analysis

Rev 0 — Initial issue
CCR-070 Repeated CCR Protection Trip

Symptom — The CCR trips repeatedly on the same or varying protection alarms over multiple operating cycles, rather than a single isolated trip event, indicating either an unresolved underlying fault or a genuinely intermittent condition.

Equipment / System

CCR, all protection subsystems — investigation spans the full protection and alarm chain.

Possible Causes
HighAn underlying cause from a specific protection topic (CCR-056 through CCR-069) that has only been reset, not actually resolved
HighA genuinely intermittent fault — loose connection or marginal component — that passes isolated testing between trips
MediumA protection threshold set too tight for the equipment's normal operating envelope, causing repeated nuisance trips under otherwise healthy conditions
MediumA developing/degrading component (transformer, bridge device, sensor) that fails progressively under load, triggering different alarms at different times
LowerOperator repeatedly resetting and restarting without allowing proper investigation between trips
Required Tools
MultimeterData logger for trend/repeated-event analysisCCR event log export toolRelay test set
Safety Precautions
  • Repeated forced resets against an unresolved protection trip can cause component damage or create a genuine safety hazard — do not simply keep resetting and retrying without investigation.
Diagnostic Procedure
  1. ObservationExport and review the CCR event/alarm log across all recent trips to determine whether the same specific alarm recurs each time or different alarms occur.
  2. DecisionSame specific alarm repeats → treat as that topic's fault not yet fully resolved; re-open the relevant investigation with more rigorous root cause verification. Different alarms occur at different times → suspect a common underlying cause (e.g. a marginal power supply or cooling deficiency) affecting multiple protection functions, or a genuinely intermittent condition per Division 22 methodology.
  3. MeasurementWhere an intermittent connection is suspected, perform a wiggle test — with power isolated — on suspect connectors/terminals while monitoring continuity.
  4. MeasurementReview whether protection thresholds are set appropriately relative to the equipment's normal operating envelope, per manufacturer guidance.
  5. Root CauseConfirm root cause with a sustained multi-cycle test under representative load conditions rather than a single successful run.
Test Points
As per the specific recurring alarm(s) identified in the event log
Root Cause Verification

Require a minimum of five consecutive successful full-load operating cycles, including under realistic field conditions, before closing out.

Corrective Action
  • Apply the specific recurring alarm's corrective action, with emphasis on thorough root cause verification rather than a quick reset.
  • Address a common underlying cause if multiple alarms trace back to one root issue.
Preventive Action
  • Make event log review a standing part of any repeated-trip investigation.
  • Track recurring alarm patterns in the site failure database.
  • Review protection threshold settings periodically against actual operating data.
Related References

SOP: SOP-CCR-06 (Repeated Fault Investigation Procedure)

Standards: —

Diagram: —

Case Study: Division 23 — Root Cause Analysis; Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue

05 · CCR Cooling & Internal Components

10 of 10 topics published
CCR-071 CCR Cooling Fan Not Working

Symptom — One or more internal cooling fans in the CCR cabinet fail to run when the unit is powered and under load, with no airflow detected at the fan outlet despite the fan being commanded on (continuously or via thermostatic control).

Equipment / System

CCR cabinet cooling fan(s), fan power supply/wiring, fan thermostat or controller-driven fan relay, heat sink and power electronics compartment.

Possible Causes
HighFan motor winding failure or seized bearing, preventing rotation even with supply present
HighBlown fan fuse or tripped fan circuit protection isolating fan supply
MediumFailed fan relay, thermostat switch, or controller output driving the fan
MediumBroken or disconnected fan power wiring/connector
LowerFan blade mechanically jammed by a foreign object or debris despite the motor being intact
Required Tools
True-RMS digital multimeterClamp meterInsulated screwdriver setFan power wiring diagramTachometer (optional)
Safety Precautions
  • Isolate and LOTO the CCR before opening the cabinet or reaching near the fan blade guard.
  • Allow the heat sink and power electronics to cool before close inspection, as surfaces may remain hot after shutdown.
  • Do not bypass fan protection or run the CCR at full load with cooling disabled to "test" — this risks thermal damage to the power stage.
Diagnostic Procedure
  1. ObservationVisually and audibly confirm which fan(s) are not running while the unit is powered and commanded to cool.
  2. MeasurementWith power isolated and verified dead, check the fan circuit fuse/breaker for continuity.
  3. MeasurementRestore power under controlled conditions and measure voltage at the fan connector terminals when the fan is commanded on.
  4. DecisionCorrect voltage present at the fan terminals but fan does not spin → fan motor/bearing fault. No voltage at the fan terminals → upstream relay, thermostat, wiring, or fuse fault.
  5. MeasurementIf voltage is absent, trace back through the fan relay/thermostat/controller output to locate the point where the command signal or supply is lost.
  6. Fault LocationIsolate to the specific fan motor, fan fuse, relay/thermostat, or wiring segment.
  7. Root CauseConfirm the failed component by isolated bench or in-circuit testing before replacement.
Test Points
Fan connector supply voltage
Fan circuit fuse/breaker continuity
Fan relay/thermostat output
Fan motor winding resistance
Root Cause Verification

After replacement/repair, confirm the fan runs continuously (or cycles correctly under thermostatic control) through a full load cycle, and verify airflow is present at the outlet.

Corrective Action
  • Replace the failed fan motor assembly.
  • Replace the blown fan fuse with the correct rating and type — do not upsize.
  • Replace the faulty relay, thermostat, or repair the controller output circuit.
  • Repair or replace damaged fan wiring/connector.
  • Clear any mechanical obstruction from the fan blade.
Preventive Action
  • Include a functional fan check (visual/audible run and airflow) in the routine PM schedule.
  • Track fan run-hours and replace preventively based on manufacturer service life.
  • Keep the cabinet interior clean to reduce the risk of debris jamming the fan.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: CCR Cooling Fan Wiring Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-072 CCR Fan Running Continuously

Symptom — The CCR cooling fan(s) run continuously at full speed regardless of load or internal temperature, including at start-up and low intensity steps when cooling demand should be minimal.

Equipment / System

CCR cabinet cooling fan(s), thermostat/temperature sensor, fan controller logic or relay.

Possible Causes
HighFan thermostat or temperature sensor stuck closed/failed, reporting a permanently high temperature
MediumFan relay contacts welded/stuck in the energized position
MediumController configured or defaulted to continuous-fan mode rather than thermostatic control
LowerGenuine elevated internal temperature due to a separate cooling deficiency (blocked filter/vents), causing the thermostat to correctly hold the fan on
Required Tools
True-RMS multimeterCalibrated reference temperature probeCCR configuration/parameter toolFan wiring diagram
Safety Precautions
  • Apply LOTO before inspecting the thermostat, relay, or wiring inside the cabinet.
  • Do not disable the fan or force it off to "test" without first ruling out a genuine overtemperature condition.
Diagnostic Procedure
  1. ObservationConfirm the fan runs continuously across a range of load/intensity conditions, not only under genuinely high ambient or internal temperature.
  2. MeasurementIndependently measure internal cabinet/heat sink temperature with a calibrated reference probe and compare against the thermostat's reported/trip value.
  3. DecisionIndependent measurement confirms genuinely elevated temperature → investigate as a cooling deficiency (see CCR-074/075/076/077). Independent measurement shows normal temperature → thermostat/sensor, relay, or configuration fault.
  4. MeasurementIf temperature is normal, check thermostat/sensor continuity and calibration against manufacturer reference values.
  5. MeasurementCheck fan relay contacts for welding by removing the control signal and confirming the fan de-energizes.
  6. ObservationReview the controller configuration/parameter settings for fan operating mode (thermostatic vs continuous).
  7. Fault LocationIsolate to the thermostat/sensor, the relay, or an incorrect configuration setting.
  8. Root CauseConfirm the specific failed or misconfigured component.
Test Points
Internal cabinet/heat sink temperature (reference measurement)
Thermostat/sensor continuity and setpoint
Fan relay contact state with signal removed
Fan operating mode configuration parameter
Root Cause Verification

After correction, confirm the fan cycles appropriately with internal temperature across at least one full representative operating period, including low-load conditions.

Corrective Action
  • Replace the failed thermostat/temperature sensor.
  • Replace the fan relay if contacts are welded or degraded.
  • Correct the controller configuration to the manufacturer-specified fan control mode.
  • If a genuine cooling deficiency is found, address the underlying blockage/ventilation fault.
Preventive Action
  • Include thermostat/sensor calibration checks in the annual PM.
  • Document fan control configuration and include it in commissioning/handover records.
  • Monitor fan run-hours to flag abnormal continuous operation trends early.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: CCR Cooling Fan Wiring Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-073 CCR Fan Starting Intermittently

Symptom — The CCR cooling fan starts and stops erratically, cycles on and off rapidly, or only runs intermittently rather than starting reliably and running continuously/thermostatically as designed.

Equipment / System

CCR cabinet cooling fan, fan motor, thermostat/sensor, relay, and associated wiring/connectors.

Possible Causes
HighLoose or corroded fan power connector/terminal causing an intermittent circuit
HighDegrading fan motor bearing or winding causing intermittent starting under load
MediumMarginal or fluttering thermostat/relay contact repeatedly making and breaking near its setpoint
MediumFan capacitor (for capacitor-start motors) degrading, causing inconsistent starts
LowerVibration-induced intermittent connection at a poorly secured wiring run
Required Tools
True-RMS multimeterData logger for trend/repeated-event analysisInsulated screwdriver setFan wiring diagram
Safety Precautions
  • Apply LOTO before performing any wiggle test or connector inspection with power isolated.
  • Do not attempt to diagnose intermittent faults by touching live fan wiring while energized.
Diagnostic Procedure
  1. ObservationLog the pattern of fan starts/stops over a representative period to characterise the intermittency (random vs. load-related vs. temperature-related).
  2. MeasurementWith power isolated, perform a wiggle test on the fan power connector and wiring while monitoring continuity.
  3. MeasurementInspect and clean/tighten the fan connector and terminals, checking for corrosion or looseness.
  4. MeasurementCheck the thermostat/relay contact behaviour near its setpoint for contact flutter.
  5. MeasurementIf fitted, check the fan run/start capacitor's capacitance against its rated value.
  6. DecisionWiggle test reveals an intermittent connection → wiring/connector fault. Connector and wiring sound but fan still starts intermittently → motor bearing/winding or capacitor degradation.
  7. Fault LocationIsolate to the specific connector, wiring segment, thermostat/relay, or fan motor/capacitor.
  8. Root CauseConfirm the intermittent fault by reproducing it under controlled conditions where possible.
Test Points
Fan power connector/terminals (wiggle test)
Thermostat/relay contact behaviour at setpoint
Fan start/run capacitor (if fitted)
Fan motor winding resistance
Root Cause Verification

After repair, monitor fan operation through a sustained multi-cycle period and confirm consistent, reliable starting with no recurrence of intermittency.

Corrective Action
  • Clean, tighten, or replace the fan connector/terminals.
  • Repair or re-secure fan wiring found to be loose or vibration-damaged.
  • Replace the fan motor or start/run capacitor if degraded.
  • Replace the thermostat/relay if contact flutter is confirmed.
Preventive Action
  • Include connector/terminal tightness checks in the fan inspection PM.
  • Secure fan wiring against vibration during maintenance.
  • Track intermittent-fault occurrences in the site failure database to catch developing patterns early.
Related References

SOP: SOP-CCR-06 (Repeated Fault Investigation Procedure), SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: CCR Cooling Fan Wiring Diagram

Case Study: Division 22 — Intermittent Fault Methodology; Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
CCR-074 CCR Heat Sink Overheating

Symptom — The heat sink for the CCR power stage (thyristor/IGBT bridge) reaches an abnormally high temperature under normal load, triggering a thermal alarm or reducing output, even though ambient cabinet conditions appear otherwise normal.

Equipment / System

CCR power stage heat sink, thermal sensor, cooling fan and airflow path directly over the heat sink.

Possible Causes
HighHeat sink fins clogged with dust/debris, reducing surface area available for heat dissipation
HighCooling fan airflow not reaching the heat sink due to blockage or fan fault upstream
MediumDegraded thermal interface (paste/pad) between the power device and heat sink, increasing thermal resistance
MediumPower device (thyristor/IGBT) itself degrading and dissipating more heat than normal for the same load
LowerThermal sensor drifted, reporting a falsely high temperature
Required Tools
Infrared thermometer/thermal cameraTrue-RMS clamp meterCalibrated reference temperature probeCCR configuration/parameter tool
Safety Precautions
  • Apply LOTO and allow the heat sink to cool before physical inspection or cleaning.
  • Do not touch the heat sink or power devices during or immediately after operation — surfaces can cause burns.
Diagnostic Procedure
  1. ObservationRecord the alarm/trip temperature and load conditions at the time of the event from the event log.
  2. MeasurementWith the unit isolated and cooled, visually inspect the heat sink fins for dust/debris accumulation.
  3. MeasurementConfirm cooling fan airflow is reaching the heat sink directly (see CCR-071/072/073/076/077 if fan or blockage is suspected).
  4. MeasurementUnder controlled load, use an infrared thermometer/thermal camera to compare temperature across the heat sink and at the power device mounting point.
  5. MeasurementIndependently verify the thermal sensor reading against the reference measurement.
  6. DecisionHeat sink clean and airflow confirmed but power device mounting point runs hot → thermal interface or power device fault. Heat sink dirty/blocked → cleaning required. Sensor reading disagrees with reference → sensor fault.
  7. Fault LocationIsolate to heat sink fouling, airflow restriction, thermal interface degradation, power device fault, or sensor fault.
  8. Root CauseConfirm the specific cause by resolving it and re-measuring under representative load.
Test Points
Heat sink fin surface temperature (thermal imaging)
Power device mounting point temperature
Airflow at the heat sink
Thermal sensor reading vs. reference
Root Cause Verification

After correction, run the CCR at full load and confirm heat sink temperature remains within manufacturer limits over a sustained operating period with no repeat alarm.

Corrective Action
  • Clean the heat sink fins of dust/debris using appropriate methods (compressed air, brush) with power isolated.
  • Resolve any upstream airflow restriction or fan fault.
  • Reapply thermal interface material at the power device mounting.
  • Replace the degraded power device (thyristor/IGBT) if confirmed faulty.
  • Recalibrate or replace the thermal sensor.
Preventive Action
  • Include heat sink cleaning in the scheduled PM, at a frequency matched to the site's dust environment.
  • Trend heat sink temperature under comparable load conditions to catch gradual degradation early.
  • Verify thermal sensor calibration during scheduled maintenance.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection), SOP-CCR-10 (Protection Relay Calibration)

Standards: IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-075 CCR Cabinet Overheating

Symptom — Overall internal cabinet temperature runs abnormally high, triggering a general cabinet overtemperature alarm, even though individual components (heat sink, fan) may test normally in isolation.

Equipment / System

CCR cabinet enclosure, cabinet temperature sensor, ventilation path, and all internal heat-generating components collectively.

Possible Causes
HighCombined restricted ventilation/filter blockage reducing overall airflow through the cabinet
HighElevated ambient temperature at the equipment shelter/room beyond the CCR's rated operating envelope
MediumMultiple internal components each running slightly hot, cumulatively raising cabinet temperature
MediumCabinet door/panel left open or improperly sealed, disrupting the designed airflow path
LowerCabinet temperature sensor miscalibrated or poorly located, reading unrepresentatively high
Required Tools
Calibrated reference temperature probeInfrared thermometer/thermal cameraAnemometer (airflow measurement)CCR configuration/parameter tool
Safety Precautions
  • Apply LOTO before internal inspection.
  • Allow the cabinet to cool before extended internal work to avoid heat-related injury.
Diagnostic Procedure
  1. ObservationRecord the cabinet overtemperature alarm value and correlate with ambient shelter/room temperature and recent load history.
  2. MeasurementIndependently measure ambient temperature at the equipment shelter/room and compare against the CCR's rated operating range.
  3. MeasurementConfirm all cabinet doors/panels are correctly closed and sealed per design, and inspect for airflow bypass paths.
  4. MeasurementCheck ventilation/filter condition and airflow rate through the cabinet (see CCR-076/077 if blockage suspected).
  5. MeasurementWith individual components tested normal, use thermal imaging to identify any localized hotspot contributing to overall rise.
  6. DecisionAmbient temperature at/above rated limit → environmental cause, review shelter cooling/ventilation. Ventilation/filter restricted → blockage fault. Individual components normal, no external cause found → sensor/location fault.
  7. Fault LocationIsolate to environmental conditions, ventilation restriction, door/panel sealing, or the cabinet temperature sensor.
  8. Root CauseConfirm the primary contributing factor(s) through resolution and re-measurement.
Test Points
Ambient shelter/room temperature
Cabinet internal airflow rate
Door/panel seal integrity
Cabinet temperature sensor reading vs. reference
Root Cause Verification

After correction, monitor cabinet temperature across a full daily/load cycle, including peak ambient conditions, and confirm it remains within the manufacturer's rated envelope.

Corrective Action
  • Resolve ventilation/filter restriction (clean or replace filters, clear blocked vents).
  • Improve equipment shelter cooling/ventilation if ambient temperature exceeds the rated envelope.
  • Repair or replace door/panel seals to restore the designed airflow path.
  • Recalibrate or relocate the cabinet temperature sensor if confirmed unrepresentative.
Preventive Action
  • Include shelter ambient temperature checks alongside CCR PM.
  • Trend cabinet temperature against ambient and load to catch gradual degradation.
  • Confirm door/panel seals during scheduled maintenance.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection)

Standards: IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Cabinet Ventilation Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-076 CCR Ventilation Blockage

Symptom — Airflow through the CCR cabinet's ventilation openings (intake/exhaust louvres, vents, or ducting) is restricted or absent, reducing overall cooling effectiveness despite the fan running correctly.

Equipment / System

CCR cabinet ventilation openings, louvres, vent grilles, and any associated ducting.

Possible Causes
HighExternal vent/louvre blocked by debris, vegetation, snow, or nesting material
HighInternal ductwork or vent path obstructed by dust build-up or a dislodged component
MediumVent grille physically damaged or incorrectly reinstalled after prior maintenance, restricting the opening
MediumEquipment shelter/cabinet positioned or modified such that the vent path is partially obstructed by nearby equipment or structure
LowerFan operating correctly but rotated/ducted in the wrong orientation after a prior fan replacement
Required Tools
Anemometer (airflow measurement)Flashlight/inspection mirrorInsulated screwdriver setCCR cabinet ventilation diagram
Safety Precautions
  • Apply LOTO before physically inspecting or clearing any ventilation path near the fan or power electronics.
  • Be alert for pests or nesting material when clearing external vents.
Diagnostic Procedure
  1. ObservationConfirm the fan is running correctly (see CCR-071) to isolate the fault to the ventilation path rather than the fan itself.
  2. MeasurementMeasure airflow at the intake and exhaust vents with an anemometer and compare against the manufacturer's rated airflow.
  3. ObservationVisually inspect external vents/louvres for debris, vegetation, snow, or nesting material.
  4. ObservationVisually inspect internal ducting/vent path for dust build-up or a dislodged/misaligned component.
  5. DecisionLow airflow with a visible external obstruction → clear the blockage. Low airflow with no visible external obstruction → inspect internal duct path and grille orientation/fitment.
  6. Fault LocationIsolate to the specific external vent, internal duct section, or grille.
  7. Root CauseConfirm restored airflow meets rated value once the obstruction is cleared.
Test Points
Intake vent airflow rate
Exhaust vent airflow rate
External louvre condition
Internal duct path condition
Root Cause Verification

After clearing the blockage, re-measure airflow at intake and exhaust and confirm it meets the manufacturer's rated value; monitor cabinet/heat sink temperature through a full load cycle to confirm effective cooling is restored.

Corrective Action
  • Clear debris, vegetation, snow, or nesting material from external vents/louvres.
  • Clean or clear internal ductwork/vent path.
  • Repair or correctly reinstall a damaged or misaligned vent grille.
  • Relocate or modify obstructing nearby equipment/structure where feasible.
Preventive Action
  • Include external vent inspection and clearing in the routine PM, especially before seasons prone to debris or nesting.
  • Install or maintain vent screens to reduce debris/pest ingress without restricting airflow.
  • Verify airflow rate periodically as part of the cooling system PM.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: CCR Cabinet Ventilation Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-077 CCR Filter Blockage

Symptom — The CCR's intake air filter (where fitted) is significantly clogged, reducing airflow into the cabinet and contributing to elevated internal temperature, despite the fan and ventilation openings being otherwise functional.

Equipment / System

CCR cabinet intake air filter/filter media, filter housing/frame.

Possible Causes
HighFilter media saturated with dust/particulate beyond its rated service interval
MediumFilter installed with incorrect orientation or an incorrect/non-standard replacement filter restricting airflow
MediumUnusually high ambient dust/particulate environment accelerating filter loading beyond the normal PM interval
LowerFilter frame/housing damaged or poorly seated, allowing bypass airflow that reduces effective filtration without necessarily reducing total airflow
Required Tools
Anemometer (airflow measurement)Flashlight/inspection mirrorReplacement filter media (correct manufacturer type)
Safety Precautions
  • Apply LOTO before opening the filter housing or accessing the intake path.
  • Use appropriate respiratory PPE when handling heavily loaded filters, particularly in high-dust environments.
Diagnostic Procedure
  1. ObservationVisually inspect the filter media for visible dust loading/discolouration and compare against a clean reference filter.
  2. MeasurementMeasure intake airflow with the filter in place and compare against the manufacturer's rated airflow for a clean filter.
  3. ObservationConfirm the filter is the correct manufacturer-specified type and is correctly oriented and seated in its housing.
  4. MeasurementWith the filter removed, re-measure airflow to confirm whether the filter itself is the primary restriction.
  5. DecisionAirflow improves significantly with the filter removed → filter loading confirmed as the primary restriction. Airflow remains low with the filter removed → investigate ventilation path or fan (CCR-071/076).
  6. Fault LocationIsolate to filter loading, incorrect filter type/fitment, or a damaged housing/seal.
  7. Root CauseConfirm restored airflow meets rated value once the filter is replaced and correctly seated.
Test Points
Intake airflow with filter installed
Intake airflow with filter removed
Filter media visual condition
Filter type/orientation vs. manufacturer specification
Root Cause Verification

After replacement, re-measure intake airflow and confirm it meets the manufacturer's rated value; monitor cabinet/heat sink temperature through a full load cycle to confirm effective cooling is restored.

Corrective Action
  • Replace the filter media with the correct manufacturer-specified type.
  • Correct the filter orientation/fitment or repair the housing seal.
  • Adjust the filter replacement interval to match the site's actual dust environment where it exceeds the standard PM assumption.
Preventive Action
  • Include filter inspection and replacement in the routine PM at a frequency matched to the site's dust environment.
  • Stock the correct manufacturer-specified filter type to avoid substitution with an incorrect part.
  • Log filter replacement dates to track loading trends over time.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: CCR Cabinet Ventilation Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-078 CCR Internal Dust Accumulation

Symptom — Significant dust/particulate build-up is found on internal components (PCBs, terminals, heat sink, contactors) during inspection, raising the risk of overheating, tracking/insulation faults, or intermittent contact issues, even where no active alarm is currently present.

Equipment / System

CCR cabinet interior generally — control board, terminals, contactors, heat sink, and other internal surfaces.

Possible Causes
HighFilter blockage or degraded filtration allowing unfiltered air and particulate into the cabinet over time (see CCR-077)
HighCabinet seals (door, cable entries, panel joints) degraded or improperly closed, allowing dust ingress bypassing the filtered path
MediumHigh ambient dust/particulate environment at the site exceeding the cabinet's rated ingress protection under normal operating conditions
MediumExtended interval since last internal cleaning relative to the site's dust environment
LowerDust generated internally by a degrading component (e.g. arcing contactor, overheating insulation)
Required Tools
Flashlight/inspection mirrorAnti-static compressed air / ESD-safe vacuumInsulation resistance tester (500V/1000V)PPE (respiratory, eye protection)
Safety Precautions
  • Apply LOTO before opening the cabinet for cleaning or inspection.
  • Use anti-static/ESD-safe cleaning methods to avoid damaging sensitive control board components.
  • Use appropriate respiratory and eye PPE when cleaning heavily loaded interiors.
  • Do not use standard (non-ESD-safe) compressed air or ungrounded vacuum equipment directly on control boards.
Diagnostic Procedure
  1. ObservationDocument the extent and location of dust accumulation during inspection, noting any components with unusually heavy build-up.
  2. MeasurementCheck the intake filter and cabinet seals (door, cable entries, panel joints) for degradation or improper closure allowing unfiltered ingress.
  3. MeasurementWhere dust is present near current-carrying terminals or the control board, perform an insulation resistance check to rule out tracking risk.
  4. ObservationInspect for any localized source of internally generated dust/debris, such as an arcing contactor or degrading insulation.
  5. DecisionIngress traced to filter/seal degradation → address the ingress path (see CCR-077 or reseal). No clear ingress path found and dust localized near one component → investigate that component as a possible internal source.
  6. Fault LocationIsolate to the specific ingress path or internally generated source.
  7. Root CauseConfirm the accumulation rate is consistent with the identified cause by comparing against the last recorded cleaning/inspection interval.
Test Points
Cabinet seal integrity (door, cable entries, panel joints)
Filter condition
Insulation resistance near affected terminals/board
Suspected internal dust source component
Root Cause Verification

After cleaning and addressing the ingress path, re-inspect at the next scheduled interval and confirm the accumulation rate has reduced to expected levels for the site's dust environment.

Corrective Action
  • Clean internal components using anti-static/ESD-safe methods appropriate to each component type.
  • Repair or replace degraded cabinet seals.
  • Address the filter condition per CCR-077 if filtration is the ingress path.
  • Replace or repair any internally degrading component identified as a dust source.
Preventive Action
  • Set an internal cleaning interval matched to the site's actual dust environment, not a generic default.
  • Include cabinet seal inspection in the routine PM.
  • Photograph internal condition at each PM visit to trend accumulation over time.
Related References

SOP: SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: —

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-079 CCR Control Board Failure

Symptom — The CCR control board (PLC/controller logic board) exhibits erratic behaviour, fails to boot, loses configuration, or stops responding entirely, with symptoms not attributable to a single sensor, relay, or power stage fault.

Equipment / System

CCR control/controller board (PLC or dedicated logic board), its power supply feed, and associated I/O terminals.

Possible Causes
HighControl board component failure (e.g. degraded capacitor, damaged I/O driver) from age, heat, or a transient surge event
HighControl board power supply feed out of tolerance, causing unstable board operation
MediumCorrupted firmware/configuration from an incomplete update or unexpected power loss during a write cycle
MediumMoisture or dust contamination on the board causing intermittent shorts or leakage paths
LowerA connected field device or wiring fault back-feeding an out-of-range signal into a board input, damaging that input
Required Tools
True-RMS multimeterOscilloscopeManufacturer diagnostic/configuration toolFirmware/configuration backup mediaESD-safe handling equipment
Safety Precautions
  • Apply LOTO before removing or handling the control board.
  • Use proper ESD precautions (wrist strap, ESD mat) when handling the board to avoid further damage.
  • Confirm board power is fully discharged before removal, per manufacturer procedure.
Diagnostic Procedure
  1. ObservationDocument the exact symptom (fails to boot, erratic behaviour, lost configuration, unresponsive) and any error/status LEDs or codes.
  2. MeasurementWith power isolated and verified dead, inspect the board visually for obvious damage, discolouration, bulging capacitors, or contamination.
  3. MeasurementRestore power under controlled conditions and measure the board's incoming power supply voltage against the manufacturer's tolerance.
  4. DecisionBoard power supply out of tolerance → investigate the upstream power supply (see CCR-006 series) rather than the board itself. Board power supply within tolerance but board still faulty → board-level hardware or firmware fault.
  5. MeasurementWhere possible, attempt to reload firmware/configuration from a known-good backup per manufacturer procedure.
  6. DecisionBoard recovers after firmware/configuration reload → corrupted firmware/configuration was the cause. Board does not recover → hardware fault, proceed to board replacement.
  7. Fault LocationIsolate to the control board hardware, its power supply feed, or corrupted firmware/configuration.
  8. Root CauseConfirm the specific failure mode before replacement or reconfiguration is finalised.
Test Points
Control board incoming power supply voltage
Board status/error LEDs or codes
Firmware/configuration integrity
Board I/O terminals for signs of overvoltage damage
Root Cause Verification

After replacement or firmware/configuration restoration, confirm the CCR boots correctly, retains configuration through a power cycle, and operates through a full representative load cycle with no recurrence.

Corrective Action
  • Replace the failed control board with a like-for-like spare.
  • Reload firmware/configuration from a verified backup, or reconfigure per manufacturer defaults if no backup exists.
  • Correct the upstream control power supply if found out of tolerance.
  • Clean and re-protect the board enclosure if contamination is confirmed as a contributing factor.
Preventive Action
  • Maintain a current, verified firmware/configuration backup for each CCR controller (cross-reference CCR-001).
  • Include a control board power supply voltage check in the PM schedule.
  • Protect the board compartment from moisture/dust ingress per CCR-078 findings.
  • Keep a spare control board on site or readily available given its criticality to CCR operation.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist), SOP-CCR-11 (CCR Cooling System Inspection)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-080 CCR Power Electronics Failure

Symptom — A power electronics component in the CCR bridge (thyristor, IGBT, diode, or associated snubber/gate drive circuitry) fails, resulting in loss of output, abnormal waveform, a protection trip, or visible component damage.

Equipment / System

CCR power stage bridge — thyristor/IGBT modules, diodes, snubber circuits, and gate/base drive electronics.

Possible Causes
HighA specific power device (thyristor/IGBT/diode) has failed short or open, from age, thermal stress, or a transient overvoltage event
HighGate/base drive circuit fault preventing correct firing/switching of an otherwise healthy device
MediumSnubber circuit component (resistor/capacitor) failed, exposing the power device to excessive switching stress
MediumSustained overheating (see CCR-074) accelerating power device degradation
LowerA transient surge or lightning-induced event damaging one or more devices despite surge protection
Required Tools
True-RMS multimeter (with diode/semiconductor test function)OscilloscopeInsulation resistance testerManufacturer power stage test procedureESD-safe handling equipment
Safety Precautions
  • Apply LOTO and verify all capacitors in the power stage are fully discharged before touching any bridge component — stored energy can persist after isolation.
  • Treat all power stage terminals as live until proven de-energized with a tested meter.
  • Follow the two-person rule for HV isolation per site electrical safety procedure.
Diagnostic Procedure
  1. ObservationRecord the exact fault symptom (loss of output, abnormal waveform, protection trip, visible damage) and any associated alarm code from the event log.
  2. ObservationWith power fully isolated and verified dead, visually inspect the bridge for signs of visible damage — scorching, cracked casing, blown fuses.
  3. MeasurementTest each power device (thyristor/IGBT/diode) individually using the multimeter's semiconductor test function or manufacturer-specified in-circuit/out-of-circuit test method.
  4. MeasurementInspect and test snubber circuit components (resistor/capacitor) associated with any failed device.
  5. MeasurementCheck the gate/base drive signal to each device with an oscilloscope, where a device tests electrically healthy but does not switch correctly.
  6. DecisionA specific device tests failed (shorted/open) → device replacement required. All devices test healthy but switching is abnormal → gate/base drive circuit fault.
  7. Fault LocationIsolate to the specific failed power device, snubber component, or drive circuit fault.
  8. Root CauseConfirm whether the failure was an isolated component failure or the result of an underlying cause (overheating, surge event, drive fault) that must also be addressed to prevent repeat failure.
Test Points
Individual power device semiconductor test (in-circuit/out-of-circuit)
Snubber circuit component values
Gate/base drive signal at each device
Bridge output waveform
Root Cause Verification

After replacement/repair, run the CCR through a full start-up and load-step cycle while monitoring output waveform and device temperatures, confirming stable operation with no recurrence.

Corrective Action
  • Replace the failed power device with a manufacturer-specified like-for-like part.
  • Replace failed snubber circuit components.
  • Repair or replace the gate/base drive circuit if confirmed faulty.
  • Address any underlying overheating or surge-related root cause to prevent repeat failure.
Preventive Action
  • Include power stage thermal monitoring and device inspection in the PM schedule.
  • Verify surge protection devices are present, correctly rated, and periodically tested.
  • Maintain a spare power device inventory given the criticality of the bridge to CCR operation.
  • Address cooling deficiencies promptly (CCR-074/075) to avoid accelerating power device degradation.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-04 (CCR Isolation & LOTO Procedure)

Standards: IEC 61820-3-2 (supersedes IEC 61822)

Diagram: CCR Power Stage Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue

06 · CCR Monitoring & Communication

15 of 15 topics published
CCR-081 CCR Display Blank

Symptom — The CCR front panel HMI/display shows nothing at all — no backlight, no text, no indicator lamps — even though the unit appears otherwise powered and, in some cases, is still regulating output current normally.

Equipment / System

CCR front panel HMI/display module, its power feed, and the data link between the display and the main controller.

Possible Causes
HighDisplay module power supply feed failed or disconnected, independent of the main controller
HighDisplay module itself failed (backlight, driver, or panel hardware)
MediumRibbon cable/data connector between the display and controller loose, damaged, or disconnected
MediumMain controller has failed or is not booting, so no data is being sent to the display (see CCR-079)
LowerDisplay brightness/contrast setting inadvertently set to minimum, appearing blank rather than genuinely powered off
Required Tools
True-RMS multimeterCCR wiring/HMI diagramInsulated screwdriver setManufacturer diagnostic tool
Safety Precautions
  • Apply LOTO before opening the cabinet to access display wiring or connectors.
  • Confirm the CCR's actual run state independently (e.g. output current) before assuming the unit itself is off, since a blank display does not necessarily mean the CCR is not running.
Diagnostic Procedure
  1. ObservationConfirm whether the CCR is otherwise operating normally (output current present) despite the blank display, to separate a display-only fault from a full unit fault.
  2. MeasurementWith power isolated and verified dead, check continuity/condition of the display's power feed fuse or supply wiring.
  3. MeasurementRestore power under controlled conditions and measure voltage at the display module's power input terminals.
  4. DecisionCorrect voltage present at the display but screen stays blank → display module hardware fault. No voltage at the display → upstream power feed, fuse, or wiring fault.
  5. MeasurementInspect and reseat the ribbon cable/data connector between display and controller.
  6. ObservationIf the display briefly shows content at power-up before going blank, check brightness/contrast configuration via the controller's parameter tool.
  7. Fault LocationIsolate to the display module, its power feed, the data connector, or a brightness/contrast configuration issue.
  8. Root CauseConfirm the specific failed component by isolated testing before replacement.
Test Points
Display module power input voltage
Display power feed fuse continuity
Display-to-controller data connector/ribbon cable
Display brightness/contrast configuration
Root Cause Verification

After repair, confirm the display shows correct content immediately at power-up and remains stable through a full operating cycle.

Corrective Action
  • Repair or restore the display's power feed/fuse.
  • Replace the failed display module.
  • Reseat or replace the damaged ribbon cable/data connector.
  • Correct the brightness/contrast configuration.
Preventive Action
  • Include a display functional check in the routine PM.
  • Keep a spare display module on site given its role in local diagnostics.
  • Document default brightness/contrast settings in the site configuration record.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist)

Standards: —

Diagram: CCR HMI Wiring Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-082 CCR Display Incorrect

Symptom — The CCR front panel HMI/display is powered and legible but shows incorrect, garbled, or nonsensical content — wrong characters, corrupted graphics, or values that do not correspond to actual CCR operation.

Equipment / System

CCR front panel HMI/display module and its data/firmware link to the main controller.

Possible Causes
HighDisplay firmware corrupted or mismatched with the controller firmware version
HighDisplay driver/graphics hardware degrading, producing corrupted characters or graphics
MediumData link between display and controller experiencing errors, garbling transmitted content
MediumUnderlying controller fault feeding genuinely incorrect data to an otherwise healthy display (see CCR-079, CCR-090/091/092)
LowerIncorrect language/localisation or display configuration setting selected
Required Tools
Manufacturer diagnostic/configuration toolFirmware/configuration backup mediaTrue-RMS multimeterOscilloscope
Safety Precautions
  • Apply LOTO before accessing internal wiring or connectors.
  • Do not act on displayed values for safety-critical decisions until the display's accuracy is confirmed — verify with independent measurement first.
Diagnostic Procedure
  1. ObservationDocument exactly what is shown incorrectly — garbled characters/graphics, or plausible-looking but wrong values — and under what conditions it occurs.
  2. MeasurementIndependently verify actual CCR operating parameters (current, status, step) with reference instruments and compare against what the display shows.
  3. DecisionDisplayed values disagree with independently measured actual values → underlying controller/sensor data fault, investigate per the relevant specific topic (CCR-090/091/092). Displayed content is garbled/corrupted rather than simply wrong → display or data link hardware/firmware fault.
  4. MeasurementWhere garbling is suspected, check the display firmware version against the controller firmware version for compatibility.
  5. MeasurementInspect the data link/ribbon cable between display and controller for damage or a marginal connection.
  6. Fault LocationIsolate to display firmware, display hardware, the data link, or an underlying controller data fault.
  7. Root CauseConfirm the specific cause by resolving it and re-verifying display content.
Test Points
Display firmware version vs. controller firmware version
Data link/ribbon cable condition
Independently measured actual operating parameters vs. displayed values
Display language/localisation configuration
Root Cause Verification

After correction, confirm the display shows accurate, stable content matching independently verified operating parameters through a full representative operating period.

Corrective Action
  • Update or reflash display firmware to the correct, compatible version.
  • Replace the display module if hardware degradation is confirmed.
  • Repair or replace the data link/ribbon cable.
  • Correct display language/localisation configuration.
  • If the underlying cause is a controller/sensor data fault, address that fault per the relevant topic.
Preventive Action
  • Keep display and controller firmware versions aligned per manufacturer compatibility guidance.
  • Include display content verification against reference measurement in the PM.
  • Maintain a firmware version log for each CCR unit.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist)

Standards: —

Diagram: CCR HMI Wiring Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-083 CCR Display Flickering

Symptom — The CCR front panel HMI/display flickers, dims and brightens erratically, or intermittently blanks and returns while otherwise showing correct content, rather than remaining stable.

Equipment / System

CCR front panel HMI/display module, its power feed, and the data link to the main controller.

Possible Causes
HighLoose or marginal display power connector causing an intermittent supply
HighDisplay backlight driver degrading, producing visible flicker
MediumMarginal data link/ribbon cable connection causing intermittent refresh issues
MediumDisplay power feed voltage fluctuating due to an upstream control power supply issue
LowerElectromagnetic interference from nearby switching equipment affecting the display driver
Required Tools
True-RMS multimeterOscilloscopeData logger for trend/repeated-event analysisInsulated screwdriver set
Safety Precautions
  • Apply LOTO before performing a wiggle test or connector inspection with power isolated.
Diagnostic Procedure
  1. ObservationLog the flicker pattern over a representative period — constant, load-related, or random — to characterise the fault.
  2. MeasurementWith power isolated, perform a wiggle test on the display power connector and data ribbon cable while monitoring continuity.
  3. MeasurementUnder controlled power-on conditions, measure the display's supply voltage stability with an oscilloscope, watching for dips or noise coinciding with flicker.
  4. DecisionWiggle test reveals an intermittent connection → connector/wiring fault. Supply voltage shows genuine instability → upstream control power supply fault. Connections and supply both stable → backlight driver degradation or EMI.
  5. MeasurementIf EMI is suspected, check display cable routing and separation from high-current/switching wiring per manufacturer guidance.
  6. Fault LocationIsolate to the display connector/wiring, the control power supply, the backlight driver, or an EMI/routing issue.
  7. Root CauseConfirm the specific cause by reproducing and resolving it under controlled conditions.
Test Points
Display power connector and data ribbon cable (wiggle test)
Display supply voltage stability (oscilloscope)
Control power supply output
Display cable routing relative to switching wiring
Root Cause Verification

After repair, monitor the display through a sustained multi-cycle operating period and confirm stable, flicker-free operation with no recurrence.

Corrective Action
  • Clean, tighten, or replace the display power connector or data cable.
  • Repair or replace the upstream control power supply if found unstable.
  • Replace the display module if the backlight driver is confirmed degraded.
  • Re-route display cabling away from high-current/switching wiring if EMI is confirmed.
Preventive Action
  • Include connector/cable tightness checks in the display PM.
  • Verify control power supply stability during scheduled maintenance.
  • Follow manufacturer cable routing/separation guidance during installation and maintenance.
Related References

SOP: SOP-CCR-06 (Repeated Fault Investigation Procedure)

Standards: —

Diagram: CCR HMI Wiring Diagram

Case Study: Division 22 — Intermittent Fault Methodology; Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
CCR-084 CCR Keypad Not Working

Symptom — The CCR front panel keypad/pushbuttons do not respond, or only some keys respond, when pressed — local navigation, parameter entry, or local start/stop commands cannot be issued via the keypad.

Equipment / System

CCR front panel keypad/pushbutton assembly and its connection to the controller.

Possible Causes
HighKeypad membrane/switch assembly worn or physically damaged, especially on frequently used keys
HighKeypad connector/ribbon cable to the controller loose, corroded, or disconnected
MediumController input scanning for the keypad has failed or locked up while the rest of the controller functions normally
MediumMoisture or contamination inside the keypad membrane causing keys to stick or fail to register
LowerA local keypad lockout/lock function has been enabled, intentionally or inadvertently, in the configuration
Required Tools
True-RMS multimeterManufacturer diagnostic/configuration toolInsulated screwdriver setContact cleaner (manufacturer-approved)
Safety Precautions
  • Apply LOTO before opening the panel to access keypad wiring/connectors.
  • Use only manufacturer-approved cleaning products on the keypad membrane to avoid damaging the seal.
Diagnostic Procedure
  1. ObservationTest each key individually and record which keys respond and which do not, to distinguish a single-key fault from a total keypad failure.
  2. ObservationCheck the controller configuration for an active keypad lockout/lock function.
  3. MeasurementWith power isolated, inspect and reseat the keypad connector/ribbon cable.
  4. MeasurementWhere possible, use the controller's diagnostic tool to verify whether individual key presses are being received by the controller at all.
  5. DecisionNo keys register at the controller → connector/wiring or controller input fault. Some keys register and others do not → localized membrane/switch wear on the non-responding keys. Keys register but no action occurs → controller logic or lockout configuration.
  6. Fault LocationIsolate to the specific worn key(s), the connector/cable, the controller input scanning, or a lockout configuration.
  7. Root CauseConfirm the specific failed component or configuration setting.
Test Points
Individual key response (physical and at controller diagnostic level)
Keypad connector/ribbon cable
Keypad lockout/lock configuration setting
Controller key-scan input function
Root Cause Verification

After repair, confirm every key responds correctly and issues the expected local command through a full functional check.

Corrective Action
  • Replace the worn or damaged keypad membrane/switch assembly.
  • Clean, reseat, or replace the keypad connector/ribbon cable.
  • Disable an inadvertently enabled keypad lockout.
  • Address the controller input scanning fault per manufacturer procedure, up to controller replacement if required (see CCR-079).
Preventive Action
  • Include a full keypad functional check in the routine PM.
  • Keep a spare keypad assembly on site given its role in local operation.
  • Document any intentional keypad lockout configuration in the site record to avoid confusion during future troubleshooting.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist)

Standards: —

Diagram: CCR HMI Wiring Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-085 CCR Local Control Failure

Symptom — Commands issued from the CCR's local control position (front panel keypad/switches in local mode) fail to take effect — start, stop, or step-change commands are accepted by the panel but the CCR does not respond, or local mode cannot be selected at all.

Equipment / System

CCR local/remote selector switch, local control input path, and controller logic governing local mode operation.

Possible Causes
HighLocal/remote selector switch faulty or not making proper contact, so the controller does not register local mode as selected
HighLocal control command wiring or input terminal fault between the keypad/switches and the controller
MediumController logic fault or configuration error preventing local commands from being actioned even when correctly received
MediumA latched interlock or protection condition silently blocking command execution (see CCR-001, CCR-070)
LowerKeypad itself faulty, distinct from the local control logic (see CCR-084)
Required Tools
True-RMS multimeterManufacturer diagnostic/configuration toolCCR control schematicInsulated screwdriver set
Safety Precautions
  • Apply LOTO before accessing selector switch wiring or control terminals.
  • Confirm no interlock/protection condition is being silently overridden before repeated local command attempts.
Diagnostic Procedure
  1. ObservationConfirm the local/remote selector switch position and verify the controller's displayed/reported mode matches the physical switch position.
  2. MeasurementWith power isolated and verified dead, check continuity of the selector switch and its wiring to the controller input.
  3. MeasurementRestore power under controlled conditions and verify the controller input terminal state changes correctly when the selector switch is toggled.
  4. DecisionController-reported mode does not match the physical switch position → selector switch or wiring fault. Mode matches but commands are still not actioned → controller logic, configuration, or a latched interlock/protection condition.
  5. ObservationReview the controller's event/alarm log for any latched interlock or protection condition blocking command execution.
  6. Fault LocationIsolate to the selector switch, its wiring, controller logic/configuration, or a latched protection condition.
  7. Root CauseConfirm the specific cause and rule out a keypad-only fault per CCR-084.
Test Points
Local/remote selector switch continuity and position feedback
Controller-reported operating mode
Controller event/alarm log for latched conditions
Local command input terminal state
Root Cause Verification

After repair, confirm local start, stop, and step-change commands each take effect correctly through a full functional check.

Corrective Action
  • Replace the faulty local/remote selector switch.
  • Repair the local control command wiring or terminal.
  • Correct the controller configuration or logic fault per manufacturer procedure.
  • Clear the latched interlock/protection condition only after confirming and resolving its underlying cause.
Preventive Action
  • Include local/remote selector switch functional testing in the routine PM.
  • Verify local control functions during every scheduled maintenance visit.
  • Document local mode configuration and interlock logic in the site SOP.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist), SOP-CCR-04 (CCR Isolation & LOTO Procedure)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-086 CCR Remote Control Failure

Symptom — Commands issued from the remote control system (ALCMS/tower/PLC) fail to take effect at the CCR — the CCR does not start, stop, or change step in response to remote commands, or remote mode cannot be selected.

Equipment / System

CCR local/remote selector switch, remote control input interface, communication link to ALCMS/PLC, and controller logic governing remote mode operation.

Possible Causes
HighLocal/remote selector switch not correctly set to remote, or faulty (see CCR-085 for switch-level diagnosis)
HighCommunication link between the CCR and ALCMS/PLC down or degraded, preventing remote commands from reaching the controller (see CCR-087/088/089)
MediumRemote command mapping/configuration mismatch between the ALCMS/PLC and the CCR controller
MediumA latched interlock or protection condition blocking command execution regardless of source
LowerRemote command issued from the wrong ALCMS/PLC point or workstation due to a configuration/addressing error upstream
Required Tools
True-RMS multimeterManufacturer diagnostic/configuration toolCommunication link test equipment (per protocol)CCR control schematic
Safety Precautions
  • Apply LOTO before accessing selector switch or communication wiring.
  • Coordinate with the ALCMS/tower control room before issuing test commands, to avoid confusion with live operational traffic.
Diagnostic Procedure
  1. ObservationConfirm the local/remote selector switch is correctly set to remote and the controller reports remote mode selected.
  2. ObservationConfirm whether the communication link to ALCMS/PLC is up and healthy (see CCR-087/088/089) as a first branch point.
  3. DecisionCommunication link is down → investigate as a communication fault per the relevant specific topic. Communication link is healthy → investigate command mapping, configuration, or a latched condition.
  4. MeasurementWith the link confirmed healthy, issue a test command from ALCMS/PLC (coordinated with the control room) and monitor whether it is received at the CCR controller's input/register.
  5. ObservationReview command point mapping/addressing configuration between ALCMS/PLC and the CCR to rule out a mismatch.
  6. ObservationReview the controller's event/alarm log for a latched interlock or protection condition blocking command execution.
  7. Fault LocationIsolate to the selector switch, the communication link, command mapping/configuration, or a latched protection condition.
  8. Root CauseConfirm the specific cause through resolution and a successful coordinated remote command test.
Test Points
Local/remote selector switch position and controller-reported mode
Communication link status
Remote command receipt at the CCR controller input/register
Command point mapping/addressing configuration
Root Cause Verification

After repair, coordinate with ALCMS/tower control room and confirm remote start, stop, and step-change commands each take effect correctly through a full functional check.

Corrective Action
  • Correct the local/remote selector switch position or replace it if faulty.
  • Resolve the underlying communication link fault per the relevant specific topic.
  • Correct command point mapping/addressing configuration.
  • Clear the latched interlock/protection condition only after confirming and resolving its underlying cause.
Preventive Action
  • Include remote command functional testing (coordinated with the control room) in the routine PM.
  • Maintain a documented, version-controlled command point mapping record between ALCMS/PLC and each CCR.
  • Verify communication link health as a standing part of remote control troubleshooting.
Related References

SOP: SOP-CCR-01 (CCR Daily Start-Up Checklist), SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-087 CCR PLC Communication Failure

Symptom — Communication between the CCR controller and its associated PLC is down or failing entirely — no data exchange, a communication fault/alarm is raised, or the PLC shows the CCR as offline/unreachable.

Equipment / System

CCR controller communication port, PLC communication port, and the physical/network link between them.

Possible Causes
HighPhysical communication cable/connector damaged, disconnected, or incorrectly terminated
HighCommunication port failure at either the CCR controller or the PLC (hardware fault)
MediumCommunication protocol/parameter mismatch (baud rate, address, protocol type) between the CCR and PLC
MediumPLC program/logic fault or the PLC itself offline/faulted, independent of the CCR
LowerElectromagnetic interference or improper cable routing/shielding degrading signal integrity on the link
Required Tools
Communication link test equipment (per protocol — e.g. RS-485/Modbus tester)True-RMS multimeterManufacturer diagnostic/configuration toolCommunication wiring diagram
Safety Precautions
  • Apply LOTO before physically inspecting or reterminating communication wiring.
  • Coordinate with other stakeholders relying on the PLC before taking the link offline for testing.
Diagnostic Procedure
  1. ObservationConfirm the exact nature of the failure — no communication ever established, or communication that was previously working has stopped — and check both the CCR and PLC for their respective fault indications.
  2. MeasurementWith power isolated where required, physically inspect the communication cable, connectors, and termination for damage or looseness.
  3. MeasurementVerify communication protocol parameters (baud rate, address, protocol type) are correctly and identically configured at both the CCR controller and the PLC.
  4. MeasurementUsing appropriate test equipment for the protocol, verify signal presence and integrity on the communication link.
  5. DecisionNo signal present on the link → cable/connector/port hardware fault. Signal present but no valid communication → protocol/parameter mismatch. Signal and parameters correct but PLC itself faulted → PLC-side investigation, independent of the CCR.
  6. Fault LocationIsolate to the communication cable/connector, a port hardware fault at either end, a protocol/parameter mismatch, or a PLC-side fault.
  7. Root CauseConfirm the specific cause by restoring communication and verifying stable data exchange.
Test Points
Communication cable/connector condition and termination
Protocol parameters at CCR controller vs. PLC
Signal presence/integrity on the link
CCR and PLC fault/status indications
Root Cause Verification

After repair, confirm stable communication with no dropouts through a sustained monitoring period, and verify data exchanged matches expected values at both ends.

Corrective Action
  • Repair or replace the damaged communication cable/connector.
  • Replace the failed communication port hardware at the CCR controller or PLC.
  • Correct protocol/parameter configuration to match at both ends.
  • Escalate to the PLC-responsible party if the fault is confirmed PLC-side.
  • Improve cable routing/shielding if EMI is confirmed as a contributing factor.
Preventive Action
  • Include communication link integrity checks in the routine PM.
  • Document and version-control communication protocol configuration at both ends.
  • Follow manufacturer cable routing/shielding guidance during installation and maintenance.
Related References

SOP: SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Communication Architecture Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-088 CCR ALCMS Communication Failure

Symptom — Communication between the CCR and the Airfield Lighting Control and Monitoring System (ALCMS) is down or failing entirely — the ALCMS shows the CCR as offline/unreachable, or no status/command data is being exchanged.

Equipment / System

CCR controller communication interface, ALCMS gateway/server-side interface, and the network/link between them (which may route via an intermediate PLC).

Possible Causes
HighNetwork/link fault between the CCR site and the ALCMS — cable, fibre, switch, or network equipment failure
HighCCR-side communication interface/gateway hardware fault
MediumALCMS-side configuration error — incorrect point address, IP address, or device profile for this CCR
MediumAn intermediate PLC or RTU in the communication path has failed or lost its own link (see CCR-087)
LowerALCMS server/application-level fault affecting this CCR's data point specifically, while the underlying network is healthy
Required Tools
Communication link test equipment (per protocol)Network cable testerManufacturer/ALCMS diagnostic toolCommunication architecture diagram
Safety Precautions
  • Apply LOTO before physically inspecting communication wiring at the CCR.
  • Coordinate with the ALCMS/control room administrator before taking any action that could affect other monitored equipment on the same network segment.
Diagnostic Procedure
  1. ObservationConfirm at the ALCMS whether only this CCR is offline/unreachable, or whether multiple devices on the same network segment are affected.
  2. DecisionMultiple devices affected → likely a shared network/link fault, investigate network infrastructure rather than this CCR specifically. Only this CCR affected → investigate this CCR's link, interface, or ALCMS configuration.
  3. MeasurementCheck the CCR-side communication interface/gateway for correct power, status LEDs, and physical link integrity.
  4. MeasurementIf an intermediate PLC/RTU is in the path, verify its communication status independently (see CCR-087).
  5. ObservationVerify the ALCMS-side configuration (point address, IP address, device profile) matches the CCR's actual configuration.
  6. Fault LocationIsolate to the network/link, the CCR-side interface hardware, an intermediate PLC/RTU, or an ALCMS-side configuration error.
  7. Root CauseConfirm the specific cause by restoring communication and verifying the CCR reappears correctly in the ALCMS.
Test Points
CCR-side communication interface/gateway status
Network/link integrity between CCR site and ALCMS
Intermediate PLC/RTU communication status (if applicable)
ALCMS-side point/device configuration
Root Cause Verification

After repair, confirm the CCR shows correctly online in the ALCMS with accurate status/command exchange through a sustained monitoring period.

Corrective Action
  • Repair or replace the faulty network/link infrastructure.
  • Replace the failed CCR-side communication interface/gateway.
  • Correct the ALCMS-side point/device configuration.
  • Resolve the intermediate PLC/RTU fault per CCR-087 if applicable.
Preventive Action
  • Include CCR-to-ALCMS communication verification in the routine PM.
  • Maintain a current network topology and point-mapping document for the ALCMS system.
  • Monitor network infrastructure health independently of individual CCR status to catch shared faults early.
Related References

SOP: SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Communication Architecture Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-089 CCR Communication Intermittent

Symptom — Communication between the CCR and PLC/ALCMS drops out and recovers repeatedly rather than failing completely or remaining stable, producing intermittent "offline" indications, data gaps, or repeated reconnection events.

Equipment / System

CCR controller communication interface, communication cable/link, and the PLC/ALCMS-side interface.

Possible Causes
HighLoose or marginal communication connector/termination causing an intermittent physical connection
HighMarginal network/link quality — degraded cable, failing switch port, or a link operating near its error-rate limit
MediumElectromagnetic interference intermittently corrupting communication traffic
MediumCommunication timeout/retry parameters set too tight for actual network latency, causing false dropout indications
LowerA shared network resource intermittently overloaded by other traffic, causing periodic congestion
Required Tools
Communication link test equipment (per protocol)Data logger for trend/repeated-event analysisNetwork cable testerTrue-RMS multimeter
Safety Precautions
  • Apply LOTO before performing a wiggle test on communication wiring with power isolated.
Diagnostic Procedure
  1. ObservationLog the pattern of communication dropouts over a representative period — timing, duration, and any correlation with load, weather, or other network activity.
  2. MeasurementWith power isolated, perform a wiggle test on the communication connector/termination while monitoring the link.
  3. MeasurementTest the communication cable/link for error rate, attenuation, or intermittent continuity using appropriate protocol test equipment.
  4. ObservationReview communication timeout/retry parameter settings against actual network latency and manufacturer recommendations.
  5. DecisionWiggle test reveals an intermittent connection → connector/termination fault. Cable/link tests show a genuine quality issue → cable/infrastructure fault. Connection and cable both sound → EMI, timeout parameter, or network congestion.
  6. Fault LocationIsolate to the connector/termination, the cable/link, EMI, timeout configuration, or network congestion.
  7. Root CauseConfirm the specific cause by reproducing and resolving it under monitored conditions.
Test Points
Communication connector/termination (wiggle test)
Cable/link error rate and continuity
Communication timeout/retry configuration
Network traffic/congestion at the shared segment
Root Cause Verification

After repair, monitor communication continuously through a sustained multi-day period and confirm no recurrence of intermittent dropouts.

Corrective Action
  • Clean, tighten, or replace the communication connector/termination.
  • Replace the degraded communication cable or resolve the failing network infrastructure component.
  • Improve cable routing/shielding if EMI is confirmed.
  • Adjust timeout/retry parameters only within manufacturer-recommended limits.
  • Address network congestion at the shared segment if confirmed as a contributing factor.
Preventive Action
  • Include communication connector/termination checks in the routine PM.
  • Trend communication link quality/error rate over time to catch gradual degradation early.
  • Document timeout/retry parameter settings and require change control for adjustment.
Related References

SOP: SOP-CCR-06 (Repeated Fault Investigation Procedure), SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Communication Architecture Diagram

Case Study: Division 22 — Intermittent Fault Methodology; Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue
CCR-090 CCR Wrong Status Indication

Symptom — The CCR's reported operating status (run/standby/fault, or local/remote mode) shown on the local display and/or at the PLC/ALCMS does not match the CCR's actual physical state.

Equipment / System

CCR controller status logic, status indication outputs (local display and remote data points), and associated sensors/feedback contacts.

Possible Causes
HighStatus feedback contact/sensor (e.g. contactor auxiliary contact) worn, misaligned, or failed, reporting an incorrect physical state
HighController status logic fault or corrupted internal state, independent of the underlying physical condition
MediumCommunication data mapping error causing the correct internal status to be displayed/transmitted incorrectly at the display or PLC/ALCMS
MediumA genuine but very brief/transient state change not being captured due to a slow status update/polling rate
LowerLocal display and remote (PLC/ALCMS) status disagree with each other, indicating the fault is isolated to one indication path rather than the controller's internal state
Required Tools
True-RMS multimeterManufacturer diagnostic/configuration toolCommunication link test equipment (per protocol)CCR control schematic
Safety Precautions
  • Treat status indication as unverified until confirmed by direct physical/electrical observation — do not make operational decisions based on unverified status alone.
  • Apply LOTO before physically inspecting feedback contacts or sensor wiring.
Diagnostic Procedure
  1. ObservationDirectly observe the CCR's actual physical state (output present/absent, contactor position, etc.) and compare against what is shown on the local display and separately at the PLC/ALCMS.
  2. DecisionLocal display and remote status agree with each other but both disagree with actual physical state → likely a controller-level status logic or feedback sensor fault. Local display and remote status disagree with each other → likely isolated to the communication/data mapping path for one of the two.
  3. MeasurementCheck the relevant status feedback contact/sensor (e.g. contactor auxiliary contact) for correct mechanical alignment and electrical continuity.
  4. MeasurementWhere the local/remote indications disagree with each other, verify the data mapping/point configuration between the controller and the PLC/ALCMS.
  5. Fault LocationIsolate to the specific feedback contact/sensor, the controller status logic, or a communication/data mapping error.
  6. Root CauseConfirm the specific cause by resolving it and re-verifying that displayed/transmitted status matches actual physical state across several state changes.
Test Points
Actual physical CCR state (direct observation)
Local display status vs. actual state
Remote (PLC/ALCMS) status vs. actual state
Status feedback contact/sensor condition
Root Cause Verification

After correction, cycle the CCR through several state changes (start/stop, mode changes) and confirm the local display and remote status both correctly and promptly reflect the actual physical state each time.

Corrective Action
  • Repair, realign, or replace the failed status feedback contact/sensor.
  • Correct the controller status logic fault, up to controller replacement if required (see CCR-079).
  • Correct the data mapping/point configuration between the controller and PLC/ALCMS.
  • Adjust the status update/polling rate only within manufacturer-recommended limits if a slow rate is confirmed as contributing.
Preventive Action
  • Include a status indication verification (comparing actual state to displayed/transmitted status) in the routine PM.
  • Document status point mapping and require change control for any adjustment.
  • Periodically verify feedback contact/sensor condition during scheduled maintenance.
Related References

SOP: SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-091 CCR Wrong Current Indication

Symptom — The output current value shown on the CCR's local display and/or reported to the PLC/ALCMS does not match the actual output current as independently measured, even though the CCR's actual regulation behaviour may be correct.

Equipment / System

CCR current feedback sensor, controller current measurement/scaling logic, and current value indication outputs (local display and remote data point).

Possible Causes
HighCurrent feedback sensor drifted out of calibration, reporting a systematically incorrect value
HighController current scaling/conversion parameter incorrectly configured, offsetting an otherwise accurate raw sensor reading
MediumCurrent feedback sensor wiring loose, corroded, or picking up electrical noise, producing an inaccurate reading
MediumCommunication data scaling mismatch between the controller and PLC/ALCMS, correct at the controller but wrong once transmitted
LowerLocal display and remote current value disagree with each other, indicating the fault is isolated to one indication path
Required Tools
True-RMS clamp meter (calibrated reference)MultimeterCCR configuration/parameter toolManufacturer alarm/parameter code reference
Safety Precautions
  • Apply LOTO before inspecting current feedback sensor wiring.
  • Do not adjust the actual output current setpoint in an attempt to "correct" a display reading — confirm which value is actually wrong first.
Diagnostic Procedure
  1. ObservationIndependently and simultaneously measure the actual output current using a calibrated reference clamp meter at the series circuit.
  2. ObservationCompare the independently measured value against what is shown on the local display and separately reported to the PLC/ALCMS.
  3. DecisionIndependent measurement confirms the displayed/reported value is wrong → sensor, scaling, or wiring fault, proceed to isolate. Independent measurement confirms the displayed value is actually correct → no fault in current indication; investigate the original complaint further.
  4. MeasurementCheck the current feedback sensor's calibration against manufacturer reference values.
  5. MeasurementInspect current feedback sensor wiring for looseness, corrosion, or noise pickup.
  6. MeasurementVerify the controller's current scaling/conversion parameter and, separately, the communication data scaling used when reporting to the PLC/ALCMS.
  7. DecisionLocal display and remote value disagree with each other → isolated to the communication/scaling path for whichever indication is wrong.
  8. Fault LocationIsolate to the current feedback sensor, its wiring, the controller scaling parameter, or the communication scaling.
  9. Root CauseConfirm the specific cause by correcting it and re-verifying against the independent reference measurement.
Test Points
Actual output current (calibrated reference measurement)
Local display current value
Remote (PLC/ALCMS) current value
Current feedback sensor calibration and wiring
Controller and communication current scaling parameters
Root Cause Verification

After correction, verify the local display, remote reported value, and independently measured actual current all agree across the full intensity step range.

Corrective Action
  • Recalibrate or replace the drifted current feedback sensor.
  • Correct the controller current scaling/conversion parameter.
  • Repair the current feedback sensor wiring.
  • Correct the communication data scaling configuration.
Preventive Action
  • Include current feedback sensor calibration checks in the annual PM.
  • Document and version-control scaling/conversion parameters at both the controller and PLC/ALCMS.
  • Cross-check displayed/reported current against a reference measurement periodically, not only when a discrepancy is suspected.
Related References

SOP: SOP-CCR-02 (CCR Output Verification), SOP-CCR-10 (Protection Relay Calibration)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-092 CCR Wrong Step Indication

Symptom — The intensity step shown on the CCR's local display and/or reported to the PLC/ALCMS does not match the actual intensity step the CCR is regulating to, even though the actual light output/current level may be correct for the step it is truly on.

Equipment / System

CCR intensity step selection logic, step feedback/readback path, and step value indication outputs (local display and remote data point).

Possible Causes
HighStep command received correctly and actioned correctly by the regulator, but the step readback/feedback value used for indication is wrong
HighStep selection logic itself has actioned the wrong step while reporting the originally commanded step, so displayed step matches command but not actual output
MediumStep value data mapping/scaling error between the controller and PLC/ALCMS, correct at the controller but wrong once transmitted
MediumStale/cached step value not updating promptly after a genuine step change
LowerLocal display and remote step value disagree with each other, indicating the fault is isolated to one indication path
Required Tools
True-RMS clamp meter (calibrated reference)CCR configuration/parameter toolManufacturer alarm/parameter code referenceCCR step/intensity chart
Safety Precautions
  • Apply LOTO before internal inspection if step selection wiring/relays need to be accessed.
  • Confirm actual light output/current independently before relying on displayed step for operational decisions.
Diagnostic Procedure
  1. ObservationIndependently measure actual output current and compare against the manufacturer's step/current chart to determine which step the CCR is genuinely regulating to.
  2. ObservationCompare the independently determined actual step against what is shown on the local display and separately reported to the PLC/ALCMS.
  3. DecisionActual step (from measured current) disagrees with both indications → the step selection/regulation itself may be at fault, investigate as an output/step fault rather than an indication fault. Actual step matches actual output but disagrees with one or both indications → genuine indication-only fault, proceed to isolate.
  4. MeasurementCommand a known step change and observe whether the step readback/feedback value updates promptly and correctly at both the controller and remote.
  5. MeasurementVerify step value data mapping/scaling configuration between the controller and PLC/ALCMS.
  6. Fault LocationIsolate to the step readback/feedback path, the communication data mapping, or a stale-value update issue.
  7. Root CauseConfirm the specific cause by commanding several step changes and verifying prompt, correct indication each time.
Test Points
Actual output current vs. manufacturer step/current chart
Local display step value
Remote (PLC/ALCMS) step value
Step readback/feedback update timing
Step value data mapping/scaling configuration
Root Cause Verification

After correction, command a full sequence of step changes and confirm the local display, remote reported step, and independently verified actual step all agree promptly at each step.

Corrective Action
  • Correct the step readback/feedback path fault.
  • Correct the communication data mapping/scaling for the step value.
  • Address a stale-value update issue per manufacturer firmware/configuration guidance.
  • If the underlying fault is in step selection/regulation itself, investigate per the relevant Division 03 (Intensity Control) topic.
Preventive Action
  • Include step indication verification (command vs. actual vs. displayed/reported) in the routine PM.
  • Document and version-control step value data mapping between the controller and PLC/ALCMS.
  • Verify step readback update timing during commissioning and after any firmware update.
Related References

SOP: SOP-CCR-03 (CCR Intensity Step Verification)

Standards: —

Diagram: CCR Control Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-093 CCR Alarm Status Not Updating

Symptom — An active CCR alarm/fault condition is not reflected, or a cleared alarm remains shown as active, on the local display and/or at the PLC/ALCMS — the alarm status indication is stale rather than reflecting the controller's current alarm state.

Equipment / System

CCR controller alarm logic, alarm status indication outputs (local display and remote data point), and event/alarm log.

Possible Causes
HighAlarm status data point not updating/refreshing correctly in the communication path to the PLC/ALCMS
HighLocal display alarm indicator logic fault, independent of the controller's actual internal alarm state
MediumAlarm requires a manual acknowledgement/reset step that has not been performed, so it correctly remains shown as active per design, and is not actually a fault
MediumController's internal alarm state itself stuck/latched due to a logic fault, distinct from the indication path
LowerAlarm status data mapping/point configuration error at the PLC/ALCMS, showing an unrelated or incorrect alarm point
Required Tools
Manufacturer diagnostic/configuration toolCommunication link test equipment (per protocol)CCR event/alarm log export toolCCR control schematic
Safety Precautions
  • Treat an unclear alarm status as potentially real until proven otherwise — do not assume an alarm is stale/incorrect without verifying the controller's actual internal state.
  • Apply LOTO before internal inspection where required.
Diagnostic Procedure
  1. ObservationQuery the controller's actual current internal alarm state directly (via its own diagnostic interface/event log), independent of what is shown on the display or at the PLC/ALCMS.
  2. DecisionController's actual internal state matches what is shown → no fault in indication; the alarm is genuinely active (or genuinely clear) as displayed. Controller's actual internal state disagrees with what is displayed/reported → indication fault, proceed to isolate.
  3. ObservationCheck whether the alarm design requires a manual acknowledgement/reset step per manufacturer documentation, which would explain a persistently "active" display that is not itself a fault.
  4. MeasurementWhere indication disagrees with actual state, verify the alarm status data point mapping/configuration between the controller and PLC/ALCMS.
  5. MeasurementCheck the local display's alarm indicator logic independently of the remote indication path.
  6. Fault LocationIsolate to the communication data mapping, the local display alarm logic, or a manual acknowledgement step that has simply not been performed.
  7. Root CauseConfirm the specific cause by resolving it and re-verifying alarm indication matches actual controller state through a test alarm cycle where safely possible.
Test Points
Controller's actual internal alarm state (direct query)
Local display alarm indicator
Remote (PLC/ALCMS) alarm status point
Alarm acknowledgement/reset requirement per manufacturer documentation
Alarm status data point mapping/configuration
Root Cause Verification

After correction, where safely possible, trigger and clear a test alarm condition and confirm the local display and remote status both promptly and correctly reflect the change.

Corrective Action
  • Correct the alarm status data point mapping/configuration.
  • Repair the local display alarm indicator logic.
  • Perform the required manual acknowledgement/reset if that was the actual cause, and document the procedure for operators.
  • Address the controller's internal alarm logic fault if confirmed, up to controller replacement if required (see CCR-079).
Preventive Action
  • Include alarm indication verification (controller state vs. displayed/reported state) in the routine PM.
  • Document alarm acknowledgement/reset requirements clearly for site operators.
  • Document and version-control alarm status data point mapping.
Related References

SOP: SOP-CCR-10 (Protection Relay Calibration), SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Protection Schematic

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-094 CCR Remote Feedback Missing

Symptom — One or more expected feedback data points (status, current, step, alarm, or other telemetry) from the CCR are entirely absent at the PLC/ALCMS — not merely wrong, but not present or updating at all — while the communication link itself may otherwise appear healthy.

Equipment / System

CCR controller data point configuration, communication interface, and PLC/ALCMS point database/configuration.

Possible Causes
HighThe specific data point was never configured or was removed from the CCR controller's communication mapping
HighThe specific data point was never configured or was removed from the PLC/ALCMS point database
MediumCommunication link is healthy overall but the specific point's polling/subscription is not active
MediumA firmware update at the CCR controller changed or reset the data point mapping without corresponding update at the PLC/ALCMS
LowerThe feedback source itself (sensor/logic) generating that specific data point has failed, so there is genuinely nothing to report (see the relevant specific topic, e.g. CCR-090/091/092)
Required Tools
Manufacturer diagnostic/configuration toolCommunication link test equipment (per protocol)Communication point mapping documentationCCR control schematic
Safety Precautions
  • Apply LOTO before internal inspection where required.
Diagnostic Procedure
  1. ObservationConfirm overall communication link health (see CCR-087/088/089) to rule out a total link failure as the cause of the missing point.
  2. ObservationIdentify precisely which data point(s) are missing versus which are present and updating correctly.
  3. MeasurementCheck the CCR controller's communication point mapping configuration for the presence and correct configuration of the missing point.
  4. MeasurementCheck the PLC/ALCMS point database/configuration for the presence and correct configuration of the same point.
  5. DecisionPoint missing from the CCR controller's mapping → controller-side configuration fault. Point present at the controller but missing from the PLC/ALCMS database → PLC/ALCMS-side configuration fault. Point present and correctly configured at both ends but still not updating → investigate the underlying feedback source per the relevant specific topic.
  6. Fault LocationIsolate to the controller-side mapping, the PLC/ALCMS-side database, or the underlying feedback source.
  7. Root CauseConfirm the specific cause by adding/correcting the missing configuration and verifying the point begins reporting correctly.
Test Points
Overall communication link health
CCR controller point mapping configuration
PLC/ALCMS point database configuration
Underlying feedback source for the missing point
Root Cause Verification

After correction, confirm the previously missing data point reports correctly and updates promptly through a sustained monitoring period.

Corrective Action
  • Add or correct the missing point in the CCR controller's communication mapping.
  • Add or correct the missing point in the PLC/ALCMS point database/configuration.
  • Activate polling/subscription for the specific point if that was the cause.
  • Address the underlying feedback source fault per the relevant specific topic if the point itself has no valid data to report.
Preventive Action
  • Maintain a current, version-controlled point mapping document covering both the CCR controller and PLC/ALCMS.
  • Re-verify point mapping after any firmware update at the CCR controller.
  • Include a full data point inventory check in the routine PM.
Related References

SOP: SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Communication Architecture Diagram

Case Study: Division 25 — Field Case Study Troubleshooting (cross-reference where applicable)

Rev 0 — Initial issue
CCR-095 CCR Data Communication Failure

Symptom — A general, unresolved data communication fault affecting the CCR that does not clearly fit a single specific topic (link down, incorrect values, missing points, or intermittent behaviour observed together or in an ambiguous combination), requiring a broader systematic investigation across the full communication chain.

Equipment / System

CCR controller communication interface, communication link/network, any intermediate PLC/RTU, and the PLC/ALCMS-side interface — the full communication chain end to end.

Possible Causes
HighA single root cause manifesting as multiple symptoms across the chain (e.g. a marginal link causing both intermittent dropouts and occasional data corruption)
HighMultiple independent faults coinciding across different points in the chain, making the overall picture appear more complex than any single specific topic covers
MediumA recent change (firmware update, network change, configuration change) affecting communication behaviour in a way not yet isolated to a specific point
MediumAn intermittent or environmental factor (power quality, EMI, temperature) affecting communication hardware broadly rather than one specific component
LowerThe issue is actually several distinct, already-covered faults occurring close together in time and has not yet been separated into its component parts
Required Tools
Communication link test equipment (per protocol)Data logger for trend/repeated-event analysisManufacturer diagnostic/configuration toolCommunication architecture diagramChange/maintenance log
Safety Precautions
  • Apply LOTO before physical inspection of any communication wiring.
  • Coordinate with the ALCMS/control room and any other stakeholders before broad testing that could affect other monitored equipment.
Diagnostic Procedure
  1. ObservationSystematically document every distinct symptom observed (dropouts, wrong values, missing points, timing) with timestamps, to determine whether this is one root cause or several coinciding faults.
  2. ObservationReview the change/maintenance log for any recent firmware, network, or configuration change coinciding with the onset of symptoms.
  3. DecisionSymptoms trace to a single identifiable point or cause → re-route the investigation to the matching specific topic (CCR-087 through CCR-094) for detailed diagnosis. Symptoms genuinely span multiple independent points → proceed with a full end-to-end systematic check.
  4. MeasurementWhere a full systematic check is needed, verify each segment of the communication chain in turn — CCR controller interface, link/network, intermediate PLC/RTU, and PLC/ALCMS interface — checking status and configuration at each.
  5. MeasurementCross-reference findings against any recent change identified in the maintenance log.
  6. Fault LocationIsolate each contributing fault to its specific point in the chain, treating multiple faults separately rather than seeking one all-encompassing cause if the evidence does not support it.
  7. Root CauseConfirm each identified cause independently and verify the chain is fully healthy end to end before closing out.
Test Points
Full communication chain, segment by segment (CCR controller, link/network, intermediate PLC/RTU, PLC/ALCMS interface)
Change/maintenance log for recent relevant changes
Environmental factors (power quality, EMI, temperature) at communication hardware locations
Root Cause Verification

After all identified faults are resolved, monitor the full communication chain through a sustained multi-day period covering representative operating and environmental conditions, and confirm no recurrence of any of the originally observed symptoms.

Corrective Action
  • Apply the specific corrective action for each fault once isolated to a specific point in the chain, per the matching specific topic where applicable.
  • Revert or correct a recent change confirmed as the cause.
  • Address environmental factors (power quality, EMI, temperature protection) if confirmed as a contributing cause.
Preventive Action
  • Maintain a detailed, timestamped change/maintenance log covering firmware, network, and configuration changes.
  • Include full end-to-end communication chain verification in periodic (not just reactive) maintenance.
  • Encourage systematic symptom documentation before broad troubleshooting begins, to catch multi-fault situations early.
Related References

SOP: SOP-CCR-06 (Repeated Fault Investigation Procedure), SOP-CCR-12 (CCR–ALCMS Communication Verification)

Standards: —

Diagram: CCR Communication Architecture Diagram

Case Study: Division 22 — Intermittent Fault Methodology; Division 23 — Root Cause Analysis; Division 25 — Field Case Study Troubleshooting

Rev 0 — Initial issue

Frequently Asked Questions

Quick answers about CCR troubleshooting in the AGL Troubleshooting Atlas.

Q1What does Division 01 of the AGL Troubleshooting Atlas cover?

Division 01 is the CCR (Constant Current Regulator) troubleshooting reference. It publishes 95 diagnostic topics, CCR-001 to CCR-095, across six subsections: Start-Up & Power (20), CCR Output (20), Intensity Control (15), Protection & Alarms (15), Cooling & Internal Components (10) and Monitoring & Communication (15).

Q2What is a CCR in airfield ground lighting?

A constant current regulator (CCR) is the series-circuit lighting control unit that feeds airfield lights with a regulated current and sets their brightness through intensity steps. The reference records describe CCRs as thyristor- or IGBT-regulated units rated about 4-100 kW with 6.6 A output (20 A or 30 A on legacy systems) and 5-step or stepless intensity control.

Q3What information does each CCR troubleshooting topic include?

Every topic follows the same 11-field diagnostic record: the symptom, equipment/system, possible causes ranked by likelihood (high, medium or low), required tools, safety precautions, diagnostic procedure, test points, root cause verification, corrective action, preventive action and related references (SOPs, standards, diagrams and case studies).

Q4What should I check first when a CCR will not start?

Start at the front panel or HMI: note whether the power-on lamp is lit and record the exact status and any alarm code before touching anything. Then work through the start-up topics (CCR-001 to CCR-020). High-probability causes for a CCR that will not start include an active emergency stop or a door interlock that is open or misaligned.

Q5What safety precautions apply before working on a CCR?

CCR output can reach several kV under load, depending on circuit length, so never work on the output terminals while the CCR is running or its capacitors are charged. Apply lock-out/tag-out (LOTO) on the CCR input isolator before any internal work. The related procedure is SOP-CCR-04 (CCR Isolation & LOTO Procedure).

Q6Which topics cover output current and output voltage faults?

CCR-021 to CCR-040 cover zero, low, high, unstable and fluctuating output current, current not matching the selected step, abnormal or unstable output voltage, no output despite healthy input, output dropping under load, hunting, overshoot, undershoot, regulation failure, output transformer overheating and internal output connection failure.

Q7How do I troubleshoot a missing or incorrect brightness step?

Use CCR-041 to CCR-055. They cover Brightness Steps 1 to 5 not working, one or multiple steps missing, incorrect or automatic intensity selection, commands not accepted, local and remote intensity control failure, incorrect step indication, step relay failure and a sticking intensity control relay. Related procedures include SOP-CCR-03 (Intensity Step Verification) and SOP-CCR-08 (Intensity Step Commissioning).

Q8Which CCR protection alarms are covered?

CCR-056 to CCR-070 cover earth fault, overcurrent, overvoltage, undervoltage, overtemperature, transformer temperature, door interlock, surge protection, internal fault, communication, fan failure and cooling failure alarms, plus protection relay failure, false alarms and repeated protection trips.

Q9How are CCR communication and ALCMS faults handled?

CCR-085 to CCR-095 cover local and remote control failure, PLC and ALCMS communication failure, intermittent communication, wrong status, current or step indication, alarm status not updating, missing remote feedback and data communication failure. Related procedures include SOP-CCR-11 (Communication Link Testing) and SOP-CCR-12 (CCR-ALCMS Communication Verification).

Q10Which standards does the CCR troubleshooting content reference?

Where a standard applies, it is cited in each topic's Related References. Examples include ICAO Annex 14 Volume I, FAA AC 150/5345-10, IEC 61820-3-2, IEC 60364, IEC 60204-1, IEC 60947-4-1, IEC 61643 and IEC 62305, and Indian Standards such as IS 7785 and IS 12290.

Take the Next Step with Precision AGL Academy

Don't Just Troubleshoot the CCR. Master the System Behind It.

A CCR fault is rarely just a fault indication.

Understanding input supply, control circuits, output current and voltage, intensity control, protection, alarms, cooling, monitoring and the connected series circuit is essential for systematic AGL fault diagnosis.

Diagnose systematically. Understand the circuit. Build real AGL expertise.

Build Practical AGL Troubleshooting Capability
AGL Fundamentals CCR Systems Series Circuits Electrical Testing Fault Diagnosis Photometry Maintenance Commissioning

Talk to Precision AGL Academy

Follow the Academy