README.md states:

The Reference FMUs are a fork of the Test FMUs by Dassault Systèmes, which are a fork of the FMU SDK by QTronic, both released under the 2-Clause BSD License.

This does not seem to be true as this repo is a real source repo and not a forked repo.

Create an example for importing FMUs with dependencies on additional binary libraries (e.g., DLLs in Windows) in the corresponding binary folder, see e.g. e.g. https://github.com/modelica/fmi-design/tree/master/Reference_FMUs/src/resources (see #34 (comment))

almost equals pre(currentCommunicationPoint) + pre(communicationStepSize)

e.g. numberOfEventIndicators="0"

following modelica/fmi-standard#1101;
(especially: examples/co_simulation.c which is included in the standard text)

As suggested by @andreas-junghanns in modelica/fmi-standard#1143 (review) , we should validate the example used to introduce synchronous clocks (see modelica/fmi-standard#1073) by creating those FMUs in the Reference FMUs.

In the standard we have

If causality = input and variability = Clock, that is, the variable is an input Clock, it is required to provide a start value for describing the expected initial condition of the input Clock for that FMU. If an input Clock has fmi3True as a start value, the environment should activate the Clock the first time it enters Event Mode. The environment can nevertheless choose different start values if it is not possible to fulfill the conditions in a simulation setup.

I don't understand what would be the point for a clock start value.
What information does it bring.

Either the master is using a clock and then it knows if it should be active at time tStart.
Or the master is not activating the clock then it should always be false.

What does it mean to have a start == true and ofset == "some value"

Or am I missing something?

moved from CATIA-Systems/Test-FMUs#13

In the modeldescription,xml file of the LinearTransoform model (

Test-FMUs/LinearTransform/FMI3.xml the variables m and n are declared as Float64 variables.
Shouldn't they have an integer data type?

Comment by @t-sommer: Yes. It's still a work in progress. Currently the dimensions are fixed.

for

• Model Exchange
• Basic Co-Simulation
• Hybrid Co-Simulation
• Scheduled Co-Simulation

to assert correct calling sequence.

The following code has strange indentation in the document:

[source, c]
----
include::Reference-FMUs/examples/model_exchange.c[tags=ModelExchange]
----

and return fmi2Error if a category does not exist

We should ship open source software licenses with the reference FMUs
Reason: to give an example for the usage of the docuemtation/licecenses folder (see https://fmi-standard.org/docs/3.0-dev/#fmu-distribution), also in the light of modelica/fmi-cross-check#114 to require from tools participating in the cross-check the necessary licesne information

Licesense files to be added:

• BSD license of the reference FMUs https://github.com/modelica/Reference-FMUs/blob/master/LICENSE.txt
• BSD and CC-BY-SA License for the FMI Standard and header files CC-BY-SA
• (what else?)

What is the purpose of this repo compared to https://github.com/modelica/Test-FMUs?

It would be good to have examples for reference FMUs for the terminals and icons features.
@CSchulzeTLK : Could you provide examples?

see also CATIA-Systems/FMPy#260

moved from CATIA-Systems/Test-FMUs#14

One could e.g. use the LinearTransform example. There trivially the Jacobian is just the Matrix A; so one can easily provide dirictionalderivatives by multiplying with A.

And I would like to extend this for the adjoint derivatives modelica/fmi-standard#722.

• I could create a new BouncingBall FMU just replacing in Visual Studio its FMI3.xml:
  (https://github.com/modelica/Reference-FMUs/blob/master/BouncingBall/FMI3.xml)
  and its alpha6 headers:
  (https://github.com/modelica/fmi-standard/tree/master/headers ).

• Installed FMPy developer version 7cd84fd
  https://dev.azure.com/CATIA-Systems/FMPy/_build/results?buildId=806&view=results

• FMU can be validated but not initialized. Could not debug it with new "restype" functionality in
  https://github.com/CATIA-Systems/FMPy/blob/216bd08c76c05a97d145e29f8ada7a156df0bceb/fmpy/fmi3.py#L307

Could you please provide an example on its usage?

Thank you

I'm attempting to port the FMI2 formal model to cover FMI3, but running this over the various Reference FMU configuration files raises some errors. It may be that these are errors in the tool rather than the FMUs, but I think these are real problems according to the current documentation. I've listed the "raw" errors with some explanation interleaved:

-------------------- Clocks/FMI3.xml
Checking XML
2.2.8 Variable "inClock3" causality/variability/initial/start <input>/<clock>/<exact>/nil invalid at line 16
2.2.8 Variable "inClock3" initial/variability/start <exact>/<clock>/nil invalid at line 16
2.2.8 Variable "input2" causality/variability/initial/start <input>/<discrete>/nil/nil invalid at line 24
2.2.9 Outputs section does not match output variables at line 28
2.2.9 InitialUnknowns must include refs: {1004, 1005, 2001, 2002, 2003, 2004, 2005, 2007}
Errors found.

inClock3 should have a start value defined, as (F) in the standard in 2.2.8.
input2 should have a start value defined, as (D) in the standard in 2.2.8
The outputs section should list all of the output variables, as it says in 2.2.9 (1004 and 1005 are missing)
The initial unknowns should include the outputs which have default initial values of calculated, see 2.2.9.

-------------------- Feedthrough/FMI3.xml
Checking XML
2.2.9 InitialUnknowns must include refs: {3, 5, 7, 9, 12}
Errors found.

The initial unknowns should include the outputs which have default initial values of calculated, see 2.2.9.

-------------------- LinearTransform/FMI3.xml
Checking XML
2.2.8 Variable "m" causality/variability/initial/start <parameter>/<constant>/nil/[2] invalid at line 16
2.2.8 Variable "m" variability/causality <constant>/<parameter> invalid at line 16
2.2.8 Variable "n" causality/variability/initial/start <parameter>/<constant>/nil/[3] invalid at line 17
2.2.8 Variable "n" variability/causality <constant>/<parameter> invalid at line 17
2.2.8 Variable "A" causality/variability/initial/start <parameter>/<fixed>/<calculated>/nil invalid at line 21
2.2.8 Dimensions of "u" do not match start vector at line 18
2.2.9 Outputs section does not match output variables at line 30
2.2.9 Derivatives declared, but no Real/derivative variables at line 30
2.2.9 InitialUnknowns must include refs: {4}
Errors found.

A parameter variability must be fixed or tunable, but m and n are constant.
The dimenions of u say it is a one-dimensional value of three elements, but the start value is not.
The outputs section should list all of the output variables, as it says in 2.2.9.
Value reference 1 is not a derivative of anything.
The initial unknowns should include 4 because it is an output variable that is calculated.

-------------------- Resource/FMI3.xml
Checking XML
2.2.8 Variable "y" initial/variability/start <calculated>/<continuous>/[0] invalid at line 16
2.2.9 InitialUnknowns must include refs: {0}
Errors found.

A calculated value cannot have a start attribute.
The initial unknowns should include 0 because it is an output variable that is calculated.

Could someone check these?

A couple of errors are raised by the formal checking of the FMI2 Reference FMUs:

-------------------- Resource/FMI2.xml
2.2.7 Variable "y" initial/variability/start <calculated>/<continuous>/0 invalid at line 29
2.2.8 InitialUnknowns must include: {1}
Errors found.

A calculated value cannot have a start attribute.
The initial unknowns should include 1 because it is an output variable that is calculated, by default.

-------------------- Stair/FMI2.xml
2.2.7 Continuous variable must be Real at line 29
Errors found.

The value is declared as an Integer.

I provide a PR that shows this problem with a modified bounding ball model (called BouncingBallStairs): #70

I also fixed this issue in #71

The expected behavior of the BouncingBallStairs model is as follows:

Essentially, each time there's a bounce, the model schedules a time event for about 0.1s later.

The model also shows that, when an timed event happens at the same time as a state event, it can happen that the state event is not longer handled. That is, if the ball collides with the floor (the importer detects a zero crossing), but the floor moves, then the ball will no longer collide with the floor.

The behavior obtained from #70 is the incorrect one:

In Reference-FMUs/src/fmi3Functions.c it shoud be
#define FMI3_FUNCTION_PREFIX pasteB(MODEL_IDENTIFIER, _)
instead of
#define fmi3_FUNCTION_PREFIX pasteB(MODEL_IDENTIFIER, _)

in order to be consisten with fmi3Functions.h:
#if defined(FMI3_FUNCTION_PREFIX)

Otherwise the build will fail

by adding a scheduler

Trying to assign "fmi3ClockActive" or "fmi3ClockInactive" using "fmi3SetClock" does not work.

1. I define in my FMU (model.c) the function setClock, for which I pass the bool value* and *index along with the model instance and the value reference:

Status setClock(ModelInstance* comp, ValueReference vr**, bool* value, size_t index*) {
switch (vr) {
case vr_inputClock1:

		// set the output variables
		M(inputClock1) = value[(*index)++];
		return OK;

}

2. The fmi3 function "fmi3SetClock" needs then more arguments in the instruction "setClock", see below:

   fmi3Status fmi3SetClock(fmi3Instance instance,
   const fmi3ValueReference valueReferences[],
   size_t nValueReferences,
   const fmi3Clock values[],
   size_t nValues) {

   ASSERT_STATE(SetClock)

   Status status = OK;

   for (size_t i = 0; i < nValueReferences; i++) {
   if (values[i]) {
   Status s = setClock(instance, valueReferences[i]);
   status = max(status, s);
   if (status > Warning) return (fmi3Status)status;
   }
   }

   return (fmi3Status)status;
   }

I'm trying to set up CI with Azure Pipelines for this repo. However https://dev.azure.com/modelica seems to exist already.

@beutlich, @sjoelund, do you know who has access to this organization?

see also https://github.com/qtronic/fmusdk/blob/master/fmu20/src/models/bouncingBall/modelDescription_me.xml

some files still have bcs, scs and hcs in the name - this should likely be cleanup for clarity.

@MBlesken, can you take a look at this?

Detected this while reading section 3.2.4. of the fmi standard doc:

    ​m = M_fmi3InstantiateModelExchange("m", MODEL_GUID, NULL, fmi3False, fmi3False, NULL, cb_logMessage);
// "m" is the instance name
// "M_" is the MODEL_IDENTIFIER

   ​if (m == NULL) {
       ​status = fmi3Error;
       ​goto TERMINATE;
   ​}

// set the start time
time  = tStart;

The intention of this request is to better understand the concept of "clocked model partitions" when applied to Co-Sim FMUs.

Hence, we would like to have a reference CS FMU featuring two "clocked model partitions", see picture below.
Each model partition contains, at least:

• a "triggered" input clock
• a float64 input variable
• a float64 output variable
• a (triggered) output clock
• a dummy calculation inside each model partition, including e.g. clock tick counters

The dependencies of the "clocked variables" associated to its corresponding partition should be clearly represented in the model. For this reason, the description of an up-to-date ModelDescription.xml, where the clocks and other variables in the FMU are described according to their current features as described in the specification, is also welcome.

using a simple scheduler

when importing and compiling multiple source code FMUs.

Hello,

Trying to generate a VS 2017 x 64 Solution using CMakeGUI v3.11.1 I got the error:

CMake Error at CMakeLists.txt:23 (add_compile_definitions):
Unknown CMake command "add_compile_definitions".

When I replaced "add_compile_definitions" through "add_definitions" I could generate a VS solution with 19 projects inside using the CMake Options:

FMI_TYPE CS
FMI_VERSION 3

But when building the VS solution I got the errors:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Severity Code Description Project File Line Suppression State
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory Dahlquist E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory BouncingBall E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory BouncingBall E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 BouncingBall e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 BouncingBall e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 BouncingBall e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory Clocks E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory Clocks E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Clocks e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 Clocks e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Clocks e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory Dahlquist E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Dahlquist e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 Dahlquist e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Dahlquist e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory Feedthrough E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory Feedthrough E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Feedthrough e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 Feedthrough e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Feedthrough e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory LinearTransform E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory LinearTransform E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 LinearTransform e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 LinearTransform e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 LinearTransform e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory Resource E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory Resource E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Resource e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 Resource e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Resource e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory Stair E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory Stair E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Stair e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 Stair e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 Stair e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory VanDerPol E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory VanDerPol E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 VanDerPol e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 VanDerPol e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 VanDerPol e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory co_simulation E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory co_simulation E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory cs_early_return E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory cs_early_return E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 cs_early_return e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be 3 cs_early_return e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 cs_early_return e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory jacobian E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory jacobian E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 jacobian e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 jacobian e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 jacobian e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory model E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory model E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 model e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 model e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 model e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory model_exchange E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory model_exchange E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 model_exchange e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 model_exchange e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 model_exchange e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory scs_synchronous E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory scs_synchronous E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 scs_synchronous e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 scs_synchronous e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 scs_synchronous e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory scs_threaded E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory scs_threaded E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 scs_threaded e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 scs_threaded e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 scs_threaded e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory slave1 E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory slave1 E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 slave1 e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 slave1 e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 slave1 e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1083 Cannot open source file: '_CRT_SECURE_NO_WARNINGS': No such file or directory slave2 E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1083 Cannot open source file: 'FMI_VERSION=3': No such file or directory slave2 E:\01_VVI\ModelicaReferenzFMUs\Build\c1 1
Error C1189 #error: FMI_VERSION must be 3 slave2 e:\01_vvi\modelicareferenzfmus\src\fmi3functions.c 9
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 slave2 e:\01_vvi\modelicareferenzfmus\include\model.h 5
Error C1189 #error: FMI_VERSION must be one of 1, 2 or 3 slave2 e:\01_vvi\modelicareferenzfmus\include\model.h 5
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////
could you please provide a solution for this?

Thank you and regards

see also modelica/fmi-standard#951

In LinearTransform FMU Example, there are more multi-dimensional variables and their Dimension elements refer to another variable by valueReference attribute. The problem is that these variables are defined as Int32, which is in contradiction with the FMI 3 standard: "The referenced variable must be a variable of type < UInt64 >"