{"id":3382,"date":"2026-10-02T01:00:00","date_gmt":"2026-10-02T01:00:00","guid":{"rendered":"https:\/\/cnsuton.com\/?p=3382"},"modified":"2026-10-04T12:19:07","modified_gmt":"2026-10-04T12:19:07","slug":"afdd-status-indication-fault-diagnosis","status":"publish","type":"post","link":"https:\/\/cnsuton.com\/id\/blog\/afdd-status-indication-fault-diagnosis\/","title":{"rendered":"Indikasi Status AFDD dan Diagnosa Gangguan"},"content":{"rendered":"

AFDD fault indication<\/strong> should be recorded before a device is reset. Check the exact model\u2019s lamp, display or trip code, then note the circuit, connected loads, time and source mode. An integrated AFDD and RCBO may open for arc, overcurrent or residual-current reasons, so the handle position alone does not identify the cause. Use the manufacturer\u2019s indication legend and an approved safe-work procedure to guide inspection and testing. Keep the as-found evidence, repair and as-left result together.<\/p>\n

Capture the indication before anyone resets the device<\/h2>\n

Record the indication in the form used by the exact manual: a steady lamp, flashing sequence, display message or other declared signal. Note when it was observed relative to the trip and whether supply was present at that moment. A photograph of an accessible front panel may help preserve the observation, but it does not replace the model-specific indication legend. Do not open a live enclosure to obtain it. If the manual does not identify the observed pattern, send the product code and event record to the manufacturer instead of borrowing a code table from another model. Keep the original observation separate from the technician’s interpretation.<\/p>\n

The first diagnostic action is to record what the AFDD actually shows. Note the handle position, any status light, display, flashing sequence or fault code, the time, circuit name, source mode and connected loads. Some products distinguish arc detection from overcurrent or residual-current operation; others provide less detail. Never assign a universal meaning to a color or flash count. Use the indication legend for the exact catalogue code and firmware revision.<\/p>\n

If there is smoke, a burning smell, visible heat damage or exposed conductors, keep the circuit safely isolated and ask a competent person to investigate. A quick reset may erase useful evidence or re-energize a fault. Where the circuit supports critical equipment, follow the site continuity plan and document any temporary alternative. The HSE electrical-safety guidance<\/a> emphasizes planned isolation and competent work.<\/p>\n

Distinguish the protective function that may have operated<\/h2>\n

An AFDD analyzes signatures associated with hazardous arcing. A device combined with an MCB or RCBO can also open for overload, short circuit or residual current. A trip on a combined product should therefore be assigned only after reading its model-specific indication and examining the circuit. The IEC 62606 product scope<\/a> recognizes standalone, integrated and declared paired AFDD arrangements; it does not define the user-facing code for every SUTON model.<\/p>\n

The AFDD versus RCBO guide<\/a> separates the arc and leakage functions. If the indication points to a residual-current event, review neutral routing, protective-earth paths and equipment leakage under the approved test procedure. If it points to overcurrent, compare load and fault evidence with the circuit study. An arc indication calls for inspection of connections, cables, plugs and affected equipment. Do not bypass one function because another protective device remains in the board.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Observed evidence<\/th>\nQuestion to investigate<\/th>\nRecord to retain<\/th>\n<\/tr>\n<\/thead>\n
Model-specific arc indication<\/td>\nIs there cable, plug or termination damage?<\/td>\nCode, circuit state and inspection result<\/td>\n<\/tr>\n
Residual-current indication<\/td>\nAre neutral and earth paths correct?<\/td>\nWiring diagram and approved test result<\/td>\n<\/tr>\n
Overcurrent indication<\/td>\nWas the load or fault current above the design basis?<\/td>\nLoad list and protection study<\/td>\n<\/tr>\n
No clear indication<\/td>\nWhat conditions repeated around the trip?<\/td>\nTime, loads, source and event log<\/td>\n<\/tr>\n
Failure to reset<\/td>\nDoes the manual indicate an internal or circuit fault?<\/td>\nAs-found state and supplier advice<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

This table is a diagnostic framework, not a device-specific code legend. The SUTON model manual controls the meaning of each indication.<\/small><\/p>\n

Build an event timeline rather than a guess<\/h2>\n

Record whether the operation happened immediately after energization, at motor start, after a charger was connected, during wet weather, during a source transfer, or after maintenance. Include loads that were already running. A simple timeline often reveals a repeatable pattern that would be lost by swapping the AFDD too early. Ask the operator what changed since the last normal period, including cords, adapters, power supplies and firmware settings.<\/p>\n

One correlated load does not prove that load is defective. A damaged plug, loose terminal, poor cable joint or shared neutral may show up only when that load draws current. Inspect and test the installation under an approved safe-work procedure. The IET AFDD overview<\/a> explains that these devices analyze waveform signatures, which makes a careful comparison with normal load operation useful.<\/p>\n

\"AFDD
Product-reference illustration based on the actual SUTON product photograph; use the exact model documentation for ratings, installation and test requirements.<\/figcaption><\/figure>\n

Check the physical circuit after safe isolation<\/h2>\n

Trace the protected final circuit from the device to outlets and fixed loads. Look for discolored terminals, heat marks, damaged insulation, crushed flexes, moisture, contamination or unsupported joints. Check line\/load markings, neutral routing, protective-earth continuity, terminal preparation and torque against the manufacturer’s instructions. A visual check does not prove that concealed wiring is sound, so use the installation tests required by the adopted rules when the evidence warrants them.<\/p>\n

Where a combined AFDD\/RCBO is involved, borrowed neutrals or downstream neutral-to-earth bonds can create a leakage trip that resembles an unexplained AFDD event to the operator. The neutral wiring guide<\/a> covers the return-path issue. Draw normal and backup-source modes if a generator, inverter or transfer switch is present; the product’s supply direction and neutral path must match the approved design.<\/p>\n

Use the test button for its declared purpose<\/h2>\n

The orange control on a product photo may be a test function, but the exact sequence and expected indication must come from the supplied manual. A successful button operation checks a defined internal path. It cannot prove that all downstream cable and equipment faults have been cleared. If the device has automatic self-test, record how the manual says a self-test failure is signaled and what maintenance action follows.<\/p>\n

Do not create a live arc with loose wires or tools to see whether the AFDD trips. That can cause fire or injury, and the resulting waveform may not resemble a controlled product test. The AFCI installation guide<\/a> provides related panel-work context. If a specialist instrument is recommended by the device manufacturer, use it only within its stated method and limits.<\/p>\n

Request model-specific evidence from the supplier<\/h2>\n

The SUTON ETB9LAF-63 product page<\/a> provides a real physical reference. For a fault investigation, ask the supplier for the exact model’s indicator legend, installation sheet, firmware or hardware revision where relevant, compatible accessories, test-button behavior and known diagnostic steps. A general AFDD brochure cannot tell you what one blinking lamp means on every variant. Keep the written response beside the observed event log.<\/p>\n

If a replacement is proposed, compare rated current, short-circuit capacity, poles, neutral treatment, terminal map, busbar, integrated protective functions and test procedure. A visually similar white DIN-rail device may not be equivalent. Record the reason for replacement and the as-left result; do not erase the original event record.<\/p>\n

Close the loop after a repair<\/h2>\n

After repairing a termination, replacing damaged equipment, removing moisture or correcting a neutral path, repeat the relevant inspection and approved tests. Confirm the AFDD model and settings still match the circuit schedule, then observe normal operation in the modes that previously produced the trip. Record the instrument, procedure, source mode, load state and result. A successful observation supports the repaired installation under those conditions; it does not guarantee that no future device or load change can cause a trip.<\/p>\n

Where a cause remains unproven, say so. Continue monitoring with a defined event log or obtain engineering\/manufacturer support. Do not label the trip \u201cfalse\u201d solely because the device later reset. Give the operator a concise reporting procedure: note the indication and affected loads, leave unsafe conditions isolated, and call a competent person for repeat events. The AFDD nuisance-tripping guide<\/a> covers the broader investigation.<\/p>\n

\"AFDD
Product-reference illustration based on the actual SUTON product photograph; use the exact model documentation for ratings, installation and test requirements.<\/figcaption><\/figure>\n

Handover record for future service<\/h2>\n

Keep the exact AFDD code, protected circuit, source-mode drawing, indication legend, event timeline, inspection findings, repairs, test results, date and responsible person together. This makes the next trip easier to diagnose without repeating a risky trial-and-error process. The circuit-breaker types guide<\/a> explains how AFDD protection fits with other devices in the same panel.<\/p>\n

For a multi-circuit site, use a consistent event form so that different maintenance shifts record comparable evidence. Include whether the circuit was occupied, what equipment was energized, ambient conditions, and whether any alarm appeared upstream. Preserve photos of the device before operation and any removed damaged component. If the same symptom appears on several circuits, investigate shared supply events and installation practices rather than replacing all devices by default.<\/p>\n

When discussing the event with a manufacturer, send the model code and as-found evidence but avoid claiming that an arc signature proves a particular fault location. The detection algorithm identifies electrical behavior at its measurement point; location and root cause still require investigation. Distinguish confirmed findings from hypotheses in the service report. That discipline helps future engineers compare events and protects against a dangerous false sense of closure.<\/p>\n

Frequently asked questions<\/h2>\n

Does a red or flashing AFDD indicator always mean an arc fault?<\/h3>\n

No. Read the exact model legend and consider any integrated overcurrent or residual-current function.<\/p>\n

Should I reset the AFDD before recording the code?<\/h3>\n

Record the indication and circuit state first, and follow the approved safe-work procedure.<\/p>\n

Can a test-button pass rule out a damaged cable?<\/h3>\n

No. It verifies a defined internal response, not every downstream cable or load condition.<\/p>\n

Video explanation<\/h2>\n

Watch AFDD Arc Fault Detection Devices Additional Tests (Part 2) by John Ward (jwflame) for visual context. Product configuration and safety steps must still follow the exact SUTON model documents.<\/p>\n