STAAD.Pro Connect Edition to V8i Compatibility Issue

Hello. 

I am having an issue with what seems to be the compatibility between different versions of STAAD. 

I was given a file to check that was created in STAAD.Pro V8i. I have CONNECT Ed. on my computer and, as expected, had no problem opening the file. During my checking made a few changes to the geometry and saved the file (using my CONNECT edition version of STAAD). I then emailed the file back to my college who informed me that he was unable to open the file. I went back to original file and checked to make sure I could open it, which i could, and then uploaded the file onto a shared network (thinking maybe somehow email was causing an issue). Still, he cannot open the file. STAAD will start to open and read the file before stalling and/or freezing until they close the program. After speaking with other colleges, some have found this issue before when trying to open certain files with V8i that were created or saved with the CONNECT edition. 

Are there any documented issues similar to what I'm describing above? I've attached the file below for reference.

Thanks,

.PSLA7 E-19-5 and E-5-B-1 FDN and MPS Tr1_rmb reveiw.std

Parents
  • This is happening because there has been a change in the way the software handles the Taub iterations within the Direct Analysis. In old versions ( v8i) there used to be a notional load factor as part of the DIRECT ANALYSIS definition which used to dictate whether Taub iterations would be carried out or not ( 0.002 meant it would be carried out whereas 0.003 meant it would not). In CE we have taken out that parameter from within the definition as it was leading to confusion because users were thinking that if they specified the notional load factor there, that would automatically handle the notional load generation whereas in reality, it was more of a switch that the software was using to determine whether the Tau-b iterations would be carried out or not. So to make it more intuitive, we added a check box for Perform Tau-b Iteration as part of the Direct Analysis command itself ( NOT part of definition anymore) which users can use to turn off the Tau-b iterations if needed ( it is on by default). This change has led to the addition of the term TBITER as part of the Direct Analysis command in the CE. When you are trying to open the file in STAAD.Pro v8i, the GUI is not able to read that command and is getting locked up. So if for any reason, you need to open models from the STAAD.Pro CE with Direct Analysis commands like this, in STAAD.Pro v8i, you would have to make a couple of manual edits to the input command file from the CE, like remove the TBITER from the analysis command and add the NOTIONAL 0.002 as part of the DIRECT ANALYSIS definition. The edited file would then open in STAAD.Pro v8i.

    Having said that, STAAD.Pro v8i should have better handled the situation with an error message rather than just locking up. I will bring this to the attention of the STAAD.Pro product management/development team. 



Reply
  • This is happening because there has been a change in the way the software handles the Taub iterations within the Direct Analysis. In old versions ( v8i) there used to be a notional load factor as part of the DIRECT ANALYSIS definition which used to dictate whether Taub iterations would be carried out or not ( 0.002 meant it would be carried out whereas 0.003 meant it would not). In CE we have taken out that parameter from within the definition as it was leading to confusion because users were thinking that if they specified the notional load factor there, that would automatically handle the notional load generation whereas in reality, it was more of a switch that the software was using to determine whether the Tau-b iterations would be carried out or not. So to make it more intuitive, we added a check box for Perform Tau-b Iteration as part of the Direct Analysis command itself ( NOT part of definition anymore) which users can use to turn off the Tau-b iterations if needed ( it is on by default). This change has led to the addition of the term TBITER as part of the Direct Analysis command in the CE. When you are trying to open the file in STAAD.Pro v8i, the GUI is not able to read that command and is getting locked up. So if for any reason, you need to open models from the STAAD.Pro CE with Direct Analysis commands like this, in STAAD.Pro v8i, you would have to make a couple of manual edits to the input command file from the CE, like remove the TBITER from the analysis command and add the NOTIONAL 0.002 as part of the DIRECT ANALYSIS definition. The edited file would then open in STAAD.Pro v8i.

    Having said that, STAAD.Pro v8i should have better handled the situation with an error message rather than just locking up. I will bring this to the attention of the STAAD.Pro product management/development team. 



Children
No Data