Pro/ENGINEER Interview Questions with Answers # 6

1. Name six common assumptions the sketcher will make.

Ans: Six common assupmption the sketcher will make are as follows - Horizontal and vertical, equal length lines, equal radius or diameter, co-linearity, 90 and 180 degree arcs, points on the same horizontal or vertical, points on other entities, tangency, symmetry, parallel and perpendicular lines.

2. What is the difference between One Side and Both Sides in extrusion?

Ans: One-side extrudes only one specified direction from the sketching plane. Both sides extrudes both sides of the sketching planes.

3. How do you change dimensions of a feature?

Ans: Modify > pick the feature > pick the dimension > enter the new value > select regenerate.

4. What is the model tree?

Ans: The model tree is a graphical representation of the features and/or components in the model.

5. Define "Parametric Feature Based Modeling" ?

Ans: Parametric means driven by parameters. Feature based means you define a series of instructions (features) to tell the system your design intent. Modeling means creating computer images coupled with geometric information defining a part or assembly.

6. What is datum planes created ‘on the fly’?

Ans: The datum plane created on the fly means it was created when you were in the middle of creating something else and it goes away after the thing you really wanted was created. These are created using the 'make datum' command.

7. List five uses of datum planes.

Ans:  Five uses of datam plane are as follows - Sketching plane, reference plane, dimension and alignment references, geometric tolerancing, creating cross sections.

8. List three uses of datum axes.

Ans: Three uses of datum axes are as follow - Dimension and alignment references, centerlines on drawings, geometric tolerancing, coaxial hole.

9. List two uses of a datum coordinate system.

Ans: Datum coordinate systme is used While exporting to iges and stl.

10. Name a feature that can both add and remove material.

Ans: Rounds and chamfers are the features which can both add or remove the material.

Pro/ENGINEER Interview Questions with Answers # 5

26 Where does Pro/ENGINEER save part files that are assembled from a directory different than the current working directory?

Ans : By default, Pro/ENGINEER will store objects that are assembled from other directories back to the directory of origin. If the user does not have write access to the directory, Pro/ENGINEER will not store the objects in the current working directory, unless specific config.pro options have been set. The config.pro options "override_store_back" and "save_object_in_current" allow greater control over this type of situation.

27 What happens during storage of an assembly if its dependent part files are located in a write-protected directory?

Ans : By default, Pro/ENGINEER will only store modified objects and will always store objects back to the directory from which they were retrieved. Therefore, if a part from a write protected directory has been modified and File, Save is selected, Pro/ENGINEER will not be able to save the object unless the config.pro options "override_store_back" and "save_object_in_current" are utilized.

28 Why can't an assembly be retrieved after clearing it from memory or after starting a new session of Pro/ENGINEER?

During assembly creation, it is possible to add components to the assembly that are located in directories other than the current working directory. When the assembly is saved, the assembly file is saved to the current working directory while modified components are saved back to the directories of origin. If the assembly is cleared from workstation memory by either exiting Pro/ENGINEER or by selecting File, Erase, and selecting all the objects in the ERASE dialog box and then retrieved, it is possible that Pro/ENGINEER will not be able to locate certain components. The config.pro option "search_path" can be used to specify directories which Pro/ENGINEER will search for objects. The config.pro file must contain a separate "search_path" option for each directory to be searched. Refer to the Configuration Options section of the Pro/HELP for details.

29 How does File, Save As function in Assembly mode?

In Assembly mode, the File, Save As functionality allows any or all members of the assembly to be copied.

By default, after selecting File, Save As, a dialog box will appear with the name of the assembly to be copied specified next to Model Name. The new assembly name is specified on the next line (New Name). After selecting OK, a check mark can then be placed next to each assembly component to be copied or Include all subcomponents can be selected to copy all assembly components.

If a check mark is placed next to any of the components or if Include all subcomponents is selected, Pro/TABLE will be displayed where new component names can be specified in the cell adjacent to the original.

If OK is selected without selecting a component or Include all subcomponents, Pro/ENGINEER will create only a copy of the assembly which references the original components.

The config.pro option "model_rename_template" is used to create a user defined renaming scheme.

Refer to the Configuration Options section of the Pro/HELP for further information.

30 Why do parts intersected by assembly features require renaming before they can be stored?

Ans : Assembly features which intersect assembly components alter the geometrical intent of the original object. When the assembly is in session, the component exists in memory in two different states. When Pro/ENGINEER tries to save the assembly, it is unclear which state of the component is to be saved. Pro/ENGINEER will prompt the user to save the object with a new name. This will create a copy of the object containing the geometric result of the assembly feature.

31 What does the config.pro option "override_store_back" do?

If the config.pro option "override_store_back" is set to "yes", Pro/ENGINEER will save objects retrieved from other directories to the current working directory;

If "override_store_back" is set to "no", which is the default, objects will be saved in the directory of origin. If the option is set to "no" and the user does not have write access to the directory of origin, Pro/ENGINEER utilizes the config.pro option "save_object_in_current".

32 What does the config.pro option "save_object_in_current" do?

When the config.pro option "save_object_in_current" is set to "yes", Pro/ENGINEER will save objects to the current working directory if the user does not have write access to the directory from which the object was originally retrieved. If the option is set to "no", Pro/ENGINEER will not save the object at all. This option should be used in conjunction with the config.pro option "override_store_back".

33 What is the preferred method to make a copy of an assembly?

The File, Save As functionality is the best way of copying assemblies.

34 What is the preferred method to rename assembly components?

The following procedure should be used to rename assembly components:

Retrieve the assembly which contains the components to be renamed

In a sub-window retrieve the component to be renamed

With the component active, select File, Rename and enter the new component name

Select Window, Activate and pick in the window containing the assembly

Regenerate the assembly

Select File, Save to save the assembly which contains a reference to the new component name.

35 what is the preferred method to rename a drawing?

The File, Rename functionality should be utilized to rename a drawing

Pro/ENGINEER Interview Questions with Answers # 4

17 Does Pro/ENGINEER over write existing objects when saving to disk? What does the object version number indicate?

Ans: Pro/ENGINEER will not overwrite existing objects while saving to disk. Objects are saved to disk with an object version number after the file extension. Pro/ENGINEER will create a new object file each time the object is saved, monotonically increasing the version number each time.

The object version number indicates the number of times the object has been stored. Objects are saved to disk with an object version number after the file extension. Example: A part called valve.prt will be initially written to disk as valve.prt.1. Subsequent storage of this object will result in the files valve.prt.2. valve.prt.3, etc. If the directory is purged, the object with the highest version will remain.

When a top-level object is retrieved (for example, an assembly drawing), it always retrieves the most recent version of the assembly and its parts. Therefore, the version of the drawing does not necessarily have to have the same version number as the part or assembly. This will frequently be the case when several different users are working on the same files.

This wouldn't cause a problem unless a user deletes or redefines a feature that is used as a reference by some other object. For example, if a feature is deleted from a part that is used for assembling another component in an assembly, then that component will fail placement when the assembly is retrieved, and must be redefined. Another example is when planar surfaces are used to orient the model in a drawing view, and the feature is then deleted or suppressed. This will result in the message, "model geometry for drawing view is missing", and the view will revert to an isometric orientation, and must be re-oriented (using the default datum planes to orient the views whenever possible will help to prevent this).

The best method for avoiding these situations is to use a database management product that will manage revision changes made to parts/assemblies/drawings. Without a system like this, any user can change any model, regardless of what other users are doing.

18 Does Pro/ENGINEER offer an auto-save function?

Auto-save functionality is not currently implemented in Pro/ENGINEER. The "prompt_on_exit" config.pro option can be utilized to prompt the user to save objects in session before exiting Pro/ENGINEER.

19 What happens if I run out of disk space while saving my objects?

If available disk space is depleted during storage, Pro/ENGINEER will issue the message: object name could not be saved: Check disk space or write access. Error in storage. Check previous message (then press Enter):"Pro/ENGINEER will not save any portion of the object to disk. Disk space must be made available before the object can be saved.

20 What is the difference between File, Erase and File, Delete?

File, Erase removes the object from workstation memory. The object is not removed from disk. File, Delete removes either old versions or all versions of the object and all associated objects from disk. It is recommended to approach this menu selection with a great deal of caution. Creating backup copies of Pro/ENGINEER objects is considered good practice and can reduce the effect of accidental removal of data.

21 Why is the following message given: "PDM database object must be renamed by Pro/PDM application"?

By default, Pro/ENGINEER will not allow Pro/PDM objects to be renamed within Pro/ENGINEER. The config.pro option "let_proe_rename_pdm_objects" set to "yes" will allow Pro/ENGINEER to rename Pro/PDM objects.

Warning: Objects renamed in Pro/ENGINEER will be considered new Pro/PDM objects when submitted back to a Pro/PDM database.

22 Why aren't part files saved when File, Save is selected in Sketcher?

While in Sketcher, the File, Save functionality will save the section to disk rather than the part file. This functionality allows sections to be stored to disk for future use in feature creation. Section files are saved to disk with a .sec file extension. Once Sketcher is exited by either completing the feature creation or quitting, File, Save will save the part file to disk.

23 How is family table instances stored to disk?

All family table instance information is stored within the generic model.Pro/ENGINEER does not save a unique object file to disk for each instance.

24 How can copies of a part be created?

Ans : The File, Save As functionality allows copies of part files to be created using the following technique: Select File, Save As. Pro/ENGINEER will open a Save As dialog box. The current object in memory will be the default object to copy (in the Model Name section of the dialog). The name of the new object is specified in the New Name line in the dialog.

25 Does Pro/ENGINEER save all components each time an assembly is saved?

Ans : By default, Pro/ENGINEER does not store all assembly components to disk upon each File, Save operation. Instead, Pro/ENGINEER will save the assembly file and only components that have been modified. By setting the config.pro option "save_objects", this can be changed. By using this option, Pro/ENGINEER can be instructed to save all dependent objects, save only the objects that were modified, or save modified objects and objects specified by the user. 

Pro/ENGINEER Interview Questions with Answers # 3

9 Is there a limitation on the number of characters that can be included in a config.pro entry?

Ans: Each line in config.pro is limited to 80 characters. Environment variables can be used to specify config.pro "search_path" values containing more than 80 characters. Refer to Configuration Options in Pro/HELP for details.

10 Where are Pro/ENGINEER objects stored when File, Save is selected?

By default, Pro/ENGINEER objects will be stored to the current working directory. If the working directory is changed using File, Working Directory, Pro/ENGINEER objects will be saved to the new directory. If a Pro/ENGINEER object is retrieved from a directory other than the current working directory, Pro/ENGINEER will save the object back to the directory from which it was retrieved. If the user does not have write permission in that directory, the object will not be saved unless the config.pro option "save_object_in_current" is set to "yes".

11 What does File Save As do?

File - Save As will make a copy of a specified Pro/ENGINEER object using a new name. List the object that is to be copied in the Model Name space in the Save As dialog box, the current object being the default. In the New Name space, a new file name should be specified. Pro/ENGINEER will create this object in the current working directory.

12. what does File, Backup do?

File, Backup can be used to save Pro/ENGINEER objects to a specified directory. The object will be saved in the specified directory using the original filename(s).

File, Backup in Assembly, Drawing, or Manufacturing modes will save all related objects to the specified directory.

13 what does File, Rename do?

File, Rename is used to change the name of Pro/ENGINEER objects in memory and on disk. Pro/ENGINEER will rename all versions of the object being renamed.

When renaming an object that was retrieved from directory other than the current working directory, the renamed object will be saved in the directory from which the object was retrieved.

14 what does File, Erase, Current do?

File, Erase is used to clear the specified object from workstation memory. This functionality will not remove objects from disk. Objects referenced by an active assembly or drawing can not be erased. A list of objects in the current model will then be displayed. Only the current top level model (i.e. assembly or drawing) can be erased, and selected objects as well.

15 what does File, Erase, Not Displayed do?

Ans: File, Erase, Not Displayed is used to erase all objects from the current session, except for those that are currently displayed and any objects referenced by the displayed objects. For example, if an assembly instance is being displayed at the time Erase, Not Displayed is selected, the instance, the instance's generic, and it's components will not be erased. There is a config.pro option related to File, Erase, Not Displayed called "prompt_on_erasenotdisp".

yes (default) - a message window for each eligible object in question appears, asking if you want to first save the object before it is erased.

no - the system will immediately erase all eligible objects.

16 What does File, Instance Operations do?

File, Instance Operations will save a particular instance of a part or assembly in a separate file called an " instance accelerator file" (suffix ".xpr" for a part, ".xas" for an assembly). This file is used to retrieve particular instances quickly from disk rather than having to first retrieve the generic into memory, selecting the particular instance according to the family table, and then regenerating. Therefore, with this functionality the amount of time that it takes to retrieve an instance of a part or assembly from disk can be considerably reduced. The trade off is that more disk space will be used to store the accelerator files. When File, Instance Operations is selected, the INST DBMS menu appears with the following options

InstIndex - create or update the Instance Index file for a specified directory

pdate Accel - create or update accelerator files for all instances currently in session

Purge Accel - examine each instance accelerator file and delete it if it is not current with

SaveAccelEnv - brings up the SV INST ACC menu When SaveAccelEnv is selected the SV INST ACC menu appears with the following options:

none (default) - the system does not save the instance in a file separate from the model.

always - the system always saves the instance in a separate file

explicit - the system saves the instance in a separate file only. When the instance is explicitly saved.

The config.pro option "save_instance_accelerator" can also be used to control instance accelerator files. The values for this config.pro option are also none (default), always, explicit. When you bring up the SV INST ACC menu, one of the options will be highlighted to reflect the last setting. That setting could have been either loaded from a configuration file or selected previously from this menu. 

Pro/ENGINEER Interview Questions with Answers #2

1 What is the maximum number of characters allowed in a Pro/ENGINEER object name?

Thirty one (31) characters can be used in Pro/ENGINEER object names. This number does not include the extension, i.e., .prt, .asm, .drw, or the object version number, i.e., .1, .2, .3. 

2 .Can upper case characters be used in Pro/ENGINEER object names?

Upper case characters cannot be specified in Pro/ENGINEER object file names. Upper case characters can be specified during object creation, however, the file will be written to disk using lower case characters only.

3 what is the reason for using a config.pro file?

The config.pro file is used to control the environment in which Pro/ENGINEER runs. There are over 150 available options which allow control of a variety of different aspects, ranging from model display to default units to search paths used to retrieve assembly components.

4 is a default config.pro file created when Pro/ENGINEER is installed?

When Pro/ENGINEER is initially installed, there is no default config.pro file that is created automatically. However, a large number of the options do have default values which are used unless the option setting is changed in a config.pro file. The Configuration Options section of Pro/HELP lists the default config.pro option values in italics. There are two methods that can be used to create a config.pro file. The first method is to utilize any text editor, vi for example, and manually create the file. Each option should have its own line in the file, with the format being {Option Value}. The second method is to use the Preferences dialog box within Pro/ENGINEER, which can be accessed by selecting Utilities, Preferences... When you exit the dialog box, the config.pro file will be written to your local directory. See the Suggested Technique for Using the Preferences Dialog Box for a detailed description of the functionality for this new dialog.

5 Where does Pro/ENGINEER look for config.pro files?

Pro/ENGINEER looks for config.pro files in 3 different directories in the following order:

1) load point/text

Config.pro files residing in load point/text will be read first.

2) The user's home directory

With UNIX systems, Pro/ENGINEER will read the config.pro file in the user's home directory. This is most commonly used for specifying user customized config.pro options such as colors and mapkeys.

3) Working directory

The directory in which Pro/ENGINEER starts is searched for a config.pro file.

If the same option appears in more than one config.pro file, the one that was read last will be utilized by the system.

6 After config.pro is edited, why aren't the changes reflected?

After config.pro is edited, the Add/Change and Apply buttons must be selected in the Preferences dialog box in order for the modifications to be reflected in the Pro/ENGINEER session, or Pro/ENGINEER can be restarted. Be aware that some config.pro options require Pro/ENGINEER to be restarted in order for config.pro modifications to be reflected.

7 After config.pro is edited, is it necessary to restart Pro/ENGINEER?

After config.pro is edited, the Apply button must be selected in the Preferences dialog in order for the modifications to be reflected in the Pro/ENGINEER session, or Pro/ENGINEER can be restarted. Modifications to the following config.pro options require Pro/ENGINEER to be restarted.

8 what is the difference between config.pro and config.sup?

There are two main differences between config.pro and config.sup.

Unlike config.pro, config.sup can only be located in the load point/text directory.

Config.sup options cannot be overridden by options found in any other config.pro. Also, items contained in the config.sup can only have one entry per option. Keeping this in mind, it is important that items which can have multiple entries, such as "mapkey", "search path", and "def_layer" are not specified in config.sup.