MasterCAM crashes . . . . help!

[Code_Breaker]

I would be generating a toolpath when this error message comes up:

 

 

after a few minutes, I get this message:

 

 

It does this about 2-3 times a day. I've loaded all patches and have done a fresh install. I have MC v9.2

 

Can anyone solve this??

[Bullines]

Is there anything in your event log in the Application section. When it says "An error log is being created", hopefully that means the event viewer and not some random log file on your hard drive somwhere.

[robk]

Happens to me once in a while. Usualy my screw up creating a toolpath. Could be a bad stepover amount/multi passes that make no sense, etc...

[Lumpnut]

I get that when I have a large Mcam file open and Solidworks open at the same time somtimes. I've seen a few threads about this on da forum and there seems to be a number of variable. Video Card , Mcam allocations , etc.

[Hardmill]

Hey code e-mail your file to me, via someone elses

e-mail addy.(since i'm banned from your site)

You out there g-code.

 

 

PEACE

[gcode]

Hardmill..

I'll bet you $10 that code breaker is running

mulitple copies of MC when this happens.

 

Don,

if you want to email me the file or put it on the ftp I'll check it out and pass it on the hardmill

[Hardmill]

quote:

---

mulitple copies of MC when this happens

---

 

Well he does have two screens

 

PEACE

[MetalMarvels]

I occasionally have th same thing happen to me - same error - the whole works. I also did a clean install and updates. It seems to be random and has happened in a variety of circumstances (no other programs, other programs running, etc.). I have never had two sessions of MC running. The only common factor when it crashes is regenerating a tool path (sometimes a new one, sometimes regenerating one that I modified). I don't have the logs - I will save them next time (I just did a full system rebuild, starting with a low-level format).

 

I now SAVE very frequently and shortened the auto-save interval - it is annoying when you have done several toolpaths, haven't saved, and .......crash....

[Code_Breaker]

Hardmill, take the bet . . . 98% of the time g-code is right, but not this time.

 

 

The file is on the FTP site called CRASH_PAD.ZIP. I left the toolpath (tool #19) in its original state when crashing MC. I had to increase the tolerance from .0001 to .0003 and the step over from .0025 to .003 before I could get it to work. Also, increase toolpath allocations from 180000 to 200000.

 

HF, I am going home . . . 12-7 is all I can take . . .

[Hardmill]

quote:

---

Hardmill, take the bet . . . 98% of the time g-code is right, but not this time.

---

Cool

 

Wanna make it $20 g-code

 

PEACE

[gcode]

I downloaded the file and sent it on to

Hardmill.

 

When I regened the troublesome OP, it went all the way through and kicked out the error " Unable to write NCI file". It did not crash, but the MC( file was corruptted.

 

I uped my tool allocation/database memeory settings to 200K and tried again.

 

It Regen'd OK the second time.

I'm running V9 MR0904 with 2 gig of ram and a 300 meg disk cache.

 

The file is on the ftp as crash_pad_OK.zip

 

[ 12-01-2004, 10:39 PM: Message edited by: gcode ]

[crazy^millman]

Don my sound liek a dumb question but did you analze the model and see if it was good before doing the toolpath. I have got soem unigraphics files and they have given us a fit.

 

HTH

[Fig sign]

Code_Breaker !

I succesfully regened your op .

PC P4 2.4 +1gb Ram

Mastercam was fourth instance

3 Previous instances were :

database allocations 25000

toolpath 100000

This instance 16000

40000

Why so low allocations settings ?

You have solids ,and solids memory is of the other nature ,parasolid kernel allocates memory directly and dynamically ,JMHO .

You must give him place to have it ,I suppose .

Now as you know ,even if you had not selected solid as geometry ,in calculation of teh toolpath solids are seen on screen and it can allocate memory for this .

So do not be afraid in case of solids free memory for parasolid kernel and do not raise toolpath allocations too much

I can send you my file too ,if you need it ,it`s

rather big 40 mb zipped ,so if you need it ,i`ll sent it

HTH

[Hardmill]

quote:

---

Code_Breaker !

I succesfully regened your op .

PC P4 2.4 +1gb Ram

---

Regened fine for me also.

P4 3.2 1gb ram

 

Current RAM allocation = 496.8

Database allocation = 200000

toolpath allocation = 300000

 

 

Brought it in first time without a problem

 

PEACE

[Hardmill]

Just closed MC, opened file again as you sent it,

and regened fine w/ solidworks open in the background.

 

 

PEACE

[gcode]

Hardmill and Iskander, what versions of MC

are you running. I ran it OK in MR0904.

Code is running SP2.

[Hardmill]

quote:

---

I ran it OK in MR0904.

---

Yup, that be the one.

 

Don,

I thought you guys were running maint.

 

 

PEACE

[gcode]

According to his his initial post he's running

V9.2 (???). That must be the Walmart version,

imported from China

 

quote:

---

I have MC v9.2

---

[Fig sign]

I used Mc9.1 sp2

[Storkman]

Mine did a regen fine too Code Breaker. Must have been the allocations. Running MuR0904 + whatever the September patch was called.

[Müřlıń®]

Code you need at least 256meg of RAM to be 100% on toolpaths with those tolerance settings of .0001. A gig would be even better...

 

Mastercam will not warn you when you run out of RAM it just crashes....

 

I got mine set as high as it will allow....

 

256 on toolpaths and 256 on database....

 

You really need 2 gig total memory on your pc.If you run multiple copies you prol need 4 gig. if you multitask while running multiple copies...

[gcode]

I think Code is running a dual Xeon with 2 gig

of ram.

[Müřlıń®]

dual xeon......hrmmm.....

[gcode]

I think Iskander is on the right track.

If you have your memory allocations set too

high, Mastercam and the OpenGl kernal start

fighting over the RAM. The results can get

really wierd.

[Teh Bear without Brains kinda idiot]

~~~~~~~~~~

I think Iskander is on the right track.

If you have your memory allocations set too

high, Mastercam and the OpenGl kernal start

fighting over the RAM. The results can get

really wierd.

~~~~~~~~~~~

Thanks ,Gcode .

Thefunny thing is going down in such cases always helps ,raising memory is unpredictable .

I checked it many times too ,and in cases of solids do not be affraid to lower toolpath allocation memory ,you will be surprised