diff options
| author | Kevin O'Connor <kevin@koconnor.net> | 2021-03-16 14:41:58 -0400 |
|---|---|---|
| committer | Kevin O'Connor <kevin@koconnor.net> | 2021-03-16 14:49:29 -0400 |
| commit | c8dc3afc235d9190591056a852f7ff4996c41c54 (patch) | |
| tree | b24186fd648a5cc3e801a69163e25b4839a878a4 | |
| parent | 0ddd6e8d21ebeb69eaa72c786887407e0b22825d (diff) | |
| download | kutter-c8dc3afc235d9190591056a852f7ff4996c41c54.tar.gz kutter-c8dc3afc235d9190591056a852f7ff4996c41c54.tar.xz kutter-c8dc3afc235d9190591056a852f7ff4996c41c54.zip | |
docs: Update TMC_Drivers.md with note on SPI failures on TMC driver checks
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
| -rw-r--r-- | docs/TMC_Drivers.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/TMC_Drivers.md b/docs/TMC_Drivers.md index a0786719..ca93be10 100644 --- a/docs/TMC_Drivers.md +++ b/docs/TMC_Drivers.md @@ -303,6 +303,15 @@ mid-print. This may be due to voltage or wiring issues. 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 +SPI errors that prevent communication with the driver (on tmc2130, +tmc5160, or tmc2660). If this occurs, it's common for the reported +driver status to show `00000000` or `ffffffff` - for example: `TMC +reports error: DRV_STATUS: ffffffff ...` OR `TMC reports error: +READRSP@RDSEL2: 00000000 ...`. Such a failure may be due to an SPI +wiring problem or may be due to a self-reset or failure of the TMC +driver. + ## How do I tune spreadcycle/coolstep/etc. mode on my drivers? The [Trinamic website](https://www.trinamic.com/) has guides on |