By default the ANCF node of (position, direction) type should have no atomic mass or inertia. Previously it had non-zero values. NOTE: in order to write an implementation that could be tested in short time, there is a sort of a hack: the current ChNodeFEAxyzD node  embeds a ChLcpVariablesBodyOwnMass interface to solver (the one that was developed for the rigid bodies). Yes, that is a 6-dof variable as needed, but the mass&inertia info stored in that ChLcpVariablesBodyOwnMass  is overkill for the ANCF node (and, moreover, it is also not well suited to use it in the ANCF context, where the D info is not a rotation info like in rigid bodies).
By default the ANCF node of (position, direction) type should have no atomic mass or inertia. Previously it had non-zero values.
NOTE: in order to write an implementation that could be tested in short time, there is a sort of a hack: the current ChNodeFEAxyzD node  embeds a ChLcpVariablesBodyOwnMass interface to solver (the one that was developed for the rigid bodies). Yes, that is a 6-dof variable as needed, but the mass&inertia info stored in that ChLcpVariablesBodyOwnMass  is overkill for the ANCF node (and, moreover, it is also not well suited to use it in the ANCF context, where the D info is not a rotation info like in rigid bodies).

jcmadsen/chrono,jcmadsen/chrono,jcmadsen/chrono,jcmadsen/chrono,jcmadsen/chrono,jcmadsen/chrono,jcmadsen/chrono