Baby Stepping Hardware Button
-
Normally closed switches are better for actual endstops from a safety perspective, but for this, I don't see it mattering as much since either way, if it's disconnected, it won't work. I have a bunch of NO buttons, so I'll just use those.
Actually, if you use the start/end code, and it's a normally closed switch, would it activate if one is connected and the other is not? (For the not connected one) which could throw stuff off, and be really annoying.
I'm kind of okay with this working whether there is a print running or not.
Edit: Second question, can I change the baby stepping increment? Sometimes 0.05mm is a little more than I want to change it by, and 0.025 would be better.
-
@supraguy Yes, if you are babystepping "manually" using this sort of macro (or a user defined one on the web interface) you can just type in the value for the M290 command for incremental steps. I think the latest PanelDue firmware actually adjusts in 0.02mm increments now which is pretty nice.
For the question about activation, if you are using two different endstops it would not cause any issue if one switch NO and the other is NC. You can set up each independently of the other.
Please keep in mind that this entire way of doing things is kind of "hackish" but should work fine.
-
Hi,
I like this idea. One question, can i use only one ground for both Buttons? I have a lot 3 wire cables and connectors. Would it make easier for me
Thanks!
-
@torro said in Baby Stepping Hardware Button:
Hi,
I like this idea. One question, can i use only one ground for both Buttons? I have a lot 3 wire cables and connectors. Would it make easier for me
Thanks!
Yes, buttons connected to different endstop inputs can use a common ground wire.
-
Thanks again!
-
Has someone noticed problems with "button bouncing" ?
increasing is fine, when i push "decrease", baby stepping decreases 2 or 3 times the programmed value.there are some possibilities with small circuits and arduino seems to have a library for this problem.
is there a solution in the firmware?
-
I was a little concerned with debounce, but that hasn't been a problem for me -- at least I haven't NOTICED a problem, which amounts to the same thing.
IIRC, this is looking for falling edge, so a small capacitor across the button wiring would work to debounce your button, at a cost of slightly slower response. Fast response is more important for mechanical/electronic things, but can be tolerated for most manual operation like this.
Depending on what you're using, it might be better to just get better buttons/switches.
-
I tried 3 different types of Buttons...
i'll try a capacitor. How small do you think should it be? -
There is already a hardware debounce circuit on the 5 endstop inputs on the Duet, but not on the ones on the expansion connector or CONN_LCD. Which inputs at you using?
-
E0 and E1.
I think the Buttons are sh*t, when there is a debouncing included...
-
I found the problem. The Buttons i tried, are big ones for 230V AC and 10-16 Amps.
Today, i found some for 12V and 0.05amps. They work like a charm. I only had to solder a small circuit Board to mount them.
