BIQU MicroProbe V2.0 not working

Basic Information:

Printer Model: Tronxy x5sa 400 pro
MCU / Printerboard: BTT SKR 1.4 Turbo
Host / SBC Pi4
klippy.log
printer (2).cfg (3.3 KB)
klippy (3).log (1.1 MB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I’m using an SKR 1.4 turbo controller with a micro probe v2. With my configuration, the way it is now, the probe does its self-checks on boot up, and the blue light stays on. It reports “TRIGGERED” in mainsail all the time and doesn’t respond to commands. I’m hoping someone here has some in site on this. It’s been driving me nuts for days now.
Thanks yall

The pin you are using is not suitable for this probe as it lacks any kind of pull-up. This probe requires a strong pull-up, so use, for example, E0Det (pin 1.26), which has a 10k pull-up.

so is that as easy as moving the wire and changing the pin in the config? Sorry, I’m fairly new in this area of nerding. Thanks a ton for your help BTW

So, I have an update after changing the probe pin to !1.27, it shows triggered with the probe up and open with the probe down. However, it still won’t respond to commands. I’m a bit afraid to try to home it without knowing if it’s working correctly.

Alright, here’s where I’m at. X and Y home fine, Z home says “Endstop z still triggered after retract.” Here’s my current log and a screenshot tof he output of the console


klippy (4).log (1.6 MB)

You seem to have a general issue with your endstops, particularly X and Y. Follow this link and, first and foremost, ensure that G28 X and G28 Y are working correctly.

Additionally, you have multiple instances of the following error:

Timeout with MCU 'mcu' (eventtime=125.968767)
Transition to shutdown state: Lost communication with MCU 'mcu'

This indicates a general hardware issue. Refer to Timeout with MCU / Lost communication with MCU.

Moreover, the MicroProbe is not a BLTouch, despite its resemblance. Neither the settings nor the commands for a BLTouch apply to it.