# Set different edge connection values for panels \[SOLVED\]

**URL:** <https://femdesign.discourse.group/t/set-different-edge-connection-values-for-panels-solved/178>\
**Category:** Help\
**Tags:** solved\
**Created:** [23 April 2024 10:34 UTC](https://femdesign.discourse.group/t/set-different-edge-connection-values-for-panels-solved/178 "2024-04-23T10:34:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AKiaer](https://avatars.discourse-cdn.com/v4/letter/a/c77e96/32.png) [@AKiaer](https://femdesign.discourse.group/u/AKiaer)\
**Post date:** [23 April 2024 10:34 UTC](https://femdesign.discourse.group/t/set-different-edge-connection-values-for-panels-solved/178/1 "2024-04-23T10:34:43Z")

</div>

Hi,  
We are trying to create 1 timber panel with different edge connection values. We want to create edge connection values on specific edges of a panel, but by using Panel.SetExtEdgeConnectionContAnalModel it creates 1 panel for each index, making it impossible to add to the model due to duplicates. See image below, where there should only be one panel as the output, with test values defined in x\_neg, x\_pos and y\_pos

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/1X/d110919d4fddbc0daa2e61e6d3da9a3f8d9d7335.png)

Is Panel.SetExtEdgeConnectionContAnalModel the wrong component for defining CLT wall connections? (for shells connected to each other)

We have tried to do the same with a slab element, and using Slab.SetEdgeConnection, and it seems this behaves the correct way, only creating 1 wall element with 4 different edge connection values.

---

<div class="post-metadata">

**Author:** ![MarcoPelle](https://dub1.discourse-cdn.com/flex017/user_avatar/femdesign.discourse.group/marcopelle/32/6_2.png) [@MarcoPelle](https://femdesign.discourse.group/u/MarcoPelle)\
**Post date:** [23 April 2024 12:39 UTC](https://femdesign.discourse.group/t/set-different-edge-connection-values-for-panels-solved/178/2 "2024-04-23T12:39:48Z")

</div>

Hi @AKiaer !

You are right. The component is not properly working and I will fix it.

In order to let you keep working, you can modify your script to replicate what I have done in the picture below.

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/femdesign_api/original/1X/65d03ec2d9a7cf2a0552130774029fc4a9c8b098.png)

It is not optimal but it should let you keep working 🙂

I have opened a ticket so that you can track the status of it

> <https://github.com/strusoft/femdesign-api/issues/998>
>
> https://femdesign.discourse.group/t/set-different-edge-connection-values-for…-panels/178
> 
> https://github.com/strusoft/femdesign-api/blob/5778745a7a1cb8c458eaf9c2a44feb85eb8e62e3/FemDesign.Grasshopper/Shells/PanelSetExternalEdgeConnectionForContinuousAnalyticalModel.cs#L14-L19
> 
> 
> The user wanted to apply 4 different edge connection to the plate.
> 
> Should the input be of type:
> Panel -\> item
> edgeConnections -\> list
> inde -\> list

---

<div class="post-metadata">

**Author:** ![anLor](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@anLor](https://femdesign.discourse.group/u/anLor)\
**Post date:** [27 June 2024 04:26 UTC](https://femdesign.discourse.group/t/set-different-edge-connection-values-for-panels-solved/178/3 "2024-06-27T04:26:34Z")

</div>

Hi @AKiaer! 👋

I’ve fixed the bug. From the next release, the `Panel.SetExtEdgeConnectionContAnalModel` component can be used to set up different edge connections on different edges.  
I’ve also changed the `EdgeConnection` input type from ‘item’ to ‘list’ for each shell constructor component (plates, walls, panels, fictitious shells, etc.). This means that it will be possible to set different edge connections on different edges directly when creating the shell object.

The next version is scheduled to be released at the end of this month. 🙂