Is it possible to print rotational dofs in .dat file?

Postprocessing/Visualization
1

I have a reference node that is part of a kinematic constraint. I would like to print the rotational dofs (U4, U5, U6). Is it possible to output these in any way? *NODE PRINT only seems to output translational dofs (U1, U2, U3).

2

You need two *NODE PRINT cards - one for REF NODE (translational DOFs) and one for ROT NODE (rotational DOFs numbered like translational ones):

*Node print, Nset=NSET_REF, Global=Yes
U
*Node print, Nset=NSET_ROT, Global=Yes
U

Or one card if you add them to a common set.

3

Thanks for the reply! Im trying to understand how to apply this to my case. So I have 2 additional nodes defined:

*NODE, NSET=MY_REF_NODE
10001, 0.0, 0.0, 1.0
*NODE, NSET=MY_ROT_NODE
10002, 0.0, 0.0, 1.0

Then, i can use the ref node with my kinematic constraint:

*COUPLING, CONSTRAINT NAME=MY_CONS, REF NODE=10001, SURFACE=MY_SURF, ORIENTATION=MY_ORIENT
*KINEMATIC
2,3

Then i have to create a rigid body for the reference node in order to specify a ROT NODE?

*RIGID BODY, NSET=MY_REF_NODE, REF NODE=10001, ROT NODE=10002

Then i have forces / moments applied to MY_REF_NODE with the *NODE PRINTcards as you have defined in your original reply.

Am i understanding correctly?

4

Actually, I thought you were already using rigid body constraint.

But since you are using *COUPLING with *KINEMATIC, DOFs 1-6 are supported in the reference node. At least for BCs/loads, it may not work for as expected for output.

5

Yeah, looks like this is the relevant line of code:

But im not sure what ipos is exactly. Its possible reference nodes that have dofs 4-6 active may be interpretted otherwise in this function.

6

Since kinematic couplings add rigidity to a surface, maybe you could just use a rigid body constraint (applied to a node set from that surface) instead ?

7

I think that may work, thanks for the help!