Bulkhead Nesting to Laser

Hi, i am trying to nest my bulkheads to a sheet with OpenNest but i need to get the referance frame numbers and cutout engraved on it as well.
I need it to be ordered from bow to aft direction.

To simplify i attached 6 sections to make it simpler as my sheet is also there to be nested on.

Normally i manually numbered them each but are there any way to number them in grasshopper in consecutive order from top to bottom ?

00.3dm (197.7 KB)

I see your drawings have separate parts next to the blue marks:

do you mean those flaps to be nested together with the bigger part on top? or they can be detached for real? like 3 different pieces?

Hi inno,

Thanks for the reply.

Actually we can try as 3 seperate part as you see for these bulkheads and if we can manage to do we can name them as well.

I think it is hard to name as in below ? ;

Bulkhead-1

1.1 / 1.2 / 1.3,

Bulkhead-2

2.1 / 2.2 / 2.3

for the production team have a better understanding which part belongs to which bulkhead number.

i dont know what is wrong with my grasshopper as it is giving error as in below or am i doing something wrong. I was watching the official tutorial of open nest, i even simplified the process down to ellipses but still cannot see any nested objects. (I managed to do that for a keel project in last year but this year im out of luck i guess :slight_smile: )

Previously, I had success with keel nesting using this setting by converting each curve into a Brep 3D object. In that case, however, I couldn’t manage to include the holes during the conversion and had to add them later, which—as you can imagine—was quite a headache.

Perhaps a better approach would be to first create a surface, similar to the method shown in the second tutorial, where the Rhino object component is used.

But in this case, do i have an option just using curves instead.

Anyone can make this nesting with marks on it ?
I tried to make rhino objects and guid from the opennest menu but it has some errors that i cannot figure out how to fix it. It gives error like " object referance not set to an instance of an object "

i tried different simpler objects like in below screenshot but somehow ellipses and circle objects has some issue to be applied to the nesting, any known reasons ?

Tried to make a boundary which makes surface of these circular objects but couldnt make them to be added to nesting geo.

I attached the gh file as well, you will see the required bulkhead sections to be nested on the right side corner.

d6-sections.gh (15.8 KB)

00.3dm (898.6 KB)

@boradtur666
This seems to work.

Hey Toni thanks for your effort and a different method.

However, the main objective is having the holes and the lines (as laser engraving) inside of it as well.

Is it possible to do that with your methods ?

@boradtur666
If I remember correctly, OpenNest only accepts polylines as inputs, so the cirles and ellipses were causing issues.

I added a small script to convert them into low-resolution polylines (you don’t want to increase the resolution too much, as nesting becomes too slow). and to surfaces from there. I had moderate success with this, but it does not solve the lines, and Transform is not an option as the object amount is different.

I could, however transform a generated surfaces, but that drops the engraving lines.


d6-sections.gh (16.4 KB)

@boradtur666
Ok, I think I got it now.
I generated branges of the object groups by centroid proximity, and applied the Tranformation by branch.


d6-sections.gh (22.7 KB)

The proximity sorting works for these simple geometries, but you can and should utilise an more robust method in your final geometries. But as long as you can branch them, you should be fine.

EDIT:
450mm is working as a good value here, but yeah… pick a more robust method for branching the geometries.

wow looks great !

i have to comprehend this process.

By the way how to easily run your script as it shows white boxes.

I will still need to do this on the right hand corner sections, hope it will work

Are you on Rhino8?
The white boxes are the Python script components- should be native to vanilla Gh in Rh8. I didn’t use any other plugins here.

If you are using Rh7, then I need to switch to another python script component version.

@boradtur666
Here’s the Rhino7 version. I replaced the python component to the older version.
d6-section_Rh7s.gh (24.2 KB)

ah thanks now working.

i tried to apply this to the other but it seems a little problematic as in the below screenshot.

I watched this tutorial lately and this is what i am actually looking for but the tutorial geometry of course much more simpler. Maybe thats why you need to make an other methods as you suggest.

isnt it possible by a native grasshopper component such as “rhino objects” and “Guid” as the tutor is mentioning about ?

maybe my geometry is more complex for the grasshopper to handle without any simpler method ?

@boradtur666 In the tutorial, the voice says that the Rhino geometry component takes in closed polylines and then searches for other objects within them - grouping them. Ok, easy enough and replicatable in Gh as well.

I see from your screencap that you are using the centerPt grouping by proximity, which clearly fails. Either because the method is not good here, or the search radius is too small.

Yes, this is the case. The tutorial is done with a very simple set of geometries and all accompanying geometry is located within a single closed border crv.

But, I got it working for you. Being on Rhino7, instead of 8, causes an issue with the text objects. So 2 things I did in Rhino:

  1. I named all sections with numbers 0-14. I could have done a geometric grouping inside Gh, but the sections are close to each other and complex - I though I’d spare that excersise and just name them. Took me 30s. But, now inside Gh, I can determine the grouping based on the object name.
  2. I exploded the text objects to curves. Because vanilla rh7 Gh does not understand text objects, I could not retrieve their names. Problem is solvable by using Elefront or Rh8.

I solved the process with only vanilla components - normally I would’ve used Elefront here, which would have allowed the use of text objects as well.

I tried to simplify the outline as much as possible to make the nesting faster. It has room for improvement, but sufficient enough. Around 25s on my computer.

00.3dm (980.5 KB)
d6-section_Rh7s.gh (19.9 KB)

It looks like the more I try to nest it the way I want, the more complex it gets.

Thank you very much for your clever move — it looks fair, but now I need to force the parameters to make it into four sheets only, as the supplier succeeded at it. I think their nesting is much better at optimising, as cutting sheets is their main job. :slight_smile:

@boradtur666
Yeah, I have the same expriences with it. With simple geometries OpenNest1 does an ok job, but I have also often ended up tweaking the results by hand at the end. Especially with geometries that are complex in shape, but easy to see that there is a repetitive solution, like stacking. But the first results help a lot in the process.

If and when you go Rhino8, there’s OpenNest2, which may improve the results.
And a new on-going development - Sparrow.