BLTouch V3.0 Reassemble
-
@jaurand said in BLTouch V3.0 Reassemble:
Also do I enable 5V logic in the config.g file?
no this is not necessary.
you are missing the deploy and retract scripts.
-
@Veti
So then I would just create all these scripts minus the 5V logic right? I had a previous thread where it was mentioned I did not need the deploy and retract with the newer setup
-
@jaurand said in BLTouch V3.0 Reassemble:
I had a previous thread where it was mentioned I did not need the deploy and retract with the newer setup
you do not need to call the deploy macro anymore, but the macro has to exist nonthless.
the duet does not know which pin the bltouch is connected to, that information only exists in those scripts.
-
I just made macros for all items other than 5V logic zmin.
Do i also need to include these in the config.g file? ie M280 P7 S150 I1, M280 P7 S120 I1 and so on?
-
@jaurand said in BLTouch V3.0 Reassemble:
M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
That betrue3d guide is a little out of date. The BLTouch has its own sensor type now, so instead of M558 P5 you should use M558 P9.
The info here should be up to date. https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
-
@Phaedrux said in BLTouch V3.0 Reassemble:
@jaurand said in BLTouch V3.0 Reassemble:
M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
That betrue3d guide is a little out of date. The BLTouch has its own sensor type now, so instead of M558 P5 you should use M558 P9.
The info here should be up to date. https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
Yep I did catch that and is setup as P9 in my config file.
-
@jaurand said in BLTouch V3.0 Reassemble:
Do I need to add the following BLTouch instructions to the config.g code? (Push-pin down, alarm release, self test, etc)
It may be a good idea to include the alarm release and pin retract commands in the config.g so that they get executed at startup. Just in case the BLTouch is too close to something at startup and the pin contacts something during the power on test and goes into an alarm state. If you try to home the printer while it's alarmed you could end up with a bed crash. It's not a bad idea to put them into the beginning of homeall.g as well.
-
@Phaedrux does M280 P7 S150 I1 need to go anywhere? or does bltouch do this already without any additional input?
-
You don't need to use that command for the Duet.
-
https://photos.app.goo.gl/syd2vYXHDURhdonS9
So everything works but the BLTouch blinks red with pin up. Am I missing something?
-
It looks like it doesn't have a pin. That's probably throwing it's detection circuit for a loop.
-
@Phaedrux yea the pin should be in tomorrow, as it broke in during a print. I'll report back once that is installed.
-
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?
-
@jaurand said in BLTouch V3.0 Reassemble:
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
-
@jaurand said in BLTouch V3.0 Reassemble:
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?
Please have a short look at the documentation: here and here.
-
@infiniteloop Well I can run M401 and M402 and the pin extends and retracts....so not sure what to say but it does work
