Cancel
Showing results for 
Search instead for 
Did you mean: 

ER: post configurator - add option to use custom procedure for tolerance value

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

I have handed in another enhancement request that I think is useful for other customers, so I post it here to allow other users to create a "me too" IR at GTAC.

Below find the proposal for the "me too" ER.

1. Short Description of desired enhancement: <Problem rather than a solution>
   * It is not possible to calculate the tolerance value for CYCLE 32 on Heidenhain
     or similar for other controllers by custom conditions

2. What activity in your process is the product not able to currently handle?
   * We cannot calculate the tolerance value based on our own source values
   * We cannot use our own machining methods

3. What result are you trying to achieve? (Please provide as many details as possible.)
   * To calculate the tolerance value
     - We want to support our own machining methods
     - We want to use our own source values instead of the tool path tolerances

4. Do you currently have a workaround?
   * No

5. Do you have a proposal for the solution you envision Siemens PLM providing for this capability?
   * Add a similar selection option like other properties have to specify a custom procedure

6. What is the level of productivity gained from such an enhancement?
   * HIGH, fully support the customers needs and environment

7. Other information:
   * Link to existing ER#9220757

Hope more users find this useful to add more control to PC.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX12.0.2, VERICUT 8.2, 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: NX (1876) | AWC 3.4 Preparing: -

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
2 REPLIES 2

Re: ER: post configurator - add option to use custom procedure for tolerance value

Siemens Legend Siemens Legend
Siemens Legend

Hello @Stefan_Pendl,

 

thanks for posting the request here. I agree to the request and it makes sense to have this in the OOTB PC libraries. So thru this ER it should be inside in next library release.

 

Nevertheless there is a workaround to bring that into now. I will try to explain this here in detail because this is a general customization capabilities of Post Configurator and hope this will help for general understanding of the functionality also for other people or other customization in PC.

 

So first step is to use the Buffer view to get the responsible Buffer for output.

extendCycl32_settings.jpg

 

Next step take a look into the Blocktemplate which is used and get the variable name which is used internally in Post Configurator libraries. In general procedures in PC are designed in the way that calculation is doing before the Buffer output command, which means e.g. for this "@CYCL32_1"-Tag that this is only calling the Blocktemplate and all the logic between the properties in the HSC settings is did before in this procedure. So it's possible to jump into this Buffer and implement a logic which will set the variable from the Blocktemplate.

extend_Cycl32_def.jpg

 

In standard libraries there is an option to use the Camtolerance from Operation or Method. It's possible to extend existing properties with more options, e.g. a Custom procedure Smiley Happy.

extend_Cycl32_prop.jpg

To extend existing properties i recommend to take a look into the documentation for the standard library commands.

To set add/ insert a new option use this command.

 

LIB_GE_CONF_set_property_options CONF_CTRL_CYCL32 cycle32_use_camtolerance insert *VALUE* "Custom Procedure" 2

 

One important thing to know is that if you want to have Custom procedure field in the UI of PC use the *VALUE* and the property must be defined as a datatype "COMMANDBLOCK". You can redefine the property datatype with following command:

 

LIB_GE_CONF_set_property_datatype CONF_CTRL_CYCL32 cycle32_use_camtolerance COMMANDBLOCK 0

 

After doing that the UI should now looks like:

extend_Cycl32_prop2.jpg

 

So next step is to implement the logic what should be happen when Custom procedure is selected. First step is to prepend a procedure from the existing CYCL32 output buffer.

 

 

 

LIB_GE_command_buffer_edit_prepend LIB_CTRL_cycle_32 CYCL32 CYCL32_custom_tolerance _customTolerance

 

In this procedure we just ask the value of the property, if 0 and 1 we do nothing because than it should use standard implementation. If the value is default/ Commandblock we want to execute the content. The important command here is the  LIB_CONF_do_prop_custom_proc which allow execution of Tcl code from PC UI.

 

#------------------------------------------------------------
proc CYCL32_custom_tolerance {} {
#------------------------------------------------------------
switch [CONF_CTRL_CYCL32 cycle32_use_camtolerance] {
"0" { }
"1" { }
"default" {
                LIB_CONF_do_prop_custom_proc CONF_CTRL_CYCL32 cycle32_use_camtolerance
                }
}

}

 

That was the base work to extend the property. Now we can put in own logic or call a procedure in the Custom procedure and it will output these values.

 

extend_Cycl32_prop3.jpg

 

If you don't want to extend the property it's also possible to just use the prepend-Buffer and execute your logic for tolerance values and overwrite calculated values. But then you may loose OOTB functionality if a user want to use Operation Tolerance or set the UDE for one operation. With the way above you add additional functionality and keep the origin implementation.

 

 

Best regards

Thomas

 

Re: ER: post configurator - add option to use custom procedure for tolerance value

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

@ThomasJ,

thanks for the detailed description about how to extend the property.

Some of the things shown here are not available with the advanced license level from within the UI.

With PB it would have been possible to add the custom tolerance calculation in the traditional way, but with PC one would at least need access to the debugging properties for buffer and UI ID display to accomplish this.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX12.0.2, VERICUT 8.2, 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: NX (1876) | AWC 3.4 Preparing: -

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