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

Height map has a substantial Z offset error with mesh

Scheduled Pinned Locked Moved
Tuning and tweaking
9
30
4.6k
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 24 Jul 2019, 02:09

    It doesn't look like there is any weirdness with your homing files.
    Do you also have a bed.g macro?
    What does your slicer start gcode look like? Does it call G32?
    When are you running G29 or loading the heightmap?

    I would suggest redefining your trigger height and re-running mesh compensation with 2.03.

    https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

    Z-Bot CoreXY Build | Thingiverse Profile

    1 Reply Last reply Reply Quote 0
    • undefined
      Origami
      last edited by Origami 24 Jul 2019, 02:22

      This is my starting gcode:

      M572 D0 S0.2 ;Pressure Advance
      M82 ;absolute extrusion mode
      G90; Use logical positioning
      G92 E0 ;Nulls out the extruder
      G28; Homes the nozzle on x,y,z
      G28 Z; Homes the z axis again
      G30; Home z again with probe
      G29 S1; load last bed mesh from memory
      G4 S15; waits 15 seconds for the heaters to recover

      G1 Z5 ;moves up a bit
      G1 X295 Y30 F2700 ;moves over the front right corner.
      G1 Z0.3 F100; height of small blob
      M106 S255 ;turns fan on full
      G1 E20 F200;extrudes a small blob
      G4 P4000; Waits 4 seconds to the blob to cool a bit
      G1 Z0.5 ;moves up a bit
      G4 P5000; Waits 5 seconds to leaker to flow and cool a bit
      G1 Z7 F100; Pull out of the blob a bit
      G4 P5000 ; used for cooling down the stringing
      M106 S0 ;turns fan off
      G92 E0 ;Nulls out the extruder
      M83 ;relative extrusion mode

      I manually do the mesh with the web gui once in a while and the starting gcode just does G29 S1 to load it.

      1 Reply Last reply Reply Quote 0
      • undefined
        Phaedrux Moderator
        last edited by 24 Jul 2019, 02:25

        That looks ok too.

        As I said above, clear your heightmap, remeasure your trigger height, and then redo the G29 with 2.03. See if the problem persists.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • undefined
          Origami
          last edited by Origami 24 Jul 2019, 03:19

          EDIT: also i found the bed.g as well here it is:
          0_1563938574407_bed.g

          I did the Calibrate the Z probe trigger height in the link you provided, also deleted the heightmap file before proceding and im still getting the exact problem.

          alt text
          alt text

          1 Reply Last reply Reply Quote 0
          • undefined
            Veti
            last edited by 24 Jul 2019, 06:06

            your bed and hotends have the default B4138 value.
            this is most likely incorrect for your thermistor and will report the wrong temperature.

            undefined 1 Reply Last reply 24 Jul 2019, 06:17 Reply Quote 0
            • undefined
              Origami @Veti
              last edited by 24 Jul 2019, 06:17

              @veti hmm what should I set it to? I have the stock cr10s thermistor for both hotend and bed

              1 Reply Last reply Reply Quote 0
              • undefined
                Veti
                last edited by 24 Jul 2019, 06:46

                according to the marlin config
                https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.0.x/config/examples/Creality/CR-10S/Configuration.h

                the hotend is a epcos 100k and the bed is a semitec 104GT-2, both can be selected in the duet configurator.

                undefined 1 Reply Last reply 24 Jul 2019, 06:49 Reply Quote 0
                • undefined
                  Origami @Veti
                  last edited by Origami 24 Jul 2019, 06:49

                  @veti this may sound stupid but how do i select it in the duet configurator lol... is it the rrf config tool? It just asks me to type in the b value there are no preset selections.

                  alt text

                  I have found the Semitec b value in the wiki here but Epcos 100k have 3 different model so not sure which one I should be using...
                  https://reprap.org/wiki/Thermistor

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    Veti
                    last edited by 24 Jul 2019, 06:58

                    click into the beta field and the selector will open

                    undefined 1 Reply Last reply 24 Jul 2019, 07:01 Reply Quote 0
                    • undefined
                      Origami @Veti
                      last edited by Origami 24 Jul 2019, 07:01

                      @veti OH now i feel dumb xD thanks for the tip there, got my bed at 4267 and nozzle at 4092 now 😄

                      I looked up datasheet for both thermistor and used that instead of the preset since it seem to be incorrect as the EPCOS was only 10k ohm on the rrf.

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Veti
                        last edited by 24 Jul 2019, 07:15

                        you are correct. that is a mistake in the configurator. it is supposed to be 100k and 4092 B
                        see
                        https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.0.x/Marlin/src/module/thermistor/thermistor_1.h

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          Origami
                          last edited by Origami 24 Jul 2019, 07:19

                          Back on topic tho... I'm running a new bed mesh now with the bed heated up to 60c... I'm sure the temp will be more accurate than before now.

                          but mesh has no luck, bed is still floating in midair on the mesh for some reason..

                          1 Reply Last reply Reply Quote 1
                          • undefined
                            Veti
                            last edited by 24 Jul 2019, 08:53

                            but it does work if you probe before every print?

                            undefined 1 Reply Last reply 24 Jul 2019, 15:16 Reply Quote 0
                            • undefined
                              Origami @Veti
                              last edited by 24 Jul 2019, 15:16

                              @veti that will have same result, basically my mesh is like 0.7 mm higher than what its supposed to be, I can use the Z baby stepping in web gui to lower the nozzle to around -0.95 mm and it'll print OK. Before the lowest I have used is like -0.25 mm

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                Veti
                                last edited by 24 Jul 2019, 15:41

                                i am guessing the you are doing the homing with the hotend and bed turned on.
                                did you create the heighmap under the same conditions?

                                undefined 1 Reply Last reply 24 Jul 2019, 19:53 Reply Quote 0
                                • undefined
                                  Origami @Veti
                                  last edited by 24 Jul 2019, 19:53

                                  @veti yes everytime mesh is done it is at printing temp

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    gueee78
                                    last edited by 24 Jul 2019, 20:10

                                    @dc42 do you have any idea what could cause that behavior. I tried to help him find the issue but since z-homing with the mini IR works flawlessly I can't think of what it actually is.
                                    it seems like it just adds a certain offset value to the probe values at some point for no reason.
                                    as if z0 gets redefined after initial z homing.

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Origami
                                      last edited by Origami 24 Jul 2019, 21:03

                                      Just an update.. I did absolutely no modifications beside the heater stuff yesterday, however today i just did another mesh and there was 1 point that was below 0 and the warning message went away. I started another print and my z babystepping value went from -0.95mm to -0.45mm which is much better than before but still not what I had before which is max -0.25mm.

                                      alt text

                                      undefined 1 Reply Last reply 22 Feb 2021, 13:53 Reply Quote 0
                                      • undefined
                                        Veti
                                        last edited by 25 Jul 2019, 05:53

                                        you are probing on glass with an Ir sensor.
                                        check that the point where you are probing does not have any special feature, since its the center and that is where the thermistor is.

                                        do check the repeatrability of your probe at different places.
                                        https://forum.duet3d.com/topic/6962/m48-measure-z-probe-repeatability-and-print-to-serial-output/7

                                        1 Reply Last reply Reply Quote 1
                                        • undefined
                                          gueee78
                                          last edited by 25 Jul 2019, 17:18

                                          Hey Veti,

                                          no he's not probing on glass he uses a TH3D sheet, completely opak and it worked flawlessly before. That phenomenonm started to appear all of a sudden with nothing changed. Btw it got better again, but the repeatability is still rather bad.
                                          Switchin the printer off and on again usually trows the settings off by about 0.3mm wich is way too much imo.

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