Stock Model - "remove chips"?

[Müřlıń®]

I agree, the photo was a horrible example.  That particular job was frustrating me because I was removing quite a bit of material with a 2.5" button facemill and the remnant was very insignificant.  It was just left in the stock model so the rest rough path wanted to remove that floating piece of material.  To be honest, in cases like that, it takes too much time to verify, save an stl, use the stl to create a stock model, then use that stock model for rest roughing.. for one little tiny floater? 

 

My frustration probably came through in the posts..   apologies.

 

in cases like that I just make a little contour that cuts the chunk off and ghost it...

[SpacePilotPro]

I asked Mcam to implement this idea about a year ago....I guess they didn't listen...*L*...it seems like a simple fix and should already be an option. I usually create a "ghost" toolpath or group to get rid of the chunks.

[Matthew Hajicek - Singularity]

They implement this in 2017 yet?

[crazy^millman]

They implement this in 2017 yet?

Nope dummy tool paths then ghost them after to have for reference.

[Colin Gilchrist]

The only issue with ghosting the paths, is that you have to "unghost" them, in order to regenerate if necessary.

 

What I do instead is create a couple extra Toolpath Groups at the end of my groups list. I like to do at least 1 "main" group, and 1 sub-group.

 

Something like

 

UNUSED

 -->STOCK_MODEL_OPS-DO_NOT_POST!!!

     --> Op200 - Contour 2D

 

Then, I rename all of the Stock Model ops to a new NC File Name, usually with !!! in the file name.

 

With a little post magic, you can trap that and warn yourself:

 

psof$     #I put the code in 'psof$', because, why not?

 

      if strstr("!", sncname$) = 1,

         [

         result = mprint("WARNING - EXCLAMATION POINT DETECTED IN NC FILE NAME!!!")

         "WARNING - EXCLAMATION POINT DETECTED IN NC FILE NAME > POSTING ABORTED!", e$

         exitpost$

        ]

[gms1]

The only issue with ghosting the paths, is that you have to "unghost" them, in order to regenerate if necessary.

 

What I do instead is create a couple extra Toolpath Groups at the end of my groups list. I like to do at least 1 "main" group, and 1 sub-group.

 

Something like

 

UNUSED

 -->STOCK_MODEL_OPS-DO_NOT_POST!!!

     --> Op200 - Contour 2D

 

Then, I rename all of the Stock Model ops to a new NC File Name, usually with !!! in the file name.

 

With a little post magic, you can trap that and warn yourself:

 

psof$     #I put the code in 'psof$', because, why not?

 

      if strstr("!", sncname$) = 1,

         [

         result = mprint("WARNING - EXCLAMATION POINT DETECTED IN NC FILE NAME!!!")

         "WARNING - EXCLAMATION POINT DETECTED IN NC FILE NAME > POSTING ABORTED!", e$

         exitpost$

        ]

 

Why so much work instead of verify>remove chips>stl>stock model? There absolutely should be a button to remove chips in stock model. It was brought up and discussed during whatever public beta version stock models were introduced. Nothing came from it of course. It has always been one of the things holding me back from using them more.

[ABOMB1977]

https://www.google.com/search?q=VERICUT+REMOVE+SLUGS&rlz=1C1GCEU_enUS955US955&oq=VERICUT+REMOVE+SLUGS&aqs=chrome..69i57.9471j0j7&sourceid=chrome&ie=UTF-8#fpstate=ive&vld=cid:6748da2a,vid:O-3r9YvHJ2Y

 

 

[crazy^millman]

11 hours ago, ABOMB1977 said:

https://www.google.com/search?q=VERICUT+REMOVE+SLUGS&rlz=1C1GCEU_enUS955US955&oq=VERICUT+REMOVE+SLUGS&aqs=chrome..69i57.9471j0j7&sourceid=chrome&ie=UTF-8#fpstate=ive&vld=cid:6748da2a,vid:O-3r9YvHJ2Y

 

 

How does that help in Mastercam?