Why Integrator with Wrapped State don't wrap the lower limit? (R2018b)

Question

Rubem Pacelli 2020-4-2

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/514916-why-integrator-with-wrapped-state-don-t-wrap-the-lower-limit-r2018b

评论： Fangjun Jiang 2020-4-3

On simulink we have a block called "Integrator with Wrapped State". This behavior looks pretty simple. This image (from the help doc) show whats the expected output (depicted by "Wrapped state integrator"):

In the parameters configuration, I set the values as follow:

Hence, I expected a output between 0 and 4. However, I got this output:

Why Integrator with Wrapped State don't wrap the lower(=0) limit?

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

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

Answer 1

Fangjun Jiang 2020-4-2

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/514916-why-integrator-with-wrapped-state-don-t-wrap-the-lower-limit-r2018b#answer_423645

It should not be like that. Create a simple new model to verify it. Grab a Sine Wave block, change the amplitude to be 3, Connect it to the Wrapped State block, change the upper value to be 4 and sample time to be 0, run simulation for 20 seconds, you should see it limits at both ends.

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

Rubem Pacelli 2020-4-3

Well Fangjun Jiang, I did it. The following picture shows what I changed in the Linked Block:

It solved my problem partially... When I run my system on sampled-based mode, the output matches the continuous-time output. It turns out that my system is a little bit complicated as it operates on frame-based. The following picture your example operating on continuous-time; discrete-time and sample-based; and discrete-time and frame-based (200 samples per frame).

And the outputs are, respectively

As you see, the last picture (discrete-time and frame-based) is a complete mess... I don't know what's exactly happens there. And I also don't know how can it keep in touch with the support team of Matlab (I never did it)

Fangjun Jiang 2020-4-3

Not sure about the issue wrt frame-based. You can contact the Mathworks tech support online from your Mathworks account, or call them up.

Your reset value is valid only when lower value is 0. Thinking of an example when upper is 5 and lower is 3.
The same block in R2019b seems to have fixed the problem. It contains the OR logic you implemented and a different way for reset value.

请先登录，再进行评论。