Difference between revisions of "OperationalModes"
(Created page with "= Operational Modes =") |
|||
Line 1: | Line 1: | ||
− | = | + | {{Axystems:Template:Temporary-Specification}} |
+ | |||
+ | ==Enabling user working in different operation modes of the drive== | ||
+ | |||
+ | User selects the operation-mode using the OpMode command.<br> | ||
+ | <pre> | ||
+ | OpMode <axis> {POSITIONMODE|VELOCITYMODE|TORQUEMODE} | ||
+ | </pre> | ||
+ | <br> | ||
+ | Command will change the drive (and axis!) opmode to the given value using the opmode bits of the SERCOS drive status word. | ||
+ | |||
+ | * Default state is POSITIONMODE (as today). All the standard deviation thresholds are checked: '''pe < pemax''','''vfb < vospd''', '''te < terrmax''', '''acmd < amax''' and '''[[Axystems:MC-Basic:axis.TORQUECOMMAND|tcmd]] < tmax'''. | ||
+ | |||
+ | * In VELOCITYMODE axis will '''NOT''' check '''position-error''', but will check: '''vfb < vospd''', '''te < terrmax''', '''acmd < amax''' and '''tcmd < tmax'''. | ||
+ | |||
+ | * In TORQUEMODE axis will '''NOT''' check '''position-error''' or acceleration max, but will check: '''vfb < vospd''', '''te < terrmax''' and '''[[Axystems:MC-Basic:axis.TORQUECOMMAND|tcmd]] < tmax'''. | ||
+ | |||
+ | ==Torque Interpolation== | ||
+ | New torque interpolation command will be implemented: | ||
+ | <pre> | ||
+ | TORQUE <axis> tfinal | ||
+ | </pre><br> | ||
+ | This command interpolate the tcmd from its initial value to the given tfinal according to the profile parameters defined. | ||
+ | |||
+ | == Stopping == | ||
+ | |||
+ | * STOP command in TORQUEMODE mode will '''''forcibly switch drive opmode to VELOCTYMODE''''' producing the deceleration profile from the current VFB value t zero. The same behavior will be implemend for both user-entred stop command and the system-generated stop commands like: velocity-over speed error, tcmd > tmax, te>temax. | ||
+ | |||
+ | * New command [[Axystems:MC-Basic:HOLD|HOLD <Axis>]] will cause axis to stop interpolating torque. New property [[Axystems:MC-Basic:axis.HOLDTYPE|<axis>.HoldType]] will give the user option to select between keeping the stopped [[Axystems:MC-Basic:axis.TORQUECOMMAND|TCMD]] value or reducing it to zero. In bot cases the original TORQUEMODE will be not changed. | ||
+ | |||
+ | <pre> | ||
+ | HOLD <axis> | ||
+ | </pre> | ||
+ | |||
+ | ==Limitations and side effects== | ||
+ | |||
+ | {{Note|Opmode changes are allowed in disabled drive state only.}} | ||
+ | {{Note|If an axis belongs to a group it's opmode can not be changed separately.This means:<br> | ||
+ | # opmode change is not allowed if an axis belongs to an attached group <br> | ||
+ | # '''a group can not be attached (implicitly or explicitly) if it consist of axes with different opmodes.'''}} | ||
+ | {{Note|MOVE <axis> and JOG <axis> commands are producing [[Axystems:MC-Basic:axis.POSITIONCOMMAND|PCMD]],[[Axystems:MC-Basic:axis.VELOCITYCOMMAND|VCMD]]and [[Axystems:MC-Basic:axis.TORQUEADDCOMMAND|TADDCMD]] (if DynamicModel is turned on). The TCMD value during these types of motion remains unchanged.}} | ||
+ | {{Note| [[Axystems:MC-Basic:TORQUE|TORQUE <axis>]] command is affecting [[Axystems:MC-Basic:axis.POSITIONCOMMAND|PCMD]], [[Axystems:MC-Basic:axis.VELOCITYCOMMAND|VCMD]], [[Axystems:MC-Basic:axis.TORQUEADDCOMMAND|TADDCMD]] values of the axis (their values are kept unchanged).Only the [[Axystems:MC-Basic:axis.TORQUECOMMAND|TCMD]] is interpolated. }} | ||
+ | |||
+ | {{Note| We assume dirves adds the [[Axystems:MC-Basic:axis.TORQUECOMMAND|TCMD]](IDN80) and [[Axystems:MC-Basic:axis.TORQUEADDCOMMAND|TADDCMD]](IDN81) in all OPMODEs. In case it is not so <nowiki><axis>.SumTorqe=1</nowiki> will cause the value of [[Axystems:MC-Basic:axis.TORQUEADDCOMMAND|TADDCMD]] to be added to [[Axystems:MC-Basic:axis.TORQUECOMMAND|TCMD]]:<br> | ||
+ | [[Axystems:MC-Basic:axis.TORQUECOMMAND|TCMD]] <nowiki>=</nowiki> [[Axystems:MC-Basic:axis.TORQUECOMMAND|TCMD]] + [[Axystems:MC-Basic:axis.TORQUEADDCOMMAND|TADDCMD]] | ||
+ | }} | ||
+ | |||
+ | {{Note| TORQUEMODE of an axis is not influencing camming/gearing operation.<br> | ||
+ | The interpolated torque values of a master axis will be '''NOT''' transferred to slave axes.<br> | ||
+ | Slave that is in TORQUEMODE continues to be slaved affecting only its PCMD and VCMD values.}} | ||
+ | |||
+ | ==See also:== | ||
+ | {{Bugzilla|5564}}<br> | ||
+ | [[Axystems:MC-Basic:axis.DYNAMICMODEL|DYNAMICMODEL]] |
Revision as of 13:56, 10 November 2011
Axystems:Template:Temporary-Specification
Contents
Enabling user working in different operation modes of the drive
User selects the operation-mode using the OpMode command.
OpMode <axis> {POSITIONMODE|VELOCITYMODE|TORQUEMODE}
Command will change the drive (and axis!) opmode to the given value using the opmode bits of the SERCOS drive status word.
- Default state is POSITIONMODE (as today). All the standard deviation thresholds are checked: pe < pemax,vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax.
- In VELOCITYMODE axis will NOT check position-error, but will check: vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax.
- In TORQUEMODE axis will NOT check position-error or acceleration max, but will check: vfb < vospd, te < terrmax and tcmd < tmax.
Torque Interpolation
New torque interpolation command will be implemented:
TORQUE <axis> tfinal
This command interpolate the tcmd from its initial value to the given tfinal according to the profile parameters defined.
Stopping
- STOP command in TORQUEMODE mode will forcibly switch drive opmode to VELOCTYMODE producing the deceleration profile from the current VFB value t zero. The same behavior will be implemend for both user-entred stop command and the system-generated stop commands like: velocity-over speed error, tcmd > tmax, te>temax.
- New command HOLD <Axis> will cause axis to stop interpolating torque. New property <axis>.HoldType will give the user option to select between keeping the stopped TCMD value or reducing it to zero. In bot cases the original TORQUEMODE will be not changed.
HOLD <axis>
Limitations and side effects
NOTE | |
Opmode changes are allowed in disabled drive state only. |
NOTE | |
If an axis belongs to a group it's opmode can not be changed separately.This means:
|
NOTE | |
MOVE <axis> and JOG <axis> commands are producing PCMD,VCMDand TADDCMD (if DynamicModel is turned on). The TCMD value during these types of motion remains unchanged. |
NOTE | |
TORQUE <axis> command is affecting PCMD, VCMD, TADDCMD values of the axis (their values are kept unchanged).Only the TCMD is interpolated. |
NOTE | |
We assume dirves adds the TCMD(IDN80) and TADDCMD(IDN81) in all OPMODEs. In case it is not so <axis>.SumTorqe=1 will cause the value of TADDCMD to be added to TCMD: |
NOTE | |
TORQUEMODE of an axis is not influencing camming/gearing operation. The interpolated torque values of a master axis will be NOT transferred to slave axes. |