Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

edge-preview: missing acceleration/deceleration when sending multiple moves at once #487

Open
prof7bit opened this issue Jan 7, 2021 · 1 comment

Comments

@prof7bit
Copy link

prof7bit commented Jan 7, 2021

I was just playing around with the edge-preview branch (to check whether my other bug was fixed there [it is not]) and found the following odd behavior:

If I send something like this:

g1 z100 f10000
g1 z0 f10000
g1 z100 f10000
g1 z0 f10000
g1 z100 f10000
g1 z0 f10000
g1 z100 f10000
g1 z0 f10000

Then it will not decelerate/accelerate between the direction reversals, it will just hard switch direction at full speed, resulting in severe mechanical stress and and my colleague coming into the room saying: "Wow, the machine might be destroyed before the software is finished"!

The edge branch does not have this bug.

I probably won't be available to test the fix on the preview branch (should it ever be fixed at all) because I am now moving back to the half finished edge branch which does not have this error. But I wanted to report it anyways, so it can be worked on in case this project ever becomes actively developed again.

@giseburt
Copy link
Member

giseburt commented Jan 7, 2021

This indicates that your jt (JUNCTION_INTEGRATION_TIME in settings) value is too high. It basically tells the system how aggressive of cornering your machine can handle.

The test you have is great, except you likely want to have the same test for X and Y and combined XY as well. I'd start with setting jt to something low, like 0.5, and raising it slowly until that axis stalls. Verify that value is good for the other axes.

Note that jt works with your axis jerk settings (xjm, or X_JERK_MAX, and yjm, etc.), so if one axis is having trouble with the jt that the other axis are fine with, then lower that axis' jerk max setting.

-Rob

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants