22 October 2018
- Last edited 22 October 2018
You say you get a warning that it is overconstrained, but isn't the warning that your model may be overconstrained? You can get rid of the warning if you exclude that single node from the scoping of the first remote point. An image would help me understand what you are trying to do.
If you want to lock rotation of a cylindrical surface but allow bending, a remote displacement sounds like a good way to do that. You can limit the slow down by limiting the number of nodes that are included. For example, instead of selecting the cylindrical face, select the circular edge.
The Padt blog was referring to a model where a remote force and remote moment were each individually created at the same remote location on the same face. This is wasteful because two remote points are created and two sets of CEs are created to the same surface. It's more efficient to create one remote point and one set of CEs then apply the two loads, a force and a moment to the remote point.
But if you have two remote points at different locations in space, you can't use that method, you need two remote points.