hexagon logo

Thread Clocking and Lead In Chamfer Strategy Guidance

Roughly determining the ID thread clocking to locate the thread start for maximum surface area for lead in chamfer diameter measurement. Basically, measuring the countersink of at most 1/3 the circumference of an internal thread entrance. I need to know the thread clocking to even make an attempt.

I understand this is one of those "could you, but should you?" questions, but please humor me, our customer has requested that we try. The threads are small, 5/16s and 1/4in, the countersink diameter doesn't even exceed the major diameter. I think at minimum, one might be able to measure the countersink angle and the radius of the countersink edge to the center of the thread minor with two lines and an intersection point. It doesn't help matters much that nobody actually models threads this small.

Imagine if this was the ONLY thing the program needed to do was this ONE task, to measure the clocking of a small thread.

My guess is, step one would be to locate the minor diameter of the thread and translate my alignment to the intersection of the thread to the surrounding surface. Then come down some distance and use a self-centering 2D vector point to nest my stylus ball between two adjacent thread minor crests. So then I would have a depth measurement from that point to the surface. I would think one could divide that distance by the pitch of the thread to get an integer number and a fractional remainder. If my point was directly below the thread start, the division would result in a clean integer with no remainder. If there is a remainder, then in theory one could relate that remainder to 360° circumference to estimate the thread clocking.

We aren't going to use thread gauges, pins, or tru-pos. The only tools we have at our disposal are the thread, the surface, and the stylus.


Am I on the right track? has anyone tried this before? Are there any productive suggestions? Stylus diameter? self-centering points? scanning?
Parents
  • It's a moot point at the moment... I'm pretty sure my company cheaped out and bought the incorrect controllers for our scanning heads. It either freezes the software, crashes the software, or crashes windows whenever we try to do anything but linear open scans or the basic circular paths in auto features. When I try to insert a self-centering point, pcdmis will crash when I simply click ok to add it to the edit window. Not even run it, just add it... rediculous. Hours on the phone with hexagon have gotten us nowhere but error logging and they say we're pretty much boned until the next time a tech can get eyes on our rigs.

    So yeah... haven't gotten very far at all... sorry, I wish I had something more substantive to report.


    Yeah, that sure sounds frustrating. Controllers can be fickle sometimes, especially when it comes to scanning. The pc-dmis crashing when adding a feature is real head scratcher. Gremlins or something.

    Thanks for the update, such as it is.
Reply
  • It's a moot point at the moment... I'm pretty sure my company cheaped out and bought the incorrect controllers for our scanning heads. It either freezes the software, crashes the software, or crashes windows whenever we try to do anything but linear open scans or the basic circular paths in auto features. When I try to insert a self-centering point, pcdmis will crash when I simply click ok to add it to the edit window. Not even run it, just add it... rediculous. Hours on the phone with hexagon have gotten us nowhere but error logging and they say we're pretty much boned until the next time a tech can get eyes on our rigs.

    So yeah... haven't gotten very far at all... sorry, I wish I had something more substantive to report.


    Yeah, that sure sounds frustrating. Controllers can be fickle sometimes, especially when it comes to scanning. The pc-dmis crashing when adding a feature is real head scratcher. Gremlins or something.

    Thanks for the update, such as it is.
Children
No Data