WHAT DOES THIS MEAN??

[brice]

 

Allocation is too low: disable Fast Zcut Technology (use tpcfg chook)or increase toolpath allocation to an amount between 50,000K (50Mb)and 1/2 the physical memory size.

 

I keep getting this and I'm not sure what to do with it??

[betts]

What version/revision are you running?

[Guest]

X I assume?

 

Settings >> Configuration >> Toolpaths >> Memory buffering >> If you have enough memory on that box, anything 1 gig or over, I'd set it at 50%

[brice]

I'm running version 9.1.

[betts]

ok-what are the specs on your machine, and are you running another CAD/CAM software while running MC?

[Slepydremr]

screen => configure,

 

allocations is the first page

 

tool path allocation is at the bottom

 

set that to 128000 or something above 50000

 

see if that helps

[brice]

I have three Fanuc milling (router) machines. I am not running anything but MC 9.1.

[betts]

ok, I meant how much memory is in your computer?

 

slepydremr's answer is what you want to do, as long as you have at least 512K memory.

[brice]

I did change it, but I still can't get the jittering issue to stop. This was on my other posting....I was trying different toolpaths to smooth it out when I got this warning!!

[betts]

What exactly do you have in your "toolpath" and "database" allocations, and what is the total memory in your computer?

[brice]

I have 8,000 in my database and I changed my toolpath to 128,000

[brice]

and I have 13.7G left of memory

[Bill]

the memory he was referring to is RAM.

 

Database is for surfaces wireframe etc... toolpath alloctaion is RAM dedicated to processing the toolpath.

 

The jittery thing... what type of toolpath are you trying to write?

 

(I believe he is talking about the up and down jagged looking cuts in backplot when you run something like a scallop or project where the surface transition changes per the step over amount.

 

Shoot a screen dump of the backplot to me so I know what you are talking about.

[betts]

brice, assuming that is 13.7MB left, I would set your database at 32000 and toolpath at 64000, then reboot the computer and start again on the toolpath.

 

But like billh says, if you can post your prg, or be more specific about the "jittery", that would help us help you too.

[Storkman]

I think your confusing hard drive space and RAM. If you have 13 gigs of RAM, I am jealous.

[Bill]

That's what I thought birdman.

[brice]

My ram 523,496Kb

[Storkman]

You should try to allocate about 256,000 to mcam.

[Mike Mattera - TFM]

In V9 I would use between 120,000 - 200,000 for Toolpath and 40,000 - 60,000 for Database.

 

FastZCut needs a min. of 90,000 for Toolpath.

 

This is for doing 3D machining.

 

Mike Mattera

[brice]

Okay...I have changed all of the allocation. This still doesn't change my jittering on my toolpath. I have a taper ring that I'm trying to toolpah. I've tried every type of toolpath, but it still jitters. HELP!!!

[Slepydremr]

Try Uploading your file to the ftp site. Maybe someone will be able to figure out what you need to do.

[brice]

Okay the file is there under jittering. When you verify this file, verify operation #4 only and do this at the lowest speed possible. You will see how slow it goes.....

[Slepydremr]

I'm not sure if this is what you're seeing but if you're refering to the fact that the project path has created thousands of little lines around your part instead of one smooth arc. I thought that was how it normally works. I don't think it will put out just one smooth constant helix for you unless you use a different type of toolpath.

 

But it didn't appear jittery to me. Just lots of segments.

 

Edit:

 

But it does appear you have some lead in/out issues from that op 3 that you're projecting. If that is your trouble try changing that around a little.

[JCLM]

I agree with Slepydremr. Just curious, have you tried running the program on your machine yet? It stops in the verify because that is where the line or arc segment stops, however when you run it on your machine you probably won't see the "jitter"

 

Jeromey

[Jack Mitchell]

quote:

---

however when you run it on your machine you probably won't see the "jitter"

---

I disagree.

It's been my experience that verify and the actual workpiece look exactly the same when surfacing.