BIQU microprobe with Duet Maestro
-
Do you have a link to more information on this probe?
Can you share how you have it wired and how it's configured?
Share your homing files?
What firmware version? -
@yagodajm , I also replaced a BLTouch with a microprobe and ran into a lot of problems before I figured things out. The microprobe uses entirely different commands. Their web site has more info. I will look-see if I can find the details .....
OK, here are the files I changed:
Deployprobe.g:
; the following was for the BLTouch
;M280 P0 S10 ;S10 is the “angle” the PIN is put in to engage.When dealing with BLTouch the engaged position is at angle 10.; this for the BEQU Micro probe:
M42 P0 S1........................................................................................
part of my config.g with comments:
; when setting up different probes or end switches the following files (besides config.g) are affected:
; homez.g
; bed.g
; deployprobe.g
; retractprobe.g
; possibly any probing macros;==============================================
; set up BIQU micro probe
;==============================================;M950 P0 C"servo0" ; was BLTouch
M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 on expansion connector;M558 P9 C"^zprobe.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; was BLTouch
M558 P5 C"^!zprobe.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed,
; T= speed between probe points, A10 = probe up to 10 times
; R1.25 = allow settlement time, S0.008 = two consecutive probes need
; to be within 0.008 mm,
;M280 P0 S10 ; B1 = turn off heat for the actual probing
; B0 = leave heating on.....................................................................................................
retractprobe.g:
; the following was for the BLTouch
;M280 P0 S10 ;S10 is the “angle” the PIN is put in to engage.When dealing with BLTouch the engaged position is at angle 10.;P-number corresponds to our H-number while S defines the “angle” to put the probe into. When dealing with BLTouch the retracted position is at angle 90.
;M280 P0 S90
; this for the BEQU Micro probe:
M42 P0 S0................................................................................................
I looked at my bed.g and it didn't seem to be changed
I checked my homez.g and didn't notice any specific commands for the microprobeI can't guarantee that those are the only changes but it will get you going
-
@jens55 thanks, I have been scratching my head on this one. I will give these commands a shot. Thanks again.
-
@yagodajm we cover BTT microprobe installation for all the STM32 supported RRF boards here https://teamgloomy.github.io/fly_cdyv3_bltouch.html
The code is identical for all the boards and would also work on Duet boards too -
@jay_s_uk I followed these instructions and could not get it to work. I got so many errors, like probe not found, the probe would not deploy. I also tried what jens55 suggested and those did not work either. I ended up going back to the BLtouch. All of the settings for the BLtouch work for the Microtouch, just the pin does not sense the bed. I am just not sure what I am missing.
Here is the probe part of my config file
; Z-Probe M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch M558 P9 C"zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds ;M558 P9 H5 F250:30 T8000 C"^probe" ; set Z probe type to bltouch and the dive height + speeds ;M950 S0 C"Servo0" ; Setup Servo0 as servo port on Fly-CDYv3 G31 P500 X-35 Y0 Z2.922 ; set Z probe trigger value, offset and trigger height M557 X20:220 Y20:220 S20 ; define mesh grid
My deploy and retract file are already like you suggested, that is what I had for the BLTouch.
Thanks for all of your help,
Justin -
@yagodajm i was part of the beta testing for the microprobe and it doesn't work as a servo like the bltouch does.
and of course it won't work as you're using a pin name not used on your board. pins are different but code is the same -
@yagodajm, the problem is in your config.g file when you set up the microprobe. You are still setting up a servo pin and the microprobe uses an on/off type signal instead of a servo signal. Have a look at my config.g code posted earlier. In particular the two M950 lines below the 'set up BIQU micro probe'. The first line is commented out as that was for the BLTouch. The second line is what you need for the micro probe. I happen to be using a heater pin. The comment on that line is probably a bit misleading - you are creating a gpio pin (on/off) and not a servo pin.
Note the M558 line that follows - that gave me a bit of a problem as well. You should be using type 5 probe and note the "^!" bits .... these are important but may be different in your setup! -
@jens55 You are technically correct, the best kind of correct!
@yagodajm see the BIQU manual, page 25: https://github.com/bigtreetech/MicroProbe/blob/master/MicroProbe V2 User Manual_20231115.pdfM42 P0 S1; Probe deploy command
G4 P500; Allow 500 milliseconds for the probe to deploy
G29; probe the bed and enable compensation
M42 P0 S0; Probe stow commandThey use M42 rather than M280, and they have this in bed.g, but as @jens55 says, you can put the M42 command in the deployprobe.g and retractprobe.g. Also configure the probe as a BLTouch (M558 P9) rather than as a switch (M558 P5) and the deploy and retract will be automatic.
Also note that the V1 and V2 BIQU Microprobes have different configuration.
Ian
-
@jens55 Yes, I finally got it, the code was a little confusing, but I figured it out. I guess you were going off of a exp connector and I was not. So once I changed it to the pin to zprobe.mod, that fixed the issue. I got it to home and did a bed leveling.
Thank you all for your help. I wanted to use the microprobe since it is a little smaller.
Thanks again,
Justin -
@jens55 said in BIQU microprobe with Duet Maestro:
@yagodajm , I also replaced a BLTouch with a microprobe and ran into a lot of problems before I figured things out. The microprobe uses entirely different commands. Their web site has more info. I will look-see if I can find the details .....
OK, here are the files I changed:
Deployprobe.g:
; the following was for the BLTouch
;M280 P0 S10 ;S10 is the “angle” the PIN is put in to engage.When dealing with BLTouch the engaged position is at angle 10.; this for the BEQU Micro probe:
M42 P0 S1........................................................................................
part of my config.g with comments:
; when setting up different probes or end switches the following files (besides config.g) are affected:
; homez.g
; bed.g
; deployprobe.g
; retractprobe.g
; possibly any probing macros;==============================================
; set up BIQU micro probe
;==============================================;M950 P0 C"servo0" ; was BLTouch
M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 on expansion connector;M558 P9 C"^zprobe.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; was BLTouch
M558 P5 C"^!zprobe.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed,
; T= speed between probe points, A10 = probe up to 10 times
; R1.25 = allow settlement time, S0.008 = two consecutive probes need
; to be within 0.008 mm,
;M280 P0 S10 ; B1 = turn off heat for the actual probing
; B0 = leave heating on.....................................................................................................
retractprobe.g:
; the following was for the BLTouch
;M280 P0 S10 ;S10 is the “angle” the PIN is put in to engage.When dealing with BLTouch the engaged position is at angle 10.;P-number corresponds to our H-number while S defines the “angle” to put the probe into. When dealing with BLTouch the retracted position is at angle 90.
;M280 P0 S90
; this for the BEQU Micro probe:
M42 P0 S0................................................................................................
I looked at my bed.g and it didn't seem to be changed
I checked my homez.g and didn't notice any specific commands for the microprobeI can't guarantee that those are the only changes but it will get you going
Hey man,I recently posted issues myself with th same as OP I tried your code and it got me a little further but still having erratic issues.
Did you have any info on your code for the bed.g homez.g etc?
Thnk you!