BLTOUCH_DEBUG commands not working
I'm trying to do initial setup (with RatOS2 Alpha) and am not able to get the BLTouch to work.
Setup: Octopus Pro 446
Toolboard: EBB42 v1.2
When the printer first boots the BLTouch goes through the self test and then enters idle state (solid red, retracted). When issuing a
BLTOUCH_DEBUG COMMAND=pin_down I get:
in console, and then no motion from the BLTouch.
I verified the wiring is correct for the toolboard, and verified that there's proper connectivity between the pins on both connectors.7 Replies
fascinating-indigoOP•3y ago
It's not totally clear to me if I should have both:
[include config/z-probe/bltouch.cfg] (under HOMING) and [include config/toolboard/bltouch.cfg] (under TOOLBOARD), but I've tried all 3 combinations (just homing version, just toolboard version, and having both)
This particular probe worked with RatOS v1, without a toolboard (directly wired to the MCU), so I think it's just a configuration issue, but I'm not sure where.fascinating-indigoOP•3y ago
I've now tried reflashing the toolboard, double and triple checking that the wiring has proper connectivity and order (per the wiring diagram on the website https://rat-os.vercel.app/docs/toolboards/btt/ebb-42-12), I cross-referenced the pins that are in the config files with the pinout for the actual board, I tried adjusting the screw on the back of the bltouch. Nothing obvious in the log files either.
fascinating-indigo•3y ago
Hi, I have the same problem with an ebb V1.1
fascinating-indigoOP•3y ago
I thought last night during testing that I could query the endstops and manually move the probe tip up/down that it would change state, but this morning it doesn't seem to do that so maybe I was mistaken. So it really just doesn't seem to have any communication on the sensor/servo
fascinating-indigoOP•3y ago
Futher dev:
Unplugging the BLTouch and checking the endstops in RatOS indicate that it's TRIGGERED
Manually bridging the GND and PROBE pins switches that back to OPEN
I don't know how I would test the SERVOS pin to see if it's properly being communicated with.
fascinating-indigoOP•3y ago
I gave up and built a Klicky probe instead (which required its own debugging, but not too bad). It uses the SERVOS and GND pins from the image above, so the board seems fine and RatOS is looking at the right pins. Only thing I can think of is that the BLTouch died after sitting for a year :/
fascinating-indigo•3y ago
Sorry, I had a failure in the printer.cfg. I have forgotten to enable the following line [include config/z-probe/bltouch.cfg]. No it works fine.
I thougt the line [include config/toolboard/bltouch.cfg] includes all functionality for bl-touch but it does not.