Duet 3 Mini 5+ Short to Ground Error
-
@phaedrux I am using stealthchop, M122 result:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: WB4NT-F096U-D65J0-40KM2-0Q03Z-ZJYMR Used output buffers: 3 of 40 (36 max) === RTOS === Static ram: 102724 Dynamic ram: 106092 of which 12 recycled Never used RAM 34876, free system stack 204 words Tasks: NETWORK(ready,15.0%,264) HEAT(delaying,0.0%,366) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,340) TMC(notifyWait,0.6%,115) MAIN(running,82.7%,426) IDLE(ready,0.7%,29) AIN(delaying,0.8%,274), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:37 ago, cause: power up Last software reset at 2022-01-06 21:02, reason: User, GCodes spinning, available RAM 31628, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 37895, completed 37895, timed out 0, errs 0 Step timer max interval 1480 MCU temperature: min 15.6, current 20.2, max 20.4 Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 1959, writes 10, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1959, writes 9, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1959, writes 9, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 1959, writes 9, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 10, reads 1958, writes 10, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2022-01-07 17:26:56 Cache data hit count 72624651 Slowest loop: 6.64ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.8ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1, chamberHeaters = -1 -1 === GCodes === Segments left: 0 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 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 338, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 189/0/0 Tx timeouts 0,0,188,0,0,148 last cancelled message type 4514 dest 127 === Network === Slowest loop: 27.87ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address f0:08:d1:02:e6:60 WiFi Vcc 3.40, reset reason Power up WiFi flash size 2097152, free heap 24672 WiFi IP address 192.168.86.30 WiFi signal strength -47dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 2 0 0 0 0 0 0``` I have checked over wiring and even replaced motors several times. -
-
@phaedrux Apologies
; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Jun 30 2021 18:28:51 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Hermione" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet M587 I192.168.86.24 ; Drives M569 P0.0 S1 D3 V0 ; physical drive 0.0 goes forwards M569 P0.1 S0 D3 V0 ; physical drive 0.1 goes forwards M569 P0.2 S0 D3 V0 ; physical drive 0.2 goes forwards M569 P0.3 S0 ; physical drive 0.3 goes forwards M569 P0.4 S0 D3 V0 M584 X0 Y1 Z2:4 E3 ; two Z motors connected to driver outputs Z and E1 M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X100.00 Y100.00 Z400.00 E409.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X15000.00 Y15000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min) M201 X4000.00 Y4000.00 Z120.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z400 E600 I30 ; set motor currents (mA) and motor idle factor in per cent M84 X Y E0 S30 ; Set idle timeout M671 X-10:240 Y0:0 S3 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X240 Y205 Z210 S0 ; set axis maxima ; Endstops M574 X1 S3 ; configure sensorless endstop for low end on X M574 Y1 S3 ; configure sensorless endstop for low end on Y ; Z-Probe M558 P5 C"^io2.out" H2 F600 T6000 A3 ; Prusa PindaV2 Endstop M308 S2 P"temp2" A"Pinda V2" Y"thermistor" T100000 B3950 ; Prusa PindaV2 Thermistor G31 P1000 X-35.75 Y-18.7 Z.68 ; Nozzle offset M574 Z1 S2 ; Set Z axis endstop, controlled by probe M557 X0:180 Y0:180 P3 ; Define mesh grid for probing M376 H2 ; Fade height 5mm M564 S0 ; ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B0 R0.274 C426.1 D11.33 S1.00 V24.0 ; control parameters for H0 M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 R2.203 C200.0:140.4 D5.77 S1.00 V24.1 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out5" Q500 ; M106 P0 C"Part Cooling" S0 H-1 ; ; M950 F1 C"out6" Q500 ; M106 P1 C"Hotend" S1 H1 T45 ; ; ; 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``` -
I think it may be related to stealthchop. Can you test with spreadcycle for a while?
-
@phaedrux Yes, I can.
-
@3dmakerkid actually, Does sensorless homing require stealthchop to be on? I can't seem to recall
-
I think stallguard works with stealthchop, but I don't think you need stallguard configured to use stealthchop.
Additionally, the TMC2209 stepper driver used in Duet 3 Mini 5+ (and Duet 3 Tool board TOOL1LC once stallGuard is implemented in firmware), features stallGuard 4. This is optimised for operation with stealthChop, while its predecessor stallGuard 2 (TMC5160 and TMC2260) works with spreadCycle. You will need to adjust the speed at which stealthChop changes over to spreadCycle. This is set by M569 V parameter. The default is 2000.
https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing
-
@phaedrux Ok, I'm using sensorless homing on this printer and it looks like it can't be used with spreadcycle, as I found out here https://teamgloomy.github.io/sensorless.html .
-
Well you'd switch between as needed I guess.
Stealthchop isn't really recommended for printing unless you're limiting your speed and acceleration due to the loss of torque in exchange for absolute quiet.
-
@phaedrux It's now doing the same thing as before except just when the machine is powered on instead of after a print, and I changed nothing. So I'm not sure how much switching stealthchop off is going to help in this case.
-
As we can't rule out whether there is an error with the stepper or not, we will replace the board under warranty.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
-
@phaedrux You guys are awesome, I'll get that done as soon as I can!
