Every line of ladder logic you write is not a command executed directly. It is merely a memo for an internal ‘invisible butler’. If you do not understand its almost obsessive three working rules, no matter how good your code is, it will be executed in a chaotic manner.
Welcome to the internal world of PLCs. Here, the supreme ruler is not your program, but a great butler we call “A-Scan”.
It possesses extraordinary abilities but has a deep-seated ‘obsessive-compulsive disorder’. Its world must be absolutely orderly. Whether your program executes correctly entirely depends on whether you understand its three iron rules.
Rule One: Fixed Point Patrol, Record Once (Input Sampling)
Every day at 5:00 AM, when the factory is still silent, the ‘A-Scan’ butler begins his unwavering first patrol.
He holds a notebook (Input Image Area) and swiftly walks through all doors, posts, and sensors (Input Point I). He clearly records: “Main gate button (I0.0) not pressed.” “Warehouse sensor (I0.1) detected goods.”
[Key Insight] Once the recording is complete, he returns to his office and locks the notebook in the drawer. For the rest of the day’s work, regardless of what earth-shattering events occur outside—whether the button was pressed ten times or the sensor signals fluctuated wildly—he remains deaf to it all. All decisions today are based solely on the records from the 5 AM patrol.
This explains the ‘signal delay’: If you press the button at 5:01, sorry, the butler will not listen to your report today. Your command must wait until tomorrow at 5 AM to be recorded before it can be processed.
Rule Two: Refer to the Manual, Sandbox Simulation (Program Execution)
Now, the ‘A-Scan’ butler takes out the thick Factory Operation Manual you left for him.
He begins to compare each page and each line with the records in his notebook, conducting a complete ‘mental sandbox simulation’:
“Manual Rule 1: If the main gate button is pressed (I0.0=1), then raise the barrier (Q0.0=1).” — He checks the notebook: “I0.0=0 (not pressed)”, so he writes on his ‘To-Do List’ (Output Image Area): “Do not raise the barrier.”
“Manual Rule 15: If there are goods in the warehouse (I0.1=1) and the robotic arm is idle (M0.0=1), then start the conveyor belt (Q0.1=1).” — He checks the notebook: “I0.1=1 (goods present)”, calculates, and writes on the ‘To-Do List’: “Start the conveyor belt.”
Note! Throughout this process, he has not issued any real commands to the factory. He has only planned all the ‘tasks’ for today on the ‘To-Do List’.
Rule Three: Unified Command, No Interruptions (Output Refresh)
When the clock strikes a sacred moment (the end of a scan cycle), the last page of the ‘Factory Operation Manual’ has also been processed.
At this point, the ‘A-Scan’ butler takes the ‘To-Do List’ filled with decisions and walks to the factory broadcast room, issuing all commands to the entire factory at once, synchronously:
“Conveyor belt (Q0.1), start!” “Indicator light (Q0.2), turn off!” “… …”
At this moment, the factory equipment truly begins to operate. The external world finally feels the will of the PLC.
Once the commands are issued, a ‘butler workday’ comes to an end. He will immediately rest, waiting for the next cycle, repeating these three iron rules from the 5 AM patrol, over and over, until eternity.
Why Set Such ‘Strange’ Rules? — Order Above All
You might think this butler is inefficient. On the contrary, it is these three iron rules that ensure the factory (your control system) operates without error for ten years.
- [Absolute Stability] Any momentary interference and signal jitter from the outside world are filtered out after that ‘one-time patrol’. The system will never fall into chaos due to a faulty button.
- [Logical Consistency] Since all decisions are based on the same moment’s ‘data snapshot’, there will never be a contradiction where the first half of the program sees the button pressed and the second half sees it released, thus avoiding fatal logical conflicts.
- [Predictability] You can precisely know that an input signal will be responded to at the latest in one cycle. This certainty is the cornerstone of industrial control.
Your Dimensionality Reduction Strike: Learn to Dance with the ‘Butler’
Now, you have gained insight into the core. Those once confusing instructions have revealed their true nature:
- What is the ‘Rising Edge/Falling Edge’ instruction?
- It is a special note you write to the ‘A-Scan’ butler: “Note: Please compare the changes in today’s and yesterday’s patrol records. If a signal changes from absent to present, execute a specific action for me.” This is a patch specifically designed to break his ‘one-time recording’ rule.
Conclusion: From Coder to Architect
At this moment, the PLC is no longer mysterious in your eyes. It is a precision estate managed by the ‘A-Scan’ butler. The program you write is the ‘Operation Manual’ you set for him.
Truly top-notch programmers are not just coders; they are architects who can design clear, efficient, and unambiguous workflows for this ‘perfectionist butler’.
Share this ‘butler metaphor’ with your colleagues or apprentices and see if they can understand it instantly! Share your teaching results in the comments, or propose a more ingenious metaphor! Let’s explore the underlying philosophy of PLCs together.