Skip to main content
D
dveljkovic10-Marble
10-Marble
January 30, 2021
Question

DEFAULT_CALLOUT_FORMAT_DATA

  • January 30, 2021
  • 1 reply
  • 4182 views

As soon as I add "DEFAULT_CALLOUT_FORMAT_DATA" to the ISO.hol file, Creo 5.0.6 does not open that file and is not visible in hole dialog. I do not add anything else. Anyone knows why this is happening?

1 reply

M
MartinHanak24-Ruby III
24-Ruby III
January 30, 2021
@dveljkovic wrote:

As soon as I add "DEFAULT_CALLOUT_FORMAT_DATA" to the ISO.hol file, Creo 5.0.6 does not open that file and is not visible in hole dialog. I do not add anything else. Anyone knows why this is happening?

Hi,

did you read http://support.ptc.com/help/creo/creo_pma/usascii/index.html#page/part_modeling/part_modeling/part_nine_sub/Formatting_Thread_Notes.html page ?

Please upload your ISO.hol file.

D
dveljkovic10-MarbleAuthor
10-Marble
January 30, 2021

Hi Martin.

Yes, I did. And everything started from there. I made file like what it says in mentioned link but I got into problem hol_1 file not showing up. At first, I though because I use Notepad++ and CR = Carriage Return and LF = Line Feed and how Creo reads text file (in this case hol file) is where the problem lies, but it is not.

Then I realised that as soon as I add DEFAULT_CALLOUT_FORMAT_DATA Creo does not show it in hole dialog. I did the same for ISO.hol and same happened.

 

P
19-Tanzanite
pausob19-Tanzanite
19-Tanzanite
January 31, 2021

I'm not sure this is the issue, but in your sample file, the table that defines the callouts is missing.

The line DEFAULT_CALLOUT_FORMAT_DATA should be followed by callout specifications.

You can specify a different callout depending on hole configuration.

 

Can you load in the hole table if you modify your example ISO_1.hol and add these 2 lines:

 

DEFAULT_CALLOUT_FORMAT_DATA
HOLE_TYPE THREAD DRILLED_DEPTH THREAD_DEPTH CSINK CBORE EXIT_CSINK CALLOUT_FORMAT
TAPPED YES NA NA NO NO NO &DIAMETER[.3]

 

(also, I think reloading .hol files requires Creo restart)

Terms & ConditionsCookie settingsAccessibility statement