Matt's MP3DP V5 Build

MattMed · October 14, 2025, 5:57pm

Where did we land on BIQU Microprobe config for the V5? My current printer.cfg is for the BLTouch.

Jonathjon · October 14, 2025, 6:05pm

You will have to adjust pin numbers for your board. But this will give you the macros and such to have it work.

I believe @Michael_Melancon is running one on his V5 so he might be able to share his config. Again depending on which board you are running the pin numbers might change

MakerJim · October 14, 2025, 7:29pm

How do users compare genuine BLTouch vs Microprobe? Pros/cons?

MattMed · October 14, 2025, 7:56pm

I don’t know too many of the differences to be honest. I am only using it because I am using the V5 design the Ryan originally put out. That design has a toolhead mount set up for the BIQU Microprobe. So that is what I got.

As far as pros, it is smaller form factor and lower weight so those are always good things.

As far as cons, it doesn’t seem to support “touch mode”. It only operates on a mechanical switch inside the probe I believe.

I could be wrong, and I am sure someone could you a better comparison between the two.

Michael_Melancon · October 14, 2025, 8:08pm

github.com/michmela44/MP3DP-v5-4

printer_data/config/printer.cfg

main

###  V1 Engineering MP3DP V5  ###
###                           ###


### BTT Manta M8P, CB1, EBB42   ###
#################################################################################################################

#[include mainsail.cfg]
[virtual_sdcard]
path: ~/printer_data/gcodes
on_error_gcode: CANCEL_PRINT

[pause_resume]
#recover_velocity: 50.
#   When capture/restore is enabled, the speed at which to return to
#   the captured position (in mm/s). Default is 50.0 mm/s.

[display_status]

[respond]

This file has been truncated. show original

# Motor3
[stepper_z]
...
endstop_pin: probe:z_virtual_endstop
...



###   Probe   ###

[output_pin probe_enable]
pin: EBBCan: PB9
value: 0

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

[gcode_macro Probe_Stow]
gcode:
	SET_PIN PIN=probe_enable VALUE=0
	
[probe]
pin: ^!EBBCan: PB8
deactivate_on_each_sample: False
x_offset: 2
y_offset: -28
#z_offset: 1
speed: 5
samples: 2
sample_retract_dist: 3.0
lift_speed: 15
samples_tolerance: 0.02
samples_tolerance_retries: 1
activate_gcode:
	Probe_Deploy
	G4 P500  #Allow 500 milliseconds for the probe to deploy
deactivate_gcode:
	Probe_Stow

I think that’s all the relevant bits, but you can check all the files in the backup if you need

MattMed · October 15, 2025, 12:07am

Thanks for this! I will try it out. Right now, I am having some strange connectivity issues with the Pi and just saving and restarting after a config change seems to freak it out. So much so, that sometimes the config file corrupts or something and completely erases.

I have a new Pi coming just to rule that out.

Jonathjon · October 15, 2025, 12:13am

Yeah you have something going on. A firmware restart shouldn’t take more than 30 seconds or less and shouldn’t mess with the actual Pi at all.

orob · October 15, 2025, 3:19am

Might just need a different sd card

MattMed · October 15, 2025, 1:49pm

Hmmm, I wonder if that could be it. It is 32GB SD and has worked fine before so I am not sure.

I guess I will find out when the new Pi gets here later.

On the topic or SD cards, I can remove the SD card from the SKR Pro once the firmware.bin has been flashed, correct? It doesn’t need the SD in it to function?

MattMed · October 15, 2025, 1:53pm

Also, while waiting for the new Pi, I want to double check my wiring is correct for the MicroProbe. For the BLTouch, I used the pins in RED below:

However, for the MicroProbe, I have read that I need to only use the pins in BLUE instead:

Something to do with pullup resistors and stuff that I am not familiar with…

Which one is correct for the Microprobe, or does it matter?

orob · October 15, 2025, 4:49pm

I used the blue ones. You specify pullup in the config with a ^ before the pin name. Just be sure you get the correct sense pin assigned.

MattMed · October 17, 2025, 9:54pm

Okay…. more unusualness. New RaspPi 4, new microSD. New install of Klipper. New firmware flashing to the SKR Pro.

I have commented out the BLTouch lines of code from my printer.cfg file. I have replaced all of that with @Michael_Melancon configuration for the BIQU MicroProbe below.

Someone tell me why the heck it is giving me the below error??? I don’t even have anything referencing BLTouch in my config file anymore. If I go into my config file and ctrl+f to search for bltouch, it doesn’t exist. So how am I supposed to edit it? Makes no sense to me.

Jonathjon · October 17, 2025, 10:21pm

Can you zip and upload your current printer.cfg?

If you copied Mikes exactly then I have a good idea of where the problem might be

MattMed · October 17, 2025, 10:31pm

Well, since posting, I went to the bottom and found some code that was commented out for bltouch and just deleted it all together. No idea why it was reading it if it was commented out…

Next error was that z_offset needs to be specified in my new [probe] section. Even though Mike’s was commented out, I went ahead and uncommented it to be z_offset: 1. Fixed that error, hopefully that’s not a problem.

Next error was that “control” was not specified under either [extruder] or [heater_bed]. So what the heck, I uncommented out the “control: pid” and the corresponding pid values below it. That fixed that. Even though my other printer running Klipper does not have these uncommented. Not sure why it is requiring them on this machine??

Anyway, got through all the errors and got the machine moving. All axes moved in the correct direction. X and Y homed. However, when I homed Z, the probe deployed, the bed came up, triggered the probe, and then the bed came crashing down. I clearly don’t have some settings right with my probe or something.

I have attached my config file here if you’d like to see it.

config-20251017-182952.zip (7.6 KB)

Jonathjon · October 17, 2025, 10:33pm

That stuff at the bottom that looks commented out really isnt. Its stuff that save_config puts in and its still able to read it.

After you do the paper test and set your offset, then SAVE_CONFIG yours will be commented out as well and it will be back at the bottom of the file. Totally normal.

If you had run PID tune then that info was also at the bottom of your config and without the PID in the extruder section it throws an error.

MattMed · October 17, 2025, 10:36pm

Ahhh interesting. So is it a problem that I just deleted all of it off the planet?

Gotcha. But, doing a z_offset calibration (paper test) would require me to be able to home Z. It just crashes when I home Z.

Jonathjon · October 17, 2025, 10:37pm

Yeah I am looking at your config now. Will report back in just a min

Jonathjon · October 17, 2025, 10:40pm

Could you see anything in the terminal when it crashes the bed? Should throw up an error. Also if you dont have Z brakes (which I am pretty sure you dont) you really should get them. I have fried 2 SKR Pro’s from the bed falling

For now when you are testing make sure you stick your hand under the bed to catch it and let it down slowly until you get the errors resolved

MakerJim · October 17, 2025, 10:41pm

I’m still mucking about with one of those boards when I get a few spare moments trying to fix it.

I agree here, get brake boards for your build.

Jonathjon · October 17, 2025, 10:43pm

Absolutely no rush on my end. I don’t have any projects that need one right now and no time to come up with any lol. If you have uses for them please have at it!