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

    Help, extruder don't work anymore.

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    3
    15
    340
    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.
    • Julien30undefined
      Julien30
      last edited by

      I everyone.
      The last week, I was testing my config for my printer and all works fine but today when I come to try and check it one more time before install every cards and motors in the printer, my extruders does not move a inch when I command them from the panel due or DWC.

      So I was thinking that my motor extruders are just dead and I have switch it with new one who's working perfectly.
      But that was apparently not the problem because It don't work when I connect it to the Mainboard.

      Then I have change the pin driver in the config and It don't change a thing. The extruder don't flinch or make some noise. Just nothing but a really long silence after the commands sended.

      My extruder is now on the "Driver 4" pin of the Mainboard 6HC.
      The 4 wire (Red Blue Green Black) are pinned properly like the Wiring Diagram of Duet 3 Mainboard 6HC. I have test with one multimeter the wire to see which go with other.

      Extruder info:
      FL42STH33-1334A
      1.8°
      1.33A

      And here is my config.g :


      w; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Dec 16 2022 13:46:14 GMT+0100 (heure normale d’Europe centrale)

      ; General preferences
      M575 P1 S1 B57600 ; enable support for PanelDue
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Titan FDM" ; set printer name
      M669 K0 ; select Cartesian mode

      ; Wait a moment for the CAN expansion boards to start
      G4 S2

      ; Network
      M552 P192.168.1.91 S1 ; enable network and acquire dynamic address via DHCP
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P40.0 S1 R1 T5:5:10:10 ; physical drive 40.0 goes forwards
      M569 P41.0 S1 R1 T5:5:10:10 ; physical drive 41.0 goes forwards
      M569 P42.0 S1 R1 T5:5:10:10 ; physical drive 42.0 goes forwards
      M569 P0.4 S1 ; physical drive 0.4 goes forwards
      M569 P0.5 S1 ; physical drive 0.5 goes forwards
      M569.7 P42.0 C"out1" ; driver 0 on board 42 uses port out 1 on board 42 to control the brake
      M584 X40.0 Y41.0 Z42.0 E0.4:0.5 ; set drive mapping
      M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
      M92 X100.00 Y100.00 Z100.00 E110.00:110.00 ; set steps per mm
      M566 X900.00 Y900.00 Z900.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X6000.00 Y6000.00 Z6000.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z500.00 E250.00:250.00 ; set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E1300:1300 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X406 Y355 Z406 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"io4.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin 40.io1.in
      M574 Y1 S1 P"io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin 41.io1.in
      M574 Z1 S1 P"io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin 42.io1.in

      ; Z-Probe
      M950 S0 C"io4.out" ; create servo pin 0 for BLTouch
      M558 P9 C"io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
      G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
      M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters
      M557 X15:215 Y15:195 S20 ; define mesh grid

      ; Heaters
      M308 S2 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin temp0
      M950 H2 C"out1" T0 ; create nozzle heater output on out1 and map it to sensor 0
      M307 H2 B0 S0.2 ; disable bang-bang mode for heater and set PWM limit
      M143 H2 S300 ; set temperature limit for heater 0 to 300C
      M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
      M950 H1 C"out2" T1 ; create nozzle heater output on out2 and map it to sensor 1
      M307 H1 B0 S0.2 ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S300 ; set temperature limit for heater 1 to 300C
      M308 S0 P"temp2" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp2
      M950 H0 C"out4" T2 ; create chamber heater output on out4 and map it to sensor 2
      M307 H0 B0 S0.2 ; disable bang-bang mode for the chamber heater and set PWM limit
      M140 H0 ; map bed to heater 0
      M143 H0 S200 ; set temperature limit for heater 0 to 200C
      M308 S0 P"temp2" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin temp2
      M950 H3 C"out3" T2 ; create chamber heater output on out3 and map it to sensor 2
      M307 H3 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit
      M141 H3 ; map chamber to heater 3
      M143 H3 S100 ; set temperature limit for heater 3 to 100C

      ; Fans
      M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency
      M106 P0 S0 H T45 ; set fan 0 value. Thermostatic control is turned on
      M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
      M106 P1 S1 H1:2:2 T45 ; set fan 1 value. Thermostatic control is turned on
      M950 F2 C"out6" Q500 ; create fan 2 on pin out6 and set its frequency
      M106 P2 S1 H0:1 T45 ; set fan 2 value. Thermostatic control is turned on

      ; Tools
      M563 P5 S"Extrudeur supports" D0.5 H2 F0 ; define tool 0
      G10 P5 X0 Y0 Z0 ; set tool 5 axis offsets
      G10 P5 R0 S0 ; set initial tool 5 active and standby temperatures to 0C
      M563 P4 S"Extrudeur fil" D0.4 H1 F1 ; define tool 1
      G10 P4 X0 Y0 Z0 ; set tool 4 axis offsets
      G10 P4 R0 S0 ; set initial tool 4 active and standby temperatures to 0C

      ; Custom settings are not defined

      ; Miscellaneous
      M501 ; load saved parameters from non-volatile memory
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
      T4 ; select Extrudeur fil tool


      Can you help me to solve this issue?
      Thanks you.

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

        @Julien30 what firmware are you running?

        @Julien30 said in Help, extruder don't work anymore.:

        M563 P4 S"Extrudeur fil" D0.4 H1 F1 ; define tool 1

        this is incorrect. the D number should be D0

        @Julien30 said in Help, extruder don't work anymore.:

        M563 P5 S"Extrudeur supports" D0.5 H2 F0 ; define tool 0

        This is also incorrect and the D number should be D1

        Both of the above go from the extruder mapping not from the driver number

        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

        Julien30undefined 2 Replies Last reply Reply Quote 0
        • Julien30undefined
          Julien30 @jay_s_uk
          last edited by

          Hi @jay_s_uk
          Ok, I was thinking that the D parameter is the related to the driver pin of the card.
          So I change it to make it look that:

          ; Tools
          M563 P5 S"Extrudeur supports" D0 H2 F0 ; define tool 0
          G10 P5 X0 Y0 Z0 ; set tool 5 axis offsets
          G10 P5 R0 S0 ; set initial tool 5 active and standby temperatures to 0C
          M563 P4 S"Extrudeur fil" D1 H1 F1 ; define tool 1
          G10 P4 X0 Y0 Z0 ; set tool 4 axis offsets
          G10 P4 R0 S0 ; set initial tool 4 active and standby temperatures to 0C

          But does my pin correspond to the Driver 4 and 5 of the Maindboard 6HC or it have change?
          Can you remember how to check the firmware version?

          deckingmanundefined 1 Reply Last reply Reply Quote 0
          • deckingmanundefined
            deckingman @Julien30
            last edited by deckingman

            @Julien30 Extruder drives are assigned numbers in the order that you define them in M584. So as you have M584 X40.0 Y41.0 Z42.0 E0.4:0.5, then extruder 0 (D0) will be the one connected to drive 4 on the main board and extruder 1 (D1) will be the one connected to drive 5 on the main board. When testing, don't forget to send M302 P1 to allow cold extrudes.

            Ian
            https://somei3deas.wordpress.com/
            https://www.youtube.com/@deckingman

            Julien30undefined 1 Reply Last reply Reply Quote 0
            • Julien30undefined
              Julien30 @deckingman
              last edited by

              Hi @deckingman
              Ok I was not thinking it work like that. Thank you.
              For the M302 P1 I always use it when I want to make some test but for that I have done a macro to send it and allow cold extrusion.

              1 Reply Last reply Reply Quote 0
              • Julien30undefined
                Julien30 @jay_s_uk
                last edited by

                @jay_s_uk said in Help, extruder don't work anymore.:

                @Julien30 what firmware are you running?

                I have just seen that the firmware version is in the configuration general of DWC so here it is.
                The firmware version is :

                3.5beta2 (2023-02-08)

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

                  @Julien30 theres a bug in beta 3.5b2 where cold extrusion doesn't work. upgrade to 3.5b3

                  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

                  Julien30undefined 1 Reply Last reply Reply Quote 0
                  • Julien30undefined
                    Julien30 @jay_s_uk
                    last edited by

                    @jay_s_uk @deckingman

                    Thank you so much,
                    I change the Firmware for the 3.5 beta 3 as @jay_s_uk said and I've made the modif as @deckingman said.
                    Now it's work perfectly.

                    Thank you.👍

                    1 Reply Last reply Reply Quote 1
                    • Julien30undefined
                      Julien30
                      last edited by

                      @jay_s_uk
                      Well maybe a little to fast.
                      After I have done the modifs I only try to move the extruders and It work well.
                      But now the 3 motors for XYZ axis who are pinned command to 3 cards EXP1XD don't want to move.
                      They worked when the Firmware was 3.5 beta 2 (2023-02-08). Do you think this issue come from the firmware?
                      Because if it's the case I switch to 3.5 beta 2 and don't allow cold extrusion. I prefer make the heater go to high temperature for extrude than the XYZ can't move...

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

                        @Julien30 i don't think so. i'm running 3.5b3 on one of my machines with success. did you update the firmware on the expansion boards as well?
                        are you homing them before trying to move them?

                        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

                        Julien30undefined 1 Reply Last reply Reply Quote 0
                        • Julien30undefined
                          Julien30 @jay_s_uk
                          last edited by

                          @jay_s_uk
                          Yes I homing them before.
                          Can you remember me the way to update the firmware on the expansion boards please.
                          Because I've downloaded the firmware in the SD card of the MainBoard and equally charge files from DWC.
                          All the time the 3 EXP boards are connected together and to the Mainboard with alim ON.

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

                            @Julien30 just upload the expansion board firmware for 3.5b3 https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.0-beta.3/Duet3Firmware_EXP1XD.bin

                            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

                            Julien30undefined 1 Reply Last reply Reply Quote 0
                            • Julien30undefined
                              Julien30 @jay_s_uk
                              last edited by

                              @jay_s_uk
                              Yes It is the file that I downloaded and upload on the SD card in plug it in my computer. Then reinstall the SD card in the Mainboard and afterall upload by DWC the file with th charge files button

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

                                @Julien30 why unplug the SD card? you can do all updates through DWC. That way it'll then prompt all the appropriate boards to update.
                                Either reupload that file or send M997 B40 and so on for each board

                                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

                                Julien30undefined 1 Reply Last reply Reply Quote 0
                                • Julien30undefined
                                  Julien30 @jay_s_uk
                                  last edited by

                                  @jay_s_uk
                                  Oh right, It's more easier.
                                  I've done what you suggest and it work perfectly.
                                  Thank you very much 👍

                                  1 Reply Last reply Reply Quote 1
                                  • dc42undefined dc42 marked this topic as a question
                                  • dc42undefined dc42 has marked this topic as solved
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA