Difference between revisions of "MC-Basic:SYNCALL"
| Line 35: | Line 35: | ||
Within a task, the specified ''<element> ''must be attached | Within a task, the specified ''<element> ''must be attached | ||
<br/>{{Note| Movement that has '''''vFinal > 0''''' can't be used with '''''SyncAll'''''.}} | <br/>{{Note| Movement that has '''''vFinal > 0''''' can't be used with '''''SyncAll'''''.}} | ||
| − | <br/>{{Note| Movement that starts with SyncAll can't be blend with the previous movement. It can be blend with the next movement only if [[ | + | <br/>{{Note| Movement that starts with SyncAll can't be blend with the previous movement. It can be blend with the next movement only if [[MC-Basic:group.BLENDINGMETHOD|BlendingMethod ]] is from type '''''SP''''' (supper Position).}} |
|EXAMPLE= | |EXAMPLE= | ||
Revision as of 08:50, 22 May 2014
This command begins executing the specified <element>s with pending motion commands. Motion commands pend by setting the STARTTYPE to SYNC and giving the motion command.
Similar to SyncStart command. The main difference is that both initial and final position of all elements in the given list are synchronized.
Syntax
SyncAll <element> {<element>}*
Availability
From 4.11.x
Scope
Task or Terminal
Limitations
Within a task, the specified <element> must be attached
 | NOTE |
| Movement that has vFinal > 0 can't be used with SyncAll. |
| NOTE |
| Movement that starts with SyncAll can't be blend with the previous movement. It can be blend with the next movement only if BlendingMethod is from type SP (supper Position). |
Examples
SyncAll SCARA PUMA DELTA