cancel
Showing results for 
Search instead for 
Did you mean: 

FBM: anyone already hit the 10000 nodes limit?

Esteemed Contributor
Esteemed Contributor

A simple part with only 563 through holes will exceed the 10000 nodes limit when creating the feature process for all of the holes.

Is there someone who can explain why there is no fall-back to automatically split the process creation, if it gets near the limit?

Sure we can manually add the failed holes after the initial process creation succeeded, but would prefer to get things done in one go Smiley Wink

The funny thing is that NX tells me that all operations are successfully created, but ignores to tell me that it failed to do so for some of the holes due to the node limit.

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: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community
2 REPLIES

Re: FBM: anyone already hit the 10000 nodes limit?

Siemens Legend Siemens Legend
Siemens Legend

There is an existing enhancement request for this issue: #7682534: increase maximum number of nodes.

 

Reinier Capelle

NX CAM Development

NX CAM Machinery and Automation

Re: FBM: anyone already hit the 10000 nodes limit?

Esteemed Contributor
Esteemed Contributor

Thanks Reinier for mentioning the existing ER.

Have a pleasant one.

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: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community

Learn online





Solution Information