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

Retraction speed overruled during travel #1476

Closed
justmyopinion opened this issue Oct 6, 2013 · 6 comments
Closed

Retraction speed overruled during travel #1476

justmyopinion opened this issue Oct 6, 2013 · 6 comments

Comments

@justmyopinion
Copy link

When extruder is travelling to a new position retraction is issued as inline code causing retraction to take as long as traveltime resulting in oozing because retraction is not working at slow speeds. Compensation is however always made in new line.
This retraction error is only programmed inline when travellling but should always be made as a new line.
Se details here:
http://forums.reprap.org/read.php?263,251182

@justmyopinion
Copy link
Author

Seams to be a problem mentioned before in #1289

@justmyopinion
Copy link
Author

Inspired by #1289 I found out that the problem only exist if MACH3/EMC flavor is selected in Printer Settings.
If I select Reprap flavor problem seems to be gone. Whether this could give me problems, I do not know yet. My machine is not a true RepRap.

@justmyopinion
Copy link
Author

Seems that problem could be related to the use of G00 command in relation to retraction and travel as non coordinated commands may not be implemented with Marlin or similar coding, If inline retraction code is not executed as fast retraction (G0) but as coordinated (G1), retraction would slow down with long travels. G0 code is not issued with RepRap printer flavor settings.

@alranel
Copy link
Member

alranel commented Oct 12, 2013

What version are you using?

@justmyopinion
Copy link
Author

0.9_10b!
See #1289 for more detailed information. Same problem.
I get around problem by not using Mach3 flavor but coding should be changed with MACH3 flavor to avoid assuming non coordinated moves with G0. Why not just do it the same way as RR flavor coding?

@alranel
Copy link
Member

alranel commented Oct 13, 2013

Okay, thank you, let's follow up in #1289

@alranel alranel closed this as completed Oct 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants