3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Correct TMC_Drivers Title Nesting 

Signed-off-by: Yifei Ding <yifeiding@protonmail.com>
This commit is contained in:
Yifei Ding 2021-10-23 11:27:48 -07:00 committed by KevinOConnor
parent ee04a6340a
commit d602177281
1 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/TMC_Drivers.md
View File

@ -167,7 +167,7 @@ homing. See the
[config reference](Config_Reference.md#tmc-stepper-driver-configuration) [config reference](Config_Reference.md#tmc-stepper-driver-configuration)
for all the available options. for all the available options.
### Find highest sensitivity that successfully homes #### Find highest sensitivity that successfully homes
Place the carriage near the center of the rail. Use the SET_TMC_FIELD Place the carriage near the center of the rail. Use the SET_TMC_FIELD
command to set the highest sensitivity. For tmc2209: command to set the highest sensitivity. For tmc2209:
@ -425,14 +425,16 @@ state.
Some common errors and tips for diagnosing them: Some common errors and tips for diagnosing them:
**TMC reports error: ... ot=1(OvertempError!)"**: This indicates the #### TMC reports error: ... ot=1(OvertempError!)"
motor driver disabled itself because it became too hot. Typical
This indicates the motor driver disabled itself because it became too hot. Typical
solutions are to decrease the stepper motor current, increase cooling solutions are to decrease the stepper motor current, increase cooling
on the stepper motor driver, and/or increase cooling on the stepper on the stepper motor driver, and/or increase cooling on the stepper
motor. motor.
**TMC reports error: ... ShortToGND** OR **LowSideShort**: This #### TMC reports error: ... ShortToGND** OR **LowSideShort
indicates the driver has disabled itself because it detected very high
This indicates the driver has disabled itself because it detected very high
current passing through the driver. This may indicate a loose or current passing through the driver. This may indicate a loose or
shorted wire to the stepper motor or within the stepper motor itself. shorted wire to the stepper motor or within the stepper motor itself.
@ -443,13 +445,15 @@ current through the motor and trigger its own over-current detection.)
To test this, disable stealthchop mode and check if the errors To test this, disable stealthchop mode and check if the errors
continue to occur. continue to occur.
**TMC reports error: ... reset=1(Reset)** OR **CS_ACTUAL=0(Reset?)** #### TMC reports error: ... reset=1(Reset)** OR **CS_ACTUAL=0(Reset?)**OR **SE=0(Reset?)
OR **SE=0(Reset?)**: This indicates that the driver has reset itself
This indicates that the driver has reset itself
mid-print. This may be due to voltage or wiring issues. mid-print. This may be due to voltage or wiring issues.
**TMC reports error: ... uv_cp=1(Undervoltage!)**: This indicates the #### TMC reports error: ... uv_cp=1(Undervoltage!)
driver has detected a low-voltage event and has disabled itself. This
may be due to wiring or power supply issues. This indicates the driver has detected a low-voltage event and has
disabled itself. This may be due to wiring or power supply issues.
It's also possible that a **TMC reports error** shutdown occurs due to It's also possible that a **TMC reports error** shutdown occurs due to
SPI errors that prevent communication with the driver (on tmc2130, SPI errors that prevent communication with the driver (on tmc2130,