PackML state model
Define machine states and allowable transitions separately from process modules, device control, and safety functions.
Foundation workshop
PLC, sensor & PackML integration fundamentals
A practical learning path from field truth to a consistent machine-state interface, with emphasis on modes, PackTags, diagnostics, safe recovery, and evidence-based commissioning.
Archive disclaimer. Disclaimer: automationworldconference.com is an independent historical archive and technical educational resource. It is not affiliated with, authorized, sponsored, or endorsed by PMMI Media Group, Automation World Magazine, or any prior conference operators. All registered trademarks belong to their respective owners.
Modes and ownership
Specify producing, maintenance, manual, and other supported modes, including who may request a transition and what blocks it.
PackTags and field truth
Map standardized status and command data to real sensor quality, actuator confirmation, counts, speed, and reason codes.
Commissioning evidence
Prove state transitions, timeout behavior, interrupted cycles, restart, line handshakes, HMI indication, and data consistency.
Learning outcome
A learner should be able to trace a production symptom backward from the reported PackML state through transition conditions, permissives, raw input, field wiring, and the physical process—then identify which evidence discriminates among competing causes.
Example acceptance test
Force or simulate each credible sensor fault without bypassing safety functions. Confirm that the controller identifies the fault, blocks hazardous motion, presents a useful diagnostic, records the event, and requires an intentional recovery sequence.