Skip to main content
D
davehaigh13-Aquamarine
13-Aquamarine
July 15, 2014
Question

Parameter for version build of Creo?

  • July 15, 2014
  • 5 replies
  • 1360 views
I have a user that would like to have a parameter on the manufacturing drawings they send out to the shops that lists the version and maintenance build of Creo that was used to create the file.

We've been hard coding that information on our formats and ignoring the maintenance build.

I'm not sure there is a parameter for this, but I told him I'd ask.

Any ideas?

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

5 replies

R
RandyJones20-Turquoise
20-Turquoise
July 15, 2014
On 07/15/14 15:46, Haigh, David A. wrote:
>
> I have a user that would like to have a parameter on the manufacturing drawings they send out to the shops that lists the version and maintenance build of Creo that was used to create the file.
>
> We've been hard coding that information on our formats and ignoring the maintenance build.
>
> I'm not sure there is a parameter for this, but I told him I'd ask.
>
> Any ideas?
>

jlink and weblink both are capable of extracting the version and build code (the old style year/day format). For example with Creo Parametric 2.0 M110 the following weblink code:

var session = pfcGetProESession();
var version = pfcCreate("MpfcCOMGlobal").GetProEVersion();
var buildCode = pfcCreate("MpfcCOMGlobal").GetProEBuildCode();
alert("Version = " + version + "\nBuildCode = " + buildCode);


Will set the version = "Creo 2.0"
and buildCode = "2014090"

You could create a weblink or jlink app that would set a parameter(s) to these values and no longer have to hard code these values.

> David Haigh
> Phone: 925-424-3931
> Fax: 925-423-7496
> Lawrence Livermore National Lab
> 7000 East Ave, L-362
> Livermore, CA 94550
>
>
> ----------


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
   Fax: 785-667-2695
------------------------------------------------------------------------

K
kevin.brault1-Visitor
1-Visitor
July 15, 2014
It can also be gleaned from the install files and watermarked on the PDF after creation via a batch file executed with the Creo print command.

Let me know if you need details.

Kevin Brault
Sr. Principal Engineer
CAD Administrator
GENERAL DYNAMICS-AIS
________________________________
K
kimndave91-Visitor
1-Visitor
July 15, 2014

I recently saw a batch file that retrieved this information. It was for setting up ProE starting environments, but should be a good basis for this as well. I will look further.


x

K
kimndave91-Visitor
1-Visitor
July 15, 2014

Found where it was in my Wiki.


From communities.ptc.com/message/247275#247275:


Markus Trautner asked I'd like to update my start script for Creo thus that it checks which date code version is installed on the users computer (e.g. M040, M090...)


Is there a general parameter, which i can use to do this?



By FABRICE PEREZ,


hello, we are using a DOS script:(if somebody has a better way...maybe we can do an idea ?


we install Creo in : C:\CAO\appli\Creo 2.0


The script:


SET DRIVE=C:
SET REP_CAO=%DRIVE%\CAO

IF EXIST "%REP_CAO%\Appli\Creo 2.0" SET CREO_INSTALL=%REP_CAO%\Appli\Creo 2.0

SET PARAMETRIC_INSTALL=%CREO_INSTALL%\Parametric
SET COMMONFILES_INSTALL=%CREO_INSTALL%\Common Files



:: *** Récupération du release installé de Creo
PUSHD %COMMONFILES_INSTALL%
FOR /F %%a IN ('DIR /d /b') DO SET RELEASE=%%a
POPD

SET COMMONFILES_INSTALL=%CREO_INSTALL%\Common Files\%RELEASE%



ECHO RELEASE: %RELEASE%
ECHO COMMON FILES: %COMMONFILES_INSTALL%


Martin Hanak includes this background:


Markus,


let us assume that you call something like C:\PTC\Creo 2.0\Parametric\bin\parametric.exe inside your script.


To get Creo Parametric 2.0 date code, look for the name of subdirectory of C:\PTC\Creo 2.0\Common Files directory.


Martin Hanak


x

A
AndyHermanson14-Alexandrite
14-Alexandrite
July 23, 2014

THANK YOU! We have been trying to figure this out for a long time.



Also for those moving to Creo 3.0 here is the new version.



We install to C:\PTC



So the Creo 3.0 folder is install to the above location.



SET DRIVE=C:


SET REP_PTC=%DRIVE%\PTC


IF EXIST "%REP_PTC%\Creo 3.0" SET CREO_INSTALL=%REP_PTC%\Creo 3.0




:: *** Recover Creo install release


PUSHD %CREO_INSTALL%


FOR /F %%a IN ('DIR /d /b') DO SET RELEASE=%%a


POPD


SET CREO_INSTALL=%CREO_INSTALL%\%RELEASE%



SET PARAMETRIC_INSTALL=%CREO_INSTALL%\Parametric


SET COMMONFILES_INSTALL=%CREO_INSTALL%\Common Files



ECHO RELEASE: %RELEASE%


ECHO COMMON FILES: %COMMONFILES_INSTALL%


Terms & ConditionsCookie settingsAccessibility statement