The PLC Pro Tutorial Framework
PLC Pro Tutorials follow a common example application through the activities required to develop its control system. The work begins by defining what the customer needs the equipment to accomplish, then follows the application through the design and programming considerations addressed by PLC Pro Methods.
Define the Customer Need
Whenever practical, the PLC Pro should participate early enough in the design process to understand the customer’s requirements and contribute controls-related considerations, including control architecture and component selection, before the equipment design is finalized.
Whether or not the PLC Pro participates in the equipment design, the customer’s expectations, requirements, standards, and operating constraints must be understood before the control program is developed.
That understanding must be translated into application-specific requirements, guidelines, and measurable criteria that can guide development and later be used to evaluate the completed solution.
Develop the IO Schedule
Before useful PLC programming can begin, the PLC Pro must determine how the control program will direct, coordinate, and verify the equipment actions required by the application. The IO Schedule is the working product of that controls-oriented review of the equipment design. In it, the PLC Pro will identify the sensors, actuators, drives, safety interfaces, communications, and other devices or systems the control program has available to get the job done.
The resulting IO Schedule is broader than a list of discrete inputs and outputs. It identifies the actual PLC interfaces to the equipment and surrounding systems, including physical IO, intelligent devices and communications data, together with the information needed to locate and use each interface in the control program.
The IO Schedule remains with the equipment throughout its service life. During development and commissioning it is maintained as the programmer's current working reference, and after commissioning it becomes a primary maintenance document for understanding the control system and locating its interfaces. Whenever wiring, hardware, addresses, devices, or communications interfaces change, the schedule is updated to reflect the equipment as it actually exists.
Map the IO
With the workstation IO identified and documented in the IO Schedule, the PLC Pro can establish the program interface between the physical IO and the internal variables used by the control application. IO Mapping provides that defined interface for both inputs and outputs.
This separation keeps physical IO addresses out of the workstation control logic. Hardware changes can therefore be accommodated in the mapping without chasing address references throughout the program, while the organized mapping provides maintenance and troubleshooting personnel a predictable place to relate program variables to the actual workstation IO.
Develop the Power Loss Response
Before equipment control logic is developed, the PLC Pro reviews how the workstation hardware and output commands respond when electrical power is lost and restored. Each output is considered individually to determine what physical state the equipment assumes on power loss and what may occur when power returns.
Where a change at the hardware level could lead to a more desirable power-loss response, the PLC Pro works with the equipment design team to identify and coordinate the hardware changes required to provide that response.
The startup response on PLC power restoration is then implemented in a ladder program that executes once when the PLC application starts, before normal workstation control logic begins executing.
Develop the E-Stop Response
The PLC Pro establishes E-Stop Mode from the Area safety-system status so the workstation control program has a defined operating-mode condition that reflects the surrounding safety system.
The workstation's physical E-Stop response is then reviewed against the behavior already established during the power-loss review. The requirements for preventing persistent Manual Mode requests from remaining actionable through an E-Stop condition are also identified for later equipment-control logic.
E-Stop Mode cancels Auto Mode. When the Area E-Stop is reset, the workstation returns to Manual Mode, with the hardware remaining in its current state until a new deliberate command is accepted.
Develop Manual Mode
Manual Mode provides operators and maintenance personnel with the controls and indications needed to operate individual workstation equipment functions independently of the automatic operating cycle. These capabilities support equipment operation, troubleshooting, and maintenance.
In this tutorial, we develop the control logic and HMI interfaces for the workstation's individual equipment functions. We also establish supporting modeless functions, equipment diagnostics, and alarm handling that serve both manual and automatic operation.
Develop the Carrier Homing Sequence
The Carrier Homing sequence establishes the carrier turntable's mechanical HOME position. As a modeless sequence, it operates independently of the workstation's automatic cycle, allowing homing to be requested in Manual Mode and incorporated into automatic operation.
In this tutorial, we apply established PLC Pro Sequencing methods to develop the sequence permissives, individual steps, equipment commands, and RESET handling. We also address requirements discovered during development and establish the handshake with a separate Position Reset sequence that will zero the servo drive's position reference.
Develop the Position Reset Sequence
The Position Reset sequence establishes the servo drive's current position at mechanical HOME as zero using Homing Method 37, without moving the carrier.
In this tutorial, we reuse established PLC Pro Sequencing methods and existing Ladder logic to develop the sequence permissives, individual steps, servo drive commands, and RESET handling. We also demonstrate how the two modeless sequences coordinate their operation and establish execution time diagnostics.