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

Duet Maestro in MakerGear M3

Scheduled Pinned Locked Moved
General Discussion
4
48
1.7k
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.
  • undefined
    Phaedrux Moderator
    last edited by 25 Feb 2020, 20:44

    M671 is where you define the position of the screws.
    https://duet3d.dozuki.com/Wiki/Gcode#Section_M671_Define_positions_of_Z_leadscrews_or_bed_levelling_screws

    Z-Bot CoreXY Build | Thingiverse Profile

    1 Reply Last reply Reply Quote 0
    • undefined
      guycobb2
      last edited by 25 Feb 2020, 20:58

      Ok, that makes more sense. So, if I place the nozzle above a screw to find it’s XY coordinates, do I use the numbers shown on the GUI or do I need to compensate for the 21mm X offset of the BLtouch? I have the BLtouch offset defined in the config.g file.

      1 Reply Last reply Reply Quote 0
      • undefined
        Phaedrux Moderator
        last edited by 25 Feb 2020, 21:07

        M671 would be the location of the screws in absolute coordinates. So yes the nozzle position should define it. It's in your bed.g where you would be defining the probing points that you may have to account for the probe offset so that you're positioning the probe close to the screws rather than the nozzle close to the screws.

        I assume you've seen these:

        https://duet3d.dozuki.com/Wiki/Using_the_manual_bed_levelling_assistant
        https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 1
        • undefined
          guycobb2
          last edited by 25 Feb 2020, 22:27

          Excellent. Thanks. I do indeed already have both of those docs opened in tabs. Currently at work, just trying to determine my attack plan for when I get home tonight.

          Some of the docs just didn’t explain enough detail as to what everything did (or at least I didn’t see it if it did) but you’re making things more clear.

          1 Reply Last reply Reply Quote 0
          • undefined
            guycobb2
            last edited by 26 Feb 2020, 11:47

            So I have the manual bed adjustment assistant working and used it to tram the bed.

            After that I setup the m557 for the bed mesh compensation and tried running it. However, I keep getting a “Error G29: no valid grid defined for bed probing” .

            Here’s my bed.g that’s setup for the leveling assistant.

            ; bed.g
            ; called to perform manual bed level assistant via G32
            ;
            ; generated by RepRapFirmware Configuration Tool v2.1.8 on Mon Feb 24 2020 01:49:32 GMT-0600 (Central Standard Time)
            M561 ; clear any bed transform
            G28 ; home all axis
            G30 P0 X25 Y16 Z-99999
            G30 P1 X215 Y16 Z-99999
            G30 P2 X25 Y248 Z-99999
            G30 P3 X215 Y248 Z-99999 S4
            G1 X100 Y126.5 F9000 ; go to center of bed

            And here’s a chunk from my config.g file....what am I missing?

            ;Z-Probe
            M558 P9 H5 F300 T9000 ; set Z probe type to bltouch and the dive height + speeds
            G31 P500 X21.0 Y0 Z1.048 ; set Z probe trigger value, offset and trigger height
            M557 X25:215 Y16:Y248 P3 ; define mesh grid with P defining number of points to probe in each axis

            ; Manual Bed Leveling Assistant
            M671 X21:219.5:21:219.5 Y8.5:8.5:257.5:257.5 P0.7 ; bed adjustment screws are front left (x21,y8.5), front right (x219.5,y8.5), rear left (x21,257.5), rear right (x219.5,y257.5), thread pitch is 0.7

            undefined 1 Reply Last reply 26 Feb 2020, 13:02 Reply Quote 0
            • undefined
              droftarts administrators @guycobb2
              last edited by 26 Feb 2020, 13:02

              @guycobb2 M557 looks okay, assuming that the X and Y limits you have set can be reached by the probe. Did you restart after changing config.g? Try entering the M557 command directly in the console. Sending M557 on it's own should report the settings. G29 doesn't use the bed.g, G32 does.

              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

              1 Reply Last reply Reply Quote 0
              • undefined
                guycobb2
                last edited by 26 Feb 2020, 18:20

                M557 reports “grid not defined”. Wtf?

                undefined 1 Reply Last reply 26 Feb 2020, 18:44 Reply Quote 0
                • undefined
                  Phaedrux Moderator @guycobb2
                  last edited by 26 Feb 2020, 18:44

                  @guycobb2 said in Duet Maestro in MakerGear M3:

                  M557 reports “grid not defined”. Wtf?

                  What do you get if you copy and paste your m557 from config.g into the console?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    Phaedrux Moderator
                    last edited by 26 Feb 2020, 18:45

                    @guycobb2 said in Duet Maestro in MakerGear M3:

                    M557 X25:215 Y16:Y248 P3

                    I think I see the issue... Do you notice the Y values? You've got an extra Y in there.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      guycobb2
                      last edited by 26 Feb 2020, 18:46

                      Sonofabitch. 😂😂😂

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Phaedrux Moderator
                        last edited by 26 Feb 2020, 18:48

                        Still curious to see what the console feedback would be from that line.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        undefined 1 Reply Last reply 26 Feb 2020, 18:48 Reply Quote 0
                        • undefined
                          guycobb2
                          last edited by 26 Feb 2020, 18:48

                          How in the crap have I overlooked that for 24 hours?

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            guycobb2 @Phaedrux
                            last edited by 26 Feb 2020, 18:48

                            @Phaedrux it said the Y value too small

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              guycobb2
                              last edited by 26 Feb 2020, 18:49

                              More specifically “error m557: bad grid definition: Y range too small”

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                Phaedrux Moderator
                                last edited by 26 Feb 2020, 18:50

                                Well that would have been a clue anyway.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  guycobb2
                                  last edited by 26 Feb 2020, 18:54

                                  Can someone give a brief explanation of the deviation and error results?

                                  https://imgur.com/zB9In38.jpg

                                  undefined 1 Reply Last reply 26 Feb 2020, 21:31 Reply Quote 0
                                  • undefined
                                    guycobb2
                                    last edited by 26 Feb 2020, 18:57

                                    After bed mesh is complete do I need to reload the height map after a reboot of the board?

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Phaedrux Moderator
                                      last edited by 26 Feb 2020, 18:58

                                      the max deviation is the lowest and highest point to either side of wherever you set the Z0 point.

                                      mean error is the average of all the deviations. So your's is slightly below the 0 point on average.

                                      RMS I'm not actually sure.

                                      Yes you need to reload the heightmap after a power cycle. This would typically be done in your slicer start gcode after homing. Use G29 S1

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      undefined 1 Reply Last reply 26 Feb 2020, 19:26 Reply Quote 1
                                      • undefined
                                        guycobb2 @Phaedrux
                                        last edited by 26 Feb 2020, 19:26

                                        @Phaedrux thanks for everybody’s help. I went ahead and knocked out a quick test print and all looks good. It looks like the duet is removing the artifacts I was experiencing with the stock Rambo board. More testing to confirm, I will play with it more tonight after I get back home from work.

                                        I forgot that I plan on running the quick 9 point mesh at the start of every print so no need to reload the height map. But good to know if I decide to remove that from my starting process. Thanks again everybody.

                                        undefined 1 Reply Last reply 26 Feb 2020, 19:29 Reply Quote 0
                                        • undefined
                                          Phaedrux Moderator @guycobb2
                                          last edited by 26 Feb 2020, 19:29

                                          @guycobb2 said in Duet Maestro in MakerGear M3:

                                          I forgot that I plan on running the quick 9 point mesh at the start of every print so no need to reload the height map. But good to know if I decide to remove that from my starting process. Thanks again everybody.

                                          If your bed is stable and doesn't really change from print to print you might benefit from doing a more detailed heightmap once, and then loading it, rather than doing a 9 point heightmap each time. Would need to compare to see what works best. It's also useful to do at least one high detail heightmap so you can see what your bed surface actually looks like.

                                          Z-Bot CoreXY Build | Thingiverse Profile

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