ISV Building up a simulation scenario

Step 3: Adding the machine to the machine database

Since we want to try multiple setup scenarios including work part and tooling it is recommended to add the machine to
the current machine database. Prior to this step we should have a general look at the organization of the files and the
file content.
There is a central database file which tells NX where the machines are located, what type they are and where to look
for additional files. This file is named machine_database.dat and located in
\Program Files\UGS\NX 7.5\MACH\resource\library\machine\ascii\machine_database.dat

the file content will be explained later when we create the example.

Figure: Find the file machine_database.dat to enter the new machine tool into the ASCII library

Up to NX 4 and older versions the additional files which belong to a machine had been placed at different locations in
the NX subdirectories. From NX 5 this policy was changed so that all files which belong to specific machines should be
placed in one subdirectory nearby the main machine prt file.
A sample structure is shown below:

\resource\library\machine\installed_machines\my_sample_machine
my_sample_machine.dat
graphics
main machine prt file including kinematics
additional geometry files
optional main raw machine file without kinematics
postprocessor
my_sample_machine.def
my_sample_machine.pui
my_sample_machine.tcl
ma_sample_machine_vnc.tcl

Note: This subdirectory can include several subfolders for several controllers as done for the sample machine tool, but
this is normally not the case for a customer machine tool
cse_driver
fanuc

fanucFamily.ccf

my_sample_machine.mcf

my_sample_machine-Main.ini

subproc
Subprograms and cycle in NC code format(e.g. for the tool mount process)
prg files for the fanuc control
user_defined_event (optional if needed)
vnck (optional if needed)

ISV_Create_CSE_Simulation_Senario.doc 20. February 2012 Page 15 of 24

ISV Building up a simulation scenario

documents (optional if needed)

The files in the graphics subdirectory are self-explanatory.

The files in the postprocessor subdirectory are belonging to the postprocessor and could have been created using
the post builder application.
The files in the cse_driver directory are belonging to the driver of the Common Simulation Engine which is the current
and future platform of NX and REAL NC applications. The files in this subdirectory are mostly binary type and cannot
be created by the user. Hence, they have to be copied from another directory which describes the current machine
and comes with the default NX installation. Identify the machine axes type (e.g. A, B, C or combination) and copy an
appropriate subdirectory from the standard machine directory.
The entire data structure is shown below.

Figure: Overview of the NX installed machine tool data structure

The file CSE_demo_machine.dat is the post configuration file and has to be created by the user. An example is given
below.
Lets make a complete setup for the current machine:
If not already done create empty subdirectories for postprocessor and cse_driver.
Copy the postprocessor related files into that directory.
Identify the machine configuration of your machine tool. In our case it is a BC axis type. Locate the appropriate
machine type in the table of installed machines which are coming with the OOTB NX installation. Here we are
selecting sim06_mill_5ax (Wich has BC configuration too). Copy the fanuc subdirectory (assume we are targeting
a fanuc post and driver) of this machine from the path \installed_machines\sim06_mill_5ax\cse_driver to your local
machine path.

ISV_Create_CSE_Simulation_Senario.doc 20. February 2012 Page 16 of 24

ISV Building up a simulation scenario

Figure: List of OOTB machine tool configurations

You have to rename the following files to be in sync with the machine definition file. Rename:
sim06_mill_5ax_fanuc_in.MCF CSE_Demo_Machine_tool.MCF
and
sim06_mill_5ax_fanuc-Main.ini CSE_Demo_Machine_tool-Main.ini
(Make sure not to have other hyphens than before the keyword Main otherwise the ini file will be misinterpreted and
you get an error message.)
The string Main indicates the name of the channel of this INI file. All single channel machine tools installed with NX
use the name Main for this one channel. The name of the channel is stored inside the MCF file.
FanucFamily.ccf and the subprog files remain unchanged.
Create the file CSE_demo_machine_tool.dat using an editor. This file looks as follows:

Figure: Content of the CSE_demo_inch.dat file pointing to the postprocessor and the cse fodler

The file items are explained below:

Header:
##########################################################################
# CSE Demo post config file - Event Handler and Definition file
###########################################################################

the machine name as it appears in NX. Any name can be given here
CSE_Demo_Machine_Tool,

The path where to find the postprocessor tcl file.

${UGII_CAM_LIBRARY_INSTALLED_MACHINES_DIR}
CSE_demo_machine_tool\postprocessor\fanuc\sim06_mill_5ax_fanuc_mm.tcl,

The path where to find the postprocessor definition file.

ISV_Create_CSE_Simulation_Senario.doc 20. February 2012 Page 17 of 24

ISV Building up a simulation scenario

${UGII_CAM_LIBRARY_INSTALLED_MACHINES_DIR}
CSE_demo_machine_tool\postprocessor\fanuc\sim06_mill_5ax_fanuc_mm.def

In a new line - The path where to find the driver for the common simulation engine.
CSE_FILES, ${UGII_CAM_LIBRARY_INSTALLED_MACHINES_DIR}
CSE_demo_machine_tool\cse_driver\fanuc\CSE_demo_machine_tool.MCF

Add the machine tool to the library

Finally we have to add an item to the machine database file. Move to the appropriate directory
\Program Files\UGS\NX 7.5\MACH\resource\library\machine\ascii\machine_database.dat
Make a copy of the default database file and open it using an editor. The additional data record should look like this:

Figure: Content of the machine_database.dat file after adding the new machine tool

The record items are explained below:

Header:
# CSE_Demo_example

(Fields divided by the | sign)

Format specifier
DATA|

unique record identifier. It is a common practice to add the controller type and the units to the name.
sim06_mill_5ax_fanuc_mm|

Machine type 1= Mill machines

1|

Short description
CSE Demo|

Name of the machine tool manufacture

None| or Manufacturers name

Name of the controller

Ex:| Controller name e.g. Fanuc

Path to the configuration file name (it must exactly match the location and name)
${UGII_CAM_LIBRARY_INSTALLED_MACHINES_DIR}
CSE_demo_machine_tool\CSE_demo_machine.dat|

Rigidity factor
1.000000|

Geometry of the kinematics machine tool prt file

${UGII_CAM_LIBRARY_INSTALLED_MACHINES_DIR}
CSE_demo_machine_tool\graphics\CSE_demo_machine_tool

Here the copy of the description inside the file

ISV_Create_CSE_Simulation_Senario.doc 20. February 2012 Page 18 of 24

ISV Building up a simulation scenario

## LIBRF - unique record identifier

## T - Machine type - 1-Mill machines
## - 2-Lathe machines
## - 3-Wedm machines
## - 4-MillTurn machines
## - 9-Mixed machines
##
## MNF - Manufacturer
## DESCR - Short description ( for example 3 Axis Mill)
## CNTR - indicating the controller of the machine
##
## POST - the configuration file name with the list of
## postprocessors for this machine
## (The path will be found from the search path environment variable)
## RIGID - Rigidity factor to apply to data from the machining data library
## This will normally be a number less than or equal to 1.0
## GRAPHICS- Geometry of the kinematic machine tool prt file
## (The full path needs to be included)

ISV_Create_CSE_Simulation_Senario.doc 20. February 2012 Page 19 of 24