The software fails to enter the managed manufacturing application. NX displays a message to the user that says simply "An invalid file is specified, for a keyword."
The log file will report something like:
+++ An invalid file in c:\Apps\Siemens\NX2206\mach\resource\configuration\cam_part_planner_mrl.dat,
c:\Apps\Siemens\NX2206\mach\resource\library\tool\inclass\dbc_mrl_tooling_library_tlas_en.def does not exist for key word LIBRARY_TOOL
The OOTB cam installation contains a managed cam configuration file that will generate errors and stop NX from entering the manufacturing application if MRL is not installed.
By default, the NX installation includes the ...\MACH\resource\configuration\cam_part_planner_mrl.dat configuration file. This file includes pointers to MRL 'inclass' scripts for the tool, device, and machine library keywords, e.g.
LIBRARY_TOOL,${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_mrl_tooling_library_tlas_en.def,${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_mrl_tooling_library_tlas.tcl
These scripts do not exist in the standard NX installation. If the site is not running MRL with TC, the software fails when trying to validate this cam configuration and it will not enter the managed manufacturing application. NX displays a message to the user that says simply "An invalid file is specified, for a keyword."
The log file will report something like:
+++ An invalid file in c:\Apps\Siemens\NX2206\mach\resource\configuration\cam_part_planner_mrl.dat,
c:\Apps\Siemens\NX2206\mach\resource\library\tool\inclass\dbc_mrl_tooling_library_tlas_en.def does not exist for key word LIBRARY_TOOL
If the site is running MRL, then these \inclass folder scripts will exist because the MRL installation includes a specific step to populate the NX installation with the tcl files from the MRL install media.
If the site is not using MRL, they have to implement one of a few workarounds right out of the gate in order to get around this failure and allow the software to function:
- manually rename/delete the cam_part_planner_mrl.dat configuration file so NX can't see it to try and validate the contents. Just change the file extension to something other than ".dat", e.g. ".notdat"
- manually copy the proper scripts to the library \inclass folders as per the notes in the ...\MACH\resource\library\tool\inclass\mrl_readme.txt and similar files
This was reported as PR 10679383, which has been fixed for the NX2306.4000 release. Only NX releases prior to this version should need this workaround.