3 pausing the edito, 4 about power flow, 3 pausing the editor – Rockwell Automation AutoMax Enhanced Ladder Editor User Manual
Page 51

5Ć5
5.3
Pausing the Editor
Because the Online Task Manager and online programs in the Editor
use the same communication channel, you must place the Editor in
the Paused state before you can use the Online Task Manager. The
programs continue to run in the Processor, but their display in a
program window is not updated.
I
MPORTANT
Before pausing the Editor's online program windows, you might
want to commit any pending changes. All pending changes are lost
once an online program is paused and then removed from the
paused state.
Any trigger information is also lost when you remove online program
windows from the pause state.
To pause or unĆpause the Editor
D From the Online menu, choose Pause.
or
D Click on
While online programs are paused, the status bar is blank and the
word Paused" appears in the programs' title bar.
Remove the programs from the paused state when the
communication port is again available. The Editor reĆestablishes
communication to all available ports and notifies you when a
connection is not available. If a connection is not available, the
online programs stay paused.
For more information about the paused state, see section 5.1.
5.4
About Power Flow
Power flow indicates the rungs and instructions that are executing in
an online program. It is shown as a bar of color that highlights wires
that are connected together. You can define the color of power flow
using the Colors Option tab of program properties.
The state of a variable is shown as a solid block of color in the
contact. For positive transition contacts (PTI), the block of color is
shown when the contact is true, but power flow from the contact is
shown only during the scan where the transition is true. The same
concept applies to the negative transition contacts (NTI). The block
of color in an NTI is shown when the contact is false, but the power
flow from the contact is shown only during the scan in which the
transition is true.
Hatch marks in the rung status area identify rungs that are not
executing. For nonĆexecuting rungs, the power flow and last state
information you see are those from the last time the rung executed
since you started monitoring the online program. Factors causing
rungs not to execute are:
D They could be skipped via a Jump instruction.
D The program is executed based on an event.
D The program is stopped.
D The scan time of the program is very long.