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

[bugfix 2.0] Button not working for pause on stow/deploy with G29 P1 #13114

Closed
pandel opened this issue Feb 9, 2019 · 7 comments
Closed

[bugfix 2.0] Button not working for pause on stow/deploy with G29 P1 #13114

pandel opened this issue Feb 9, 2019 · 7 comments

Comments

@pandel
Copy link

pandel commented Feb 9, 2019

Printer: Anycubic Kossel Linear Plus with Trigorilla 1.4, UBL active
Used commit: 9ae7cca

PAUSE_BEFORE_DEPLOY_STOW is defined / activated in Configuration.h

When I run step one from UBL mesh generation menu, the printer first executes a G28 and then a G29 P1. During this it asks me to "Deploy Z-Probe", but doesn't react when I hit the button. It simply waits forever.

BUT: when I run "Delta Auto Calibration" it works as expected. The printer is homing all axis, drops the nozzle a bit, asks for "Deploy Z-Probe", I attach the probe and hit the button and the printer begins calibration.

What's going wrong here?

EDIT: FWIW, when I activate BILINEAR leveling, everything works as expected regarding deploy/stow. So it must be something in the G29 or UBL code going wrong here.

@pixelbucket
Copy link

pixelbucket commented Feb 26, 2019

Same issue here. Sending M108 will get you past "Deploy Z-Probe" but unfortunately you'll hit the same problem at "Stow Z-Probe" and the same solution won't work a second time.

@boelle
Copy link
Contributor

boelle commented Mar 6, 2019

tried with todays commit of 2.0?

@pandel
Copy link
Author

pandel commented Mar 6, 2019

No, at least I didn't. While tuning my printbed a little, I went from UBL to bilinear to no leveling at all anymore. Just Z probe offset and be fine...

@boelle
Copy link
Contributor

boelle commented Mar 6, 2019

@pandel oki, maybe click close below and open new issue in future if you find the problem again?

@pandel
Copy link
Author

pandel commented Mar 6, 2019

@boelle Ok, sure :-)!

@pandel pandel closed this as completed Mar 6, 2019
@robbycandra
Copy link
Contributor

Try with bugfix2.0 the problem still exist.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants