I’m experiencing issues with the “Create Profile” component in Grasshopper when using the Tekla Link. I’m working with plate girders that include lateral stiffeners (PGB), as shown in the image below. Each girder has an outline and two holes.
If I try to create a single PGB profile, everything works perfectly in Tekla. However, when I attempt to create multiple profile types (IPE, HE, Boxed), even though they are correctly organized in data trees, the results are inconsistent.
In the second image, you can see that for some elements, only the outline is created, while others include one or both holes. This structure is correct, because if I check the preview in Rhino, everything looks as expected. However, once I import it into Tekla, the profiles appear incorrectly.
I suspect that the component might expect a single list rather than multiple lists, which could be causing this behavior.
Has anyone else encountered this issue? What’s the best way to solve it?
Your setup seems ok. If all input trees have matching structure, the component will execute once for each branch. So there should be one item in each branch for the outline, and then there can be one or multiple items in each branch for the hole input.
The second image seems to show the input for the holes, where you have only one item in some branches. So whatever is causing this mismatch is happening already before the Profile component.
If you’re able to share the relevant portion of the definition it’s easier to give advice.
Sebastian, you’re absolutely right. The component works perfectly fine—the issue was upstream of the profile component. I’ve reviewed the script, and now everything is working as expected. Thanks a lot for your support.
I have one more question. Would it be possible to represent a situation like this: two concentric steel profiles with different diameters, with a concrete annulus between them, as shown in the image below?
Even representing just the two concentric steel profiles would be sufficient for my purposes.
So I don’t think Tekla supports this as a single profile.
One way to go is to create a custom part. Here’s a basic example that you can import into Tekla. The subparts use profiles like O600*20 so they’d need to be available in your environment.
