BLTouch Not Working After Firmware Update to 3.4
-
Please try uploading the 3.4 zip file as is to the system tab in DWC to make sure all files are up to date.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.0/Duet2and3Firmware-3.4.0.zip
It's strange that M401/M402 will work to deploy but G30 won't.
Can you post your homing files and deploy/retract macros please?
-
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:08 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-475 Y605 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y-5 F6000 ; go back a few mm G1 H1 X-475 Y605 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 H2 Z5 F6000 ; lift Z relative to current position - we are about to move X and Y and we want to be sure the nozzle is clear of the bed. G90 G1 X222 Y500 F6000 ; move the probe to the center of the bed - for aaa, bbb, ccc use values suitable for your printer G30 ; probe the bed and set the logical position of Z thus homing the Z axis ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:08 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-475 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F6000 ; go back a few mm G1 H1 X-475 F360 ; move slowly to X axis endstop once more (second pass) ;G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioning
; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:08 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 Y605 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y-5 F6000 ; go back a few mm G1 H1 Y605 F360 ; move slowly to Y axis endstop once more (second pass) ;G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioning
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:08 GMT-0700 (Pacific Daylight Time) ;G90 ; relative positioning ;G1 Z5 F6000 ; lift Z relative to current position G90 G1 X222 Y500 F6000 ; go to first probe point G30 ;G1 H1 Z-305 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing G91 ; relative positioning G1 Z5 F100 ; lift Z relative to current position G90 ; absolute positioning
; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:07 GMT-0700 (Pacific Daylight Time) M280 P0 S90 ; retract BLTouch
; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:07 GMT-0700 (Pacific Daylight Time) M280 P0 S10 ; deploy BLTouch
-
@Phaedrux Is it ok to run?
-
Ok so uploaded the zip and performed the update. At this moment the problem still persists
-
Unrelated to your problem, but
@alecsanchez said in BLTouch Not Working After Firmware Update to 3.4:
G30 ;G1 H1 Z-305 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
In your homez you have a G92 Z0 after the G30 to force the z position to 0. This is not likely what you intend to happen when using the probe as it would ignore the probe offset. Remove that G92 Z0.
When you updated to 3.4 did you use sudo apt update and sudo apt upgrade on the Pi?
I don't see anything incorrect in your config, other than lacking a measured XYZ probe offset in G31.
Do you get any error messages when you send G30 by itself?
-
@Phaedrux Yes I did use sudo update and sudo apt upgrade. G30 also doesn't give me any error messages
-
Is the pin perhaps sticking? You say it drops when you do an emergency stop.
-
It doesn't seem like it, I can send m401/m402 successively many times and it doesn't stick. How it deploys when I emergency stop is very odd though. This never occurred before
-
I confirmed that bltouch still triggers and stops the bed if I deploy it and then send G30. I'm just not sure what is preventing it from deploying when I send g30
-
As a test can you add the M401 deploy command before the G30 in your homing macros and see if it behaves then? If it does work, does it retract afterwards?
-
@Phaedrux I added M401 to the homez.g macro and it did not deploy
-
Where did you add it?
-
Right before G30
-
Try adding a M400 between, like this.
G1 X Y positioning move
M400
M401
M400
G30 -
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Apr 06 2022 16:00:08 GMT-0700 (Pacific Daylight Time) ;G90 ; relative positioning ;G1 Z5 F6000 ; lift Z relative to current position G90 M401 G1 X222 Y500 F6000 ; go to first probe point G30 ;G1 H1 Z-305 F1800 ; move Z down until the endstop is triggered ;G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing G91 ; relative positioning G1 Z5 F100 ; lift Z relative to current position G90 ; absolute positioning
I added it here now and it did deploy, but it did not retract after I triggered it with my finger. However it did stop the bed. M401/M402 commands did not work after this
-
@phaedrux The M400 commands did not appear to work, bltouch did not deploy
-
Does M401 and M402 work manually and repeatedly when the print head is in the probing position? Perhaps it's a loose cable when in certain locations.
-
@Phaedrux I found something interesting about this situation, sorry for the late reply. So if the y axis is homed and the y endstop is triggered, the probe will deploy and retract normally. But if I home the z axis in a location thats not at y-min, it wont deploy since the y endstop isn't triggered. However if I manually trigger the y endstop while in the process of homing z, the probe will deploy. Very odd
-
What relation does your Y axis endstop wiring have with the BLtouch wiring? Are they co-located possibly causing interference? Or a short?
-
y-endstop is on io1, bltouch is on io4. They are right above eachother on the board, but the wires are not run through the same path if that makes sense