Klipper probe config for the BIQU Microprobe (V1/V2)

biqu_microprobe.cfg

## --- BIQU Microprobe Klipper configuration ---
# Not much different from a standard probe config. The
# main difference compared to most probes is to disable
# deactivating the probe (PROBE_UP) after each sample
#
# You can either copy pasta this directly or import
# into your config.yml using [include microprobe.cfg]
#
# Note: if you are changing from a bltouch or one of its
# clones, remove/comment out the [bltouch] config!
# That also includes any auto generated config stored
# at the bottom by the PROBE_CALIBRATE command
#
# Note: the current control and sensor pin values are
# configured for the 'BTT SKR E3 mini V2' controller 
# board. You may need to update these values depending
# on your controller board model.
#
# Update (2023-10-17): This config is configured for
# the V1 microprobe. V2 users must update the 
# polarity of the sensor pin in the config to be 
# pull-down (^!) not pull up (^)

[gcode_macro PROBE_DOWN]
gcode:
    SET_PIN PIN=probe_enable VALUE=1

[gcode_macro PROBE_UP]
gcode:
    SET_PIN PIN=probe_enable VALUE=0

[output_pin probe_enable]
pin: PA1  # Set to the control pin on your board
value: 0

[probe]
pin: ^PC14  # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger 
deactivate_on_each_sample: False
x_offset: -40
y_offset: -35
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
    PROBE_DOWN
    G4 P500
deactivate_gcode:
    PROBE_UP

This was a big help. Thank you

This was a big help. Thank you

No worries! 👍

its doesnt work at me. my toolhead crashed everytime into to bed. in need to cry

@digitalBulldog My guess is that you have the wrong pin ID configured for your sensor pin. In my config its PC14 but depending on what control board your printer is using that value will be different.

As written in the title, I use the SKR mini E3 V3 board and have all the pins, including the connector mentioned. However, the pin extends and does not trigger when it comes into contact with the bed. I had to! in front of PC14, otherwise it will pull in the pin when approaching Z. Sometimes the message comes that the Z_Probe is switched.

I use all pins as indicated on the pinout here.

Do you have a V1 or V2 microprobe? This config is for a V1 microprobe (I made it before V2 existed).

After doing some research, it appears the the V2 probe requires reversing the polarity of the sensor pin (i.e. set ^!PC14).

so far the Zprobe works too, retracts and retracts via the macro after I have set !pc14. However, with z_homing, the z stepper does not stop once the pin makes contact with the bed. I do not know why. I also know which model I have, it is not on the packaging! 😭

Maybe add a pull up resistor as well (^!PC14)? The sensor pin could be floating and not correctly registering contact with the bed?

i will testing tomorrow, i need to go sleep, thank you, i think i forgot the ^ in front of !PC14, i has only write vom PC14 to !PC14...i will get testing tommorow, thank you utlandr

I also cut off the pins today and checked the cables for continuity. no cable break. That's why I'll crimp the plugs again tomorrow and then I'll go back to the config. I just had to work on static calculations for another 5 hours and I'm done for today. I thank you....

Well this probe (V2) is leading me a merry dance!
The printer is an Artillery Genius to which I have fitted a Manta M4P v1.0 and have set up the MicroProbe in the printer.cfg exactly the same as the first post on here.

I get this on start up -

Klipper reports: ERROR

Option 'set_pin pin' is not valid in section 'gcode_macro probe_deploy'

The probe deploys and retracts on power up, But does not deploy when trying to home Z.

@PaulStep61 Try setting ^!PC14 (assuming that is your sensor pin for that board). Also:

Option 'set_pin pin' is not valid in section 'gcode_macro probe_deploy'

My config at the top doesn't have a probe_deploy macro.

Okay,
I have removed the probe_deploy and probe_stow macros.
I now have this:
[gcode_macro PROBE_DOWN]
gcode:
SET_PIN PIN=probe_enable VALUE=1

[gcode_macro PROBE_UP]
gcode:
SET_PIN PIN=probe_enable VALUE=0

[output_pin probe_enable]
pin: !PA1 # Set to the control pin on your board
value: 0

[probe]
pin: ^!PC14 # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger
deactivate_on_each_sample: False
x_offset: 44
y_offset: 44
z_offset: 5 # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
samples_tolerance: 0.05
samples_tolerance_retries: 3
activate_gcode:
PROBE_DOWN
G4 P500
deactivate_gcode:
PROBE_UP

When I power up the printer the probe deploys and retracts 3 times and then deploys ready for Z homing.
When I home Z there is no reaction to the probe making contact with the bed and retracting.

pin: !PA1 # Set to the control pin on your board

That should be PA1. ! inverts the signal of the control pin (VALUE=0 now means extend, and VALUE=1 means retract). This will invert the logic of your macros and the default setting.

The 3 deploy/retracts happen on power up of the probe and cannot be influenced by the control pin. The reason your probe immediately extends afterwards is because your default setting for the control pin is value: 0 but inverted, which means extend.

When I home Z there is no reaction to the probe making contact with the bed and retracting.

You should expect the probe to stay extended when it contacts the bed. The microprobe does not work the same way as a bltouch. In this video you can see the probe touch the bed but doesn't retract. Retracting it actually deactivates the sensor which is why the deactivate_on_each_sample: False is set.

I've tried many things but alas no success.
I even tried installing a BL Touch clone - at first it was in alarm mode (fast flashes red) I inverted the control pin and now its constant red.
I've connected both probes to the M4P as per the manual, the cables are good.

Thank you for the file and explanation!

I also know which model I have, it is not on the packaging! 😭

I also couldn't find a version on the packaging, but there might be a version written on the back of the sensor above the connector. My one states: MicroProbe V2.

I have a M8P V1.1 board and some trouble with this microprobe (maybe V2). Trying the BLTouch installation has no success and after a while i am landing here. It was a big step in the right direction. But i had always „still triggered“ errors. One of my tries with „!“ and the „^“ was to remove the pull up from PC14 - and it works now without an error - better to write PB2 -

The correct command is instead of PC14 !PB2 for the manta m8p without pull up.

After doing a manual test again - i failed. So i tested again and again. Every time i have „still triggered after rectract“. My fault was to simulate the nearing heatbed i took something flat to trigger the microprobe. I forgot that the stepper makes a small movement back and forward after - and I relay don‘t how sensitiv this probe is. I tested again with a little touch and a second after a very short time and my test was successful.

Ok in summery .. instead of ^PC14 the very very correct command is: pin: ^!PB2 for the Manta M8P

Thank you for this thread - it was a great help for me :)

Ok in summery .. instead of ^PC14 the very very correct command is: pin: ^!PB2 for the Manta M8P

Thank you for this thread - it was a great help for me :)

No worries! Glad you got it all sorted. I'll revise the config to include a note about different controller boards. ^PC14 works for my BTT SKR Mini E3 V2 (and probably a bunch of other BTT boards), but in a lot of cases this value will be different.

J'ai une carte M8P V1.1 et quelques soucis avec cette microsonde (peut-être V2). Essayer l’installation de BLTouch n’a pas réussi et après un moment j’atterris ici. C'était un grand pas dans la bonne direction. Mais j'avais toujours "encore déclenché" des erreurs. Un de mes essais avec "!" et le "^" était de supprimer le pull up du PC14 - et cela fonctionne maintenant sans erreur - mieux vaut écrire PB2 -

La commande correcte est au lieu de PC14 !PB2 pour le manta m8p sans pull up.

Après avoir refait un test manuel, j'ai échoué. J'ai donc testé encore et encore. À chaque fois, j'ai "toujours déclenché après rétractation". Ma faute était de simuler l'approche du lit chauffant, j'ai pris quelque chose de plat pour déclencher la microsonde. J'ai oublié que le stepper fait un petit mouvement d'avant en arrière après - et je ne sais pas à quel point cette sonde est sensible. J'ai testé à nouveau avec une petite touche et une seconde après un temps très court et mon test a été réussi.

Ok en résumé .. au lieu de ^PC14 la commande très très correcte est : pin: ^!PB2 pour le Manta M8P

Merci pour ce fil, il m'a été d'une grande aide :)

Good morning !
I come to you because I am desperate to find a solution to my problem!
I am new to klipper and I use a BTT mp8 card with a V2 microprobe as well, but at the moment I cannot trigger this probe, I had the same problem as you, but being on ratos ( klipper) I'm at a dead end, can you provide your configuration lines for this pin please? I'm really in a big problem
friendly

@cylon1975 I found the manual for V2 probe :) . It has a section for the Manta 8P. The configuration is quite different depending on whether you have the M8P v1.1 or the M8P v2.0.

https://github.com/bigtreetech/MicroProbe/blob/master/MicroProbe%20V2%20User%20Manual_20240304.pdf

^!PB2 Is what you want for your sensor pin (pull down configuration since you are using a Microprobe V2)
PB1 Is you control pin

@cylon1975J'ai trouvé le manuel de la sonde V2 :) . Il dispose d'une section pour le Manta 8P. La configuration est assez différente selon que vous possédez le M8P v1.1 ou le M8P v2.0.

https://github.com/bigtreetech/MicroProbe/blob/master/MicroProbe%20V2%20User%20Manual_20240304.pdf

^!PB2Est-ce que vous voulez pour la broche de votre capteur (configuration déroulante puisque vous utilisez une Microprobe V2) PB1Est-ce que vous contrôlez la broche

Hello and thank you for your quick response !! I finally succeeded by copying the script list by creating a fileMicroProbe.cfgand report this file inprinter.cfg!! Thanks again for the help !!                                                                                                                                                                 

@PaulStep61 You need to tab all the gcodes that you call.

gcode:
SET_PIN PIN=probe_enable VALUE=1

This does not work, it should rather be:

gcode:
    SET_PIN PIN=probe_enable VALUE=1

Otherwise klipper will see it as its own variable inside the config, rather than the gcode belonging to a variable.