machine models in mc

[cherokeechief79]

i am just starting to use the machine models in mc x6.

my company is looking into vericut but for what we do i dont think it would be an extreme benefit.

we dont have any crazy multitasking machinery other than a mazak integrex (runs basically one part for us)and a couple of lathes with live tooling but no y axis.

my company is very concerned that vericut can model all of the machines we have exactly as they are.

are there any other machine models except the ones that came with mc that define exacly the machines we have now?we have some hurco verticals, haas verticals and horizontals 2 gantry type mills ans several other frankenstien large cncs.

[Mgrenier]

The only way to get machine models is to call your machine builder and ask for them or use the old method by measuring yourself and drawing from that.  This is what we had to do here.

 

HTH

[#Rekd™]

I have Vericut here and I am not completely satisfied with it to tell you the truth. Vericut is not 100% fool proof, the part may look okay in Vericut but the actual machine/ controller may interpret the code differently. I have had this happen.

 

As for modeling the machines that is only part of it then you need to add the kinetics and set up the machine. I would have this all negotiated with CGTech before they purchase. They will promise you the world but get it in writing.

 

Good luck!

[gaijin_2007]

I think what a lot of people don't realize about Vericut is that it is essentially a second post processor that needs to be set up correctly.

Yes, it does read the posted NC code but how does Vericut know what the G and M codes are?

It has to be told what they mean so it can interpret them into internal Vericut commands.

So the information flow is:

 

internal CAM data > post > NC code > vericut control/machine definition (vericut post) > internal Vericut code

 

I've seen some potentially serious collisions not caught by Vericut because it wasn't configured correctly.

So of course time is spent configuring it correctly rather than correcting the original post.

 

Of course, I will say that it has other options like stock compare and an understanding of the machine kinematics better than most CAM systems (and some companies insist on third party verification of NC code which is BS in my opinion) but effectively it is a band-aid over lacking functionality in CAM software.

[cherokeechief79]

I think what a lot of people don't realize about Vericut is that it is essentially a second post processor that needs to be set up correctly.

Yes, it does read the posted NC code but how does Vericut know what the G and M codes are?

It has to be told what they mean so it can interpret them into internal Vericut commands.

So the information flow is:

 

internal CAM data > post > NC code > vericut control/machine definition (vericut post) > internal Vericut code

 

I've seen some potentially serious collisions not caught by Vericut because it wasn't configured correctly.

So of course time is spent configuring it correctly rather than correcting the original post.

 

Of course, I will say that it has other options like stock compare and an understanding of the machine kinematics better than most CAM systems (and some companies insist on third party verification of NC code which is BS in my opinion) but effectively it is a band-aid over lacking functionality in CAM software.

i have the fastest laptop in our shop and when i simulate the machine it slows down and is choppy.this is the reason we really never use it,and the fact that with just 3 and 4 axis work i trust what i see in mc.

mc also has stock compare doesnt it?cant i compare the finisahed stl ot the original model?

one thing he did tell us in vc was that nothing was modeled as an stl(inluding the machine) and that everything was still a true solid so no matter how far you zoomed in nothing looked faceted as i see in mc.

maybe this is why it seems to run and simulate smoothly.