Add and Remove Entities

Entities can be added or cut/removed from panels using the Browser Context-Sensitive Menu.

Right-click on the entity folder in the Project Browser and select Add "Entity", or Delete to remove the entity, or Cut to remove the entity and make it available to reinsert/paste it elsewhere.
Tip: You can also add entities by right clicking the "entity" panel button on the toolbar.
Entities can be added/removed from the following panels:
System/Assemby Forces
Analysis Bushings
Command Sets Fields
Points Spring Dampers
Bodies Beams
Vectors Polybeams
Markers Contacts
Spline2D/Curves Solver Variables
Graphics Solver Arrays
Surfaces Solver Strings
Deformable Curves Solver Differential Equations
Deformable Surfaces Control SISOs
Joints Sensors
Motions Outputs
Couplers Datasets
Gears Templates
Advanced Joints Forms

Adding Entities

Each entity that is added requires a variable name, label, and an indication as to whether the entity is single or a pair. An optional descriptive note can also be included. Each variable name must be unique in the system to which the entity is being added. Once an entity has been added, its variable name cannot be changed from a MotionView panel.

Graphics, joints, advanced joints, and spring dampers require additional information in the Add dialog:
  • The graphic type can be specified in the Add Graphic or GraphicPair dialog by selecting from a list of available graphic types.
  • The joint type can be specified in the Add Joint or JointPair dialog by selecting from a list of available joint types. Allow compliance specifies if the joint is replaced by a bushing when the model is switched to the compliant mode. The advanced joint type can also be specified in the Add AdvJoint dialog by selecting from a list of available joint types.
  • The spring damper type can be specified as a coil spring or torsional spring from the Add SpringDamper or SpringDamperPair dialog.

Removing Entities

Before an entity is removed, MotionView prompts you with a list of dependencies associated with that entity and allows you to cancel the action.
Note: There are two areas where you must check dependencies manually: Templex templates and expressions. If the MDL model contains expressions that refer to the entity being deleted, MotionView will not prompt you. Similarly, if the MDL model contains Templex templates that refer to the entity being deleted, you must track those dependencies.