Difference between revisions of "MC-Basic:robot.Persistent"
(Replaced <gallery> tags with thumbs) |
|||
| (21 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Languages|MC-Basic:robot.Persistent}} | ||
{{MC-Basic | {{MC-Basic | ||
|SHORT FORM= | |SHORT FORM= | ||
| Line 6: | Line 7: | ||
|AVAILABILITY= | |AVAILABILITY= | ||
| − | 4.10.x | + | Since Version 4.10.x |
|DESCRIPTION= | |DESCRIPTION= | ||
| − | If | + | Every element(robot/group/axis) in ControlStudio needs to be attached in order to be moved or accessed. Only one task can attach an element at same time using |
| + | [[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 [[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 [[MC-Basic:element.RTKActive| active]] (producing Motion Bus commands (pcm,vcmd, drive status) and reading from it, checking position error, etc.) or [[MC-Basic:element.RTKActive| suspended]]. A single axis is [[MC-Basic:element.RTKActive| active]] by default and deactivated only when a group that it belongs to is attached. | ||
| + | |||
| + | [[File:AXY;Peristant Axis.png|thumb|right|sub|300x300px|axis]] | ||
| + | [[File:AXY;Peristant Group.png|thumb|right|sub|300x300px|group]] | ||
| + | |||
| + | |||
| + | '''If <robot>.persistent 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 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. | * Trying to attach another group/robot that has a common axis with an active group will return and error. | ||
| + | |||
| + | ''What happens is that if <robot>.persistent is on, the group detaches is only partially. It means the RTK is not suspended but another task can issue an attachment.'' | ||
|TYPE= | |TYPE= | ||
| Line 31: | Line 43: | ||
|LIMITATIONS= | |LIMITATIONS= | ||
| − | + | Modal only, Read-Write | |
|EXAMPLE= | |EXAMPLE= | ||
| Line 37: | Line 49: | ||
|SEE ALSO= | |SEE ALSO= | ||
| − | * [[ | + | * [[MC-Basic:element.RTKActive| robot.RTKActive]] |
}} | }} | ||
| − | [[Category | + | |
| + | [[Category:PLC]] | ||
Latest revision as of 03:46, 19 April 2022
| Language: | English • 中文（简体） |
|---|
Every element(robot/group/axis) in ControlStudio 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 active by default and deactivated only when a group that it belongs to is attached.
If <robot>.persistent 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.
What happens is that if <robot>.persistent is on, the group detaches is only partially. It means the RTK is not suspended but another task can issue an attachment.
Syntax
<group/robot>.persistent
Availability
Since Version 4.10.x
Type
Long
Range
0/1
Units
N/A
Default
0
Scope
Task or Terminal
Limitations
Modal only, Read-Write
Examples
SpeedPicker.Persistent = 1