2 weeks and already went bad? Duet 2 Wifi?

A Former User

@EzeE said in 2 weeks and already went bad? Duet 2 Wifi?:

Also now when I try to home Y access I get a message saying phase A may be disconnected while it actually runs X motor and not Y.

M667 S1 ; select CoreXY mode

thats kinda relevant i suspect, but i'll defer to the others for config and corexy stuff.

meanwhile, maybe throw in the homeall, homex and homey files

EzeE

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Apr 04 2020 15:16:06 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-505 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 H1 X-505 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Apr 04 2020 15:16:06 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y-505 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 H1 Y-505 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Apr 04 2020 15:16:06 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Z-605 F1800 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Phaedrux

@EzeE said in 2 weeks and already went bad? Duet 2 Wifi?:

Also now when I try to home Y access I get a message saying phase A may be disconnected while it actually runs X motor and not Y.

Check your wiring. With CoreXY two motors produce the X and Y motion, not just one. So if only one is moving and it's complaining that there may be phases disconnected, it's probably right. Check you crimps on the motors cables.

EzeE

This post is deleted!

EzeE

@Phaedrux @Phaedrux said in 2 weeks and already went bad? Duet 2 Wifi?:

@EzeE said in 2 weeks and already went bad? Duet 2 Wifi?:

Also now when I try to home Y access I get a message saying phase A may be disconnected while it actually runs X motor and not Y.

Check your wiring. With CoreXY two motors produce the X and Y motion, not just one. So if only one is moving and it's complaining that there may be phases disconnected, it's probably right. Check you crimps on the motors cables.

Not sure exactly what you mean about checking the wiring they were working fine, no nicks felt wires look the same, none are loose. When I would hit home previous times it would move the Y motor just fine in fact it moved and homed it prior to the print. Now it throws an error and the X motor turns on when I hit home on the Y with no changes in wiring. Crimps look tight, I assumed they would I used proper crimping tool.

Also again Hotbed and Hotend both started reading 2k at same time, and z probe not working. I thought Z-probe was just cheap and I was using z-stop instead so didn't think much of it since I was going to replace with a BL-touch.

Hitting E-stop on webpage should not cause a board to wig out. If it does cause Duet problems why is it there?

EzeE

@Phaedrux I also understand that the X and Y motors produce the movement. If I take the belt off the y motor is does not spin. If I move my z cable to the Y motor it spins. If I use Y cable on X motor it spins. If I plug any motor into Y port it does not spin.

Phaedrux

It sounds like you've had a failure of the Y driver for sure. Possibly more.

Can you post some close up well lit high res photos of the board? Do you see any areas that look damaged, burnt, etc?

EzeE

@Phaedrux I'll take some pictures just post them here? Nothing looks burned that I can tell, I do know I do not smell any of that lovely ozone of burnt electronics.

Phaedrux

Yes please post them here, or on an online file sharing folder like dropbox or google drive.

EzeE

@Phaedrux Hopefully this works

https://drive.google.com/file/d/1l2wgaa3ZwHttCgenJIocm9l2QrbCGfBl/view?usp=sharing
https://drive.google.com/file/d/12Wt7HpUuwI5AxnGoN1vUtaYQgV5DXQV4/view?usp=sharing
https://drive.google.com/file/d/1maniM2el2XS4bAmyNfQ9xHAxUgfsI_gy/view?usp=sharing
https://drive.google.com/file/d/1A0D3gYaJUDsKnR63bWMDxyIBUiGFhl0R/view?usp=sharing
https://drive.google.com/file/d/1byWBEEtQa-88TeLkCA9kk5uMx245rpxX/view?usp=sharing
https://drive.google.com/file/d/1dD33aAgnptyP5pg68S3bUfBujc2Z32J4/view?usp=sharing
https://drive.google.com/file/d/1HD7ZJEE6i7H-KXD0x2lMC1UCaxksfRVa/view?usp=sharing

Phaedrux

I can't see any obvious signs of burnt chips.

Are you using the nylon washers to isolate the board from the mounting screws?

EzeE

yes I am using nylon washers and stand off posts

elmoret

@dc42 , does this quality for warranty replacement?

Phaedrux

@EzeE said in 2 weeks and already went bad? Duet 2 Wifi?:

I started a print and the bed did not trip my z stop

What exactly do you mean by this? Was there a head crash? The Y driver not working is one thing, but the thermistor reading 2000 would indicate a possible short.

EzeE

@Phaedrux

So when I started the print the X, Y, and Z all homed properly. The Z axis moved down and the extruder moved to the center of the bed. What should have happened but didn't is the Z should have moved up which usually trips Z sensor. Instead it sat there like it maybe thought it made the move and then started extruding with the bed not in place. Which is why I tripped the stop.

The Z not moving into position could be my fault since I unplugged z probe since it stopped working, but code is still in there.

There was no bed crash.

EzeE

@Phaedrux

Also when the Hot end started reading 2l the Bed went to 2k as well.

EzeE

@Phaedrux

Just fixed the Thermistors reading 2k. Found an old post about a delta printer having similar issue and the M305 lines being commented out. Scrolled up to look at config.g I posted and my M305 were commented. Loaded the backed up config.g file from printer and readings are 21 degrees idle.

So now just the Y not working. And possibly z-probe.

droftarts

@EzeE Please send M115 to the Duet, and post reply, to report the firmware version.

Were the X and Y axes moving particularly fast when you pressed estop? What motors do you have on X and Y? Standard TronXY X5ST-500? I notice you have the max speed, accelerations and motor currents set quite high:

M566 X600.00 Y600.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z180.00 E1500.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E250.00 ; set accelerations (mm/s^2)
M906 X1680 Y1680 Z1680 E950 I30 ; set motor currents (mA) and motor idle factor in per cent

Thinking maybe sudden stop during fast move caused a voltage spike back through the driver, killing the driver.

Ian

droftarts

@EzeE said in 2 weeks and already went bad? Duet 2 Wifi?:

@Phaedrux

Just fixed the Thermistors reading 2k. Found an old post about a delta printer having similar issue and the M305 lines being commented out. Scrolled up to look at config.g I posted and my M305 were commented. Loaded the backed up config.g file from printer and readings are 21 degrees idle.

So now just the Y not working. And possibly z-probe.

So... how did you manage to start the print? Did you send the M305 commands by hand? And I thought you said the probe wasn't working anyway (which is why it started printing 6mm off the bed)?

Ian

EzeE

@droftarts

The z probe worked for couple days then stopped. so I unplugged it while I await a new one one. I set it in slicer to move down 6mm for initial move to center then up 6mm to start the print.

No I loaded my backed up config.g which do not have the lines commented out. I'm not entirely sure how they got commented out in the first place. That is one I will be pondering for awhile.

Is it possible it somehow loaded the config.g.bak? I wouldn't think so but at this point I'm really confused.