SystemTest's Limit Check throws an error as the variable being tested on is empty. How do I get this LimitCheck working?

2 views (last 30 days)
James on 26 Aug 2011
I have a SystemTest of a Simulink model, where the outport signals are mapped to Test Variables.
When I try and perform a limitcheck, I get the Error Message: "[variableName] is empty."
I've not managed to figure out a workaround. When I attach a scope onto the outport signal, I find it is producing a signal right from the start of model simulation.

Accepted Answer

James on 14 Sep 2011
Within SystemTest the order of execution corresponds to the order of elements within each of Pre/Main/Post test. So a LimitCheck or MatLab code that is run before the Simulink Model (i.e. listed above the Simulink Model, within Main Test) will not have access to the variables corresponding to the output of the model. This gives the variable is empty error.
To sort, click on the LimitCheck/MatLab script test elements and drag them down within SystemTest to below the Simulink test element.

More Answers (1)

Fangjun Jiang
Fangjun Jiang on 26 Aug 2011
I think the problem might be that the signal is not logged. Do you have a signal label for that signal line? Does the "variableName" exist in the base workspace after the simulation? Right click the signal line, choose "signal properties", you will see a dialog to specify the signal name, log name, etc. Make it match the variable name.

Sign in to comment.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!