Create a classic "edge" with three beams

compas_rhino
1

first i’d like to thank you for this piece of software / environment. great work

i’m trying to use compas-timber in rhino8

when having a look at the examples i miss one type of Joint, the classic three beam edge in a “fachwerk” construction.

two horizontal beams have a L-Lap joint and the vertical beam has a tenon / mortise into them.

i suspect it need to be composed with rules and features?
is there an example of this around?

2

here the sketch in grasshopper.

since the joints are a 3dimensional Y topology, rather than L joints (which is what the given components offer at first hand) i guess the recognition / built in hierarchy fails.

i tried adding a tenon feature to the posts, but so far i failed. (guess i also need to ad a mortise to the sills to complete what i want…

but i suspect there are better ways. if anybody could point this out for me.

image
image1920×1233 204 KB

the result when i bake them:

image
image1890×1020 140 KB

there are no mortises in the sills (may because i didn’t explicitly add the feature). and also on edge doesnt seem to generate the lap correctly (which i don’t know why this acutally is…)

PS: i wouldn’t mind if this has to be solved with the GHpython component. in a similiar matter like the “Y topology” in the “example script beam joints” file.

but i seek advices to get started with this particular set.

3

Hi @supcha !

Thanks for posting.

So if I’m getting it correctly, the two base “Schwelle” beams should meet with a french ridge lap, and then the tenon of the “Pfosten” should run through a mortise in both beams, is that correct?

Not sure if this case can be automatically handled by the JointSolver just based on the Y topology, it could take some tinkering and potentially some manual joint assignment.

Any chance you can share you Rhino/GH document so that we can try some stuff out?

Thanks,

Chen

4

thanks for your reply.

i’d gladly share the file here, but it seems i can’t upload the .gh file.
so i uploaded it to my webserver instead.. here the link.

https://seismic.industries/test/test_compas_timber.gh
(or please advise on how to share)

as the “edges” are two horizontal beams and a vertical one, this does not get recognized as it’s own category.. a flavor of a Y joint.

thanks for any hint/help on pointing out on how to solve or work around this.

5

@chenkasirer
i had a peek at the listed issues in the compas timber github repo.
it seems the project is aware of this circumstance of the missing components & logic.

https://github.com/gramaziokohler/compas_timber/issues/687