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

Nozzle height too high #73

Open
LeandroSQ opened this issue Sep 24, 2024 · 5 comments
Open

Nozzle height too high #73

LeandroSQ opened this issue Sep 24, 2024 · 5 comments

Comments

@LeandroSQ
Copy link

Hello,
I've been trying to calibrate my Eddy, using it as endstop and without the Z-Offset config.

When the nozzle is touching the bed, Eddy is 2mm from the bed surface
I ran LDC_CALIBRATE_DRIVE_CURRENT CHIP=btt_eddy with Eddy 20mm from surface.
And running PROBE_EDDY_CURRENT_CALIBRATE_AUTO CHIP=btt_eddy (Manual does not work too) results in the nozzle being to high, unable to print.

I also did the temperature calibration, as I have the USB variant.

On the paper calibration, tried several times and all of them seem to result in the same issue.

@aldoale
Copy link

aldoale commented Sep 26, 2024

same problem but nozzle too low in my case and I can't calibrate manually.

@LeandroSQ
Copy link
Author

@bigtreetech any ideas on how we can calibrate this?

@bigtreetech
Copy link
Owner

Completely clear out anything probe related from the automatically generated section. This includes all thermal offsets, z offsets, mesh settings, drive current, etc... start fresh.

Run the calibration, then run the thermal calibration and then see what happens. Should be good. Also, why did you choose not to use the z-offset out of interest?

@LeandroSQ
Copy link
Author

As the guide mentioned Z offset was not needed due to the nature of Eddy, I decided not to go with the an offset config, seemed a lot simpler as well.

Thank you for the instructions, will try later and let you know how it goes.

@aldoale
Copy link

aldoale commented Oct 20, 2024

I tried to reinstall everything but the first layer is always wrong, did you solve it?

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

3 participants