I always right click and save tool holder. Then I saved the toool library after.

Back when I was a lowercase machinist I ran a casting magnesium job. I forgot to run one piece so I took the tap out and indicated it in as best as I could.then proceeded to drive the tap down through the casting because I had to use that part of the program to get it in position and never went back to the top. Luckily the casting just cracked.

I work with a guy that thinks if it takes more than five clicks to make a five-axis path that's too much work. I was showing him tilt lines one time and he said that the butcher way to do it.

There is definitely a position on the dial maybe it's called remote? Okay I just looked at the picture so maybe not

We use moxa boxes on our 6m control. Dnc works fine. You have to have it on tape, but there may be a parameter you need to change

I even made 3D chains when a combination of multipasses and depth cuts wouldn't do what I wanted.

It should be .5mm or 1mm at the most. When zeroing it is not finding the pulse and cant go further because the limit is there.

It took them 5 or 10 years to successfully make the ball for a ball point pen.

That's overrides the soft limit. This same as putting 99999999 in for soft limit switch(1320). The may have crashed the machine and it may need a grid shift.(1850)

Should be able to open 2 instances of Mastercam. You'll have to right click and click master cam so it opens a second time. For work orders you can pick from geometry and pick the two corners of the rectangle and I believe it will straighten it. Or dynamic it will give you a gnomen manipulate with the mouse

Put g131 on. You can use p2 for roughing. I use 500 and 1000 ipm backfeeds and they run fine on our mx machines

The control always seems faster looking for an n number in memory or run mode instead of searching in edit

It may not be possible. Maybe a baud rate increase? Our matsuura PC4 will read a program and compare it against the tool list to spit the pallet back out if there is a broken tool. With a million character program this takes about 30 seconds. If you're on the offset screen you will actually see outputting blink. So you may be limited by hardware communication speed.

M198 or are you setting dnc file from program library?

In the horizontal tool bar in the screen there may be a face selection icon

When you extrude the block or a cut, in the tab I think called advanced there is the settings for making a draft

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.

That looks like a cool idea

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.

Yes remove the g-code first and see if it works

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.

Delete the tool change from the program first. If it works without error then you have a starting point

Thanks, I've actually done that for some three-axis stuff too. It's a nice double check

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 <>