Showing results for 
Search instead for 
Do you mean 
Reply
Solved! Go to solution

FBM THREAD MILL

Hello,

 

I am trying to implement FBM in my company. I have succeed with some operations but with some others I am having troubles.

 

Have anyone used the Thread Mill operation? Every time I use it, it creates the operation but also shows this message:

 

[F_14]-STEP1POCKET_THREAD -->> [F_16]-STEP1POCKET_THREAD (double node,
identical features)

 

No solution found for the following features:

feature.STEP1POCKET_THREAD (STEP1POCKET_THREAD) : extId

Tue_May_17_11_20_35_2016_9284_1000023, af_id -999

9, instant 16 (parent = none, pbl )
MACHINING_RULE (MACHINING_RULE): == THREAD_MILLING_STEP1POCKET_THREAD
X_ORIENTATION_D == -0.0000
X_ORIENTATION_L == 1.0000
X_POSITION == -50.0000

 

This is a picture of the code.

 

Capture.JPG

 

Can anyone help to understand what is happening with my code? 

 

Thanks,

 

Salvador

 

 

 

13 REPLIES
Solution
Solution
Accepted by topic author Salvador_P
‎05-20-2016 10:43 AM

Re: FBM THREAD MILL

The problem is that you don't have any application criteria, that will hinder the system to execute the rule once more.

 

I would add the following application criteria to the rule.

mwf.MACHINING_RULE <> "THREAD_MILLING_STEP1POCKET_THREAD"

This will make sure that the rule is only executed once for each threaded hole.

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: FBM THREAD MILL

Hello Stefan,

 

I just tried and it worked! I will try to look into detail for what the "Machining Rules" are used in order to make a better/clean code.

 

Thank you for your information.

 

Salvador

 

 

Re: FBM THREAD MILL

I just noticed that you used the machining rule in the LWF section of the conditions, so I suggested to use that as an indication, that there is no more threading needed.

 

The machining rule attribute can be used for anything you like, it is just a flag variable with no dedicated usage.

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: FBM THREAD MILL

Generally there are two ways of handling the machining feature process rules:

  1. let more and less worked features always be the same
  2. more and less worked features are always different

Way 1. allows to specify a dedicated process for each feature, but needed flag attributes to control the flow of the process.

Way 2. allows reuse of code, since after a thread has been machined, the previous feature is without a thread.

 

From my point of view a mixture of both is now best starting with NX 9 and using the new drilling operations and the machining areas (FACES_CYLINDER_n) Smiley Wink

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: FBM THREAD MILL

Thanks for the explication!

 

In the manual of Siemens there are only two pages in which this is explained. Any complementary knowledge related to the topic is more than welcome jejejeje

Re: FBM THREAD MILL

Hello Stefan, 

 

Sorry for bothering again, but I am stuck trying to link different codes from a Blank to a Step2Hole.

 

Do you have an example of how to link the codes?

 

Thanks in advance!

 

 

Re: FBM THREAD MILL

Can you post what you have so far, since there is no general way of creating the rules for FBM.

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: FBM THREAD MILL

Hello Stefan,

 

 

 

 

Libraries.jpg

 

Ok this is a picture of my library. The main problem I am having is when there are subsecuent operations:

 

1st   Operation - Pre Drill

2nd  Operation - Mill Rough 

3rd   Operation - Mill Finish

4th   Operation - Thread

5th   Operation - Chamfer   

 

 

 

 

 

 

 

 

 

Secuence1.jpgSecuence2.jpg

So far,I am using comments and priorities to stablish a correct operation secuence. The reason of my question, is because I have not found a logicall method to do it and maybe there is a better one.

 

 

 

Re: FBM THREAD MILL

Generally the last operation should have the highest priority.

Example:

  1. Mill finish .... priority 100
  2. Mill rough ... priority 50
  3. Drill ............. priority 10

The comment will then show the action already taken.

Example ( first is always application criteria, second is always LWF value handed forward ):

  1. Mill finish
    • NOT is_defined(mwf.comment) OR mwf.comment = ""
    • lwf.comment = "MILL_F"
  2. Mill rough
    • is_defined(mwf.comment) AND mwf.comment = "MILL_F"
    • lwf.comment = "MILL_R"
  3. Drill
    • NOT is_defined(mwf.comment) OR mwf.comment = "MILL_R"
    • lwf.comment = "DRILL"

You just have to keep in mind that the system searches from the most worked feature (mwf) to the less worked feature (lwf).

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