2024-10-31 (Th) OLEDHoleMount The nut was the problem

Whenever I printed a screen mount and nut, I worked hard to make the nut fit onto the stalk by working it back and forth to wear away the rough edges, but they were always too snug. I felt plastic crack on the thin stalks several times, but nothing catastrophically failed until a nut broke in half when I used a metal wrench. I placed the shattered halves onto the tube and saw that the threads did not align. The thread-per-inch factor differed for each, so they were only partially compatible.

The threads do not match

I used this clue to look at my code and made a cutaway view to check the area where the threads intersected, and they did not mesh. I played with the variables and found that changing the "tolerance" variable I sent to the library changed the angle on the threads but ONLY in the internal thread iteration, not the threaded post. I hardcoded the "pitch" on both, which forced the components to align. I printed some new nuts to confirm, and they fit.

I was surprised to find that the printed parts had significant play. I had the tolerance up so high that I introduced a significant gap, but my printer was capable of printing with a better tolerance. The next prints will have nuts that fit well.

Compatible thread code

GitHub files for OLEDHoleMount.

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.
2024-11-06