Simulink assignment block writes garbage inside iterator subsystem.

I have an assignment block inside a complex model that I developed to run inside a time step. It should write a value to a 100-element array at the given index (zero-based). This is the expected behavior:

These are the assignment block parameters:

I then moved the model of which this was a part inside an iterated subsystem. Here is what I am getting:

The input U is being written to the array at the correct index, but the other elements of the array have been filled up with junk. (The "junk" in this case appears to be array values from MUCH earlier iterations before the array was re-initialized.) I note that this appears to only happen on this particular iteration; subsequent iterations overwrite the junk values at increasing indices as appropriate, but that is still leaving me with the value at the first index being incorrect.

Answer 1

[Leepakshi]

Hi Allan,

The array at the Y0 port should be constant if you want the Assignment block to reinitialize the output at every iteration. If the array is not constant, the block will accumulate changes, which may not be what you expect. Based on the understanding from your provided snippet.

If you share more about how <YArray> is connected, I might be able to provide you more specific answer.

Hope it helps!

[gowthaman muthuvel]

Hello,

I'm facing the same issue, but In my case it's updating all the elements in the array with same value. But I am expecting array element to be updated with respect to the for iterator index value.

Could you guide me through to avoid this issue ?