FiveD_on_Arduino
FiveD_on_Arduino copied to clipboard
Pull request1
It's written in the commit comment, but basically I noticed that if I ran two moves: G1X10 G1X10 I could hear the steppers hesitate between the moves. This change removes that hesitation, at the price of a possibly much longer-running timer interrupt.
This is because next_move is now tail-recursive when there are zero step moves queued.
Also it's not yet perfect, see commit notes for my reflections on the timer status across moves.
Defining "bang-bang" will allow debugging to be built for a 168 chip. If we're not using endstops, we shouldn't require that they be defined.
This was closed? Did I do that by mistake or did somebody mean to close this pull request?
hi, is this still relevant to the current codebase? Without my motors set up I can't tell
I don't know. With my laptop broken I can't tell :)