Making a Bolted Gusset (11) connection for angle and it does not work properly via GH component - the angle as a secondary member does not fitted by a fitting plane, bolts do not come as well (refer to the snap 1). If in Tekla to click this connection and in the component window to click Modify without changing anything, the connection gets updated properly (refer to the snap 2). Thought about some one more time modifying the connection via GH, but did not succeeded much.
Hello Rajeev,
Thank you for your reply!
zsuunta was already assigned as needed, otherwise the gusset plate does not come with proper orientation.
I did not assign zang1/zang2 though, but I reckon it is not needed for the orientation of the gusset plate and, means, the connection itself is correct.
Still somehow I “blame” the fitting plane. However, in the Tekla model directly linked with GH (not via GH component), the fitting plane comes fine.
post the code so can be reviewed
make both manual connection and check out the difference in grasshopper by extract component
Regards
Rajeev
GH definition is attached.
Please refer to the snap, where it is visible that for the model linked with GH and for manual connections is all fine. However, for the model, inserted via GH component, fitting planes and bolts do not come.
I have checked differences of attributes by extract component (basically initially those attributes were gotten this way), there is no difference, except zsuunta itself and exact_positions 0, which should be applicable for weld seams only as I understood (anyway, removing of this change nothing).
Bracing connection.gh (20.6 KB)
I only modified the bolt standard it worked
Please check the bolt standard is already exist in the tekla model
Is this snap for a model generated in Tekla via GH component or this model linked to GH direclty?
Because the bolt standard ISO4014, which I have there in the attributes, is available in Tekla. And in case of the model linked to GH directly and manual connections there are no problems for bolt appearance with this standard. The issue is only there when I try to use GH component.
Bracing connection_r1.gh (21.9 KB)
yes you r right its not working when you use the Grasshopper component
regards
rajeev
Thank you, Rajeev, for your trials!
At least now I know that it is not I am doing something wrongly here.
Will try to get fitting for these profiles before connection getting implemented. Otherwise, it would be required to modify manually from Tekla.
Hi, just to chip in here, I also replicated the same issue.
Curiously I noticed that the cut planes and bolts do appear with certain combinations of zsuunta and zang, e.g. like this:
Which isn’t really helpful I know, as they otherwise don’t appear until you Modify the connection in Tekla.
My guess is that it’s related to how the work planes are handled when using the Bracing connection as a sub component of the GH component, but can’t figure out why and where it goes wrong. E.g. the Std bracing connection (67) doesn’t seem to suffer from this problem.
On this topic, while it probably doesn’t solve this problem, we’ve added a new input Up-direction for connections and details in the GH link 1.16 WIP version. This can be used instead of the zsuunta and zang attributes.
Try it here:
https://drive.google.com/drive/folders/1qnDUaCr7rkJgawBJ7UgL2CkuePwGmAHK?usp=drive_link
Cheers,
Sebastian
Hello Sebastian,
Somehow I was not able to get it in my case.
Thank you for your continuous work on the link updates and sharing this here! Nice solution for Up Direction. I was trying to play with this, but also did not help much in this particular case. By the way, if I understood correctly that “zsuunta” numbers does not correspond to the Tekla list in the General tab of connections. It means, if I would count there in Tekla for “-y” starting from 0, I would recieve 2. But in GH I need zsuunta 5 to get “-y”. Perhaps, it would be nice to have a list of zsuunta numbers with corresponding axes in FAQ.
Also, might be this Up direction could be required in
I was trying to make fitting before creating the connection in GH, it did not help to get bolts either. It looks for me that in the connection 11 code there is a break somewhere when it could not make fitting, and subsequently bolts are not getting implemented.
I was also trying to reassign some attributes to the connection in order to replicate Tekla Modify, but it did not help as well.
Thought that C# script could help again to replicate Tekla Modify, also did not work.
No idea what else to try.
Suddenly found out a strange work around (other than clicking of Modify for every component due to different attributes) - if to move the entire GH component in Tekla, these connections are getting remodelled properly.
1 Like
Seems the move triggers a Modify… but I assume this isn’t something you can use as a proper workaround? Perhaps there’s another connection you can use that plays nicer as a sub-component, quite a few of them have overlapping use cases? I’m a bit lost here as well.
Cheers,
-b
