Export JT with journal 1

[claforet]

Does any one know if there is a similar function to ufs.Ps.exportdata() that can be used to export a JT file using a journal?

Thanks.

 

[JohnRBaker]

File -> Export -> JT... is not yet supported by the Journal function.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[claforet]

OK, thanks. I also have a problem when I choose the "Save JT Data" from the save options and try to save an assembly, the JT is not created. When I save individual parts the jt's are created but when I save an assembly, I get the part file but no jt file. Is there a way around this?

Thanks.

 

[jpetach]

Claforet,

Hopefully the -generate_jt_assembly option for ugtopv.exe will do the trick without requiring an interactive session.

Regards, Joe

"%ugii_base_dir%\pvtrans\run_ugtopv.bat"


Usage: %UGII_BASE_DIR%\PVTRANS\ugtopv.exe <.prt | .bkm |
directory | file> [-pim=yes] [-noupdate]
[-u=<user>] [-p=<password>] [-g=<group>] [-rev=<rule>]
[-single_part] [-config=<file>] [-save_outside_teamcenter]
[-generate_assy_jt] [-honour_structure] [-generate_bookmark]
[-nopopulate] [-force_output_dir] [-rev=<revision rule>]
[-transform={<transform>}

General options demonstrating usage of this program:
-help Print a message to command prompt, summarizing
various command line parameters.
-examples Provide some examples of how to run this program.

General options for running this program in Teamcenter:
-pim=yes If running with Teamcenter Integration for NX.
-u=<user name> If connecting Teamcenter under different
user name, add this option
-p=<password> If connected to Teamcenter under different
user name, add this option for password.
-g=<group> If connecting Teamcenter under different
group, add this option
-role=<role name> If connecting Teamcenter under different
role, add this option
-rev=<rule> Specifies which revision rule to use while translating
NX assembly. This can only be used while translating
files stored within Teamcenter
-save_outside_teamcenter Saves the JT data outside Teamcenter

Options that affect how and where the component JT files are generated:
-config=<file> Name of the .config file containing tessellation parameters.
-single_part Just generate a JT file for the top part being processed.
-force_output_dir Write the JT files to the location specified by the
OutputDirectory setting in the .config file or
the location specified by the optional directory argument
(takes an optional "=<output directory>" argument).

Options that affect how assembly JT files are generated:
-generate_assy_jt Produce an assembly jt file for the assembly passed in
(takes an optional "=<assy jt file spec>" argument).
-honour_structure Honours the structureOption value in the .config file.
This produces JT files in the format previously generated
by the ugtojt translator. This allows support for
MONOLITHIC and FULL_SHATTER structure options.
Warning: This option will fully load the assembly and
will therefore use more memory.The files produced
can not be used for interoperation.
-generate_bookmark Produce a bookmark file for the assembly passed in
(takes an optional "=<bookmark file spec>" argument).
-nopopulate Do not write any component JT files
-noupdate Do not update assembly structure after loading the assembly
-transform={<transform>} Specifies a transform to apply to the geometry
in each component. This transform is a comma separated
list of 12 floats with the format:
{X1, X2, X3, Tx, Y1, Y2, Y3, Ty, Z1, Z2, Z3, Tz}