Cancel
Showing results for 
Search instead for 
Did you mean: 

Roughness mapping rule

Builder
Builder

Hi,

 

I would like to create 2 mapping features which belogs to STEP2POCKET_THREAD.

So I created 2 mapping rules for each mapped feature.

 

#1 The first mapping rule contains following function:

roughness_value(in.SIDE_ROUGHNESS_1.ALLOWANCE) <= 25 OR

roughness_value(in.SIDE_ROUGHNESS_1.DIRECTION_OF_LAY) <= 25 OR

roughness_value(in.SIDE_ROUGHNESS_1.PROCESS) <= 25 OR

roughness_value(in.SIDE_ROUGHNESS_1.ROUGHNESS_VALUE) <= 25 OR

roughness_value(in.SIDE_ROUGHNESS_1.ROUGHNESS_CUTOFF) <= 25

 

#2 the second mapping rule contains the same function just with > 25

 

What I want is, when one of the roughness values is defined, the feature can be recognized.

My values are assigned to the right attributes #1 Rz 16 and #2 Rz 30, but my feature is not assigned to the mapping rule #2

 

snip_20170629140211.png

 

 

 

 

 

 

 

I think it is beacause some Attributes are not defined, so there the condition is not right or wrong...

is there a way to solve this ?

 

Hope you can help me, thank you Smiley Happy

NX 11.0.1.11
7 REPLIES

Re: Roughness mapping rule

Esteemed Contributor
Esteemed Contributor

The easiest is to have no custom attributes without a default value, which is a value that one would never apply to it regularly.

In addition there is a syntax error, since the attribute names don't contain dots, there are only underscores, see your posted image.

If this is no option then you need to use the is_defined() function to check for the existence of the attribute:

(is_defined(in.SIDE_ROUGHNESS_1_ALLOWANCE) AND roughness_value(in.SIDE_ROUGHNESS_1_ALLOWANCE) <= 25) OR
(is_defined(in.SIDE_ROUGHNESS_1_DIRECTION_OF_LAY) AND roughness_value(in.SIDE_ROUGHNESS_1_DIRECTION_OF_LAY) <= 25) OR
(is_defined(in.SIDE_ROUGHNESS_1_PROCESS) AND roughness_value(in.SIDE_ROUGHNESS_1_PROCESS) <= 25) OR
(is_defined(in.SIDE_ROUGHNESS_1_ROUGHNESS_VALUE) AND roughness_value(in.SIDE_ROUGHNESS_1_ROUGHNESS_VALUE) <= 25) OR
(is_defined(in.SIDE_ROUGHNESS_1_ROUGHNESS_CUTOFF) AND roughness_value(in.SIDE_ROUGHNESS_1_ROUGHNESS_CUTOFF) <= 25)

As you see attributes without a default value are making things really complex :'(

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Re: Roughness mapping rule

Builder
Builder

Hi, 

 

thank you for your solution, I will check it soon.

 

What do you mean with no custom attributes without a default value  ?

NX 11.0.1.11

Re: Roughness mapping rule

Esteemed Contributor
Esteemed Contributor

See the image below.MKE Default Values for AttributesMKE Default Values for Attributes

 Click the image to get a full size preview.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Re: Roughness mapping rule

Siemens Legend Siemens Legend
Siemens Legend

It should be enough to use only these mapping conditions:

 

First rule:

roughness_value(in.SIDE_ROUGHNESS_1) <= 25

 

Second rule is complementary:

roughness_value(in.SIDE_ROUGHNESS_1) > 25

 

Reinier Capelle

NX CAM Development

NX CAM Machinery and Automation

Re: Roughness mapping rule

Builder
Builder
In my case, I have mapped the features. So I cannot change the roughness attributes in customization.
NX 11.0.1.11

Re: Roughness mapping rule

Siemens Legend Siemens Legend
Siemens Legend

This is the standard customization.

Reinier Capelle

NX CAM Development

NX CAM Machinery and Automation

Re: Roughness mapping rule

Esteemed Contributor
Esteemed Contributor

Only blue user defined attributes can be changed, the black OOTB attributes are subject to be changed by Siemens only.

As @ReinierCapelle pointed out, there is no need to check all attributes, it is enough to check the main attribute only, which in turn keeps the conditions simple.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Learn online





Solution Information