Do you have a final check list before posting?

[lowcountrycamo]

I have a quick check list I use before posting:

I post a .set file to check my wcs and t planes, rpm and feed.

i take a second look at clearance height.

on trunnion mills I focus on rotations. Then I mass edit for coolant and misc no. 

I also use the compare function in verify and set tolerance to + - .003. 

I do not have vericut yet but will soon.

any one have something similar. 

Thanks,  Steve Austin 

[gcode]

Mass edit all ops with

Right Click/Edit Common Parameter/Change NC file name

and make sure all ops get posted with the same filename

There is nothing more embarrassing than importing a nice pocket roughing operation then failing to post it..

and figuring it out after a $400 endmill dives in to finish a pocket that has not been roughed. 

This is an error Mastercam Verify will not catch

I also have my Post Dialog setting set to "Ask"  as a further safeguard against this 

 

[Guest]

When I post I usually follow these steps :

check the visual of the toolpaths that the rapid movements are above the part.

 

check that any location holes are drilled if requiring a flip

 

check my stock setup is correct

 

Rename all the operations to ensure everything gets posted(like G said)

 

Check my simulation and verify (collision detection recommended as collisions during rapid may no show up in simulation)

 

[lowcountrycamo]

47 minutes ago, lowcountrycamo said:

I have a quick check list I use before posting:

I post a .set file to check my wcs and t planes, rpm and feed.

i take a second look at clearance height.

on trunnion mills I focus on rotations. Then I mass edit for coolant and misc no. 

I also use the compare function in verify and set tolerance to + - .003. 

I do not have vericut yet but will soon.

any one have something similar. 

Thanks,  Steve Austin 

Yes I have had that happen.  Good one to add.

[Newbeeee™]

My process was;-

Finish (or so i thought )

Verify checking to Model

Run Gunthers X+ setup sheet so one click gave me tool# H&D, (to check all match). Coolant on, WCS, G54# etc

Post

Run through NCPlot to check again

Then we're good to go

[JParis]

I'm pretty thorough about setting my toolpaths up as I create my programs....

when I'm done, 

Edit All Ops, Program #

Edit All Ops, NC File Name...

Because I use a variety of coolant styles, I don't use the edit all for coolant...

 

[Tim Johnson]

I check every finished operation on the fly. That seems to work for me.

[So not a Guru]

3 hours ago, JParis said:

I'm pretty thorough about setting my toolpaths up as I create my programs....

when I'm done, 

Edit All Ops, Program #

Edit All Ops, NC File Name...

Because I use a variety of coolant styles, I don't use the edit all for coolant...

 

I use different coolant strategies, for different tools, too. I generally:

Edit All Ops Coolant Flood on

Then I use Toolpath manager Select, to chose the tools that also have CTS, then Edit Selected Operations Coolant Thru coolant on.

I love the Select function, it can be a real time saver.

[Matthew Hajicek - Singularity]

I use a stock model every few ops to track the progress of the program, and it works like a quick verify.  Will show retract errors etc.

I rename the NCI and reset the O number.

Then I post it and run it through Vericut.