PLC Input LED On but the Tag Is Off? Check These 5 Layers First
An illuminated input LED does not prove that the application is reading the correct live signal. The LED, module status, process image, mapped tag, and HMI can represent different points in the data path. Compare those layers before replacing a sensor or editing the machine sequence.
General diagnostic method; Siemens documentation illustrates one controller family's I/O behavior.
What is happening?
The exact meaning of an LED depends on the module. Separately, a controller may read an I/O image or a direct peripheral value, and remote I/O has its own update behavior. A healthy electrical channel can therefore coexist with an incorrect address, stale connection, or application mapping error. Use the hardware manual to identify what the indicator actually confirms.
Check these five things
-
Confirm the physical channel and module part number against the drawing. Similar terminal labels on adjacent modules are an easy source of mistaken identity.
-
Read module and connection diagnostics. Record whether the channel data is valid, substituted, inhibited, or unavailable before interpreting the Boolean value.
-
Observe the actual hardware input address in the correct controller project. Verify slot, channel, rack, and any configured process-image partition.
-
Cross-reference the application tag. Look for copied values, aliases, inversion, simulation selection, and additional assignments that separate it from the hardware input.
-
Compare the PLC value with the HMI value and timestamp. A display tag can be wrong even when the controller's own input is updating correctly.
Worked example
In a training project, input channel 3 changes correctly but DoorClosed stays false. The mapping routine copies channel 4 into DoorClosed. Correcting the verified mapping resolves the discrepancy; replacing the sensor would not. This is an illustrative diagnostic path, not evidence that mapping is always the cause.
Quick diagnostic reference
| Observation | Next question |
|---|---|
| LED changes; hardware tag does not | Is the address correct and the module data valid? |
| Hardware tag changes; application tag does not | Where is the mapping or overwrite? |
| PLC tag changes; HMI does not | Is the display connection current and correctly mapped? |
The mistake to avoid
Do not force the input to make the sequence continue. That can hide the fault and misrepresent the physical condition to the program.
How to verify the fix
Repeat the input's normal state changes under the approved test procedure and record agreement across the channel, hardware tag, application tag, and display.
Field-work boundary: These are educational diagnostic guides. Use the exact equipment manuals and approved site procedures. Electrical testing and machinery changes belong to qualified, authorized personnel; control hazardous energy and validate affected functions before release.
Technical reference
Siemens S7-1200: scan-cycle and I/O-image behavior. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.