Non-zero discrepancy on axis after a reset_closed_loop
We observed on BM32 runtime errors due to a discrepancy on IcePap axes after a call to reset_closed_loop.
After some investigations we identified the origin of the problem: the sync_hard (on axis controlled by IcePaps) method get the current position using the ?FPOS command. For axes with 'autopower' set to False the call to sync_hard happens just after the set_position, and the position given by FPOS is not always updated to the new value.