Hi Guido,

thanks for your update, this sounds like a known bug in the product where we fail to add the automatic inner declaration to a inner outer declaration.

I have added you to the list of reporter so that we can contact you when it is fixed.

As you pointed out, a workaround is to add by hand the missing inner declaration at the top level of your model.

Quentin

The internal error shown is also preventing SystemModelSimulate[ ] from running a model that contains a simultaneous inner outer declaration (WSM will simulate a model despite an internal error message).

Which example are you referring to here? The InnerOuterTest.UsesComponentWithInnerOuterParameter in your Update 2 doesn't build for me in Simulation Center either (which is expected when there is an internal error).

In the example TestingInnerOuter2, my understanding is that when declaring an “inner outer” component it behaves as an outer in its scope, but as inner for its subcomponents. Seems like the problem here is that the modelica compiler is expecting to receive a binding for the outer part of the component. That’s why your example TestingInnerOuter3 works.

In example TestingInnerOuter_3, it’s not clear to me what’s the value that submodel.x and submodes.y should display. To any submodel containing an outer the values seen should be the negative, but in its own context they should be the positive. Seems like the SimulationCenter is picking the first case.

Regarding your Update 1, every time that there’s a component declared as outer (no matter if it’s inner as well), when a matching inner is not found, the warning is displayed.

Your Update 2 example seems to be a bug because is reported as an Internal Error. I’m not sure why this is happening.

All your examples have been sent to the developers.