Error Short to Ground reported by driver(s)

davidewen

I have a couple large / long print jobs that need to be completed. Customers are waiting for product, so I will not be able to do this until sometime late next week.

There is nothing conductive under the board. It is elevated off the Ender 6 mounts by a 3D printed PETG spacer.

davidewen

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen with power off please unplug the motor from driver 3, then power up, command driver 3 to move and see if you get the same error message.

Also check that there is nothing conductive under the board that it could be shorting against.

I would to make a note for us to refer back to should it be needed.

After the 1st failure of D3, I moved the Extruder to D4 with no problems since.

When @droftarts sent the 1st request for info on 9/17, I reconnected the Extruder to D3 and revised my config.g to match.

I was able to run for about 20-30 minutes before the error "short to ground" was reported.

I suspect this will be the same when I move the extruder back to D3 again.

I don't think it will do any good if D3 is not reporting the error, so I'm suspecting that you will want me to run it until the error shows up, then run the test you requested?

Please confirm.

David

dc42

@davidewen if RRF reports an intermittent "short to ground" message, then normally either there is a genuine intermittent short in the wiring, or the message is caused by running the driver in stealthChop mode and you are trying to move the motor too fast (this is a behaviour documented by Trinamic). Are you running that driver in stealthChop mode at high speeds?

If the message is caused by a driver failure, then normally the error occurs immediately you try to move the motor.

davidewen

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen if RRF reports an intermittent "short to ground" message, then normally either there is a genuine intermittent short in the wiring, or the message is caused by running the driver in stealthChop mode and you are trying to move the motor too fast (this is a behaviour documented by Trinamic). Are you running that driver in stealthChop mode at high speeds?

If the message is caused by a driver failure, then normally the error occurs immediately you try to move the motor.

As far as I know, I am not running in stealth/chop mode.
Is there some way I can test / confirm that?

As far as a short in the wiring.
Why would I get the error only for D3 and not on D4?

David

davidewen

@dc42

Any update to this case yet?

Thanks,
David

davidewen

@dc42

Have you had the opportunity to look over my last post from Sept 28?

Are there any other questions or tests you want me to run or can I get a RMA for a replacement board?

@davidewen said in Error Short to Ground reported by driver(s):

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen if RRF reports an intermittent "short to ground" message, then normally either there is a genuine intermittent short in the wiring, or the message is caused by running the driver in stealthChop mode and you are trying to move the motor too fast (this is a behaviour documented by Trinamic). Are you running that driver in stealthChop mode at high speeds?

If the message is caused by a driver failure, then normally the error occurs immediately you try to move the motor.

As far as I know, I am not running in stealth/chop mode.
Is there some way I can test / confirm that?

As far as a short in the wiring.
Why would I get the error only for D3 and not on D4?

David

dc42

@davidewen we will replace the Duet. Please email warranty@duet3d.com and include a link to this thread.

davidewen

@dc42 said in Error Short to Ground reported by driver(s):

@davidewen we will replace the Duet. Please email warranty@duet3d.com and include a link to this thread.

Thank you.

I have sent an email as requested.

David

davidewen

@dc42
I received the replacement board.

Swapped old board with new board.
Put SD card from old board into new board.

Could not connect via Wi-Fi.
Took new board out.
Put SD card that came with new board back in.
Connected USB to Mac. (macOS 11.6.1 with M1 chip)
Could not detect board

Followed "Fallback 1 & Fallback 2" instructions @ https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

Neither worked.
Still can not connect to board via USB
Board does not show up in System Information, or in Terminal via ls /dev/tty.*.

Any suggestions?

Thanks,
David

T3P3Tony

@davidewen with nothing other than the power plugged inot the board, what LEDS are lit? also please send a picture of the board.

davidewen

@t3p3tony

R40 = off
R49 = flashing red (slow flash)
R28 = off
R27 = off
R29 = Red
P30 = Green
ESP = off

elmoret

@T3P3Tony Could you assist David, please?

T3P3Tony

@davidewen with it setup as you have it in the image above, please double click the reset button and see if a Duetboot drive becomes available on the PC over USB. If it does then you can drop the 3.3 firmware for mini 5+ into that drive, it will.opy across then install. After that it should be available over YAT.

Firmware is here:

Duet3Firmware_Mini5plus.uf2
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet3Firmware_Mini5plus.uf2

davidewen

@t3p3tony
Tony, as mentioned in a previous post.
I have followed all instructions for Fallback 1 & 2 per the guide.
Neither work. Board is not found on computer under System Information, via Terminal or Disk Utility.

@davidewen said in Error Short to Ground reported by driver(s):

Followed "Fallback 1 & Fallback 2" instructions @ https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
Neither worked.
Still can not connect to board via USB
Board does not show up in System Information, or in Terminal via ls /dev/tty.*.

Results from Terminal
@Macmini-M1 ~ % ls /dev/tty..
zsh: no matches found: /dev/tty..

Results from System Information.
This is what shows up when board is plugged in.

Results from Disk Utility
I do get a "DuetBOOT" after double clicking the reset button, and copying the firmware to the drive does cause a restart, but then I'm back to square 1.

No Duet in System Info or Terminal.
Even with a good copy of sys folder files, no Duet on my WiFi.

T3P3Tony

@davidewen if DuetBoot shows up and the file is transferred successfully then at least part of the USB system is working as expected. I don't have a Mac to test this on - there might be some interaction between the USB driver in that particular version of MacOS/Mac hardware and the Duet. Or it might be a (partially) faulty USB hardware on the Duet.

Would it be possible to try connecting on a PC/laptop running windows?

davidewen

@t3p3tony
I don't have a Windows computer. I do run Windows in Parallels and/or Bootcamp, but still on a Mac computer.

I've tested the connection on the new M1 macMini and an older Intel based MacBookPro_2017. Same issue on both.

I attempted to connect via Parallels.
Did not work.
Could not update the device drivers.

T3P3Tony

@davidewen in that screenshot it showed a serial port on com4 - is that the Duet?

davidewen

@t3p3tony
yes, that's correc

T3P3Tony

@davidewen ok so what happens when you connect to com4 with YAT?

davidewen

@t3p3tony
I have Macs only, so I'm using SerialTools.

Your (dozuki) instructions are not very clear.
First you state to connect using SerialTools.
Then you never show any examples of SerialTools again.
You only show using Terminal.
Some consistency within your instructions would be helpful.

https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7

It looks like I can connect, but there is no information displayed.

And Terminal will not connect