Error Messages: MM*

• List of Error Messages, Part 1: E*

• List of Error Messages, Part 2: F*

• List of Error Messages, Part 3: G*

• List of Error Messages, Part 4: MB* – ML*

MMdl0

statements not allowed here

MMdl1

%1 identifier "%2" already declared

MMdl10

%1 – please %2

EXAMPLES
AUTOSAR package name must consist at least of subpackage and short name – please correct AUTOSAR package name "/package" of SenderReceiver_InterfaceType Type of element "array_name" (array of records) not supported for array flattening - please remodel

MMdl100

priority of task "%1"%2 must be in interval %3

MMdl101

min period (%1s) for interrupt "%2" must not be smaller than minimum task cycle time (%3s) specified for target

MMdl102

specified deadline (%1s) of task "%2" may not exceed specified period (%3s)

MMdl104

<%1> – due to %2 – is not a lvalue and can not be used with a OUT/INOUT method argument

MMdl105

<%1> – due to %2 – can not be used as method argument

MMdl106

Element "%1" of provide port "%2" can not be read

MMdl107

Element "%1" of require port "%2" can not be written

MMdl108

<%1> – due to %2 – can not be used as OUT method argument

MMdl109

Assert operator is not supported for elements without implementation (e.g. literal and constants)

MMdl11

can not declare %2 "%1" – used as reserved word

MMdl110

internal method (macro) "%1" of type "%2" must not be called from C code component

MMdl111

usage of "%1" variable not supported in code generation for AUTOSAR

MMdl112

Access operators cannot be cascaded

MMdl113

An access operator can only be applied to a require or provide port, except for client server interface ports

MMdl1131

An invoke operator can only be applied to a client server interface port

MMdl1132

An implicit access operator can not be applied to element "%1" with its implPolicy set to "QUEUED"

MMdl114

An explicit write must be assigned to a variable, array element or record field

MMdl115

No mode defined for mode switch event "%1"

MMdl1151

Mode switch event "%1" shall not simultaneously reference the same mode declaration ("%2") as activation and disabling mode

MMdl116

%1 is not allowed in arithmetic context

MMdl117

%1 cannot be used in method "%2" which is not called from a runnable

MMdl1171

%1 cannot be used in method "%2" (called from runnable "%3") with no timing event associated

MMdl1172

%1 cannot be used in runnable "%2" with no timing event associated

MMdl118

%1 cannot be used in method "%2" which is called from more than one runnable

MMdl119

%1 access to a record element cannot be explicit

MMdl1190

%1 access to an array element "%2" (%3) cannot be explicit

MMdl1191

RTE status variable may reference multiple status returns

MMdl1192

RTE status variable is not initialized

MMdl1193

RTE status operator on "%1" requires implicit read access on that variable

MMdl1194

RTE status operator on "%1" not supported, only implicit read access to SenderReceiver Interfaces

MMdl12

%1 "%2" already declared

MMdl120

expression does not have an effect

MMdl121

INOUT argument "%1" and actual value "%2" must have same implementation because of reference semantics

MMdl122

No %1 defined for %2 event "%3" – Please press "Build\Update Interfaces" in the software component to remove the invalid event

MMdl1221

No trigger defined in trigger interface %1. Please define trigger.

MMdl1222

Please define both elements (or none) CSE-Code and Factor of Trigger Period in trigger "%1".

MMdl123

Element "%1" can not be used with copy semantics, since its type "%2" forces reference semantics

MMdl124

Timing Event "%1" has period of zero

MMdl125

Invalid %1 event specification "%2" – %3

MMdl1281

AUTOSAR component requires an operation invoked event to be specified for each operation represented by provide port "%1" – Please press "Build\Update Interfaces" in the software component to add the missing event

MMdl1282

%3 mismatch between ClientServer operation "%2" and associated runnable "%1"

MMdl1283

%4 mismatch of argument "%1" between ClientServer operation "%2" and associated runnable "%3"

MMdl1285

AUTOSAR provide port "%1" must not be used as %2, only require port allowed

MMdl1286

Invalid value (%1) for enum label "%2" of %3. Values must be in range of an implementation type.

MMdl1287

Wrong value (%3) for application error "%1" defined for ClientServer iterface "%2". AUTOSAR restricts values to be in range 1...63.

MMdl1288

Multiple enumeration types (%1) used as application errors in ClientServer interface "%2". Please restrict to one.

MMdl1289

Value range ([%1,%2]) of %3 too large to fit an implementation type

MMdl1290

Multiple %1 ("%2") used in %3

MMdl1291

Unable to deduce bound Client Server interface for application error literal <%1>

MMdl1292

The Client Server Interface Operations <%1> will have the same name <%2> due to their symbols, but it shall be unique.

MMdl14

application mode id "%1" already declared

MMdl140

operator "%1" not supported

MMdl15

identifier "%1" not declared in project "%2"

MMdl150

Memory class "%1" specified for %2 is not declared in file "%3" – Please add declaration

MMdl1500

Memory class "%1" required for %2 is not declared in file "%3" - Please add declaration

MMdl151

Name clash in EHOOKS conversion macro generation. Macro name "%1" used more than once. Please change model name of any of the involved elements.

MMdl152

Type "%1" of variable "%2" is not supported with EHOOKS

MMdl153

Mapping to external bypass value is not supported for %1 "%2"

MMdl154

Missing error code for %1 "%2"

MMdl155

Wrong type ("%1") for error code "%2" – Please use scalar type

MMdl156

Mapping of "%1" not supported – unsupported type: %2 of %3

MMdl16

missing export of variable "%1"

MMdl160

missing %1 of %2 "%3"

MMdl161

Both export and import of "%1" must have memory attribute "%2"

MMdl17

methodname "%1" already declared – used as access method name

MMdl170

%1 "%2" already declared --- %3

MMdl18

element name "%1" already declared – used in "%2"

MMdl180

element name "%1" of %2 already declared – used in %3

MMdl181

implementation cast <%1> used like variable identifier

MMdl19

multiple usage of enum value "%1" – used in "%2" and "%3"

MMdl190

multiple usage of constant value %1 in switch statement

MMdl191

ambiguous enum value "%1" – please qualify with enum type

MMdl192

ambiguous enum type – please use qualified labels

MMdl20

%1 "%2" not declared %3

EXAMPLES
ISR source "Level2" not declared identifier "<name>" not declared method or implementation cast "<impl.cast>" not declared

MMdl201

Method call argument "%2" used multiple times with OUT or INOUT direction in "%1", values overwrite each other

MMdl21

class "%1" not declared

MMdl211

Component <%1> is implemented as service routine/prototype class although it is not a ASCET class -- other component types like modules or SWCs are not supported

MMdl212

Element <%1> in service routine/prototype class is not allowed to have get/set access.

MMdl213

Element <%1> is declared as reference to prototype class <%2> -- this is not supported by ASCET

MMdl22

method "%1" not defined in class "%2"

MMdl23

method "%1" not available for "%2"

MMdl25

last operation of "%1" must be return statement

MMdl26

unknown attribute <%1> for identifier "%2"

MMdl27

unknown class <%1> for identifier "%2"

MMdl270

Invalid access to message "%1" %2 – missing or invalid message mapping

MMdl271

Invalid %1 mapping for element "%2" in "%3" – mapping to %4 supported only

MMdl2710

Invalid %1 mapping for element "%2" in "%3" – non scalar message of type "%4" is not supported by selected EHOOKS tool, but accessed in bypass function "%5" --- please use more recent version of EHOOKS-DEV

MMdl2711

Invalid %1 mapping for element "%2" in "%3" – type mismatch with "%4" and "%5"

MMdl2712

Element <%1> has mapping, but is neither a message nor a parameter

MMdl272

Invalid %1 to message "%2" in "%3" – missing internal mapping to %4

MMdl273

Invalid %1 to message "%2" in "%3" – message access in c-code component not supported in AUTOSAR context

MMdl274

Multiple mapping of "%1" to all of (%2) ––– %3

MMdl275

Mapping of record typed element "%1" requires all fields to be mapped; missing mappings for fields (%2)

MMdl276

Invalid mapping <%1> to <%2> – kind of element and kind of interface do not match.

MMdl2761

Missing mapping for %1 – %2.

MMdl277

Invalid access to %1 "%2" – local %1 can not be accessed externally

MMdl278

Missing export for element "%1" which is mandatory when using %2 type, since mapping can not provide such type.

MMdl28

call to process "%1" not allowed – %2%

MMdl280

call to runnable "%1" not allowed – use AUTOSAR means to activate runnable

MMdl281

AUTOSAR release 4x requires elements of SENDER-RECEIVER-INTERFACE "%1" to be either all mode groups or all non mode groups

MMdl282

AUTOSAR attribute "%1" has invalid value (%2) for element "%3" of kind %4

MMdl283

Invalid settings of AUTOSAR attributes for element "%1": %2="%3" and %4="%5" not supported

MMdl284

Explicit %1 access to SenderReceiver element "%2" due to %3 attribute set to "%4" not supported

MMdl2841

Implicit %1 access (%2) to message "%3", can not be converted to explicit access due complex type of message

MMdl285

Invalid %1 access to "%2" due to %3 attribute set to "%4"

MMdl2851

Explicit %1 access to element "%2" using event semantics requires "queueLength" value of port "%3" to be > 0

MMdl286

AUTOSAR release 4x restricts number of elements in MODE-SWITCH-INTERFACE "%1" to 1

MMdl287

AUTOSAR release %1 does not support %2

MMdl288

Invalid explicit access (%1) to %2 specified as implicit

MMdl289

Identical RTE macro name ("%1") for multiple runnables (%2) – please change naming

MMdl2891

Rte_Result() call to operation "%1" via port "%2" misses associated asynchronous Rte_Call() in runnable %3

MMdl29

need at least one cooperative level when specifying software tasks

MMdl290

prio for <%1> exceeds prio levels

MMdl291

%1 preemptive priority levels exceed maximum of %2

MMdl292

%1 cooperative priority levels exceed maximum of %2

MMdl293

%1 software priority levels (cooperative + preemptive) exceed maximum of %2

MMdl3

<%1> – due to %2 – is not a left value for assignment

MMdl30

<%1> – due to %2 – is not a left value for increment/decrement operation

MMdl300

<%1> – due to %2 – is not an expr to be used for call-by-reference semantics

MMdl3000

<%1> – due to %2 – is not allowed to have set method

MMdl3001

Unable to build reference from <%1>

MMdl301

cannot assign %1 element <%2> to %3 element <%4>

MMdl302

<%1> – due to %2 can not be used as reference

MMdl3021

Reference element <%1> must have read or write access

MMdl3022

Reference element <%1> must have read and write access

MMdl3023

Cannot use the address of a stack object %1

MMdl3024

Cannot use the address of a message object %1

MMdl3025

Unable to read from write-only reference <%1>

MMdl3026

Unable to read from write-only element <%1>

MMdl303

cannot initialize reference <%1> with reference <%2>

MMdl304

cannot initialize reference <%1> with implicit reference <%2>

MMdl305

cannot initialize %3 reference <%4> with %1 element <%2>

MMdl306

cannot assign to non-write reference <%1>

MMdl307

<%1> – due to %2 – is not a left value for compound assignment %3

MMdl308

illegal return value in "%1" – due to %2

MMdl309

cannot initialize <%1> with zero, because element is specified as ZERO NOT INCLUDED

MMdl31

application modes missing for task "%1"

MMdl310

application mode "%1" is assigned to several init tasks: %2 ––– only one init task per application mode is allowed

MMdl32

init task "%1" contains not unique assignments to application modes %2

MMdl33

illegal use of virtual element "%1" – may not be used in specification

MMdl340

Name of %1 ("%2") matches OIL keyword – please change

MMdl341

Name of %1 ("%2") matches reserved name – please change

MMdl342

Name of %1 ("%2")  matches %3 – please change

MMdl345

Process "%1" of module "%2" cannot be assigned to a task/ISR and an init task (%3)

MMdl346

There are more than one init runnables used, %1which is not allowed for multiple instance SWCs due to dynamic initialization of substruct pointers.

MMdl3461

There is no init runnable defined, which is not allowed for multiple instance SWCs due to dynamic initialization of substruct pointers.

MMdl3462

The memory class of the element <%1> is %2, but it has to be a variable memory class (due to dynamic initialization of substruct pointers for multiple instance SWCs).

MMdl351

operating system specification must not be empty with option message usage variant set to %1

MMdl352

process %1 must not be assigned to multiple tasks with option message usage variant set to %2

MMdl353

method %1 must not be called from different tasks with option message usage variant set to %2

MMdl355

method %1 must not use messages with option message copy variant set to "%2"

MMdl356

process %1 is used in task %2 and can there not be inlined

MMdl357

runnable %1 can not be inlined

MMdl36

Discrete type cannot be converted to modular or limited: %1

MMdl361

Invalid argument for conversion: %1

MMdl37

redundant data flag is set for %1, but %2

EXAMPLES
redundant data flag is set for <message>, but redundant data and mapped messages cannot be combined. redundant data flag is set for <NV_variable>, but redundant data and non-volatile cannot be combined.

MMdl371

verify operator can only be used on model identifier with redundant flag set

MMdl372

redundant arrays/matrices <%1> can not be assigned to references <%2> with write-to-referenced-element flag

MMdl373

verify operator is not supported in C code classes/modules

MMdl4

invalid initial value for blocklocal variable "%1"

MMdl40

Invalid initial value %2 for variable "%1" with non-linear formula – leads to division by 0

MMdl41

wrong dimension of init value for <%1> – check maxSize

MMdl42

wrong %1-dimension of init value for <%2> – check %1-maxSize

MMdl43

can''''t init global reference <%1> with local instance <%2>; use a global init value instead

MMdl44

init value <%1> of non modifiable element "%2" does not match specified physical interval %3 of selected implementation

MMdl45

wrong init value for enumerated element "%1" --- label "%2" not found in enum type "%3"

MMdl451

Dependent parameter "%1" of type "%2" currently not supported.

MMdl452

Virtual element "%1" of type "%2" currently not supported.

MMdl46

init value for rescalable element "%1" must be 0

MMdl47

Implementation of instance <%1> of rescalable component <%2> must have a rescaling formula

MMdl471

Rescalable element <%1> is not allowed in project

MMdl472

Local variables are not allowed in project context: "%1"

MMdl48

constant folding: generated endless loop --- please change specification of %1

MMdl490

No dispatch point is connected to any bypass function

MMdl491

Local messages are not supported by selected EHOOKS tool, but accessed in bypass function "%1" (%2) --- please use more recent version of EHOOKS-DEV

MMdl492

Name clash "%1" with %2 defined by all of (%3) --- please rename elements appropriately

MMdl493

Bypass Function "%1" uses dT and thus should have a period specified

MMdl5

n-dimensional arrays in <%1> not supported

MMdl50

expected at least one element in %1 specification <%2>

MMdl500

expected expression for argument, got statement

MMdl501

element <%1> (no reference flag) uses external %2 which does not contain at least one element

MMdl502

external %1 contains element <%2> of type %3 which should match the specification with respect to "external struct"

MMdl503

element "%2" has type "%1" with external declaration which is currently not supported for %3 generation

MMdl51

expected type <matrix> (<%1>) for two-dimensional access

MMdl510

%1 with external struct/typedef should be defined with user-defined order

MMdl52

expected type <array> (<%1>) for one-dimensional access

MMdl53

expected return value for method

MMdl54

illegal use of label <%1>

MMdl55

implementation type <Bit> currently not supported for complex class type

MMdl551

Method argument <%1>  must have an implementation, but does not

MMdl552

Method return of <%1> must have an implementation, but does not

MMdl553

Grouped tables are not supported as method argument: "%1"

MMdl554

The type %1 is only supported as method argument with IN direction ("%2"). %3 is not allowed.

MMdl56

multiple defined enum value <%1>

MMdl560

Multiple defined conversion name "%1" – used as formula as well as enumeration name

MMdl561

multiple defined label "%1" – as enum value of %2 and label in specification of %3

MMdl562

name clash: multiple defined label "%1" as "%2" and "%3"

MMdl563

ambiguous reference to element "%1"

MMdl57

name clash in "%1": elements with GET() access enabled, should not start with "SET"

MMdl6

type mismatch: expected <%1> (<%2>), got <%3> (<%4>)

MMdl60

type mismatch: expected <%1>, got <%2>

MMdl600

type mismatch for oneDInterpolation (%1): expected cont/cont or disc/disc combination

MMdl601

type mismatch for twoDInterpolation (%1): expected cont/cont/cont or disc/disc/disc combination

MMdl602

mismatch of interpolation: %1 and %2

MMdl603

Undefined interpolation %1

MMdl6031

No interpolation found for %1, please specify the interpolation.

MMdl604

Char tables cannot have optimized data structures in the experiment

MMdl605

type mismatch for method call ("%1"): expected return value

MMdl606

type mismatch for method call ("%1"): expected VOID method, i.e. no return value

MMdl607

cannot return %1 element <%2> from %3 return of method <%4>

MMdl608

Char tables with optimized data structures are not supported by SCOOP-IX

MMdl609

Double precision char tables are not allowed for value implementation type uint32/sint32/real64

MMdl610

type mismatch: selected implementation type <%1> is not suited for %2 "%3" and can not be used

MMdl611

Illegal Type in %1 mapping of message "%2". Enumeration type "%3" must have consecutive values

MMdl612

Literal or constant already has unit %1 and cannot be converted to %2

MMdl613

Invalid operand of type %2 for operator <%1>

MMdl614

Instance <%1> of component with generic physical units <%2> must have a concrete unit

MMdl615

Instance <%1> of component with generic physical units <%2> must have a concrete unit without offset

MMdl616

Unable to deduce associated client server interface from first assignment to local variable <%1> of application error type <%2>.

MMdl62

type mismatch: expected <cont> or <disc>, got <%1>

MMdl620

cannot assign complex type to blocklocal variable "%1" without implementation

MMdl6201

blocklocal variable <%1> of non-scalar type <%2> (without reference flag) must have implementation

MMdl621

illegal implementation type "%1" used for model type "%2" at element "%3"

MMdl622

Operand <%1> of pre/post inc/decrement must not be rescalable

MMdl623

Operation %1 is not supported for non-linear formula %2

MMdl624

Operation <%1> is only supported for reciprocal formula <%2> if all operands have same signedness and have identical formulas or are literals

MMdl63

type mismatch: expected <disc>, got <%1>

MMdl630

either both or none of blocklocal variable "%1" without implementation and its assignment expression must be enumeration

MMdl631

type mismatch: expected numerical type, got %1

MMdl632

type mismatch: at most one operand must be rescalable for operation <mul>

MMdl633

type mismatch: the numerator must be rescalable if the denominator is rescalable for operation <div>

MMdl635

non identical types in %1 mapping for "%2" (defined in "%3") – %4: expected <%5>, got <%6>

MMdl636

multiple elements are mapped to %1, but only one allowed

MMdl639

illegal type for input or output "%1" of %2 component – use struct (i.e. class component with no methods) or record instead

MMdl64

type mismatch: type <%1> is not indexable

MMdl640

illegal type for method "%1" – Module components may not be used as return type due to the single instance semantics of Modules

MMdl641

illegal type for argument "%1" – Module components may not be used as type for arguments of Class methods

MMdl642

illegal type %2 for record element "%1" – Record elements may only be of type cont, limited, wrap around, sdisc, udisc, log, enum, array, matrix or record

MMdl6421

illegal type <%3> for record element <%2> in external %1 – External record elements in experiments may only be of type cont, limited, wrap around, sdisc, udisc, log, or enum

MMdl643

illegal type %2 for record element "%1" – Record elements may not be references

MMdl6431

element <%1> has illegal element kind <%2> for record

MMdl644

Assignments to records are not allowed (only to record references or primitive record elements)

MMdl645

illegal type %2 for sender/receiver interface element "%1" – Elements may be cont, limited, wrap around, sdisc, udisc, log, enum, array, or record (with such fields)

MMdl6451

Illegal type %2 for calibration interface element "%1" – Elements may be cont, limited, wrap around, sdisc, udisc, log, enum, array, or record (with such fields)

MMdl6452

Illegal type %2 for NV Data element "%1" – Elements may be cont, limited, wrap around, sdisc, udisc, log, enum, array, or record (with such fields)

MMdl646

Illegal type %2 for client/server operation "%3" argument "%1" – Arguments may be cont, limited, wrap around, sdisc, udisc, log, enum, array, or record (with such fields except arrays)

MMdl647

Illegal type %1 for client/server operation "%2" return type – Returns may be enumerations (application errors) or AUTOSAR Std_ReturnType

MMdl648

illegal use of interrupt task "%1" --- not supported, please remove from operating system specification

MMdl649

Illegal type %1 (for element "%2" in %3) – enumeration used as application error

MMdl6490

The AUTOSAR package cannot be empty for an externally defined %1 %2

MMdl6491

The specified AUTOSAR package name "%1" must be unique for %2 "%3"

MMdl65

illegal class for interpolation: expected char table, got  <%1>

MMdl650

Invalid type "%1" for IRV "%2" – %3

MMdl651

Illegal type %2 for IRV "%1" – IRVs may be cont, limited, wrap around, sdisc, udisc, log, enum, or record (with such fields except arrays)

MMdl652

Illegal %1 for element "%2" in %3 – must be %4

MMdl653

Invalid attribute "%1" for element "%2" - %3

MMdl66

illegal dimension for interpolation: expected 1-D char table, got 2-D

MMdl67

illegal dimension for interpolation: expected 2-D char table, got 1-D

MMdl670

Cannot read or change the axis points of a fixed char table

MMdl671

Interpolation performed on a changed char table without previous search on "%1"

MMdl672

Fixed char table "%1" with a power-of-2 distance is not compatible with fixed char table "%2"

MMdl673

Fixed char table "%1" is not compatible with fixed char table "%2" due to different axis definitions

MMdl674

Fixed char table "%1" has non-equidistant implementation values %2

MMdl675

Fixed char table "%1" has distance "%2" which is not representable in implementation "%3"

MMdl68

illegal class for search: expected distribution, got <%1>

MMdl69

illegal implementation type for array/matrix <%1>: bit type not supported

MMdl691

element <%1> has type array/matrix of record – this type is not supported

MMdl692

Arrays/matrices of distributions are not supported: <%1>

MMdl693

Arrays/matrices of char tables or grouped tables %2 are not supported: <%1>

MMdl694

Element <%1> has type %2, which is not supported by ASCET for generation of multi instance software components.

MMdl695

The element <%1> needs an IRV copy, which is not supported by ASCET for generation of multi instance software components.

MMdl696

The element <%1> has type Fixed Char Table, which is not supported by RTE for generation of data structures.

MMdl697

The element <%1> is of type matrix with %2 length, which is not supported by ASCET for Autosar projects.

MMdl698

Arrays/Matrices of classes are not allowed in AUTOSAR projects <%1>.

MMdl7

wrong number of arguments for %1 <%2> of class <%3> – expected %4, got %5

MMdl71

illegal value <%1> for case literal – exceeds value range <%2..%3> of switch entry expression

MMdl710

illegal value <%1> for case literal – does not match switch entry expression type <%2>

MMdl72

illegal indexing of return value (function <%1> – must enable direct access (in code generation settings)

MMdl721

Illegal receiver of direct access method call – must be an identifier

MMdl722

Illegal receiver of method call "%1" - must be %2

MMdl73

expected constant expr in case statement

MMdl74

illegal value <%1> for indexed expression "%2"

MMdl75

unused code due to multiple return statements in method "%1"

MMdl76

multiple default statements in switch statement

MMdl77

index <%1> out of bounds for indexed expression "%2"

MMdl771

Dimension of array/matrix <%1> has invalid value <%2>. Allowed range for dimension is <1-%3>

MMdl772

Too many elements in %4 "%1" (<%2>). Allowed number of elements is <%3>

MMdl780

Cannot use the local system constant <%1> as the variant for global element <%2>.

MMdl781

Variant size <%1> for element <%2> must be a system constant.

MMdl782

Variant size <%1> for element <%2> must be of type limited, wrap around, udisc, sdisc, or enum.

MMdl783

Variant size <%1> for element <%2> must have values inside the array index range.

MMdl784

It is not possible to use the element <%1> with a variant size as an implicit reference.

MMdl785

It is not possible to use the element <%1> with a variant size when ResolveSystemConstants=Runtime.

MMdl786

The init value <%3> of <%1> is out of bounds %2 due to ResolveSystemConstants=Generationtime.

MMdl7861

The init value "%1" of "%2" is not an integer and cannot be used as array size for "%3"

MMdl787

Element <%1> has variable array/matrix reference flag but is no reference.

MMdl788

Expression <%1> can not be converted to a variable array/matrix reference.

MMdl789

Fixed/variant reference <%1> can not be converted to variable reference.

MMdl790

Variable array/matrix references should not be used as runnable <%1> arguments.

MMdl791

Variable array/matrix references to array/matrix instance in records <%1> are not allowed.

MMdl792

Variable array/matrix references to array/matrix with external get access are not allowed for %1.

MMdl793

Element <%1> uses deprecated CCode reference. Please replace CCode reference (see implementation editor) by explicit reference (see properties editor).

MMdl794

Element <%1> is a message and a reference, but the combination is not allowed.

MMdl795

Variant size <%1> for element <%2> is system constant at runtime which is not supported.

MMdl7951

The type <%1> has the variant size <%2>, but the resolve time of the system constant is not valid for this usecase.

MMdl7952

The usage of <%1> is not allowed in <%2>. (System constants are not allowed inside %3.).

MMdl7961

Expression for dependent system constant %1 must be compile-time constant

MMdl7962

Expression for dependent system constant %1 must be generation-time constant

MMdl7963

Recursive dependency for system constant %1

MMdl7964

Expression for dependent system constant %1 must not be empty

MMdl797

Expression for dependent system constant %1 cannot contain floating point elements

MMdl798

Dependent system constant %1 cannot be rescalable

MMdl799

User defined system constant %1 cannot be externally defined as it %2

MMdl7991

User defined system constant %1 cannot be resolved at run time

MMdl8

macro on stack is not an expr

MMdl81

macro on stack is an expr

MMdl82

read access to %2 "%1" prior to assignment

EXAMPLE
read access to method local variable "localVar_name" prior to assignment

MMdl821

read access to method local variable "%1" prior to initialization of reference

MMdl83

read access to a definitely uninitialized reference "%1"

MMdl84

illegal use of method call "%1" – need constant value here

MMdl85

illegal use of method call "%1" – only direct access macros allowed here

MMdl871

Continuous state element <%1> has type <%2>, but should be of model type cont (or array of cont)

MMdl872

CT component element <%1> has type <%2>, but should be of arithmetic model type or bool (or array of arithmetic or bool)

MMdl873

Constant <%1> has type <%2>, but should have scalar model type

MMdl88

illegal use of direct access to "%1" – no assignment allowed here

MMdl89

illegal definition of direct access (%1) for "%2" – due to %3

MMdl91

method "%1" of class "%2" not defined as public

MMdl911

method call and access to element are ambiguous: both have the name <%1>

MMdl912

method call to method <%1> without parenthesis

MMdl92

invalid recursive method call to "%1" ––– possibly leads to infinite loop

MMdl93

illegal use of type <%1> as system constant for element <%2>

MMdl94

writable value expected instead of <%1>

MMdl95

method argument "%1" not assigned, but needs assignment because of OUT direction

MMdl96

method "%1" declared as side-effect-free, but %2

MMdl97

method "%1" declared with preprocessor inlining, but %2