Vericut vs. MC verify

[kinglouie V]

just got the license for our server. waiting on IT now.

 

-chompin' at the bit.

[gcode]

quote:

---

If you have both Vericut and Mastercam, it is not an extra cost for this chook to work

---

I don't own Vericut, but I've got a V5 price list

that says the Mastercam/Vericut chook is a $1000

addon

The trouble with using this chook is that it runs

on the Mastercam NCI file.

If you have a post error or a bad tool plane, you'll get the same results in Vericut as you would in Mastercam Verify.

Pretty pictures on your screen, but crashes and scap on the machine.

Posted gcode is the only way to go

[kinglouie V]

I can confirm the $1000 price tag but the instructions say that you can verify both nci and

posted code. However, I'm still waiting for someone to install, since we just got it on my request.

 

quote:

---

If you wish to verify G-code data previously generated by one of Mastercam's post-processors, select the "Verify G-Code" option. This will enable five additional input fields in the dialog, for the specification of the G-code files and location of the stock on the machine.

---

[Zoober]

We Dont have the MC side (yet), but with our Catia, we verify Gcode. Easy enough with MC Gcode if you have models and create the tools in Vericut. I think (you may prove me wrong) the Chook just makes bringing in stock and tools easier.

[kinglouie V]

zoober we do the catia here also, so I'm hoping to mooch off someone's machine def's. I think you're correct though, brings in material, tool, holders and makes life a little easier.

[DavidB]

gcode,

quote:

---

The trouble with using this chook is that it runs

on the Mastercam NCI file.

---

That's not correct you can run the posted g-code in Vericut via the C-hook.

[kinglouie V]

ok I got all the stuff I need but it still isn't working.

 

"Mastercam .net support DLL nethook not found"

 

is it looking for the one in the MC c-hook directory here or the one in vericut?

[kinglouie V]

I'm guessing it's looking for the batch file that's in the command folder in Vericut. there's a ver8 and a ver9 but no X batch file. I just recieved another disk from cgtech per tech support but it looks like I'm still going to have to call.

[NCGUY]

The MasterCam to Vericut interface will run the NCI file or the posted data. It does not run the g-code via the NCI as described above. It runs the actual G-code file itself.

 

If you want to test it, take an nci file and post it out to G-code. Then, open the G-code file and type in a few X,Y,Z moves and see what happens. If it is running the G-code file you will see axis motion in the Vericut simulation of the additional data you added to the G-Code file. Or, delete the NCI file then run the G-code in Vericut.

 

Just a note. Vericut does control emulation of G-code data. Meaning it is not just moving a tool through out the point data to create the geometry. It actualy simulates the machine behavior depending on which G & M code cycles are active.