— For ADINA Users Only —

This is a restricted area meant for current ADINA users only. If your license does not include current support of ADINA, please kindly exit this page.

ADINA 9.0.7 has been released.

These Useful Hints and Issues, while reported for the specific version 9.0.7, are usually also applicable to the ADINA versions 9.0.6, 9.0.5, 9.0.4, 9.0.3, 9.0.2, 9.0.1 and 9.0.0.

Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.7

Issue No. 48, posted March 27, 2015

The 3D-Iterative solver might not converge if the prescribed displacement unloading option is used.

As a workaround, use the sparse solver instead of the 3D-Iterative solver if the prescribed displacement unloading option is used. This bug is fixed in v. 9.0.8.

Issue No. 47, posted March 27, 2015

When a model created in the AUI contains more than 1 element group and an Import Nastran command is run before the Export Nastran command, the exported Nastran file will contain elements with the same element labels.

As a workaround, specify the AUI command 'CONTROL ELEMENT-LABEL=UNIQUE' before generating any mesh in the AUI model. This bug is fixed in v. 9.0.8.

Issue No. 46, posted March 27, 2015

When meshing with quadrilateral elements, every geometry point on the face must have exactly 2 edges only (i.e., must be a manifold face), otherwise the AUI crashes.

There is no workaround. This bug is fixed in v. 9.0.8.

Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.6

Issue No. 45, posted March 16, 2015

In a 2D FSI fluid model, if the mesh is imported from a Nastran file, some nodes on the defined FSI boundaries are not processed correctly.

There is no workaround. This bug is fixed in v. 9.0.7.

Issue No. 44, posted March 16, 2015

A fluid model with some leader-followers can be loaded into AUI 9.0, but the AUI hangs when trying to write the data file.

There is no workaround. This bug is fixed in v. 9.0.7.

Issue No. 43, posted March 16, 2015

In a frequency analysis with cyclic symmetry and contact, the results (frequencies, mode shapes and modal stresses) might be wrong if there is more than one contact group in the model.

As a workaround, use only one contact group in the model. This bug is fixed in v. 9.0.7.

Issue No. 42, posted January 30, 2015

If the central difference method is used, and nonlinear rigid links are present in a model, and prescribed displacement/velocities or accelerations are applied, then results might be obviously incorrect if the model is subjected to large rotations.

There is no workaround. This bug is fixed in v. 9.0.7.

Issue No. 41, posted January 30, 2015

The AUI cannot generate the correct boundary condition in a 2D FSI model when the fluid and structural meshes are imported in Nastran format. The error messages are

   Invalid boundary definition found near node ... and ... (in the user interface)

   Invalid boundary condition found – FSI boundary ... (in the ADINA-F .out file)

For the bug to be triggered, both the following must be true:

  1. It is a 2D model.
  2. The model mesh is imported into the AUI in Nastran format.

There is no workaround. This bug is fixed in v. 9.0.7.

Issue No. 40, posted January 30, 2015

ADP-MESH in the case of a swept mesh that deforms transversally is unable to remove the transversal movement in the adapted meshes.

This is not a bug since as the mesh deforms, it becomes the new geometry. Since the geometry becomes distorted transversally, the new mesh which must follow the geometry picks up that transversal motion and stays distorted.

In the case of swept meshes, we recommend then to add the parameters DX, DY, DZ to the ADP-MESH command. The values should be the same as the ones that were used in the BODY SWEEP command to create the initial mesh. This will have the effect of removing any transversal motion in the mesh on the side walls.

Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.5

Issue No. 39, posted December 19, 2014

ADINA stops with a sparse solver internal error message when using contact with birth/death and consistent stiffness, under the conditions given below. The message is

SOLVER INTERFACE ERROR: CODE = ....

Sparse solver internal error, please contact ADINA R&D, Inc.

For the bug to be triggered, the following must all be true:

  1. There is more than one contact group. For example, contact groups with numbers 1 and 2.
  2. The consistent stiffness option is used for contact group 1.
  3. Contact group 2 has its birth time greater than the first solution time.

As a workaround, do not use the consistent stiffness option. This bug is fixed in v. 9.0.6.

Issue No. 38, posted October 31, 2014

The calculation of the Hermitian beam element stiffness matrix is incorrect under the following conditions:

  1. Product of inertia of the cross-section is non-zero, and
  2. Shear correction factors are non-zero

Condition 1 occurs either for the general cross-section when the product of inertia is nonzero, or for the L section when the cross-sectional axes are aligned with the legs of the section.

Depending upon the cross-section geometry, the stiffness matrix might have negative pivots.

As a workaround, do not specify shear correction factors. This bug is fixed in v. 9.0.6.

Issue No. 37, posted October 31, 2014

When using the constraint function contact algorithm in ADINA, contactor nodes connected to a master via rigid links and possessing a constrained degree of freedom are erroneously identified as nodes with no active degrees of freedom.

When those nodes come into contact with a rigid target, this results in ADINA giving a spurious message in the .out file stating "Rigid to rigid contact detected and ignored", and missing contact.

There is no workaround. This bug is fixed in v. 9.0.6.

Issue No. 36, posted October 31, 2014

In the AUI, unsteady particle tracing stops with an internal error message when particle tracing is used within adaptive meshes (e.g., SAM adaptive meshes). The internal error message is

**** INTERNAL ERROR: TRFLZM: Bad IGEL = ...

There is no workaround. This bug is fixed in v. 9.0.6.

Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.4

Issue No. 35, posted October 1, 2014

ADINA stops with an error message when running a fluid potential element model with result output in universal file requested.

There is no workaround. This bug is fixed in v. 9.0.6.

Issue No. 34, posted October 1, 2014

The universal file result output from ADINA is wrong if the model contains spring elements. Consequently, the universal file cannot be imported into I-DEAS for post-processing.

There is no workaround. This bug is fixed inv. 9.0.5.

Issue No. 33, posted October 1, 2014

In the AUI, when a spline line is converted to an edge as a result of the BODY SHEET command, the subdivision of the line is not properly transferred to the corresponding edge.

There is no workaround. This bug is fixed in v. 9.0.5.

Issue No. 32, posted October 1, 2014

For models containing pipe-shell elements, the warping degrees of freedom cannot be listed in the AUI.

There is no workaround. This bug is fixed in v. 9.0.5.

Issue No. 31, posted October 1, 2014

When a Nastran model consisting of different types of 3D solid elements (CHEXA, CPENTA, CPYRAM, CTETRA) sharing the same property ID is imported into the AUI, and the option SPLIT=NO (not the default) is used, the ADINA stress/strain result output in the op2 file is wrong.

The stress/strain display in a third-party postprocessor, e.g., FEMAP or FEMFAT will show very discontinuous results.

The workaround is to use the default option SPLIT=YES when importing Nastran models with different types of 3D solid elements. This bug is fixed in v. 9.0.5.

Issue No. 30, posted September 3, 2014

ADINA crashes when the number of points on the stress-strain curve for a nonlinear elastic material exceeds 100.

There is no workaround. This limitation is removed in v. 9.0.5.

Issue No. 29, posted September 3, 2014

In some cases, the AUI crashes when turning on the 'Display Beam Cross Section' option. The crash usually occurs when there are Hermitian beam elements that refer to cross sections that were deleted.

As a workaround, avoid the deletion of any cross section that is referred to by beam elements. This bug is fixed in v. 9.0.5.

Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.3

Issue No. 28, posted July 28, 2014

When direct FSI coupling is used in conjunction with contact, the incremental displacements are scaled so that the contact overlap is minimal. The purpose of this scaling is to prevent any fluid mesh adjacent to the contact from becoming overdistorted.

In some cases, this scaling can prevent convergence of the solution procedure. The scaling procedure has been improved in v. 9.0.4.

When convergence is not reached in previous versions of ADINA, use iterative FSI coupling.

Issue No. 27, posted July 28, 2014

If pressure loading is applied to the edges of a face that is discretized with a mapped mesh of 2D elements, the data (.dat) file cannot be created.

There is no workaround. This bug is fixed in v. 9.0.4.

Issue No. 26, posted June 30, 2014

ADINA 9.0 and earlier versions accepted 3D plane stress elements (membrane elements) that are initially warped. However, ADINA assumes that 3D plane stress elements are initially flat.

ADINA version 9.0.3 issues an error message and stops when initially warped 3D plane stress elements are input. The workaround is to use 3-node elements which can be most effective for membrane analyses.

Issue No. 25, posted June 30, 2014

The ADINA program does not print strain energy in linear static solutions if shell elements are used and some of the shell nodes are attached to either rigid links or beam/isobeam/pipe elements, or have rotational fixities.

There is no workaround. This bug is fixed in v. 9.0.4.

Issue No. 24, posted June 30, 2014

In 2D contact analysis, when 2D solid elements are created in the XZ or XY plane, the results of distributed contact tractions output by the REACTIONPLOT command are not correct, with the plotted values always being zeros.

As a workaround, create the model in the YZ plane. This bug is fixed in v. 9.0.4.

Issue No. 23, posted June 30, 2014

Contact detection does not work in all cases when double-sided contact is used in conjunction with FSI with direct coupling. Nodes might pass through the target surface without contact being detected.

As a workaround, either use FSI with iterative coupling, or use single-sided contact instead of double-sided contact.

As a side effect of the bug fix, frictional contact in FSI (either with single-sided or double-sided contact) is improved. Hence slightly different results might be obtained.

This bug is fixed in v. 9.0.4.

Issue No. 22, posted June 30, 2014

The porthole file cannot be loaded in the AUI in a standard explicit restart analysis if the implicit-explicit solution flag is switched on and an explicit method is the first solution option after restart.

There is no workaround. This bug is fixed in v. 9.0.4.

Issue No. 21, posted June 30, 2014

When a GPFORCE result is requested for op2 output, the program crashes when ATS acceleration takes place during the solution and result saving is not requested at the final step of the solution.

For example, an analysis has 10 time steps and result saving is requested only for step 10; if ATS acceleration takes place and the solution is completed in 7 time steps, the program crashes when processing the GPFORCE results.

There is no workaround. This bug is fixed in v. 9.0.4.

Issue No. 20, posted June 30, 2014

When a face is meshed with the mapped meshing option (MESHING=MAPPED in the command GFACE), the contact information is not updated.

As a workaround, generate the mesh before defining the contact surfaces.  This bug is fixed in v. 9.0.4.

Issue No. 19, posted June 2, 2014

The isobeam nodal forces in the AUI display and program output listing are wrong in large displacement analysis because the forces are not calculated correctly according to the deformed beam local axes.

There is no workaround.  This bug is fixed in v. 9.0.4.

Issue No. 18, posted June 2, 2014

When performing an ADINA Thermal analysis with a large model to obtain a mapping file, the program may give wrong results on 64-bit Windows computers, or crash on Linux computers.

As a workaround, assign to MSTORE (Memory for Storing Model Data) a value greater than the value of MESTIM (Estimated Memory to be Taken) printed in the out file; this will often be at least 200 MB, possibly more than 400 MB for larger problems. This bug is fixed in v. 9.0.4.

Issue No. 17, posted June 2, 2014

In the AUI 9.0.0 to AUI 9.0.3, the distance between integration points on the pipe element is computed wrongly for the graphs along result lines of pipe integration points.

There is no workaround.  This bug is fixed in v. 9.0.4.


Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.2

Issue No. 16, posted April 30, 2014

The command to generate a mesh around a crack (CRACK-M MESH) does not allow the creation of 20-node elements (8 and 27 node elements are allowed). Also, if there is no second crack body but the number of subdivisions in the tangential direction is given for the second crack body (NDIVTAN2) in the command to subdivide crack bodies (CRACK-M SUBDIVIDE), the virtual shifts generated will be wrong (J-VIRTUAL-SHIFT CRACK-M).

As a workaround, use 8 or 27 node elements, and in the case where there is no second crack body, set NDIVTAN2=0. These bugs are fixed in v. 9.0.3.

Issue No. 15, posted April 30, 2014

For deformation-dependent concentrated force loadings, the program crashes if time functions have gaps in the label numbering.

As a workaround, use consecutive numbers in the time function labels. This bug is fixed in v. 9.0.3.

Issue No. 14, posted April 30, 2014

In versions 9.0.2 and earlier, ADINA crashes when there are 7-node triangular 3D contact segments and when contact compliance is used.

As a workaround, remesh so that there are no 7-node triangular 3D contact segments, or turn off contact compliance. This bug is fixed in v. 9.0.3.

Issue No. 13, posted April 30, 2014

In versions 9.0.2 and earlier, the porthole file cannot be loaded when there are 3D-shell element groups in the model and when nodal point forces are saved (not the default) for the 3D-shell element groups.

As a workaround, do not save nodal point forces in the 3D-shell elements. This bug is fixed in v. 9.0.3.

Issue No. 12, posted April 30, 2014

In versions 9.0.2 and earlier, the AUI allows the definition of a 3-node pipe element. However, ADINA does not support a 3-node pipe element.

As a workaround, define either a 2-node or a 4-node pipe element. The bug is fixed in v 9.0.3 (so that the AUI gives an error when a 3-node pipe element is defined).

Issue No. 11, posted April 30, 2014

In version 9.0.2 and earlier, there is a bug involving beam distributed loads and beam definitions using orientation vectors. When the beam element is defined using an orientation vector, then, when there is beam distributed loading from Nastran input, or beam distributed loading from the LOADS-ELEMENT command, ADINA crashes.

As a workaround, define the beam element using auxiliary nodes. This bug is fixed in v. 9.0.3.

Issue No. 10, posted April 16, 2014

When Lumped Mass Matrix is selected (Menu > Control > Analysis Assumptions > Mass Matrix) for an ADINA model, the AUI dialog box for defining matrices for general elements does not show the input columns for stiffness, damping and stress matrices.

As a workaround, input the matrices using an AUI *.in file when a lumped mass matrix is used with general elements. This bug is fixed in v. 9.0.3.

Issue No. 9, posted April 16, 2014

The AUI program may crash when modifying or deleting a contact surface which is defined on geometry entities that have been deleted.

There is no workaround. This bug is fixed in v. 9.0.3.

Issue No. 8, posted April 16, 2014

During a modal superposition analysis of a very large model, if a large number of modes is requested, the program crashes.

There is no workaround. This bug is fixed in v. 9.0.3.


Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.1

Issue No. 7, posted April 16, 2014

When a group-based gravity loading is used in a linear static solution, the program stops with an error message.

As a workaround, use model-based gravity loading. This bug is fixed in v. 9.0.2.

Issue No. 6, posted April 16, 2014

If an *.idb file containing Parasolid parts is opened in the AUI, and the Parasolid parts are then modified and saved to another *.idb file, the Parasolid parts might be invalid when this new *.idb file is opened in the AUI. When the Parasolid parts are invalid, the program gives an error message.

There is no workaround. This bug is fixed in v. 9.0.2.

Issue No. 5, posted March 13, 2014

In a 6DOF spring element group, up to 6 nonlinear stiffness curves can be assigned to the elements. If the sum of all the force-displacement points in all the assigned nonlinear stiffness curves is different for any of the elements in the group, the ADINA program crashes.

As a workaround, make sure that the sum of all the force-displacement points in all the nonlinear stiffness curves assigned to 6DOF spring elements within the same element group is the same. This bug is fixed in v. 9.0.2.

Issue No. 4, posted March 13, 2014

If the analysis type is set to Linear Buckling, and there is a user-supplied load defined in the model, ADINA crashes when it reads the user-supplied load from the *.dat file.

There is no workaround. This bug is fixed in v. 9.0.2.


Useful Hints and Issues
Regarding the Use of the ADINA System, v. 9.0.0

Issue No. 3, posted February 17, 2014

In a model created in the AUI, if an element group contains different 3D solid element types, e.g., bricks, wedges and tetrahedrals, and Nastran op2 output is requested, the element labels in the ADINA data (.dat) file may be inconsistent with the exported Nastran model (.nas) file. As a result, when the op2 file is loaded into a third party post-processor, e.g., Femap, stress/strain results for some elements are missing.

As a workaround, put only one type of element into each element group if possible. This bug is fixed in v. 9.0.1.

Issue No. 2, posted January 31, 2014

This bug concerns contact tractions computed for 3D contact conditions in which higher-order contact segments are used. When the contact occurs over a line of nodes in the model, the contact tractions output at the mid-side nodes are correct but the contact tractions output at the corner nodes are much too small.

Note that when the contact occurs over an area, such as over one or more contact segments, there is no bug and all of the contact tractions are correct.

While there is no workaround, the contact tractions output at the corner nodes can simply be ignored. This bug is fixed in v. 9.0.1.

Issue No. 1, posted January 15, 2014

When an orthotropic material is modeled with 2D solid elements in a plane other than the YZ-plane, and the 'Show Material Axes' option is turned on in the AUI, the display of the orthotropic axes is not correct. The solution, however, is not affected.

There is no workaround. This bug is fixed in v. 9.0.1.



For Useful Hints and Issues regarding the use of earlier versions of the ADINA System, see here

Version 8.9       Version 8.8       Version 8.7       Version 8.6       Version 8.5       Version 8.4