#
Errors and Warning Messages

Here you can find a complete List of all SimulationX Error Messages

From SimulationX 3.7 on, all warnings and error messages have a name to identify them. This name is shown at the end of the message. This page lists notifications with their idents, the message text and a description. Placeholders, such as *%1*, are used by SimulationX to insert context-related content (e.g. model name, variable, equation etc.) specific to the message shown in the ouput area.

Whether a message is shown as an error, warning, notification or not at all depends on the chosen control level which can be changed *(Options>General>Warnings and Errors)*.

## List of all Messages:

Check.ActivityExpressionVariability

Show more ...### The conditional declaration expression must be a parameter expression.

The declaration condition must be a constant expression (parameter or constant).

Example: `Boolean conditionVar; Real v if conditionVar;`

This is an error because `conditionVar`

is a variable and not a parameter.

Solution: Provide the declaration condition with the correct variability.`parameter Boolean conditionVar; Real v if conditionVar;`

Check.ArgNameTwice

Show more ...### Argument name already exists.

Multiple arguments of a function have the same name. Please check the names of the arguments.

Example: `function myProduct input Real argument; input Real argument; output Real result; algorithm result := argument*argument; end myProduct;`

Solution: Choose unique names for the different inputs.`function myProduct input Real argument1; input Real argument2; output Real result; algorithm result := argument1*argument2; end myProduct;`

Check.ArgType

Show more ...### Wrong argument type.

The type of the argument does not match the type in the operator definition. Please check the arguments.

Example: `Real myArray[Boolean]; Real myScalar; equation myScalar = myArray[1];`

Solution: Select the correct types for the operator arguments.`Real myArray[Boolean]; Real myScalar; equation myScalar = myArray[False];`

Check.ArgumentTypeMismatch

Show more ...### Wrong argument type in the function call detected.

The type of the argument does not match the type in the function definition. Please check the arguments.

Example: `function myProduct input Real argument1; input Real argument2; output Real result; algorithm result := argument1*argument2; end myProduct; Integer argument1; Real argument2; Real result; equation: result = myProduct(argument1, argument2);`

Solution: Choose the correct types for the arguments of the function.`function myProduct input Real argument1; input Real argument2; output Real result; algorithm result := argument1*argument2; end myProduct; Real argument1; Real argument2; Real result; equation: result = myProduct(argument1, argument2);`

Check.ArrayArgNotAllowed

Show more ...### Array arguments are not permitted.

Check.AssignToExternal

Show more ...### Assignment to an external variable not permitted.

Assignments to external variables are not permitted. Mark the variable as `outer`

to use it inside the local type.

Check.BadDimensionString

Show more ...### String %1 not a valid dimension description.

Invalid dimension string. Valid dimension descriptions have the syntax `<Number> { ',' <Number>}`

, where Number must be >0. See Modelica Specification, chapter 10 "Arrays".

Check.BadDomainId

Show more ...### Domain identifier is invalid.

Check.BadExternalFunctionCall

Show more ...### Error during call of external function.

There was an error during the call of the external function, e.g. the call signature or the types of parameters and result do not match to the real implementation in the DLL.

Check.BadFirstStringArg

Show more ...### Wrong argument in String function.

A name must be specified as the first argument of the *String* function.

Example: `String("My String");`

Solution: Use a correct variable name.`String myString; String(myString);`

Check.BadFirstStringOpArg

Show more ...### Bad first argument in String function.

Check.BadNrOfOutputArgs

Show more ...### Wrong number of output arguments.

The number of assigned output variables does not match the function definition.

Example: `function myProduct input Real argument1; input Real argument2; Real result; algorithm result := argument1*argument2; end myProduct; Real argument1; Real argument2; Real result; equation: result = myProduct(argument1, argument2);`

Solution: Check whether the outputs of the function are marked with "output" and whether you have assigned the correct number of outputs.`function myProduct input Real argument1; input Real argument2; output Real result; algorithm result := argument1*argument2; end myProduct; Real argument1; Real argument2; Real result; equation: result = myProduct(argument1, argument2);`

Check.BadNumberOfArgs

Show more ...### Wrong number of function arguments.

The number of function arguments does not match the function definition.

Example: `function myProduct input Real argument1; Real argument2; output Real result; algorithm result := argument1*argument2; end myProduct; Real argument1; Real argument2; Real result; equation: result = myProduct(argument1, argument2);`

Solution: Check whether the inputs of the function are marked with *input* and whether you have passed on the correct number of arguments.`function myProduct input Real argument1; input Real argument2; output Real result; algorithm result := argument1*argument2; end myProduct; Real argument1; Real argument2; Real result; equation: result = myProduct(argument1, argument2);`

Check.BadUnitFactor

Show more ...### Bad factor expression.

The given unit has an invalid factor expression.

Check.BoolArrayReq

Show more ...### At least one array component is not of the required type Boolean.

At least one array component is not of the required type Boolean. Please check the data type of the expression.

Check.BoolReq

Show more ...### The expression must be of type Boolean.

The expression must be of type *Boolean*.

Example: `Integer myValue; equation: if (myValue) ... end if;`

Solution: Check if the expression is really a Boolean condition.`Integer myValue; equation: if (myValue > 0) ... end if;`

Check.Break

Show more ...### Invalid Break statement.

The `break`

statement is only permitted in `for`

or `while`

loops.

Check.BusSameType

Show more ...### Bus line variables must have the same value type.

All variables that are connected with each other via a bus component must have the same value type. Please check the types of the respective bus components.

Check.CanNotLoadDll

Show more ...### Cannot load %1.

Check.Cardinality

Show more ...### The argument of the function "cardinality" needs to be a pin.

The argument of the function *cardinality* must be a connector. Please check whether you really used a connection as the argument.

Check.ClockedElseWhen

Show more ...### Invalid Elsewhen statement.

A clocked `when`

statement must not have an `elsewhen`

section.

Example: `Clock myClock1; Clock myClock2; equation when(myClock1) ... elsewhen(myClock2) ... end when;`

Solution: Define each clocked partition individually.`Clock myClock1; Clock myClock2; equation when(myClock1) ... end when; when(myClock2) ... end when;`

Check.ClockedWhenInAlg

Show more ...### Invalid When statement.

A clocked `when`

statement cannot be used within an algorithm section. Move the clocked `when`

statement if possible to an equation section.

Check.CompoundPinFlowVarRef

Show more ...### Reference to flow variable in compound pin not permitted.

References to flow variables in compound pins are not permitted.

Check.ConflictingStartAttr

Show more ...### Conflicting start values.

A variable may have only one start value. Typically, this error occurs when different start values are assigned to two synonyms. Resolve one of the two start value fixations.

Check.ConnectDimNotMatch

Show more ...### Dimensions in Connect statement do not match.

The dimensions of the two variables in the `connect`

statement do not match.

Example: `Integer myOutput[5]; Integer myInput[6]; equation: connect(myOutput, myInput);`

Solution: Check the dimensions of the two variables in the `connect`

statement.`Integer myOutput[5]; Integer myInput[5] equation: connect(myOutput, myInput);`

Check.ConnectDimUnknown

Show more ...### Connector dimension unknown

The dimension of one of the variables in the `connect`

statement is unknown.

Example: `Integer myOutput[:]; Integer myInput[:]; equation: connect(myOutput, myInput);`

Solution: Check whether one of the two variables in the `connect`

statement has a fixed dimension.`Integer myOutput[5]; Integer myInput[:] equation: connect(myOutput, myInput);`

Check.ConnectedConstantsValue

Show more ...### Components of connected connectors must have identical values.

The values of two constants in `connect`

statements must be identical.

Example: `parameter Integer myOutput = 5; parameter Integer myInput = 6; equation: connect(myOutput, myInput);`

Solution: Check whether one of the two parameters/constants in the `connect`

statement has assigned the same values.`parameter Integer myOutput = 5; parameter Integer myInput = 5; equation: connect(myOutput, myInput);`

Check.ConnectNotMatch

Show more ...### Invalid connect statement.

Check.ConnectorComponentsDim

Show more ...### Dimension of connected connector components does not match.

The dimensions of two components in a connector do not match.

Check.ConstantArg

Show more ...### Argument must be constant.

The argument must be a constant value.

Example: `Real myArray[2, 2, 2]; Integer sliceIndex; Integer subDimension; equation: subDimension = size(myArray, sliceIndex);`

Solution: Make sure that the respective variable is a parameter/constant.`Real myArray[2, 2, 2]; parameter Integer sliceIndex = 2; integer subDimension; equation: subDimension = size(myArray, sliceIndex);`

Check.ConstNoValue

Show more ...### Constant has no value.

A constant must have a value assigned to it.

Example: `constant Integer myConstant;`

Solution: Make sure that a value is assigned to each constant/parameter.`constant Integer myConstant = 42;`

Check.ConstReq

Show more ...### Parameter expression must be a constant.

The parameter expression must be a constant.

Check.ConstSubscript

Show more ...### Only constant subscripts are permitted for object arrays.

Only constant subscripts are permitted for object arrays.

Check.CVodeCompiler

Show more ...### No compiler for CVode (External Solver) found.

No compiler for CVode (External Solver) found.

Check.DecomposeArrayWrongTypeAssignment

Show more ...### Wrong types assigned to an array with DecomposeArray=true.

An element of an array with the annotation `DecomposeArray=true`

must be of type *Real*, *Integer* or *Boolean*, but instead it has a value of another type assigned to it. Please check the type of the respective assignment

Check.Der2ArgNotAssigned

Show more ...### Cannot determine partial derivative.

A partial derivative cannot be determined and is *0*, because an argument is not explicitly assigned.

Check.Der2Cycle

Show more ...### Partial derivative of a partial derivative not implemented.

The partial derivative of a partial derivative is not implemented.

Check.DerivativeAnnoDoesNotMatch

Show more ...### The derivative annotation does not match.

The annotation of a function does not match the given derivative. The calculated number of arguments does not match the actual number of arguments.

Check.DerivativeReferenceSelf

Show more ...### The derivative annotation refers to itself.

The derivative annotation refers to itself.

Check.DerOfInput

Show more ...### Input derivative reqired.

A given input needs a time derivative. This cannot be determined numerically. Please add an input for the derivative.

If this error occurs in combination with clocked systems (Modelica Synchronous technology, e.g. when you are using elements from the *Clocked Signal Blocks* library), it is probably caused by the use of a simple *D* component within the clocked controller structure. Please implement a time response at this point (e.g. *DT1*). If this error also occurs in combination with *Code Export*, the Global Symbolic Analysis tries to derive a model input symbolically. In this case, this derivative of that signal must be provided separately. It is best to use the element *Signal Input with Derivatives* from the library *Generic Interfaces* (ident: `InterfacesGeneral.PhysicsSignalInterfaces.GeneralElements.SigInDer`

).

Check.DerVarNotCalculated

Show more ...### Variable %1 cannot be calculated and is set to 0.

For the calculation of a variable a symbolic derivative is necessary, which cannot be performed. This variable serves only as output and does not contribute to the equations system. Therefore, it is set to *0*.

Check.DifferentEnumerationTypes

Show more ...### Invalid comparison of enumerations.

Different enumerations cannot be compared with each other directly.

Example: `enumeration myEnum1 {...}; enumeration myEnum2 {...}; myEnum1 enum1; myEnum2 enum2; equation: if (enum1 == enum2) ... end if;`

Solution: Check if one of the two variables may have the wrong enumeration type. If you really want to compare different enumerations, they can be cast to their integral value with the help of *Integer*. Please note that there is no guarantee that the same alternatives have the same value in different enumerations!`enumeration myEnum1 {...}; enumeration myEnum2 {...}; myEnum1 enum1; myEnum2 enum2; equation: if (Integer(enum1) == Integer(enum2)) ... end if;`

Check.DimAssertArg

Show more ...### Wrong argument dimension.

The argument of the `assert`

function must be a scalar.

Example: `Bool myCondition[5]; equation: assert(myCondition, "Error");`

Solution: Check the dimensionality of the argument. If you really want to check an array of conditions, you can iterate them using a `for`

loop.`Bool myCondition[5]; equation: for i loop assert(myCondition[i], "Error"); end for;`

Check.DimAssignA

Show more ...### Dimension mismatch.

In an assignment, the assigned expression must have the same dimension as the variable on the left.

Example: `Real first[5]; Real second[6]; equation: first = second;`

Solution: Check the dimensionality of both variables.`Real first[5]; Real second[5]; equation: first = second;`

Check.DimAssignE

Show more ...### Dimension mismatch.

In an equation, the left and right sides must have the same dimension.

Example: `Real first[5]; Real second[6]; equation: first = second;`

Solution: Check the dimensionality of the left and right sides of the equation.`Real first[5]; Real second[5]; equation: first = second;`

Check.DimAssignEach

Show more ...### Dimensions not matching in Each modification.

In a modification with `each`

, the lower dimensions of the modified variable must match the dimension of the expression.

Example: `model B parameter Real a[5, 4, 3]; end B; model C Real d[4, 4]; B (each a = d); end C;`

Solution: Check the dimensionality of the `each`

modification.`model B parameter Real a[5, 4, 3]; end B; model C Real d[4, 3]; B (each a = d); end C;`

Check.DimCallArg

Show more ...### Wrong argument dimension.

An argument in a function call has a wrong dimension.

Example: `function arraySum input Real argument[:]; output Real result; algorithm for i loop result := result + argument[i]; end myProduct; Real argument; Real result; equation: result = arraySum(argument);`

Solution: Check the dimensionality of the transferred function argument.`function arraySum input Real argument[:]; output Real result; algorithm for i loop result := result + argument[i]; end myProduct; Real argument[5]; Real result; equation: result = arraySum(argument);`

Check.DimCatFuncArg

Show more ...### Wrong argument dimension.

The `cat`

function needs arguments of equal size in each dimension.

Check.DimCatFuncArgN

Show more ...### Wrong argument dimension.

The `cat`

function needs arguments of equal dimension.

Check.DimCatOpArg

Show more ...### Wrong argument dimension

The given operator needs arguments of equal dimension.

Check.DimCatOpArg1

Show more ...### Wrong argument dimension.

The operator needs arguments of equal dimension, except for the first argument.

Check.DimCatOpArg2

Show more ...### Wrong argument dimension.

The operator needs arguments of equal dimension, except for the second argument.

Check.DimCrossArg

Show more ...### Wrong argument dimension

The argument of the `cross`

function must be a vector of size 3.

Check.DimDiagonalArg

Show more ...### Invalid Diagonal argument.

The argument of the `diagonal`

function must be of vector dimension.

Check.DimensionType

Show more ...### Invalid type for dimension definition.

The type of the given expression cannot be used to specify the dimension! Use as type Integer, Boolean or Enumeration.

Check.DimEntryIsInteger

Show more ...### Wrong element type.

The element in the dimension assignment of a variable declaration must be of type *Integer*.

Check.DimEntryIsScalar

Show more ...### Dimension element must be scalar.

A dimension element of a variable declaration must be of scalar dimension.

Check.DimEntryIsVector

Show more ...### Dimension assignment must be a vector.

The dimension assignment of a variable declaration must be a vector.

Check.DimEqualArg

Show more ...### Dimension mismatch.

The dimensions of the arguments of a given function must be identical.

Check.DimEqualScalarArg

Show more ...### Dimension mismatch.

The dimensions of the arguments of a given function must be identical or scalar.

Check.DimIdentityArg

Show more ...### Invalid Identity argument.

The argument of the `identity`

function must be of scalar dimension.

Check.DimMatrixArg

Show more ...### Invalid Matrix argument.

The higher dimensions (>2) of the arguments of the `matrix`

function must be of size *1*.

Check.DimMismatch

Show more ...### Dimension mismatch.

Dimensions do not match. Please check the dimensionality of the variables.

Check.DimMustMatchBusGenVar

Show more ...### The dimensions of bus variables must match.

The dimensions of bus variables must match.

Check.DimNotCalculable

Show more ...### Dimension cannot be calculated.

The Dimension of a variable cannot be calculated.

Check.DimOuterProductArg

Show more ...### Wrong argument dimension.

The arguments of the function `outerProduct`

must be vectors.

Check.DimRangeArg

Show more ...### Wrong argument dimension.

The arguments of the range operator must be scalars.

Check.DimRelation

Show more ...### Dimension mismatch.

The arguments of a relation must have the same dimension.

Check.DimScalarArg

Show more ...### Invalid scalar argument.

The argument of the `scalar`

function must be a vector.

Check.DimSizeOutOfRange

Show more ...### Argument outside of domain.

The second argument of `size`

lies outside the domain.

Check.DimSkewArg

Show more ...### Wrong argument dimension.

The argument of the `skew`

function must be a vector of size *3*.

Check.DimSymmetricArg

Show more ...### Invalid Symmetric argument.

The argument of the `symmetric`

function must be of matrix dimension.

Check.DimTerminateArg

Show more ...### Wrong argument dimension

The argument of the `terminate`

function must be a scalar.

Check.DimTransposeArg

Show more ...### Wrong argument dimension.

The argument for `transpose`

function must be at least a matrix. Please check the dimensionality of the argument.

Check.DimVectorArg

Show more ...### Incorrect argument dimensions.

Only one dimension of the argument can be greater than *1*. Please check the dimensionality of the argument.

Check.DiscreteAlgebraicLoop

Show more ...### An algebraic loop contains a discrete-time variable.

An algebraic loop contains a discrete-time variable. Use `pre`

in the condition to prevent that.

Check.DiscreteArg

Show more ...### The argument must be a discrete-time value.

The argument must be a discrete-time value. Please check the time dependency of the argument.

Check.DiscreteDer

Show more ...### Derivative of a discrete-time variable is 0.

The derivative of a discrete-time variable is *0*. Please check the time dependency of the variable.

Check.DllBadExeFormat

Show more...### Library or dependencies are not valid Win32 applications.

Library or dependencies are not valid Win32 applications.

Check.DllFunctionNotFound

Show more ...### Function not exported from library.

The function is not exported from library.

Check.DllNotFound

Show more ...### Library or dependencies not found.

Library or dependencies could not be found.

Check.DomainInitFailed

Show more ...### Initializing domains failed.

Initializing the domains has failed.

Check.ElementwiseAddition

Show more ...### Wrong elementwise addition, "+" instead of ".+"

A scalar and an array are added. In accordance with the Modelica standard, the element by element addition ".+" must be used here instead of "+".

Check.EmptyArrayConstr

Show more ...### Empty array constructors are not permitted.

Empty array constructors are not permitted. Make sure that the generated array is not empty.

Check.EndSubscript

Show more ...### "End" not possible.

The subscript `end`

can only be used on arrays (vectors, matrices etc).

Check.EnumArrayReq

Show more ...### At least one array component is not of the required type Enumeration.

At least one array component is not of the required type Enumeration. Please check the data type of the expression.

Check.EnumReq

Show more ...### The parameter expression must be of type Enumeration.

The parameter expression must be of type *Enumeration*. Please check the data type of the expression.

Check.EnumTypeMismatch

Show more ...### The resulting enumeration type is not compatible to this parameter. The expected type (ident) is: %1

The resulting enumeration type is not compatible to this parameter. Expected type (ident): %1. Please check the data type of the expression.

Check.EqMissing

Show more ...### Equation missing.

One of the states is lacking an equation rendering the resulting system of equations singular. Please check the number of equations.

Check.EventCycle

Show more ...### Cycle during event iteration.

Cycle during the event iteration.

Check.EventsDependFromNonDiscrete

Show more ...### An event-generating expression cannot depend on a noEvent condition.

AAn event-generating expression cannot depend on a noEvent condition.

Check.ExternalInfoArg

Show more ...### Invalid external specification.

Invalid external specification in a function. The external argument is not defined.

Check.ExtFuncCallSig

Show more ...### Error in external function signature.

Expressions in an external function call can only be references to local variables *v* or *size(v,n)*.

Check.FixedAndStartAttrMissing

Show more ...### Fixed variable without start value

A variable with `fixed=true`

must have a start value. Specify a valid start value using `start= ...`

.

Check.FixStatesWarning

Show more ...### Fix start values of variables.

Fix the start values of the given variable with `start= ...`

.

Check.ForExprDim

Show more ...### Invalid For expression

The expression in a `for`

statement must be a vector. Please check the dimensionality of the expression.

Check.ForIndexRange

Show more ...### Index variable undefined.

A `for`

variable requires an explicit range or must be used in an index expression. Please check whether the `for`

variable is used in a subscript or specify a valid range.

Check.ForIndexType

Show more ...### Conflicting type of index variable.

The type of a `for`

variable cannot be determined because of conflicts. Make sure that the `for`

variable is only used in subscripts of the same type.

Check.ForIndicesParametric

Show more ...### The expression of a For equation must be a parameter expression.

The expression of a `for`

equation must be a parameter expression. Please check the variability of the expression.

Check.GeneralError

Show more ...### Error.

An error occurred during the symbolical analysis. Please report this error together with the related model to the Helpdesk.

Check.GreaterEqual

Show more ...### %1 must be greater than or equal %2.

An expression has a lower limit which must not be violated.

Check.GreaterThan

Show more ...### %1 must be greater than %2.

An expression has a lower limit that must not be reached.

Check.IfAltDim

Show more ...### Dimension mismatch.

The alternatives of an `if`

statement must have the same dimension. Please check the dimensionality of the corresponding branches.

Check.IfCondition

Show more ...### The condition in an If statement must be of scalar dimension.

The condition in an `if`

statement must be a scalar. Please check the dimensionality of the condition.

Check.IfThenElseAltTypes

Show more ...### If/Then/Else alternatives must have the same value type.

The alternative expressions of `if ... then <ausdr1> else <ausdr2>`

must have the same value type. Make sure that all expressions result in the same type.

Check.IgnoredWhenInitial

Show more ...### A When equation with active condition for initial equations was ignored.

`when`

equation with active condition is ignored for initial equations. Use \"when initial() then\" or \" when {...,initial(),...} then\".

Check.InactiveInstanceUsed

Show more ...### Variable from an inactive component used.

Variables from an inactive component must not be used. Remove the inactive variables from the model or activate the corresponding component.

Check.InactiveVarUsed

Show more ...### Inactive variable used.

Inactive variables must not be used. Remove the inactive variables from the model or activate the corresponding component.

Check.IndexOverrun

Show more ...### Index too big.

An index exceeds the maximum size of the array. Please check the index expression.

Check.IndexUnderrun

Show more ...### Index too small.

An index is smaller than the minimum size of the array. Please check the index expression.

Check.InitialAlgebraicLoop

Show more ...### Algebraic loop during initialization ignored.

Algebraic loops during initialization will be ignored: The affected variable is used without prior assignment. Its value is then *0*.

Check.InputInStartExpression

Show more ...### Model input variable used in parameter.

A variable marked as model input is used in a parameter expression and cannot have the correct value from the start. Please check the variability of the expression.

Check.InputState

Show more ...### Model input is not a state.

A variable depends on a model input and is no longer a state.

Check.IntegerArrayReq

Show more ...### At least one array component is not of the required type Integer.

At least one array component is not of the required type Integer. Please check the data type of the expression.

Check.IntegerReq

Show more ...### The expression must be of type Integer.

The expression must be of type *Integer*. Check the type of expression.

Check.IntRealArg

Show more ...### Wrong argument type.

The given argument must be of type*Integer* or *Real*. Check the type of expression.

Check.InvalidArg

Show more ...### Invalid argument.

An invalid argument was passed on to an operator or a function, e.g. arguments with names before positional arguments. The latter must always be specified first.

Check.InvalidConnect

Show more ...### Invalid Connect statement.

In the `connect`

statement, two SimulationX connectors are connected directly. With this type of connection, a reference in the `connect`

statement must always refer to a connection object. To avoid this error, always connect ports using the SimulationX GUI.

Check.InvalidEMIDll

Show more ...### Invalid EMI DLL.

Check.InvalidEquation

Show more ...### Invalid equation removed.

A trivial invalid equation was removed, e.g. *0=1*.

Check.InvalidUnit

Show more ...### Invalid unit.

Check.InWhen

Show more ...### Invalid function call.

The function `reinit`

can only be called in a `when`

block.

Check.LinSpaceDimMismatch

Show more ...### The third argument of "linspace" must be >=2.

The third argument of `linspace`

must be >=2.

Check.MatchingConnectors

Show more ...### Connected connectors do not match.

Connected connectors do not match. To be able to connect two connectors, the components they contain must have matching names and types. Furthermore, two matching components must have the *flow*, *stream* or *parameter* prefix or one the *input* prefix and the other the *output* prefix or neither a prefix at all.

Check.MatrixReq

Show more ...### The parameter expression must be a matrix.

Check.MissingArg

Show more ...### Missing argument.

The given argument of the function is missing in the function call.

Check.MissingElse

Show more ...### An Else section is required.

Alternatives in the `equation`

section must have an `else`

branch.

Check.MissingInner

Show more ...### Inner component missing.

The `inner`

element of a corresponding `outer`

element cannot be found.

Check.MissingInnerWarning

Show more ...### Missing inner component created.

An element declared as `outer`

is lacking the corresponding `inner`

element. It was generated automatically.

Check.MissingOverloadOperation

Show more ...### Missing overload operation %1 for type %2.

The given overloaded operator cannot be found.

Check.ModifyOuterWarning

Show more ...### Outer components cannot be modified.

Check.MultipleMatchOverloadOperations

Show more ...### Multiple matching functions for the overload operation in %1.

Several suitable functions were found for the overloaded operator. The search for overloaded operators must return exactly one matching function. Delete one of the reported functions.

Check.NAlternatives

Show more ...### Not the same number of equations inside If/Then/Else alternatives.

`if`

/`then`

/`else`

alternatives in equation sections must have the same number of equations, or the condition must be constant.

Check.NeedConnection

Show more ...### The connector %1 needs to be connected.

The given connector must be connected.

Check.NestedWhen

Show more ...### Invalid When statement.

`when`

statements cannot be nested.

Check.NoDefaultArgument

Show more ...### Argument missing.

A value for an argument is missing in the function call of the given function. There is no default value.

Check.NoDiscreteVar

Show more ...### No discrete-time variable.

The given variable must be a discrete-time variable.

Check.NoDllName

Show more ...### Library name missing.

The name of the library in which the given external function is defined is missing. Use the annotation `Library=name`

or `dll=name.dll`

.

Check.NoExtFucRefs

Show more ...### References to external functions are not permitted.

Check.NoFluid

Show more ...### No fluid.

There is no valid fluid referenced in the connection.

Check.NoFuncDerIndRedWarn

Show more ...### No derivative for function %1 available.

The specified function cannot be derived during index reduction. Define a derivative and use the `derivative`

annotation to assign it to the function. See Modelica Specification, chapter 12.7.

Check.NoFuncRefsAllowed

Show more ...### References to external functions not permitted.

References to external functions are not permitted.

Check.NoFunctionCalls

Show more ...### Function calls are not permitted.

Check.NoFunctionCallsAllowed

Show more ...### Function calls not permitted.

Function calls are not permitted.

Check.NoFunctionDerivativeIndexRed

Show more ...### No function derivative for function %1 available.

The specified function cannot be differentiated during index reduction. A simulation is not possible. Define a derivative and use the `derivative`

annotation to assign it to the function. See Modelica Specification, chapter 12.7.

Check.NoNamedArguments

Show more ...### List of name arguments not permitted for function %1.

The given function does not permit lists of name arguments.

Check.NonDiscreteArg

Show more ...### The argument must not be a discrete-time value.

The argument must not be a discrete-time value.

Check.NonMatchOverloadOperations

Show more ...### Could not find matching functions for the overloaded operator in %1.

No suitable function could be found for the given overloaded operator.

Check.NoNonCompoundPinVar

Show more ...### Could not find matching non-compound variable.

Variables of compound pins cannot be referenced, because they are not given a valid value during the calculation. Reference a variable of a normal pin that is connected to the connection.

Check.NoODE

Show more ...### The equation system is not an ODE. The optimization cannot be applied.

Check.NoOutputFct

Show more ...### Function needs at least one output parameter.

Check.NoPartialDer

Show more ...### Cannot determine partial derivative.

A partial derivative cannot be determined.

Check.NoStrings

Show more ...### Strings are not permitted.

Strings are not permitted.

Check.NoStringsAllowed

Show more ...### Strings not permitted.

Strings are not permitted.

Check.NotAConnector

Show more ...### Not a connector.

The argument of `connect`

or "cardinality" must be a connector.

Check.NotAConstRef

Show more ...### Invalid reference.

The given variable is not part of the calculation and is not a constant. It cannot be referenced here.

Check.NotADomain

Show more ...### Identifier not referring to a domain.

The identifier does not refer to a domain.

Check.NotAFluid

Show more ...### Not a valid fluid identifier.

The specified identifier does not refer to an suitable fluid.

Check.NotAFunction

Show more ...### %1 is not a function.

The specified identifier is not a function.

Check.NotAValidConnector

Show more ...### Not a valid connector.

The specified identifier is not a valid connector.

Check.NotAVariable

Show more ...### %1 is not a variable.

The identifier is not a variable. Only instances of simple types (*Real*, *Integer*, *Boolean*, *String* or enumerations), records or derivatives of `ExternalObject`

or their derivatives are permitted here.

Check.NotConnected

Show more ...### Connection %1 is not connected.

The given connection is not connected. All state variables are set to *0*.

Check.NotInFunction

Show more ...### Function call not permitted.

The given function can only be called from outside a function, because it is not stateless.

Check.NotInWhen

Show more ...### Invalid function call.

The given function cannot be called in a `when`

block.

Check.NoVarRefs

Show more ...### References to variables are not permitted.

Check.NoVarRefsAllowed

Show more ...### Variables not permitted.

Variables are not permitted.

Check.NrOutputs

Show more ...### Wrong number of output variables.

Check.NStateEqNotEqual

Show more ...### The equation system is structurally singular.

The system of equations is structurally singular. The number of states does not match the number of equations.

Check.NumericArgType

Show more ...### The argument must be of numeric type.

The argument of the `min`

or `max`

operator must have a numeric value (*Integer*, *Real*, *Boolean*).

Check.OnlyConstants

Show more ...### Only constant expressions are permitted.

Check.OnlyIncludeAnnotation

Show more ...### Only Include annotation in external function.

The external function has only an `include`

annotation and is only used correctly fcorrectly in methods with compiled C-code. The function cannot be evaluated during symbolic analysis. So even constant arguments are not recognized as such. This may cause error messages where constant expressions are needed that can be calculated at the compile time, e.g. in dimension specifications, `if`

/`then`

/`else`

conditions in equations etc.

Check.OnlyOneConnectArgUndeclared

Show more ...### In a Connect statement, only one argument can be an undeclared component of an expandable connector.

In a connect statement, only one argument can be an undeclared component of an expandable connector.

Check.OnlyScalars

Show more ...### Only scalar expression are permitted.

Check.OnlyScalarsAllowed

Show more ...### Only scalar expressions permitted.

Only scalar expressions are permitted.

Check.OnlyShortClassDefInElementRedeclaration

Show more ...The given declaration is not a short class definition. Only short class definitions are permitted as element declarations.

Check.OutputVarRequired

Show more ...### Not an output variable.

In the definition of an external function, the name of the variable used as the return variable of the external C function must refer to an output variable in the corresponding Modelica function.

Check.Overdetermined

Show more ...### The equation system overdetermined.

Check.ParamDefaultValue

Show more ...### Parameter default value used.

The given parameter has no value. The value of the `start`

attribute will be used for the simulation.

Check.ParamDefaultValueMin

Show more ...### Parameter default value used.

The given parameter has no value. For the simulation, the value of the `min`

attribute is used.

Check.ParamNotConstant

Show more ...### Parameter not constant.

Check.ParamNoValue

Show more ...### Parameter has no value.

If no value has been assigned to a parameter and it also has no start or min attribute, a default value (usually 0) is assumed.

Check.PartialDerFctNoArgument

Show more ...### Partial derivative has no argument.

The given partial derivative has no argument.

Check.PartialDerFctNoBase

Show more ...### Partial derivative not referring to function.

The given partial derivative does not reference a function.

Check.PositiveSubscript

Show more ...### Invalid subscript.

Only positive subscripts are permitted in arrays.

Check.QuantityDomainNotFound

Show more ...### Domain not found.

The given domain could not be found.

Check.QuantityInitFailded

Show more ...### Initializing quantity database failed.

Initializing the quantity database has failed.

Check.QuantityNameNotFound

Show more ...### Quantity not defined.

The given physical quantity is not defined.

Check.RealArrayReq

Show more ...### At least one array component is not of the required type Real.

At least one array component is not of the required type Real. Please check the data type of the expression.

Check.RealEquality

Show more ...### Real values in %1 relations should be avoided.

In a comparison, the arguments should not be of type *Real*, because they do not trigger discrete events and in case of small numerical deviations the relation is no longer or never fulfilled.

Check.RealReq

Show more ...### The expression must be of type Real.

In parameters of type *Real*, the expression must also be of type *Real*.

Check.RecordArrayReq

Show more ...### At least one array component is not of the required type Record.

At least one array component is not of the required type Record. Please check the data type of the expression.

Check.RecordCompModification

Show more ...### Record component modification ignored.

If an entire record has a modification, e.g. an assignment with a record constructor call, then modifications of a record component are ignored.

Example: In `R r(a=3,b=4)=R(1,2);`

the modifications `a=3`

and `b=4`

are ignored.

Check.RecordComponentMissing

Show more ...### Record component missing.

In equations between records, the records on both sides must consist of the same components (with the same type and name).

Check.RecordConstrCallNotType

Show more ...### A record constructor can only be called with a record type.

A record constructor can only be called with a record type. An instance was specified. Please select the appropriate type.

Check.RecordReq

Show more ...### The parameter expression must be of type Record.

The parameter expression must be of type *Record*. Please check the type of the expression.

Check.RecordsNotCompatible

Show more ...### Records not compatible.

In case of an equation between records, the records on both sides must consist of the same components (type and name must be the same).

Check.RecordType

Show more ...### Equal record types required

Check.RecordTypeMismatch

Show more ...### The resulting record type is not compatible to this parameter. The expected type (ident) is: %1

The resulting record type is not compatible to this parameter. Expected type (ident): %1. Please check the data type of the expression.

Check.RecordTypeReferenced

Show more ...### Record type directly referenced.

The given identifier refers directly to a record type. Record types can only be referenced in a record constructor call.

Check.Reinit

Show more ...### The Der operator needs to be applied to the first argument of the Reinit operator.

Check.ReinitDim

Show more ...### Wrong dimension.

Check.RelationBooleanTypes

Show more ...### Invalid relation with Booleans.

Boolean expressions cannot be compared with non-Boolean expressions directly. Use the operator `Integer€`

to convert a Boolean value to an integer value.

Check.RelationEnumerationTypes

Show more ...### Invalid relation with enumerations.

Enumerations cannot be compared with other types directly. Use the operator `Integer€`

to convert an enumeration value to an integer value.

Check.ReservedName

Show more ...### A reserved name was referenced.

Check.Return

Show more ...### Invalid Return statement.

The `return`

statement can only be used within functions.

Check.ScalarArg

Show more ...### The argument must be a scalar value.

Check.ScalarReq

Show more ...### The parameter expression must be a scalar value.

Check.ScalarReturnVar

Show more ...### Result variable must be a scalar.

The result variable of an external function must be scalar.

Check.ScalarWhileCond

Show more ...### Invalid While condition.

The expression in the condition of a `while`

statement must be a scalar.

Check.Singular

Show more ...### Equation system is singular.

The system of equations is singular, i.e. the number of equations does not match the number of variables. Each primitive data type (*Real*, *Integer*, *Boolean*, *String*) is counted separately.

Check.SingularType

Show more ...### The equation system is singular for type %1.

Check.SizeInvalidIndex

Show more ...### Invalid index for Size function

The dimension index in argument 2 of the `size`

function for a variable must be in the interval [1, ndims(X)].

Check.StartAttrMissing

Show more ...### Start attribute missing.

The given state has no specified start attribute and is therefore set to a default value.

Check.StartAttrNotFixed

Show more ...### Start value may change.

The start value of the given state is not fixed and may change during the calculation of initial values

Check.StartValueIgnored

Show more ...### The start value is being ignored.

Check.StringReq

Show more ...### The expression must be of type String.

The expression must be of type *String*. Please check the datatype of the expression.

Check.StructSingular

Show more ...### The equation system is structurally singular.

Check.SubscriptEmptyArray

Show more ...### Subscript accessing empty array.

An empty array is accessed by a subscript.

Check.SubscriptsNotAllowed

Show more ...### Subscripts of undeclared components of expandable connectors not permitted.

Indexing undeclared components of expandable connectors is not permitted.

Check.SubscriptType

Show more ...### Incorrect subscript type.

The type of the given subscript of a variable does not match the declared type.

Check.SymanaError

Show more ...### Invalid model.

Errors ocurred during the analysis of the model. Further information can be found in the output area.

Check.SyntaxError

Show more ...### Syntax error.

The Modelica text is syntactically wrong and cannot be processed. Correct it at the reported location and try again.

Check.TernaryArrayReq

Show more ...### At least one array component is not of the required type Ternary or Boolean.

At least one array component is not of the required type Ternary or Boolean. Please check the data type of the expression.

Check.TernaryReq

Show more ...### The expression must be of type Ternary.

The expression must be of type *Ternary* or *Boolean*.

Check.TooManyEquations

Show more ...### Several equations not assigned. Variables missing.

Check.TooManyInitialValues

Show more ...### Too many initial values.

Due to the hierarchical structure of a connection structure, different initial values may exist for several connected variables. The outer ones prevail, and if there are several of them at the same level, the fixed ones prevail.

Check.TooManyOutputs

Show more ...### Too many output variables in function call.

On the left side of an assignment of a function call with several output variables, there are more result variables than the function has outputs. Remove them or add more outputs to the function.

Check.TooManyVariables

Show more ...### Several variables not assigned. Equations missing.

Check.TypeInconsistentEquation

Show more ...### Incompatible types in an equation detected.

The type of the expression on the left side of the equation is not compatible with the one on the right.

Check.TypeInconsistentRelation

Show more ...### Incompatible types in comparison.

Incompatible types cannot be compared.

Check.TypeReferenced

Show more ...### Type referenced.

The given identifier refers to a type. Only references to instances of this type (variables, parameters, constants) are permitted.

Check.UnderFlow

Show more ...### Floating point number too small.

During the calculation, a floating point number was too small.

Check.UnitNameNotFound

Show more ...### Unit not defined.

The given unit is not defined.

Check.UnitReal

Show more ...### The expression before a given unit must be of type Integer or Real.

Units can only be assigned to *Integer* or *Real* expressions.

Check.UnknownArgName

Show more ...### Unknown argument name.

A non-existing argument name was specified in a function call with name-based argument assignments.

Check.UnknownConnector

Show more ...### Unknown connector referenced.

An unknown connection was referenced in a `connect`

statement.

Check.UnknownFunctionCall

Show more ...### Unknown function %1.

Check.UnknownFunctionRef

Show more ...### Unknown function %1 referenced.

An unknown function was referenced in a function call.

Check.UnknownVarRef

Show more ...### Unknown variable %1 referenced.

An unknown variable was referenced.

Check.VarAutoInit

Show more ...### Variable not assigned.

Check.VariableArg

Show more ...### Argument must be a variable.

The first argument of the `reinit`

operator and the second argument of the integral operator must be variables.

Check.VariableInActivityExpression

Show more ...### Variable in declaration condition.

A variable is referenced in the given declaration condition. Only parameters can be referenced.

Check.VectorReq

Show more ...### Parameter expression must be a vector.

Check.WhenExprDim

Show more ...### Invalid When expression.

The condition in a `when`

statement must be a scalar or a vector.

Check.WhenInLoop

Show more ...### Invalid When statement.

A `when`

statement cannot be used within a `for`

or `while`

loop.

Check.WhenOrDiscreteArg

Show more ...### The function %1 needs to be called in a When block, or the argument %2 must be a discrete-time variable.

The argument of the `pre`

operator must be a discrete-time variable. If not, it must be called in a `when`

block.

Check.Writeable

Show more ...### Not writeable.

The left side of an assignment must be either a variable or a constant parameter with `fixed=false`

assigned in an initial algorithm section.

Check.WrongArgType

Show more ...### Wrong argument type.

In a function call, the argument type does not match the type of the input variable of the function, or the *Clock* constructor does not accept arguments of this type.

Check.WrongFluidMixDim

Show more ...### Dimension mismatch.

CodeExport.Forbidden

Show more ...### Code export not permitted.

Code export or external simulation of the model is not permitted due to the security settings in the given type.

CodeExport.SymanaError

Show more ...### Errors during model analysis.

Errors occurred during the analysis of the model.

CodeGen.CreateDir

Show more ...### Could not create directory.

The specified directory could not be created.

CodeGen.ElementNotSupported

Show more ...### Unsupported model.

CodeGen.ExportError

Show more ...### Code export error.

CodeGen.ExternalFunc

Show more ...### External function in exported code.

CodeGen.FileException

Show more ...

CodeGen.GeneralError

Show more ...

CodeGen.GetValueError

Show more ...

Codegen.InitialBlockLimitExceeded

Show more...### Initial block size limit exceeded.

The number of variables assigned in the block with the state of the initial system exceeds the configured number. Therefore, no symbolic Jacobian is generated for this block, but it is determined numerically instead. If you want to avoid this, increase the number in "Properties / Simulation Control / Symbolic Analysis / Numerical calculation of initial Jacobian ..." to be greater than the current one or turn off this option entirely.

CodeGen.InputNotUsed

Show more ...### Input not used.

CodeGen.InstructionNotSupported

Show more ...

CodeGen.InvalidPrjParam

Show more ...

CodeGen.InvalidProjectId

Show more ...

CodeGen.InvalidSettingsKey

Show more ...

CodeGen.InvalidSettingsKeyNoValue

Show more ...

CodeGen.InvalidSettingsKeyValue

Show more ...

CodeGen.LabViewSizeWarning

Show more ...

CodeGen.LoadDll

Show more...### Failed to load generated DLL.

CodeGen.MoveDll

Show more ...### Generated DLL could not be moved.

CodeGen.NoDir

Show more ...

CodeGen.SymanaError

Show more ...

CodeGen.SystemError

Show more ...

CodeGen.ToManyArgsForFuncCall

Show more ...

Crypto.ReadException

Show more ...### File could not be loaded.

CurveDlg.ExcelExport2DMap

Show more ...### Text file could not be saved.

CurveDlg.ExcelExport3DMap

Show more ...### Excel workbook could not be saved.

CurveDlg.ExcelImport2DMap

Show more ...### Text file could not be loaded.

CurveDlg.ExcelImport2DMapSheets

Show more ...### Only one worksheet supported.

CurveDlg.ExcelImport3DMap

Show more ...### Excel workbook could not be loaded.

CurveDlg.ExcelWorkbookException

Show more ...### Cannot access Excel worksheet.

DB.TabModified

Show more ...### Table contains modifications.

EigenSys.IllConditionedEigensystem

Show more ...### Numerically ill-conditioned eigenvalues and eigenvectors.

The reciprocal condition of some of the eigenvalues and some of the eigenvectors is very small. The smaller the reciprocal condition number is the more the corresponding numerically computed eigenvalues and eigenvectors can be disturbed.

That happens if eigenvalues have eigenvectors that are nearly linearly dependent and if eigenvalues are very close to each other, respectively.

Examples are described in the manual.

EigenSys.IllConditionedEigenvalues

Show more ...### Numerically ill-conditioned eigenvalues.

The reciprocal condition of some of the eigenvalues is very small. The smaller the reciprocal condition number is the more the corresponding numerically computed eigenvectors can be disturbed.

That happens if eigenvalues have eigenvectors that are nearly linearly dependent.

Examples are described in the manual.

EigenSys.IllConditionedEigenvaluesInfo

Show more ...### Informations about numerically ill-conditioned eigenvalues.

EigenSys.IllConditionedEigenvectors

Show more ...### Ill-conditioned eigenvectors.

The reciprocal condition values of some of the eigenvectors are very small. The smaller the reciprocal condition number is the more the corresponding numerically computed eigenvectors can be disturbed.

That happens if eigenvalues are very close to each other.

Ill-conditioned eigenvectors can also belong to an eigenvalue that has a higher multiplicity in exact arithmetics but is split up into multiple eigenvalues that are very close to each other in the numerical calculation.

Ill-conditioned eigenvectors result for an example if a model is composed of decoupled submodels with very similar dynamical behavior.

Examples are described in the manual.

EigenSys.IllConditionedEigenvectorsInfo

Show more ...### Informations about numerically ill-conditioned eigenvectors.

Eval.InvalidBinOp

Show more ...### Invalid call of operator %1.

A division or potentiation could not be executed, because the arguments lie outside of the definition range, e.g. 0/0 or (-1.5)^0.5. To identify the error, use the tracing option "Calculation of equations" during the simulation. The last equation contains the incorrect calculation.

Eval.InvalidFunctionCall1

Show more ...### Invalid function call.

A one-digit mathematical function could not be calculated, because it was called with arguments outside of its domain, e.g. sqrt(-0.1), log(-1), asin(2) etc. To identify the error, use the tracing option "Calculation of equations" during the simulation. The last equation contains the incorrect calculation.

Eval.InvalidFunctionCall2

Show more ...### Invalid function call.

A two-digit mathematical function could not be calculated, because it was called with arguments outside of its domain, e.g. atan(2,0), pow(-1,0.5), log(10,0) etc. To identify the error, use the tracing option "Calculation of equations" during the simulation. The last equation contains the incorrect calculation.

Eval.QueryUnknownDimSize

Show more ...### Unknown dimension size.

An attempt was made to determine the dimension of a variable with the `size`

operator before the simulation, although it is not yet known at this time. This message can be ignored as long as it does not occur during the simulation, as it otherwise indicates an error in SimulationX.

FTgen.BasicEvent

Show more ...### Error %1 not defined.

The logical expression for the failure propagation contains a basic/normal event which is not defined.

FTgen.BinaryModelicaConnection

Show more ...### Binary Modelica connections not supported (connector %1).

Binary Modelica connections are not supported yet in the fault tree synthesis for *xfta*.

FTgen.CycleInFailurePropagation

Show more ...### Cycle in failure propagation: %1.

The failure propagation contains a cycle. A fault tree can only be created if the failure propagation is acyclic. The cycle is shown for diagnostic purposes.

FTgen.CyclicFailureGraph

Show more ...### Failure propagation contains cycles.

The failure propagation contains a cycle. A fault tree can only be created if the failure propagation is acyclic.

FTgen.DirectedBinaryITIConnectionExplicit

Show more ...### Directed binary SimulationX connections not supported (connection %1).

Directed binary SimulationX connections with explicit failure propagation are not supported yet in the fault tree synthesis for *xfta*.

FTgen.FTSyntaxError

Show more ...### Syntax error.

The logical expression for the failure propagation contains a syntax error.

FTgen.FTSyntaxError2

Show more ...### Syntax error.

The logical expression for the failure propagation contains a syntax error.

FTgen.GateNoChildren

Show more ...### No children found for %1.

A node in the graph for failure propagation has no children. It was set to the constant value *false* to allow for the creation of a fault tree if possible.

FTgen.MoreThanOneChild

Show more ...### %1 %2 has more than one child node.

A node in the failure graph which may only have one child has more than one. This is not permitted.

FTgen.NaryITIConnection

Show more ...### N-ary SimulationX connections not supported (connection %1).

N-ary SimulationX connections are not supported yet in the fault tree synthesis for *xfta*.

FTgen.NaryModelicaConnection

Show more ...### N-ary Modelica connections not supported (connector %1).

N-ary Modelica connections are not supported yet in the fault tree synthesis for *xfta*.

FTgen.NoPropagator

Show more ...### Selection no longer supported.

The model was created with a very early version of the *SafetyDesigner* and contains a setting which is no longer supported.

FTgen.NotAPort

Show more ...### Object %1 not a port.

The logical expression for the failure propagation references an object like a port/pin/connector, but the object is none.

FTgen.ODClass

Show more ...### Output deviation class %1 not defined.

An output deviation class must be defined before it can be used in the logical expression for the failure propagation.

FTgen.ODClassNotExists

Show more ...### Output deviation class %1 not defined.

The model uses an output deviation class for fault tree analyses which was not defined. The output deviation class was created automatically.

FTgen.PortNotExist

Show more ...### Port does not exist.

The logical expression for the failure propagation references a port/pin/connector which does not exist (anymore).

FTgen.QuoteInDescription

Show more ...### Descriptioncontains double quotes.

The description must not contain double quotes, as they are used as delimiters in Modelica text.

FTgen.UndirectedBinaryITIConnectionExplicit

Show more ...### Undirected binary SimulationX connections not supported (connection %1).

Undirected binary SimulationX connections with explicit failure propagation are not supported yet in the fault tree synthesis for *xfta*.

FTgen.XftaOutputDirectory

Show more ...### Input files for XFTA solver generated in %1.

Shows the directory in which the input files for the XFTA solver are generated.

Gui.Check.BadDimension

Show more ...### Dimension mismatch.

Gui.Check.OutOfRangeMax

Show more ...### Exceeding the maximum value. The value must be smaller than or equal to the maximum.

The value of the entered expression is greater than the defined maximum. Please reduce the value (at least down to the maximum), correct the expression or modify the `max`

attribute.

Gui.Check.OutOfRangeMaxArray

Show more ...### At least one of the array components in %1 returns a value greater than the defined maximum of "%2".

At least one of the components in the entered array, returns a value greater than the defined maximum. Please correct the array component or change the `max`

attribute.

Gui.Check.OutOfRangeMaxNotReached

Show more ...### Exceeding the maximum value. The value must be smaller than the maximum.

The value of the entered expression is greater than or equal to the defined maximum. Please reduce the value to below the maximum, correct the expression or modify the `max`

or `maxNotReached`

attribute.

Gui.Check.OutOfRangeMaxNotReachedArray

Show more ...### At least one array component exceeds the maximum value. The value must be smaller than the maximum.

The value of the entered expression of at least one array component is greater than or equal to the defined maximum. Please reduce the value to below the maximum, correct the expression or modify the `max`

or `maxNotReached`

attribute.

Gui.Check.OutOfRangeMin

Show more ...### Falling below the minimum value. The value must be greater than or equal to the minimum.

The value of the entered expression falls below the defined minimum. Please increase the value (at least up to the minimum), correct the expression or modify the `min`

attribute.

Gui.Check.OutOfRangeMinArray

Show more ...### At least one of the array components in %1 returns a value smaller than the defined minimum of "%2".

At least one of the components in the entered array returns a value, smaller than the defined minimum. Please correct the array component or change the `min`

attribute.

Gui.Check.OutOfRangeMinNotReached

Show more ...### Falling below the minimum value. The value must be greater than the minimum.

The value of the entered expression falls below or is equal to the defined minimum. Please increase the value to above the minimum, correct the expression, or modify the `min`

or `minNotReached`

attribute.

Gui.Check.OutOfRangeMinNotReachedArray

Show more ...### At least one array component falls below the minimum value. The value must be greater than the minimum.

The value of the entered expression of at least one array component falls below or is equal to the defined minimum. Please increase the value to above the minimum, correct the expression, or modify the `min`

or `minNotReached`

attribute.

Gui.Compound.IntersectedTransition

Show more ...### The compound could not be created from the current selection.

Hydraulics.AccuPSat

Show more ...### Absolute gas pressure above saturation pressure of %1 Pa.

Hydraulics.AccuTMin

Show more ...### Gas temperature below minimum of %1 K.

Hydraulics.aURefMinMax

Show more ...### Incorrect value for alphaURef.

Hydraulics.flowAflowBnotEqual

Show more ...### Volume flow on both sides must be equal.

Hydraulics.NotConnected

Show more ...### Hydraulic port %1 not connected.

Hydraulics.NotConnectedPneu

Show more ...### Pneumatic port %1 not connected.

Hydraulics.NotConverged

Show more ...### Solution not converging.

Hydraulics.pAAbsInit

Show more ...### Inconsistent settings. Absolute pressure of %1 Pa necessary.

For a steady-state condition, an absolute pressure of %1 Pa would be necessary at portA. Hence your settings are inconsistent. Please increase the value for the initial pressure at portB or decrease the value for the volume flow at portA.

Hydraulics.PipeDis_pBAbsInit

Show more ...### Inconsistent settings. Absolute pressure of %1 Pa necessary.

For a steady-state condition, an absolute pressure of %1 Pa would be necessary at portB. Hence your settings are inconsistent. Please increase the value for the initial pressure at portA or decrease the value for the volume flow at portB.

Hydraulics.pSrc_pMax

Show more ...### Pressure above limit of %1 Pa.

Hydraulics.pSrc_pMin

Show more ...### Pressure below limit of %1 Pa.

Hydraulics.pSrc_Tmax

Show more ...### Temperature above limit of %1 K.

Hydraulics.pSrc_Tmin

Show more ...### Temperature below limit %1 K.

Hydraulics.Tank_pMax

Show more ...### Pressure above limit of %1 Pa.

Hydraulics.Tank_pMin

Show more ...### Pressure below limit of %1 Pa.

Hydraulics.Tmax

Show more ...### Temperature exceeds maximum of %1 °C.

Hydraulics.Tmin

Show more ...### Temperature below minimum of %1 °C.

Hydraulics.Vtank

Show more ...### Tank %1 is empty.

IndexReduction.NotDifferentiableEqns

Show more ...### Cannot differentiate equations.

Some equations cannot be differentiated during index reduction.

IndexReduction.NotDifferentiableEqnsStateSelect

Show more ...### Check manual state selection.

Some equations cannot be differentiated for symbolic index reduction. The following variables were modified with `StateSelect.always`

: %1. The modification may require these equations to be differentiated. Please check if the modification is necessary.

InitialSystem.FixedFromInitialValue

Show more ...### Variable %1 fixed by initial values.

The fixation of a variable (`fixed=true`

) was obtained from an initialization parameter.

InitialSystem.IterationVar

Show more ...### System of equations for initial values underdetermined.

The initialie equation system has no unique solution. If necessary, add a fixed initial value, initial equation or initial assignment.

InitialSystem.MissingInitialAssignment

Show more ...### Missing assignment in initial system.

An assigning equation for a variable in the initial system could not be found. The default value is used as the start value. Use `fixed=true`

or add an assignment in an initial section.

InitialSystem.ModifiedInitialParam

Show more ...### Assignment from declaration or modification used in initial section.

An initial parameter has an assignment from the declaration or a modification and is used in the initial section. Please check that there is no assignment to the parameter in the initial section.

InitialSystem.MultipleAlgorithmOutputVar

Show more ...### Variable is output of multiple algorithm sections.

There are variables which are assigned by mulitple algorithms causing the system of equations to be overdetermined. Correct this so that a variable has only one assignment or is only assigned within an algorithm.

InitialSystem.StartAttrNotFound

Show more ...### Start attribute not found. Using default value.

No start value could be determined for a variable, the default value is used. Please define the start attribute of this variable or the variables it depends on.

InitialSystem.StartDepentInitialState

Show more ...### Start attribute of an initial state depends on initial states.

The `start`

attribute of an initial state depends itself on initial states. This can lead to inconsistent initial values. Introduce an additional initial equation for the relationship between the variable and the state.

InitialSystem.TooManyInitialEqns.Initial

Show more ...### Too many initial equations

The initial system is overdetermined. Remove initial equations.

InitialSystem.TooManyInitialEqns.Start

Show more ...### System of equations for initial values overdetermined.

The system of equations for the computation of initial values is overdetermined. Remove initial value fixations.

InitialSystem.TooManyInitialEqns.StartInitial

Show more ...### System of equations for initial values overdetermined.

The system of equations for the computation of initial values is overdetermined. Remove some of the initial value fixations, as they are in conflict with the initial equations.

InitialSystem.WhenStatement

Show more ...### Initial section contains When statement.

`when`

statements are not permitted in an initial section. Move it to a normal equation section.

IOAna.NumSingMatPencil

Show more...### Singular system matrix during the computation of the frequency response function.

The matrix of the linear system of equations for the calculation of the frequency response is singular at all frequency grid points.

Models where this may occur:

- Models with structural changes like:
- mechanical models with rigid end stops
- electrical models with ideal diodes and ideal switches

- extrem parametrization like:
- modeling of factual ideal connections through elements with extreme parameters
- models of extreme application areas

The computation is repeated with the solver for singular linear systems.This may lead to an unfavorable representation of poles directly on the imaginary axis as occurs in models with undamped oscillation modes.

LinSysAna.SynchronousNotSupported

Show more ...### Modelica Sychronous Extension not yet supported.

Modelica.Assert

Show more ...### Assert failed.

The condition of a `assert(b,"...");`

instruction became false during the simulation and the simulation was terminated. The output message contains the description of the error. Most of the times, the model is outside of its range of validity.

Modelica.AssertWarning

Show more ...### Assert warning.

The condition of a `assert(b,"...",AssertionLevel.warning);`

instruction became false during the simulation. This is only an indication that the model has left its range of validity, though the simulation continued. The output message contains information about the parts of the model being affected.

Modelica.AssertWarningRevoked

Show more ...### Assert warning revoked.

The condition of `assert(b,"...",AssertionLevel.warning);`

has changed from *false* to *true*, i.e. the simulation of the model runs in its range of validity again.

Modelica.AssignedFlowVar

Show more ...### Assignment to a disconnected flow variable.

A flow variable of an disconnected port gets an automatic zero assignment even though another assignment already exists. This message can be interpreted as an indication for a later singularity message of the model (e.g. too many equations).

Modelica.AssignmentFromNonDiscreteToDiscrete

Show more ...### Discrete-time variable assigned from continuous-time statement.

A discrete variable is assigned within a continuous equation. Assignments to discrete variables are only allowed with discrete expressions (with discrete variables, constants and discrete operators, such as `pre()`

, `edge()...`

) or within `when`

statements. All statements are discrete there, since they are only executed at event times.

Modelica.AssignmentWithoutFunctionOutput

Show more ...### Illegal assignment.

In an equation, an attempt is made to use the value of a function even though it does not contain a variable declared as output.

Modelica.BadValue

Show more ...### Invalid value.

A value could not be assigned to a modification when a file was loaded, because its text could not be converted to the corresponding data type. The value is not included in the model and is lost when the model is saved.

Modelica.BadValueWarn

Show more ...### Invalid value.

A value of an annotation could not be assigned to a modification when a file was loaded, because its text could not be converted to the corresponding data type. The value is not included in the model and is lost when the model is saved.

Modelica.CanNotInstantiate

Show more ...Modelica.CircularDependencForDimension

Show more ...### Circular dependency during determination of dimensions.

Determining the dimension of a parameter or variable fails due to a cyclic dependency of the dimension expression from the dimension of the variable itself. Rephrase the expression (using other parameters).

Modelica.ClockArgumentNonNegative

Show more ...### Invalid argument of clock constructor.

Modelica.ClockedInEventClockConstructor

Show more ...### Clocked condition for event-triggered clock.

The condition of an event-triggered clock constructor must be a continuous-time expression. Please check the corresponding condition!

Modelica.ClockedOpUsedInContinuous

Show more ...### Clocked expression used in continuous-time environment.

An operator that requires a clock is used in a continuous-time environment.

Modelica.ClockedUsedInContinuous

Show more ...### Clocked expression used in continuous-time environment.

Modelica.CondRecordComps

Show more ...### Conditional declarations in records not implemented.

Conditional declarations of components in records are not implemented. The condition is ignored.

Modelica.ConflictingSolverMethod

Show more ...### Inconsistent SolverMethod.

A clocked partition is affected by multiple different `solverMethod`

specifications. Please make sure that information is consisten for each partition.

Modelica.ContinuousUsedInHoldOp

Show more ...A continuous-time expression is used in a statement as an argument of a `hold`

-Operators. You can remove the `hold`

-Operators.

Modelica.ContinuousUsedInSubPartition

Show more ...### Continuous-time expression used in clocked partition.

A time continuous expression is used in a clocked partition. Use the `sample`

operator to use continuous expressions within a clocked partition.

Modelica.CyclicallyLinkedSubpartitions

Show more ...### Cyclically linked sub-partitions.

Some sub-partitions are connected cyclically. Use `noClock`

to resolve the loop.

Modelica.CyclicModification

Show more ...### Cyclic reference in modification %1.

There are cyclic references to other arguments in the default values of function arguments. Resolve them.

Modelica.CyclicReferenceInParameter

Show more ...### Cyclic reference in parameter %1.

There is a cyclic self-reference in one parameter via other parameters.

Modelica.DefaultClockGenerated

Show more ...### Default clock generated.

Modelica.DimensionNeedsConstantVar

Show more ...### Dimension expression must be constant.

The dimension of variables outside of functions must be constant (determinable at compile time).

Modelica.DimMustBeKnownAtCompileTime

Show more ...### Dimension of %1 must be known at compile time.

The dimension of variables outside of functions must be constant (determinable at compile time). If the message apears for a signal input, the dimension of the connected output is unknown. The dimension can usually be defined by through the dimension of its input, for example:`input SignalBlocks.InputPin x[*];output SignalBlocks.OutputPin y[=size(x)];`

Modelica.DirectoryNameNotMatch

Show more ...### Directory name not matching package name.

Modelica.DiscreteRealnoWhen

Show more ...### Discrete-time variable without assignment in When statement.

*Real* variables declared as *discrete* must be assigned in `when`

statements.

Modelica.DivisionByArray

Show more ...### Division by array.

An attempt was made to divide by an array (vector, matrix). That is not permitted. Use element-wise division "./" instead.

Modelica.EachGenerated

Show more ...### Missing Each.

An array (vector, matrix) was modified with a scalar. The keyword `each`

is usually used to assign this value to each element of the array. If it was not specified, it is added automatically and this warning is shown to hint at the potential error.

Modelica.ErrorInPackageOrderFile

Show more ...### Inconsistent package.order file %1.%2

The message indicates that there are entries for classes missing in the *package.order* file if the package is stored as a directory structure.

Modelica.FileNameNotMatch

Show more ...### Filename not matching package name.

If models are saved in a **.mo* file, the file name must match the class name. Rename the file.

Modelica.Function.CondUndefinedOutput

Show more ...### Function not fully defining value(s) for output variable(s).

Return variables of functions need a value assigned to them within the function. In the current function, however, these values are assigned only under certain conditions, i.e. there are execution paths in which variables are not assigned. Change the function so that these variables are always assigned, e.g. by assigning a default value to them at the beginning of the function.

Modelica.Function.CondUndefinedOutputOnReturn

Show more ...### Function not fully defining value(s) for output variable(s) with Return statement.

Return variables of functions need a value assigned to them within the function. In the current function, however, these values are assigned only under certain conditions, i.e. there are execution paths in which variables are not assigned. Change the function so that these variables are always assigned, e.g. by assigning a default value to them at the beginning of the function.

Modelica.Function.CondUninitialisedVarUsed

Show more ...### Not fully initialized variable in function.

In the algorithm of a function, a variable is used that cannot be initialized under certain conditions, i.e. there are execution paths in which variables are not assigned. Change the function so that these variables are assigned, e.g. by assigning a value to them right at the beginning of the function.

Modelica.Function.UndefinedOutput

Show more ...### Function not defining value for output variable(s).

Return variables of functions need a value assigned to them within the function. In the current function, one or more have none. Change the function so that these variables are assigned, e.g. by assigning a default value to them at the beginning of the function.

Modelica.Function.UndefinedOutputOnReturn

Show more ...### Function not defining value for output variable(s) with Return statement.

Return variables of functions need a value assignment within the function. In the current function, one or more have none. Change the function so that these variables are assigned, e.g. by assigning a default value to them at the beginning of the function.

Modelica.Function.UninitialisedVarUsed

Show more ...### Uninitialized variable in function.

The algorithm of a function uses a variable that has not been initialized. Change the function so that these variables are assigned, e.g. by assigning a value to them right at the beginning of the function.

Modelica.FunctionInputAssigned

Show more ...### Input variable assigned in function.

An input parameter is assigned in the function, which is not permitted. Use a local variable to which the value of the input.is assigned. You can then assign these repeatedly.

Modelica.IdentifiersDoNotMatch

Show more ...### Identifiers %1 (line %2) and %3 (line %4) differ.

In a definition, the name behind the keyword at the beginning must match the name behind the keyword at the end. Please correct the name at the end.

Modelica.IdentifiersDoNotMatchWithFileName

Show more ...### Identifiers different.

In a definition of a model, block, function, record, ... the name behind the keyword at the beginning must match the name behind the keyword at the end. Please correct the name at the end.

Modelica.IncompatibleBaseClass

Show more ...### Modelica class of %1 and base class %2 incompatible.

The Modella class must match the base class. Alternatively, you can create a component of the base class and use it in the equations.

Modelica.IncorrectInverseFunctionArgumentList

Show more ...### Argument lists mismatch.

The function and its inverse function must have the same number of input arguments. Please make the necessary adjustments. See also Modelica Specification, chapter 12.8 "Declaring Inverses of Functions".

Modelica.IncorrectInverseFunctionArguments

Show more ...### Arguments not matching.

The arguments in the inverse annotation must match those of the original function, except that an input argument now becomes an output argument and vice versa. The order may change. The assignment of the paremeters of the original and inverse functions is described in the inverse annotation. All arguments must be referenced there by name. See Modelica Specification, chapter 12.8 "Declaring Inverses of Functions".

Modelica.IncorrectInverseFunctionDefinition

Show more ...### Arguments not matching.

The arguments in the inverse annotation must match those of the original function, except that an input argument now becomes an output argument and vice versa. The order may change. The assignment of the paremeters of the original and inverse functions is described in the inverse annotation. All arguments must be referenced there by name. See Modelica Specification, chapter 12.8 "Declaring Inverses of Functions".

Modelica.IncorrectInverseFunctionOutput

Show more ...### Too many outputs.

Functions with inverse annotation and the inverse itself may have only one output argument. Please modify the function definitions accordingly. See Modelica Specification, chapter 12.8 "Declaring Inverses of Functions".

Modelica.InfiniteInheritance

Show more ...### Infinite inheritance.

The class is derived from itself, directly or indirectly. Please remove the unnecessary `extends`

statement.

Modelica.InstantiationInterruptedByUser

Show more ...### Instantiation aborted.

The instantiation was aborted by you.

Modelica.InvalidClockPrefix

Show more ...### Illegal Clock prefix.

A `clock`

variable was declared with an invalid prefix. Only `input`

, `output`

, `inner`

and `outer`

are permitted.

Modelica.InvalidConnectorBlock

Show more ...### Missing prefix in Block connector.

Modelica.InvalidConnectorPrefix

Show more ...### Illegal prefix in connector.

A connector contains an element with an invalid prefix (`protected`

, `inner`

, `outer`

).

Modelica.InvalidConnectorStatement

Show more ...### Illegal statement in connector.

A connector must not have an equation or algorithm section.

Modelica.InvalidEnumerationLiteral

Show more ...### Illegal enumeration.

An invalid name for an enumeration alternative was used. Sinceattributes and alternatives of an enumeration lie in the same namespace, their names cannot be used for alternatives.

Modelica.InvalidOperatorElement

Show more ...### Illegal element in operator.

An operator class may only contain functions, but not an equation or algorithm section and no variables, parameters, or constants.

Modelica.InvalidRecordOperatorStatement

Show more ...### Illegal statement in record operator.

A record operator class must not have an equation or algorithm section.

Modelica.InvalidRecordPrefix

Show more ...### Illegal prefix in record.

In a record definition, a component has an invalid prefix.

Modelica.InvalidRecordStatement

Show more ...### Illegales statement in record.

A record class must not have an equation or algorithm section.

Modelica.ITIVersionNotFound

Show more ...### Required version %1 of type %2 not found.

The requested version of a class was not found. The current version is used instead.

Modelica.LeftSideInWhen

Show more ...Equations in `when`

blocks may only refer to variables on the left side. More complex expressions with operators, functions, or numbers are not permitted.

Modelica.MissingDimAssign

Show more ...### Unknown variable size.

Variables with ":" in the dimension specification require a modification from which the dimension sizes can be determined.

Modelica.MultipleBaseClocks

Show more ...### Multiple clock definitions in base clock partition.

A clocked partition can have only one clock.

Modelica.MultipleClocksForStmt

Show more ...### Multiple clocks in statements.

A statement references variables that have different clocks.

Modelica.MultipleInverseFunctionDefinitions

Show more ...### Multiple inverse functions found.

For the function, there are several inverse functions specified for the same argument. Please correct the inverse annotation so that only one inverse function is specified for each input argument of the function.

Modelica.MultipleWhenAssignedVar

Show more ...### Variable cannot be assigned in multiple When statements.

A variable is assigned in multiple `when`

statements. Use `when ... elsewhen ... end when;`

to define a proper sequence.

Modelica.NegativDimAssign

Show more ...### Negative variable size.

Dimensions cannot be negative.

Modelica.NoBaseClass

Show more ...### Model %1 has no base class.

Modelica.NoConnection

Show more ...### No connection specified.

Connections of SimulationX connectors must always have a connection object. Create connections within the GUI of SimulationX.

Modelica.NonRealAlgebraicLoop

Show more ...### Variables in algebraic loop not of type Real.

There is an algebraic loop over variables that are not of type *Real*. Use the `pre(…)`

operator to break them up.

Modelica.NonScalarRelationOperand

Show more ...### Relational operators are only defined for scalar operands.

Comparison operators are only defined for scalar operands.

Modelica.NoOuterMod

Show more ...### Modifying outer elements (%1) not permitted.

Modelica.NotAPin

Show more ...### Not a connector.

The object referenced in a `connect`

statement is not a connector.

Modelica.NotAType

Show more ...### Not a type.

Modelica.NotEvaluableExpression

Show more ...### Expression %1 must be evaluable.

The value of subscripts in `connect`

statements must be determinable at compile time.

Modelica.NotReplaceable

Show more ...### Not marked as replaceable.

Modelica.NoTypeLicense

Show more ...### No license.

Modelica.NoTypename

Show more ...### Type name missing.

The `typename`

element is missing in a compound annotation.

Modelica.ObsoleteTypeUsed

Show more ...The type of a component is marked as obsolete. Avoid using such types in new models as they are no longer maintained. There is usually a newer type with improved functionality.

Modelica.OverwriteFinalMod

Show more ...### A component declared with "final" has been modified.

An element declared with `final`

, e.g. `final parameter Real x=5;`

, must not be changed (modified) or redeclared in instances (simulation models, *Compounds*) or derived types. Solve the problem by reverting the corresponding modification or redeclaration.

Modelica.PartialFunctionCalled

Show more...Modelica.RecCompCreation

Show more ...### It is not possible to create a component of type %1 in the same type, a base type or a component of it (%2).

An attempt was made to create a component of a type in itself, in a base class or in a component of it. This is not possible.

Modelica.RedeclareNonReplaceable

Show more ...### Redeclaration of non-replaceable element.

An element marked as non-replaceable is declared. Remove the redeclaration or mark the element as replaceable.

Modelica.SameConnection

Show more ...### Multiple connections at the same connector.

Only one connection object can be connected to an SimulationX connection at a time. Remove the `connect`

statement and connect the connectors through the SimulationX GUI. The various connection objects are then combined into one.

Modelica.SetInitialParameter

Show more ...### Changing parameter to fixed=false.

The variability of the assigned parameter is lower than the variability of the assignment. The parameter is then calculated by the initial system, but remains constant for the transient simulation. To avoid this warning, set the `fixed`

attribute of the parameter to *false*.

Modelica.SingularLinearBlockWithDiffEqns

Show more ...### Singular linear block with equations from differentation.

A linear algebraic loop is singular and cannot be treated symbolically, because it contains equations that were created by index reduction.

Modelica.StackOverflowDuringInstantiation

Show more ...### Maximum recursion depth reached during instantiation of %1.

The maximum stack depth was exceeded during instantiation. This indicates a recursive definition of a class and an error in the instantiation. There should be another, more concrete error message.

Modelica.StateMachine.ContainInvalid

Show more ...### Invalid content in state machine.

In the equations of a state machine state, continuous equations or algorithms are not permitted.

Modelica.StateMachine.InvalidUsage

Show more ...### Invalid call of 1%.

Calling the operators `ticksInState`

and `timeInState`

is only allowed in conditions of transitions of state machines that do not have a parent state machine.

Modelica.StateMachine.MissingInitialState

Show more ...### Initial state missing in state machine.

A state machine must have an initial state. This is marked with the `initialState(state)`

operator.

Modelica.StateMachine.MultipleInitialState

Show more ...### Multiple states market as initial state.

In a state machine, there can only be one start state. Remove redundant markings.

Modelica.StateMachine.NotAState

Show more ...### Instance is not a state machine state!

The argument of `activeState()`

is not a state in a state machine.

Modelica.StateMachine.Priority

Show more ...### Identical priority value used twice.

All outbound state transitions must have their own priority. Priority values must not be reused.

Modelica.States.InvalidCondition

Show more ...### Invalid condition.

A transition requires a condition.

Modelica.States.InvalidPriority

Show more ...### Invalid priority.

All outbound state transitions must have their own priority. Priority values must not be reused.

Modelica.SubClockArgumentNonNegative

Show more ...### Invalid argument of sub-clock operator.

The second argument of an operator must not be negative.

Modelica.Synchronous.UnsupportedSolver

Show more ...### Unsupported Code Export Target.

*Synchronous Language Elements* are not supported for this Code Export target.

Modelica.SynchronousArgumentComponent

Show more ...### Invalid argument of Synchronous function.

The first argument of the clock constructor must be a variable (clocked component expression) or constant (parameter expression).

Modelica.SynchronousArgumentParameter

Show more ...### Invalid argument of Synchronous function.

The third argument of the `shiftsample`

or `backsample`

operator must be constant (parameter expression).

Modelica.SyntaxError

Show more ...### Syntax error.

Modelica.TypeInconsistentAssignment

Show more ...### Inconsistent types assigned.

In an assignment, the right and left sides must have matching data types.

Modelica.TypeMismatchInnerOuter

Show more ...### Inner and outer components must have identical types.

For variables declared with `inner`

and `outer`

, the type of the `outer`

variable must match the type of the corresponding `inner`

variable.

Modelica.TypeOrComponentNotCreated

Show more ...### Instantiation failed for type %1.

During instantiation, a component or type could not be instantiated due to a missing type or base class and was removed automatically.

Modelica.UnknownBaseClass

Show more ...### Unknown base class.

A base class of a type could not be found. Make sure it exists. Try changing the search path (Menu File -> Options -> Directories -> Modelica search path (MODELICAPATH)) for instance.

Modelica.UnknownInverseFunctionDefinition

Show more ...### Definition for inverse function not found.

No definition was found for the function in the inverse annotation.

Modelica.UnknownNameRef

Show more ...### Unknown name referenced.

An unknown name is used in a reference.

Modelica.UnknownNameRefWarn

Show more ...### Unknown name referenced.

An unknown name is used in a reference.

Modelica.UnknownTypename

Show more ...### Unknown type.

The type of a component cannot be found.

Modelica.UnsupportedSolverMethod

Show more ...### Solver method not supported.

The selected solver method is not supported, Use *External* instead. For supported solver methods, see ModelicaServices.Types.SolverMethod.

Modelica.UnsupportedSolverMethod_CompiledDAE

Show more ...### Solver method not supported.

The selected solver method is currently not supported for BDF method (compiled C-code), Use *External* instead.

Modelica.ValueNotSet

Show more ...### Value cannot be set.

The value of an annotation cannot be set. Some annotatons do not yet support expressions, and only numeric constants (numbers and arrays of numbers) can be specified.

Modelica.VariabilityMismatched

Show more ...### Invalid variability in definition

The variability of the assigned variable is lower than the variability of the assignment.

Modelica.WhenConditionDependsFromLoop

Show more ...### Dependency error.

The condition of the `when`

statement depends on a variable in an algebraic loop. Break the loop by using `pre`

.

Modelica.WhenInAlgebraicLoop

Show more ...### When statement in algebraic loop.

When statements are contained in an algebraic loop. These are executed several times due to the solution algorithm.

Modelica.WithinError

Show more ...### Incorrect Within statement.

The environment in the `within`

statement does not match the actual environment of a package.

Names.BadIdent

Show more ...### String %1 not a valid identifier.

A string is not a valid identifier. Identifiers consist of names with subscripts in [] that are connected with dots.

Names.BadName

Show more ...### String %1 not a valid name.

A string is not a valid name. A name begins with a letter (*A-Z* or *a-z*) and can include letters and underscores.

Names.ComponentNameAlreadyExists

Show more ...### Component name %1 already exists.

A component with the name already exists. Only the first component with this name will be kept.

Names.ConstrainingTypeNotFound

Show more ...### Constraining type not found.

The constraining type was not found.

Names.FileCouldNotBeLoaded

Show more ...### File %1 could not be loaded.

A file exists, but could not be opened.

Names.GeneralParserError

Show more ...### Cannot open file %1.

A general error occurred during the attempt to read or unpack a model file. Please report the error with the corresponding model to the Helpdesk at Helpdesk.

Names.ImportAlreadyExist

Show more ...### Import definition %1 already exist.

An import definition with this name already exists.

Names.ImportAmbiguous

Show more ...### Import statements are ambiguous.

The `import`

statements are not unique, i.e. several imports are possible for one name.

Names.ImportNotFound

Show more ...### Import target cannot be found.

The target of the import definition cannot be found.

Names.ImportNotPackage

Show more ...### Wrong import target.

The import definition does not refer to a package or package element.

Names.InvalidModelicaPath

Show more ...### Invalid MODELICAPATH.

A *MODELICAPATH* directory must not contain a package.mo file.

Names.NameAlreadyExist

Show more ...### Name %1 already exists.

An element with this name already exists in the current environment.

Names.NameAlreadyExistsAtTopLevel

Show more ...### Library or model %1 already exists.

A library or model with the name already exists. Unload the model or library from the library tree and try again.

Names.NameAlreadyInEnv

Show more ...### Cannot create object %1.

An element with this name already exists in the current environment.

Names.NoLibraryLicense

Show more ...### No license for library %1.

There is no valid license available for a library. Please contact our sales department via www.simulationx.com to obtain a license.

Names.NoLicense

Show more ...### No license.

There are as many instances of a type as the license allows. It is not possible to create another object of it. Please contact our sales department at www.simulationx.com to extend your license.

Names.NotATypename

Show more ...### %1 not a type identifier.

The identifier for the base class of a short class definition does not refer to a type.

Names.ReservedName

Show more ...### String %1 is reserved name.

The given name is a reserved name, i.e. a keyword in Modelica (see Modelica Specification, chapter 2.3.3.).

Names.SingleInstance

Show more ...### Type %1 can be used only once.

The type can be used only once as a component.

Names.SyntaxTreeNotCreated

Show more ...### Syntax tree error.

The syntax tree could not be created. This may be a subsequent error.

Names.TextException

Show more ...

Names.UnknownName

Show more ...### Unknown name %1.

A name cannot be resolved.

Names.VersionAlreadyExist

Show more ...### Version already exists.

A special version of a type already exists. Give the new version a different version number.

Names.VersionChanged

Show more ...### Base type version of type %1 changed.

NFAna.SynchronousNotSupported

Show more ...### Modelica Sychronous Extension not yet supported.

Obsolete.IsConstantOperator

Show more ...### Operator is obsolete.

Obsolete.VariableInStartAttribute

Show more ...### This reference is obsolete.

Referencing a variable in a `start`

or `fixed`

attribute or in a start parameter is obsolete. Please use an additional initial equation instead.

Pneumatics.NotConnected

Show more ...### Pneumatic port %1 not connected.

Pneumatics.VolumeHeatChangesWith41HeatWasGivenWithTW

Show more ...### Loaded model differs in %1.

The pneumatic element is connected to a thermal network. The wall temperature `Tw` has been used so far to describe the wall temperature by value or expression. In the elements *volume*, *pipeline* and *cylinder*, the wall temperature of the port is now used if a thermal port is connected. Please check whether you want to disconnect the thermal connection to keep the previous parameterization or whether you want to use the wall temperature of the port for the calculation.

Pneumatics.VolumeHeatChangesWith41HeatWasNotActivated

Show more ...### Loaded model differs in %1.

The pneumatic element is connected to a thermal network, but the option *Consider heat transfer* has not been used by default. In the elements *volume*, *pipeline* and *cylinder*, heat transfer is now taken into accound and the wall temperature of the port is used if a thermal port is connected. Please check whether you want to disconnect the thermal connection to keep the previous parameterization or whether you want to take heat transfer into account and use the wall temperature of the port for the calculation.

Quantity.BadDomainId

Show more ...### Domain identifier %1 invalid.

The domain name is invalid.

Quantity.BadUnitFactor

Show more ...### Bad factor expression %2 for unit %1.

The unit has a wrong factor expression.

Quantity.CantExecDBCommand

Show more ...### Cannot execute database query %1.

The database query cannot be executed.

Quantity.CantOpenDB

Show more ...### Cannot open database %1.

The quantity database cannot be opened.

Quantity.CantOpenDBTable

Show more ...### Cannot open database table %1.

A table in the quantity database cannot be opened.

Quantity.DBFileNotFound

Show more ...### Database file %1 not found.

The database file could not be found.

Quantity.DomainInitFailed

Show more ...### Initialization of domains failed.

The initialization of the domains has failed.

Quantity.DomainNotFound

Show more ...### Domain %1 not found.

A domain could not be found.

Quantity.NotADomain

Show more ...### Identifier %1 not pointing to domain.

The given identifier does not refer to a domain.

Quantity.OLEDBException

Show more ...### Error accessing database.

Error accessing database.

Quantity.QuantityInitFailed

Show more ...### Database initialization failed.

Initialization of the quantity database has failed.

Quantity.QuantityNameNotFound

Show more ...### Quantity %1 not defined.

A quantity could not be found.

Quantity.UnitNameNotFound

Show more ...### Unit %1 not defined.

A unit could not be found.

Sim.ModelChange

Show more ...### Model modifications not permitted.

Modifying the model during the simulation is not permitted.

Sim.ParamChange

Show more ...### Parameter modification not permitted.

Modifying parameters during the simulation ist not permitted.

Simplify.CircularDependency

Show more ...### Circular dependency detected.

A circular dependency was found in the simple equations, e.g. a=b, a=-b. This indicates an error in the model structure. Examine the model and remove the loop in the model.

Simplify.ConsistentOverdeterminedEquation

Show more ...### Consistent overdetermined equation removed.

There is one equation too many in the model. However, it does not contribute to the result calculation, since it could be reduced to 0=0 and will thus be removed.

Simplify.Overdetermined

Show more ...### Equation system overdetermined.

In the system of equations of simple equations, e.g. a=b, a=-b, there are too many equations. Remove them.

Simplify.StateLoop

Show more ...### Loop in hierarchy of derivatives.

There are loops in the derivatives of states, e.g. x->der(x)==y->der(y)==x->... Examine your model and remove them.

Solver.Abs_Tol

Show more ...### Absolute tolerance less than zero.

The absolute tolerance is less than zero. A tolerance must always be greater than or equal to *0*. Additional information

Solver.CalcAssert

Show more ...### Assert during the calculation

Solver.CalcExcept

Show more ...### Exception during the calculation

Solver.CE_Initial

Show more ...### Initialization aborted!

Solver.CE_TimeSteps

Show more ...### Simulation aborted!

Solver.Conv

Show more ...### Calculation step size (dtMin) too large.

The values at the beginning of a time step are very large and the relative tolerances are very small. Reduce the minimum calculation step size *dtMin* or increase the tolerances.

Solver.CvodeUnknownError

Show more ...### Unknown Error!

Solver.DampFactor

Show more ...### Error during the calculation of the damping factor for the Newton-update.

Due to extinction, the damping factor in the solver was nor selected correctly. The step was discarded.Additional information

Solver.ErrTest

Show more ...### Required accuracy not achievable

Solver.EventCycle

Show more ...### Cycle during event iteration.

Cycle found during event iteration. The simulation was aborted.Additional information

Solver.ExtSolveCvodeError

Show more ...### Error during CVODE method (external solver).

An error occurred during the calculation with CVODE (external solver).Additional information

Solver.ExtSolveCvodeFailed

Show more ...### Unknown error during CVODE method (external solver).

Solver.ExtSolveFixStepError

Show more ...### Error with fixed-step solver (external solver).

Solver.ExtSolveFixStepFailed

Show more ...### Unknown error with fixed-step solver (external solver).

Solver.ExtSolveFixStepTerminate

Show more ...### Simulation aborted.

Solver.InconsIV

Show more ...### The solver cannot calculate consistent initial values.

Solver.InconsIVDisc

Show more ...### Calculation of consistent values failed after a discontinuity.

Solver.InconsIVEnd

Show more ...### Calculation of consistent values failed at the end.

Same as with error "Calculation of consistent values failed after a discontinuity.", but in the last event iteration at the stop time tStop.

Solver.InitializeNoError

Show more ...### Event-Iteration at simulation start finished successfully.

Solver.IVStopped

Show more ...### Event iteration stopped

Solver.LinSystemNotSolvable

Show more ...### Linear system not solvable. Order and step size not reducible.

Solver.MemoryAllocation

Show more ...### Insufficient memory.

When external data structures are initialized for the CompiledBDF solver, no more memory could be allocated. Either the model is too large for the available memory or there is an error in SimulationX. Please report the error with the corresponding model to the Helpdesk at Helpdesk.

Solver.No_States_Equ

Show more ...### Number of states and equations not matching.

The number of states does not correspond to the number of residuals. This indicates an error in SimulationX. Please report the error with the corresponding model to the Helpdesk at https://helpdesk.simulationx.com/helpdesk

Additional information

Solver.NoConv

Show more ...### Solution failed to converge.

Solver.NoError

Show more ...### Simulation finished successfully.

Solver.PredStateBound

Show more ...### Minimum/Maximum of states exceeded.

Solver.PureDiscreteLoop

Show more ...### Discrete loop.

In the model, there is an algebraic loop consisting only of discrete variables and equations. Use the `pre`

operator to break the loop.

Solver.Rel_Tol

Show more ...### Relative tolerance less than zero.

The relative tolerance is less than zero. A tolerance must always be greater than or equal to *0*. Additional information

Solver.SingularScalarSystem

Show more ...### Singular inconsistent scalar system for %1.

In the model, there is a scalar implicit equation of the form *A*x=b* where *x* is the subject. However, *A==0*, so a solution is not possible.

Solver.SingularSystem

Show more ...### Equation system singular.

The system of equations is singular. Variables that are to be calculated from the system are not included.

Solver.Statistics

Show more ...### Solver statistics

Solver.SteadyStateFailed

Show more ...### Steady State (Equilibrium) not found.

Solver.SteadyStateNoError

Show more ...### Equilibrium calculation successfully (Steady State found).

Solver.SteadyStateStopped

Show more ...### Calculation of equilibrium stopped

Solver.Stopped

Show more ...### Calculation stopped

Solver.Tol_dt_min

Show more ...### Solver could not meet required accuracy.

Same as with "Required accuracy not achievable", but only for the MEBDF method.

Solver.UnmatchedDiscreteVariable

Show more ...### Unmatched discrete variable

There are too many discrete variables in the model. Not all of them can be calculated by an equation.

StatAna.DynamicStateSelection

Show more ...### Dynamic state selection required.

The model requires a dynamic state selection. It is recommended you disable the index reduction for this model during the steady-state simulation. Activate the option *No index reduction* on the page *Symbolic Analysis* of the settings dialog box for steady-state simulations,

StatAna.NewtonStepData

Show more ...### Quality measures for the Newton step.

Statana.OnlyScalarOutput

Show more ...### Only scalar outputs supported.

A variable marked as simulation output is not scalar. In steady-state simulations, only scalar variables are supported as output. It will be ignored.

StatAna.PeriodVarNoState

Show more ...### Period variable %1 not a state of the system.

The selected period variable is not a state of the system. Please select a variable with a derivative.

StatAna.RefVarNoState

Show more ...### Reference quantity %1 not a state of the system.

The selected reference variable is not a state of the system. Please select a variable with a derivative.

Statana.SynchronousNotSupported

Show more ...### Modelica Sychronous Extension not yet supported.

StateMachine.EvaluateImmediate

Show more ...### Parameter expression must be evaluable.

The expression of the parameter *immediate* a transition must be evaluable at compile time, i.e. it must be constant.

StateMachine.MissingOutputOnOuter

Show more ...### Missing output declaration on outer component.

Variables in state machines that are assigned in states and used in other states must be declared in the states as `outer output`

and in the state machine itself as `inner`

.

StateMachine.UnassignedOuterOutput

Show more ...### Outer output without assignment in state.

Variables in state machines that are not assigned in a state must not be declared as `outer output`

, but only as `outer`

.

StateSelection.AlgebraicReinit

Show more ...### Algebraic variable used in Reinit.

A variable *v* is used in `reinit`

as the first argument, but is not a state of the continuous system, i.e. there is no derivative *der(v)*. `reinit`

is therefore ignored.

StateSelection.ImplicitWithReinit

Show more ...### Dynamically selected state with Reinit.

A variable that is dynamically selected as the state is set with a `reinit`

operator. This is currently not supported in external solvers. In BDF, the `reinit`

is ignored if the variable is not a state.

StateSelection.InvalidNever

Show more ...### Continuous state variable could not be deselected.

A variable marked with `stateSelect = StateSelect.never`

could not be deselected as a state, because no assigning equation was found and the variable must be calculated with its derivative.

StateSelection.InvalidReinit

Show more ...### Variable used in Reinit operator cannot be continuous state.

A variable is used as the first argument of the `reinit`

operator. However, this cannot be selected as the state of the system. `reinit`

is ignored.

StateSelection.InvalidReinitNever

Show more ...### Variable used in Reinit operator marked with StateSelect.never.

A variable marked with `stateSelect = StateSelect.never`

is used as the first argument in the `reinit`

operator. That is contradictory. Remove the marker or the `reinit`

call.

StateSelection.NotSelectableCandidate

Show more ...### Too many variables marked as states.

Too many variables are marked with `stateSelect = StateSelect.always`

. Some of them cannot become state variables of the continuous system. Edit the `stateSelect`

attribute of this variable or the model.

StateSelection.NotSelectableCandidateAlwaysReinit

Show more ...### Too many variables marked as states.

Some variables are used in `reinit`

or are marked with `stateSelect = StateSelect.always`

. They cannot be state variables of the continuous system.

StateSelection.NotSelectableCandidateReinit

Show more ...### Too many variables marked as states.

Some variables are used in `reinit`

and must therefore become states of the continuous system. Some of them cannot be state variables of the continuous system.

StateSelection.NotSelectableDiscrete

Show more ...### Discrete-time variables cannot be states.

A discrete variable is marked with `stateSelect = StateSelect.always`

, but cannot become a state. Edit the `stateSelect`

attribute of this variable.

StateSelection.NotSelectableStates

Show more ...### Too many variables marked as states.

In the model, too many variables are marked with `stateSelect = StateSelect.always`

. An equation makes these variables dependent. Not all of them can become state variables of the continuous system. Edit the `stateSelect`

attribute of this variable.

SymAna.NoPartialDer

Show more...### No partial derivation possible.

System.LowMemoryJacobian

Show more ...### Insufficient memory for Jacobian matrix.

Due to insufficient memory during the preparation of the Jacobian matrix, it will be calculated numerically. To avoid this use the 64-bit version of the program.

ThermoFluidics.ObsoleteFluids

Show more ...### Fluid "%1" is obsolete.

The domain *ThermoFluidics* is intended for the simulation of fluid systems in which the phase transition between liquid and gaseous plays a major role. Accordingly, the purely single-phase fluids where removed in SimulationX Version 4.0 . Please use the elements of the domain *Hydraulics* (liquid) or *Pneumatics* (gaseous) for the simulation of single-phase systems. For the simulation of two-phase systems the fluid classes *NIST* and *Table-based Fluids* are still available in the *ThermoFluidics*.

Transformation.InvalidResultDimension.Array

Show more ...### Error in expression.

The result of the expression has an impermissible dimension. Only arrays of dimension *n:2* and *2:n* as well as vectors of length *m* are permitted where *m* must equal the number of *X* values.

Transformation.InvalidResultDimension.Scalar

Show more ...### Error in expression

The result of the expression has an invalid dimension. A scalar is required.

UserInit.DimNotMatch

Show more ...### Subscript %2 of variables %1 not matching dimension (%3).

The dimension of the variable does not match the dimension of the assigned expression.

UserInit.FileNotFound

Show more ...### Initialization file %1 not found.

The initialization file could not be found.

UserInit.InvalidSubscript

Show more ...### The subscript %2 cannot be applied, because variable %1 is scalar.

The subscript cannot be applied, because the variable is a scalar.

UserInit.InvalidValue

Show more ...### Invalid value %2 for variable %1.

The type of the assigned value does not match the type of the variable.

UserInit.ValueIgnored

Show more ...### Initialization value %2 of variable %1 ignored.

The initialization value of a variable is ignored. It is not used in the model.

UserInit.VarNotFound

Show more ...### Variable %1 not found.

A variable that is initialized in the initialization file could not be found in the model

UserInit.WrongValueType

Show more ...### Value type of variable %1 not supported for initialization.

The type of a variable is not supported during initialization. It cannot be initialized with the file.

Value.BadIndex

Show more ...### Index outside of domain.

During the calculation, a subscript lies outside the valid domain.

Value.BadRecordType

Show more ...### Arguments of equal Record types required.

To compare two *Records*, they must have the same type.

Value.BadType

Show more ...### Argument has the wrong type.

In an operation, values of non-matching types are linked.

Value.Boolean

Show more ...### Argument must be of type Boolean.

Value.DimMismatch

Show more ...### Equal dimensions required.

An operator requires arguments of the same dimension. The current values have different values.

Value.DivideByZero

Show more ...### Division by zero.

Division by *0* occurred during the calculation. To find the cause, switch on *Tracing* for the calculation of the equations. All calculations are tracked in the output area. When the simulation terminates due to division by *0*, the last line of the last item contains an error message and the penultimate line contains the incorrect equation. You can then determine by tracing the values of the variables what caused this division by *0*. The tracing slows down the simulation considerably. With the help of the *traceOn* parameter of the model, you can also limit the amount of data output over time, e.g. with `0.5<time`

, so that performance is virtually maintained.

Value.ExprMonotonicty

Show more ...### Expression %1 breaking monotonicity.

Value.FamilyParam

Show more ...### Parameter value %1 aready exists.

Value.GenFloat

Show more ...### General floating point error.

Value.Integer

Show more ...### Argument must be of type Integer.

The argument of an operator or function must have an *Integer* value.

Value.InvalidOp

Show more ...### General error while calling %1 "%2".

There was an error when a mathematical function was called.

Value.InvalidOperation

Show more ...### Invalid floating point operation.

An unauthorized floating point operation occurred during the calculation. For troubleshooting see *Value.DivideByZero*.

Value.Monotonicty

Show more ...### Curve not monotonic.

An axis, usually the x axis, of a characteristic curve is not strictly monotonic.

Value.NoSequence

Show more ...### No curve with index %1.

There is no curve with the given index in a characteristic curve.

Value.NoSquareMatrix

Show more ...### Argument must be a square matrix.

The operator argument `^`

must be a square matrix or a scalar.

Value.OpDomain

Show more ...### Argument outside of domain.

The value of the argument of a mathematical function is outside of its domain.

Value.OpOverflow

Show more ...### Floating point overflow.

During the calculation of a mathematical function, a floating point overflow occurred . For troubleshooting see *Value.DivideByZero*.

Value.OpSingular

Show more ...### Argument causes singularity.

The value of the argument of a mathematical function lies within a singularity of the function.

Value.Overflow

Show more ...### Floating point overflow.

A floating point overflow occurred during the calculation. For troubleshooting see *Value.DivideByZero*.

Value.PosInteger

Show more ...### Argument must have a positive Integer value.

The argument of a function or operator must be a positive *Integer*.

Value.RangeToBig

Show more ...### Vector too big.

The arguments of the range operator generate a vector so large that no contiguous memory can be allocated to it.

Value.Real

Show more ...### Argument must be of type Real.

Value.SampleIntervalPositive

Show more ...### Sample interval must be positive.

An argument of an operator must have a scalar value.

Value.Scalar

Show more ...### Argument must have a scalar value.

An argument of an operator must have a scalar value.

Value.SeqIndexOutOfRange

Show more ...### Index outside of domain.

Value.SeqMinMax

Show more ...### Minimum/Maximum violation.

Value.SeqXOutOfRange

Show more ...### X value not defined.

The x value does not lie within the domain of a called characteristic curve. Extrapolation is disabled. Enable extrapolation or extend the domain.

Value.SeqYOutOfRange

Show more ...### Y value not defined.

When inverse calculation of a characteristic curve is used, the y value does not lie within the domain. Extrapolation is disabled. Enable extrapolation or extend the domain.

Value.SimpleValue

Show more ...### Argument must have a simple value.

The argument of the scalar operator has more than one element. It must be an array of one element, e.g. {1},{{2}}.

Value.TooManySubscripts

Show more ...### Too many subscripts.

In a subscript of a variable, e.g. v[1,2,3], there are more subscripts (here 3) than the variable has dimensions.

Value.ValueMonotonicty

Show more ...### Value %1 breaking monotonicity. %2

The inserted value would break the monotonicity of an axis, usually the x axis.