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

Error 4 on Center Finder #434

Open
MartinBaadsgaard opened this issue Jan 14, 2025 · 6 comments
Open

Error 4 on Center Finder #434

MartinBaadsgaard opened this issue Jan 14, 2025 · 6 comments

Comments

@MartinBaadsgaard
Copy link

MartinBaadsgaard commented Jan 14, 2025

Using Center Finder in 2.0.45, I get Error: 4 on the 4th probe, 1st pass when backing off first time.
By suggesting, tried disabling soft limits.
No error in 5 runs with soft limits off, 3/5 with limits on.

image

@terjeio
Copy link
Owner

terjeio commented Jan 28, 2025

Fix available for you to test in the latest edge version.

@MartinBaadsgaard
Copy link
Author

MartinBaadsgaard commented Jan 28, 2025

Thank you!
Tried ioSender Edge 2.0.46p1, unfortunately I got the same error again at different points in the probing process (2nd pass 2nd probe, 1st pass 2nd probe)
Soft limits on:
Repro rate: 2/3
Soft limits off:
Repro rate: 1/3

I have also found an error in my initial reporting. (Very sorry about that!) It was ALARM 4, not error 4.
I hope this is not a massive difference in how you interpreted the issue.

Let me know if I can provide anything else. Videos, pictures, system specs.

@terjeio
Copy link
Owner

terjeio commented Jan 29, 2025

Does it help increasing the Latch distance?
The probe motion is decelerated to a halt on contact, this takes time. There is a compiler option for reducing it if you need a small latch distance, if using the Web Builder to generate the firmware you can find it in the Advanced features tab, Minimize probe overshoot_ checkbox. This may also be worth a try.

@MartinBaadsgaard
Copy link
Author

Increased latch distance to 0.7mm
Repro rate: 0/5

Thank you Terje, this is an decent solution for me personally.
If you get more reports or feel this is an issue that needs tackling, let me know how I can help (Like the firmware build with lowered probe overshoot).

As a sidenote, issue #435 occurred consistently through testing, with probe stopping one move before finishing.

@terjeio
Copy link
Owner

terjeio commented Jan 30, 2025

As a sidenote, issue #435 occurred consistently through testing, with probe stopping one move before finishing.

With 2.0.46p1? I was able to reproduce the behaviour with 2.0,45 but I have not seen it again after more than one hundred runs with 2.0.46p1.

@MartinBaadsgaard
Copy link
Author

Sorry, I did not realise it was that bug which had been addressed, the release comment only mentioned this one.
Let me test on 2.0.46p1 when I'm back at the machine.

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