Sorry to spam the board, but I’m really stuck. I’m using DO R53 on a TAZ 6 with BLtouch and Archim2 and Dual v3.1 extruder.
Here is what I can’t wrap my head around:
My Z probe offsets are:
X = 6.5 (centered between the two nozzles)
Y = 33 (behind the nozzles)
the default Z offset is -2.35.
If I use my actual X and Y probe offsets, the printer head crashes (or complains that Z probe is past the bed) because the X axis moves probably starting from the -26.1 start point (Does PROBING_MARGIN = 35 effect this?)
So, I’ve been fudging them and making the X offset = 16, which just barely hits the bed. Now as for the Z offset: the default in the firmware is -2.35. I home the printer with G28, and the print head moves up to 33.35. If I Move the print head down towards the bed at this point, the nozzle hits the bed at about Z = 5. Meaning, I think, that my Z offset it 2.7ish. But I’m pretty sure it’s supposed to be negative. And I can physically measure the end of the stowed BLtouch sensor as about 2.7mm higher than the nozzle. What am I getting backwards?
…And I can’t get G29 P1 to work, but one thing at a time.
Please help. I’ve been doing the same procedure for hours.
Recompiled firmware with Z_SAFE_HOMING positions set to 140,140, and the Z probe offsets set in firmware. Fixed the first couple issues.
The culprit for the failed probing was MANUAL_Z_HOME_POS 5.5. Any idea why this is specified in the firmware? I’m not being accusatory, just wondering.
Hi trashcat. It looks like the Dual V3.1 is a new product from LulzBot. I suspect this is why you are having problems with the firmware in Drunken Octopus, which is meant for the original Dual V3.
The MANUAL_Z_HOME_POS is meant to account for the Z button riser that used to ship with these toolheads. It would make sense that it should not be used with the BLTouch.
So it looks like there was an error in my config script where it was not properly disabling the modifications for the Z button riser when using BLTouch. I will correct this in the next Drunken Octopus release. Thank you for bringing it to my attention.