Bltouch Probing Question



  • So I setup my BLtouch per these instructions at this link. And it works fine for the most part. But I noticed everytime it probes when it lifts up it deploys and retracts an extra time as its lifting. So its moving the probe double for every time it probes. Why is it doing that.? Does it have anything to do with my deploy and retract macros I created?

    https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/

    ; bed.g
    ; called to perform automatic bed compensation via G32
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Fri Jun 14 2019 19:58:14 GMT-0700 (Pacific Daylight Time)
    M98 Pdeployprobe.g ; deploy mechanical Z probe
    M561 ; clear any bed transform
    G28 ; home all axes
    G29 ; probe the bed and enable compensation

    ; General preferences
    M111 S0 ; Debugging off
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves
    M555 P2 ; Set firmware compatibility to look like Marlin
    M208 X0 Y0 Z0 S1 ; sets the minimum values for all axes
    M208 X300 Y300 Z400 S0 ; sets the maximum values for all axes

    ; Endstops
    M574 X1 Y1 S1 ; X home to min. Y home to min. Normally Closed limit switches.
    M574 Z1 S2 ; Define Z to use Probe. Home to Min
    M558 P9 H7 F200 T4000 X0 Y0 Z1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed the bed moves
    G31 P25 X-38 Y-8 Z1.58 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment
    M557 X20:280 Y20:280 S20 ; Define mesh grid

    ; Drives
    M569 P0 S0 ; Drive 0 goes backwards
    M569 P1 S0 ; Drive 1 goes backwards
    M569 P2 S0 ; Drive 2 goes forwards
    M569 P3 S0 ; Drive 3 goes backwards
    M350 X16 Y16 Z16 E32 I1 ; Configure microstepping with interpolation
    M92 X80 Y80 Z400 E202.2 ; Set steps per mm
    M566 X1200 Y1200 Z24 E300 ; Set maximum instantaneous speed changes (mm/min)
    M203 X30000 Y30000 Z600 E5000 ; Set maximum speeds (mm/min)
    M201 X500 Y500 Z100 E5000 ; Set accelerations (mm/s^2)
    M906 X800 Y800 Z700 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Heaters
    M143 S265 ; Set maximum heater temperature to 265C
    M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
    M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1

    ; BLTouch - Heaters
    M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board

    ; Tools
    M563 P0 D0 H1 ; 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

    ; Network
    M550 PCR10SDuet ; Set machine name
    M552 S1 ; Enable network
    M586 P0 S1 ; Enable HTTP
    M586 P1 S0 ; Disable FTP
    M586 P2 S0 ; Disable Telnet

    ; Fans
    M106 P0 S1 I0 F500 H1 T50 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P1 S0 I0 F30 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off - have 2 Blowers parallel
    M106 P2 S0.5 I0 F30 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off - have 2 Case Fans parallel

    ; Custom settings
    M912 P0 S-13 ; calibrate MCU Temp

    ; Miscellaneous
    M501 ; with PID Tune data
    T0 ; Select first tool

    ; homeall.g
    ; called to home all axes
    ;
    ; generated by RepRapFirmware Configuration Tool on Sat Oct 28 2017 00:02:03 GMT+0200 (Mitteleuropäische Sommerzeit)

    ; Relative positioning
    G91

    ; Course home X and Y
    G1 X-305 Y-305 F3600 S1

    ; Fine home X and Y
    G1 X-305 Y-305 F3000 S1

    ; Move away from the endstops
    G1 X150 Y150 F3000

    G30 ; Do a single probe

    ; Homez.g
    ; Move away from the endstops
    G1 X150 Y150 F6000
    G30 ; Do a single probe to home our Z axis
    G91
    G1 Z20 F3000 ; Rapidly move the Z axis to Z=20



  • @57buick said in Bltouch Probing Question:

    M98 Pdeployprobe.g ; deploy mechanical Z probe

    Remove that from bed.g. The firmware will handle the deployment as needed.

    M558 P9 H7 F200 T4000 X0 Y0 Z1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed the bed moves

    Remove the X0 Y0 Z1 part. It's not used anymore. The M574 Z1 S2 command already sets the Z stop as the probe.

    The rest of your config looks ok for BLTouch settings.

    You haven't posted your deploy and retract macros, but if it's working to home the printer that would indicate that it is working.

    Does the double probing you describe also apply to homing?

    What firmware version are you using?

    What version of BLTouch is it?



  • Im using version 2.0(RTOS) (2018-06-05b3) for my firmware.

    It does it anytime the probe is used whether im just homing Z or doing a bed mesh or whatever it doesnt matter. Like when I run an auto bed mesh you will hear it click 4 times for every probe. It will deploy, move down until it detects the bed and retract then quickly deploy and retract again as its lifting to move the next probe point.

    I was at first using a 3dtouch clone then I swapped it out for a genuine V2.1 BLtouch and it acts exactly the same way.

    I just started a 30 hour print, when that finishes I'll go and delete those lines you mentioned and see if it has any affect, thanks


  • administrators

    The M98 command in your bed.g file may be causing this.



  • I just edited both those files and rebooted but it is the same. Removed the M98 command in bed.g and removed the X0 Y0 Z1 from the M558 command



  • @dc42 said in Bltouch Probing Question:

    The M98 command in your bed.g file may be causing this.

    Any other ideas? Im using a genuine bltouch now and I've deleted the M98 command as well as the X0 Y0 Z1 from the M558 command but it still does the same thing



  • What is in your deploy and retract files?



  • deployprobe.g is just one line M280 P7 S10 I1
    retractprobe.g is M280 P3 S90 I1



  • @57buick said in Bltouch Probing Question:

    Im using version 2.0

    That firmware version is fairly out of date at this point. There have been some BLTouch changes since then.

    Try updating to version 2.03 by going to the settings tab and uploading this zip file: https://github.com/dc42/RepRapFirmware/releases/download/2.03/Duet2Firmware-2.03.zip

    Full release notes here: https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md



  • @phaedrux said in Bltouch Probing Question:

    @57buick said in Bltouch Probing Question:

    Im using version 2.0

    That firmware version is fairly out of date at this point. There have been some BLTouch changes since then.

    Try updating to version 2.03 by going to the settings tab and uploading this zip file: https://github.com/dc42/RepRapFirmware/releases/download/2.03/Duet2Firmware-2.03.zip

    Full release notes here: https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md

    Awesome! I just updated and everything seems to be working properly, thanks. One question I dont see on the pages anywere that specify what is the latest version of wifi server and web interface etc. Are these all the latest versions?

    Firmware Version: 2.03 (2019-06-13b2)
    WiFi Server Version: 1.23
    Web Interface Version: 1.22.6


  • administrators

    Yes those are latest stable versions. There is also a beta of DWC 2.0 for those who want to try it.



  • @57buick By uploading that single combined zip file all the relevant firmwares, etc get updated.



  • Awesome thank you guys! I am ordering two more Duet boards for my Folgertech FT5 printers so I will make sure and install that file to those too



  • Note that that single file upload process only works with boards that are already running firmware 2.0 to begin with. If it's an older firmware you'd need to update the individual files first to at least 2.0



  • @phaedrux said in Bltouch Probing Question:

    Note that that single file upload process only works with boards that are already running firmware 2.0 to begin with. If it's an older firmware you'd need to update the individual files first to at least 2.0

    good to know


Log in to reply