What are the dynamical consequences of creating a marker on a flex body (.mnf) with preserve_location (away from native nodes) ? How are forces/torques at the marker implemented on the body ?
What are the dynamical consequences of creating a marker on a flex body (.mnf) with preserve_location (away from native nodes) ? How are forces/torques at the marker implemented on the body ?
Hi Ziad - The forces and torques should be implemented as if they were applied to the node with no offset, thus resulting in no additional/unwanted forces/torques.
In the .cmd file no node_id line exists for such a marker and I could not see a white leader line in Aview. How is the associated node determined ? Is it the CM of the part ?
Here is what the Adams Solver Documentation read for the MARKER statement's NODE (i.e. NODE_ID) argument:
"If the NODE argument is not specified for a marker on a FLEX_BODY, the marker behaves as if it were attached to a rigid body; its position, velocity, and acceleration are invariant to deformation, and all forces/torques defined on that marker only project onto the rigid body degrees of freedom."
If you read further in the Adams Solver online help for the marker statement you can see that you can specify a node for the marker, and if the marker is offset from this node, a rigid lever is used to connect the marker to the node.
If multiple nodes are specified, the position of a marker relative to BCS is a least square weighted average of the relative position of the attachment nodes in their deformed configuration.
