Is there amywhere that i can find a complete reference of all of the commands and their propper usage in a .str file? Looking at a couple of examples on this form i have found that it is possible to add custom materials and sections using the .str file format. I would like to write these files directly rather than using the api. Is there any where i can find more info on this? For example i would like to create w sections with custom dimensions. I would also like to name the custome materials that i am using for now i can use the NAMe keyword after defining a materials physical properties to assign a name to the specific dimension set, is there some way to do this for materials as well? Is there any document out there explaining these options?
Solved! Go to Solution.
Yes, the description of English syntax of STR text file is contained in R97mod01.doc file, which can be found in the following folder for Autodesk Robot Structural Analysis 2012:
C:\Program Files\Common Files\Autodesk Shared\Structural\Help\2012
or in 64-bit systems
C:\Program Files (x86)\Common Files\Autodesk Shared\Structural\Help\2012
This folder contains also description of some other language syntax (syntax of STR file depends on language version of Robot).
I have also attached R97mod01.doc to this post.
But it is important to know that STR text file is no longer developed and it does not support many features supported by RTD binary file and available through API. For example panels and meshing of them, code design paramaters, job preferences related with the model, etc.
As concerns material definition through STR it is in reality not adding new material but overwriting for specific project properties of already existing material (if material with appropriate name is not existing it is reported as syntax error).
I hope these explanations will be helpful.
If this post answer your question please click "Accept as Solution".
It will help everyone to find answer more quickly!
Dear! I've got mad trying to find this syntax, and it was in my computer!! :-(
¿Why the .STR format is gonna be deprecated? Structures doesn't begin nor end with RSA.
¿Why my home-made-programs will not be able to easyli generate a model I can proces with ROBOT?
Remember civil-engineering and structural specialist all began writting our own pre, proc and post proces programs and probably won't be very happy to throw away the work of years of profession to adapt all our production to just one soft...
On the other hand, having a simple (and well documented, not-man-hidden ;-) text format throw wich add RSA to our production process seems a more intelligent strategy (yes, an open Visual language helps too, but not's the usual way we did it ;-)
Nevertheless, all of us know that marketing guides are from day to day more and more far away from production sites (and ¿who is the best paid CEO in Autodesk? ;-)
Gui Gon Se
architect and structural designer
I agree, I say bring back and further develop the .str format to have the same capabilities as the API. Its more versatile, more stable, simple and strait forward. I prefer it and would use it in place of the API if it were an option.