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

    removing a warning height map message

    Scheduled Pinned Locked Moved
    Duet Web Control
    5
    23
    992
    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.
    • fcwiltundefined
      fcwilt @Stephen6309
      last edited by

      @stephen6309 said in removing a warning height map message:

      @fcwilt I used them to make it easier to set them. I just changed to a chimera, and only had to edit that file with the new offsets and run it, since I also use them in the macros to set my G31. Don't like to edit config.g, too many times a typo foobared it.

      Got it.

      I deal with that sort of thing, where the values are not likely to change, by putting the needed commands in a separate g-code file in the sys folder.

      For example I put all of the Z probe configuration commands in a file name probe_config.g. I include a M98 P"probe_config.g" command in any other file that is about to use the probe, so the most recent settings I edited into probe_config.g are applied. No need to re-boot the printer, just edit the file and the changes will be used.

      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 1
      • sebxtremeundefined
        sebxtreme
        last edited by sebxtreme

        hi sorry for lte response, but i'm on delta , and i use Homedelta.g, but this warning message come when i launch a print job, and only on my delta printer ... not on my CR10...and on this my mesh is 6 month old... so i'm not understanding why....

        homedelta.g
        ; called to home all towers on a delta printer
        ;
        ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 13:22:54 GMT+0200 (heure d’été d’Europe centrale)
        G91 ; relative positioning
        G1 H1 X650 Y650 Z650 F1800 ; move all towers to the high end stopping at the endstops (first pass)
        G1 H2 X-5 Y-5 Z-5 F900 ; go down a few mm
        G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
        G1 Z-3 F900 ; move down a few mm so that the nozzle can be centred
        G90 ; absolute positioning
        G1 X0 Y0 F6000 ; move X+Y to the centre

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

          @sebxtreme said in removing a warning height map message:

          hi sorry for lte response, but i'm on delta , and i use Homedelta.g, but this warning message come when i launch a print job, and only on my delta printer ... not on my CR10...and on this my mesh is 6 month old... so i'm not understanding why....

          homedelta.g
          ; called to home all towers on a delta printer
          ;
          ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 13:22:54 GMT+0200 (heure d’été d’Europe centrale)
          G91 ; relative positioning
          G1 H1 X650 Y650 Z650 F1800 ; move all towers to the high end stopping at the endstops (first pass)
          G1 H2 X-5 Y-5 Z-5 F900 ; go down a few mm
          G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
          G1 Z-3 F900 ; move down a few mm so that the nozzle can be centred
          G90 ; absolute positioning
          G1 X0 Y0 F6000 ; move X+Y to the centre

          We'd need to see your config.g, bed.g and your slicer start gocode to see when the mesh is actually being loaded and when/how Z0 is being set. You may just need to add a single G30 at the center of the bed right before the heightmap is loaded to eliminate the warning.

          Z-Bot CoreXY Build | Thingiverse Profile

          sebxtremeundefined 3 Replies Last reply Reply Quote 0
          • sebxtremeundefined
            sebxtreme @Phaedrux
            last edited by sebxtreme

            @phaedrux

            ; executed by the firmware on start-up
            ;
            ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 13:22:54 GMT+0200 (heure d’été d’Europe centrale)
            
            ; General preferences
            G90                                                  ; send absolute coordinates...
            M83                                                  ; ...but relative extruder moves
            M550 P"predatorseb"                                  ; set printer name
            M665 L440.356:440.356:440.356 R232.585 H421.757 B185.0 X0.750 Y-0.100 Z0.000
            M666 X0.185 Y-1.345 Z1.160 A-0.43 B0.95
            ; Network
            M552 S1                                              ; enable network
            M586 P0 S1                                           ; enable HTTP
            M586 P1 S0                                           ; disable FTP
            M586 P2 S0                                           ; disable Telnet
            ; Drives
            M569 P0 S1                                           ; physical drive 0 goes forwards
            M569 P1 S0                                           ; physical drive 1 goes forwards
            M569 P2 S1                                           ; physical drive 2 goes forwards
            M569 P3 S1                                           ; physical drive 3 goes forwards
            M584 X0 Y1 Z2 E3                                     ; set drive mapping
            M350 X16 Y16 Z16 E16 I1                              ; configure microstepping with interpolation
            M92 X160.00 Y160.00 Z160.00 E832.48                  ; set steps per mm config smart effector
            M566 X300 Y300 Z300 E300
            M203 X18000.00 Y18000.00 Z18000.00 E1200.00          ; set maximum speeds (mm/min)
            M201 X1000.00 Y1000.00 Z1000.00 E1000.00             ; set accelerations (mm/s^2)
            M906 X1100 Y1100 Z1100 E800 I30                      ; set motor currents (mA) and motor idle factor in per cent
            M84 S30                                              ; Set idle timeout
            
            ; Axis Limits
            M208 Z0 S1                                           ; set minimum Z
            
            ; Endstops
            M574 X2 S1 P"xstop"                                  ; configure active-high endstop for high end on X via pin xstop
            M574 Y2 S1 P"ystop"                                  ; configure active-high endstop for high end on Y via pin ystop
            M574 Z2 S1 P"zstop"                                  ; configure active-high endstop for high end on Z via pin zstop
            
            ; Z-Probe
            M558 P8 R0.2 C"zprobe.in+zprobe.mod" H5 F1800 T10000 ; config smart effector
            G31 P500 X0 Y0 Z-0.30									; set Z probe trigger value, offset and trigger height (z-0.30)
            M556 S50 X0 Y0 Z0									; set orthogonal axis compensation parameters
            M557 R170 S20                                          ; define mesh grid
            G29 S1                                                  ; Load the heightmap
            
            ; Filament sensor 
            ;M591 D0 P2 C"e0stop" S1						 	     ; Set filament sensor
            
            ;Linear advance
            M572 D0 S0.2
            
            ; Heaters
            M308 S0 P"bedtemp" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin bedtemp
            M950 H0 C"bedheat" T0                                ; create bed heater output on bedheat and map it to sensor 0
            M307 H0 B0 R0.311 C292.2 D1.48 S1.00 V23.9           ; disable bang-bang mode for the bed heater and set PWM limit
            M140 H0                                              ; map heated bed to heater 0
            M143 H0 S120                                         ; set temperature limit for heater 0 to 120C
            M308 S1 P"e0temp" Y"thermistor" T100000 B4138        ; configure sensor 1 as thermistor on pin e0temp
            M950 H1 C"e0heat" T1                                 ; create nozzle heater output on e0heat and map it to sensor 1
            M307 H1 B0 R2.582 C251.0 D6.27 S1.00 V23.8           ; disable bang-bang mode for heater  and set PWM limit
            M143 H1 S280                                         ; set temperature limit for heater 1 to 280C
            
            ; Fans
            M950 F0 C"fan0" Q50                               ; create fan 0 on pin fan0 and set its frequency
            M106 P0 S0 H-1 C"Nozzle"                            ; set fan 0 value. Thermostatic control is turned off
            M950 F1 C"fan1" Q250                                ; create fan 1 on pin fan1 and set its frequency
            M106 P1 H1 S1 T45 C"head"                           ; set fan 1 value. Thermostatic control is turned on
            M950 F2 C"fan2" Q10
            M106 P2 S0.3 H-1 C"MB"
            
            ; Tools
            M563 P0 S"Nozzle" D0 H1 F0                           ; define tool 0
            G10 P0 X0 Y0 Z0                                      ; set tool 0 axis offsets
            G10 P0 R0 S0                                         ; set initial tool 0 active and standby temperatures to 0C
            
            ; Custom settings are not defined
            
            ; Miscellaneous
            T0
            M911 S22 R23.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
            M501
            Stephen6309undefined 1 Reply Last reply Reply Quote 0
            • sebxtremeundefined
              sebxtreme @Phaedrux
              last edited by sebxtreme

              @phaedrux

              ; called to perform automatic delta calibration via G ; bed.g
              ; called to perform automatic delta calibration via G32
              ;
              ; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Sep 30 2021 14:23:12 GMT+0200 (CEST)
              M561 ; clear any bed transform
              ; Probe the bed at 12 peripheral and 3 halfway points, and perform 9-factor auto compensation
              ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
              G30 P0 X0 Y169.9 H0 Z-99999
              G30 P1 X84.95 Y147.14 H0 Z-99999
              G30 P2 X147.14 Y84.95 H0 Z-99999
              G30 P3 X169.9 Y0 H0 Z-99999
              G30 P4 X147.14 Y-84.95 H0 Z-99999
              G30 P5 X84.95 Y-147.14 H0 Z-99999
              G30 P6 X0 Y-169.9 H0 Z-99999
              G30 P7 X-84.95 Y-147.14 H0 Z-99999
              G30 P8 X-147.14 Y-84.95 H0 Z-99999
              G30 P9 X-169.9 Y0 H0 Z-99999
              G30 P10 X-147.14 Y84.95 H0 Z-99999
              G30 P11 X-84.95 Y147.14 H0 Z-99999
              G30 P12 X0 Y84.9 H0 Z-99999
              G30 P13 X73.53 Y-42.45 H0 Z-99999
              G30 P14 X-73.53 Y-42.45 H0 Z-99999
              G30 P15 X0 Y0 H0 Z-99999 S6
              ; Use S-1 for measurements only, without calculations. Use S4 for 
              stop heights and Z-height only. Use S6 for full 6 factors
              ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
              G29
              1 Reply Last reply Reply Quote 0
              • sebxtremeundefined
                sebxtreme @Phaedrux
                last edited by

                @phaedrux
                prusa slicer start gcode

                G28 ; home all axes
                G1 Z5 F5000 ; lift nozzle
                G29 S1
                Phaedruxundefined 1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator @sebxtreme
                  last edited by

                  @sebxtreme said in removing a warning height map message:

                  @phaedrux
                  prusa slicer start gcode

                  G28 ; home all axes
                  G1 Z5 F5000 ; lift nozzle
                  G29 S1
                  

                  Well there you go. G28 will call home delta, which uses the tower endstops to set position. Then you load the heightmap which was created by the probe.

                  I suggest you add a single G30 after the G28 and before the G29 S1. That should get rid of the warning.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  sebxtremeundefined 1 Reply Last reply Reply Quote 1
                  • sebxtremeundefined
                    sebxtreme @Phaedrux
                    last edited by

                    @phaedrux you're right ! just trying now, and your solution remove my warning mess...
                    Many thanks for help 🙂

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

                      @sebxtreme said in removing a warning height map message:

                      @phaedrux you're right ! just trying now, and your solution remove my warning mess...
                      Many thanks for help 🙂

                      That single G30 sets what is called the Z=0 Datum. The practical result is, once set, moving to Z=0 should have the nozzle just touching the bed, or nearly so.

                      You needed to do that before creating heightmaps and before loading heightmaps.

                      That insures that the Z=0 position was consistent and accurate during creation and loading.

                      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
                      • Stephen6309undefined
                        Stephen6309 @sebxtreme
                        last edited by

                        @sebxtreme You have G29 S1 in config.g, remove it.

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

                          In theory, if your delta homed height is set perfectly, it should give the same Z0 result as the probe (assuming it's trigger offset is also set accurately), but it's far easier to just let the probe dictate the bed position.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          sebxtremeundefined 1 Reply Last reply Reply Quote 1
                          • sebxtremeundefined
                            sebxtreme @Phaedrux
                            last edited by sebxtreme

                            @phaedrux yes the G30 give the same height of my config each time . many thanks.

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