MBREQM – Multi-body output request based on markers
Defines a multi-body solver output request to output displacement, velocity, acceleration, or force with respect to markers.
|
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
|
MBREQM |
RSID |
RID |
TYPE |
IMARK |
JMARK |
RMARK |
|
|
|
|
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
|
MBREQM |
20 |
234 |
DISP |
20 |
30 |
10 |
|
|
|
|
Field |
Contents |
|
RSID |
Request set identification number. (Integer > 0) |
|
RID |
Request identification number. (Integer > 0) |
|
TYPE |
Output type (DIS or VEL or ACC or FRC). No default – see comment 1 |
|
IMARK |
Marker ID. (Integer > 0) – see comment 2 |
|
JMARK |
Marker ID. Default = blank; (blank or integer > 0) – see comments 2 and 3 |
|
RMARK |
Reference marker ID. Default = blank; (blank or integer > 0) – see comment 4 |
Comments
Output type should be specified to one of the following (DIS, VEL, ACC or FRC). DIS – Displacement request; VEL – Velocity request; ACC – Acceleration request; FRC – Force request.
The output request is usually of IMARK with respect to JMARK resolved in RMARK.
If the JMARK is not specified, the results are with respect to global frame.
If the RMARK is not specified, the results are resolved in the global frame.
Request set will be specified in the subcase definition.
Request ID must be unique with respect to all other MBREQM and MBREQE cards.
Go To
Guidelines for Bulk Data Entries