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

    Problem with high temperature in the drivers

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    18
    632
    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.
    • Arisoyundefined
      Arisoy
      last edited by Arisoy

      Hello,

      I just finished my 3d printer.

      Everything works fine, i can move all the motors. But when i start a print, this happened :

      2022-01-22_15h10_22.png

      The motors haven't even move when this happened. It's at the really beggining of the print.

      I believe that the problem is in my slicer not in my config.g. Do you think it is possible? Which parametrer should i check?

      Here is my drives conf :

      ;;;;;;;;;; Drives ;;;;;;;;;;
      M569 P0.0 S1 D3                         ; physical drive 0.0
      M569 P0.1 S1 D3                         ; physical drive 0.1
      M569 P0.2 S0 D3                         ; physical drive 0.2
      M569 P0.3 S0 D3                         ; physical drive 0.3
      M569 P0.4 S0 D3                         ; physical drive 0.4
      M569 P20.0 S0 D3                        ; physical drive 20.0 (on toolboard)
      M584 X0.0 Y0.1 Z0.2:0.3:0.4 E20.0.0     ; set drive mapping
      M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation
      
      M92 X80.00 Y80.00 Z800.00               ; set steps per mm
      M906 X1000 Y1000 Z800 I30               ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                 ; Set idle timeout
      
      M566 X400.00 Y400.00 Z6.00 E120.00 P1          ; set maximum instantaneous speed changes (mm/min)
      M203 X10800.00 Y10800.00 Z1000.00 E3600.00     ; set maximum speeds (mm/min)
      M201 X3000.00 Y3000.00 Z100.00 E3600.00        ; set accelerations (mm/s^2)
      

      I'm using Duet 3 mini 5 + with Duet 3 toolboard 1LC.

      dc42undefined 1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @Arisoy
        last edited by

        @arisoy which firmware version are you using? Send M115 or M122 to find out.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        Arisoyundefined 1 Reply Last reply Reply Quote 0
        • Arisoyundefined
          Arisoy @dc42
          last edited by

          @dc42 there is the whole response to these commands:

          M122
          === 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: 0F53H-W396U-D65J0-40KMJ-JD03Z-RY85Y
          Used output buffers: 3 of 40 (11 max)
          === RTOS ===
          Static ram: 102724
          Dynamic ram: 105980 of which 100 recycled
          Never used RAM 34900, free system stack 186 words
          Tasks: NETWORK(ready,15.3%,259) HEAT(delaying,0.0%,348) Move(notifyWait,0.1%,362) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,347) TMC(notifyWait,0.6%,106) MAIN(running,83.1%,426) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0%
          Owned mutexes: WiFi(NETWORK)
          === Platform ===
          Last reset 01:32:38 ago, cause: software
          Last software reset at 2022-01-22 18:00, reason: User, GCodes spinning, available RAM 34900, slot 2
          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 5558984, completed 5558984, timed out 0, errs 0
          Step timer max interval 1328
          MCU temperature: min 33.8, current 34.3, max 34.8
          Supply voltage: min 24.0, current 24.1, max 24.2, 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 1, ifcnt 38, reads 30403, writes 12, timeouts 0, DMA errors 0
          Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 38, reads 30403, writes 12, timeouts 0, DMA errors 0
          Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 38, reads 30403, writes 12, timeouts 0, DMA errors 0
          Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 38, reads 30402, writes 12, timeouts 0, DMA errors 0
          Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 38, reads 30403, writes 12, timeouts 0, DMA errors 0
          Driver 5: position 0, assumed not present
          Driver 6: position 0, assumed not present
          Date/time: 2022-01-22 19:33:12
          Cache data hit count 4294967295
          Slowest loop: 5.79ms; fastest: 0.12ms
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 22.5MBytes/sec
          SD card longest read time 3.5ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, maxWait 0ms, bed compensation in use: mesh, 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 50045, received 66712, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 192, free buffers 17 (min 16), ts 27795/27794/0
          Tx timeouts 0,0,0,0,0,0
          === Network ===
          Slowest loop: 10.40ms; 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:e5:a2
          WiFi Vcc 3.35, reset reason Power up
          WiFi flash size 2097152, free heap 23120
          WiFi IP address 192.168.1.16
          WiFi signal strength -51dBm, mode 802.11n, reconnections 0, sleep mode modem
          Clock register 00002002
          Socket states: 4 0 0 0 0 0 0 0
          
          M115
          FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-06-15 21:46:20
          
          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @Arisoy
            last edited by dc42

            @arisoy thanks. Please can you start a print that causes these errors to be produced. Then when you start getting the error messages:

            1. Carefully touch the stepper driver chips to see if they really are hot.
            2. Run M122 again and post the results here.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            Arisoyundefined 1 Reply Last reply Reply Quote 0
            • Arisoyundefined
              Arisoy @dc42
              last edited by

              @dc42 They are really hot, i cannot leave my finger on it...

              Here is the new M122 :

              M122
              === 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: 0F53H-W396U-D65J0-40KMJ-JD03Z-RY85Y
              Used output buffers: 3 of 40 (26 max)
              === RTOS ===
              Static ram: 102724
              Dynamic ram: 106196 of which 100 recycled
              Never used RAM 34684, free system stack 134 words
              Tasks: NETWORK(ready,15.6%,244) HEAT(delaying,0.0%,348) Move(notifyWait,0.1%,283) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,367) CanClock(delaying,0.0%,338) TMC(notifyWait,0.7%,106) MAIN(running,82.7%,408) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0%
              Owned mutexes: WiFi(NETWORK)
              === Platform ===
              Last reset 01:46:59 ago, cause: software
              Last software reset at 2022-01-22 18:00, reason: User, GCodes spinning, available RAM 34900, slot 2
              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 6419710, completed 6419708, timed out 0, errs 0
              Step timer max interval 1455
              MCU temperature: min 34.3, current 44.9, max 45.1
              Supply voltage: min 23.8, current 24.1, max 24.2, 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 48076, standstill, SG min/max 0/26, read errors 0, write errors 0, ifcnt 43, reads 45295, writes 5, timeouts 0, DMA errors 0
              Driver 1: position 1200, standstill, SG min/max 0/28, read errors 0, write errors 0, ifcnt 43, reads 45295, writes 5, timeouts 0, DMA errors 0
              Driver 2: position -2, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 45, reads 45292, writes 7, timeouts 0, DMA errors 0
              Driver 3: position 0, standstill, SG min/max 0/14, read errors 0, write errors 0, ifcnt 45, reads 45293, writes 7, timeouts 0, DMA errors 0
              Driver 4: position 0, standstill, SG min/max 0/22, read errors 0, write errors 0, ifcnt 45, reads 45293, writes 7, timeouts 0, DMA errors 0
              Driver 5: position 0, assumed not present
              Driver 6: position 0, assumed not present
              Date/time: 2022-01-22 19:47:33
              Cache data hit count 4294967295
              Slowest loop: 138.37ms; fastest: 0.08ms
              === Storage ===
              Free file entries: 10
              SD card 0 detected, interface speed: 22.5MBytes/sec
              SD card longest read time 3.6ms, write time 4.0ms, max retries 0
              === Move ===
              DMs created 83, maxWait 6067306ms, bed compensation in use: mesh, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 2, completed moves 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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
              Heater 0 is on, I-accum = 0.3
              Heater 1 is on, I-accum = 0.0
              === 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 8107, received 10743, lost 0, longest wait 1ms for reply type 4012, peak Tx sync delay 173, free buffers 17 (min 15), ts 4303/4303/0
              Tx timeouts 0,0,0,0,0,0
              === Network ===
              Slowest loop: 200.75ms; fastest: 0.06ms
              Responder states: HTTP(2) 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 1
              WiFi firmware version 1.26
              WiFi MAC address f0:08:d1:02:e5:a2
              WiFi Vcc 3.35, reset reason Power up
              WiFi flash size 2097152, free heap 19968
              WiFi IP address 192.168.1.16
              WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
              Clock register 00002002
              Socket states: 0 4 0 0 0 0 0 0
              
              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @Arisoy
                last edited by dc42

                @arisoy thanks. You've set the current to 1000mA in your M906 command in config.g, so they should not be getting hot. Do they remain cool if you reset the printer, home it and command some manual moves? If so then maybe it is indeed commands generated by the slicer that are causing the drivers to heat up; in which case, please make the GCode file available via Dropbox, Google Drive, or another file sharing site.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                Arisoyundefined 1 Reply Last reply Reply Quote 0
                • Arisoyundefined
                  Arisoy @dc42
                  last edited by Arisoy

                  @dc42 I did some manual move. I did some homing. Everything is alright. No error message and i can "touch" the drivers.

                  The strange thing is that when i load my gcode nothing move but the drivers get hot and the errors appears.

                  Here is the Gcode if you want look at it :
                  FilamentClipV2_0.2mm_PLA_20m.gcode

                  Gixxerfastundefined 1 Reply Last reply Reply Quote 0
                  • Gixxerfastundefined
                    Gixxerfast @Arisoy
                    last edited by

                    @arisoy As a long shot, are you tuning the steppers for stealhchop somewhere in you print start or homing sequence?

                    Do you have something like this somewhere (M17)?

                    ; enables motors and wait for driver tuning
                    M17
                    G4 P200
                    

                    It's a long shot but ... 🙂

                    Voron V2.4 (#1317) with Duet 3 Mini5+ Wifi and 1LC v1.1 Toolboard
                    Voron V0.1 (#637) with Duet 3 Mini 5+ Wifi and 1LC v1.2 Toolboard
                    Ender 3 Pro with BTT SKR-2 + RRF

                    Arisoyundefined 1 Reply Last reply Reply Quote 0
                    • Arisoyundefined
                      Arisoy @Gixxerfast
                      last edited by

                      @gixxerfast

                      @gixxerfast said in Problem with high temperature in the drivers:

                      are you tuning the steppers for stealhchop somewhere in you print start or homing sequence?

                      I don't know... Where can i check this?

                      I check for M17 in my config.g in all homing.g files and in the gcode and i didn't found any. Is there somewhere else i have to check.

                      Gixxerfastundefined 1 Reply Last reply Reply Quote 0
                      • Gixxerfastundefined
                        Gixxerfast @Arisoy
                        last edited by

                        @arisoy Well it was a long shot 🙂

                        When I started with the Duets i "borrowed" a configuration that had that M17 in the middle of the config.g and I didn't understand better so I didn't remove it. I very nearly cooked my motors and drivers. The whole room smelled hot flux.

                        In your slicer, do you have a custom startup sequence there? How does that look?

                        .

                        Voron V2.4 (#1317) with Duet 3 Mini5+ Wifi and 1LC v1.1 Toolboard
                        Voron V0.1 (#637) with Duet 3 Mini 5+ Wifi and 1LC v1.2 Toolboard
                        Ender 3 Pro with BTT SKR-2 + RRF

                        Arisoyundefined 1 Reply Last reply Reply Quote 0
                        • Arisoyundefined
                          Arisoy @Gixxerfast
                          last edited by

                          @gixxerfast I have only one line in my startup sequence and it's this one :

                          START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]
                          

                          I didn't add this line, it was there at the begining.

                          And it gives me an error when i import the gcode but i don't think it's the problem.

                          Arisoyundefined 1 Reply Last reply Reply Quote 0
                          • Arisoyundefined
                            Arisoy @Arisoy
                            last edited by

                            No one can help me? As i said the problem occured when i load and start a gcode.

                            The drives are in error even before they move.

                            While the bed&hotend are warming up the errors start to appear.

                            But when i warm them up in manual or when i move in manuel i have no problem at all.

                            Baenwortundefined dc42undefined 2 Replies Last reply Reply Quote 0
                            • Baenwortundefined
                              Baenwort @Arisoy
                              last edited by

                              This is a new one for me as the earlier steps have hit on all the causes I've seen before. I think we will have to wait for one of the experts like @Phaedrux or someone to give some ideas.

                              1 Reply Last reply Reply Quote 0
                              • markzundefined
                                markz
                                last edited by

                                I took a quick look at your gcode file and it's very hard to believe you have it set correctly for your printer.

                                To begin with, the gcode file reprograms the entire printer dynamics... strangely. This line:

                                M203 X500 Y500 Z10 E60 I0; sets maximum feedrates, mm/min

                                sets the maximum feedrate for Z to 10mm/min which is so slow you probably can't see it move and the others are similarly very slow. I'd recommend you look at your slicer settings and not have it set printer dynamics.

                                Also your slicer is sprinkling this line

                                M204 P4000

                                through the code which I don't understand. It's resetting the print acceleration? Finally, it sets the temperatures I think a little strangely in that it starts heating up the head at the same time as the bed.

                                With all that said - the one time I got "high temperature reported by driver" was when I did a lousy crimp job and one of my motor wires was only sometimes connected.

                                1 Reply Last reply Reply Quote 1
                                • dc42undefined
                                  dc42 administrators @Arisoy
                                  last edited by

                                  @arisoy there is a problem with your GCode file, although I don't know whether it is causing this issue. In this extract:

                                  G10 P0 S205 ; set temperature
                                  ;TYPE:Custom
                                  START_PRINT EXTRUDER_TEMP=205 BED_TEMP=68
                                  G21 ; set units to millimeters
                                  G90 ; use absolute coordinates
                                  M82 ; use absolute distances for extrusion
                                  G92 E0
                                  ; Filament gcode
                                  SET_GCODE_OFFSET Z=0
                                  SET_PRESSURE_ADVANCE ADVANCE=0.05
                                  G10 P0 S205 ; set temperature
                                  M116 ; wait for temperature to be reached
                                  M190 S68 ; set bed temperature and wait for it to be reached
                                  

                                  there are 3 lines that are obviously meant to be comments, but don't have the leading semicolon. They are the lines starting START_PRINT, SET_GCODE and SET_PRESSURE. Perhaps these lines come from the start GCode that you have configured in the slicer; or perhaps they are generated for Prusa printers. So:

                                  1. In Printer Settings/General, change G-code flavor to "RepRapFirmware". I also recommend that you select "Use relative E distance".
                                  2. In Printer Settings/Custom G-code check whether those 3 lines are present, and if so then add a leading semicolon to mark them as comments.
                                  3. Re-slice the file and try printing again.

                                  Duet WiFi hardware designer and firmware engineer
                                  Please do not ask me for Duet support via PM or email, use the forum
                                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                                  Arisoyundefined 1 Reply Last reply Reply Quote 1
                                  • Arisoyundefined
                                    Arisoy @dc42
                                    last edited by

                                    @dc42 Thanks everything works fine now 🙂

                                    dc42undefined 2 Replies Last reply Reply Quote 1
                                    • dc42undefined
                                      dc42 administrators @Arisoy
                                      last edited by

                                      @arisoy thanks for confirming that. I will try running your original file on a Duet 3 Mini to see if I can identify exactly what happened. You are not the first person to report this type of problem, so I want to get to the bottom of it.

                                      Duet WiFi hardware designer and firmware engineer
                                      Please do not ask me for Duet support via PM or email, use the forum
                                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                                      1 Reply Last reply Reply Quote 1
                                      • dc42undefined
                                        dc42 administrators @Arisoy
                                        last edited by

                                        @arisoy I have tested that file under RRF 3.4beta7. If I have the drivers in spreadCycle mode, it works. However, if I have them in stealthChop mode and I start the file without doing the correct stealthChop tuning procedure first, then the drivers provide excessive current to the motors. So I suspect that the issue was caused by lack of stealthChop tuning in the homing files.

                                        Duet WiFi hardware designer and firmware engineer
                                        Please do not ask me for Duet support via PM or email, use the forum
                                        http://www.escher3d.com, https://miscsolutions.wordpress.com

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