Could not load/create parameter sets for "Tunable block and global parameter" in real-time application speedgoat

Question

Hai Zeng 2022-3-21

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1676709-could-not-load-create-parameter-sets-for-tunable-block-and-global-parameter-in-real-time-applicati

评论： Hai Zeng 2022-8-23

Platform: MATLAB 2021a, Simulink, speedgoat (OS QNX)

When I used the simple MATLAB/Simulink example, it works fine: https://www.mathworks.com/help/slrealtime/ug/save-and-reload-application-parameters-with-the-matlab-interface.html?searchHighlight=slrt_ex_osc_outport&s_tid=srchtitle_slrt_ex_osc_outport_2

But when I use my own Simulink real-time applications (includes many library blocks, reference subsystems, reference models, variant subsystem), I could not even load/create the parameter sets. Are there any configuration that I am missing or there are limitations on "Tunable block and global parameter" that will not work on my application? Please help. Thank you.

Following are some example commands and error messages:

example 1:

>> slbuild(mdlName);
........
>> tg = slrealtime('TargetPC1');
>> tg.stop
>> load(tg,mdlName);
>> paramSetName = 'outportTypes';
>> saveParamSet(tg,paramSetName);
>> loadParamSet(tg,paramSetName);
Dot indexing is not supported for variables of this type.

example 2:

>> myParamList = listParamSet(tg,'mdlName')
myParamList =
5×1 cell array
{'autoSaveOnStop'}
{'autoSaveOnStop'}
{'autoSaveOnStop'}
{'myParamSet'    }
{'autoSaveOnStop'}
>> tg.status
ans =
'loaded'
>> paramSetName = 'myParamSet';
saveParamSet(tg,paramSetName);
>> myParamSet = importParamSet(tg,paramSetName);
Error using slrealtime.Target/importParamSet
Dot indexing is not supported for variables of this type.

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Stefanie Schwarz 2022-8-23

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1676709-could-not-load-create-parameter-sets-for-tunable-block-and-global-parameter-in-real-time-applicati#answer_1031165

This appears to be a bug which occurs if a bus object has a boolean type bus element and the bus is used as a parameter in the application.

There are 2 workarounds:

Don't use boolean bus elements if possible, especially if the bus type is used for a parameter. Use a numeric data type instead and convert the signal in Simulink to a boolean with a Data Type Conversion block if necessary. Obviously this workaround might not scale depending on how many such parameters or bus types there are.
If the parameter with bus data type does not actually need to be tuned in the application, exclude it from tunable parameters. This can be done by changing default parameter behavior from tunable to inlined and then specifying the parameters that need to be tuned with Simulink.Parameter objects.