Here’s the thread that got the same behavior Real time control of a Voron 2.4 using a gamepad
that I couldn’t link earlier due to limit for newcombers. klippy.log for experiment 2 klippy.log (21.3 KB)
I’m painfully aware that a CPU and MCU communicating via 12Mbit/s UART isn’t conducive to low latency. But I’m not asking for very low latency. Even 200ms lag and 1 cm accuracy from over or undershoot is good enough for coarse grained jogging. Can always do fine grained jogging another way.
That’s not much to ask for is it? It would be a shame if even 200ms isn’t achievable and I would have to switch to Marlin, which has much less support on this board.
designed to move to a POSITION … You are attempting to get it to accept a VELOCITY input
Exactly, I want velocity control, which gcode doesn’t really allow. I thought the closest thing to velocity control was doing a bunch of relative G1 with constant distance and variable feedrate. But I don’t see how that’s much different than variable distance and constant feed rate. I tried both ways and they both suffer the 1s delay when loop executes every 100ms.
Could the lag and jerkiness be bypassed by using non-gcode commands like
toolhead.manual_move
FORCE_MOVE STEPPER