Cancel
Showing results for 
Search instead for 
Did you mean: 

.def file with conditional entries (e.g. dbc_tool_ascii.def)

Genius
Genius

Hi,

 

in my environment we have about 27 different departments. In order to support them with a tailored CAM environment we have customized a lot.

 

There is now the topic of holder systems (e.g. SK40, HSK63).

 

Certain holder systems are just available in some departments. I would like to customize the environment in a way that a user can just choose the holder available in his department.

 

Instead of loading different files from different locations (controlled by environment variables), I would like to know if it is possible to source e.g. a statement like

 

DB_ALIAS Holder

{

   DB_ID    HLD

   DB_ID_TYPE   s

   OPTIONS „All“ „SK40“ „SK50“ „HSK63“   „NONE“

    ...

}

 

from another file to dbc_tool_ascii.def ?

 

What is a def file anyway? Is it somehow linked to tcl?

 

Thanks for your replies.

 

Best wishes,
Joachim

In production NX 12.0.1.7 D2
In testing NX 12.0.1.7 MP4
11 REPLIES

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I have resolved this by duplicating the DEF files and edited the entry for it in the configuration file.

  • dbc_mrl_tooling_library_tlas_english.def
  • dbc_mrl_tooling_library_tlas_english_AT_NB.def
  • dbc_mrl_tooling_library_tlas_english_AT_NB_HSK100A.def
  • dbc_mrl_tooling_library_tlas_english_AT_NB_HSK50A.def
  • dbc_mrl_tooling_library_tlas_english_AT_NB_SK50.def
  • dbc_mrl_tooling_library_tlas_english_AT_SB.def
  • dbc_mrl_tooling_library_tlas_english_AutoDMU80.def
  • dbc_mrl_tooling_library_tlas_german.def
  • dbc_mrl_tooling_library_tlas_german_AT_NB.def
  • dbc_mrl_tooling_library_tlas_german_AT_NB_HSK100A.def
  • dbc_mrl_tooling_library_tlas_german_AT_NB_HSK50A.def
  • dbc_mrl_tooling_library_tlas_german_AT_NB_SK50.def
  • dbc_mrl_tooling_library_tlas_german_AT_SB.def
  • dbc_mrl_tooling_library_tlas_german_AutoDMU80.def

DEF files for post-processors support an include directive, but I have not seen this for other DEF files.

 

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Genius
Genius

Hi Stefan,

 

right. I forgot the cam config file. With that I can at least point to a department specific dbc_tool_ascii.def file.

 

Thanks for the idea!

Best wishes,
Joachim

In production NX 12.0.1.7 D2
In testing NX 12.0.1.7 MP4

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Make sure to get a file difference checker, so you can easily apply common changes to all the duplicates.

I would be lost without this tool.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Genius
Genius
I have that, but don’t want to remember I have to maintain several files with almost the same content.
Best wishes,
Joachim

In production NX 12.0.1.7 D2
In testing NX 12.0.1.7 MP4

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I will create a report at GTAC to get an answer if there is an include directive possible for dbc (Data-Base-Connector) DEF files.

If not, an ER can be created and I will post the result of the request here.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Siemens Valued Contributor Siemens Valued Contributor
Siemens Valued Contributor

Hi!

 

If you manage your tools in Teamcenter Resource Manager, you can define site specific attributes.

There is a "Search by site" functionality. Sites can be different plants and can be also different groups in the same plant.

Perhaps this could be also an idea...

 

So long...

 

   Markus Dietz

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

We do use MRL and also plants and machine groups, but we don't want to have users forced to always select the correct plant and machine group.

Currently I have one DEF file for each plant and one additional DEF file for each machine group inside the plant.

It would be much easier, if one could specify a default query for the tool class through an environment variable in ugii_env.dat

This query would contain the plant, machine group and machine adapter for each department or machine operator in our case.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Siemens Valued Contributor Siemens Valued Contributor
Siemens Valued Contributor

I agree. This would be a nice enhancement.

I'll put it on our project candidates list.

 

We also plan to start using Active Workspace in the future - also for retrieving tools in NX CAM.

AFAIK it is possible to have user specific predefined queries there.

Perhaps this could help us...

 

So long...

 

   Markus Dietz

Re: .def file with conditional entries (e.g. dbc_tool_ascii.def)

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I have opened ER#9034502 - add support to pre-define tool query values, see ER text below.

                            ER Template
                            -----------

* Short Description of desired enhancement: <Problem rather than a solution>
    it is not possible to specify the default plant, machine group, machine adapter, etc. for a tool query for separate departments

* What activity in your process is the product not able to currently handle?
    NX doesn't provide a simple way to specify a default tool query to handle multiple plants, machine groups, machine adapters, etc. for separate departments
    within one NX configuration

* What result are you trying to achieve? (Please provide as many details as possible.)
    we want to avoid to force the user to have to always select the plant, machine group, machine adapter, etc. if there are multiple possibilities

* Do you currently have a workaround?
    the only way to support this is to duplicate the CAM configuration and tool class definition files,
    but this is cumbersome when it comes to maintaining changes that affect all departments and plants

* Do you have a proposal for the solution you envision Siemens PLM providing for this capability?
    No

* What is the level of productivity gained from such an enhancement?
    HIGH, better usability for the regular and administrative user

* Other information:
    None

If you see value in this enhancement, feel free to ask GTAC to be added to the ER.

The request for the include feature is still open.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Learn online





Solution Information