Trim Solid Limit?

I'm generating tool paths for my CNC (that part is easy ) and trying to generate a rendering (this part is not easy) .

The red box (rectangle) is the base material and the sphere is simulating the ball nose end mill. I'm placing a sphere at every pt (x,y,z) of the tool path and triming the box with the spheres. I want to increase the tool path points to trim more "material" away from the box. I'm only increasing points for the rendering, the actual tool path points don't require any further resolution.

Everything works great when there are 1292 tool path points (spheres). I can produce a good rendering. When I double the tool path points (and spheres) to 2528 the rendering doesn't happen. I get a "Boolean Trim Set is Empty" run time error from the <Trim Solid> component.

Is there a "limit" to the <Trim Solid> component?

Replies to This Discussion

Permalink Reply by Greg J on January 5, 2011 at 11:27am

I made the box and sphere from meshes, but ran out of windows memory and crashed Rhino 4.0

My machine is a Precision T7500, E5620 @ 2.40GHz with 6GB of RAM.

Since the tool paths have random lengths and overlap one another, sweeping the surface is difficult because I can't trim the two surfaces where they overlap.

Is there a more efficient method to build this surface?

Permalink Reply by to] on January 5, 2011 at 12:03pm

Hi Greg

Rhino for uses only 2 GB of RAM

if you change to Rhino 5 64bit this limitation is gone and you have also better boolean algorithms .

best

to]

Permalink Reply by Greg J on January 5, 2011 at 12:14pm

Thanks to]

I have been using Rhino 5, but just too many little thing not working (minimize window doesn't work properly, layers window doesn't work, etc. ) so I went back to Rhino 4. I'll be glad when they have the final release. There are not too many programs I actually enjoy using, but Rhino (and GH) are two programs I enjoy.

I'm gonna work on this definitions for a little longer and try different "things". If its too much trouble, I'll go back to Rhino 5.

Permalink Reply by to] on January 5, 2011 at 12:16pm

I do not have this Problems ....

i wish you all the best and hope it works

Permalink Reply by Greg J on January 5, 2011 at 12:28pm

Thank you Sir,

Just to make it clear, you are NOT having any problems with Rhino 5 ?

Permalink Reply by to] on January 5, 2011 at 12:38pm

I do not have this problems you describe or any others with Rhino5 64bit

nothing i have seen yet ;)

Permalink Reply by Greg J on January 5, 2011 at 12:40pm

Thanks again.

I've emailed Rhino support.

Permalink Reply by Greg J on January 5, 2011 at 1:23pm

I thought I'd try Rhino 5 again, so I started the program and everything is working fine. Go figure. I already received a reply from Rhino support (best support around) so need to check some things there.

Anyways, under Rhino 5, I can't get the definition with 1292 points now. No error message, just a null string. Must be my diffinition.

Permalink Reply by Juan Alberto Galicia Osorno on March 17, 2011 at 7:22pm

Erm what if its 34 bits? is it the same?

Permalink Reply by Victor Leung on January 5, 2011 at 2:34pm

I saw most CNC software/plugin will do the toolpath simulation by a mesh boolean operation, not nurbs boolean. I think it is just easier for the computer. Try think about it...

Permalink Reply by Greg J on January 5, 2011 at 2:59pm

Thanks Victor,

Yes, I will give it a try. I'm slowly trying everything.

Its interesting that the <Trim Solid> component behaves strange some times. I have a rectangle box, and I <Trim Solid> one sphere, and it works. Trim 2 spheres, and it works. Trim 5 spheres and it doesn't work. Trim 10 spheres and it works. Strange.

I always approach these "issues" by reducing the problem to its fundamental form, and re-building. Kinda fun actually. Back to the model :)

RSS