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

    Warning: the height map has a substantial Z offset

    Scheduled Pinned Locked Moved
    General Discussion
    3
    40
    2.2k
    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.
    • downshift64undefined
      downshift64
      last edited by

      i heat the bed up then probe it and save the height map i have something that uses that each time i start a new print

      fcwiltundefined 1 Reply Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt @downshift64
        last edited by

        @downshift64 said in Warning: the height map has a substantial Z offset:

        damn i wish this was easier

        If you have a Z probe AND make use of macros called via M98 it can be fairly straightforward and easy to maintain.

        Frederick

        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

        1 Reply Last reply Reply Quote 0
        • downshift64undefined
          downshift64
          last edited by

          my slicer start g code
          G90 ; use absolute coordinates
          M83 ; extruder relative mode
          M104 S[first_layer_temperature] T0 ; set extruder temp
          M140 S[first_layer_bed_temperature] ; set bed temp
          M190 S[first_layer_bed_temperature] ; wait for bed temp
          M109 S[first_layer_temperature] T0; wait for extruder temp
          G28 ; home all without mesh bed level
          G29 S1 ; mesh bed leveling
          G1 Z0.25 F2500
          G1 Y0 F1000.0 ; go outside print area
          G92 E0.0
          G1 X60.0 E9.0 F1000.0 ; intro line
          G1 X100.0 E12.5 F1000.0 ; intro line
          G92 E0.0
          M221 S{if layer_height<0.075}100{else}95{endif}

          1 Reply Last reply Reply Quote 0
          • fcwiltundefined
            fcwilt @downshift64
            last edited by fcwilt

            @downshift64 said in Warning: the height map has a substantial Z offset:

            i heat the bed up then probe it and save the height map i have something that uses that each time i start a new print

            The problem is the height map is referenced to the Z=0 datum when the height map is created.

            When the height map is loaded it expects that Z=0 datum to be the same value.

            Without a Z probe I'm not sure how to handle it other than assuming Z=0 is a fixed value and never changes.

            Frederick

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            1 Reply Last reply Reply Quote 0
            • downshift64undefined
              downshift64
              last edited by

              ya once i get height map it is a fixed value and should never change really

              fcwiltundefined 1 Reply Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @downshift64
                last edited by

                @downshift64 said in Warning: the height map has a substantial Z offset:

                ya once i get height map it is a fixed value and should never change really

                That has not been my experience with my printers but if yours is unchanging that is great.

                Frederick

                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                1 Reply Last reply Reply Quote 0
                • downshift64undefined
                  downshift64
                  last edited by

                  its an Ulitmate XL from Elite Machine Works its a solid bed

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

                    Post your home all.

                    The warning is a warning, it may not apply to you, but without seeing your homing files I can't say. Your slicer start gcode does a G28 to home the printer and then G29 S1 to load the heightmap. What we don't know is what homeall.g is doing to home the printer. Is it using an endstop, or a zprobe? That's where the potential for an offset lies. You probably updated the firmware from a version that didn't have the warning to one that does. If your first layer is still good, then you have no problem and you can ignore it. Or if you want to get rid of it, post your homeall so we can see what's going on with the gcode.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 1
                    • downshift64undefined
                      downshift64
                      last edited by

                      thank you i would like to get rid of it
                      G91 ; relative mode
                      G1 S1 Z310 F3500 ; move Z towards the switch until it triggers
                      G1 Z-4 F900 ; move Z back 10mm
                      G1 S1 Z6 F600 ; move Z slowly towards the switch until it triggers
                      G1 Z-4 F900 ; move Z back 10mm
                      G1 S1 Z6 F400 ; move Z slowly towards the switch until it triggers

                      G1 X-340 F7000 S1 ;
                      G1 X4 F600 ; move slowly 4mm in the +X direction
                      G1 X-5 S1 ; move slowly 10mm in the -X direction, stopping at the homing switch

                      G1 Y-340 F7000 S1 ; move up to 240mm in the -Y direction, stopping if the homing switch is triggered
                      G1 Y5 F600 ; move slowly 4mm in the +X direction
                      G1 Y-6 S1 ; move slowly 10mm in the -X direction, stopping at the homing switch

                      G4 P0 ; CLEAR BUFFER IN ORDER TO PROPERLY LOAD SAVED GRID
                      G90
                      ;G29 S1 ; LOAD SAVED BED GRID

                      G4 P0 ; CLEAR BUFFER AFTER LOADING GRID

                      G1 X0 Y0 F8000

                      fcwiltundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                      • fcwiltundefined
                        fcwilt @downshift64
                        last edited by

                        @downshift64 said in Warning: the height map has a substantial Z offset:

                        G4 P0 ; CLEAR BUFFER IN ORDER TO PROPERLY LOAD SAVED GRID

                        Hi,

                        I see the comment but I don't understand the purpose.

                        What buffer do you think needs clearing to load the height map?

                        I have never used G4 P0 and everything works just fine.

                        Thanks.

                        Frederick

                        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                        1 Reply Last reply Reply Quote 0
                        • downshift64undefined
                          downshift64
                          last edited by

                          sorry i cant answer your question this is what i got when i purchased the printer

                          1 Reply Last reply Reply Quote 0
                          • downshift64undefined
                            downshift64
                            last edited by

                            maybe something to do with not having to probe the bed every time before i print

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

                              @downshift64 said in Warning: the height map has a substantial Z offset:

                              G1 S1 Z310 F3500 ; move Z towards the switch until it triggers
                              G1 Z-4 F900 ; move Z back 10mm
                              G1 S1 Z6 F600 ; move Z slowly towards the switch until it triggers
                              G1 Z-4 F900 ; move Z back 10mm
                              G1 S1 Z6 F400 ; move Z slowly towards the switch until it triggers

                              It's saying you may have an offset because it's using an endstop to home the Z axis before loading the heightmap. If the endstop position is perfectly set then you don't have an issue, but it will still warn you.

                              Z-Bot CoreXY Build | Thingiverse Profile

                              fcwiltundefined downshift64undefined 2 Replies Last reply Reply Quote 0
                              • fcwiltundefined
                                fcwilt @Phaedrux
                                last edited by

                                @Phaedrux said in Warning: the height map has a substantial Z offset:

                                It's saying you may have an offset because it's using an endstop to home the Z axis before loading the heightmap. If the endstop position is perfectly set then you don't have an issue, but it will still warn you.

                                You sure?

                                I thought the offset warning was based on the contents of the height map file alone.

                                I tried to verify that but I couldn't figure an easy way to add a significant offset to each value in the file and then load it.

                                Frederick

                                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                                1 Reply Last reply Reply Quote 0
                                • downshift64undefined
                                  downshift64 @Phaedrux
                                  last edited by

                                  @Phaedrux so there is nothing i can do to get rid of the warning,, if not is it still using my heightmap as intended

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

                                    You can get rid of the warning and any potential offset by using the z probe to home the z axis. (Provided your z probe z offset in g31 is correct).

                                    If your first layers are good, then yes your height map is being applied and all is good.

                                    Z-Bot CoreXY Build | Thingiverse Profile

                                    downshift64undefined 1 Reply Last reply Reply Quote 0
                                    • downshift64undefined
                                      downshift64 @Phaedrux
                                      last edited by

                                      @Phaedrux i only use the z probe only when i change something with my printer like a new bed or i switch out the nozzle to make sure everything is still good

                                      downshift64undefined 1 Reply Last reply Reply Quote 0
                                      • downshift64undefined
                                        downshift64 @downshift64
                                        last edited by

                                        @downshift64 could i go back to the board software that didnt have this warning

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

                                          Is the warning that obtrusive?

                                          Z-Bot CoreXY Build | Thingiverse Profile

                                          downshift64undefined 1 Reply Last reply Reply Quote 0
                                          • downshift64undefined
                                            downshift64 @Phaedrux
                                            last edited by

                                            @Phaedrux no just everything worked great before i upgraded the board just wanted to go back to that, that way i know everything works as it should

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