Replies: 2 comments 11 replies
|
that is something I've thought too. I'll have to take another look into it, but from what I understand it can be a limitation of the board itself and how the firmware reads the pins. like it cant read both, it has to be one or the other. for instance, I tried having it so each axis could be disabled individually, but its not possible at all because they share the same connections on the board. so if you were to enable or disable one it has to be all. |
Aquila_N32_UBL-ProUI-EX-MPC-01-27-tests.zipImportant I'm sure you know what to do in order to test this out. so the probe should be connected in the 5-pin port, and the Z limit switch connected to the port Caution !!🛑 Just be ready to KILL the power incase!!🚫 ⚡🔌Okay, try test ending in
edit: here are a couple more I made if the first two don't work, or doesn't work as well Aquila_N32_UBL-ProUI-EX-MPC-01-27-tests2.zip |
Uh oh!
There was an error while loading. Please reload this page.
I've had a few nozzle <-> bed crashes due to bad connectors on my 3Dtouch probe wiring, which got me to thinking as to why the Z-limit switch wasn't working as an emergency backup for just such touch probe failures.
Is there some reason the firmware can't check for both when Z-limit testing?
Also by extension, would it be difficult to add a menu option to set the Z testing method to either the Z-microswitch or the 3Dtouch, or both?
All reactions