-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Small improvement suggested to BLTouch.md #4367
Comments
Interesting. I'm not sure we want to reword the documentation, because a lot of users wont know if they have an external pull-up and the inverse problem tends to cause many more issues for users. (Specifically, they leave the line floating and they get random failures from that.) I am curious to see if your issue goes away with the internal pullup removed. -Kevin |
My suggestion was purely based on the fact that I suspect many people simply don't know what they don't know. In my case for example, when I put together my printer.cfg I read the full content of BLTouch.md and I immediately assumed that I need the pull-up as referenced in the document. Now, I am not a 3D printing or MCU expert, but I am very comfortable with all things mechanical and electrical (engineer with 25+ years of work). I thought that highlighting the fact that the pull-up is required but not on all boards would at least make people think about it and perhaps ask questions. But I do understand your point. In my case the outcome was the same - three head crashes into the bed that were arrested by the Z steppers stalling on torque. The first one was not with reduced current, unfortunately, and I had to replace the X carriage wheels as they developed permanent indentations (I have some pretty screenshots of the resultant bed mesh waviness). It has been a while and I have done a huge amount of experimenting trying to trigger the misbehaviour with no success. So it is looking very positive. I was fairly certain that the problem was fixed once I looked at the electrical noise on the BL Touch lines with my scope, but it's nice to have the empirical proof. In the end I did four separate things:
On a separate note, the Duet 3 Mini 5+ is awesome! Peter. |
Quick update: after many prints and countless hours of me trying to purposefully trigger BL Touch misbehaviour, I can confirm that everything has been working perfectly. |
I guess I can somewhat confirm @ReXT3D findings. I'm using a BTT SKR1.4. When connecting the BL-Touch to the dedicated Probe-Pin on the board, the BLTouch will not work until the pin is pulled-up (^) in the cfg (took me a while to figure this out). It though works out-of-the-box on a regular Endstop pin See the relevant schematics: |
Hello, It looks like there hasn't been any recent updates on this Best regards, ~ Your friendly GitIssueBot PS: I'm just an automated script, not a human being. |
Can you please upload the config file. My Bltouch is not working on probe pin. I did all the things |
BLTouch v3.1 |
Hello, It looks like there hasn't been any recent updates on this Best regards, ~ Your friendly GitIssueBot PS: I'm just an automated script, not a human being. |
I suggest the following small clarification be added to the BLTouch.md document:
"You need to configure these pins according to your wiring. Most BL-Touch devices require a pullup on the sensor pin. If the board does not supply an external pull-up resistor on the input used for BL-Touch, prefix the pin name with "^" to use the internal pull-up. For example:"
See here for a bit more background: Duet 3 Mini 5+ 5V supply capacitive load limits
Thank you.
The text was updated successfully, but these errors were encountered: