{"id":3208,"date":"2026-10-04T09:00:00","date_gmt":"2026-10-04T01:00:00","guid":{"rendered":"https:\/\/cnbygele.com\/?p=3208"},"modified":"2026-10-06T17:06:46","modified_gmt":"2026-10-06T09:06:46","slug":"apfc-controller-alarm-troubleshooting","status":"publish","type":"post","link":"https:\/\/cnbygele.com\/ru\/blog\/apfc-controller-alarm-troubleshooting\/","title":{"rendered":"APFC Controller Alarm Codes and Troubleshooting"},"content":{"rendered":"

APFC controller troubleshooting<\/strong> should begin with the exact alarm message, controller model and operating state. Alarm codes are manufacturer-specific: a code from one manual cannot safely be applied to another device. Save the message and event time, identify what protection action occurred, then separate measurement, supply, stage-output, thermal and harmonic problems. Resetting an alarm without addressing its cause can hide an unresolved fault. If there is damaged insulation, overheating, abnormal noise or repeated protection operation, follow the plant’s procedure for taking the affected equipment out of service.<\/p>\n

This guide provides a diagnostic framework for capacitor-compensation controllers. It deliberately does not invent a universal JKW alarm-code list. Use the exact product manual alongside automatic power-factor-controller settings<\/a>.<\/p>\n

Preserve the first useful evidence<\/h2>\n

Before clearing an alarm, record its displayed text or code, timestamp, active stages, operating mode and load condition. Photograph the display from a safe position if appropriate. Retain any event log or communication record. An alarm that appears only during a stage transition may require different investigation from one present immediately after controller power-up.<\/p>\n

Record what the controller actually did. It may have blocked new connections, disconnected one stage, disconnected all stages or issued only a warning. These behaviors are not interchangeable. Operators need to know which equipment remains active and whether an automatic reset or restart is configured.<\/p>\n

Include recent changes: replacement capacitors, CT work, controller replacement, new drives, ventilation maintenance or a changed target. Timing can help form a hypothesis, but it does not prove causation. Keep the earlier configuration so a later review can compare settings rather than relying on memory.<\/p>\n

Obtain the correct manual and identify the alarm meaning<\/h2>\n

Use the controller’s full model designation and the relevant manual or firmware revision. A series may contain variants with different input ratings, output counts and features. Confirm that the manual’s terminal diagram and menu descriptions match the installed unit.<\/p>\n

Translate the alarm into its documented condition and action. Determine whether it refers to supply voltage, measured current, insufficient compensation, stage response, temperature, harmonic conditions or communication. Do not infer a numeric threshold from the alarm name. Check the configured setting and any factory or project requirement for the exact equipment.<\/p>\n

For CNBYG JKW reactive-power controllers<\/a>, provide a nameplate photograph and the actual message when requesting support. Ask for the model-specific interpretation rather than assuming a generic internet list applies.<\/p>\n

A practical alarm-group triage table<\/h2>\n
\n\n\n\n\n\n\n\n\n\n\n\n
Alarm group<\/th>\nEvidence to collect<\/th>\nFirst diagnostic distinction<\/th>\n<\/tr>\n<\/thead>\n
Supply or voltage<\/td>\nActual measurement point, voltage readings and event timing<\/td>\nIs the supply abnormal, or is the measurement\/configuration wrong?<\/td>\n<\/tr>\n
Current or CT signal<\/td>\nCT ratings, input compatibility, location and load<\/td>\nIs the current genuinely small or absent, or is the measurement chain faulty?<\/td>\n<\/tr>\n
Insufficient correction<\/td>\nReactive demand, connected stages and available capacity<\/td>\nIs capacity insufficient, a stage unavailable or the CT unable to see correction?<\/td>\n<\/tr>\n
Stage response<\/td>\nCommand log, switching state and measured branch output<\/td>\nDid the stage fail to operate, or did the controller fail to measure its effect?<\/td>\n<\/tr>\n
Temperature<\/td>\nSensor type, location, enclosure ambient and cooling<\/td>\nIs the assembly overheating, or is sensor\/configuration interpretation wrong?<\/td>\n<\/tr>\n
Harmonic or power quality<\/td>\nInstrument definitions and voltage\/current spectra<\/td>\nIs measured duty outside the design, or are unrelated metrics being compared?<\/td>\n<\/tr>\n
Communication<\/td>\nAddress, protocol, wiring and local controller operation<\/td>\nIs remote reporting lost while local compensation still works?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The groups are a troubleshooting aid, not a product code table. The electricity authority’s APFC specification<\/a> illustrates why measurement, protection and control functions need to be documented together. Confirm the installed model’s actual implementation.<\/p>\n

Investigate supply-voltage alarms at the correct point<\/h2>\n

Compare the controller’s voltage quantity with the exact measurement scheme. A phase-to-phase input and a phase-to-neutral input represent different quantities. Confirm any configured nominal value or scaling before diagnosing an overvoltage or undervoltage condition.<\/p>\n

Correlate the event with motor starts, source changes, bus-coupler operation and production cycles. A short event may require suitable logging to capture; an occasional handheld reading taken much later may not represent the alarm condition. Record instrument location and timing so the comparison is meaningful.<\/p>\n

Do not widen thresholds simply to make the alarm disappear. The permitted range should come from the equipment and project requirements. If the supply genuinely exceeds those conditions, address the supply problem or review the equipment design with the responsible engineer.<\/p>\n

Investigate CT and current-signal alarms safely<\/h2>\n

Check the physical CT rating, connected secondary tap and controller input capability. Confirm the menu convention used for scaling. A controller expecting primary amperes may be misconfigured if a mathematical ratio was entered, and a physical 1 A or 5 A secondary must be compatible with the specified input.<\/p>\n

Consider light-load operation separately. A very small secondary signal can affect measurement or automatic stage learning without indicating a broken controller. Review the CT’s operating range and the device’s stated minimum signal requirements. Do not select an arbitrary new ratio merely to suppress a warning.<\/p>\n

Physical CT work requires the approved qualified-person procedure. The California CT-secondary rule<\/a> addresses the open-secondary hazard. Use APFC CT-ratio setup<\/a> to organize the evidence; do not disconnect live secondary conductors as an informal test.<\/p>\n

\"CNBYG-reference
Product-reference illustration; not a photograph of an actual energized test.<\/figcaption><\/figure>\n<\/p>\n

Separate insufficient capacity from failed stage output<\/h2>\n

An insufficient-compensation alarm can reflect demand beyond the bank’s available output, but it can also reflect unavailable stages, a wrong sequence or a CT location that excludes the correction response. Compare reactive demand with the actual net stage outputs at operating voltage and the stages genuinely available for connection.<\/p>\n

Check controller commands against the switching-device state and measured branch output using the approved commissioning method. A commanded output does not prove a contactor closed, and a closed contactor does not prove that the capacitor branch supplies the expected kvar. A fuse or capacitor problem can leave a stage electrically ineffective.<\/p>\n

Do not add more capacity before identifying missing existing output. Review the stage drawing, protection history and replacement records. If the bank genuinely lacks sufficient range or resolution, APFC step selection<\/a> helps separate total capacity from minimum-stage control limitations.<\/p>\n

Treat thermal alarms as evidence, not a setting inconvenience<\/h2>\n

Identify the sensor and what it measures. A winding sensor, core-mounted sensor and cabinet-air sensor have different meanings. Record the actual location, sensor type and configured action. An apparent mismatch may arise from comparing a sensor reading with an infrared surface measurement that represents another location.<\/p>\n

Inspect ventilation, fans, blocked filters and nearby heat sources during the appropriate safe condition. Compare current and harmonic loading as well as enclosure ambient. A thermal issue can result from the interaction of electrical losses and inadequate cooling rather than one isolated defect.<\/p>\n

Do not raise a threshold because the reactor’s insulation class appears high. The permitted operating conditions and protection setting belong to the complete assembly. If overheating accompanies discoloration, damaged insulation or repeated trips, follow the equipment shutdown procedure and obtain supplier review.<\/p>\n

Investigate harmonic alarms with compatible measurements<\/h2>\n

Determine whether the alarm responds to voltage THD, current distortion, a particular harmonic or another model-specific quantity. The controller and reference analyzer may use different definitions or measurement bandwidths. Compare like quantities at the same operating point rather than treating every percentage as equivalent.<\/p>\n

Capacitor-stage switching can change network conditions. Correlate events with stage combinations and nonlinear-load operation, and retain the harmonic spectrum. A single average reading can miss the condition that triggered protection. The bank’s intended harmonic duty and reactor matching should be reviewed if events recur.<\/p>\n

Adding capacitor stages does not automatically remove current distortion. The OpenStax AC-power discussion<\/a> explains the basic sinusoidal quantities, but a distorted-waveform problem requires an appropriate power-quality assessment and equipment response.<\/p>\n

Distinguish communication failure from compensation failure<\/h2>\n

A remote monitoring system may lose data while the local controller continues operating. Check local display and stage behavior before declaring the compensation system unavailable. Conversely, a communication link that works does not prove that measurement or stage operation is correct.<\/p>\n

Record the configured address, protocol settings, wiring arrangement and any recent changes to gateways or polling software. Follow the actual communication manual rather than changing several parameters at random. Preserve local operation during diagnosis unless the approved procedure requires shutdown.<\/p>\n

Define what the operator should do when remote data is stale. A monitoring screen should not continue presenting old measurements as current. The maintenance record should state whether the issue affects remote reporting, local control or both.<\/p>\n

Reset only after the documented conditions are satisfied<\/h2>\n

Use the manual’s reset and restart procedure after resolving the verified cause. Confirm whether a reset reconnects stages automatically and whether reconnection intervals still apply. Ensure personnel and equipment are ready for the actual action, not merely the disappearance of an alarm icon.<\/p>\n

Repeat the relevant test under representative conditions. Record whether the alarm recurs, whether all required stages are available and whether protection functions behave as intended. A controller that remains quiet because the affected stage is disabled has not necessarily been restored to full service.<\/p>\n

Save the fault, evidence, correction and verification in one service record. If the cause is unresolved, state that explicitly and retain the safe operating arrangement approved for the site. Repeated resets without diagnosis make the next investigation harder and can increase equipment stress.<\/p>\n

\"CNBYG-reference
Product-reference illustration; not a photograph of an actual energized test.<\/figcaption><\/figure>\n<\/p>\n

Further learning<\/h2>\n