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.

Sign up for GitHub

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

Added kinematic_bed troubleshooting guide draft. #5

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Added kinematic_bed troubleshooting guide draft. #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e618fad
Added kinematic_bed troubleshooting guide draft.
Hajto Jul 31, 2021
35e4444
Added kinematic bed troubleshooting to the toubleshooting.md
Hajto Jul 31, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,12 @@ You're not supposed to change *any* files inside the config/ folder. You should

## Klipper says the MCU is unable to connect
Double check your USB connection, try another cable (the one that comes with the board usually works), and check that your firmware was flashed correctly (refer to the guide for your board).

[filename](troubleshooting/kinematic_bed.md ':include')

## Get help
For further support check out the v-coreos-support and klipper channels on Discord. Use the invite link below to join.



<a href="https://discord.gg/D62e8XNeYa" class="button">Join the Unnofficial RatRig Discord Community</a>
38 changes: 38 additions & 0 deletions docs/troubleshooting/kinematic_bed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
## Kinematic Bed does not finish leveling successfully
This issue often shows up as bed being more out of alignment each iteration and sometimes does throw an error after few iterations.

If you are getting this error, this section should help you:

```
!! Retries aborting: Probed points range is increasing.
!! Retries aborting: Probed points range is increasing.
```

There are two most common mistakes that cause this behavior:
- one of the motors cable detached
- mixed cables of the motors

In order to verify expected order of the drives look for `z_tilt` section in
your printer.cfg.
```
[z_tilt]
points:
60,60
235,370
360,60
```

These points designate where the probing will occur and should correspond to
nearest stepper. In this case motors should left bottom of the buildplate,
top middle of the buildplate, and right bottom of the buildplate.

You can use [STEPPER_BUZZ](https://github.com/KevinOConnor/klipper/blob/master/docs/Config_checks.md#verify-stepper-motors) command:
```
STEPPER_BUZZ STEPPER=stepper_z
STEPPER_BUZZ STEPPER=stepper_z1
STEPPER_BUZZ STEPPER=stepper_z2
```

Upon execution, motor in question should go first up and then down.

Stepper names should correspond to their names in the printer.cfg.