Using external interface along with model referencing

I have a relatively large model and have tried to use model referencing. I have a target for which i generate and compile code and this seems to work.

However, i have problems getting the external interface to work (Connecting to target). I can connect, but i can only see values for the main model. The referenced models does not go external, when connecting.

Is this expected or is there a way to use external mode with referenced models?

Answer 1

[Kaustubha Govind]

According to this page in the documentation:

Simulink Coder builds and Embedded Coder software projects do not support external mode in model reference. If you select the external mode option, it is ignored during code generation.

So it looks like what you see is expected.

If this is a desirable feature for you, please consider submitting an enhancement request by contacting MathWorks Technical Support.

[Thomas Becker]

Hi, does anyone know, if the feature of using the External Mode together with referenced models has been added in the mean time, up to Release R2017b? I didn't find anything the the release notes...

Answer 2

[Casper Lyngesen Mogensen]

I have seen that in the documentation and refused to believe it. With out external mode, debugging is more difficult, especially with larger systems.

I have submitted an enhancement and hopes that this is added soon.

We just have to continue with one large model, as it is now. And yes we do have parts of the model in libraries, but it would be nice to have some parts precompiled..

Answer 3

[René]

I also experienced the same problem. I am using dSPACE and without having the possibility to tune the parameters real-time, I cannot use dSPACE for tuning my controllers (for a air pressure controller). This is really annoying, because I adapted my model to use model referencing instead of libraries, to have some advantages with embedded code generation. But this is a real show stopper!

I guess I will have to build my model back to use libraries and accept the disadvantages for setting up a C++ interface description.

Regards,

René