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

    Issue with tool definition/motor not responding

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    3
    8
    322
    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.
    • CSLTMundefined
      CSLTM
      last edited by

      Hi,

      I've got an issue with a toolboard/config wherein I believe I've defined the tool correctly and the drivers for said tool but the motor doesn't respond.

      Here is where the drivers are bound to the extruders.

      ; Drives
      M569 P0.0 S0                                       ;  X
      M569 P0.1 S0                                       ;  Y
      M569 P0.2 S1                                       ;  Z1
      M569 P0.3 S1                                       ;  Z2
      M569 P0.4 S1                                       ;  Z3
      M569 P0.5 S1                                       ;  Z4
      M569 P1.0 S1					   				   ;  C
      M569 P20.0 S0 									   ;  E0
      M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 C1.0               ; set drive mapping for motion system
      M584 E20.0 							               ; set drive mapping for tools
      M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
      M350 C8 I0				 	                       ; configure microstepping with no interpolation
      M92 X80.00 Y80.00 Z817 C100 E409                 ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 C2 E120.00                ; set maximum instantaneous speed changes (mm/min)
      M203 X36000.00 Y36000.00 Z400 C5000 E1200.00            ; set maximum speeds (mm/min)
      M201 X1000.00 Y1000.00 Z20.00 C400 E250.00                ; set accelerations (mm/s^2)
      M906 X2000 Y2000 Z2000 C400 E800 I30                    ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                            ; Set idle timeout
      
      

      And here is where the tool is defined.

      M563 P0 S"Tool 0" D0 H1 F1                                  ; define tool 0
      G10 L2 P1 X23 Y67 Z15.5                                    ; set tool 0 axis offsets
      G10 L2 P1 R0 S0                                       		   ; set initial tool 0 active and standby temperatures to 0C
      

      I can't figure out for the life of me why this isn't working!

      Any help appreciated!

      Cheers,

      Tom

      SIamundefined 1 Reply Last reply Reply Quote 0
      • SIamundefined
        SIam @CSLTM
        last edited by SIam

        @csltm you have to select the tool

        T0
        

        in your config.g or in your start gcode in the slicer

        Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
        Duet WiFi 1.02 or later + DueX5
        RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
        Duet WiFi Server: 1.26
        Duet Web Control 3.4.0beta4 (2021-09-27)

        CSLTMundefined 1 Reply Last reply Reply Quote 0
        • CSLTMundefined
          CSLTM @SIam
          last edited by

          @siam Thanks for the quick reply.

          The machine when it starts up doesn't have a tool on it so would it be worth adding T0 to the TPRE0.g?

          What would I add to the TFREE0.g to de-select the tool?

          Thanks!

          SIamundefined 1 Reply Last reply Reply Quote 0
          • SIamundefined
            SIam @CSLTM
            last edited by

            @csltm as far as i know is the tpre0.g for change tool script
            if you only have one tool is enough when you put t0 at the end of the config.g file

            Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
            Duet WiFi 1.02 or later + DueX5
            RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
            Duet WiFi Server: 1.26
            Duet Web Control 3.4.0beta4 (2021-09-27)

            CSLTMundefined 1 Reply Last reply Reply Quote 0
            • CSLTMundefined
              CSLTM @SIam
              last edited by

              @siam I should have mentioned I'm using the E3D toolchanger.

              The TPRE0 script correctly picks up the tool, allows me to heat up the hotend and use the fans but the motor won't spin.

              I tried adding T0 to the TPRE0.g script but it sent it into a loop of picking the tool up and putting it down again.

              Even with the tool hooked up and the heater on, the motor doesn't spin or twitch or engage.

              SIamundefined 1 Reply Last reply Reply Quote 0
              • SIamundefined
                SIam @CSLTM
                last edited by

                @csltm
                Ok with a tool changer i'm out but
                i think your mistake is here P20.0 ?

                M569 P20.0 S0 									   ;  E0
                

                and here you map P0 to the to tool 0

                M563 P0 S"Tool 0" D0 H1 F1                                  ; define tool 0
                

                Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
                Duet WiFi 1.02 or later + DueX5
                RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
                Duet WiFi Server: 1.26
                Duet Web Control 3.4.0beta4 (2021-09-27)

                CSLTMundefined 1 Reply Last reply Reply Quote 0
                • CSLTMundefined
                  CSLTM @SIam
                  last edited by

                  @siam P20 directs the firmware to the Toolboard as it is numbered 20.
                  Will have a play with the M563 command.

                  Thanks for your help anyway 🙂

                  1 Reply Last reply Reply Quote 0
                  • o_lampeundefined
                    o_lampe
                    last edited by

                    Hi @CSLTM
                    I fell in the same trap lately > M584 should come very early in config.g
                    I'd put it before M669 to be sure.
                    The configuration tool will be adapted soon.

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