-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Biqu Microprobe support #2956
Comments
Can you provide more technical information or technical reference for the Microprobe? |
Hi, yes, here is the github page: https://github.com/bigtreetech/MicroProbe. Deploying/stowing seems to be done by changing the state of the control pin, and the reading of the state is the same as with BLtouch |
I read the document, here is the key related info. There are 2 versions, V1 and V2. V1 triggers on high, V2 triggers on low. A 10K ohm pull-up cannot be achieved with the MCU internal pull-ups. I believe the TFTs have no external pull-ups, so one might need to add an external pull-up for the probe to work (especially for the V2). If you just want to do some testing then you can define custom commands in the TFT to deploy and stow the probe. The range of the probe seems to be very limited. The price is lower than the BL Touch, but much more expensive than the 3D Touch. |
The BTT TFTs have a manu for manually testing the BlTouch probe. In there you can test the probe, deploy it, stow it..., but there is currently no support for the Biqu Microprobe. Since the Microprobe works based on the pin state and does not emulate the servo motor, current buttons just show an error when pressed, as the G code commands are not recognised.
I would like to have an option to choose between the Bltouch probe and Microprobe in configuration.ini, and if the microprobe is selected it should show a different menu with buttons that emulate the appropriate comands.
The text was updated successfully, but these errors were encountered: