Are you telling me... that you didn't have your simulation set up properly... so that you would AVOID DOG LEG GOUGING?!?!

SETTINGS > CONFIGURATION

MasterCam for Lawns has a few bugs to work out. Mostly grubs and weevils.

It took a few reads, but I think I see what he is saying. He wants mastercam to combine three or four programs for three or four different parts (details) and then build a tool list. If the programs use the same tool, he wants mastercam to only count the tool once. So if the tool is used on four different parts, it doesn't come up in the tool list four different times. Then he takes this list, loads up his carousel, and has his app change the tool numbers in the programs to match how he loaded the carousel. ...so basically all he is looking for is a tool list across several programs. Seem right?

You can't clean up with 100% stepover. Think about it like this: you machine the outside of a block, you can get square corners on the block. If you machine the inside of that block, when you get to the corners, what do you have? A radius left over from the tool. When you have 100% step over, this is essentially what you're doing. You're leaving sharp corners on the inside and then when the tool comes around on the second pass, it can't get in that corner. When you have it at 100% you're saying, "I absolutely do not want you to cut where you already cut." There is no way the tool can clean those corners up without travelling into those areas. You should be able to select "clean corners" with the appropriate toolpath.

We have Blaser, that's all we use in our 21 CNC machines. It will start stinking if you have oil in it and let it sit too long, The tramp oil floats to the top and traps all the gas from the bacteria; as soon as you mix it up all that gas comes out. The key is aeration. Feed an air line into your tank with a small brass muffler on the end and let it keep bubbling away.

Not when the monitor resolution is maxed out already. The only way to go is down, and then things start looking like Windows 3.1

I've had this happen to me several times now. I guess I'm lucky that I have three monitors, so I can just extend the mastercam window all the way to the right to grab op manager and resize it. I've tried replicating the problem but no success. I was looking at a tool list through the set-up sheet viewer while searching online for tool numbers. I went to close the mcx file to open another and fwooop! it went super stretch.

What kind of machine? Lathe or mill with a true fourth, or 3+1? When I do paths like that on the c-axis lathes, I will make curves on the pocket and unroll them flat onto a different level. Apply your pocketing strategy, such as high speed core or area roughing, and then use "axis substitution" to roll the toolpath onto the part. You can do the same thing if you have a true fourth axis.

2d contour > depth cuts > tapered walls I use that all the time to put chamfers and angles at the bottom of bores. Just select the geometry at the top of the chamfer and set the angled walls to whatever you need.

MIlling pockets and drilling is two completely different animals inside the brain of mastercam and in the post. Just because it works in milling, that has no affect on the drilling cycles. It's very possible your drill cycles weren't configured right, and no matter what you do all you'll get is a G99.

N2 ( ISCAR .610" SUMO DRILL ) G0 G40 G80 G90 G54 P1 S1000 M3 G43 H2 X-2.0607 Y1.4774 Z.05 M8 G98 G81 Z-1.5 R-.59 F5. X-1.633 Y-.3577 X.8865 Y.7465 X2.0062 Y-1.3219 X-.0855 Y-1.8274 G80 M9 M5

If you've tried what the others have suggested and it's not working, the problem lies within your post or machine definition. I do G98 and G99 drill day in and day out and it's always worked the way I need it to. Since we're all telling you pretty much the same thing and you're still not getting results, you've got to dig deeper.

Set top of stock to -.640 Set retract to .05, incremental Set clearance to .05, absolute, make sure box is NOT check to only use at start and end.

*Finishes mowing front yard, moves to mow back yard, error message pops up* LAWNMOWER HAS CHANGED The blade and engine in this operation do not match the blade and engine specified for the selected lawnmower O Update lawnmower and all yards that use the lawnmower O Create a new lawnmower. This will create a new blade with a new blade number O Cancel all lawnmower changes

In theory, the post you use should be the last one modified, so you can go into the folder that holds the post and sort by Date Modified. If you're uncertain or the dates don't match, you can open up your control definition, make a simple small change, save it, then undo the change and save it again. It will save your control- and machine definition and will move it to the top of the list. While you're in there you can check the pathway of the post being used and make sure you save that one.

make sure the font you use, if not a mastercam font file, is a true-type font.

...provided they have your machine built in swiss expert. We've got seven swiss machines here, and Swiss expert only has a model for one. So that's the only one I can program.

Your control definition probably has the arc type set to "Delta center to start" instead of "delta start to center" or vice versa. Try flipping it from one to the other.

Find and change the following postblocks to look like what I highlighted in orange: # -------------------------------------------------------------------------- # Select motion G code sg00 G-0 # Linear movement at rapid feedrate sg01 G-1 # Linear movement at feedrate sg02 G-2 # Circular interpolation CW sg03 G-3 # Circular interpolation CCW sgcode # Target string fstrsel sg00 gcode sgcode prapidm # Linear line movement - at rapid feedrate pcan sccomp, e pcan1, n, sgplane, sgcode, x, y, z, strcantext, e pcan2 plinm # Linear line movement - at feedrate pcan sccomp, e pcan1, n, sgcode, pApproach, x, y, z, pfr, strcantext, e pcan2 pcirm # Circular interpolation pcan sccomp, e pcan1, n, sgplane, sgcode, pApproach, x, y, z, parctyp, pfr, strcantext, e pcan2

Like I said before, I can't see your post processor. Did you try the changes I suggested?

Don't take things so personally, man. What you posted looks great, but you can't deny that it doesn't reflect the actual tool motion inside mastercam. That's all I meant.

I just got done doing this for my own post, using Helix Bore to pull the parameters and insert them into a single line of code--we use a helix bore macro that I wrote a long time ago on the floor. I didn't want to use a custom drill cycle inside mastercam because I wanted the toolpath and simulation to accurately reflect how the tool would be moving and cutting. Here is how my output looks: N19 ( 1/4 FLAT ENDMILL ) G0 G40 G80 G90 G55 S7609 M3 G43 H19 X.095 Y2.03 Z1. M8 Z-.935 G65 H.427 T.25 D-1.25 R-.935 C.015 F10. Z1. M9 instead of mastercam doing the whole helix. Obviously the macro is unique, but all the numbers are pulled from the actual helix bore cycle and not a work around.

It's hard to think of a solution when I don't know what your post is like.

Find the line that looks similar to this in your post: fmt "P" 4 dwell$ #Dwell Notice the number that is orange- it is probably a 2 or 3 in your post. Change it to 4. You shouldn't get the decimal point anymore.