Real time vector saving

Dear all,

I am using xPC with R2014b version and in my model I have a state machine that in one state there is a function with two inputs coming from 2 sensors. I want to save all the values of the inputs into 2 vectors (eg. 10,1) that I will use in an other state.

Until now I used a persistent variable for the index for the vectors. My question is: how is it possible to save the 2 vectors and use them in the next state?

Bests, Stergios

[Geoff Hayes]

Stergios - are you using Simulink?

[Stergios Verros]

Hi Geoff,

Yes I am using simulink.

[Guillaume]

So I've added Simulink under Products

[Stergios Verros]

Thank you!

[Stergios Verros]

To make it more clear, I want to make a polyfit from the 2 vectors, save the coefficients and then use them into an other state!

Answer 1

[Gareth Thomas]

If I understand you correctly you have a stateflow chart, in which one state you are calculating some parameters for a polyfit and you want to send them to another state based on a particular condition.

Have you looked into Events in Stateflow? One can broadcast events with data to another states.

MathWorks Documentation

[Stergios Verros]

Thanks for that but my main question is one step before that.

I try to save the values in 2 vectors (1000x1) and polyfit in every cyrcle and at the last circle (before the condition) to save the coefficients. I use persistent variables but the xPC keeps giving a CPU overload. Would it be helpful to paste the code here?

Answer 2

[Brandon Eidson]

Hey Stergios,

One way to save variables in one state that can be used in another state is by using the "Data Store Memory" block and its associated blocks. I have provided the link to its documentation below as well as a link to information on how to use this block in Stateflow.

http://www.mathworks.com/help/releases/R2016a/simulink/slref/datastorememory.html

https://www.mathworks.com/help/stateflow/ug/sharing-global-data-with-multiple-charts.html

Also, if you are using C for your Stateflow Action Language, note that the scope of variables can be handled differently. A list of some of the differences is found at the link below.

http://www.mathworks.com/help/stateflow/ug/differences-between-matlab-and-stateflow-action-language.html