Difference between revisions of "Endless Axes"
(→endless axes) |
(→drive (SERCOS) limitations) |
||
Line 6: | Line 6: | ||
== drive (SERCOS) limitations == | == drive (SERCOS) limitations == | ||
− | However, the drive-controller communication uses much smaller range it's position data is transferred using 32-bits data so the limits of internal drive position units are '''[-2 <sup> 31 </sup>,+2 <sup> 31 </sup>]'''. This is visible on properties: [[Axystems:MC-Basic:axis.COUNTFEEDBACK|CCFB]], [[Axystems:MC-Basic:axis.COUNTCOMMAND|CCMD]], and [[Axystems:MC-Basic:axis.COUNTEXTERNAL|CEXT]]. | + | However, the drive-controller communication uses much smaller range it's position data is transferred using 32-bits data so the limits of internal drive position units are '''[-2 <sup> 31 </sup>,+2 <sup> 31 </sup>]'''. This is visible on properties: [[Axystems:MC-Basic:axis.COUNTFEEDBACK|CCFB]], [[Axystems:MC-Basic:axis.COUNTCOMMAND|CCMD]], and [[Axystems:MC-Basic:axis.COUNTEXTERNAL|CEXT]]. They are all integer type, 32-bit variables and as such have limited values. |
== AMCS position variables == | == AMCS position variables == |
Revision as of 05:23, 5 October 2011
Contents
Infinite axes
endless axes
Axes that can theoretically move endlessly in ether direction are supported in AMCS system. The limits of such axes are actually the range of the double-floating point format (-1.79769e+308,1.79769e+308) which practically gives endless axes operation.
drive (SERCOS) limitations
However, the drive-controller communication uses much smaller range it's position data is transferred using 32-bits data so the limits of internal drive position units are [-2 31 ,+2 31 ]. This is visible on properties: CCFB, CCMD, and CEXT. They are all integer type, 32-bit variables and as such have limited values.
AMCS position variables
The system automatically extends range position variables (pcmd,pfb,pext) to [mindouble,maxdouble] by counting the number of cycles of 32-bit range. Each time the position feedback (or external) passes 31 bit limit internal counter of revolutions is increased (decreased). So the related PFB values does not exhibit any discontinuities.
the revoultion counter can be reset by:
- accessing position factor i.e. "pfac = pfac" or any other assignment.
- calling user function: MOT_RESET_ROLLOVER or MOT_RESET_EXROLLOVER