Learn to distinguish a real process condition from a failed sensor, wiring problem, or logic interpretation.
Figure: Days 12–18: Sensors, Inputs, and the Difference Between Signal and Truth — a practical way to think about the system.
What to understand
A PLC input LED tells you the controller is seeing a signal; it does not prove the real-world condition is correct. The sensor may be misaligned, contaminated, or detecting the wrong target.
Start by turning the idea into an observable question. What should the machine, component, person, or process be doing at this moment, and what evidence would prove that it is doing it? Defining normal first gives your troubleshooting a reference point and prevents you from reacting to the first unusual thing you notice.
How to apply it
Troubleshoot from the physical condition through sensor, wiring, input module, logic, and HMI indication. That chain prevents you from jumping directly to software.
Apply the idea one boundary at a time. Confirm one condition, record what you learned, and only then move to the next point in the chain. This makes your work easier to explain and greatly reduces the temptation to swap parts or change several variables at once.
What good work looks like
Intermittent sensors often fail because of mounting, vibration, contamination, marginal alignment, damaged cables, or unstable supply voltage.
Good maintenance work leaves a trail of evidence. Measurements, alarm times, verified states, photos where permitted, and clear work-order notes let another technician understand why you made the repair and whether the same failure mechanism returns later.
Field scenario
A photoelectric sensor appears to switch normally when tested by hand, but the machine misses one carton every few minutes. Watching the actual process reveals the carton edge passes through the extreme edge of the beam. A 3 mm bracket adjustment fixes the reliability problem without replacing the sensor.
After the immediate repair, capture the point in the sequence where the expected condition was lost and what evidence proved the cause. That small discipline turns a one-time fix into knowledge the whole maintenance team can reuse.
Field checklist
Common mistakes to avoid
Replacing sensors because an input is off
Testing only with the machine stationary
Ignoring mechanical alignment
Forcing PLC inputs instead of fixing field conditions
Ask yourself: If this machine failed again on the next shift, what information could I leave behind that would make the next diagnosis faster and safer?
90-day action
Before moving on, choose one task from this chapter and perform it during normal work. Record what you learned in your plant notebook. The value of the first 90 days comes from turning concepts into repeatable behavior, not from reading alone.
CHAPTER 11