You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The variable naming convention of the FMU MUST be structured.
Does not hold for usage of the FMU with MATLAB Simulink, as there is the requirement to set it to flat to get it connected to other Simulink blocks.
Can we chage this requirement on the OSMP doc?
Where did it actually come from?
The text was updated successfully, but these errors were encountered:
Hmmm, I have never seen a problem in Simulink with structured naming convention; can you be more specific?
The reason that structured naming convention is required (from the beginning) is that we use it in the OSMP names, and hence structured naming convention ensures that no conflicting names are generated (in flat anything more or less goes, structured is the naming convention that assigns meaning to . and [], etc.).
So, I tried to get the FMU connected, when structured naming convention is selected.
Unfortunately, I could not manage to get the BUS input connected in Simulink that appears in this case instead of three signal inputs.
MATLAB-Docu doesn't help at all in this case.
@pmai do you guys have experience with that?
So far, I will stick to flat naming convention, as it works :-)
Describe the problem
We experienced that the line in the doc:
Does not hold for usage of the FMU with MATLAB Simulink, as there is the requirement to set it to
flat
to get it connected to other Simulink blocks.Can we chage this requirement on the OSMP doc?
Where did it actually come from?
The text was updated successfully, but these errors were encountered: