Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    duet 3 mini 5+ short to ground reported by driver 2

    Scheduled Pinned Locked Moved
    General Discussion
    2
    2
    146
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • juliannundefined
      juliann
      last edited by

      Hi

      I've been using the Duet 3 mini wifi since i got without any issues and have not made any modifications lately.
      But few days ago (maybe in coincidence with the 3.4.0beta6 update) it showed an error message (short to ground reported by driver 2).

      If I turn off/ on the printer or I press emergency stop few times sometimes the issue disappears and I am able to print again.
      I already checked all the wiring many times and everything seems to be fine. Actually the printer is being working perfectly since March 2021.

      Duet 3 Mini 5+ Wifi V0.5 with Expansion Mini 2+, SBC and tool board v1.1

      I think this is the exact same issue reported by another user here: https://forum.duet3d.com/topic/26124/duet-3-mini-5-short-to-ground-reported-by-driver-1

      config.g

      ; General preferences 
      
      G90                                     ; send absolute coordinates...
      M83                                     ; ...but relative extruder moves
      M550 P"duet3"                        ; set printer name
      M669 K1                                 ; CoreXY
      G21                                     ; Set Units to Millimeters
      
      ; Network
      M586 P0 S1                              ; enable HTTP
      M586 P1 S0                              ; disable FTP
      M586 P2 S0                              ; disable Telnet
       
       G4 S2   ;wait for expansion boards to start
       
      ; Drives
      M569 P0.0 S0 D3                         ; physical drive 0.0 goes forwards
      M569 P0.1 S0 D3                         ; physical drive 0.1 goes forwards
      M569 P0.2 S0 D3                         ; physical drive 0.2 goes forwards
      M569 P0.3 S1 D3                         ; physical drive 0.3 goes forwards
      M569 P0.4 S1 D3                         ; physical drive 0.4 goes forwards
      M569 P20.0 S0 D3                         ; physical drive 0.5 goes forwards
      M584 X0.4 Y0.3 Z0.0:0.1:0.2 E20.0        ; set drive mapping
      M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation
      
      ;LGX
      M92 X80.00 Y80.00 Z800.00 E412.35
      M906 X1200 Y1200 Z1000 E500 I30               ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                 ; Set idle timeout
      
      M566 X600.00 Y600.00 Z60.00 E600 P1          ; set maximum instantaneous speed changes (mm/min)
      M203 X10800.00 Y10800.00 Z1000.00 E3600.00     ; set maximum speeds (mm/min)
      ;M203 X60000.00 Y60000.00 Z1000.00 E3600.00     ; set maximum speeds (mm/min)
      M201 X5000.00 Y5000.00 Z100.00 E3600.00
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1                              ; set axis minima
      M208 X500 Y500 Z500 S0                         ; set axis maxima
      
      ; Endstops
      M574 X1 S1 P"20.io2.in"                           ; configure active high endstops
      M574 Y2 S1 P"io1.in"                           ; configure active high endstops
      M574 Z1 S2                                     ; configure Z-probe endstop for low end on Z
      
      ; Z-Probe
      ;; BLTouch
      M950 S0 C"20.io0.out"                     ; Create a servo pin on io3
      M558 P9 C"20.io0.in" F150 H4 R0.2 T12000 A5 B0  ; set Z probe type to unmodulated and the dive height + speeds
      
      G31 P1000 X-29.146 Y0 Z2.395
      
      M671 X-4.5:250:504.5 Y-4.52:505:-4.52 S50       ; Define positions of Z leadscrews or bed levelling screws
      M557 X10:460 Y15:470 S25                    ; define 5x5 mesh grid
      
      M563 P0 D0 H1 F1           ; define tool 0
      
      ; BED HEATER
      M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed"    ; configure sensor 0 as thermistor on pin temp0
      M950 H0 C"out0" T0                                     ; create bed heater output on out5 and map it to sensor 0
      M307 H0 B0 S1.00                                       ; disable 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 110C
      
      ;; BED Heater PID Tune JEN
      M307 H0 B0 R0.795 C325.9 D3.08 S1.00 V23.9
      
      ; Fans
      M950 F0 C"20.out2" Q25000                   ; create fan 0 on pin out3 and set its frequency
      M106 P0 C"Hotend Fan" S.5 H1 T45      ; set fan 0 name and value. Thermostatic control turned on for Hotend
      M950 F1 C"!20.out1+out1.tach" Q25000                   ; create fan 1 on pin out4 and set its frequency
      M106 P1 C"Layer Fan" S0 H-1 L0.2 X0.4     ; set fan 1 name and value. Thermostatic control is turned off
      M950 F2 C"!out3+out3.tach" Q25000                  ; create fan 1 on pin out4 and set its frequency
      M106 P2 C"Filter & Bottom Fans" S0 H-1 L255       ; set fan 1 name and value. Thermostatic control is turned off
      M950 F3 C"!out4+out4.tach" Q25000                  ; create fan 1 on pin out4 and set its frequency
      M106 P3 C"Exhaust Fan" S0 H-1 L255       ; set fan 1 name and value. Thermostatic control is turned off
      M950 F4 C"out5" Q10                  ; create fan 1 on pin out4 and set its frequency
      M106 P4 C"12vFANs" S1.0 H-1 L255       ; set fan 1 name and value. Thermostatic control is turned off
      
      ; Tools
      G10 P0 X0 Y0 Z0            ; set tool 0 axis offsets
      G10 P0 R0 S0               ; set initial tool 0 active and standby temperatures to 0C
      
      M308 S1 P"20.temp1" Y"thermistor" T500000 B4723 C1.196220e-7 ; PARA SLICE ENGINNERING HIGH TEMP
      M950 H1 C"20.out0" T1         ; create nozzle heater output on out2 and map it to sensor 1
      M307 H1 B0 S1.00           ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S301               ; set the maximum temperature in C for heater
      M307 H1 B0 R2.138 C163.4:146.8 D7.88 S1.00 V23.8
      
      
      ; Miscellaneous
      M575 P1 B57600 S1;enable panelDue UART
      M501                                               ; load saved parameters from non-volatile memory
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set tension thresholds and actions to run on power loss
      M404 N1.75 D0.4                                 ; Filament width and nozzle diameter
      
      ;DHT Sensor on IO4
      M308 S10 P"io4.out+io4.in" Y"dht22" A"Chbr Temp[C]"
      M308 S11 P"S10.1" Y"dhthumidity" A"Chbr Hum[%]"
      
      M591 D0 P3 C"20.io1.in" S0 R10:200 L22.00 E3.0 	; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection length
      
      ;Input Shaping
      M593 P"none"     ; disable DAA
      ;M593 P"mzv" F34.76
      
      ; Pressure Advance
      M572 D0 S0.06
      
      ;Taper Height
      M376 H20
      
      ; Set up Accelerometer
      M955 P20.0 I12 S1000 Q2000000 ; Accelerometer on toolboard, Enable for RRF 3.3 Stable
      T0
      
      

      m122

      m122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.4.0beta6 (2021-11-06 11:39:32) running on Duet 3 Mini5plus WiFi (SBC mode)
      Board ID: BJHV4-F396U-D65J0-40KML-NT03Z-74PH4
      Used output buffers: 1 of 40 (20 max)
      === RTOS ===
      Static ram: 103876
      Dynamic ram: 99104 of which 0 recycled
      Never used RAM 38732, free system stack 194 words
      Tasks: SBC(resourceWait:,3.1%,478) HEAT(notifyWait,0.0%,344) Move(notifyWait,0.0%,361) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,337) TMC(notifyWait,1.2%,105) MAIN(running,94.8%,507) IDLE(ready,0.1%,29) AIN(delaying,0.8%,264), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:19:08 ago, cause: software
      Last software reset at 2021-11-29 18:25, reason: User, GCodes spinning, available RAM 34916, slot 0
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU revision 3, ADC conversions started 1149342, completed 1149342, timed out 0, errs 0
      Step timer max interval 1477
      MCU temperature: min 29.9, current 30.1, max 42.9
      Supply voltage: min 23.9, current 24.0, max 24.0, 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: pos 0, standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 38880, writes 12, timeouts 0, DMA errors 0
      Driver 1: pos 0, standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 38880, writes 12, timeouts 0, DMA errors 0
      Driver 2: pos 0, standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 38880, writes 12, timeouts 0, DMA errors 0
      Driver 3: pos 0, standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 38879, writes 12, timeouts 0, DMA errors 0
      Driver 4: pos 0, standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 38880, writes 12, timeouts 0, DMA errors 0
      Driver 5: pos 0, standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 38883, writes 9, timeouts 0, DMA errors 0
      Driver 6: pos 0, standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 38883, writes 9, timeouts 0, DMA errors 0
      Date/time: 2021-11-29 18:44:22
      Cache data hit count 2676970072
      Slowest loop: 11.55ms; fastest: 0.10ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 0.0MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP* is doing "M122" 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
      === Filament sensors ===
      Extruder 0: no data received
      === CAN ===
      Messages queued 10337, received 23491, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 272, free buffers 17 (min 16), ts 5745/5744/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 4, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 45390/45390
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x0f120
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.4-b6
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 39.56, max wait times: 69.7ms/14.6ms
      Codes per second: 0.07
      Maximum length of RX/TX data transfers: 3596/832
      

      M122 b20

      M122 b20
      Diagnostics for board 20:
      Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta6 (2021-11-06 11:56:11)
      Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
      Never used RAM 2124, free system stack 2762 words
      Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,111) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.8%,350) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
      Last reset 00:25:20 ago, cause: software
      Last software reset data not available
      Driver 0: pos 0, 412.4 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 39441, writes 12, timeouts 0, DMA errors 0, steps req 0 done 0
      Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
      Peak sync jitter -2/9, peak Rx sync delay 211, resyncs 0/0, no step interrupt scheduled
      VIN voltage: min 24.3, current 24.4, max 24.4
      MCU temperature: min 47.8C, current 47.9C, max 50.5C
      Last sensors broadcast 0x00000002 found 1 237 ticks ago, 0 ordering errs, loop time 0
      CAN messages queued 31124, send timeouts 0, received 13686, lost 0, free buffers 37, min 37, error reg 110000
      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
      Accelerometer detected: yes, status: 00
      I2C bus errors 0, naks 3, other errors 0
      === Filament sensors ===
      Interrupt 4 to 8us, poll 6 to 738us
      Driver 0: pos 208.12, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
      

      Thank you!
      Regards
      Julián.

      T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @juliann
        last edited by

        @juliann please can you post the M122 once the issue occurs. I see driver 2 is one of the Z axis motors so its unlikely to be moving wiring causing the issue but can you check that you can't recreate the issue by moving the wiring around. Also something to check would be to switch the motors in driver 1 and driver 2 at the Duet end, update your config to match, and see if the issue moves with the motor or stays with the driver.

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Unless otherwise noted, all forum content is licensed under CC-BY-SA