# Unable to read tmc uart 'stepper\_z' register DRV\_STATUS **URL:** \ **Category:** General Discussion\ **Created:** [May 26, 2022, 10:39am UTC](https://klipper.discourse.group/t/unable-to-read-tmc-uart-stepper-z-register-drv-status/2991 "2022-05-26T10:39:32Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![TwinklE](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@TwinklE](https://klipper.discourse.group/u/TwinklE)\ **Post date:** [May 26, 2022, 10:39am UTC](https://klipper.discourse.group/t/unable-to-read-tmc-uart-stepper-z-register-drv-status/2991/1 "2022-05-26T10:39:33Z")
[klippy(5).log](https://klipper.discourse.group/uploads/short-url/3SSpMNwsflPwyf9fOlqd7Tg9K0j.log) (4.6 MB) [moonraker(5).log](https://klipper.discourse.group/uploads/short-url/lNrvPpYZYCbFqb0TIgZNIBTtR1C.log) (422.8 KB) Hi Together, I got a problem with my voron 2.4 with ocotopus V1.1. First I will explan the history of this problem. I got the voron about 07.2021 and printed since then about 1700 hours successfully without an issue. After I upgraded with stealthburner BETA and got it running. I got some LED Problems some days later, tried to fix it and fried my octopus board with a short circuit… I bought a new board, kopied the exact same wiring (triple checked) and did the standard proceedure. - I created the firmware with the already existing rspi configuration, flashed it and got an error which told me I had some different Versions. So I updated everything to Klipper Version v0.10.0-426-gaf38d708. Then created firmware again, flashed, error code disappeared. - New error code appeared, which was related to the update and some commands had to be changed. So I changed the lines accordingly to the new manual, started again. Error code disappeared. -New error code appeared. This time I could not solve it. Here I need your advice. Unable to read tmc uart ‘stepper\_z’ register DRV\_STATUS Once the underlying issue is corrected, use the “FIRMWARE\_RESTART” command to reset the firmware, reload the config, and restart the host software. Printer is shutdown So I checked every Pin in my printer.cfg file, checked the right wiring again… Still the same issue or other issues, see the following Unable to read tmc uart ‘stepper\_z’ register IFCNT Once the underlying issue is corrected, use the “FIRMWARE\_RESTART” command to reset the firmware, reload the config, and restart the host software. Printer is shutdown Unable to read tmc uart ‘stepper\_z3’ register IFCNT Once the underlying issue is corrected, use the “FIRMWARE\_RESTART” command to reset the firmware, reload the config, and restart the host software. Printer is shutdown Unable to read tmc uart ‘stepper\_z2’ register IFCNT Once the underlying issue is corrected, use the “FIRMWARE\_RESTART” command to reset the firmware, reload the config, and restart the host software. Printer is shutdown NOTE: About half of the time, all 4 z-steppers are moving accordingly upwards, at the end of this movement, the printer stops and give the error message consistently. So the errors come up when starting to home instantly, or after the first upwards movement from all 4 steppers. NOTE Nr. 2: The console brings up the following message consistently. 12:29:01 $ G28 12:29:01 // Homing X 12:29:01 // Homing Y 12:29:01 // Homing Z 12:29:01 // Unknown command:“CHECKPROBE” 12:29:01 // Klipper state: Shutdown 12:29:01 !! Homing failed due to printer shutdown 12:29:01 !! Homing failed due to printer shutdown 12:29:04 $ FIRMWARE\_RESTART 12:29:08 // Klipper state: Ready * * * Thats all from my knowledge. To be honest do not have much of a clue of wiring and electrical stuff, so I really hope that you can help me get my Voron back up and running. As I said, im not experienced with the software stuff, but I will try to provide every information you ask for analysing my problem. I searched in advance for other solutions of the topic, most of the time it were power issues or the firmware had to be reflashed. But after I followed those steps I didnt get rid of my problem. Could it be that my X or Y stepper got damaged? I thank you all in advance! Best regards. TwinklE ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [May 26, 2022, 11:17am UTC](https://klipper.discourse.group/t/unable-to-read-tmc-uart-stepper-z-register-drv-status/2991/2 "2022-05-26T11:17:25Z")
See [TMC 'extruder' reports error: GSTAT: 00000001 reset=1(reset - #39 by Sineos](https://klipper.discourse.group/t/tmc-extruder-reports-error-gstat-00000001-reset-1-reset/1156/39) ---
**Author:** ![TwinklE](https://avatars.discourse-cdn.com/v4/letter/t/67e7ee/32.png) [@TwinklE](https://klipper.discourse.group/u/TwinklE)\ **Post date:** [May 29, 2022, 4:01pm UTC](https://klipper.discourse.group/t/unable-to-read-tmc-uart-stepper-z-register-drv-status/2991/3 "2022-05-29T16:01:48Z")
Hi Sineos, thank you for your replay and the link to other topics related to mine. To be honest I read through the other 3 topics and couldnt find much of a similarity. Maybe I do not understand the problem to the extend necessary to act. So my straight forward question is: - Is there anything I can do to solve the problem reliably? - Reading through the other topics, are there tests and other actions in order to solve this kind of problems? - Is there a possibility to downgrade to a version prior Klipper Version v0.10.0-426-gaf38d708? I have the feeling that the upgrade caused this issue for me Thank you very much in advance! Best regards. TwinklE ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [May 29, 2022, 5:19pm UTC](https://klipper.discourse.group/t/unable-to-read-tmc-uart-stepper-z-register-drv-status/2991/4 "2022-05-29T17:19:52Z")
Well, it is generally accepted that these kind of errors point to a hardware problem. Unfortunately this hardware problem is not limited to stepper or stepper driver but also other faulty hardware seems to lead to such issues. > [@TwinklE](#): > > I got some LED Problems some days later, tried to fix it and fried my octopus board with a short circuit… I guess you answered your own question already. What makes you believe that a short circuit where potentially some dozens of amperes run through your hardware only fried your board? There is most likely nothing but trial and error to find the culprit. Of course you can downgrade but this does not mean the problem goes away. Klipper just no longer reacts with a hard fault. Consequences are quite simple: - You might suffer from other problems, which will then be impossible to diagnose - You will never be able to update again and profit from fixes and added features. If you do, you are at the same spot as you are now It’s your call. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [November 4, 2025, 2:30pm UTC](https://klipper.discourse.group/t/unable-to-read-tmc-uart-stepper-z-register-drv-status/2991/5 "2025-11-04T14:30:42Z")