Unusual behaviour in model outputs recorded by SystemTest - a value for every outport, on every outport.

Question

James 2011-9-8

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/15381-unusual-behaviour-in-model-outputs-recorded-by-systemtest-a-value-for-every-outport-on-every-outp

I have a model in SystemTest with a number of inports and outports.

With each timestep, the values for all the inputs are read in from an Excel spreadsheet.

Normally in my experience, for every timestep, one value for every outport is recorded.

What I am finding for a particular SystemTest is that many values are recorded for every outport, for every timestep. The number of values appears to correspond to the number of outports, so that if there is 5 outports, on every timestep all 5 outports have a 1x5 double each recorded as the result.

It's a discrete fixed step solver of sample time 0.01 - this corresponds to the size of each timestep in the spreadsheet of data.

Any ideas as to how to sort this or what might be causing the behaviour? Many thanks

4 个评论
显示 2更早的评论隐藏 2更早的评论

Bart Addis 2011-9-13

Does the model behave this way without SystemTest? In other words, if you connect a scope to the output signals, what do you see?

James 2011-9-14

Using a scope it displays precisely what's expected.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Fangjun Jiang 2011-9-8

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/15381-unusual-behaviour-in-model-outputs-recorded-by-systemtest-a-value-for-every-outport-on-every-outp#answer_20914

It looks like the signal associated with each of your Outport has become a vector signal. Click menu Format->Port/Signal Displays->Signal Dimensions and Wide Nonscalar lines to check it out. It is probably inherited from the Inport, which means the data inport from the Excel spreadsheet is not in the right format.

2 个评论
显示无隐藏无

James 2011-9-14

There could be something in this actually. Eventually I deleted all inports and outports, and redid them. This fixed it.

I can only assume the first outport was connected when I was still configuring inputs and it inherited some settings, that somehow were copied to every other outport when I cloned the outport for the other signals. Why it didn't update to what it should inherit, I don't know, but it's the best that I can understand.

Fangjun Jiang 2011-9-14

That is a good point. In our organization, we recommended to drag and drop every block from the library, not to duplicate from the model, unless you are 100% sure that is what you want. There are so many parameters now for every block. You don't know what is different from the default setting.

请先登录，再进行评论。