-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUESTION] BLTouch/Endstop always TRIGGERED #16552
Comments
I would try with nothing connected to the Z endstop connection and see what happens. If your x and y end stops are working the I would test one of these connected to the z stop connector to see what happens. I think that you may have damaged the board if it was working before. |
I tried that already. It always says "triggered". But I don't understand what cutting off the protruding pins has to do with the Z-min issue :-( |
Hoping you have done it without power, it can be that electrostatic discharge has destroyed processor input |
of course I did it without power. Plugged off the AC cable from the printer as well. Who is going to solder with power turned on if someone does that he deserves to fry his board :-D I can trigger and open the mechanical endstops for X and Y so I don't know why Z is not working. I plugged the Y endstop to Z but it's always saying triggered. Never mind, I'll check again when the new mainboard arrives. |
I'm not sure what the problem is here:
Pin down = open, Pin up = TRIGGERED. |
Is this a question from your issue or what are you trying to tell us? You should read what M119 command is doing You need to use M43 S1 and touch your BLTouch barely to see if the state changes from open to triggered and vice versa. From what I can say is either your mainboard or the BLTouch has a malfunction. |
It's always been like this from day #1 - and it works fine. In fact, it was one of the test units for working on the BLTOUCH_HS_MODE functionality in Marlin. It's a genuine BLTouch v3.0 and tested on both an SKR e3 mini v1.2 and the stock Ender 3 mainboard. Further, you can see me sending the RESET ALARM ( |
@CRCinAU the thing is then why my ender 3 is not working? My BLTouch is also a original one not one of this knockoffs for 10 bucks. |
Go back to basics. If you deploy the probe, does it change to OPEN? If you stow the probe again, does it go back to TRIGGERED? At this stage, I'd ignore what the documentation says - as a lot of boards don't support interrupts on the probe ports - meaning it all has to be done via polling - so a pulse can be very bad - especially if missed... |
@CRCinAU i did everything i know but so far it doesn’t change. Do you have a recommended way to test? I can then try that later when I’m home again. |
@CRCinAU please note this:
this is not a bltouch issue... Edit: |
Certainly. I wonder though, I never could get it working on the PROBE port on the SKR E3 Mini v1.2 - I had to use the Z-STOP port. While that's an off topic discussion, I wonder if its to do with the input setup - which would be board specific... |
That may be an hardware issues maybe because of some sort of PNP NPN? Don't know how skr works. |
As this might be useful to OP, as it may well be a similar board issue, schematics for the SKR E3 mini v1.2 are here: |
Stop and probe are, on H/W side, identical. Edit: Only difference I see is PROBE that is connected to a multifunction pin (PC14-OSC32-IN) maybe it needs a special processor setup to be correctly used. I don't know how stm32 works, maybe some other developpers know it |
I'm experiencing this issue across several HW platforms and would be willing to show the problem on each HW platform on camera. These are the HW platforms; RAMPS 1.4/1.6, MKS Gen L 1.0/1.4, SKR V1.3/1.4 SKR Pro and more. I want to proven incorrect. Let me know. |
Marlin trusts what the pin tells it. Perhaps pullups / pulldowns need to be set on these pins…? |
Give me the marlin setting you want and I'll compile and load for each board. |
Is it your BLTouch that is failing to work, as with the OP? |
Without pullups/pulldowns pins may float, but as GMagician points out, the pins are apparently pull-up. Still, it cannot hurt to try enabling the pull-ups for NC switches or pull-downs for NO switches. |
Yes, the BLtouch is failing and shows triggered. I have two flavors of BLtouch V2.0 and 3.1. |
Hardware: Downloaded Marlin-bugfix-2.0.x Configuration.h changes: Opened PronterFace.exe Output:SENDING:M119 |
Repeated with SKR 1.4 Turbo (LPC1769) Results: |
RAMPS 1.4 PlatformIO.ini Recompiled and uploaded Opened Pronterface: |
Which board would you like me to try next? Or did I miss a step? |
Swapped in BLtouch 2.0 with same results on RAMPS 1.4. |
3dTouch on RAMPS 1.4 has same issue. |
Set #define ENDSTOPPULLUP_ZMIN Set //#define ENDSTOPPULLUP_ZMIN |
Not sure if all my HW is broken, but seems like a low probability. |
Wow. Now if you could only identify an older version of the firmware that actually works correctly on all your improbably broken HW . That might be useful to someone. |
Example 1 Would you like more examples? |
@ebraiman please note that original post by @Anilo1990 was about problem with bltocuh but also mechanical endstop. Now one question about your test. Have you ever tryed with an endstop on the same input? Maybe something wrong with pin assignment for your board? Edit: what if you close input to gnd/3.3V (pay attention to this may be dangerous)? |
Tested just now on RAMPS 1.4 with Mechanical two wire switch and worked correctly. echo:Marlin bugfix-2.0.x
|
Just some thoughts. If BLtouch does not work for multiple chipsets of Marlin for 1768/1769/MEGA2560, then could this be an implementation issue? |
Do you mean @ebraiman that you have suddenly multiple boards that show BLTouch triggered regardless whether the probe is stowed or deployed and thus you can't use the probe? |
I'm using a fixed mounted configuration. Should we set fixed mount? Did this change recently? This has been occurring sine last summer 2019. |
I mean that is the state reported by M119 still triggered after you deploy the probe pin down with M280 P0 S10 or through the BLTouch menu via LCD. |
@ebraiman don't try M119. Try sending M43 S1 and then see what happens. |
I have a mega2560 + ramps 1.4 + bltouch clone and it works, so not too clear what happens to you |
@Anilo1990 is your org issue still there? |
@boelle yes still waiting for the replacement board from china. it's on his way. estimated arrival time is mid february. |
@Anilo1990 since your board may be dead and nothing can be worse, you may try to short-circuit gnd and input signal (on board connector with nothing connected) and check what M119 says. Then repeat with 3.3V (I think your board is also 5V tolerant) and signal. |
@Anilo1990 have you checked what your dead board said when sending M119 ? |
So I got my new Cheeta 1.2a board today. Swaped it and my printer works again like before. [...] [...] I tried M43 S1 before and like I wrote 23 days ago when I touched my BLTouch with the old board it didn't detect triggering. The new board detects the manual triggering. |
@Anilo1990 so this one is solved? if so please click the close button below |
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. |
Hi guys.
Hope you guys can help me a little because my printer is broken right now.
My Configurations
So I own a Ender 3 Pro with a Cheetah 1.2a silent board. For ABL I'm using a genuine BLTouch V3.1 with Marling Bugfix 2.0.x. Since I've this printer it worked fine for me. No big issues at all for months.
Configuration.h and Configuration_adv.h file below in the zip file.
Configuration.zip
What Happened / Bug Description
I was designing a case for the motherboard so I can store it on the backside of the printer. Because there is limited amount of space I cut off the protruding PINs for the display cable on the back of the motherboard. After that I realized that my printer isn't autohoming anymore.
https://youtu.be/LqzZSbMJdMM (with BLTouch)
https://youtu.be/A5y0Ab0J8RQ (with mech. Endstop)
### Actual behavior: [What actually happens]
I checked every wire twice and thrice. Did a continuity test with my multimeter for the BLTouch wires and the multimeter is beeping. Before autohoming I can move the Z-axis up and down via LCD commands. I don't know what happened to this board which was functioning properly before cutting of the protruding pins. Btw the protruding pins which you see on the picture below are for the LCD and they have nothing to do with the Z-axis or BLTouch. Also I didn't put any stress on this board which might be a result of cold joints.
I also tried the stock Fysetc Marlin software from https://github.com/MarlinFirmware/Marlin/issues/new/choose without any success.
### Expected behavior: [What you expect to happen]
The expected behavior would be that I can autohome my printer and the Z-axis is not always triggered. I can see that when I manually trigger the mechanical endstops for X and Y. The state changes from open to triggered but not for Z.
### Additional Information
I'm reading through the whole internet since yesterday night.
Also in Github there are a few topics related to this issue but unfortunately nothing works for me
#11877
#12657
#7024
The text was updated successfully, but these errors were encountered: