Rockwell Automation 193 Drives and Motion Accelerator Toolkit Quick Start - Manual (Page 222)

222 Rockwell Automation Publication IASIMP-QS019E-EN-P - August 2013
Appendix B Logic Module Customization
Tag and Logic Modification Recommendations
This table contains some of the common modifications to consider for the state machine. The modifications and
corresponding recommended actions are meant to highlight the more significant updates that are needed.
Additional updates could also be necessary.
Modification Description Recommended Actions
State Names
Simple change to the state name. The number of states and relationship
between states remain unaltered.
Example: Change RUNNING state to PRODUCING.
• Modify the UDT_MachState data type.
• Update the corresponding MachineSTATE_AOI embedded state
name. (1)
• Update the HMI file as needed. (2)
(1) Refer to State Display Tag Modifications, on page 223 , for more information.
(2) Refer to Chapter 5, on page 101 , for more information on the HMI terminal layout and function.
Command Names
Simple change to the command name. Their intended function remains
unaltered.
Example: Change RESET command to INITIALIZE.
• Modify the UDT_MachCmd data type.
• Update the HMI file as needed.
(2)
Mode Names
Simple change to the mode name. The number of modes and their
intended function remain unaltered.
Example: Change OPERATOR mode to MANUAL.
• Modify the UDT_MachMode data type.
• Update the HMI file as needed.
(2)
Add/Remove States
Adding additional states or removing states. The operation of the state
machine will change to accommodate an increase or decrease in states.
Example: Add a new state called PAUSED.
• Modify the UDT_MachState data type.
• Modify the machine module monitor and control routines as needed.
• If necessary, add/remove commands to support the changes in the
states. Refer to Add/Remove Commands modification.
• If new states were added, then update the corresponding
MachineSTATE_AOI embedded state name.
• Update the HMI file as needed.
(2)
Add/Remove Commands
Adding additional commands or removing commands. Typically,
increases or decreases in commands are required to support
corresponding changes (+/-) with states.
Example: Add a new command called PAUSE to support a new state
called PAUSED.
• Modify the UDT_MachCmd data type.
• Modify the machine module monitor and control routines as needed.
• Modify the application and device modules monitor and control
routines as needed. Typically, changes in commands require changes
in the module status (UDT_AppStatus and UDT_ModuleStatus). For
example, if you add a new command called PAUSE, then you should
add a new status response from the modules called Paused.
• Update the HMI file as needed.
(2)
Add/Remove Modes
Adding additional modes or removing modes.
Example: Add a new mode called THREAD.
• Modify the UDT_MachMode data type.
• Modify the machine module monitor and control routines as needed.
• Modify the application and device modules monitor and control
routines as needed.
• Update the HMI file as needed.
(2)
State-to-State Relationships
Changing the conditions that enable transitions between states.
Example: Update logic to transition from STOPPED directly to STARTING,
bypassing IDLE.
• Modify the machine module monitor and control routines as needed.
• Modify the application and device modules monitor and control
routines as needed.
• Update the HMI file as needed.
(2)