kwince
commented
3 years ago I feel that the way the dog system works is that your input immediately stores some amount of impulse into it that it has to dissipate with travel. This would be count exactly opposite what I would want I would want the movement to begin to accelerate and the minute you let go it would destroy all that it had accumulated and do Max deceleration
On Thu, Sep 17, 2020, 3:10 PM DougCoffland notifications@github.com wrote:
This issue occurs when jogging from the "Jog" tab on the "Control" page and with the "step" checkbox active. If you click the blue up arrow or the blue down arrow to jog the "Z" axis, it takes off and does not stop. This only seems to happen on the outermost ring (labelled 100). The inner rings seem to jog correctly.
This can be a real problem because you have to click the stop button to stop it before it runs into the top end stop going up or drives the bit into the table surface going down. Unfortunately, the stop button is not present on the "Jog" tab, so you have to change screens. By that time the crash has probably already occurred.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/buildbotics/bbctrl-firmware/issues/276, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADFKN5KBYXJ4U42GONPDRDSGKCL5ANCNFSM4RRCNFSQ .
DougCoffland
This issue occurs when jogging from the "Jog" tab on the "Control" page and with the "step" checkbox active. If you click the blue up arrow or the blue down arrow to jog the "Z" axis, it takes off and does not stop. This only seems to happen on the outermost ring (labelled 100). The inner rings seem to jog correctly.
This can be a real problem because you have to click the stop button to stop it before it runs into the top end stop going up or drives the bit into the table surface going down. Unfortunately, the stop button is not present on the "Jog" tab, so you have to change screens. By that time the crash has probably already occurred.