Simulink Simulation Model Controls Greyed Out During Running Of Simulation In LabVIEW...

[MSATLAB]

Hello,

     I have a simulation model that I have made in Simulink and we are running it in LabVIEW.  I went through the SIT Connection Manager and loaded my model and put some knobs and charts down to change and monitor variables.  I also went to the Mappings section of the SIT Connection Manager and mapped the corresponding parameters.  So now that I have everything linked, I go and run the VI and a chart and two knobs are greyed out and I cannot monitor or change the values, but some of the others are working just fine.  I am not sure why, I guess I am assuming that it is just a compatibility issue between LabVIEW and Simulink, but I wanted someone elses opinion.  So if someone could shed some light on this, I would greatly appreciate it.  Thank you.

Michael

[Jarrod_S.]

This isn't an incompatibility between LabVIEW and Matlab. Most likely you are trying to set a parameter that doesn't really exist in your model during run-time. Simulink has various optimization settings that make the model run faster or use less memory, but one downside is that these optimizations make it impossible to tune some parameters or probe some signals.

For instance, one such optimization is called inline parameters. The basic idea (according to my understanding) behind inlining a parameter is that instead of having the parameter value stored in a variable that can be altered at run-time, the parameter value is built directly into the generated code that gets run in the simulation. This allows your block that has the parameter to run more quickly, because it doesn't have to access a variable value every time it runs. It also saves some space in memory. However, that leaves the Simulation Interface Toolkit with no way to tune the parameter.

Here's a document you can refer to for more information on what optimizations might be impacting your simulation, and what you can do to get it to work properly. In SIT 4.0, which was just released, we made it a point to give the user much more information about the source of this type of problem, since it's a common issue. Hope this helps!

Message Edited by Jarrod S. on 08-16-2007 10:34 AM

[boltzmann]

This is caused by invalid mappings to the Simulink model and is discussed in the help for the Simulink Interface toolkit.  Mappings typically become invalid if the Simulation Interface Toolkit cannot communicate with a model parameter or signal correctly.  Look at the Creating Mappings help topic under the Simulation Interface Toolkit help for a discussion of why this happens and ways to fix

[Jarrod_S.]

Thanks boltzmann... My post took too long to write!

[MSATLAB]

Thank you both very much for the information!!! I will definately be looking into it deeper now.  I have a better udnerstanding of what is going on.  Thank you both very much!

Michael