Fatek FBs PLC — ERR LED Blink & Error Codes

Fatek · beginner · 15 min

On a Fatek FBs PLC the ERR LED is your first diagnostic. Solid ERR means a hardware failure; a 0.5-second blink means a main-unit error such as a watchdog timeout, program error or system error — and the Y0–Y3 outputs turn into a live error-code readout.

ℹ️ On a Fatek FBs main unit the ERR LED tells you the class of fault at a glance: steady = PLC hardware failure, blinking (0.5 s) = main-unit error (watchdog / program / system). When it blinks, Y0–Y3 stop being outputs and show an error code instead.

The ERR LED is the first thing to read

Every Fatek FBs main unit has an ERR indicator, and how it behaves tells you which kind of problem you have:

• ERR steady ON — a PLC failure. Power-cycle to try to recover: turn the power off, then on again; the RUN status is resumed by recycling power. If it comes straight back, the main unit needs service.
• ERR blinking at a 0.5-second interval — an anomaly in the main unit: a watchdog timeout, a program error, or a system error. The corresponding outputs are disabled while this is active.

Y0–Y3 become an error-code readout

What makes the FBs quick to diagnose in the field: when the ERR LED flashes, the status indicators Y0–Y3 switch roles and serve as an indication of 15 possible error codes (the real Y0–Y3 outputs are disabled while this is happening). Read the Y0–Y3 pattern against the error-code table in the FBs hardware manual to identify the specific fault without a laptop.

Confirm the exact cause in WinProladder

For the precise error and its description, connect to the PLC with WinProladder (Fatek's programming software). It shows the error code and its description — typically a program syntax error, an I/O module fault, or a memory issue. This turns "the ERR light is blinking" into a named cause you can fix.

Step-by-step recovery

1. Look at the ERR LED. Steady or blinking?
2. Steady ON → power-cycle. Turn off, turn on; RUN should resume. If it doesn't, the unit is faulty.
3. Blinking → read Y0–Y3 against the error-code table for a fast field ID, and/or connect WinProladder to read the exact error code and description.
4. Resolve the named cause. For a major error you must clear the cause first, then use the programming software to put the PLC back into RUN. Fix a program syntax error and re-download; reseat or replace a faulty I/O module; address the memory fault.
5. Return to RUN and confirm the ERR LED is off and outputs are live again.

Watchdog timeouts specifically

A watchdog timeout means a scan took too long — usually a long loop, a large amount of interrupt processing, or a program structure that overruns the watchdog time. Review the offending logic (or the watchdog setting) rather than just clearing it, or it will trip again on the same scan.

Never do this

Don't leave a PLC that recovers only by repeated power-cycling running a live machine — a unit whose ERR LED keeps returning to steady-on is failing, and it should be replaced, not nursed. And never force RUN over an unresolved program or I/O error just to keep the line moving.