Describe Each Action In Pseudocode - Allen-Bradley Logix 5000 Programming Manual

Design a sequential function chart
If you want to
Determine how many times an action has
become active
Use one tag for the various status bits of
this action
Describe each action in
pseudocode
Then select or set this Data type
member
Count DINT
Status DINT
To organize the logic for an action, first you describe the action in pseudocode.
•
Use a series of short statements that describe what should happen.
•
Use terms or symbols, such as: if, then, otherwise, until, and, or, =, >, <.
•
Sequence the statements in the order that they should execute.
•
If necessary, name the conditions to check first (the "when to act" first) and
then the action to take second (the "what to do" second).
Enter the pseudocode into the body of the action.
•
Refine the pseudocode so it executes as structured text.
•
Use the pseudocode to design your logic and leave the pseudocode as
comments. Since all structured text comments download to the controller,
your pseudocode is always available as documentation for the action.
To convert the pseudocode to structured text comments, add these comment
symbols.
For a comment
On a single line
That spans more than one line
Rockwell Automation Publication 1756-PM006I-EN-P - February 2018
Details
This is not a count of scans of the action.
• The count increments each time the action becomes active.
• It increments again only after the action goes inactive and then active again.
• The count resets only if you configure the SFC to restart at the initial step. With that
configuration, it resets when the controller changes from program mode to run
mode.
For this member Use this bit
Q 30
A 31
Use one of these formats
//comment
(
*start of comment... end of
)
comment*
/*start of comment... end of
comment*/
Chapter 1
31