crash

[Ployd]

We keep getting a crash on a particular file. We have four large molds and they are very similar, although they each have their own file. The first two blend toolpaths went great. They took 30-40 minutes to generate.

 

Now for some reason we keep crashing on the third file. I'm not sure why we keep crashing and get this error.

 

Anyway has anyone seen this error before?

 

[crazy^millman]

I GET IT ALL THE TIME AND IT SUCKS. Sorry was hoping my yelling might get some of the real people's that needs it attention. I got over 25 of these on file last week. I got many email from CNC about it and we have not yet come up with what is the root cause of the problem.

[Ployd]

Hey Crazy, thanks for your help. You are always quick to respond when someone has a problem and I appreciate it. And it does SUCK!

 

Any how it seems like it is getting hung up at Surface 80(/94): preparing edges...100%

 

Usually when this happens I get the oppotunity to change the color of the offensive surface, but not when it crashes. Is there anyway to figure out what surface is messing me up????

 

Thanks

[gcode]

On large surafcing operations just changing the stepover by .0001 can sometime fix the crash.

Don't know why, but I've seen it work

[Guest CNC Apps Guy 1]

It probably works because you are changing the affected edges slice.

[Ployd]

I've changed the stepover from 0.02" to 0.021"

 

Hope it works!

[Ployd]

Didn't work...I checked our temp file and we have 5.2 Gb in there. I saw this in another thread about unhandled exceptions. I tried to delete the file but the computer said it was too big for the trash can WTF! I hate to delete the file if there is important stuff in there.

[Todd Tracey from Fastech]

You might try to Analyze "test" the surfaces and it may find the offending surface ahead of time before you try to run the toolpath again. It looks for self intersection and sharp corner errors

[RobertELee]

As long as MC is closed, there will be no important stuff in the temp folder. If you are worried of that make a new folder on the desktop and throw the stuff in there for the time being.

[Ployd]

I will try analyzing the surfaces.

 

Check out my Task Manager when I try and regen the file. Is this typical during regen? I ran the benchmark a while ago and we were about average as far as speed goes. The only application running is Mastercam and the Task Manager. You can see right when I hit regen. I see the CPU is maxed out but I'm not sure about the other numbers.

 

We have a Dell, Pentium 4 CPU 3.6GHz, 3 GHz of ram

 

 

[gcode]

Look in System Config/Toolpaths

and see what options you are using for regen

files.

If you are saving big regen files, tryt cleaning out the regen folder ( defined in Ssytem Config/Files).. you may have a corrupt regen

file that is causing the crash.

You could also try bumping the physical memeory setting on the toolpath page..

Make sure you resart Mastercam if to change this setting

[Thee Rickster ™]

Also try reelecting your machine definition.

on certian files with this crash it fixes it for me

[Ployd]

I deleted all regen files and temp files. Boosted Physical Memory to 90% from 80%

Also, reselected machine def.

rebooted

 

No luck, I emaild you the file gcode, thanks!

[Thee Rickster ™]

I just remembered that once in a while I have a path goes corrupt, and making a new one (the same then delete the old one)works too.

[Ployd]

Rickster, I tried that because it has worked for me also.

 

I finally got it to go but it was 198 megs! Like I said we have four of these and the first two had blend toolpaths of about 5 megs. I tried to post it but it froze up on me. I think it is a surface messing it up, but after analyzing the surfaces nothing showed up. I changed some normals so they were all facing the same way. I'm trying it again. If not I will have to use a surface parallel to get it done.

 

to be contd....

[pip]

Do you have any text or dimensions in your file.

We allways have this problem when we have text or dimensions in our file. We delete all text/dimensions, and run ram saver. Then everything seems to run okay.

[gcode]

I got it to regen, but the toolpath was no good.

There were a couple of surfaces thatwere omitted from the tool path. The resulting file was huge.

I brought all the surfaces into SW2009

and tried to heal them. SW blew a hole in the wall

in the same area that Mastercam failed to cut.

[Murray Mold]

I had several last week too after I installed XP SP3.

[Ployd]

gcode, where were the problem surfaces? Was it the small surfaces below the top flange (on one side)? I noticed a couple small surfaces that looked suspect.

 

So it wasn't the red flange area that was added for toolpathing. Seems like it kept going to 72 of 74 surfaces. If I can isolate the problem surfaces than I can fix it. But no surfaces were bad when I analyzed them.

 

It isn't a big deal because I'm working around the problem with a different toolpath that works fine. But I prefer the results of the blend toolpath if it worked. Why does finish parallel work and blend doesn't?

 

Anyway I really appreciate you looking at the file for me. Have a good day!

 

Bill