default install in mmNs ..how ?

Hi all,

how can I make that the default install is in millimeter second newton
second ?
Or do something closely after install so I NEVER have to worry about the
wrong units ?

Can I suffice by editing the config.sup ?

Is there a smart solution to this or should I just keep close track of
config.pro files ?

wzzl

 

: Hi all,
:
: how can I make that the default install is in millimeter second newton
: second ?
: Or do something closely after install so I NEVER have to worry about the
: wrong units ?
:

A few revs ago, PTC started distributing Pro/e with start parts, including ones
with units set to mmNs. The names, I believe, are identified this way. They are
located in the <loadpoint>/templates directory. And, in the last couple revs,
they've included several config.pro options that start with TEMPLATE so that you
can tell Pro/e what you want to use when you have the box checked to 'Use default
template'. If you point Pro/e to the start part/assembly you want to use by
default, then always use the default start part, you should never have another
moment of worry over units (unless you get parts from other people.)

David Janes

 

I have this in my config.pro:
pro_unit_length unit_mm
pro_unit_mass unit_kilogram
pro_unit_sys mmns

template_solidpart solid_part_mmns.prt
template_designasm mmns_asm_design.asm
template_drawing a1_drawing.drw

But how do I know for sure Pro-e is actually *using* this file.
I mean, I know I should check this, but I want to make this as
monkey-proof as possible to prevent out=r trainees working in the wrong
units.

my two cents: if anything needs to be fixed in wildfire it is a good and
monkey-proof system to differntiate between metric and imperial units.
I have seen colleagues break stuff around the office while screaming
"what the f888 ! @#$%^&^%$#" when trying to deal with this stuff.

I mean, if autocad can get it right ( I have thrown similar fits over
acad's stupidity esp. boundary hatches ) , I mean...... c'mon.. AUTOCAD
gets it right.. autocad...


wzzl

 

: > David Janes wrote:
:
: > : Hi all,
: > :
: > : how can I make that the default install is in millimeter second newton
: > : second ?
: > : Or do something closely after install so I NEVER have to worry about the
: > : wrong units ?
: > :
: >
: > A few revs ago, PTC started distributing Pro/e with start parts, including
ones
: > with units set to mmNs. The names, I believe, are identified this way. They
are
: > located in the <loadpoint>/templates directory. And, in the last couple revs,
: > they've included several config.pro options that start with TEMPLATE so that
you
: > can tell Pro/e what you want to use when you have the box checked to 'Use
default
: > template'. If you point Pro/e to the start part/assembly you want to use by
: > default, then always use the default start part, you should never have another
: > moment of worry over units (unless you get parts from other people.)
: >
: > David Janes
: >
: >
:
: I have this in my config.pro:
: pro_unit_length unit_mm
: pro_unit_mass unit_kilogram
: pro_unit_sys mmns
:
The above comes into play only when a user doesn't use a start part where the
units are actually embedded. I guess the first step would be to confirm that the
start parts have the correct units.

: template_solidpart solid_part_mmns.prt
: template_designasm mmns_asm_design.asm
: template_drawing a1_drawing.drw
:
Hopefully, the values for the options like template_solidpart, include the full
path string. Otherwise you can't be sure where users are finding these parts.
'Unofficial' copies could be stored on their local drives and be found instead of
the official ones. The full path string gives you some assurance that they are
only finding the corporate standard parts.

: But how do I know for sure Pro-e is actually *using* this file.
: I mean, I know I should check this, but I want to make this as
: monkey-proof as possible to prevent out=r trainees working in the wrong
: units.
:
Some monkey-proofing points:
* To repeat, use full path strings for options pointing to files.
* Place the critical options in config.sup and lock the file/folder against write
access by anyone but sysadmin.
* Make sure start parts are not pointed to in any other config.pros on the system;
as soon as you make start parts user customizable, you open a door to error and
confusion.
* Make sure people are using the default start parts, in other words, that the
infinite inventiveness of Pro/e users is not being applied to defeating a very
workable system, even if only inadvertently.
* User instruction, published procedures, clear and unambiguous standards.

David Janes

 

Full paths are impractical when using pro/e win32 and pro/E linux
together => find config.sup edit each install

Thanks anyway for the pointers though

wzzl

 

If you have ModelCHECK, it can be configured to check the units of your file
against a list of acceptable units. Configure this check to report it as an
error and the user will always be flagged when a file does not have the
correct units.

Ron