<
From version < 60.1 >
edited by Isak Björhag
on 2020/02/10 15:36
To version < 61.1 >
edited by Isak Björhag
on 2020/02/10 15:41
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -168,14 +168,15 @@
168 168  
169 169  It is possible to read the material GUID which is the same as the bar_part attribute. Moreover, we can also read the specific material properties of this material as attributes.
170 170  
171 -
172 172  
173 173  There are two different types of XML files in FEM-Design: struxml and fdscript.
174 174  
175 175  (% style="text-align: justify;" %)
176 -== StruXML ==
175 +== XML Schema ==
177 177  
177 +The StruXML format comes with a XML Schema that describes this specific XML type.
178 178  
179 +
179 179  |=(% style="background-color: rgb(29, 89, 152); width: 261px;" %)(((
180 180  (% style="color:#ffffff" %)Latest version
181 181  )))|=(% style="background-color: rgb(29, 89, 152); width: 1216px;" %)(((
... ... @@ -183,40 +183,8 @@
183 183  )))
184 184  |(% style="width:261px" %)StruXML Schema|(% style="width:1216px" %)[[⭳ **Download **>>https://drive.google.com/file/d/1tvHaijL-5PrE6HuR4r6YjKcREs6YZcc5/view?usp=sharing]]
185 185  
186 -(% style="text-align: justify;" %)
187 -Struxml contains the objects and loads of the model. FEM-Design is able to both read and export models to struxml file format. Go to "File/Save as..." and choose struxml as the format. Go to "File/Open" to open the struxml file or just drag it into the FEM-Design window. StruXML is also the format used in exchange models between Revit / Tekla and FEM-Design.
188 188  
189 -
190 -(% style="text-align: justify;" %)
191 -== Fdscript ==
192 -
193 -
194 -(% style="text-align: justify;" %)
195 -Fdscript is used to execute different types of calculations and to export results. For more information about the script function, please visit the [[wiki page.>>doc:FEM-Design API.Run script.WebHome]]
196 -
197 -
198 198  ----
199 199  
200 -= Customer cases =
201 -
202 -
203 -Did you use the API functionality in your project? Please contact us with feedback and you may also be featured on the wiki!
204 -
205 -
206 -== Bridge geometry - Norconsult AS ==
207 -
208 208  (% style="text-align: justify;" %)
209 -The bridge is modeled with shell elements and the geometry is very complex with different thickness and angles of the shells. This is almost impossible to modell by hand so instead it is generated with the API. The geometry is defined as a nodal list with different thicknesses.
210 -
211 -
212 -[[image:1557491889197-384.png||height="594" width="800"]]
213 -
214 -[[image:1557491914708-988.png||height="423" width="1000"]]
215 -
216 -(% style="text-align: justify;" %)
217 -Customer: Norconsult AS
218 -
219 -----
220 -
221 -(% style="text-align: justify;" %)
222 222  (% class="small" %)Disclaimer: All example files, wrappers and documentation are for illustrative and educational purposes and may not interact with FEM-Design in a reliable way depending on your version, installation and content of the files. Furthermore, StruSoft won´t guarantee full support of the API functions since they are customizable by the customer.
Copyright 2020 StruSoft AB
FEM-Design Wiki