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

    Help with new setup please

    Scheduled Pinned Locked Moved Solved
    General Discussion
    4
    19
    508
    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.
    • fcwiltundefined
      fcwilt @troydeming
      last edited by

      @troydeming said in Help with new setup please:

      @troydeming

      So when I try to home x using g29 x or hitting the home button or the home all button the x will move in the correct direction but stops after about 10 mm.

      You don't use G29 to home, you use G28.

      Please post your homing files AND be sure and use the </> tag to paste them right into your post so we can all see them without having to download files.

      Frederick

      Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

      troydemingundefined 1 Reply Last reply Reply Quote 0
      • troydemingundefined
        troydeming @fcwilt
        last edited by droftarts

        @fcwilt
        I meant to say g28 dont know why I said g29.

        Here are the files

        ; homex.g
        ; called to home the X axis
        ;
        ; generated by RepRapFirmware Configuration Tool v3.5.10 on Wed Jan 29 2025 19:21:26 GMT-0500 (Eastern Standard Time)
        
        ; increase Z
        G91 ; relative positioning
        G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
        G90 ; absolute positioning
        
        ; home X
        G91 ; relative positioning
        var maxTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
        G1 H1 X-300 F1800 ; coarse home in the -X direction
        G1 X5 F6000 ; move back 5mm
        G1 H1 X-300 F300 ; fine home in the -X direction
        G90 ; absolute positioning
        
        ; decrease Z again
        G91 ; relative positioning
        G1 H2 Z-5 F6000 ; move Z relative to current position
        G90 ; absolute positioning
        
        ; homey.g
        ; called to home the Y axis
        ;
        ; generated by RepRapFirmware Configuration Tool v3.5.10 on Wed Jan 29 2025 19:21:26 GMT-0500 (Eastern Standard Time)
        
        ; increase Z
        G91 ; relative positioning
        G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
        G90 ; absolute positioning
        
        ; home Y
        G91 ; relative positioning
        var maxTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
        G1 H1 Y-300 F1800 ; coarse home in the -Y direction
        G1 Y5 F6000 ; move back 5mm
        G1 H1 Y-300 F300 ; fine home in the -Y direction
        G90 ; absolute positioning
        
        ; decrease Z again
        G91 ; relative positioning
        G1 H2 Z-5 F6000 ; move Z relative to current position
        G90 ; absolute positioning
        
        ; homez.g
        ; called to home the Z axis
        ;
        ; generated by RepRapFirmware Configuration Tool v3.5.10 on Wed Jan 29 2025 19:21:26 GMT-0500 (Eastern Standard Time)
        
        ; increase Z
        G91 ; relative positioning
        G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
        G90 ; absolute positioning
        
        ; home Z
        var xCenter = move.compensation.probeGrid.mins[0] + (move.compensation.probeGrid.maxs[0] - move.compensation.probeGrid.mins[0]) / 2 - sensors.probes[0].offsets[0]
        var yCenter = move.compensation.probeGrid.mins[1] + (move.compensation.probeGrid.maxs[1] - move.compensation.probeGrid.mins[1]) / 2 - sensors.probes[0].offsets[1]
        G1 X150 Y150 F6000 ; go to bed centre
        G30 ; probe the bed
        
        troydemingundefined fcwiltundefined 2 Replies Last reply Reply Quote 0
        • troydemingundefined
          troydeming @troydeming
          last edited by

          @troydeming
          I just saw the following error on startup.

          Error in start-up file macro line 58: Pin name needed for switch-type endstop on Z axis

          droftartsundefined 1 Reply Last reply Reply Quote 0
          • droftartsundefined
            droftarts administrators @troydeming
            last edited by

            @troydeming said in Help with new setup please:

            Error in start-up file macro line 58: Pin name needed for switch-type endstop on Z axis

            That's due to this line:

            M574 Z1 S2 ; configure Z axis endstop
            

            Though I think you may have changed this from S2 to S1? Either way, it's not needed if you use the probe for homing the Z axis with G30, so delete the line, or comment out the line with ; at the beginning.

            Are you still having problems with the X and Y axis homing? Maybe repost your config.g if you have made changes to it.

            Ian

            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

            troydemingundefined 1 Reply Last reply Reply Quote 0
            • fcwiltundefined
              fcwilt @troydeming
              last edited by

              @troydeming

              I see you compute various values, example var.maxTravel, and then don't use them.

              Did you at one time use them?

              Now this is just me, my two cents, feel free to ignore because you don't talk to crazy folks - On all of my printers I install a Z end-stop sensor for homing Z, which means I don't have to home X and Y first, which must be done so the Z probe can be used for homing Z. Being able to home Z first also means, when homing X and Y, I don't need to jog Z out of the way with those G1 H2 moves, which under certain circumstances can drive Z against end of the axis, which makes unpleasant noises, which upset my dogs.

              🤣

              Frederick

              Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

              1 Reply Last reply Reply Quote 0
              • troydemingundefined
                troydeming @droftarts
                last edited by

                @droftarts Thank You for your help. The error stopped but I am still having the same issue with homing. Here is the current config.g
                ;; Configuration file for RepRapFirmware on Duet 2 WiFi
                ; executed by the firmware on start-up
                ;
                ; generated by RepRapFirmware Configuration Tool v3.5.10 on Wed Jan 29 2025 19:21:22 GMT-0500 (Eastern Standard Time)

                ; General
                G90 ; absolute coordinates
                M83 ; relative extruder moves
                M550 P"Alumiman FT5 v3.5" ; set hostname

                ; Accessories
                M575 P1 S0 B57600 ; configure PanelDue support

                ; Network
                M552 S1 ; configure WiFi adapter
                M586 P0 S1 ; configure HTTP

                ; Smart Drivers
                M569 P0 S1 D2 ; driver 0 goes Forwards(X axis)(s0- back s1-fwd)
                M569 P1 S1 D2 ; driver 1 goes Forwards (Y axis)
                M569 P2 S0 D2 ; driver 2 goes Backwards (Z axis)
                M569 P3 S0 D2 ; driver 3 goes Backwards (extruder 0)

                ; Motor Idle Current Reduction
                M906 I30 ; set motor current idle factor
                M84 S30 ; set motor current idle timeout

                ; Axes
                M584 X2 Y1 Z0 ; set axis mapping
                M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
                M906 X800 Y800 Z800 ; set axis driver currents
                M92 X160 Y160 Z800 ; configure steps per mm
                M208 X-5:300 Y0:300 Z0:400 ; set minimum and maximum axis limits
                M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
                M203 X6000 Y6000 Z180 ; set maximum speeds (mm/min)
                M201 X500 Y500 Z250 ; set accelerations (mm/s^2)

                ; Extruders
                M584 E3 ; set extruder mapping
                M350 E16 I1 ; configure microstepping with interpolation
                M906 E800 ; set extruder driver currents
                M92 E420 ; configure steps per mm
                M566 E120 ; set maximum instantaneous speed changes (mm/min)
                M203 E3600 ; set maximum speeds (mm/min)
                M201 E250 ; set accelerations (mm/s^2)

                ; Kinematics
                M669 K0 ; configure Cartesian kinematics

                ; Probes
                M558 P9 C"^zprobe.in" H5 F120 T6000 ; configure BLTouch probe via slot #0
                G31 P500 X5 Y15 Z0.7 ; set Z probe trigger value, offset and trigger height
                M950 S0 C"exp.heater3" ; create servo #0 for BLtouch

                ; Endstops
                M574 X1 P"!xstop" S1 ; configure X axis endstop
                M574 Y1 P"!ystop" S1 ; configure Y axis endstop
                ;M574 Z1 S1 ; configure Z axis endstop

                ; Mesh Bed Compensation
                M557 X25:275 Y25:275 S40:40 ; define grid for mesh bed compensation

                ; Sensors
                M308 S0 P"bedtemp" Y"thermistor" A"Heated Bed" T100000 B4725 C7.06e-8 ; configure sensor #0
                M308 S1 P"e0temp" Y"thermistor" A"Nozzle" T100000 B4725 C7.06e-8 ; configure sensor #1

                ; Heaters
                M950 H0 C"bedheat" T0 ; create heater #0
                M143 H0 P0 T0 C0 S140 A0 ; configure heater monitor #0 for heater #0
                M307 H0 R2.43 D5.5 E1.35 K0.56 B1 ; configure model of heater #0
                M950 H1 C"e0heat" T1 ; create heater #1
                M143 H1 P0 T1 C0 S350 A0 ; configure heater monitor #0 for heater #1
                M307 H1 R2.43 D5.5 E1.35 K0.56 B0 ; configure model of heater #1

                ; Heated beds
                M140 P0 H0 ; configure heated bed #0

                ; Fans
                M950 F0 C"fan0" ; create fan #0
                M106 P0 S0 L0 X1 B0.1 ; configure fan #0
                M950 F1 C"fan2" ; create fan #1
                M106 P1 S0 B0.1 H1 T45 ; configure fan #1

                ; Tools
                M563 P0 D0 H1 F0 ; create tool #0
                M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C
                ;

                fcwiltundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @troydeming
                  last edited by

                  @troydeming

                  Just to be sure we are all on the same page, what is the issue you are having with homing?

                  Frederick

                  Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                  troydemingundefined 1 Reply Last reply Reply Quote 0
                  • troydemingundefined
                    troydeming @fcwilt
                    last edited by

                    @fcwilt
                    when I home x the carriage only moves 10-20 cm then it stops and the bed then rises 20 cm

                    fcwiltundefined 1 Reply Last reply Reply Quote 0
                    • fcwiltundefined
                      fcwilt @troydeming
                      last edited by

                      @troydeming said in Help with new setup please:

                      @fcwilt
                      when I home x the carriage only moves 10-20 cm then it stops and the bed then rises 20 cm

                      Can you jog each axis (X Y Z) separately from the DWC jog buttons?

                      You can use this command to allow jogging axes that are not homed:

                      M564: Limit axes
                      Parameters
                      Hnnn H1 = forbid movement of axes that have not been homed, H0 = allow movement of axes that have not been homed (firmware 1.21 and later)
                      Snnn S1 = limit movement within axis boundaries, S0 = allow movement outside boundaries

                      If you can jog each axis separately have you verified that jogging a certain amount from the DWC actually moves the axis that amount?

                      Frederick

                      Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                      troydemingundefined 1 Reply Last reply Reply Quote 0
                      • troydemingundefined
                        troydeming @fcwilt
                        last edited by troydeming

                        @fcwilt
                        Thank you for that I am able to jog them now. Now I found out that when I jog X the Z is moving. I double checked the wiring and its all correct. So now I am going down the rabbit hole of why the two are crossed in the mapping.

                        I am showing right now.
                        ;M584 X2 Y1 Z0 ; set axis mapping

                        It seems right to me but is it?

                        troydemingundefined 1 Reply Last reply Reply Quote 0
                        • troydemingundefined
                          troydeming @troydeming
                          last edited by

                          @troydeming

                          I just looked it up and I have them configured backwards.

                          fcwiltundefined 1 Reply Last reply Reply Quote 1
                          • fcwiltundefined
                            fcwilt @troydeming
                            last edited by

                            @troydeming

                            That might make homing not work quite right.

                            😁

                            Frederick

                            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                            troydemingundefined 1 Reply Last reply Reply Quote 0
                            • troydemingundefined
                              troydeming @fcwilt
                              last edited by

                              @fcwilt

                              I got it working finally. Therre was a fault in the wiring.

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