Perhaps because of "Round" setting?
I need more information. Which mode and how it is used?
I also need zip file of your profile and video showing this problem. You can send this to our email.
Since the version 18/11/22 I and a few friends have the
problem that the radio handwheel no longer works as accurately as before when moving the axes.
The movement no longer stops immediately.
The axes still seem to run a little after.
First I searched the error with me but the problem have several people.
Could someone from Planet-cnc check this?
Thanks a lot
Similar Threads:
Perhaps because of "Round" setting?
I need more information. Which mode and how it is used?
I also need zip file of your profile and video showing this problem. You can send this to our email.
I will check the settings for the handwheel again.
It could be that the selection to the step is no longer selected.
Unfortunately, I can't do that until early next week.
Thanks
I have noticed that you and ScorpionTDL have searched for the error over the weekend.
Thanks a lot
I noticed such extremely slow deceleration in previous versions, but I guess with latest update it got worse. Kind of got used to it but having the machine stop immediately when the handwheel stops would be nice.
Right now, it overshoots at high speed setting sometimes a centimeter or two.
Puzzle, Finger Joint, Maze and Guilloche freeware at https://fabrikisto.com/tailmaker-software/
the latest version 2022-12-11 fixed the issue for me
Problem is, in some cases if handwheel is rotated quickly the pulses are stored / buffered so even when you stop turning the handwheel, the axis will continue until the buffer = 0 pulses. Handwheel pulses need matching with the controller.
When you stop turning the wheel, machine must decelerate to stop and should not stop immediately, otherwise something might break or steps are lost.
If machine is able to stop sooner then machine deceleration settings can be set higher.
There was an issue with averaging logarithm and deceleration took longer than expected. This is all fixed now.