Difference between revisions of "EtherCAT:EC SET MOTION OPMODE"
m |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Languages|EtherCAT:EC_SET_MOTION_OPMODE}} | ||
{{Template:EtherCAT-Function | {{Template:EtherCAT-Function | ||
| Line 19: | Line 20: | ||
|RETURN VALUE= | |RETURN VALUE= | ||
Void | Void | ||
| + | |||
| + | |LIMITATIONS= | ||
| + | In case of switching to TORQUEMODE the axis must be attached to the calling task | ||
|EXCEPTIONS= | |EXCEPTIONS= | ||
Latest revision as of 18:01, 6 May 2017
| Language: | English • 中文（简体） |
|---|
This subroutine sets the axis and the drive to a motion operational mode.
In EtherCAT it is not sufficient to set the axis opmode property. The drive opmode must also be set.
The value of object 0x6060 is written to the drive via PDO or SDO according to the new opmode.
Object 0x6061 confirms whether the opmode is correctly set.
 | IMPORTANT |
| If the axis is set to Torque Mode, the property sumTorque is set to ON by default! |
Input
Generic axis
New opmode - POSITIONMODE, VELOCITYMODE or TORQUEMODE
Output
None
Return Value
Void
Declaration
Public Sub EC_SET_MOTION_OPMODE(Ax as generic axis, byval new_opmode as long)
Syntax
call EC_SET_MOTION_OPMODE(<Axis>, <new opmode>)
Limitations
In case of switching to TORQUEMODE the axis must be attached to the calling task
Exceptions
This subroutine throws the exception EC_OPMODE_CHANGE_FAILED if the drive was not successfully set to the desired opmode, or if the argument <new opmode> is not valid.
Examples
call EC_SET_MOTION_OPMODE(MLeader, VelocityMode)