Difference between revisions of "MC-Basic:robot.Persistent"
Line 9: | Line 9: | ||
|DESCRIPTION= | |DESCRIPTION= | ||
+ | |||
+ | Every element(robot/group/axis) in the "Aico.Control" system needs to be attached in order to be moved or accessed. Only one task can attach an element at same time using | ||
+ | [[Axystems:MC-Basic:ATTACH|attach]] command. Terminal dos not need to use attach statement, every element is automatically attached by a terminal when a motion command is started and automatically detached when the motion is finished. In case of a task element is detached only when the explicit [[Axystems:MC-Basic:DETACH|detach]] command is given or the program ends. | ||
+ | |||
+ | In addition to attach operation there is also an RTK (Real-Time-Kernel) task activation related to it. Every element has an associated RTK task to it. It can be active (producing Motion Bus commands (pcm,vcmd, drive status) and reading from it, checking position error, etc.) or suspended. A single axis is acitve by defulat and deactivated only when a group that it belongs to is attached. | ||
If this flag is on the group's RTK remains active even after detaching it from a task/terminal. | If this flag is on the group's RTK remains active even after detaching it from a task/terminal. |
Revision as of 11:56, 22 October 2012
Every element(robot/group/axis) in the "Aico.Control" system needs to be attached in order to be moved or accessed. Only one task can attach an element at same time using attach command. Terminal dos not need to use attach statement, every element is automatically attached by a terminal when a motion command is started and automatically detached when the motion is finished. In case of a task element is detached only when the explicit detach command is given or the program ends.
In addition to attach operation there is also an RTK (Real-Time-Kernel) task activation related to it. Every element has an associated RTK task to it. It can be active (producing Motion Bus commands (pcm,vcmd, drive status) and reading from it, checking position error, etc.) or suspended. A single axis is acitve by defulat and deactivated only when a group that it belongs to is attached.
If this flag is on the group's RTK remains active even after detaching it from a task/terminal.
- Trying to attach an axis belonging to an active group will return error
- Trying to attach another group/robot that has a common axis with an active group will return and error.
Syntax
<group/robot>.persistent
Availability
4.10.x and up
Type
Long
Range
0/1
Units
N/A
Default
0
Scope
Task or Terminal
Examples
SpeedPicker.Persistent = 1