Difference between revisions of "MC-Basic:axis.OPMODE"

From SoftMC-Wiki
Jump to: navigation, search
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Languages|MC-Basic:axis.OPMODE}}
 
{{MC-Basic
 
{{MC-Basic
 
|SHORT FORM= None
 
|SHORT FORM= None
|SYNTAX= <axis>.OpMode = <value> <br> <lvalue> = OpMode
+
|SYNTAX= <''axis''>.OpMode = <''value''> <br> <lvalue> = OpMode
 
|AVAILABILITY=
 
|AVAILABILITY=
|DESCRIPTION= Axis property . Assigning this property allows you to change the drive operation mode.
 
{{Note| There is a difference between [[Axystems:MC-Basic:axis.DRIVEOPMODE | DRIVEOPMODE ]] and OPMODE. The DRIVEOPMODE does not change  the axis operational mode so the axis does not "know"  that it is in e.g. TORQUE and continues checking position and velocity. Also in this case the TORQUE command will not operate correctly. }}
 
  
{{Note|The command [[Axystems:MC-Basic:axis.DRIVEOPMODE|DRIVEOPMODE]] can also change the drive operation mode, but this is not supported by the motion module.}}
+
|DESCRIPTION= Axis property. Assigning this property allows you to change the drive operation mode.
  
|TYPE= long
 
|RANGE= 0-2<br>
 
 
* 2 - TORQUEMODE<br>
 
* 2 - TORQUEMODE<br>
'''Position-error or acceleration max are NOT checked''',  but vfb < vospd, te < terrmax and tcmd < tmax  are checked as usual.<br>
+
::::'''Position-error or acceleration max are NOT checked''',  but vfb < vospd, te < terrmax and tcmd < tmax  are checked as usual.<br>
 
* 1 - VELOCITYMODE<br>
 
* 1 - VELOCITYMODE<br>
'''Position-error is not NOT checked''' , but: vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax  are checked as usual.<br>
+
::::'''Position-error is not NOT checked''' , but: vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax  are checked as usual.<br>
 
* 0 - POSITIONMODE<br>
 
* 0 - POSITIONMODE<br>
'''All the standard deviation thresholds are checked''': pe < pemax,vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax.<br>
+
::::'''All the standard deviation thresholds are checked''': pe < pemax,vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax.<br>
 +
 
 +
 
 +
{{Note| Note the difference between [[MC-Basic:axis.DRIVEOPMODE| DRIVEOPMODE ]] and OPMODE. <br>
 +
DRIVEOPMODE does not change the axis operational mode, so the axis does not "know"  that it is in e.g. TORQUE and continues checking position and velocity. Also in this case the TORQUE command will not operate correctly.}}
 +
 
 +
 
 +
{{Note|The command [[MC-Basic:axis.DRIVEOPMODE|DRIVEOPMODE]] can also change the drive operation mode, but this is not supported by the motion module.}}
 +
 
 +
 
 +
|TYPE= Long
 +
|RANGE= 0, 1, 2
 +
 
  
 
|UNITS= NA
 
|UNITS= NA
Line 23: Line 32:
 
* Write in CP4 only, Opmode change allowed in disabled state only.<br>
 
* Write in CP4 only, Opmode change allowed in disabled state only.<br>
 
* OPMODE change of an axis belonging to an ''attached group'' is not allowed
 
* OPMODE change of an axis belonging to an ''attached group'' is not allowed
* Modal-Only
+
* Modal only
 
{{Note| At Sercos phase different then 4 query on Opmode will return -1.}}
 
{{Note| At Sercos phase different then 4 query on Opmode will return -1.}}
  
Line 31: Line 40:
 
|SEE ALSO=  
 
|SEE ALSO=  
  
* [[Axystems:MC-Basic:TORQUE|TORQUE ]]
+
* [[MC-Basic:TORQUE|TORQUE ]]
* [[Axystems:MC-Basic:axis.TORQUECHANGERATIO|TORQUECHANGERATIO]]
+
* [[MC-Basic:axis.TORQUECHANGERATIO|TORQUECHANGERATIO]]
* [[Axystems:MC-Basic:axis.TORQUECHANGERATIOMAX |TORQUECHANGERATIOMAX]]
+
* [[MC-Basic:axis.TORQUECHANGERATIOMAX|TORQUECHANGERATIOMAX]]
* [[Axystems:MC-Basic:axis.OPMODEMAP|OPMODEMAP ]]
+
* [[MC-Basic:axis.OPMODEMAP|OPMODEMAP ]]
* [[Axystems:MC-Basic:axis.SUMTORQUE|SUMTORQUE ]]
+
* [[MC-Basic:axis.SUMTORQUE|SUMTORQUE ]]
* [[Axystems:OperationalModes| Operational Modes]]
+
* [[OperationalModes| Operational Modes]]
* [[AXY:SERCOS_Operation_Modes|SERCOS OPMODEs]]
+
* [[SERCOS Operation Modes|SERCOS OPMODEs]]
* [[Axystems:MC-Basic:axis.DRIVEOPMODE | DRIVEOPMODE ]]
+
* [[MC-Basic:axis.DRIVEOPMODE| DRIVEOPMODE ]]
  
 
<br><br>
 
<br><br>
Line 44: Line 53:
 
* ''[[AXY:Operational_Modes | Operational Modes]]''
 
* ''[[AXY:Operational_Modes | Operational Modes]]''
 
}}
 
}}
[[Category:Axystems:OperationalModes]]
+
[[Category:OperationalModes]]

Latest revision as of 02:30, 20 April 2017

Language: English  • 中文(简体)‎

Axis property. Assigning this property allows you to change the drive operation mode.

  • 2 - TORQUEMODE
Position-error or acceleration max are NOT checked, but vfb < vospd, te < terrmax and tcmd < tmax are checked as usual.
  • 1 - VELOCITYMODE
Position-error is not NOT checked , but: vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax are checked as usual.
  • 0 - POSITIONMODE
All the standard deviation thresholds are checked: pe < pemax,vfb < vospd, te < terrmax, acmd < amax and tcmd < tmax.


NOTE-Info.svgNOTE
Note the difference between DRIVEOPMODE and OPMODE.
DRIVEOPMODE does not change the axis operational mode, so the axis does not "know" that it is in e.g. TORQUE and continues checking position and velocity. Also in this case the TORQUE command will not operate correctly.


NOTE-Info.svgNOTE
The command DRIVEOPMODE can also change the drive operation mode, but this is not supported by the motion module.

Short form

None

Syntax

<axis>.OpMode = <value>
<lvalue> = OpMode

Type

Long

Range

0, 1, 2

Units

NA

Default

2

Scope

Task, Terminal

Limitations

  • Write in CP4 only, Opmode change allowed in disabled state only.
  • OPMODE change of an axis belonging to an attached group is not allowed
  • Modal only
NOTE-Info.svgNOTE
At Sercos phase different then 4 query on Opmode will return -1.

Examples

Ax1.OpMode = 2
i = Ax1.OpMode

See Also