You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.
Current implementation (with #1474 fix) causes motor/motors moving in backlash direction to abort movement immediately after the first Ctrl + C hit (no stop and abort distinction).
On the last follow-up meeting discussion, it has been decided that the most adequate behavior (according to hardware as well as simmilar to SPEC behaviour) is to distinguish between stop and abort (one/two Ctrl + C). First Ctrl + C should stop the movement and apply backlash from current position whereas second should abort the movement immediately (no backlash applied).
Cheers,
Michał
The text was updated successfully, but these errors were encountered:
Hi,
Continuation of #1421 discussion.
Current implementation (with #1474 fix) causes motor/motors moving in backlash direction to abort movement immediately after the first
Ctrl + C
hit (nostop
andabort
distinction).On the last follow-up meeting discussion, it has been decided that the most adequate behavior (according to hardware as well as simmilar to SPEC behaviour) is to distinguish between
stop
andabort
(one/twoCtrl + C
). FirstCtrl + C
should stop the movement and apply backlash from current position whereas second should abort the movement immediately (no backlash applied).Cheers,
Michał
The text was updated successfully, but these errors were encountered: