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

    strange first layer. bed and mesh are calibrated

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    15
    491
    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.
    • c310undefined
      c310
      last edited by

      I decided to print something bigger than usual and found that some parts of the bed are not printed well.

      i calibrated my delta duetwifi and run mesh with 11 mm spacing.
      where should i look to make 1st layer consistent?

      IMG_20210318_141241.jpg IMG_20210318_141244.jpg IMG_20210318_141247.jpg

      b003b2f1-6cd2-4965-a0c9-45e8945a71c7-изображение.png

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

        Post your config.g, homedelta, bed.g, and slicer start gcode And Results of M122 and M98 P"config.g"

        Z-Bot CoreXY Build | Thingiverse Profile

        c310undefined 1 Reply Last reply Reply Quote 0
        • c310undefined
          c310 @Phaedrux
          last edited by

          @Phaedrux

          attached are configs... M92 Pconfig.g gave only "M98 P"config.g" Use P parameter to specify which module to debug" i was not able to locate that information in g-code documentation 😞

          thank you in advance !

          bed.g

          config.g

          config-override.g

          homedelta.g

          slicer_start.gcode

          M122.txt

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

            @c310 said in strange first layer. bed and mesh are calibrated:

            M92 Pconfig.g gave only "M98 P"config.g" Use P parameter to specify which module to debug" i was not able to locate that information in g-code documentation

            I'm not sure what this means.

            In the gcode console, send M98 P"config.g" and report the results.

            Z-Bot CoreXY Build | Thingiverse Profile

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

              When was the last time you re-created your heightmap mesh?

              Z-Bot CoreXY Build | Thingiverse Profile

              c310undefined 1 Reply Last reply Reply Quote 0
              • c310undefined
                c310 @Phaedrux
                last edited by

                @Phaedrux

                heightmap was re-created after last "under-the-heatbed works", maybe a week age. since than i did not touch bed or nozzle.

                and M98

                d1887d2c-9e98-4195-bfc4-e8b5b9dd473c-изображение.png

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

                  Ah ok, I understand the error message there. It's from your M111 command.

                  https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M111_Set_Debug_Level

                  Z-Bot CoreXY Build | Thingiverse Profile

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

                    Can you show the heightmap from a isometric side angle so we can see the surface pattern better?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • c310undefined
                      c310
                      last edited by

                      5b5849e6-1cfd-4410-85a2-2111ab000351-изображение.png

                      16cced3d-8dc0-4a8c-8a5d-22ad5aca28b1-изображение.png

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

                        Would you say there are ridges in the pattern? If so that could be a result of backlash.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        c310undefined 1 Reply Last reply Reply Quote 0
                        • vwegertundefined
                          vwegert
                          last edited by

                          Would you say that it looks similar to what I've reported in https://forum.duet3d.com/topic/21341/first-layer-extrusion-issues?_=1612116959524 ?

                          c310undefined 1 Reply Last reply Reply Quote 0
                          • c310undefined
                            c310 @vwegert
                            last edited by

                            @vwegert yes, it is very similar

                            1 Reply Last reply Reply Quote 0
                            • c310undefined
                              c310 @Phaedrux
                              last edited by

                              @Phaedrux i would say it is more like peaks, not ridges on the height map. I also was not able to find correlation between heightmap and defects of the first layer.

                              ...backlash - do you mean belt tension?

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

                                Seems like maybe the smart effector sensitivity is too low and you're getting inconsistent probe results.

                                https://duet3d.dozuki.com/Wiki/Smart_effector_and_carriage_adapters_for_delta_printer#Section_Commissioning

                                Z-Bot CoreXY Build | Thingiverse Profile

                                c310undefined 1 Reply Last reply Reply Quote 0
                                • c310undefined
                                  c310 @Phaedrux
                                  last edited by c310

                                  @Phaedrux

                                  thank you for the hint. is my smarteffector (v.1.3 i think) board goes crazy?

                                  in the documentations it is mentioned that after sending " M672 S131:131" LED should flash 5 times. my does not flash at all. However LED itself works: when i probe the bed with hands - LED flashes when nozzle touches the bed. And it does flashes twice when boot.

                                  in my case smarteffector is configured before G31 in RRF3.2.2 by M558 P8 C"zprobe.in" R0.4 F1200

                                  should i replace smarteffector board or it is still can be reprogrammed ???

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