some beautification
ok, this is more or less the motion planning …

or at least a beginning
adding some fixed point math to the mix
some minor corrections (start interrupt)
ok, let's start slowy … 

… just moving the motors according to the queue
is this enough to move?? (adding output to check it )
we need some more considerable command lenght - and some min/max values
dealing with all those dicts and lists is complicated …
correcting output
hmm optional motor decoding works a tad different …
it might come in handy to have a dedicated start/stop print method
we need to start if the buffer is full and not overfill it …
cleaning up the queue at init
at least it should move now … so why doesn't it do it??
this was gettin' too hot
pretty printing
acceleration values are configured …
we need to configure the acceleration settings

and have to test for reasonable defaults
after some corrections it works

to wait for movements
pretty print