cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X

Translate the entire conversation x

Define countersink note in .hol files

Foggy
4-Participant

Define countersink note in .hol files

I can define the thread hole format in the .hol file after  edit CALLOUT_FORMAT line.

but i can't define the countersink hole format based on this way, anyone can tell me how to define that?

 

another problem is how to hide the zero after the decimal point?

11.png

ACCEPTED SOLUTION

Accepted Solutions
TrainStopper
12-Amethyst
(To:Foggy)

Ah OK, that is a counterbore, not a countersink.

Try this for counterbored holes:

CALLOUT_FORMAT <CTRL-a>n<CTRL-b>&Diameter / <CTRL-a>v<CTRL-b> <CTRL-a>n<CTRL-b>&CBORE_DIAMETER <CTRL-a>x<CTRL-b> &CBORE_DEPTH

What I did was to create multiple .hol files so I could setup the callout format once and just invoke the hole type that used the callout format I wanted when creating the hole.

PTC has some documentation on .hol files, you need to track down a few separate documents to get all of the syntax, its just old school weird stuff.

A little patience and you should be able to get the note pretty close to what you need.

View solution in original post

10 REPLIES 10
TrainStopper
12-Amethyst
(To:Foggy)

This is mine-

CALLOUT_FORMAT &Screw_Size &Thread_Series-&Thread_Class <CTRL-a>x<CTRL-b> &Thread_Depth /<CTRL-a>w<CTRL-b> <CTRL-a>n<CTRL-b>&CSINK_DIAMETER[.2] X &CSINK_ANGLE[.0]<CTRL-a>$<CTRL-b>

Foggy
4-Participant
(To:TrainStopper)

Thanks for your reply,I tried your code but it didn't work as I wanted;

The display result I'm expecting is like in the image below:

For thread holes:

Foggy_1-1754615948139.png

For countersink holes:

Foggy_0-1754615438993.png

 

TrainStopper
12-Amethyst
(To:Foggy)

Ah OK, that is a counterbore, not a countersink.

Try this for counterbored holes:

CALLOUT_FORMAT <CTRL-a>n<CTRL-b>&Diameter / <CTRL-a>v<CTRL-b> <CTRL-a>n<CTRL-b>&CBORE_DIAMETER <CTRL-a>x<CTRL-b> &CBORE_DEPTH

What I did was to create multiple .hol files so I could setup the callout format once and just invoke the hole type that used the callout format I wanted when creating the hole.

PTC has some documentation on .hol files, you need to track down a few separate documents to get all of the syntax, its just old school weird stuff.

A little patience and you should be able to get the note pretty close to what you need.

Foggy
4-Participant
(To:TrainStopper)

Different callout format use different .hol file is a good way to solve this problem, 

Thanks for your help very much!!

pausob
18-Opal
(To:Foggy)

Note that you can define all callouts in the same hole file - in the DEFAULT_CALLOUT_FORMAT_DATA section - this is documented here.  This seems better than using and managing multiple .hol files with the same THREAD_DATA...

Foggy
4-Participant
(To:pausob)

I tried define all callouts in the same .hol file but all of the hole type notes display on my screen;

 

Here is my code, could you give me some advice to solve this problem? 

 

&HOLE_INSTANCE_COUNT&HOLE_INSTANCE_x_SYMBOL &METRIC_SIZE - &THREAD_CLASS &VAR_THREAD &THREAD_DEPTH[.2] / <ctrl-a>n<ctrl-b> &DIAMETER[.2] &VAR_DEPTH &DRILL_DEPTH[.2]
&HOLE_INSTANCE_COUNT&HOLE_INSTANCE_x_SYMBOL <CTRL-a>n<CTRL-b>&Diameter[.2] THRU / <CTRL-a>v<CTRL-b> <CTRL-a>n<CTRL-b>&CBORE_DIAMETER[.2] <CTRL-a>x<CTRL-b> &CBORE_DEPTH[.2]

 

 

Chris3
21-Topaz I
(To:Foggy)

It would be helpful for you to state exactly what hole configuration you are using. Maybe a screenshot would help. For instance, the .hole files have formats for Tapped, clearance, CSINK, CBORE, EXIT_CSINK and CSINK + CBORE. The notes change for each of those options. Which one are you trying to craft a note for? Also you should be aware unless you have reset_hole_note_at_edit set to yes, you need to go into the hole note tab and hit the "reset" button to get the new hole note.

 

Lastly you should be aware that Creo loads the hole files at boot only. Updating them without restarting Creo will not have any effect.

TrainStopper
12-Amethyst
(To:Foggy)

Some good points so far.

I setup my .hol files a long time ago, there may be better ways to approach all of this as the software has evolved.

Is there a way to have one .hol file that does everything? I don't see how.

How in a single .hol file do you standardize on a countersink diameter that is appropriate for a clearance vs. tapped vs. flat head screw?

While I agree it takes some time to setup specific .hol files, I value the simplicity where I ensure all users execute consistently & don't need to edit dimensions while modeling or modify hole callouts in drawings.

Yes, @TrainStopper , I agree that one .HOL file cannot accommodate everything.  However, @Foggy , if your holes are defined by the same THREAD_DATA table, then the "variable" callouts - i.e., depending on whether there is a countersink or whether it is a blind hole or if it is threaded, etc... - they can all be defined at the DEFAULT_CALLOUT_FORMAT_DATA section:

pausob_1-1754921451314.png

 

 

 

 

Foggy
4-Participant
(To:pausob)

Oh, thanks for explaining, you're right-- I am using the same THREAD_DATA table, I finally understand how to configure the .hole file exactly,

Announcements

Top Tags