I'm using a large FMU with over 36K variables. Some of which are initial conditions that need to be changed at run time.
I'm using FMIKit-Simulink-3.0-alpha.4. Typing in the start (value) window for a variable will make the value bold, and have it show up in the s-function parameter list for the FMU.
However, if the path to the parameter is long FMIKit will construct a variable name from the structure path.name.
As shown in the image below that name can be more than Matlab's 73 char limit and though the name is bold in the FMIKit GUI for the FMU, a Matlab error is thrown (see below) and the parameter is not added to the s-function parameter list.
I'm using a large FMU with over 36K variables. Some of which are initial conditions that need to be changed at run time. I'm using FMIKit-Simulink-3.0-alpha.4. Typing in the start (value) window for a variable will make the value bold, and have it show up in the s-function parameter list for the FMU. However, if the path to the parameter is long FMIKit will construct a variable name from the structure path.name. As shown in the image below that name can be more than Matlab's 73 char limit and though the name is bold in the FMIKit GUI for the FMU, a Matlab error is thrown (see below) and the parameter is not added to the s-function parameter list.