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

Servo should be turned off when performing z axis move during bed autoleveling (G29) #2365

Closed
foulowl opened this issue Jul 3, 2015 · 8 comments

Comments

@foulowl
Copy link

foulowl commented Jul 3, 2015

Hi folks,

Currently the block diagram for bed autoleveling is as follows: (for each of the four points)
Lower arm -> lower z axis until switch hit -> record data -> raise z axis -> raise arm

The downside of this is that my servo arm skips around roughly +-5 degrees during any axis moves. Discussion on #reprap IRC channel states this servo skipping is a known issue.

A better procedure would be:
Turn servo on -> lower arm -> turn servo off -> lower z axis until switch hit -> record data -> raise z axis -> turn servo on -> raise arm -> turn servo off

Thanks!

(As an item of note, I have a RAMPS 1.4 board.)

@Roxy-3D
Copy link
Member

Roxy-3D commented Jul 3, 2015

You must be running a very old version of Marlin. There are options to control the engagement and retraction of the probe now. And the default is to leave it engaged during the G29.

@foulowl
Copy link
Author

foulowl commented Jul 3, 2015

Marlin version was checked out three days ago.

Let me clarify: I'm not interested in controlling the engagement and retraction of the probe. I want G29 to do exactly what it does now, except that during z axis moves I want the supply voltage turned off to the servo pins. The reason for this is that there appears to be a hardware bug in the RAMPS1.4 board that causes the servo arm to randomly jump around during any axis moves.

@Wackerbarth
Copy link
Contributor

"during z axis moves I want the supply voltage turned off to the servo pins" -- During ALL z-axis moves? Or only some of them? I cannot imagine the hardware being very happy if this supply is being switched off and on very often.

If you just want it done associated with probing, then what we need to do is implement the switch in G-code and make the probe action something that can be customized. (We have discussed doing this for all of the probe actions, unifying deltas, sleds, etc.)

@foulowl
Copy link
Author

foulowl commented Jul 3, 2015

To be more specific: "during all z axis moves while G29 is executing I want the supply voltage turned off to the servo pins".

@foulowl
Copy link
Author

foulowl commented Jul 5, 2015

Just to confirm: I built an external 5V power supply for my 9g bed leveling servo, but it had no effect on this issue. So this isn't an issue of the servo 5V supply being underpowered, as suggested on the reprap forums.

I like the suggestion that was made on IRC #reprap, which is to turn off the servo during the z axis moves, then turn it on again after the move has completed.

An item of note: this is a crucial bug for me, as with the random jiggling on my servo I can't get a proper bed autolevel to complete. It will randomly work sometimes, it just depends on how much the servo arm has jiggled around.

If I post a bounty on this issue, would anyone like to work with me on getting it resolved?

Thank you!!

@Ziggy2013
Copy link

There is already a parameter in configuration.h to turn the servo off between moves. By default this parameter is commented out.

#define PROBE_SERVO_DEACTIVATION_DELAY 300

Uncomment this parameter and the servo should stay stable after moves. This parameter also introduces a delay after the servo write to allow the servo to settle.

@foulowl
Copy link
Author

foulowl commented Jul 5, 2015

That works perfectly! Thank you for the help, sorry I missed that.

@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 Apr 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants