In the Solid Rotor and
Solid Rotor, Fixed Frame interfaces, the
Rotor Axis and
Change Rotor Speed nodes have been deprecated. When opening a model created in an earlier version of COMSOL Multiphysics, all
Rotor Axis nodes are automatically replaced by corresponding
Rotating Frame nodes.
If the model contains any Change Rotor Speed nodes with matching domain selections, the settings will automatically be updated in the corresponding
Rotating Frame node. Any unmatched
Change Rotor Speed nodes must be updated manually.
For those using the COMSOL API for use with Java, manual migration of old models is required. This can be done by replacing old code such as:
If you do not want to use the new and improved Rotating Frame node, the previously default
Rotor Axis node must be added manually. You can do this by adding the following lines of code:
For consistency reasons, the local z direction is used as the axis of rotation in the
Solid Rotor and
Solid Rotor, Fixed Frame interfaces. In most cases, the migration is handled automatically.
However, if a model contains features with manually typed in expressions that rely on the previous local coordinate system, manual migration of the variables is required. One example is a Journal Bearing node with the
Bearing model selected as
Total force and moment. If the first entry in the
Total force user input was manually defined as
1[N/m]*rotsld.jrb1.du2 + 2[N/m]*rotsld.jrb1.du3, the same entry must be updated to
1[N/m]*rotsld.jrb1.du1 + 2[N/m]*rotsld.jrb1.du2.
Also, if you are using the Misalignment node (subnode to, for example, the
Journal Bearing node), along with COMSOL API
for use with Java, manual migration of old models is required. This can be done by replacing old code such as:
If you were using the default plot Whirl, manual migration is needed. You can either delete the existing
Whirl plot (for example
Whirl (rotsld)) and add the new
Whirl result template, or follow these steps: