SMARACT - problems with linear stages
Today I played with a linear smaract stage (rotations seem to work fine) on ID01.
seems like at the end of the move bliss does not really keep the final value in the setting but a value that was read slightly before.
- I have tested with different velocities and accelerations ... that did not have a big impact...
- Seems like the
axis.tolerance
may play a role ? is it possible that there is a confusion about the unit of tolerance for this controller? ... I don't really see why though...
BLISS [36]: smy.sync_hard()
BLISS [37]: umvr(smy,1000)
DEBUG 2020-10-21 15:30:28,429 global.controllers.SmarAct.smy: get_motion: user_target_pos=1000, relative=True
Moving smy from -4505.193 to -3505.193
smy
-3505.194
BLISS [38]: umvr(smy,1000)
DEBUG 2020-10-21 15:30:33,141 global.controllers.SmarAct.smy: get_motion: user_target_pos=1000, relative=True
Moving smy from -3505.194 to -2505.193
smy
-2505.196
BLISS [39]: umvr(smy,1000)
DEBUG 2020-10-21 15:30:36,189 global.controllers.SmarAct.smy: get_motion: user_target_pos=1000, relative=True
!!! === RuntimeError: smy: discrepancy between dial (-2505.196000) and controller position (-2505.193000), aborting === !!! ( for more details type cmd 'last_error' )
BLISS [40]: umvr(smy,1000)
DEBUG 2020-10-21 15:30:37,141 global.controllers.SmarAct.smy: get_motion: user_target_pos=1000, relative=True
!!! === RuntimeError: smy: discrepancy between dial (-2505.196000) and controller position (-2505.193000), aborting === !!! ( for more details type cmd 'last_error' )
currently there is smy
installed on nano1
that can be used without danger remotely (umvr +/- in steps of 1000 should be good to see the problem).