Flexcom > New Features! > Known Software Faults

Overview

The following faults are present in Flexcom 8.13.2. More detailed information on each fault is provided in the following sections.

No	Issue	Severity
1	Wind turbine simulations fail due to a licensing issue	Major
2	*FLOATING BODY keyword ignores node label information, leading to incorrect application of hydrodynamic loading	Minor
3	Program crash when reduced database storage is used in combination with mooring line elements	Minor
4	Sliding pipe-in-pipe connections may be assigned an incorrect orientation vector	Major

Detailed Information

Issue 1: Wind turbine simulations fail due to a licensing issue

•Related Topics: Network Licensing

•Description: It is not possible to run wind turbine simulations due to a fault in the licensing code.

•Workaround: None. You must upgrade to a later version.

Issue 2: *FLOATING BODY keyword ignores node label information, leading to incorrect application of hydrodynamic loading

•Related Topics: Floating Body

•Description: The *FLOATING BODY keyword accepts nodal inputs, allowing you to identify the centre of gravity, centre of buoyancy, centre of hydrodynamic forces (also known as the force RAO reference point) and centre of drag. These inputs may be specified as node numbers or node labels. If you specify node labels, the program ignores the CoB, CoF and CoD labels, and applies all forces at the centre of gravity location. This includes hydrostatic stiffness, force RAOs, added mass, radiation damping and (concentrated) viscous drag.

•Workaround: Specify node numbers rather than node labels.

Issue 3: Program crash when reduced database storage is used in combination with mooring line elements

•Related Topics: Customised Database Contents

•Description: If your model contains elements with Geometric Properties in Mooring Line Format, and you request reduced database storage via the Customised Database Contents option, the simulation can fail due to a database writing error.

•Workaround: Request full database storage via the Standard Database Contents option.

Issue 4: Sliding pipe-in-pipe connections may be assigned an incorrect orientation vector

•Related Topics: Sliding Connections

•Description: Sliding pipe-in-pipe connections may be set-up incorrectly by Flexcom 8.13.2 and Flexcom 8.13.3. The algorithm which selects the appropriate primary and secondary elements does not function correctly in all cases, following a restructuring process undertaken during the development of Flexcom 8.13. This fault relates only to models with sliding pipe-in-pipe connections and it is usually encountered when there are several elements which share the same node (e.g. when several elements meet at a branch/intersection point in the model). If the program selects an inappropriate element, the connection stiffness can be applied in an incorrect direction.

•Workaround: There is no workaround, so you are advised to upgrade to Flexcom 8.13.4 or later. If it is not possible for you to upgrade, you could perform some spot-checks on the connected node pairs using the *PRINT keyword. If you are satisfied that the connections are set-up correctly for your particular model, you may continue to use Flexcom 8.13.2 or Flexcom 8.13.3.