Table of Contents
Advertisement
XPS-Q8 Controller
Example
The following shows an example of a positioner mapping data file:
PosMapping.txt
-3.00
-2.00
-1.00
0.00
1.00
2.00
3.00
Define the positioner mapping in the stages.ini file:
;--- Backlash
Backlash =0
;--- Positioner mapping
PositionerMappingFileName = PosMapping.txt
PositionerMappingLineNumber = 7
PositionerMappingMaxPositionError = 0.00154
;--- Travels
MinimumTargetPosition =-3
HomePreset =0
MaximumTargetPosition =3
These travel limits must be equal to or be within the positioner's limit positions of
the mapping file (+3 and -3 in the above example).
Use of the functions:
• GroupInitialize(MyGroup)
• GroupHomeSearch(MyGroup)
• GroupMoveAbsolute(MyGroup.Positioner, 0.25)
The mapping file must at least cover the minimum and the maximum travel of the
positioner. It must cover MinimumTargetPosition and MaximumTargetPosition
parameters defined in the stages.ini, section Travels. In the example above, the travel of
the positioner can not be larger than ±3 units, but it can be smaller than this. The units
for the data are the same as defined by EncoderResolution in the stages.ini. The data
reads as follows: the corrected position at position 3.00 units is 2.99846 units (3.00 -
0.00154). Between two data points, the XPS controller performs a linear interpolation of
the error. The corrected position at position 0.25 units is 0.24965 units (0.25 -
0.00140*0.25/1).
Mapping is a function implemented within the controller to correct positioning
errors. Once activated, mapping is transparent to the user. The function
GroupPositionCurrentGet doesn't return 0.24965 (0.25 - 0.00140*0.25/1) but 0.25.
115
-0.00125
-0.00112
-0.00137
0.00000
0.00140
0.00145
0.00154
; unit
; unit
; unit
; unit
NOTE
NOTE
XPSDocumentation V1.4.x (EDH0301En1060 — 10/17)
Motion Tutorial
Advertisement
Table of Contents
