Aerotech UNIDEX 600 Series, Руководство пользователя

Страница: 301 / 354

Parameters U600 User’s Guide
C-76
Aerotech, Inc.
Version 1.4
MFO monitoring, watch monitoring (see ON and ONGOSUB CNC commands), and
immediate command execution. Normally, the execution of tasks is performed as follows:
FOR EACH TASK (4)
Generate an interrupt back to PC, as required.
Check ESTOP, MFO, MSO, and feedhold, react as required.
Monitor spindle and asynchronous motion (if any).
Test ONGOSUBS and ON’s, execute the indicated action, as required.
Test for RIAction1 or ROAction1 commands.
Execute canned functions, if commanded to.
Execute external jogging, if commanded to.
Execute immediate command (if any requested).
Execute the next CNC statement (if that CNC is running a program), or if a statement
was still running (like a G1, or G4) then check to see if its finished or not.
END FOR
The ExecuteNumLines parameter can be used to change the above behavior as follows.
Note, that the default value for ExecuteNumLines is one.
If ExecuteNumLines = 0 for a task, then that task is inactive (none of the chores
listed above, including program execution and ESTOP monitoring, are executed
for that task. Setting ExecuteNumLines to 0 for a given task, disables that task,
significantly increasing the execution speed of the other tasks. However, when
ExecuteNumLines is zero, none of the steps listed in the “for loop” above, are
executed for that task.
If ExecuteNumLines > 0 for a task, then that task will execute all the steps in the
"For Loop" above, and try to execute that many lines in the CNC program,
before giving control to the next task. However, if an error occurs at any time
during CNC program execution, or the statement can not be completed
immediately (a G1, G2, G3, G4, M3, etc. or any other statement requiring a
certain amount of time), then that task will stop trying to execute lines and
release execution to the next task. Setting ExecuteNumLines > 0 for a given task,
increases the execution speed of that task relative to the other tasks, if it is
executing CNC statements that can be completed immediately.
If ExecuteNumLines < 0 for a task, then it will behave as described for
ExecuteNumLines > 0 (with the number of lines to execute being the absolute
value of the parameter value), except, that it will not stop executing for a
statement that can not be completed immediately (a G1, G2, G3, G4, M3, etc.).
These settings are more drastic than their corresponding positive values, and will
increase the execution speed of the current task. However, negative values are
drastic, and high negative values will starve everything else, including library
calling applications like the MMI600. High negative values will cause the
MMI600 to freeze up.
The user should be warned that changing this parameter (especially to negative values)
can adversely effect the performance of any critical controller function, such as I/O or
ESTOP monitoring, as well as the update rate of the positions in the UNIDEX 600 MMI.
The user must understand the tradeoffs involved, and be willing to accept reduced
performance is some areas, in order to obtain the increased performance in others.