Thanks for the comment Matthew, I think that's a good suggestion. As you use it, let me know if there are any additional options/features that would be useful.

Hi Warwick,

Thanks for trying out the app. That's a bug I hadn't caught in testing. I'm updating the file, but since I work for MathWorks there's a separate submission process and I'm not sure when it will go through. Please use the 'Watch this file' link at the top of the page to get auto updates when the file changes.

Thanks, Adam

Hi Scott,

As an enhancement request, it'd be nice if this could also return the names of the variables selected from the workspace, for use in things like labeling axes.

Very useful! Thanks!

Hi Gernot,

Thanks for pointing out that blog post. You're correct that there's a very simple solution pointed to in that post that will take care of checking initialization. However in that example you are initializing the bus through a constant block, so you can't use non-constant signals to check simulation behavior. In the attached file you could easily swap out the constant blocks for something else.

I originally built this such that it used sine blocks instead of constants, and read in the appropriate frequency and amplitudes from another source, but decided to reduce it to just constants to simplify the example. Once you get the hang of how the sorting works and using the Simulink API to construct a model, it's fairly easy to expand this example to more complex situations.

Adam