• No results found

Value differs 3D and actual entry

In document Title Block Editor Catia Eng v5 (Page 35-39)

If you press the 3D logo on the right side of the entry, the 3D value will be taken and the yellow color will change to white. If all entries are accepted, the question mark on the tab will be removed.

6.4.3.6 Summary of pre configured values

Here a table which shows the built in values which are directly extracted from CATIA (3D values and special values as mentioned above)

Name of title block entry Meaning Source

TitleBlock_Text_Number Number 3D-Master Property

TitleBlock_Text_Title Title 3D-Master Property

TitleBlock_Text_Revision Revision 3D-Master Property

TitleBlock_Text_Nomenclature Nomenclature 3D-Master Property

3D Info Remin-

der for mismatch

TitleBlock_Text_CADSystem Version, Release, Ser- vice Pack

CATDrawing

TitleBlock_Text_NumSheets Number of sheets in the

drawing (details not in- cluded)

CATDrawing

TitleBlock_Text _numActSheet Number of the sheet in

the sequence of sheets

CATDrawing

TitleBlock_Text _SheetScale Main scale of the sheet CATDrawing

TitleBlock_Text_UPName User Property from the

3D Master

3D-Master User Property

6.4.4 TD1 compatibility – td1_config.cfg

The file for the TD1 compatibility has to be stored in the config directory. The naming has to be: config\td1_config.cfg

If set in the basics.cfg, the macro will link the given parameter to the corresponding title block field (s) if necessary.

Sample provided:

' Each line has the following info ' - SmarTeam Parameter Name

' - Name of text component on the sheet ' - Parameter visible in V5 tree

' - Parameter only linked on sheet 1 (e.g. as scale, material, ...) '

'Parameter name;Text component name;visible;sheet1_only

Description;TitleBlock_Text_Description;true;false Creation Date;TitleBlock_Text_BearbeitetDate;true;false Approval Date;TitleBlock_Text_GeprueftDate;true;false Originator;TitleBlock_Text_Bearbeitet;true;false Approved By;TitleBlock_Text_Geprueft;true;false

Original Creation Date;TitleBlock_Text_BearbeitetDate;true;false Title;TitleBlock_Text_Number;true;false

Scale;TitleBlock_Text_Massstab;true;true

6.4.5 Modifying the GUI – skin.tcl

In this data set you can provide your own icons or background color. #

# define background color #

set background_colour "#FFE7BD" #

# define language, the default is English, omit # the declaration, if you want to use English #

set language "de"

#set background_colour "#FFFFFF" #

# define the files for the icons here

# $where_am_i is the installation directory #

image create photo but_def -file "$where_am_i/icons/pic_default_1.gif"

image create photo but_from3d -file "$where_am_i/icons/pic_from3d.gif"

image create photo but_calendar -file "$where_am_i/icons/pic_calendar_1.gif"

image create photo but_ok -file "$where_am_i/icons/pic_ok.gif"

image create photo but_can -file "$where_am_i/icons/pic_can.gif"

image create photo but_change -file "$where_am_i/icons/pic_change_small.gif"

image create photo but_data_copy -file "$where_am_i/icons/pic_data_copy.gif"

image create photo logo -file "$where_am_i/icons/logo.gif"

image create photo but_open -file "$where_am_i/icons/open.gif"

image create photo but_save -file "$where_am_i/icons/save.gif"

image create photo but_help -file "$where_am_i/icons/help.gif"

image create photo but_down -file "$where_am_i/icons/pic_down.gif"

image create photo but_td1 -file "$where_am_i/icons/td1.gif"

If you want to use your own logo, simply exchange the logo.gif or choose another name.

6.4.6 NLS Support

Within the config directory, language dependant files can be supplied under an appropriate directory (e.g. de for German). The file containing the translated messages has to be named

message.cfg

The language to be selected is defined in the skin dataset (see above).

If the GUI doesn’t find a message in the file, the original string (English) will be displayed. If someone supplies a file for another language – send it to me, I will add it in the distribution.

In case you want to use the English messages, set the language in the skin.tcl config file to en, sample

set language "en"

6.5 BOM management

For derived drawings, the script will pick up the associated 3d product from the active sheet and ex- tract the bom to a table which has to be in the drawing. An existing bom will be updated.

6.5.1 Get a Bom table

Copy the Matrix for the bom (text table) from a sample drawing or library to your drawing. A sample model is provided

Product Ableitung.CATDrawing in the sample directory.

Title block frames can be prepared in advance, to contain a bom table. E.g.: Provide a frame for A0 with a bom table and one without. One sample is provided in the template directory.

You can use all CATIA functions to build up a sample table for your bom entries. The mapping of the different columns for the bom is described in the next chapter.

The first or last row should contain the header for your bom. The placement of the bom should be up or bottom, that will keep the table in the same location even if the number of entries in the table will change. If you plan to add the bom table just above the title block, you should use the positioning bot- tom left (that’s also done for the sample provided).

Keep playing with the options for the CATIA DrawingTable. Normally you should be able to get a layout as you want it.

6.5.2 Configure your Bom

The mapping of the CATIA internal bom to the table is done by defining the component name of the bom table in the right way.

Picture 23 Component Id for Bom Table

In document Title Block Editor Catia Eng v5 (Page 35-39)

Related documents