Skip to content

Commit

Permalink
Fix various typos (#422)
Browse files Browse the repository at this point in the history
While reading through the documentation I've spotted a few minor typos
/ misspellings. They are easy enough to fix so why shouldn't I.
  • Loading branch information
andir authored Jul 29, 2024
1 parent 227c97a commit 6f95126
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions community/howto/clee/sensorless_xy_homing.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,8 +102,8 @@ The calibration process is:
- Try running `G28 X0` to see if the toolhead moves along the X axis.
- If your toolhead moves all the way to the end of the rail, **IMMEDIATELY HIT THE EMERGENCY STOP BUTTON**. Go back and double-check that you have configured your hardware and the Klipper sections above correctly. Ask on Discord if you need help.

- When running the `G28 X0` or `G28 Y0` command, the toolhead *WILL* move ever so slightly before it triggers the virtual endstop. This is normal. after triggering the toolhead will also move 10mm beck in the opposite direction. for example: if you stallguard value is too high you may observe the toolhead only moving 10mm to the left. this is expected and simply means your stallguard value is still too sensative for the toolhead to overcome the resistance in the beltpath.
- As described above when you first start trying to find your value, it will look like the toolhead is moving away from the right rail, then stopping. This is normal and just means the value is still too sensitive to home properly. Early on, you can jump down in jumps of 50. to change the stallguard value quickly simply enter `SET_TMC_FIELD FIELD=SGTHRS STEPPER=stepper_x VALUE=XXX` into the console, replacing the XXX with your desired stallgurad value to test. This command only overwrites the value temporarily so when you are finished it will have to be updated in your actual printer.cfg file.
- When running the `G28 X0` or `G28 Y0` command, the toolhead *WILL* move ever so slightly before it triggers the virtual endstop. This is normal. After triggering the toolhead will also move 10mm back in the opposite direction. For example: if you stallguard value is too high you may observe the toolhead only moving 10mm to the left. This is expected and simply means your stallguard value is still too sensitive for the toolhead to overcome the resistance in the beltpath.
- As described above when you first start trying to find your value, it will look like the toolhead is moving away from the right rail, then stopping. This is normal and just means the value is still too sensitive to home properly. Early on, you can jump down in jumps of 50. To change the stallguard value quickly simply enter `SET_TMC_FIELD FIELD=SGTHRS STEPPER=stepper_x VALUE=XXX` into the console, replacing the XXX with your desired stallgurad value to test. This command only overwrites the value temporarily so when you are finished it will have to be updated in your actual printer.cfg file.
- At some point you will get X to home all the way to the rail. However, if you went TOO low, it might bump harder into the rail than it should. In this case, split the difference and try homing the axis again.
- Eventually you will find the BIGGEST number that homes X successfully. Nice! With the maximum found, continue to DECREASE the value by 5 or so until X homes, but bumps too hard into the rail. You may need to walk this in by changing the value by 1 when getting close. This is your MINIUMUM value. Ideally we want to hard code a final value between the minimum and maximum that will always work, it is best to shoot for something slightly LESS than halfway between minimum and maximum.

Expand All @@ -113,7 +113,7 @@ The calibration process is:

### Homing macros

The Klipper docs recommend setting up dedicated `SENSORLESS_HOME_X`/`SENSORLESS_HOME_Y` macros. The stock configs have renamed them to `_HOME_X` and `_HOME_Y` (the leading underscores will hide them in Mainsail/Fluidd, and those specific names are special for Klicky). This setup that has been working well for several Voron owners. these should already be present in your stock config but if you are building a confi file from scratch or configuring a board that does not have a premade file the homing macros basic layout is as follows:
The Klipper docs recommend setting up dedicated `SENSORLESS_HOME_X`/`SENSORLESS_HOME_Y` macros. The stock configs have renamed them to `_HOME_X` and `_HOME_Y` (the leading underscores will hide them in Mainsail/Fluidd, and those specific names are special for Klicky). This setup that has been working well for several Voron owners. These should already be present in your stock config but if you are building a confi file from scratch or configuring a board that does not have a premade file the homing macros basic layout is as follows:

<!-- {% raw %} -->
```
Expand Down

0 comments on commit 6f95126

Please sign in to comment.