Showing results for 
Search instead for 
Do you mean 
Reply

NX11 toolpath different than NX10

I brought a n NX10 part file into NX11 and just copied and regenerated a 5 axis operation, I'm getting a different toolpath and was wondering why?

 

 NX10_toolpath.jpgNX11_toolpath.jpg

4 REPLIES

Re: NX11 toolpath different than NX10

This is a mill_multi_blade Blade Finish operation. NX 10.0.3.5 mp13 and NX11.0.1.11 mp1. Again no changes, just called it up and regenerated the copied operation.

 

Rick D.

Re: NX11 toolpath different than NX10

Best is to report it as a bug at GTAC, since the NX 11 tool path doesn't look right.

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

Re: NX11 toolpath different than NX10

I've also noticed some strange behaviour with recalculating an operation in NX11 that's created in NX10.

The time to recalculate in NX11 is much longer than in NX10.
When u create a new operation with the same settings the calculation time is back the same as the one in NX10.


Regards,
Sven

NX11.0.1

Re: NX11 toolpath different than NX10

I think that only the second time you regenerate in NX 11 will be as fast as in NX 10, since there is information created during the first regeneration, that was not present in NX 10.

this is also true if you regenerate a tool path from NX 8.5 in NX 10, starting with the second regeneration performance is better.

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