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

    Extruder E1 not working

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    28
    737
    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.
    • jackd2282undefined
      jackd2282 @chrishamm
      last edited by

      @chrishamm said in Extruder E1 not working:

      M98 P"config.g"

      I tried M563 P0 D0 H1 F0 and M563 P0 D0 H1 F1 because both were mentioned and while the tool interface now stays on both for the hot end and M98 P"config.g" showsM98 P"config.g"
      HTTP is enabled on port 80
      FTP is disabled
      TELNET is disabled
      when I heat up the hotend to 195c to get both extrusion and retraction buttons to become available i get Warning: motor phase A may be disconnected reported by driver(s) 4
      Warning: motor phase B may be disconnected reported by driver(s) 4 with multiple
      with multiple stepper motors

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

        Can you send M122 and provide the results?

        How did you "burn" driver 3?

        Can you provide some photos of the board? Especially close ups of the drivers?

        Z-Bot CoreXY Build | Thingiverse Profile

        jackd2282undefined 1 Reply Last reply Reply Quote 0
        • jackd2282undefined
          jackd2282 @Phaedrux
          last edited by

          @phaedruxM122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
          Board ID: 08DLM-996RU-N85S4-7JKD2-3SN6K-1U97R
          Used output buffers: 3 of 24 (23 max)
          === RTOS ===
          Static ram: 23876
          Dynamic ram: 75020 of which 24 recycled
          Never used RAM 15496, free system stack 184 words
          Tasks: NETWORK(ready,6.0%,246) HEAT(delaying,0.0%,314) Move(notifyWait,0.1%,364) MAIN(running,93.9%,441) IDLE(ready,0.0%,29), total 100.0%
          Owned mutexes: WiFi(NETWORK)
          === Platform ===
          Last reset 00:01:42 ago, cause: software
          Last software reset at 2021-08-03 14:09, reason: User, GCodes spinning, available RAM 15496, slot 2
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Step timer max interval 0
          MCU temperature: min 23.4, current 24.5, max 24.8
          Supply voltage: min 27.1, current 27.3, max 27.4, 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 not available
          Driver 1: position 0, standstill, SG min/max not available
          Driver 2: position 0, standstill, SG min/max not available
          Driver 3: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
          Driver 4: position 0, standstill, SG min/max not available
          Driver 5: position 0
          Driver 6: position 0
          Driver 7: position 0
          Driver 8: position 0
          Driver 9: position 0
          Driver 10: position 0
          Driver 11: position 0
          Date/time: 2021-08-03 14:10:58
          Cache data hit count 4294967295
          Slowest loop: 7.65ms; fastest: 0.17ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest read time 2.0ms, 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 -1 -1, chamberHeaters = -1 -1 -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
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 202.62ms; fastest: 0.08ms
          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 1
            WiFi firmware version 1.26
            WiFi MAC address 8c:aa:b5:c2:16:2b
            WiFi Vcc 3.38, reset reason Turned on by main processor
            WiFi flash size 4194304, free heap 26952
            WiFi IP address 192.168.1.140
            WiFi signal strength -71dBm, mode 802.11n, reconnections 0, sleep mode modem
            Clock register 00002002
            Socket states: 0 0 0 0 0 0 0 0
          jackd2282undefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
          • jackd2282undefined
            jackd2282 @jackd2282
            last edited by

            @jackd2282 I hooked up my new bondtech ddx and my guess is that the motor was wired wrong cause it got hot then the driver burned

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

              @jackd2282 said in Extruder E1 not working:

              Driver 3: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available

              Driver 3 is definitely damaged.

              @jackd2282 said in Extruder E1 not working:

              Warning: motor phase A may be disconnected reported by driver(s) 4
              Warning: motor phase B may be disconnected reported by driver(s) 4 with multiple
              with multiple stepper motors

              And it sounds like you still have the motor wired incorrectly.

              Carefully identify the motors phase pairs first before wiring them up again.

              https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

              Z-Bot CoreXY Build | Thingiverse Profile

              jackd2282undefined 1 Reply Last reply Reply Quote 0
              • jackd2282undefined
                jackd2282 @Phaedrux
                last edited by

                @phaedrux I made sure the phases are right and tried all 4 combinations on the motor. No luck. Maybe E1 is also damaged?

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

                  Possibly, or the damage to driver 3 is also preventing driver 4 from working.

                  @phaedrux said in Extruder E1 not working:

                  Can you provide some photos of the board? Especially close ups of the drivers?

                  Do you notice any damage or pock marks?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  jackd2282undefined 1 Reply Last reply Reply Quote 0
                  • jackd2282undefined
                    jackd2282 @Phaedrux
                    last edited by

                    @phaedrux it was physically burned and not dremeled out

                    jackd2282undefined 1 Reply Last reply Reply Quote 0
                    • jackd2282undefined
                      jackd2282 @jackd2282
                      last edited by

                      @jackd2282 I don’t know why driver 4 would be affected though. It wasn’t even hooked up when this happened but back to my question on the expansion boards, would that bypass this problem?

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

                        Well yes, if you added an expansion board like a Duex or external driver expansion board you could use the drivers on that as replacements. Just map the extruders to the new drivers with M584.

                        @jackd2282 said in Extruder E1 not working:

                        I don’t know why driver 4 would be affected though

                        I'm not sure, but I think if the damage was bad enough it may have damaged the SPI bus which could cut communication to further drivers down the line.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        jackd2282undefined 1 Reply Last reply Reply Quote 0
                        • jackd2282undefined
                          jackd2282 @Phaedrux
                          last edited by

                          @phaedrux that would make sense why my xyz still work

                          jackd2282undefined Phaedruxundefined 3 Replies Last reply Reply Quote 0
                          • jackd2282undefined
                            jackd2282 @jackd2282
                            last edited by

                            @jackd2282 ordered the expansion board so will see when it comes in

                            1 Reply Last reply Reply Quote 0
                            • jackd2282undefined
                              jackd2282 @jackd2282
                              last edited by

                              @jackd2282 ok so I am thinking that the expansion board may not work. It’s not here yet but I was taking for granted that my other drivers worked because they did before all this. But that’s not the case. None of them do. Same problem phase a and b. I tried just the z and modified the config.g to only include that drive and nothing. My board may be shot and that sucks cause I just bought that expansion board with next day shipping for nothing. None of them get warm. No errors unless I try to move a motor. I tried resetting the firmware on the board and card to just start over but no luck.

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

                                @jackd2282 said in Extruder E1 not working:

                                @phaedrux that would make sense why my xyz still work

                                Did they work before but not anymore?

                                Z-Bot CoreXY Build | Thingiverse Profile

                                jackd2282undefined 1 Reply Last reply Reply Quote 0
                                • jackd2282undefined
                                  jackd2282 @Phaedrux
                                  last edited by

                                  @phaedrux they worked before the extruder problem but I was so focused on that that I didn’t even try them.

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