I really can't send the files off to our reseller because of Boeing policies.

Yeah today it happened when i ran 3 surface finish parallels at the same time. Tried to save the in work stl and it dumped it and gave me that error. I re verified all the previous toolpaths (like 45 of them) and ran the 3 problem paths individually, and it saved fine on each... this is driving me nuts.

IIRC you need to convert tool files from x2 to x3. I think what it's doing is converting them as you call up the file.

No one huh?

The shop is Boeing, fyi.

I work in a prototype shop that uses X3. Because of the nature of the work we do, it's usually a program as you go type of deal. We use the .stl compare for obvious reasons, but ever since X3 came along we've had issues saving certain toolpaths, namely 5 axis paths. At first i thought it was a toolpath size issue, but then i got a 5 axis curve to save that was 2+ mb and couldn't get a 5 axis swarf to save that was less than 900 kb. General practice here is to verify, then compare and save the progress as a "sofar.stl". Number of operations range from 40 up to 100+ for some parts. So the problem lies in time that it saves the next shift. If there's no progress on the .stl file, they have to re-verify and this gets very time consuming when all 3 shifts have to go through and verify sometimes 20+ 5 axis paths. Certain toolpaths make it freeze, then an error pops up that says "Fatal error in Verify/simulation. Please exit Verify/simulation and try again with reduced image quality. If the problem persists, please report it to CNC Software." Then another window pops up that says "Operation Failed!" My tolerance for Verify is set to .002 if it means anything. Is this an X3 bug or is it just the nature of the beast? My whole shop runs 32 bit win xp on a computer that imo, should be running a 64 bit OS. It's a Dell Precision 490 pc. Twin dual cores, Nvidia Quadro FX3500 vid card, maxed out for ram on xp at 3.25GB. Any help on shedding some light on this issue is much appreciated. Sorry for the long post, but i felt you would need me to go into as much detail as possible about the issue.

Thanks for all your help dude. You're the man.

We ended up changing it to: pcoolon # Coolant on "M" code output #if prv_coolant$ > 0, ex$ if prv_coolant$ <> coolant$ & coolant$ > 0, [ if coolant$ = 1, "/M8" # Flood if coolant$ = 2, "M8" # Mist ] !coolant$

It didn't work. What did you change?

You got mail John.

One more thing. The post worked fine on MasterCam 9 and we converted it over to X. It's kinda weird that it would start doing it now, isn't it?

What would it be under? Canned cycles maybe? I'm new to this whole messing with posts stuff.

Yesterday i posted a program with a few drilling canned cycles and what happened was, after the canned cycle it posted 2 lines on the same line as the canned cycle. I can't figure out what's going on. Please help! Example: G98G83X-1.5Y0.R.1Z-1.25Q.1F10.X1.5Y0.G0G80Z2. Thanks in advance. Matt