Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 3 of 3
I am interested in boundary conditions a point at which point frequency of the controller would start affecting accuracy or break it's assumptions. I am trying to read the code but it's going to take some time as I learn as I go. So far it seems to me that the code is not expecting to have less than one tick per 1us.
by
rmichael_cd
-
Firmware - experimental, borrowed, and future
Thanks for the explanation. Your first few posts to this thread were enlightening as well - such as that compression algorithm is lossy.
Forgetting about compression for a moment, where in the code is the time rounded up to the nearest tick?
How well do you think would Klipper work with 250kHz (step) clock on the MCU (controller with shift registers connected to 10 steppers)?
EDIT: I think
by
rmichael_cd
-
Firmware - experimental, borrowed, and future
I understand that in Klipper position is described by distance and time.
What is the resolution of the time variable?
I would imagine that it depends on speed of the controller - is it derived from max velocity? Can you have different interval for each stepper?
Does position depend on given point in time or time on given position?
What happens if steppers resolution does not allow to achi
by
rmichael_cd
-
Firmware - experimental, borrowed, and future
