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

BL-Touch - Multiple Probes?

Scheduled Pinned Locked Moved Solved
Tuning and tweaking
3
8
538
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
    zemlin
    last edited by zemlin 28 Mar 2022, 23:00

    My BL-Touch is working fine, but I see a little bit of variability in the apparent Z-Height across the bed, so I thought maybe multiple probes would provide a more consistent result.

    I tried adding an A3 and S-1 parameter to my M558 in the config.g, but it still only pokes once. I thought that would poke three times and average the readings. I also added two speeds to the F parameter so the second poke would be slower. What am I missing?

    M558 P9 C"^zprobe.in" H2 F60:30 T24000 A3 S-1      ; set Z probe type to bltouch and the dive height + speeds
    G31 P25 X12.5 Y51.05 Z4.5                          ; set Z probe trigger value, offset and trigger height
    M557 X25:275 Y50:300 S50 
    
    1 Reply Last reply Reply Quote 1
    • undefined
      Phaedrux Moderator
      last edited by 29 Mar 2022, 05:56

      What firmware version?

      Perhaps part of the problem is that our trigger height is 4.5mm but the dive height is only 2mm.

      4.5mm seems very high for a bltouch. The Bltouch documentation says the probe should be mounted so that the probe body is ~8mm above the nozzle tip, which should result in a trigger height of ~2mm.

      Regardless, your dive height should be equal to or greater than the trigger height.

      Also, for best results with multiple probes with the BLtouch you should try leaving the S value off entirely to leave the default tolerance, and just use a larger value for A. Then it will probe at least twice until two results are within tolerance up to A# of times. Averaging the values should only be used if your probe is truly giving inconsistent results. In which case, something is wrong with the BLTouch.

      Z-Bot CoreXY Build | Thingiverse Profile

      undefined undefined 3 Replies Last reply 29 Mar 2022, 11:32 Reply Quote 0
      • undefined
        zemlin @Phaedrux
        last edited by zemlin 29 Mar 2022, 11:32

        RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)

        It's been a couple years since I set this up, and looking at the CAD models of the print head and bracket I recall the sensor model I downloaded didn't quite match the actual sensor, but I will look into that and see if I need to adjust my bracket.

        Initially I did just add the A option, and it did not double-dip with that alone.

        undefined 1 Reply Last reply 29 Mar 2022, 18:16 Reply Quote 0
        • undefined
          Phaedrux Moderator @zemlin
          last edited by 29 Mar 2022, 18:16

          @zemlin said in BL-Touch - Multiple Probes?:

          Initially I did just add the A option, and it did not double-dip with that alone.

          Well I wonder if that's related to the dive height being lower than the trigger height.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • undefined
            dc42 administrators @Phaedrux
            last edited by 19 Apr 2022, 11:19

            @phaedrux said in BL-Touch - Multiple Probes?:

            Regardless, your dive height should be equal to or greater than the trigger height.

            Actually, that's not necessary. The actual starting height is calculated by adding the trigger height to the configured dive height.

            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 1
            • undefined
              zemlin @Phaedrux
              last edited by 6 Jul 2022, 14:18

              @phaedrux - I finally got around to modifying my sensor bracket so the height relative to the nozzle is the correct 8mm and adjusted trigger height and dive height accordingly.

              The A option on M558 still does not result in repeat probes.

              ; Z-Probe
              M950 S0 C"exp.heater3"                             ; create servo pin 0 for BLTouch
              M558 P9 C"^zprobe.in" H2 F20 T24000 A2          ; set Z probe type to bltouch and the dive height + speeds
              G31 P25 X12.5 Y51.05 Z2                            ; set Z probe trigger value, offset and trigger height
              M557 X25:275 Y50:300 S50 						   ; define mesh grid
              M307 H3 A-1 C-1 D-1  
              
              
              1 Reply Last reply Reply Quote 0
              • undefined
                Phaedrux Moderator
                last edited by 6 Jul 2022, 17:03

                What happens if you leave off the S parameter and set A10?

                @zemlin said in BL-Touch - Multiple Probes?:

                M307 H3 A-1 C-1 D-1

                Also remove that line entirely as it's no longer valid in RRF3.

                Can you share your full config.g and homing files? Bed.g as well if it's used? It feels like something is getting altered somewhere that we're just not seeing.

                Z-Bot CoreXY Build | Thingiverse Profile

                undefined 1 Reply Last reply 8 Jul 2022, 23:42 Reply Quote 0
                • undefined
                  zemlin @Phaedrux
                  last edited by zemlin 7 Sept 2022, 18:43 8 Jul 2022, 23:42

                  @phaedrux
                  Good call - Homing has an A1. Will change that. Thanks.

                  update: Editing the M588 command in the homeall and homez files resolved the issue. Thanks.

                  1 Reply Last reply Reply Quote 2
                  • undefined Phaedrux marked this topic as a question 10 Jul 2022, 20:05
                  • undefined Phaedrux has marked this topic as solved 10 Jul 2022, 20:05
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA