2 weeks and already went bad? Duet 2 Wifi?



  • Recieved my Duet 2 Wifi april 4th 2020

    Got it wired and had been printing calibration cubes with no issue, until today.

    I started a print and the bed did not trip my z stop (it did prior while homing and previous prints). Printer bed and hotend got to temperature and printer moved to start printing and started feeding filament about 6mm off the bed. I clicked e-stop on the duet webpage. Now the printer will not read temperatures it says there is a fault and reads 2000 on bed and hot end. 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.

    I looked at the fuses and they look fine.



  • temp of 2000 suggest disconnected wire on the thermistor, or possibly a short on f.ex. the hotend causing the polyfuse to fail and cause all sorts of interesting cascading failures.

    examine the hotend for any signs of faulty wirng. did not hitting the z stop cause a crash?



  • This post is deleted!


  • @bearer
    EzeE
    EzeE 20 Apr 2020, 17:54

    It touched off the z stop during initial home. before I started the print and homed all. I have checked hotend and bed thermistor wiring and it appears okay.

    One issue that that I did not mention that happened a few days ago was the z-probe stopped working as well. I chocked it up to a cheap probe and ordered a BL Touch so I disconnected the probe for now.



  • can you disconnect the hotend thermistor and measure the resistance across the connector with a multimeter? you should get to the terminals on the inside from the back side of the connector. it should read close-ish to 100k most likely.

    then (with power off) measure from the vssa pin on the thermistor header on the board and to the Vin ground. (ref wiring diagram) it should be close to 0.



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

    can you disconnect the hotend thermistor and measure the resistance across the connector with a multimeter? you should get to the terminals on the inside from the back side of the connector. it should read close-ish to 100k most likely.

    then (with power off) measure from the vssa pin on the thermistor header on the board and to the Vin ground. (ref wiring diagram) it should be close to 0.

    115k on thermistor, VSSA to V-in Gnd 1 ohm



  • that should be all good.

    maybe add your config and any config-override file, but given the description not sure its a config issue



  • ; Configuration file for Duet WiFi (firmware version 2.03)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Apr 04 2020 15:16:06 GMT-0700 (Pacific Daylight Time)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"Tronxy X5ST-500" ; set printer name

    M667 S1 ; select CoreXY mode

    ; Network
    M550 PTronxy X5S ; Set machine name
    M552 S1 ; enable network
    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    ; Drives
    M569 P0 S0 ; physical drive 0 goes forwards
    M569 P1 S0 ; physical drive 1 goes forwards
    M569 P2 S1 ; physical drive 2 goes backwards
    M569 P3 S1 ; physical drive 3 goes backwards
    M584 X0 Y1 Z2 E3 ; set drive mapping
    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E142.00 ; set steps per mm
    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
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X500 Y500 Z600 S0 ; set axis maxima

    ; Endstops
    M574 X1 Y1 Z1 S0 ; set active low and disabled endstops

    ; Z-Probe
    M558 P5 H5 F0 T6000 ; set Z probe type to switch and the dive height + speeds
    G31 P600 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height
    M557 X15:215 Y15:195 S20 ; define mesh grid

    ; Heaters
    ;M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0
    ;M143 H0 S120 ; set temperature limit for heater 0 to 120C
    ;M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
    ;M143 H1 S280 ; set temperature limit for heater 1 to 280C

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S1 I0 F500 H1 T45 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Tools
    M563 P0 D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

    ; Custom settings are not defined

    ; Miscellaneous
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss



  • @bearer No overrides



  • @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



  • ; 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


  • Moderator

    @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.



  • This post is deleted!


  • @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?



  • @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.


  • Moderator

    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?



  • @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.


  • Moderator

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




  • Moderator

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

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



  • yes I am using nylon washers and stand off posts



  • @dc42 , does this quality for warranty replacement?


  • Moderator

    @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.



  • @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.



  • @Phaedrux

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


Log in to reply