search

knutwurst / Marlin-2-0-x-Anycubic-i3-MEGA-S

Marlin 2.0.x Version for Anycubic i3 MEGA M/S/P/X/CHIRON and 4MAX with Anycubic TFT or the "new" DGUS Clone TFT - Now also with BLTouch!
GNU General Public License v3.0
787 stars 187 forks source link

[BUG] BLTouch Sensor triggers mid air #504

Closed Druckmichel closed 11 months ago

Druckmichel commented 11 months ago

Hello, I installed an BLtouch on Anycubic i3 Mega Pro following your Beginner's Guide. Flashed "MEGA_P_DGUS_BLT_10_v1.5.2.hex". Via Octoprint I did Determination and configuration of the Z offset, so far no issue.

When it gets to G29/ Meshleveling the Printhead lift up and travel to point one and starts probing midair. (Depoying and retracting the pin. No Z travel downwards touching the bed.)

knutwurst commented 11 months ago

This is most likely due to incorrect wiring of the sensor. It triggers even though it doesn't trigger. White and black swapped? ;)

Druckmichel commented 11 months ago

Wow response time Zero :)

I swapped it for testing but then it's not working. I was wondered about that behavior because "Determination and configuration of the Z offset" went very well. Wiring double checked five times.

knutwurst commented 11 months ago

Take a look at your hotend board. Are there various small SMD components installed there? Maybe that's the cause... they have to be removed. I still suspect an electrical problem. There's a loose connection somewhere or a cold solder joint or something.

Druckmichel commented 11 months ago

You are so right. It was my fault, forgot swapping A5 / B5 on the green connector.

Sent you Coffee on PayPal. Merry Christmas from East Frisia

knutwurst commented 11 months ago

Never mind. Everybody makes mistakes. I destroyed the stepper drivers the first time. Or where do you think the images in the wiki come from? ;)

I'm glad it works now!

Thank you and Merry Christmas! <3

github-actions[bot] commented 1 month ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.