RRF 3.4 Will Not recognize my Extruder
-
@siam Sorry, I did that trying to get things to work. Currently, config.g is set using M584 X0 Y1 Z2 E3 with the same result. The rest of the attached file is correct except for the T0 you suggest I add. I also connected the Y motor cable to the extruder and the stepper worked as you would expect.
-
@jadoglio Do I understand it right when you disconnect the cable from driver 3 and connect it to the unused Driver(5) everything is working ? If yes, I would say there is a technical Problem with the driver 3
-
@siam I hope this is not too confusing. I connected the cable from E0 to driver 0 (X Axis) to the extruder motor and the motor worked normally. So the cable and the motor seem to be good. I then connected the X axis cable from driver 3 (E0) to the x axis stepper and it caused the same error. I also connected driver 4 (E1) to both E0 and X stepper motors and got the same error. I am beginning to wonder if the E0 and E1 drivers are bad. That seems unlikely since I had no issues until now. I am really flummoxed on this one. I have been using this Duet configuration for over 3 years with no issues.
-
Please post your current config.g, and the results of sending M122 and M98 P"config.g"
@jadoglio said in RRF 3.4 Will Not recognize my Extruder:
Driver 3 error: phase A short to ground
Double check the crimps and the pins on the board.
Did you happen to unplug a cable while the board was powered on?
-
@jadoglio weird can you post the result of M122 and M98 P"config.g"
-
Siam and Pheadrux
Thanks again for helping here.
The cables and stepper work fine when I connect them to one of the X Y or Z drivers on the board so I don't think that is a problem. I did not disconnect anything with the power on that I know of... but anything is possible. I have attached the files you requested. Hope they help.
-
@jadoglio Also, here is my current config.g and the results of issuing a extrude command at 200C from the dashboard. Homing for all other steppers works fine.
-
M584 X0 Y1 Z2 E1
Is your config still trying to use driver 1 twice?
Short to ground on driver 3 would indicate it's either a wiring fault or the driver is damaged. And since you've tested the motors and wiring on other drivers and it works, it would mean the driver is likely damaged.
Did anything else change recently along side the firmware update?
How long has this printer been up and running? When and where did you purchase the Duet?
-
No, config.g M584 X0 Y1 Z2 E3 is currently set as noted.
Nothing else changed as far as I know. If the driver is damaged (the extruder was connected to driver 4 at the time this started) would it also damage driver 3? Becasue, I get the same result when I connect the extruder to that driver as well.
I have been printing for 4 years with my heavily modified Ender 3 and running the Duet 2 Wi-Fi that I bought from Filastruder in May of 2019. As far as I know it is not a Chinese knockoff.
BTW... I get the same error when I heat up the hot end and then execute a extrude command with the extruder not even pluggged into the driver pins. So, it is failing even before it tries to send any signal to the extruder.... sounds more and more like a bad driver... is there any way to definitively prove that before I spend $170 on a new board?
-
Unfortunately that is well out of warranty, but occasionally we have refurbished boards we can offer at reduced cost on exchange. Please contact roland@duet3d.com to enquire about availability and include a link to this thread.
-
Maybe you can get an expansion driver board and map the driver off that vs. a new board or are there too many bad drivers ? coming late to this
-
@sputnikoc3d Thanks for the help. I ordered a new Duet 2 WiFi yesterday to get this machine up and running and it has already shipped. I also ordered a new Prusa XL... unfortunately that wont ship until who knows when.... but if I ever get it it will replace this machine. Thanks to Phaedrux, Siam, and yourself for trying to help.
-
@jadoglio I installed the new board...big surprise everything works now. Thanks again for trying to help.
