Use Vericut For 3-Axis Machines?

[JakeL]

Got Vericut last summer, and after dragging our feet, this past October-December we got machine templates so we could actually use the software  .

Anyway, we only got templates for our 4 and 5-axis machines. That seemed reasonable until recently. I'm getting one of our 3-axis VMC geared up to run lights out. Got a bunch of parts all across the table, and the deeper I get into this the more I'm wishing I could run it thru Vercut.

So now I'm curious, do you guys run 3-Axis programs thru Vericut? Or is MC verification sufficient?

[JParis]

Got Vericut last summer, and after dragging our feet, this past October-December we got machine templates so we could actually use the software  .

Anyway, we only got templates for our 4 and 5-axis machines. That seemed reasonable until recently. I'm getting one of our 3-axis VMC geared up to run lights out. Got a bunch of parts all across the table, and the deeper I get into this the more I'm wishing I could run it thru Vercut.

So now I'm curious, do you guys run 3-Axis programs thru Vericut? Or is MC verification sufficient?

At our purchase last year, I wanted to add our 3 - 5 axis machines....as we do a very limited set of work on them, I was overridden and the decision was made to add the 3 axis verticals instead....

We have not done a 3 axis yet but I know moving forward, especially after the first part was so successful that it will only be a matter of time before those requests start coming in..

For my own, I do think it's a bit of overkill but, we now have it, we'll use it.

[JakeL]

For my own, I do think it's a bit of overkill but, we now have it, we'll use it.

It feels like overkill, at the same time these parts are going to be completely sub programmed and very smushed together.

I scrapped a part once when a machine dog-legged (obviously never saw it in MC). I can't help but worry about something dumb like that happening with this setup.

[JParis]

Yup, you just made the argument as to why to do it

[gcode]

obviously never saw it in MC

If you set the Rapids fields in the Control Def correctly, Mastercam Verify will simulate dogleg rapids.

[Zoffen]

IMHO if you have vericut you should figure out the workflow to be able to vericut almost everything you run. Yes it takes time but its not about the time it takes, its about the consistency of good part/programs flowing through the shop. You can do just as much damage to a machine in a simple program as a complex one. Simple and easy often lead to the biggest crashes as comfort level is too high and pucker factor is too low.

Simulate or die.

[JakeL]

If you set the Rapids fields in the Control Def correctly, Mastercam Verify will simulate dogleg rapids.

Now I'm confused. In my control def Linear > Rapid Motion > Each axis moves at maximum feed rate independently --- this is selected and I see no dogleg in verify or simulation.

So I tried selecting a different option to see what it would do. I switched back to what it was originally, it's now showing doglegs in verify.

Do I need to manually update this field for it to work correctly?

[CNCAppsJames]

I run everything through CAMplete. 3-Axis, 4-Axis, and of course 5-Axis. It's definitely overkill on 3-Axis, but anything worth doing is worth overdoing when it comes to unattended machining operations. Seriously.

Unattended Operations is the world I live in. It's not sexy. It doesn't make for spectacular YouTube videos. It DEFINITELY doesn't get the likes and the subscriptions. It does however pay the bills, keeps service calls to a minimum, keeps tool life up, and is predictable when done properly. And last but not least, doesn't require babysitting.

Unattended Operations FTMFW!

[gcode]

Now I'm confused. In my control def Linear > Rapid Motion > Each axis moves at maximum feed rate independently --- this is selected and I see no dogleg in verify or simulation.

So I tried selecting a different option to see what it would do. I switched back to what it was originally, it's now showing doglegs in verify.



Do I need to manually update this field for it to work correctly?

sometimes you need to edit the Control Def then reload the post into your file to make sure the edit sticks

[__]

Now I'm confused. In my control def Linear > Rapid Motion > Each axis moves at maximum feed rate independently --- this is selected and I see no dogleg in verify or simulation.

So I tried selecting a different option to see what it would do. I switched back to what it was originally, it's now showing doglegs in verify.

Do I need to manually update this field for it to work correctly?

I remember having this issue and the machine definition change you described fixed it, not sure where that setting is defined or how the default works.

[__]

sometimes you need to edit the Control Def then reload the post into your file to make sure the edit sticks

The way the machine definition sticks in files with existing machine groups always irked me

[JakeL]

IMHO if you have vericut you should figure out the workflow to be able to vericut almost everything you run. Yes it takes time but its not about the time it takes, its about the consistency of good part/programs flowing through the shop. You can do just as much damage to a machine in a simple program as a complex one. Simple and easy often lead to the biggest crashes as comfort level is too high and pucker factor is too low.

Simulate or die.

One side of me says this ^ , the other says 3-axis vericut is overkill.

Here's our issue, we have about 35 mills. There's 14 different 4&5 axis machine make/models, and 9 different 3-axis machine make/model.

I don't imagine that would be a cheap vericut bill to get the 3 axis setup. Not to mention the upkeep on all the additional vericut templates.

[Zoffen]

One side of me says this ^ , the other says 3-axis vericut is overkill.

Here's our issue, we have about 35 mills. There's 14 different 4&5 axis machine make/models, and 9 different 3-axis machine make/model.

I don't imagine that would be a cheap vericut bill to get the 3 axis setup. Not to mention the upkeep on all the additional vericut templates.

Building machines, especially 3 axis machines is pretty easy. Get your boss to pay for a class and go to town.

This can also be a good time to point out that STNADARDIZATION in the shop for the future will make things like this alot easier.

It should take less than 5 minutes to output a 3 axis vericut session. Don't be lazy. Well worth the piece of mind that the code is good. So many things that can go wrong in this business its nice to have SOMETHING you know is 99% before sending to the machine.

[gcode]

I don't imagine that would be a cheap vericut bill to get the 3 axis setup. Not to mention the upkeep on all the additional vericut templates.

Have you tried looking in the Machine library that installs with Vericut
They have a lot of machines in there. You might get lucky.

[CNCAppsJames]

Simulate or die.

SO much THIS ^^^^^^^