FMDC LED Code 9513: A Circuit Clue, Not Proof of IC Failure

After the counter-path defect is corrected, the FMDC should no longer display LED code 9513. Decode the LED pattern first, then troubleshoot the complete circuit identified by S6 and IC 32; neither reference alone proves that a particular integrated circuit or axis has failed.

LED Pattern Capture

1. Before anything else, record the complete LED pattern exactly as displayed. Note every illuminated, extinguished, and flashing LED without interpreting the sequence from memory.
2. Repeat the observation through another startup cycle. Separate a stable diagnostic pattern from normal transitional LED activity.
3. Compare the recorded pattern with the available FMDC decode table. Preserve the table's LED order and grouping; reversing the viewing direction can produce a different code.
4. Confirm that the decoded entry is 9513 counter failure (S6, IC 32) before opening the electrical troubleshooting path below.

Do not move on until the same stable pattern decodes as 9513 on repeated observations. If the pattern changes between cycles, troubleshoot the changing condition rather than forcing every display into the 9513 diagnosis.

Code 9513 Interpretation

A digital counter fault can originate in the counter element, its clock or pulse input, enable and reset logic, data connections, local supply, or the circuitry that reads the count. A self-diagnostic can report failure at the functional block it tests even when an upstream signal or downstream readback path caused the failed comparison.

The axis association is unresolved. The component was interpreted as related to the Z axis, but exchanging it with the corresponding X-axis part did not change the result. Treat that outcome as evidence against a simple axis-specific removable-component failure, not as proof that both channels are healthy. Do not move on until S6 and IC 32 have been located on documentation that matches the installed board.

Board and Documentation Prerequisites

1. Record the FMDC board identifiers visible on the assembly. Use them to select the correct schematic, layout, or service drawing; a drawing for another revision can place IC 32 in a different function.
2. Locate IC 32 by its printed reference designator rather than by package position or assumed axis grouping.
3. Find every occurrence of S6 in the matching documents. Follow its cross-reference to the counter circuit, connector, signal, or diagnostic step defined by that drawing.
4. Trace the counter block far enough to identify its supply, return, inputs, control lines, and readback path. Mark accessible connector pins and test points from the drawing.
5. Inspect the board before applying power. Look for disturbed sockets, bent pins, contamination, damaged traces, cracked joints, and incorrect device orientation around the identified path.

De-energize the equipment before continuity checks, reseating, or exchanging components. Use appropriate electrostatic-discharge handling for board-level work. Do not move on until the physical references on the board agree with the same references on the selected drawing.

Counter-Path Isolation

1. Check the local supply and return at the counter circuit under the operating condition that produces 9513. Read the required level and tolerance from the board documentation or the installed device data rather than applying a generic logic-voltage assumption.
2. Check reset, enable, select, and gating signals at IC 32. A counter held in reset or never enabled can fail a diagnostic even when the package is serviceable.
3. Observe the counter input or clock with equipment suited to the signal. Verify that transitions reach the referenced input and are not stuck, missing, or badly distorted.
4. Trace the output or readback path. Confirm continuity through connectors, sockets, vias, buffers, and data lines identified by the schematic.
5. Compare equivalent X- and Z-related paths only after confirming that the schematic defines them as equivalent. Compare signal behavior and connectivity, not just component appearance.

The unsuccessful X/Z exchange narrows the search only if the exchanged parts were truly equivalent, correctly seated, and the fault pattern remained exactly 9513. A stationary code after a swap directs attention toward shared support logic, board interconnects, the signal source, or the diagnostic readback path. Do not move on until one abnormal measurement has been reproduced and traced to both sides of the affected node.

Repair Decision and Retest

1. Repair the measured defect rather than replacing IC 32 solely because its identifier appears in the decode text. Correct an open connection, damaged joint, missing control signal, supply problem, or failed device only after the corresponding test isolates it.
2. If a component must be exchanged for diagnosis, document its original location and orientation. Confirm electrical equivalence from the applicable documentation before installation.
3. Inspect the repaired area for bridges, lifted pads, displaced components, and incomplete connections.
4. Restore all connectors and removable devices to their intended locations. Check seating and orientation before power is reapplied.
5. Start the controller and capture the LED sequence again. Decode the new stable pattern using the same LED order used for the initial diagnosis.

If 9513 remains, return to the first abnormal signal boundary and continue outward; repeated replacement without a new measurement does not isolate the fault. Do not move on until the original electrical abnormality is gone and the FMDC no longer settles on the 9513 pattern.

End-to-End Verification

1. Perform repeated startup checks and confirm that 9513 does not return.
2. Exercise the affected machine function through its permitted operating range while monitoring the FMDC indicators.
3. Verify the functions associated with every channel disturbed during diagnosis, including the X- and Z-related locations involved in the earlier exchange.
4. Recheck the repaired node under operating conditions. Confirm that its supply, control input, counter activity, and readback remain valid when the function is active.
5. Record the initial pattern, decoded text, failed measurement, repair, and final observations for future troubleshooting.

Complete the commissioning check only when the LED diagnostic remains clear, the repaired signal stays valid under operation, and all disturbed channels perform correctly.

FAQ