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

    Printer locked up

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    9
    389
    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.
    • tomasroundefined
      tomasro
      last edited by

      Printer was working just fine, and then while running g32, xy drivers started skipping and running backward. I emergency stopped the printer and now I can't home, and the console is reporting "Warning: high temperature reported by driver(s) 1 2".

      M308 s2
      "Sensor 2 (DRIVERS) type Stepper driver temperature warnings, reading 0.0, last error: success".

      m308 s3
      "Sensor 3 (MCU) type Microcontroller embedded temperature sensor, reading 22.7, last error: success".

      Endstops for X&Y drivers reporter homed, but the printhead is in the middle of the printer.

      Machine spec:
      CoreXY
      Duetwifi v1.01 & duex5 v0.10
      Quad Z motors

      ; Configuration file for Duet WiFi (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.4 on Fri Oct 22 2021 23:28:40 GMT-0700 (Pacific Daylight Time)
      
      ; General preferences
      G90                                                    ; send absolute coordinates...
      M83                                                    ; ...but relative extruder moves
      M550 P"R2D Cube"                                       ; set printer name
      M669 K1                                                ; select CoreXY mode
      
      M912 P0 S-8.2					;calibrate MCU temperature
      
      ; Network
      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 backwards
      M569 P1 S0                                             ; physical drive 1 goes backwards
      M569 P3 S1                                             ; physical drive 3 goes forwards
      M569 P5 S0
      M569 P6 S0
      M569 P7 S0
      M569 P8 S0
      M584 X0 Y1 Z5:6:7:8 E3                                       ; set drive mapping
      M671 X-40:515:-40:515 Y37:37:430:430 S5 ; leadscrews at left front, right front, left rear, right rear
      M350 X16 Y16 Z16 E16 I1                                ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z808.00 E402.00                      ; set steps per mm
      M566 X900.00 Y900.00 Z100.00 E120.00                    ; set maximum instantaneous speed changes (mm/min)
      M203 X12000.00 Y12000.00 Z6000 E1200.00                ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z250 E250.00                    ; set accelerations (mm/s^2)
      M906 X900 Y900 Z800 E800 I1                            ; set motor currents (mA) and motor idle factor in per cent
      M84 S10                                                ; Set idle timeout
      
      ; Axis Limits
      M208 X0:455 Y0:405 Z0:420
      
      ; Endstops
      M591 P2 C"!duex.e2stop" S1   D0 			       ; filament monitor connected to E0 endstop
      M574 X1 S1 P"!duex.e3stop"                                   ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !xstop
      M574 Y1 S1 P"!duex.e4stop"                                   ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin !ystop
      M574 Z1 S2                                             ; configure Z-probe endstop for low end on Z
      
      ; Z-Probe
      M950 S0 C"duex.pwm1"                                  ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H10 F600 T10000                   ; set Z probe type to bltouch and the dive height + speeds
      G31 P500 X35 Y35 Z1.7                                   ; set Z probe trigger value, offset and trigger height
      M557 X72:490 Y35:440 S100                              ; define mesh grid
      
      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B3950         ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0                                  ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 B0 R0.221 C451.3 D2.62 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
      M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1                                   ; create nozzle heater output on e0heat and map it to sensor 1
      ;M307 H1 B0 S1.00                                       ; disable bang-bang mode for heater  and set PWM limit
      M307 H1 B0 R2.107 C262.7:238.2 D6.31 S1.00 V24.6
      M143 H1 S280                                           ; set temperature limit for heater 1 to 280C
      
      ; Fans
      M950 F0 C"fan0" Q500                                   ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1                                         ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500                                   ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1.0 H1 T45                                     ; set fan 1 value. 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
      
      ;Temp Sensor trigger
      M308 S2 Y"drivers" A"DRIVERS"  ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
      M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as on-chip MCU temperature sensor
      M950 F2 C"fan2" Q100 ; create fan 2 on pin fan2 and set its frequency                        
      ;M106 P2 H2:3 L0.15 X1 B0.3 T30:70 ; set fan 2 value
      M106 P2 H2:3 S1 T20
      ; Custom settings are not defined
      
      

      Any help would be appreciated. Thanks!

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @tomasro
        last edited by

        @tomasro sounds like you need to check your wiring on whatever is connected to drivers 1 and 2 (usually Y and Z)

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        tomasroundefined 1 Reply Last reply Reply Quote 0
        • tomasroundefined
          tomasro @jay_s_uk
          last edited by

          @jay_s_uk Driver 2 is completely empty. I've got 4 z motors on drivers 5, 6, 7 and 8 on the duex board

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @tomasro
            last edited by

            @tomasro that doesn't sound good then. When and where did you buy your duet?

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            tomasroundefined 1 Reply Last reply Reply Quote 0
            • tomasroundefined
              tomasro @jay_s_uk
              last edited by

              @jay_s_uk Filastruder. I've had it for a couple years now. It's never had this problem until I added the Duex5 board and redid the wiring. I've got active cooling on the back of the boards. Would heatsinks on the back or front help?

              tomasroundefined 1 Reply Last reply Reply Quote 0
              • tomasroundefined
                tomasro @tomasro
                last edited by

                @tomasro I turned the machine off overnight and now the driver are working, but they still don't return a temperature from the sensor.

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @tomasro
                  last edited by

                  @tomasro drivers only report 0, 100 and 130 degrees

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  tomasroundefined 1 Reply Last reply Reply Quote 0
                  • tomasroundefined
                    tomasro @jay_s_uk
                    last edited by

                    @jay_s_uk So why would it report drivers over temp when it shows 0?

                    Phaedruxundefined 1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator @tomasro
                      last edited by

                      @tomasro said in Printer locked up:

                      @jay_s_uk So why would it report drivers over temp when it shows 0?

                      possibly because by the time you sent the command to check they had cooled below the warning temp.

                      Z-Bot CoreXY Build | Thingiverse Profile

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