Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.
Use your display name or email address to sign in:
I find master cam easier to model with than fusion. but that's probably because I've used master cam exclusively for years.
One nice thing about fusion is if you have the sketch on the push pull is kind of intuitive for pushing and pulling out pockets and bosses based on closed chains on the face.
Sometimes the o-rings need to be changed. Our makino says to change every 2000 hours.
At the end of the program you can also switch to an empty tool and blow the spindle out for a longer time so it doesn't increase your chip to chip time.
When I tried to use the the g-code remap we have it ended up too many levels deep and tried to tool change before it was in the atc position. It alarmed out
Our format had the canned high speed mapping as well. One version in mastercam was buggy with adding and removing it so I had changed it.
some manual entry work.
you can change where it outputs. we currently have 3, in the path me1, before the tool change mb1, or after tool change mt1,
here is one where i modified the post processor to output formated for camplete
probe cycles. those custom names act weird if you are not in the active group
post
select as text file
post from camplete your probe cycles, no manual edits needed
manual entry macro calls placed in the tool change block
mb1, macro with 500 lines usable code length
these are the tool break calls from the first post
The tool breakage macro call was placed in the end path block. I don't have a picture of that one.
You can also call macros is values are not equal to a parameter with <>
call a misc real in integer format
use real as a real value, in this case tolerance.
the output is shown on the right. it pulls the tool diameter from the tool data for endmill check
1. using a machine parameter to alter output.
we have 4 types in our shop.
mx330.mx520,mx520pc4 and an mx850. we want the program to end differently for all 4.
edit the machine and create a parameter. Its not showing here but apply to machining setup.
so each machine will have a different number
make a format macro how you want it to end.
330 goes to g53x-11. 850 and 520 go to tool change position in x pc4 calls m98p1 pallet program
label them so you know what they do
you can see here i used the same parameter to call a save index macro also
call them up in the end program block
here we can call them up in other areas
I did a report. The planes go from 50 to 72.
When I deleted the entire 1st rough operation group it seemed to lag less but still ran the cursor busy. This group had 2 toolpath groups in it. 1 for each side.
My plan started out as duplicates of the top.
Then I would copy and edit to rotate. They are very similar except they reflect material left for heat treat so the z height of the plane sometimes is .005 or .01 different than one of its duplicates.
But they're only about 10 custom planes in this particular file it's under a half a gigabyte
Only this file
I exited and still get the lag.
It's fine if I make geometry or use a function. If I click a plane, machine group or toolpath it spins the mouse for 3 or 4 seconds.
I'm going to save as and delete things untill I figure it out I guess
Every time I move the view I get a 3 or 4 second lag with the spinning mouse icon.
The event log is filled with the get gapid in the picture. It is almost unusable. It happens in this file only.
Any idea what causes this?
Thanks
The force tool change can be tricky depending on some of the settings And how the NC format is written. But I got it to work pretty good The only thing I can't do is get it to make an n number in line with the tool change index.
For close true position work we use the probe and a sub program. We tried to use the TWP but unless the machine is in a lab it's very hard.
For multiple work offsets you have to edit the machine because it defaults to -1 for the cam index for every work offset
As for not outputting the spindle speed on every path you need to utilize the NC format macros.
eMastercam - your online source for all things Mastercam.
Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.