Hey guys, first off love the duet wifi I have been using them on my other 2 printers for a while now and they are heads and shoulders above the rest I won't use anything else at this point. So I was told to post here by the folks at filastruder, I bought a duet2 wifi and duex5 on like Feb 8th and just got it this week, I had it up and running, then I added the BL touch probe and had it working fine still. I hadn't even done the first test print as I was getting the multi Z motor leveling working and once I got that working I went to do a "Self test" macro for the probe (M280 P7 S120 ; Send PWM channel 7 the S10 (angle) command) and then the printer turned off and has remained since.
I removed all the stuff connected to it and tried to just run it with only Vin 24V and all that happens is the Vin light turns on but nothing else was responding at all. I followed the trouble shooting guide on there and it said to try and connect it to the PC but then it just does nothing and nothing pops up and no lights come on.
I don't know what the next step here is maybe there is something I am missing but to my best approximation it seems toasted. The guys at Filastruder told me I had to post here to try to do any kind of troubleshooting / warranty stuff.
Thank you for your time
Could you post a clear, well lit photo oof the top of the board, especially the area around the fan connectors, please?
Tim here, from Filastruder. There's a hole in your 5 volt regulator, the part above the fan connectors. ICs don't work well with holes in them, it lets the magic smoke out
oh WOW I cannot believe I didn't notice that until just now. Is this a component I can replace if I know someone who can do small scale soldering like that?
Yes, if you know someone that can do hot air work. Other options are warranty coverage (unsure if this is covered, dc42/Tony would have the say), or repair through Filastruder (~$20).
Well awesome you guys are the best, how long would repair through filastruder would be? Honestly if its fixable and not a whole hassle I totally would not mind spending 20 bucks and y'all are close I'm in Florida.
If the board is within the warranty period, then it's covered for that fault. After 2 years of shipping many thousands of Duets and seeing zero failures of that chip, we've seen several in recent weeks and we don't yet know the cause. Possibly a substandard batch of chips.
Okay awesome, Its not even 2 weeks old yet so it should be covered then
Also can I just say @dc42 I have been super impressed over the last few months since I have joined team Duet how awesome the support here is
Thanks for your kind words, and for buying a genuine Duet!
Deanethiro last edited by Deanethiro
@dc42 So I sent back the broken board already, but I actually went ahead and started testing the Duex5 that was connected to it during the failure with a different Duet2 from one of my other printers and it seems none of the drivers want to work. Any ideas on troubleshooting or is the duex5 probably dead too?
Edit to provide more details: When the board is connected to the Duet2 and powered on no lights come on, but the 12V regulator is still regulating the 24Vin to 12V for the fans. When I go into the Settings page on the web interface it says "Duet WiFi 1.02 or later + DueX5". When I try to use any drivers to run a stepper motor it simply does nothing. The thermistor connectors work and show data, fan controllers seem to work fine as well. I did not test the heaters, but the PWM all seem to work fine as by BL touch is hooked up to PWM5 and it did its self test when I powered up the printer
That's an odd fault. The 3.3V feed to the DueX must be OK because it the Duet knows it is there, so the I2C expander chip on it is working. Normally I'd say that it looks like a missing VIN supply, but you report that you have a 12V output from the onboard regulator, so VIN must be present.
Please send M122 and report the output here, in particular the status of all the stepper drivers.
How did you try to use the stepper drivers on the DueX5?
How did you try to use the stepper drivers on the DueX5?
Here is the M122 results
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917DA-G4MSJ-6JTDJ-3SD6Q-TVN7A
Used output buffers: 3 of 20 (14 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98924 of which 0 recycled
Exception stack ram used: 328
Never used ram: 6296
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3844) IDLE(ready,200)
=== Platform ===
Last reset 00:31:47 ago, cause: software
Last software reset at 2019-02-20 10:53, reason: User, spinning module GCodes, available RAM 6296 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 32.3, current 33.6, max 33.9
Supply voltage: min 24.3, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2019-02-20 11:24:49
Cache data hit count 4294967295
Slowest loop: 5.27ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = 5 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 14.07ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address 80:7d:3a:3f:f5:90
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 15664
WiFi IP address 10.1.10.178
WiFi signal strength -35dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
I have 3 of the drivers ( 5 6 7 ) along with 2 as Z motor drivers and I have them mapped but when I try to do any Z moves only drive 2 moved
- WiFi -
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
; generated by RepRapFirmware Configuration Tool v2 on Mon Feb 11 2019 12:17:42 GMT-0500 (Eastern Standard Time)
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M667 S1 ; Select CoreXY mode
M550 P"Hypercube 25" V1" ; Set machine name
M552 S1 ; Enable network
M587 S"MkMachine2.4" P"9545725995" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S1 ; Drive 5 goes forwards
M569 P6 S1 ; Drive 6 goes forwards
M569 P7 S1 ; Drive 7 goes forwards
M569 P8 S1 ; Drive 8 goes forwards
M569 P9 S1 ; Drive 9 goes forwards
M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z1600.00 E420.00:420.00 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; Set accelerations (mm/s^2)
M906 X800.00 Y800.00 Z800.00 E800.00:800.00 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 X625 Y625 Z625 S0 ; Set axis maxima
M574 X1 Y2 S1 ; Set active high endstops
M574 Z1 S2 ; Set endstops controlled by probe
M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y-25 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:550 Y15:550 S40 ; Define mesh grid
M141 H5 ; Assign chamber heater to heater 0
M307 H6 B0 S1.0 ; Enable bang-bang mode for the bed heater and set PWM limit
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
M305 P2 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 2
M143 H2 S280 ; Set temperature limit for heater 2 to 280C
M305 P5 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 6
M143 H5 S120 ; Set temperature limit for heater 6 to 120C
M106 P0 S0 I0 F500 H-1 C"Parts Cooler Fan0" ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 C"Hotend Fan Fan1" ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P3 S255 I0 F500 H-1 C"LED Strip Fan3"
M563 P0 D0 H1 ; 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
M563 P1 D1 H2 ; Define tool 1
G10 P1 X25.784 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
; Automatic saving after power loss is not enabled
; Custom settings are not configured
M584 X0 Y1 Z6:7:5:2 ; Z Motor Mapping
M671 X-22.0:670.0:-22.75:670.0 Y127.0:127.0:500.0:500.0 S5. P2.
Your M584 command is in the wrong place. Please read the section on order dependency in the entry for M584 on the GCodes wiki page. Also the section flagged Important in bold.
Yup there we go turns out I am just stupid thank you so much