Support-focused enterprise controls: trigger-first design strategy
A trigger-first design strategy enables manufacturers to obtain structured and organized control applications from many independent machine and conveyor suppliers. This method creates a common path for designs to trigger applications while enabling a standard way to develop rule-, template-, and table-based control applications.
A trigger-first design strategy means control system designers must develop movement detection and ancillary trigger circuits as the foundation for all controller applications. This means designers group, assign, and isolate trigger circuits for each control point or station. Trigger circuit isolation makes it easy for support personnel, controls integrators, and future programmers to access, understand, and change logic circuits. Isolation and subsequent recognition will provide the foundational basis for developing most latch/unlatch circuit signals for control applications. This trigger-first strategy eliminates the need for different designers to develop redundant and possibly less reliable instruction-based triggers for the same sets of movement and ancillary events.
Redundant triggers are a result of control and information system designers unnecessarily adding sensors and/or triggers to a control system design. The elimination of redundant circuits happens when manufacturers enforce specifications that dictate all trigger circuits shall reside in a common trigger routine. Eliminating randomly programmed instruction-based triggers means prohibiting their use. Exceptions are possible with advanced approval. Through specifications, manufacturers can prohibit the everyday use of instruction-based and coil-blocked triggers. These less reliable triggers cannot exist in a control application without approval documentation describing a need for the exception. Specifications should also dictate that programmers include approval information in a comment area above all exception circuits.
A trigger-first design strategy enables manufacturers to obtain structured and organized control applications from many independent machine and conveyor suppliers. The design process enables a manufacturer to realize that most latch/unlatch circuit signals are set or reset via of a movement detection or subsequent ancillary trigger. This method creates a common method for designs to trigger applications while enabling a standard way to develop rule-, template-, and table-based control applications.
Mechanical engineers were the first to recognize that physically locating and positioning objects after they stop at a station is the key to most designs. Many control system designers have gone along with this premise because presence detection is fundamental to most machines that work on stationary parts. However, if designers re-evaluate the use and effect of movement detection on all aspects of control and information system applications, they will conclude that trigger designs must come first. Any objective examination process makes it clear that movement detection has a significantly greater impact on control and system applications. For example, movement detection enables the development of the following:
- Cycle-start and cycle-complete anti-repeat circuits
- Anti-repeat pushbutton circuits
- Object-occupied memory circuits
- Blocking circuits that prevent object collisions
- Blocking circuits that prevent machine-to-object collisions or crashes
- Shift-register index signals keep data synchronized with moving objects
- Station part or object counting circuits
- Station cycle-time collection circuits
- Station blocked waiting for downstream process timing circuits
- Station starved waiting for upstream process timing circuits
- Elemental movement timing circuits for mechanisms and objects
- Arming ancillary trigger circuits
- Reader application trigger circuits
- System-destined messaging circuits
- Critical process information used by buffering circuits
- Application enabled or reset circuits.
It becomes obvious that movement detection is the cornerstone or catalyst for supporting and spawning a multitude of control and information system applications. Enabling an index signal allows designers to develop shift-register applications. The development of shift-registers enables other applications to synchronize, compare, collect, and send process information. Multiple shift-registers for merging process lines enable tracking and monitoring applications to minimize production losses caused by an out-of-sequence or out-of-balance flow of parts. The development of shift-registers also enables the development of system-level tracking applications.
With all the known movement detection trigger uses, why does it remain as a hidden feature of control system designs? Is it possible that it remains hidden because there are many machine-specific variations? Perhaps it is because management emphasizes the need for designers to be focused on controller features not process similarities. Regardless, this hidden feature forces controls integrators to develop redundant trigger circuits. A signal-free, one-shot circuit is another contributing factor. Why does anyone have to add redundant sensors? Chaos-caused confusion is normally a result of something moving to adversely affect each independently triggered application.
The bigger question is how or whether manufacturers will correct this situation. The answer to all these questions is quite simple. Recognize the problem and put controls in place to make triggers readily available to all designers, programmers, integrators, and support personnel. This starts by controlling how mechanical engineers actuate and locate sensors through machine design specifications. Equally important is bringing all trigger logic circuits to the forefront of control system designs. This way everyone will recognize and understand how they work, the interdependencies that exist between applications, and the expected common outcomes when something moves.
Recognizing the importance of movement detection should be obvious. Developing and enforcing circuit design specifications will be more difficult because each machine supplier will likely object. Objections will revolve around increasing costs associated with changing their standard hardware designs to include additional sensors and input hardware. Regardless, the idea is to understand these costs and provide justification for change. For example, the simple two-step form of movement detection is easier, but it requires two sensors. Some low-cost conveyor companies use release-based movement detection. This cheaper method allows them to escape the design, purchase, install, and wiring costs of one extra sensor per station. This means manufacturers that use release-based designs must knowingly accept the burden of built-in costs of foreseen anomalies.
Before, anomaly costs were unexpected because they did not understand the cause. Armed with this information, manufacturers must recognize and associate anomaly costs with the poor electro-mechanical characteristics of movement detection. When specification analyses are complete, it is more important that everyone understands what they have or do not have and at what cost.
Another obstacle to recognizing the importance of movement detection is breaking down the organizational barriers that manufacturers have set up. These barriers usually separate controls design teams into groups based on machine types. Specifically, one group is responsible for conveyor processes while another group is responsible for station processes. This situation makes overall designs look more chaotic because support personnel do not understand the fundamental reasons for separate groups. The following definitions provide insight into the types of control applications each group designs and implements:
- Conveyor controls monitors the movements of objects as they travel from station to station.
- Machine controls are for repetitive movements of mechanisms and processes after objects stop at stations.
The transition between conveyor and machine control is difficult for many designers. Many manufacturers see some obvious differences and use them to justify the need to divide personnel into two groups. A conveyor control group is responsible for conveyor designs, whereas a machine control group oversees static station processes. Design differences revolve around the differing control domains. A conveyor group works in a domain where travel speeds, times, distances, and machine clearances are critical to controller applications, while the machine group works in a domain where cycle times and mechanical sequences are important to applications.
To recognize design similarities between conveyor and machine control systems strategists must separate the qualities that make them different. First, manufacturers must specify that all trigger circuits must come to the forefront of each design. This means specifying the placement of trigger circuits into special routines that are easily viewable and accessible by all design teams. Second, strategists must recognize that conveyor control applications need object-moving signals that enable and disable output devices when objects enter or exit stations. Third, strategists must recognize that machine designs need to contend with the sequential movements of mechanisms and objects at process stations. This means designs need cycle-complete or cycle-start anti-repeat circuits that ensure station processes cycle once per object.
These special anti-repeat signals also provide machine control applications with a way to determine whether to move mechanisms forward or backward in a sequence when machines are physically in a duplicated state defined only by sensor input signals. Fourth, strategists need to recognize the differing ways designers model their individual processes. Conveyor designers use sensor-activation charts that depict a dimensional domain. These charts show the locations of sensors that are critical to moving objects. Machine designers use sequence-of-operation charts that depict a time domain. A time-domain chart shows the individual mechanism movement times that are critical to processing an object that has stopped at a station. In contrast, conveyor designers model the physical locations of events, whereas machine designers model event times.
Mechanical designers create sensor-activation charts using bars to represent activated sensors in a dimensional domain. Specifically, the length of each bar represents the physical length of the actuator. Deactivation bars represent the distance an object travels between two deactivated sensors. Conveyor designers use sensor-activation charts to decide the number and location of possible station triggers. The rising and falling edge of sensor transitions represent potential physical trigger points. Many designs artificially delay enabling triggers, thus changing where triggers activate when objects move. The following definitions describe how conveyor control applications produce movement detection triggers and how machine control applications produce ancillary triggers.
- Object sensor is a device that activates and deactivates a controller input signal to indicate an object is moving through a station.
- Process sensor is a device that activates and deactivates a controller input signal to indicate the position of a mechanism.
- Position trigger is a signal enabled using the rising edge activation of an object sensor.
- Moving-off trigger is a signal armed by the activation of a position trigger and is directly or indirectly enabled by the falling edge deactivation of an object sensor.
- Process trigger is a signal armed by the direct or indirect activation of a position or moving trigger and enabled by the activation or deactivation of a process sensor.
- Release-now trigger is a signal armed by an in-position trigger and enabled when the process cycle completes, and the process machine is physically clear to release the object.
Position, moving-off, and process triggers are the descriptive names assigned to otherwise generic movement detection and ancillary triggers. These triggers fire when object or process sensors activate or deactivate. The release-now trigger fires the moment a station's control application is ready to release a part from a station and before the object starts to leave the station.
Figure 1 shows the conversion to the step domain for an object entering and exiting the second conveyor station. The individual overlaps represent the simultaneous activation of object sensors. Recognizing the overlap is important because the next step in a trigger-first design strategy involves converting activation bars from the dimensional domain to a step domain. In the dimensional domain, the length of a sensor-activation bar represents the length of the actuator. In the step domain, all object sensor-activation bars have incremental unit lengths based on activation bar overlaps. A bar one unit in length represents the activation and deactivation of one object sensor with no overlapped activations with another sensor.
A bar two unit in length represents the activation of one object sensor whose activation overlaps with another sensor and that other sensor does not have an activation overlap with any other sensors. A bar three unit in length represents a sensor that overlaps at different points with two other object sensors. Some sensor activation bars have extra extensions that represent an object stopped waiting for mechanism-based machine control application to run in a time domain. Furthermore, all descriptive properties stay with each bar converted to the step domain.
- Events & Awards
- Magazine Archives
- Digital Reports
- Global SI Database
- Oil & Gas Engineering
- Survey Prize Winners
- CFE Edu