NX Using the native ASCII device database in managed NX

When running NX managed with TC, users are able to use the native libraries for tools, machines, and devices.  How does the device library work in this environment?

Devices, like tools, use a straightforward name match.  The same device_database.dat file can be shared between native and managed NX. 

The library reference code of the item in the device_database.dat file is matched to the kinematics .prt file of the device so NX knows what data to retrieve when the device is loaded.  In native NX, the software looks for the matching prt file in the \MACH\resource\library\device\graphics\ folder, and in managed NX, the software simply looks for any item ID in Teamcenter that matches the libref string and retrieves the associate prt file.

Best practice is to get the devices all set up and working correctly in native NX, and then import the prt files from the device \graphics folder into Teamcenter so they are findable when using the device library.  The import should set the item type to 'Resource' and use the prt filename as the item id to ensure that the new item in teamcenter gets the same libref code as the line item in the device_database.dat file.

In the sample case here, a specific destination folder was created in Teamcenter to store the device files in a single organized spot, but this is not required.