Etabs frame elements are not updating upon the 2nd push from GH to ETABS

Help
,
1

Hi,

I created an ETABS model for a warehouse using a Grasshopper script and Speckle. The only sections I initially assigned were:

IPE400(to 4,596 elements)
IPE200(to 6,742 elements)

The total number of elements in the model is 11,338.

In the second push, I made a single change: updated IPE200 to IPE300. On Speckle’s web viewer, it correctly shows that 6,742 elements were modified. However, when receiving the updated data in ETABS:

  1. It creates a new frame property for IPE300,
  2. But it doesn’t override IPE200 with IPE300 for the 6,742 elements.

Could someone help me resolve this issue or let me know if I’m missing something?

Thanks!

1 Like
2

Hi @m.abrar,

Thanks for the question! :cool_spockle: . Looking at your specific questions:

  1. Yes - a new frame property for IPE300 will be created because it wasn’t found on Receive. The old IPE200 section won’t be deleted / modified.

  2. I wasn’t able to reproduce the bug on my end - the update is working (see video). Let’s get to the bottom of this.

  • Are you updating on receive? See below setting:

image
image405×782 23.5 KB

  • Are these updates happening within the same GH session? Or are these different versions sent on, for example, different days (after shutting down Rhino + GH and reopening things / after geometry script has regenerated baseLine)?

  • Please check the applicationId’s for me between the two versions. Below screenshot shows left the new version and right shows the previous version. As we can see, the applicationId remains the same.

image
image2559×1389 210 KB

How to compare in the viewer? Automatically you will be viewing the latest version, but by clicking on previous versions, you can switch.

image
image372×529 36 KB

1 Like
3

Hi @bjoern, Thank you so much for such a detailed response. Yes, I did the same in the last 2 attempts and 3rd attempt alongside of @abreyjames but I didn’t update. I tried again this morning in 2 ways:

  1. I tried to update the ETABS file created in the first push, but it didn’t update.
  2. I recreated the ETABS file from the first push using Speckle. A few minutes later, I received the second push for an update, and fortunately, it worked.

And yes, the “ApplicationID” remained the same. My GH was close today. It’s strange that I used the same two existing versions on Speckle and repeated the exact same steps. It failed a few times, but now it updates.

Has anyone else reported a similar problem?

4

Thanks for testing again and letting me know. To answer your question, no this hasn’t been reported yet.

If I‘m understanding your two scenarios correctly; the difference between Scenario 1 and 2 is that in Scenario 1 the ETABS application received a model which was saved and then closed. When reopening the ETABS application (and model) and trying to update this didn’t work as expected? The second scenario was a receive and update step within the same ETABS session. Have I understood that correctly?

5

Yes, that’s correct. In reality, Scenario One occurs when a senior engineer has already worked on the development, and we have an existing ETABS file that needs to be updated with a new revision after a few days or weeks.

6

This is interesting - I was able to reproduce Scenario 1 on my end. Let me have a closer look and I’ll get back to you! :cool_spockle:

2 Likes
7

All good, Thanks for the support