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

    Piezo as Z Endstop & as Z-Probe config

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    26
    2.1k
    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.
    • grizewaldundefined
      grizewald
      last edited by

      There's no need to probe the bed for every print.

      In my bed.g, I use G29 S1 to load and activate the stored map. This allows you to create a much more detailed map than 5 x 5 and save it. I refresh the map once in a while, but there is rarely any difference between the new and previous maps.

      Are you executing a G32 so that bed.g is executed in your slicer's start code?

      1 Reply Last reply Reply Quote 0
      • sinned6915undefined
        sinned6915
        last edited by

        I only probe at every power on. I don't re-probe between prints

        I am not using G32. I thought that was for Delta's.

        Is it redundant with G29?

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

          G32 just runs bed.g.

          What do you have in your slicer start gcode?

          When G29 is run the mesh is probed and the results are saved, and compensation is made active.

          G29 S1 will load the saved heightmap. So you should have that in your slicer start code after your G28.

          You can send M122 to get a diagnostics report, look for a line saying compensation: mesh to indicate that it's active.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • sinned6915undefined
            sinned6915
            last edited by sinned6915

            I currently don't have anything in my start gcode. I understood that the mesh bed compensation was active until you re-homed via G28.

            EDIT: when I print, I use a macro to preheat, then home & level-

            M80
            M106 S0
            M104 S130
            G28 X Y
            M109 S130
            G28 Z
            G29 
            G1 X150 Y150 Z5 F3500 
            

            M122 shows-

            === Move ===
            Hiccups: 0, FreeDm: 99, MinFreeDm: 63, MaxWait: 24240329ms
            Bed compensation in use: mesh, comp offset 0.000
            

            full listing is here- https://pastebin.com/HGviebvr

            BTW: Is there a way to get more verbose output to the console? I wish that more info would get displayed to know what is going on.

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

              G28 won't clear G29 by default. Yours will because you have M561 at the start.

              M122 shows mesh is active.

              What does your heightmap image look like?

              I think the best way to test if mesh compensation is effective is to print an STL like this once with mesh disabled and once with mesh enabled. The results should be better when it's enabled.

              0_1565997501514_bedlevel_nozzle_0.4_200x200-0.3-0.8.stl

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 1
              • sinned6915undefined
                sinned6915
                last edited by sinned6915

                Which M561 do you mean? I have that in there because I wanted to make sure I cleared out baby-stepping in the case I forgot to clear it.

                Perhaps this is the source of my issue? How do you clear baby-steps?

                here is my heightmap from different views-

                alt text

                alt text

                alt text

                alt text

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

                  So the z motors don't move at all if you move to that dipped area?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  sinned6915undefined 1 Reply Last reply Reply Quote 0
                  • sinned6915undefined
                    sinned6915
                    last edited by

                    typically, i stay away from that area if i can.

                    i will scale the stl you linked and print it over the whole bed.

                    i have a print finishing now- it might be a couple of hours before i can post results.

                    1 Reply Last reply Reply Quote 0
                    • sinned6915undefined
                      sinned6915 @Phaedrux
                      last edited by

                      @phaedrux

                      thanks again for your tutelage.

                      the compensation does work as expected. i have been trying to straighten the bed little by little by taking it off and giving it a good, strategic hammer blow or two.

                      sinneD

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

                        @sinned6915 nothing wrong with a little percussive maintenance now and then.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 1
                        • grizewaldundefined
                          grizewald
                          last edited by

                          "percussive maintenance"

                          🤣

                          Lovely!

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