Rockwell Automation 1398-PDM-xxx IQ Master Version 3.2.4 for IA-2000 and IQ-5000 Positioning Drive Modules, IQ-55 - Manual (Page 87)

Run Menu • Extended Debug 65
Publication 1398-PM601A-EN-P — October 2000
MENUS
run selected debug tools and methods.
Auto Execution Delay
Sets the time delay in seconds to be inserted between the execution of source code lines. Typical values
for this parameter are 1 to 3 seconds typically. If set to 0 (zero), the auto mode executes at the same
speed as the Trace debugger mode. The range of values for this parameter is 0 to 65.5 seconds.
Active Trace Paths
Active Trace Path check boxes filter specific debug information sent by the IQ to IQ Master when
debugging a source program. Execution modes that display an execution trace bar in the source code
window (e.g., Trace, Auto, and Pause), require the active trace path to debug a specific code thread. For
example, if an application has a main program loop, scanned event #1 and XKey #2, check the Main
Program, Scanned Event 1, and X2 Key Routine check boxes. If the application executes code that does
not have its associated active trace path defined, IQ Master debugger software will not respond to the
executing code and the debug information being sent by the IQ. All application code executes on the IQ
even when no active trace path boxes are checked.
Enabling active trace paths for specific thread execution is used primarily when executing in the Auto
or Trace debugger modes. In these modes, you have the ability to visually see trace execution for spe-
cific code areas of the application.
When in doubt as to the proper settings for the active trace path check boxes, simply check them all.
Debugger Thread
Debugger Thread radio buttons target specific execution threads for debugging commands. The IQ exe-
cutes its application programs in a multi threaded programming environment. Under certain situations,
it may be beneficial for you to debug the main program only. In another application, you may want to
set breakpoints in scanned event code to debug them. The Debugger Thread radio buttons indepen-
dently specify which execution thread(s) to command.
All Threads should be selected if you are new to IQ multithreaded programming. This setting allows
you gain experience with how the main program, scanned events, and XKey routines execute in relation
to one another.
Special attention is required when not using the “All Threads” command target, pay particular attention
to setting break points in code areas that are not being sent debugger commands. For example: If a
breakpoint is set in scanned event #1 and the main program is set as the target for debugger commands,
the scanned event could hit the defined breakpoint while debugging the main program thread. In this
case, all scanned event execution stops until commanded to start execution again.
Points to keep in mind when debugging in the IQ's multi threaded environment include:
• Users unexperienced with IQ multi threaded programming should select the “All Threads” radio
button.
• When initially starting a program all execution threads receive the first debugger command issued,
regardless of the debugger command thread selected.