Z-TILT ERROR: BLTouch failed to raise probe : using klipper v0.11.0-114-g0a645e49
Hmmm software bug with latest update??
If I manually run BLTOUCH_DEBUG COMMAND=pin_down and BLTOUCH_DEBUG COMMAND=pin_up directly after this error is generated both commands succeed without any errors.
12 Replies
There have been no bltouch related changes in RatOS. Those commands are klipper internals.
More than likely a wiring issue that just coincided with a software update
wise-white•16mo ago
That would be the second time in no time. Only about 3hours printing on the new BLTOUCH cable. Note if I run the BLTOUCH_DEBUG command pin_down pin_up at the same coordinates at which the error was first generated both commands work just fine.
NB The first z-tilt probe works fine.
RatOS does nothing besides configure the bltouch for you. You're having hardware problems, not software.
Intermittent issues further point towards hardware issues
The bltouch is a complicated device without any noticeable advantages. There are so many things that can fail on it.
(that's why you'll see people recommend the SuperPINDA, or if you really want a tactile probe, something like the Euclid).
wise-white•16mo ago
Laughing a little. Was finalizing the setup after the 3.0->3.1 upgrade so I could prepare for printing my bltouch replacement parts, mount for a Euclid probe. Feels like the chicken and egg are chasing their tails.
Haha yeah, hope you can get it to work. Usually wiring or problems with the solenoid (there's a hex screw in the "foot" that might help here) is the cause.
there's also the more obvious things such as a bent pin.
wise-white•16mo ago
Bent pin? Do mean not hitting the bed at exactly 90degrees?
Bent as in retracting could fail
BLTouch is extremely sensitive
There's even a warning about not touching the pin because it's "sensitive to finger oil" 😂
wise-white•16mo ago
Except every time I manually probe it works. That’s why I keep wondering about software since as indicated the z-tilt run always works on the first probe point and fails at the second probe point. If I run a manual probe at the second point it works.
Basically the sooner I can be done with it the better.
Wait are you running RatOS v2 ?
wise-white•16mo ago
No.
Then it's highly unlikely to be a software issue. If it was everyone with bltouch and klipper would have similar problems.
in v2 i changed the homing routine
So there could be something there
But nothing has changed in v1
(it's all klipper)
If you run PROBE_ACCURACY, it'll probe 10 times in a row, try that one of the points that fail and see if it gets through that with no issues
wise-white•16mo ago
Good one! But for tomorrow, need to get some shut eye.
Lied. Looks like it's some sort of hardware issue. Just booted the printer and ran Home-All and the probe failed, reporting the original error, even though the probe had actually retracted.
Did some more testing and I'd say it was noise interference rather than a cable fault.