diff options
| author | Kevin O'Connor <kevin@koconnor.net> | 2021-04-24 12:30:27 -0400 |
|---|---|---|
| committer | Kevin O'Connor <kevin@koconnor.net> | 2021-04-24 12:30:27 -0400 |
| commit | a58e9eddbe0996ff68fda114b9af290ff641f554 (patch) | |
| tree | 2b03cfe8d9624760d845bb6d1d7f38029f85693f | |
| parent | dfccc872b14b9a9f767c64db79de2d700b161ba2 (diff) | |
| download | kutter-a58e9eddbe0996ff68fda114b9af290ff641f554.tar.gz kutter-a58e9eddbe0996ff68fda114b9af290ff641f554.tar.xz kutter-a58e9eddbe0996ff68fda114b9af290ff641f554.zip | |
docs: Note stealthchop can cause overcurrent error in TMC_Drivers.md
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
| -rw-r--r-- | docs/TMC_Drivers.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/TMC_Drivers.md b/docs/TMC_Drivers.md index 0b08c332..413f4ee1 100644 --- a/docs/TMC_Drivers.md +++ b/docs/TMC_Drivers.md @@ -425,6 +425,13 @@ indicates the driver has disabled itself because it detected very high current passing through the driver. This may indicate a loose or shorted wire to the stepper motor or within the stepper motor itself. +This error may also occur if using stealthchop mode and the TMC driver +is not able to accurately predict the mechanical load of the motor. +(If the driver makes a poor prediction then it may send too much +current through the motor and trigger its own over-current detection.) +To test this, disable stealthchop mode and check if the errors +continue to occur. + **TMC reports error: ... reset=1(Reset)** OR **CS_ACTUAL=0(Reset?)** OR **SE=0(Reset?)**: This indicates that the driver has reset itself mid-print. This may be due to voltage or wiring issues. |