X4 MU1 Crash Regenerating Toolpath

[Thee Rickster ™]

File size is 355 meg.

Reselect geometry on a toolpath and hit regen.

 

Got an error opening temp folder and then it Crashed. unhandled exception error, send in report.

 

Any body else getting this problem?

 

Rick

[gcode]

I haven't had that error in a long time, but I never get files that big.

If I did, the first this I'd do is close all instances of Mastercam and empty my temp file.

I've been doing a lot of high speed rest rough

toolpaths lately and I found that tweaking the

"Delete regen files" settings on the Toolpaths

page of System Config can really help with proccessing times.

I've got my settings at 1, 7 and 2

[Thee Rickster ™]

Happened twice now.

[Thee Rickster ™]

This is my first huge file in MU1

 

Got the 1st path to work without doing a thing,

cept rebooting the p.c. again.

 

The 2nd time I checked the temp file and it was empty.

 

I'll give your settings a go.

 

Thanks

Rick

[Hardmill]

quote:

---

Happened twice now.

---

:CLAPPING:

 

oOps sorry wrong thread

 

 

PEACE

[peon]

Only twice? I get that damn temp error and crash problem several times a day! I sent in every report without a reply. I have only seen this problem since the release of X4 and it continues with MU1.

[Thee Rickster ™]

Peon, set your memory buffer in config/toolpaths to 99%.

That cleared it up in X4, don't know what to do in X4 MU1 yet. (still have to see if gcodes suggestion works after I am done modeling component)

[peon]

Memory buffer has already been set to 99%. Gcode, you must have three of those settings ticked in the box on the left. I'll give that a shot. My top and bottom setting is unticked. My files are generally the same file sizes as Rickster's. Would these files grow larger by ticking these settings on?

[[email protected]]

quote:

---

unhandled exception error, send in report.

---

I've got about 20+ of those in the past few weeks. Once I was just rotating the solid (with space pilot) to look at bottom side and it done it. Out of all I sent in, I think I got 1 maybe 2 replies

[Thee Rickster ™]

Murray, is the solid associated to a toolpath?

DO NOT use solids for tool paths!

 

BTW they have not fully implemented a generic automatic

reply to that

[The_Evil_Machinist]

quote:

---

DO NOT use solids for tool paths!

---

.

Why not?

[Thee Rickster ™]

problematic

[The_Evil_Machinist]

I've never had a problem with it. Though the biggest files I get are high 100's. Maybe it's just a mac thang

[peon]

9:36 and crash! 1st one today.

 

[3R!< W3NG3R]

It all depends on the solid. I get some that have bad surfaces ( ??? ). So I convert to surfaces and delete the bad ones. Surfaces also crunch toolpaths faster IMO.

[Thee Rickster ™]

Do a search and read about it.

 

Biggest one is for no apparent reason opening a

file that has toolpaths associated to solids

always opened up dirty for me and the paths would

not regenerate. Error was something like problem opening solid...

 

My first experiences were back in X2 mostly.

 

I now create surfs from solids, always.

MoldPlus also splits the model for me and creates

the surfs and moves the solid to a set level.

 

and like eric said Faster path crunching could mean 'hours' less waiting.

[gcode]

quote:

---

Would these files grow larger by ticking these settings on?

---

no but you should check your regen folder and clean it once in a while... that is another good folder to keep clean..

If you clean it out while working on a big job, you'll wipe out all your current regen files

and have to crunch them over..

[[email protected]]

quote:

---

DO NOT use solids for tool paths!

---

Maybe that's why I have so many problems......I always use the solids

[gcode]

quote:

---

Maybe that's why I have so many problems......I always use the solids

---

Dumb solids or Mastercam solids

make a difference too.

I usually run with dumb bricks

imported from SolidWorks..

If I'm running a Mastercam built solid

I run the nohist chook and turn it into

a dumb brick..

Mastercam will run much quicker and cleaner

with far fewer crashes that way..

Of course you kill your ability it edit

your solid when you do this..

[[email protected]]

I use solids from SolidEdge mostly. We do get a few from customers with different softwares.

[neil qwerty]

We also never use solids for toolpaths....we had too many problems. That being said, it's been a while since I've used them, maybe some of the issues have been resolved.

 

N.

[The_Evil_Machinist]

I have no problems with programming solids. And my files get up there in size. Weird.

[Thee Rickster ™]

quote:

---

We also never use solids for toolpaths....we had too many problems. That being said, it's been a while since I've used them, maybe some of the issues have been resolved.

---

Same here

[peon]

I've been converting solids into surfaces since vs9 for most machining. I only recently started toolpathing using solids when I program trodes since their file sizes are generally small. Most of the mcam programmers in our general area that I have spoken to also convert to surfaces.

[htm01]

quote:

---

Error was something like problem opening solid...

---

that can happen if you modify any geo used to create the solid, i always make surfs from the solid too.