The CFX implementation only supports "co-simulation mode" using Functional Mockup Interface 2.0, not "model exchange".

Only transient analysis is supported. Steady-state analysis is not supported. Time must be the independent variable in the Functional Mockup Units.

Transient blade row cases are not supported.

If an FMU does not specify the units, you will need to ensure that the correct values are passed in the arguments. Simply divide the input by the expected quantity dimension. For details, see Units of FMU Output Variables.

Both integer and logical parameters are represented by real values inside the CFX-Solver, and converted during communication with FMUs. CFX implementation does not support FMU parameters of strings or enumeration types.

For an FMU input parameter with a variability of "fixed", you cannot specify a value using an expression that resolves to different values. You can specify a value for such an FMU input parameter using a numerical value or an expression that resolves to a constant value.

Special ASCII characters are supported for FMU scalar variables via the Value Name setting (see Functional Mockup Unit Instance in the CFX-Pre User's Guide); CFX Object names are altered to avoid such characters. Non-ASCII Unicode characters are not supported.

Clean solution restarts are not possible if the FMU cannot serialize the state (canSerializeFMUState is equal to "false" or is not set in the .xml file within the .fmu file).

If you specify more than one FMU, those FMUs are assumed to be order-independent. CFX provides no control of the order of execution.