Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X
When we originally did our .Hol files over a decade ago we decided it wasn't possible to call out both FREE and CLOSE in the callout formats. The Hole note on the drawing could only be shown as a Free(what we set it as).
Is that still the case? When i add in CLOSE to the matrix/table it still just only gives me a Free callout and not the Close when Close is the value set in the model
Thanks!
DEFAULT_CALLOUT_FORMAT_DATA HOLE_TYPE THREAD DRILLED_DEPTH THREAD_DEPTH CSINK CBORE EXIT_CSINK CALLOUT_FORMAT CLEARANCE NO THRU_ALL NA NO NO NO &HOLE_INSTANCE_COUNT&HOLE_INSTANCE_X_SYMBOL <CTRL-a>n<CTRL-b>&FREE_DEC[.2] DRILL <CTRL-A>x<CTRL-B> &DRILL_DEPTH CLEARANCE NO THRU_ALL NA NO NO NO &HOLE_INSTANCE_COUNT&HOLE_INSTANCE_X_SYMBOL <CTRL-a>n<CTRL-b>&CLOSE_DEC[.2] DRILL <CTRL-A>x<CTRL-B> &DRILL_DEPTH
Solved! Go to Solution.
@jchance wrote:
PTC said there's a bug in the system
Hi,
trail file contains following information (I renamed NPT-JAMIE.hol to NPT_REFINED.hol]
!%CILoading Hole Charts ...
!%CWFormat error in fastener input file : E:\PTC\Creo10_060\Creo 10.0.6.0\Common Files\text\hole\NPT_REFINED.hol at line no: 38
This means that Creo does not accept bottom part of .hol file, i.e. CALLOUT FORMAT definition table.
I apologize that I do not have time to resolve your problem.
Going through the PTC Help some more...
i changed Free Dec/Close Dec/Etc to report &DIAMETER instead of &FREE_DEC. Working through some other stuff, but i think i got a handle on some of this after not looking at it for a decade
DEFAULT_CALLOUT_FORMAT_DATA
HOLE_TYPE THREAD DRILLED_DEPTH THREAD_DEPTH CSINK CBORE EXIT_CSINK CALLOUT_FORMAT
CLEARANCE NO THRU_ALL NA NO NO NO &HOLE_INSTANCE_COUNT&HOLE_INSTANCE_X_SYMBOL <CTRL-a>n<CTRL-b>&DIAMETER[.2] DRILL <CTRL-A>x<CTRL-B> &DRILL_DEPTH
Help from anyone:
Is there a way to have two different countersink diameters in the same .HOL file?
I model a countersink for every tapped hole i use and i have to manually adjust the diameter to the desired number.
Do i have to have two different hole files to do that? ie Tapped UNC and Clearance UNC?
I created a custom NPT file. I have it loaded into the directory that my other .HOL files are. All of the straight drill .hol files are being read correctly, but the NPT .HOL file isn't being read. I've renamed it to something different (thread series thread name) and I've also copied the same name as the commonfiles NPT file. Neither is working.
Any ideas?
@jchance wrote:
I created a custom NPT file. I have it loaded into the directory that my other .HOL files are. All of the straight drill .hol files are being read correctly, but the NPT .HOL file isn't being read. I've renamed it to something different (thread series thread name) and I've also copied the same name as the commonfiles NPT file. Neither is working.
Any ideas?
Hi,
there is probably an error in your file. Please upload it.
@jchance wrote:
PTC said there's a bug in the system
Hi,
trail file contains following information (I renamed NPT-JAMIE.hol to NPT_REFINED.hol]
!%CILoading Hole Charts ...
!%CWFormat error in fastener input file : E:\PTC\Creo10_060\Creo 10.0.6.0\Common Files\text\hole\NPT_REFINED.hol at line no: 38
This means that Creo does not accept bottom part of .hol file, i.e. CALLOUT FORMAT definition table.
I apologize that I do not have time to resolve your problem.
Thank you so much for that. The error was not having
DEFAULT_CALLOUT_FORMAT_DATA
above the specific combination note syntaxes.
appreciate it!
Can you answer if you can have a different CSINK diameter for tapped holes vs clearance holes in the same .hol file or do you need two different .hol files?
@jchance wrote:
Can you answer if you can have a different CSINK diameter for tapped holes vs clearance holes in the same .hol file or do you need two different .hol files?
Unfortunately I don't know.
There is only one column for values in the .hol file that gets read. There is no way that I know to change this.
You can however create a mapkey that changes that value to something else once it is selected.
