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

    hbot homes correctly but prints mirrored ,

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    169
    8.8k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      No problem.

      Z-Bot CoreXY Build | Thingiverse Profile

      tracarundefined 1 Reply Last reply Reply Quote 1
      • tracarundefined
        tracar @Phaedrux
        last edited by tracar

        @Phaedrux
        are you aware of anywhere i can download differnt macro files for differnt things, fully auto scripts, manual stuff.... dont care what they are, just want to find, learn, modify , try things out see what i can do with this printer. if you have any stuff you can pass on to me , please send me a file with a side of everything 😉

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

          You can take a look at mine if you like.

          https://www.dropbox.com/s/td86jdrztubq2dg/macros.zip?dl=0

          https://www.dropbox.com/s/k25fuhdrr7c3miy/Config V22.zip?dl=0

          Z-Bot CoreXY Build | Thingiverse Profile

          tracarundefined 2 Replies Last reply Reply Quote 0
          • tracarundefined
            tracar @Phaedrux
            last edited by

            @Phaedruxnice, Thanks this gives me hours of hair pulling fun

            1 Reply Last reply Reply Quote 0
            • tracarundefined
              tracar @Phaedrux
              last edited by tracar

              @Phaedrux

              after upgrading to 3xx this wont save its probe data
              what needs to be changed?

              ; bed.g
              ; called to perform automatic bed compensation via G32
              ;
              ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Aug 02 2020 19:54:07

              ; BLTOUCH PREP
              ;
              M400
              G4 S1
              M280 P0 S160 I1 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed
              G4 S1
              M402 ; Retract probe just in case it's down
              M400
              M561 ; clear all bed compensation
              G28 ; home all axis
              G90 ; absolute positioning
              G1 X220 Y330 Z10 ; move probe to center of the bed
              G30 ; set Z0 position with the probe
              ;G1 Z25 ; return to 25mm height
              G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
              G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
              G1 X220 Y330 Z25 ; move probe to center of the bed
              M500 P31; save results
              M501 ; load new data
              G30 ; set Z0 position with the probe
              M280 P7 S90
              M402 ; retract probe

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

                @tracar said in hbot homes correctly but prints mirrored ,:

                M280 P7 S90

                If you're on RRF3 P7 should be P0

                @tracar said in hbot homes correctly but prints mirrored ,:

                M500 P31; save results

                Does it work if you put a space between the P31 and the ; ?

                The only issues I am aware of with M500 is that it's currently not supported with the Duet 3 when used with a Pi.

                Do you get any error messages if you send M500 by itself?

                If you delete your config-override.g and send M500 does it get created?'

                Actually, looking again, it doesn't look like you're using G30 S-3 to measure the probe offset with this macro, so M500 P31 isn't going to do anything here. What are you expecting it to save?

                Z-Bot CoreXY Build | Thingiverse Profile

                tracarundefined 1 Reply Last reply Reply Quote 0
                • tracarundefined
                  tracar @Phaedrux
                  last edited by tracar

                  @Phaedrux
                  i moved the m500 and m501 below the line under the 501, seens to work and generate the correct offset and save it in a newly created config override file correctly......as i deleted to test with m32
                  verified by homing z, droping the table and baby stepping up till the probe is triggered. the z axis ,matches what was automatically stored

                  no error message when send m500.

                  ; bed.g
                  ; called to perform automatic bed compensation via G32
                  ;
                  ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Aug 02 2020 19:54:07

                  ; BLTOUCH PREP
                  ;
                  M400
                  G4 S1
                  M280 P0 S160 I1 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed
                  G4 S1
                  M402 ; Retract probe just in case it's down
                  M400
                  M561 ; clear all bed compensation
                  G28 ; home all axis
                  G90 ; absolute positioning
                  G1 X220 Y330 Z10 ; move probe to center of the bed
                  G30 ; set Z0 position with the probe
                  G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
                  G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
                  G1 X220 Y330 Z25 ; move probe to center of the bed
                  M500 P31; save results
                  M501 ; load new data
                  G30 ; set Z0 position with the probe
                  M280 P0 S90
                  M402 ; retract probe
                  G28 ; home all axis

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

                    @tracar said in hbot homes correctly but prints mirrored ,:

                    i moved the m500 and m501 below the line under the 501, seens to work and generate the correct offset and save it in a newly created config override file

                    Since you haven't changed it with a G30 S-1 it's just saving the same value as before. There is no reason in this macro to have M500 or M501

                    Z-Bot CoreXY Build | Thingiverse Profile

                    tracarundefined 1 Reply Last reply Reply Quote 0
                    • tracarundefined
                      tracar
                      last edited by tracar

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • tracarundefined
                        tracar @Phaedrux
                        last edited by tracar

                        @Phaedrux
                        ; bed.g
                        ; called to perform automatic bed compensation via G32
                        ;
                        M400 ; Finishes all current moves and clears the buffer
                        G4 S1 ; wait 1 second
                        M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
                        G4 S1 ; wait 1 second
                        M402 ; Retract probe just in case it's down
                        M400 ; Finishes all current moves and clears the buffer
                        M561 ; clear all bed compensation
                        G28 ; home all axis
                        G90 ; absolute positioning
                        G1 X220 Y330 F8000 Z10 F800 ; move probe to center of the bed
                        G30 S-1 ; set Z0 position with the probe
                        G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
                        G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
                        G1 X220 Y330 F8000 Z10 F800 ; move probe to center of the bed
                        G30 S-1 ; set Z0 position with the probe
                        M402 ; retract probe

                        what im trying to do is have this auto level the bed. and figure out how to keep this new probed info after another homez or homeall is called, say like starting a print.

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

                          @tracar said in hbot homes correctly but prints mirrored ,:

                          figure out how to keep this new probed info after another homez or homeall is called, say like starting a print.

                          Well it will stay in effect until the motors are de-energized. It should stay leveled through a G28 unless you're changing the position of individual motors in your homeall.

                          G30 S-1 ; set Z0 position with the probe
                          M402 ; retract probe
                          

                          Don't do that. The G30 S-1 is only for determining your trigger height. You don't need or want to do that after you've done the tilt correction. Just do a single G30 at the center of the bed to redefine the Z0 position because the tilt correction will change it slightly. Trigonometry and all that.

                          If your G28/homeall homes the Z axis, you don't need to do that again at the start of the leveling points. Just after.

                          ; bed.g
                          ; called to perform automatic bed compensation via G32
                          ;
                          M400 ; Finishes all current moves and clears the buffer
                          G4 S1 ; wait 1 second
                          M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
                          G4 S1 ; wait 1 second
                          M402 ; Retract probe just in case it's down
                          M400 ; Finishes all current moves and clears the buffer
                          M561 ; clear all bed compensation
                          G28 ; home all axis
                          G90 ; absolute positioning
                          G30 P0 X440 Y330 Z-99999 ; probe near a leadscrew, half way along Y axis
                          G30 P1 X0 Y330 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
                          G1 X220 Y330 F8000 Z10 F800 ; move probe to center of the bed
                          G30 ; set Z0 position with the probe
                          M402 ; retract probe

                          Also keep in mind that the tilt correction for the bed is only in one axis. It can't correct for tilt along Y. You might also need to run the G32 a couple times to get the tilt completely corrected, and depending on the repeatability of the probe you might end up bouncing around in the noise. So try and get it leveled up as best as you can manually to begin with.

                          After it's all leveled you may want to run a G29 to get a heightmap of the bed surface itself to see how it looks.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          tracarundefined 1 Reply Last reply Reply Quote 0
                          • tracarundefined
                            tracar @Phaedrux
                            last edited by

                            @Phaedrux said in hbot homes correctly but prints mirrored ,:

                            to get a heightmap of the bed surface itself to s

                            flawless !!!

                            you rock.

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