-
Notifications
You must be signed in to change notification settings - Fork 3
Known issues
For general issues identified and planned to be fixed see the issue page.
There are some known limitations with the Robot object model that might make some information get lost when pushing to the software. The known limitations are outlined below.
It is important that all unique section properties, materials, constraints and releases have a unique name, to be able to push all objects to Robot. Objects with the same name will be treated as the same object.
Missing Properties:
- Name
Node constraints below
Missing properties:
- Name
Bar releases, materials and Section properties below
Missing properties:
- Name
Note that Robot will try to use pre-existing materials if name of the assigned material matches the name of a material in Robot.
Missing properties:
- DryDensity
- CompressiveYieldStrength
- TensileYieldStrength
- StrainAtYield
When pushing a section property, the adapter first tries to create a standard section based on the name of the section. Which of the section data bases that will be used depends on the RobotConfig. Read the robot object relations page for more details.
Missing properties:
- Corner, toe and fillet radii
- Weld size
- Reinforcement (On concrete sections)
Limitations:
- Name. Some names sometimes gets changed slightly due to matching with pre-existing sections from the database. (CHS 33.7x4.0 => CHS 33.7x4 etc.)
- Area and other related constants might get slightly changed due to the above mentioned missing radii and weld size properties
Limitations:
- PanelType (Always set to 'Slab')
Limitations:
- Available DOF Types: Free, Spring, Fixed
Missing properties:
- Name
Limitations:
- Available DOF Types: Free, Spring, Fixed
While BHoM LinkConstraint implements 12 different constraint types (XtoX XtoYY XtoZZ XXtoXX YtoXX YtoY YtoZZ YYtoYY ZtoXX ZtoYY ZtoZ ZZtoZZ), RobotOM only implements 6 in the IRobotNodeRigidLinkData (RX RY RZ UX UY UZ).