[BUG] E driver error detected: 0x1075052576 coil short circuit

[rick-ryerson]

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

After installing bugfix-2.0.x on SKR 1.4 Turbo and running a calibration cube, the printer halts and says to "reset" with the following message in octopi terminal.

Recv: E driver error detected: 0x1075052576.0000000000000000
Recv: coil short circuit

Attached are all the appropriate files
octoprint-output.txt
platformio.ini.txt
Configuration.h.txt
Configuration_adv.h.txt

Bug Timeline

Errors in bugfix-2.0.x; Works in 2.0.4

Expected behavior

I expected the printer to print the calibration cube.

Actual behavior

The printer halted and said to reset.

Steps to Reproduce

Compile bugfix-2.0.x with the attached files
Deploy to SKR 1.4 Turbo
Verify BLTouch is working
Autohome

Use OctoPi to load and print a calibration cube
Watch autobedleveling work
watch printer print rim of cube

watch printer fail after attempting to print inside cube rim.

Version of Marlin Firmware

bugfix-2.0.x

Printer model

Ender 3 Pro

Electronics

SKR 1.4 Turbo, TMC2208 drivers

Add-ons

Creality BLTouch 3.x

Your Slicer

Cura

Host Software

OctoPrint

Additional information & file uploads

files.zip

I tried 2.0.9, 2.0.8 and 2.0.7 plus the version that BTT hosts on their github. 2.0.6.x All these have the same results.

Recv: E driver error detected: 0x1075052576.0000000000000000
Recv: coil short circuit

A quick search of reddit in /r/BIGTREETECH will show you other instances of people having the same issue and reverting to 2.0.4 for a working printer.

I tried to report this as a bug last week and you closed it. Don't ignore this again. It's a repeatable bug, and is correctable by going back to 2.0.4

I replaced the stepper motors with brand new Creality motors and the error still happens on bugfix-2.0.x

[GMagician]

This may be disabled by commenting, in configuration_adv.h, below line:
#define STOP_ON_ERROR
but I think its an error reporter by TMC driver (for 10 times consecutively)

[rick-ryerson]

This may be disabled by commenting, in configuration_adv.h, below line:
#define STOP_ON_ERROR
but I think its an error reporter by TMC driver (for 10 times consecutively)

Doing that just makes it so the printer doesn't halt. The stepper stops advancing or retracting.

In the error message, this is the status of the stepper 0x1075052576

[Holm-tech]

I have exactly the same issue.

Well fault code is a bit different but...
Recv: E driver error detected: 0x1075380256
Recv: coil short circuit

Version of Marlin Firmware
bugfix-2.0.9

Printer model
FolgerTech FT-5

Electronics
SKR 1.4 Turbo, TMC2208 drivers

Add-ons
BLTouch

Your Slicer
Cura

Host Software
OctoPrint

[DerAndere1]

The root cause is probably the bug described in #15797

[rick-ryerson]

That'd be cool. Either way, it'd be nice to be able to upgrade.

[thinkyhead]

Are you able to narrow down the version of Marlin or the date range where the bug starts to appear? That can help us to narrow down which change(s) led to this bad behavior.

[sjirafje]

Same issue here. Printer halts in the first layer.

E driver error detected: 0x1074921488.0000000000000000
coil short circuit
echo:Driver error
Error:Printer halted. kill() called!
[ERROR] Error:Printer halted. kill() called!

//action:poweroff

Version of Marlin Firmware: 2.0.9.1
Printer model: Creality Ender 5 Plus
Electronics: SKR 1.4 Turbo, BTT TFT35,
Add-ons: TMC2208, Biqu H2 Extruder, dual Z

[rsperry79]

The root cause is probably the bug described in #15797

I get the same error when I am entering commands in the terminal manually. Turing STEALTHCHOP off for E in the control panel did allow me to run the following commands without error. With it on I get the above error.

G0 X10 Y10 F9000
G0 Z0.15
G1 Y90 E50 F500

[rsperry79]

Pulled the latest bugfix and this is now working as expected

[wundi22]

Unfortunately the exact same issue here for me. It just stops printing on the first layer and I need to reset the printer.

my fault code is again different to the others
Recv: E driver error detected: 0x1075314720
Recv: coil short circuit

Version of Marlin Firmware
bugfix-2.0.x (Latest Revision 06 September 2021)

Printer model
Custom - CoreYX motion system

Electronics
BTT SKR Pro 1.2 with TMC2225 drivers (essentially the same as TMC2208)

Add-ons
Inductive probe connected to the BLTouch pin set

Your Slicer
PrusaSlicer2.3.3

Host Software
OctoPrint

Update - Changing my E0 from stealthchop to spreadcycles in the firmware seems to fix the problem albeit noisier than desired. Hope this helps

[elminster]

Same issue here. Although I get the error for Z rather than E. And the issue normally takes several hours before it occurs.

BTT SKR 1.4 Turbo with TMS2209, sensorless homing and BLTouch homing.

Changing Z (and I did E0 to be on the safe side) from stealthchop to spreadcycles fixed the issue, and allowed prints that never finished to complete.

Upgraded from 2.0.5_3 (ran for a year or so, no issues) to 2.0.9_1.

[github-actions]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[rick-ryerson]

Replying to keep alive. It would be nice to have corrected so I can update to latest version.

[arminth]

Randomly, I have the same issue with a 2208 on E0 on an SKR 1.4 Turbo LPC1769. When I deactivate stealthchop, it seems to work. I will now try this solution:
https://techoverflow.net/2021/11/16/how-to-fix-marlin-random-driver-error-detected-coil-short-circuit-crash-trinamic-tmc/
will report on any success.
Cheers
Armin

[arminth]

Didn't compile with latest bugfix. so no solution.

[tockmos]

I have BTT SKR 2/TMC2208. I get: E driver error detected: 0x40190010, coil short circuit. after 2 min.
Tried to change stepper and inserting st.diss2g(true); in trinamic.cpp, no luck.
Can’t downgrade to Marlin 2.0.4 because it doesn’t recognize SKR 2.
NEED HELP!

[arminth]

Try to switch the E Stepper to spread cycle. This helped for me and I didn't get any errors any more. Not that it is a great solution but a solution after all.

[tockmos]

Try to switch the E Stepper to spread cycle. This helped for me and I didn't get any errors any more. Not that it is a great solution but a solution after all.

It seems to work, (didn’t store it in EEPROM on first try).
I have printed for 10 min now 😊
Thank You!

[arminth]

Good luck for next 100 hours!

[blindley125]

So I have this same issue when compiling the latest release 2.0.9.03. I have been able to determine that it is related to Linear Advance. If I leave it disabled everything runs as normal. If I enable Linear advance it faults out with the Same Error posted in this thread. For now I am just running without Linear Advance .

[arminth]

You can use linear advance but you have to switch to spread cycle!

[dannyglover]

Any progress on this issue? I'm also experiencing it.

[blindley125]

Actually the driver burnt up and I switched to an SKR 2 board. However after investigating the board I believe I had the jumpers in UART and SPI mode which may be the leading issue so maybe start there.

…

On Thu, Mar 10, 2022 at 8:03 AM Danny ***@***.***> wrote: Any progress on this issue? I'm also experiencing it. — Reply to this email directly, view it on GitHub <#22312 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN5IEHWLAUIPKSPIXXFDI4LU7HXKBANCNFSM477T5MCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[dannyglover]

Actually the driver burnt up and I switched to an SKR 2 board. However after investigating the board I believe I had the jumpers in UART and SPI mode which may be the leading issue so maybe start there.

Hey.

I don't have that problem at my end at least. I'm using an SKR 1.4 and have repeatedly checked that my 2208's are setup for UART both in hardware and firmware, and the correct jumpers are used.

I did have an interesting development though. With LIN_ADVANCE enabled, the 4 prints I had failed midway through the first layer, whilst printing the XYZ calibration cube, at the same exact place. Moaning about the E driver.

After disabling LIN_ADVANCE, I tried printing it again. It completed the print first go with no issues.
Thoughts?

[blindley125]

That was my issue in a nut shell as soon as linear advance was used it would stop extruding or stop with E driver error . I don’t have this issue on the same board on my Ender 5 plus using 2209 and marlin 2.0.9.1. So maybe try an earlier version of marlin as well.

…

Sent from my iPhone

On Mar 10, 2022, at 12:19 PM, Danny ***@***.***> wrote:  Actually the driver burnt up and I switched to an SKR 2 board. However after investigating the board I believe I had the jumpers in UART and SPI mode which may be the leading issue so maybe start there. … On Thu, Mar 10, 2022 at 8:03 AM Danny @.> wrote: Any progress on this issue? I'm also experiencing it. — Reply to this email directly, view it on GitHub <#22312 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN5IEHWLAUIPKSPIXXFDI4LU7HXKBANCNFSM477T5MCQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.> Hey. I don't have that problem at my end at least. I'm using an SKR 1.4 and have repeatedly checked that my 2208's are setup for UART both in hardware and firmware, and the correct jumpers are used. I did have an interesting development though. With LIN_ADVANCE enabled, the 4 prints I had failed midway through the first layer, whilst printing the XYZ calibration cube, at the same exact place. Moaning about the E driver. After disabling LIN_ADVANCE, I tried printing it again. It completed the print first go with no issues. Thoughts? — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

[thisiskeithb]

@dannyglover If you're running TMC2208s/TMC2225s, this is a known issue and they will shutdown: #16076.

Disable LIN_ADVANCE or switch to a different driver.

[dannyglover]

@dannyglover If you're running TMC2208s/TMC2225s, this is a known issue and they will shutdown: #16076.

Disable LIN_ADVANCE or switch to a different driver.

Thanks Keith. Good to know.
Thankfully I don't use linear advance anyway, I just forgot to disable it initially in the config file.

I assume this issue isn't a "you can't use linear advance with these drivers" and more of a "we're looking into fixing it" situation?
Cheers.

[azjose]

I have the same issues on Y though. This on MKS Robin Nano v1.2 using 2.0.9.3 2208 drivers

Not using Linear Advance and turned off stealth chop.

Recv: Y driver error detected: 0x40190010
Recv: coil short circuit
Recv: 		X	Y	Z	Z2
Recv: Enabled		true	true	true	true
Recv: Set current	800	800	800	800
Recv: RMS current	795	795	795	795
Recv: MAX current	1121	1121	1121	1121
Recv: Run current	25/31	25/31	25/31	25/31
Recv: Hold current	12/31	12/31	12/31	12/31
Recv: CS actual	25/31	25/31	18/31	18/31
Recv: PWM scale
Recv: vsense		1=.18	1=.18	1=.18	1=.18
Recv: stealthChop	true	true	true	true
Recv: msteps		16	16	16	16
Recv: interp		true	true	true	true
Recv: tstep		161	159	max	max
Recv: PWM thresh.
Recv: [mm/s]
Recv: OT prewarn	false	false	false	false
Recv: triggered
Recv:  OTP		false	false	false	false
Recv: pwm scale sum	74	68	30	28
Recv: pwm scale auto	-2	0	2	0
Recv: pwm offset auto	58	45	51	50
Recv: pwm grad auto	12	19	30	48
Recv: off time	4	4	4	4
Recv: blank time	24	24	24	24
Recv: hysteresis
Recv:  -end		2	2	2	2
Recv:  -start		1	1	1	1
Recv: Stallguard thrs
Recv: uStep count	8	504	968	424
Recv: DRVSTATUS	X	Y	Z	Z2
Recv: sg_result
Recv: stst
Recv: olb
Recv: ola
Recv: s2gb
Recv: s2ga
Recv: otpw
Recv: ot
Recv: 157C
Recv: 150C
Recv: 143C
Recv: 120C
Recv: s2vsa			*
Recv: s2vsb
Recv: Driver registers:
Recv: 		X	0xC0:19:00:00
Recv: 		Y	0xC0:19:00:10
Recv: 		Z	0xC0:0E:00:00
Recv: 		Z2	0xC0:0E:00:00
Recv: 
Recv: 
Recv: echo:Driver error
Recv: Error:Printer halted. kill() called!
Changing monitoring state from "Printing" to "Error"

[ellensp]

An Interesting discovery on another board bigtreetech/BIGTREETECH-OCTOPUS-V1.0#114
I don't know if this is related, but the 1.4 board also has tmc's butted together.
So give this a try. Put some kapton tape between the stepper module that errors and its neighbours

[rick-ryerson]

@ellensp considering that link is to a "theory" of a hardware problem, and that this problem is worked around by going back to a previous version of the software, I'm going to say they aren't related.

[charlesrg]

Having the same problem with BTT SKR PRO 1.2. Trying to print the same pattern and both times errors on first layer.
Recv: E driver error detected: 0x40170060
I'm running 2.0.9.4

[parallyze]

Having the same problem with BTT SKR PRO 1.2. Trying to print the same pattern and both times errors on first layer. Recv: E driver error detected: 0x40170060 I'm running 2.0.9.4

Out of curiousity: Which "same problem" do you refer to? Looking at this thread there's the inital post with a
different driver error, various reports of people having "same problems" with either the e or the z axis and different
error codes.... and the ones who disabled StealthChop on the extruder, which seemed to solve their problem.
And the ones who said they had StealthChop disabled and problems with the Y axis right before posting a log which says "true" for "stealthChop" on X, Y, Z and Z2.... maybe you'd like to add one or more details of your setup, the stepper drivers you're running and if you're using linear advance in combination with stealthchop? Maybe config files? It's a bit hard trying to keep all those "same problems" apart.... ^^

And unless I'm missing it the thread starter didn't tell if disabling StealthChop on E did change anything... according to the config files he's using TMC2208s, LIN_ADVANCE and STEALTHCHOP_E.

#16076 might be what's causing trouble for you, try disabling StealthChop on E if you're using TMC2208/TMC2225.

[charlesrg]

Sure, I'm doing a print test now to confirm I can reproduce the problem just by changing firmware. So far no issues with 2.0.9.3
I've tried 2.0.9.4 twice and both failed, now trying 2.0.9.3 and will try bugfix-2.0.x next.
My error is on the Extruder: Recv: E driver error detected: 0x40170060

I'm using TMC2209 with BIQU H2
Both binaries have #define STEALTHCHOP_E

Linear Advance is enabled in the firmware but disabled on the GCODE as I didn't have time to tune it yet.

[charlesrg]

I ran the same 5 hour print on bugfix-2.0.x and I've got no error. I've Configuration.h Configuration_adv.h and pins exactly the same as on 2.0.9.4. So I'm assuming the issue is resolved in the bugfix.

[joaoachando]

I have an skr 1.4 turbo with tmc2208 and can confirm that this error still exists in bugfix 2.1.x

[AapoTahkola]

It seems that there is another bug which means that none of the defines STEALTHCHOP_XY etc. have no effect and stealth chop is always on.
#undef STEALTHCHOP_XY
#undef STEALTHCHOP_Z
#undef STEALTHCHOP_E
also has no effect
but "M569 S0 X Y Z E" followed by "M500" does disable them. More noisy and M122 has them disabled.

[rick-ryerson]

It's been a year now. Can we expect someone to be assigned to this bug?

[AapoTahkola]

I think the Linux kernel folks deal with this kind of stuff all the time. If things start getting worse then at some point the process of booting patches even at random starts until things start looking little bit better again.

[thisiskeithb]

Disable LIN_ADVANCE with TMC2225/TMC2208s or they will shutdown. This is a known bug with these drivers: #16076

[thisiskeithb]

Duplicate of #16076

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.