Hard to tell since it depends on where you live. Where I’m living the mains power net has three connections: Live, Neutral and PE. These 3 lines are also connected to my PSU and I use the PE as ground
1 Like
Ok, yeah same here. My extra ground cable goes from frame to PE. And again, i have 0 ohm between the stepper motor housing and PE then. So there is contact between them.
I guess these caps you mention are against interference from the suppply, not for ESD protection. See https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_Datasheet_V103.pdf
page 14.
Yes, the mentioned capacitors (if missing) would rather end in GSTAT: uv_cp=1 error. Your board has those capacitors. So better forget my post from above 
It might be a good idea to solder the capacitors mentioned on page 14 on the left schematic to your board. I think it can be done easily. I would give it a try! Good luck!
I am having this issue on a BTT Manta M8P with CB1 on a Tronxy X5SA Pro/ VZBot conversion. It started out on the Y stepper. Following multiple threads, I tried swapping drivers (Same issue on Y), swapping wires (Same issue on Y), swapping steppers (Issue switched to X). So I replaced both X and Y steppers and problem resolved for a few prints. It has came up recently again on the X stepper. Hoping there is a resolution soon.
Small update here, as something funny happend just now.
Got a gstat stepper reset error on Z, because of statics spark (wearing my rubber sandals, that create a ton of statics…) but funny is that this happend when i touched the printer sitting next to the printer in use. Like a foot apart.
So that tells me that it’s going thru the AC, or the Pi at least, since that’s the only thing connectiom them. They go to the same Pi, and same wall outlet.
Joining the list with my SKR2 and ender 5. TMC ‘extruder’ reports error: GSTAT: 00000001 reset=1(Reset)
This isn’t klipper specific, on marlin my extruder will drop steps from 16 to 8 when this happens and start to overheat and extrude we too much filament.
It always seems to be the extruder on my side.
Updated: Replaced the extruder stepper motor and the issue have been resolved.
Another update after printing for much longer the issue reoccurred.
Things I have tried:
- Swapping out the stepper TMC driver.
- Ensure the SKR2 is properly grounded.
- Placed a hot dab of glue on the connections.
- Swapping out the extruder stepper.
I will be swapping out the mainboard with a SKR3 next hoping the issue isn’t specific to BigTreeTech boards. Then I will replace the stepper drivers with TMC2226 instead of the TMC2209. And then I will re-crimp all the wires.
I have replaced my mainboard with a SKR3 and TMC2226 drivers, printing worked without an issue until I neaten (bundled) up the cables, I got a reset again on the Extruder. Now looking into the possibility of signal interference on the stepper motor cable.
I have redone the stepper cable and tied it to the frame via Velcro ties which seems to have made a difference. Still keeping an eye on it.
1 Like
Same problem here with an octopus 1.1 on a Sovol SV02 machine.
I changed the motor three times, and the extruder wires twice. I admit I still have a cable extender since I couldn’t find long enough extruder wires until now. I’m looking for a good cable/wires.
@Peggy and @some-klipper-user
Have you tried to put some active cooling across the TMC drivers?
You could just put a small fan blowing air across the drivers and see if they stabilize.
我想我解决了这个报错，引发这个报错的原因是机器的震动
2 Likes
在我把机器从桌搬到地上之后出现了这个报错，我尝试了各种办法，结果发现是因为搬到地上后，机器没有桌子吸收震动，倒是机器的震动传导到主板导致的报错，而且几乎是在同一个地方，我通过给主板支架增加缓冲解决了这个问题
2 Likes
@jjarosz I solved my problem by shorting the direct drive extruder wires
@jjarosz I have a 12cm fan to cool down the MCU and steppers, I don’t think it is a cooling issue, the room is also air conditioned at 23 degrees Celsius. I have tightened the stepper cable wiring by tying it to the frame which seems to have done the trick. Still keeping an eye on it though.
After not seeing this problem for a long time it’s back.
This Time it happened to a printer with another E3 Turbo board that has worked good for some years. I then switched out the Board for an Octopus 1.1 and the Issue was gone for a while, but then it reappeared.
I’m really lost here, I tried different stepper slots, stepper drivers, cables, steppers.
It seems to be just random.
On Octopus 1.1 I changed all parts several times, the only thing that worked is the cable lenght.
What Cable are you refering too? The USB cable?
the stepper cable wiring
1 Like
mid adxl calibration for my Y I started getting these errors:
- TMC ‘stepper_y’ reports error: GSTAT: 00000001 reset=1(Reset)
- Unable to read tmc uart ‘stepper_y’ register MSCNT
This first happened mid-print and right after as soon as I would try to home Y, it would hit the end stop and crash with the second error repeatedly (most of the time - once in a while it would home correctly if I would hit the end stop manually and not let the carriage hit it).
Reading this thread I immediately checked my wiring - I do my own crimping, so I double checked all the pins, reseated all the plugs and replaced the endstop with no results.
The strange part is that even after the error came up, I could still DUMP_TMC STEPPER=stepper_y without any issues!
Output
12:35
SG_RESULT: 00000000
12:35
PWM_AUTO: 000e0023 pwm_ofs_auto=35 pwm_grad_auto=14
12:35
PWM_SCALE: 00000023 pwm_scale_sum=35
12:35
PWMCONF: c80d0e24 pwm_ofs=36 pwm_grad=14 pwm_freq=1 pwm_autoscale=1 pwm_autograd=1 pwm_reg=8 pwm_lim=12
12:35
DRV_STATUS: c01f0000 cs_actual=31 stealth=1 stst=1
12:35
CHOPCONF: 15010053 toff=3 hstrt=5 tbl=2 mres=5(8usteps) intpol=1
12:35
MSCURACT: 00f60018 cur_a=24 cur_b=246
12:35
MSCNT: 00000010 mscnt=16
12:35
TSTEP: 000fffff tstep=1048575
12:35
FACTORY_CONF: 0000000f fclktrim=15
12:35
IOIN: 21000041 enn=1 pdn_uart=1 version=0x21
12:35
OTP_READ: 0000000f otp_fclktrim=15
12:35
IFCNT: 00000000
12:35
GSTAT: 00000001 reset=1(Reset)
12:35
GCONF: 00000101 i_scale_analog=1(ExtVREF) multistep_filt=1
12:35
========== Queried registers ==========
12:35
SGTHRS: 00000000
12:35
TPOWERDOWN: 00000014 tpowerdown=20
12:35
TPWMTHRS: 000fffff tpwmthrs=1048575
12:35
IHOLD_IRUN: 00081919 ihold=25 irun=25 iholddelay=8
12:35
SLAVECONF: 00000200 senddelay=2
12:35
========== Write-only registers ==========
12:35
DUMP_TMC STEPPER=stepper_y
12:35
SG_RESULT: 00000000
12:35
PWM_AUTO: 000e0024 pwm_ofs_auto=36 pwm_grad_auto=14
12:35
PWM_SCALE: 0000001d pwm_scale_sum=29
12:35
PWMCONF: c80d0e24 pwm_ofs=36 pwm_grad=14 pwm_freq=1 pwm_autoscale=1 pwm_autograd=1 pwm_reg=8 pwm_lim=12
12:35
DRV_STATUS: c0190000 cs_actual=25 stealth=1 stst=1
12:35
CHOPCONF: 24030053 toff=3 hstrt=5 tbl=2 vsense=1 mres=4(16usteps) dedge=1
12:35
MSCURACT: 00df006a cur_a=106 cur_b=223
12:35
MSCNT: 00000048 mscnt=72
12:35
TSTEP: 000fffff tstep=1048575
12:35
FACTORY_CONF: 0000000f fclktrim=15
12:35
IOIN: 21000041 enn=1 pdn_uart=1 version=0x21
12:35
OTP_READ: 0000000f otp_fclktrim=15
12:35
IFCNT: 00000010 ifcnt=16
12:35
GSTAT: 00000001 reset=1(Reset)
12:35
GCONF: 000001c0 pdn_disable=1 mstep_reg_select=1 multistep_filt=1
12:35
========== Queried registers ==========
12:35
SGTHRS: 00000000
12:35
TPOWERDOWN: 00000014 tpowerdown=20
12:35
TPWMTHRS: 00000000
12:35
IHOLD_IRUN: 00081919 ihold=25 irun=25 iholddelay=8
12:35
SLAVECONF: 00000200 senddelay=2
12:35
========== Write-only registers ==========
12:35
DUMP_TMC STEPPER=stepper_x
I happen to have a spare 2209, so I replaced my Y stepper motor and the issue went away!
I’m running skr 1.4 turbo with btt 2209 steppers.
I fully admit that it’s possible I forgot to unplug the stepper while testing my Y carriage for alignment as part of the acceleration calibration.
I do tend to disconnect the drivers when I manually move any of the axes, as I know how back-driving your drivers can quickly kill them - but it’s possible it was my fault.
Anyway, if you have removable drivers, try replacing the sus one.
Edit:
Just before the Y finally gave up, I remembered I was getting errors on all my other steppers as well.
So I’m guessing that some shared bus / or power rail was being pulled up/down by the dying stepper?
output
TMC ‘stepper_z1’ reports GSTAT: 00000001 reset=1(Reset)
TMC ‘stepper_z’ reports GSTAT: 00000001 reset=1(Reset)
TMC ‘stepper_z1’ reports GSTAT: 00000000
TMC ‘stepper_z’ reports GSTAT: 00000000
TMC ‘stepper_x’ reports GSTAT: 00000001 reset=1(Reset)
TMC ‘stepper_x’ reports GSTAT: 00000000
TMC ‘extruder’ reports GSTAT: 00000001 reset=1(Reset)
TMC ‘extruder’ reports GSTAT: 00000000
TMC ‘stepper_y’ reports GSTAT: 00000001 reset=1(Reset)
TMC ‘stepper_y’ reports GSTAT: 00000000
Unable to obtain tmc stepper_y phase
Unable to read tmc uart ‘stepper_y’ register MSCNT
A post was split to a new topic: TMC Reset / G1 Error
Hi guys, I’ve just encountered the same problem. I’d like to point out that sometimes the problem is an actual mecha-electrical problem. In my case, it was a worn-out wire on the extruder. I have a direct-drive extruder with the cable sticking back. It turns out that one of the crimped cables just snapped, and moreover, the plug from the extruder was recessed a little bit.
I’m running a strongly modified Ender 3 with SKR 3 board, Klipper, linear rails and a second Y axis to keep the construction as rigid as possible. Most of the mods I’ve done using parts from aliexpress (like the X-axis carriage, Y-axis plates and the extruder). However, the extruder has been turned 90° so that the cables, as mentioned before, stick out to the back. In afterthought, I think I’m going to have to modify that part a bit so that there is less strain on the extruder cable.
Like I said in the beginning, sometimes it actually is a mechanical and/or electrical problem, and it’s great that TMC reports those so that Klipper can stop printing. I guess the reason for SKR 3 being one of the boards that people report the issue the most is that it is so easy to set up the UART-based communication with the drivers and as such, those problems just appear more often.