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

Z-axis switch bounces. V0.60 #19

Closed
capitaenz opened this issue Apr 8, 2012 · 5 comments
Closed

Z-axis switch bounces. V0.60 #19

capitaenz opened this issue Apr 8, 2012 · 5 comments

Comments

@capitaenz
Copy link

I've been using version 0.50 with no problems.
In the new version 0.60 of the Z-axis switch bounces at homing.
Have I missed a setting, or is it a fault?
I use a mechanical endswitch and a Sanguinololu version 1.3a.

@repetier
Copy link
Owner

repetier commented Apr 8, 2012

There was never a debounce code in the firmware. But the speed for the second try of the z-axis has changed. It is now configurable and set to 50% of the homing speed by default. With 0.50 it was the same speed. Check this in configuration.h

// For higher precision you can reduce the speed for the second test on the endstop
// during homing operation. The homing speed is divided by the value. 1 = same speed, 2 = half speed
#define ENDSTOP_X_RETEST_REDUCTION_FACTOR 2
#define ENDSTOP_Y_RETEST_REDUCTION_FACTOR 2
#define ENDSTOP_Z_RETEST_REDUCTION_FACTOR 2

set value to 1 for the old speeding. I guess hitting the switch with a slower speed made the difference.

@capitaenz
Copy link
Author

At this setting is not the problem. I just tried it.
I will if I have time later the version 0.50 install again.
I can not remember to have changed anything else.

@capitaenz
Copy link
Author

I have now flashed the firmware v0.50 - no bounce.
Then I flashed the firmware v0.60 - bounce
I again went through the configuration so far, on my side everything is ok.

@repetier
Copy link
Owner

repetier commented Apr 9, 2012

I think you had an other definition of bounce. You didn't mean the printer bounced at z=0 but at some higher position, right! If i'm right with the assumption, the problem should now be fixed (still version 0.60). I had the number of steps for the x axis used, but the z axis needed more steps for a full distance. Haven't tested such high moves, so it went unnoticed.

@capitaenz
Copy link
Author

Yes, that's it!
Thank you the bug is fixed =)

@repetier repetier closed this as completed Apr 9, 2012
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