Thank you roulv for the clarification, haven't heard of Cartesian positioning accuracy before and it doesn't explain the issue very well.
Shame that Flexpicker don't have the Absolute accuracy option.
If I were to generate a map of Cartesian Position vs Actual Position, will it be possible to put it back within the software for corrections?
Or is there alternative ways to improve Cartesian Positioning Accuracy? that could be implemented ourselves or using 3rd parties (vision, external calibration...)