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

    Gcode for test BlTouch

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    23
    13.8k
    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.
    • peirofundefined
      peirof
      last edited by

      Lets thinking….

      if it was working correctly, what should the printer do?

      1- Homing
      2- The Nozzle goes down to find the bed, at a speed T600 (in this case)
      3- When BlTouch touches the bed, the Nozzle stops going down, and goes up. How much does it rise?
      4- It moves horizontally to the next point defined in bed.g.
      5- Go back down, until the BlTouch plays ....
      and this process for all points in bed.g ....

      It would be like this?
      which can cause the head to NOT stop going down when the BlTouch is playing? Assuming it is working, since the G30 S-1 command works

      Is there any other way to prove that the BlTouch works?
      There was not a form of relative movement, which stopped when the BlTouch (ZProbe) was activated ???

      1 Reply Last reply Reply Quote 0
      • Scachiundefined
        Scachi
        last edited by

        Maybe this helps you.
        This are my config.g lines for bltouch

        [[language]]
        
        M307 H7 A-1 C-1 D-1 ; disable heater7 free it up for pwm control for bltouch
        
        M558 P5 X0 Y0 Z1 H3 F100 T500; Set Z Probe to type Switch or Digital output where Z probe connector is used. Used for z only. ; bltouch
        
        G31 P25 X0 Y-15 Z1.00 ; Set Z probe trigger value, offset and trigger height - bltouch
        
        M557 X5:205 Y5:205 S20 ; Define mesh grid
        M376 H3.0 ; taper of height compensation above this mm value
        
        

        This is my home.z:

        [[language]]
        ; Lift Z relatively to current position
        G91
        G1 Z5 F1000
        
        ; Back to absolute positioning - mid of bed
        G90
        G1 X105 Y120 F3000
        
        ; Move Z down until the switch triggers
        G30
        
        ; Uncomment the following lines to lift Z after probing
        ;G91
        G1 Z5 F100
        ;G90
        
        
        1 Reply Last reply Reply Quote 0
        • peirofundefined
          peirof
          last edited by

          @Scachi:

          Maybe this helps you.
          This are my config.g lines for bltouch

          [[language]]
          
          M307 H7 A-1 C-1 D-1 ; disable heater7 free it up for pwm control for bltouch
          
          M558 P5 X0 Y0 Z1 H3 F100 T500; Set Z Probe to type Switch or Digital output where Z probe connector is used. Used for z only. ; bltouch
          
          G31 P25 X0 Y-15 Z1.00 ; Set Z probe trigger value, offset and trigger height - bltouch
          
          M557 X5:205 Y5:205 S20 ; Define mesh grid
          M376 H3.0 ; taper of height compensation above this mm value
          
          

          This is my home.z:

          [[language]]
          ; Lift Z relatively to current position
          G91
          G1 Z5 F1000
          
          ; Back to absolute positioning - mid of bed
          G90
          G1 X105 Y120 F3000
          
          ; Move Z down until the switch triggers
          G30
          
          ; Uncomment the following lines to lift Z after probing
          ;G91
          G1 Z5 F100
          ;G90
          
          

          Thanks, later try, now i am not in home, and give feedback

          1 Reply Last reply Reply Quote 0
          • peirofundefined
            peirof
            last edited by

            Sachin, one question of your config…

            You have in config.g, this line

            [[language]]
            M558 P5 X0 Y0 Z1 H3 F100 T500;
            
            

            Z… Is the distance between, nozzle and Bltouch... When is deployed? No, in your config... You have Bltouch deployed under nozzle 1mm. No?

            1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators
              last edited by

              In firmware 1.19 and earlier, Z1 in the M558 just means that the Z probe is used in lieu of a Z endstop switch. In firmware 1.20 and later it is ignored, because that option is set in M574 instead. But in fact it isn't necessary to tell the firmware to substitute the Z probe for the Z endstop switch at all, assuming you set up your homing files correctly to use G30 to do Z homing.

              The Z probe trigger height is set in the G31 command.

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              1 Reply Last reply Reply Quote 0
              • peirofundefined
                peirof
                last edited by

                I have installed firmware 1.20….

                Whats the correct configuration.g?

                Someone using Bltouch, and firmware 1.20, can post his working configuration?

                1 Reply Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators
                  last edited by

                  The configuration that Scachi posted should work with 1.20 too.

                  Duet WiFi hardware designer and firmware engineer
                  Please do not ask me for Duet support via PM or email, use the forum
                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                  1 Reply Last reply Reply Quote 0
                  • peirofundefined
                    peirof
                    last edited by

                    I suspect that the problem may be in the file bed.g, which makes me think that:

                    A- The BlTouch sensor, now, seems to work correctly, when I turn on the printer it does the initial test
                    B- If you send the gcode G30 S-1 via a console, it seems to execute it well.

                    So….

                    When by DWI, you send the autocalibrate order ... it is supposed to make the orders contained in bed.g. Do not?
                    When you send the order to use the mesh compensation ... It does not depend on what you put in bed.g, but on order M557 in config.g. DO NOT?

                    Someone, that have a Delta and uses BlTouch, can post his [c]bed.g[/c]

                    1 Reply Last reply Reply Quote 0
                    • peirofundefined
                      peirof
                      last edited by

                      News….

                      I try to make a [c]bedcompesation[/c], and partial works, with the next behavoir:

                      1- Nozzle go down, a bit slow, but go down….
                      2- With Nozzle is near bed, aprox 30 mm, slow, VERY SLOW.
                      3- With BlTouch, reach bed... MAGIC, WORKS. Retract, and Nozzle go up.
                      4- Go to the next point... and here start the problems, de BlTouch, NO re Deploy.

                      Why?

                      And why bed compenstation works, or semi works, and calibration NO works, nothing?

                      Ideas?

                      1 Reply Last reply Reply Quote 0
                      • peirofundefined
                        peirof
                        last edited by

                        eeee…..

                        i think i have it.... not sure.

                        Dc42.... if someone, has put the files deployprobe.g and retractprobe.g.... in dir [c]\macro[/c]…. maybe.... and only maybe, can be the cause of behavoir descrived in previous post?

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