BLTouch V3.0 Reassemble
I suspect that if you send the alarm release command it would stop blinking, but I'm not sure how it will behave with no pin there for the hall effect sensor to trigger with.
New pin installed. At start up still blinks, even with putting M280 P7 S160 I1 in the config.g file. When I run M280 P7 S160 I1 macro, BLTouch still blinks red, but when I initiate Alarm Release & Touch SW " M280 P7 S60 I1" blinking stops but z-probe indicates 1000, with pin retracted.
I'm confused. So it's working now, or not working?
Veti last edited by
New pin installed. At start up still blinks,
when the printer start the bltouch does a self test. if it blinks it says there is a problem. maybe the new pin is not working.
The set screw on the top of the body needs to be adjusted somewhat for best operation. Try giving it a turn in either direction.
Moved scripts around. Originally I had them under the heading ;bltouch in the config.g, bit then moved them under endstops. Also made a separate folder for the deploy and retract macros, labeled bltouch.
At startup bltouch does not perform self-test, however it was not doing that before anyways,but is no longer blinking.
Interesting to see that location of code effected this
infiniteloop last edited by
Also made a separate folder for the deploy and retract macros, labeled bltouch.
Perhaps not the best idea of the day: M401 and M402 call these macros but won’t find them - neither in your config.g nor in the folder „bltouch“. How should they know?
@infiniteloop Well I can run M401 and M402 and the pin extends and retracts....so not sure what to say but it does work
infiniteloop last edited by
Well I can run M401 and M402 and the pin extends and retracts…
In this case, you must have left additional copies of deployprobe.g and retractprobe.g in the sys/ directory - just where they belong. Remove the folder „bltouch“ - M401 and M402 should still work.
@infiniteloop i misunderstood, I have a set of macros for deploy and retract labeled bltouch. looking under system editor, deployprobe.g and retractprobe.g are in the sys/ directory
still confused why the bltouch is not performing the self test at start up. other than that it appears to be operating correctly
luc last edited by
I say mine, maybe it has been tried but you never know.
If with the machine off you pull out the pin and then turn it on, does the Bltouch work? Yes?
If yes, make the extension wiring new from scratch ... I change wires I used the Cat5 ones for network cables and above all crimp the terminals well (and with the pliers).
If with the machine off you pull out the pin and then turn it on, does the Bltouch work?
The BLTouch works, just does not perform the default self test when it printer is turned on
Do you have the alarm release at the start of config.g?
jaurand last edited by jaurand
@Phaedrux I've got it right under general preferences
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
; generated by RepRapFirmware Configuration Tool v2 on Sun Mar 17 2019 11:31:51 GMT-0400 (Eastern Daylight Time)
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M575 P1 B38400 S1 ; Baudrate for Paneldue 38400
M667 S1 ; Select CoreXY mode
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5
M280 P7 S160 I1 ; Alarm Release and Push pin Up
When I power it up the BLTouch will blink its read, but running Alarm Release and Push Pin Up (M280 P7 S160 I1) results in no change.
Only running Alarm Release & Touch SW Mode (M280 P7 S60 I1) stops the blinking, but then I have to run Push Pin Up (M280 P7 S90) so that it works correctly after.
Maybe move alarm release to the end of config. G to give it time to finish the self test.
@Phaedrux But the BLTouch is not even doing the self test
Well new problems creeping up. Pin will not retract at start of print but print starts regardless.
I'm going to try a fresh install of firmware and start that from scratch to ensure updating did not cause any issues. What is the best method for this?
@jaurand Upload the firmware on the system tab of DWC and it should update automatically.
@Phaedrux that is how i've been updating firmware before. My thought is something did not stick right causing my issues. Hence why delete it all and start from a fresh build is my thought