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

    G1 H1 X-355 F3000 does not work as expected

    Scheduled Pinned Locked Moved Solved
    Tuning and tweaking
    6
    11
    411
    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.
    • jay_s_ukundefined
      jay_s_uk @spllg
      last edited by

      @spllg how big is your printer?
      Try increasing the -350 to a larger number. I use -999 in mine which is larger than my print size.

      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

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

        Please upgrade your firmware to 3.0RC2.

        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

        spllgundefined 2 Replies Last reply Reply Quote 1
        • spllgundefined
          spllg @dc42
          last edited by spllg

          @dc42 upgrading to 3.0RC2 made things worse:

          • after an initial failed x-home (from x=100,y=0, g1 h1 premature stopped at invisible endswitch) a subsequent x-home attempt (null-effect) did not terminate

          • after a successful x-home from (x=100,y=120) a z-home caused one spindle to move upwards while the other spindle did not move (dual z-steppers) resulting in a very ugly noise.

          reverted to 3.0beta12

          1 Reply Last reply Reply Quote 0
          • spllgundefined
            spllg @jay_s_uk
            last edited by

            @jay_s_uk already have tried this - could not observe any change

            1 Reply Last reply Reply Quote 0
            • spllgundefined
              spllg @dc42
              last edited by

              @dc42 i feel, the problem might be related to micro step configuration as the y-threshold changes when i change micro step configuration (using m350 xnn ynn)

              A Former User? 1 Reply Last reply Reply Quote 0
              • A Former User?
                A Former User @spllg
                last edited by

                @spllg said in G1 H1 X-355 F3000 does not work as expected:

                @dc42 i feel, the problem might be related to micro step configuration as the y-threshold changes when i change micro step configuration (using m350 xnn ynn)

                don't recall the specifics, but changes to microstepper or steps/mm after the other will affect the former. I.e. the order matters. show your config and I'm sure someone will spot any issues there.

                1 Reply Last reply Reply Quote 1
                • Danalundefined
                  Danal
                  last edited by

                  Yes, please post your entire config.g

                  Delta / Kossel printer fanatic

                  spllgundefined 1 Reply Last reply Reply Quote 0
                  • spllgundefined
                    spllg @Danal
                    last edited by

                    @Danal here it is

                    ; General preferences
                    G90 ; send absolute coordinates...
                    M83 ; ...but relative extruder moves
                    M550 P"3dd" ; set printer name

                    M667 S1 ; select CoreXY mode

                    ; Drives
                    M569 P0.0 S1 ; physical drive 0.0 goes forwards ; XY - right
                    M569 P0.1 S1 ; physical drive 0.1 goes forwards ; XY - left
                    M569 P0.2 S1 ; physical drive 0.2 goes forwards ; Zr
                    M569 P0.3 S1 ; physical drive 0.3 goes forwards ; Zl
                    M569 P0.4 S0 ; physical drive 0.3 goes forwards ; E0

                    ;M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
                    ;M584 X0.0 Y0.1 Z0.3 E0.3 ; set drive mapping
                    M584 X0.0 Y0.1 Z0.2:3 E0.4 ; set drive mapping

                    M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
                    M92 X200.00 Y200.00 Z400.00 E420.00 ; set steps per mm

                    M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
                    M203 X12000.00 Y12000.00 Z3000.00 E3600.00 ; set maximum speeds (mm/min)

                    M201 X500.00 Y500.00 Z25.00 E250.00 ; set accelerations (mm/s^2)
                    M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
                    M84 S30 ; Set idle timeout

                    ; Axis Limits
                    M208 X-26 Y0 Z0 S1 ; set axis minima
                    M208 X280 Y300 Z340 S0 ; set axis maxima

                    ; Endstops
                    M574 X1 S1 P"io3.in" ; configure active-low endstop for low end on X via pin io3.in
                    M574 Y1 S1 P"io4.in" ; configure active-low endstop for low end on Y via pin io4.in
                    M574 Z1 S1 P"io5.in" ; configure active-low endstop for low end on Z via pin io5.in

                    ; bed leveling
                    ;M671 X50:150 Y150:150 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis

                    ; ???
                    ;M558 P1 C"io5.in" H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed

                    ; Z-Probe ( https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type )
                    ;M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
                    ;M557 X15:215 Y15:195 S20 ; define mesh grid

                    M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
                    M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1

                    ; 2DO: fix and all below
                    ; Heaters
                    M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
                    M143 H0 S110 ; set temperature limit for heater 0 to 120C
                    M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
                    M140 H0 ; map heated bed to heater 0

                    M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
                    M143 H1 S280 ; set temperature limit for heater 1 to 280C
                    M307 H1 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit

                    ; Fans
                    M950 F0 C"out4" Q500 ; create fan 0 on pin out3 and set its frequency
                    M106 P0 H-1 ; set fan 0 value. Thermostatic control is turned off
                    ;M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
                    M950 F1 C"out5" Q500 ; create fan 1 on pin out4 and set its frequency
                    M106 P1 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
                    ;M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

                    ; Tools
                    M563 P0 D0 H1 F0 ; define tool 0
                    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
                    G10 P0 R0 S0 ; set initial tool 0 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

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

                      @spllg The Z movement issue might be caused by this M584 X0.0 Y0.1 Z0.2:3 E0.4 which ought to be M584 X0.0 Y0.1 Z0.2:0.3 E0.4. Also, strictly speaking M667 is deprecated so M667 S1 ought to be M669 K1.

                      It might be an idea if you post your homing files too.

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

                      spllgundefined 1 Reply Last reply Reply Quote 2
                      • spllgundefined
                        spllg @deckingman
                        last edited by

                        @deckingman changing the 2 suggested lines solved both issues - x-homing now works fine using 3.0RC2

                        thanks a lot

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