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

    SOLVED: Multiple Dive Heights Possible?

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    4
    160
    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.
    • Fun King 3Dundefined
      Fun King 3D
      last edited by Fun King 3D

      So I am tweaking and tuning on the FK-1 and I have run into a problem that likely does not plague many people.

      I am using a Duet2Wifi and a Duex5 to allow auto tramming of the Z. I have my bed.g file running:

      M561 							; clear any bed transform
      G28                 			; home all axes
      G30 P0 X5 Y395 Z-99999			; probe near a leadscrew Left Rear
      G30 P1 X5 Y5 Z-99999 			; probe near a leadscrew Left Front
      G30 P2 X1180 Y5 Z-99999 		; probe near a leadscrew Right Front
      G30 P3 X1180 Y395 Z-99999 S4 	; probe near a leadscrew Right Rear and calibrate 4 motors
      G30 P0 X5 Y395 Z-99999			; probe near a leadscrew Left Rear
      G30 P1 X5 Y5 Z-99999 			; probe near a leadscrew Left Front
      G30 P2 X1180 Y5 Z-99999 		; probe near a leadscrew Right Front
      G30 P3 X1180 Y395 Z-99999 S4 	; probe near a leadscrew Right Rear and calibrate 4 motors
      G28                 			; home all axes
      G29  							; probe the bed and enable compensation
      

      This runs through the "Auto Bed Leveling" twice and adjusts the motors each time. (I may think about a third time, but for now is gets REALLY close.)

      Then it runs the G29 to map the bed for mesh bed leveling.

      My config.g contains:

      ; Z-Probe
      M950 S0 C"duex.pwm1"                           ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H10 F120 T6000           ; set Z probe type to bltouch and the dive height + speeds
      G31 P500 X-24.5 Y18.5 Z0.15                    ; set Z probe trigger value, offset and trigger height
      M557 X0:1150 Y50:400 S50                       ; define mesh grid
      

      Here lies my issue/question:

      As you can see in my M558, I use a dive height of 10mm. This is excessive, but necessary on a printer that is 1200mm wide as it is very easy to knock it out of level pretty extremely. When I had an H of 5, I would frequently get errors as out of range.

      As you can see from my M557, I have a "FEW" probe points for the mesh leveling. With a dive height of 10mm, it adds a significant amount of movement to the process.

      I am curious if there is a way to have a different dive height for each part. Example, could I call the M558 in my config.g as normal, but then call it again using an H5 between the last G30 and the G28/G29 and then call it again after to set it back to the H10 in case I level again without reboot?

      Hope this all makes sense. 🙂

      Thanks in advance.

      1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk
        last edited by

        Just run an M558 before each call.
        Eg

        M558 H5
        G28
        M558 H2
        G29
        

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        1 Reply Last reply Reply Quote 1
        • Fun King 3Dundefined
          Fun King 3D
          last edited by Fun King 3D

          That is what I was hoping to hear!

          So I only need the H parameter?

          EDIT: Worked like a champ! Thank you so much for the help.

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

            Same technique can be used for doing a fast probe first and then a slower one after.

            M558 F600 A1
            G30
            M558 F60 A10
            G30

            Z-Bot CoreXY Build | Thingiverse Profile

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