The timing of Buffers are off.

The output timings of Buffers when the Buffer has to cut the incoming message are off. Here is a Minimal Working Example. The out.simout1.Time should be [0 160] not [0 133.3333].

Answer 1

[Yuvraj Singh]

Hi Lóránt,

I understand you have a Simulink model and one of the outputs of “To Workspace” Block gives an unexpected result according to you.

Simulink automatically computes the appropriate sample rates for the blocks connected to the source blocks. You may notice “out.simout1” has a sample rate/period of 133.3333 . So, the block is sampled at the multiples of 133.3333 second and simulation stops at 160. Hence 133.3333 second is the last time it was sampled during the 160 second simulation.

Follow the link below to better understand sample rates and how to inspect them.

Inspect Sample and Frame Rates in Simulink - MATLAB & Simulink (mathworks.com)

I hope it helps you.

-Yuvraj

Answer 2

[Lóránt Farkas]

The Matlab computes the Timing automatically wrong. As you see on the upper path the padding takes 0 time to be done. The problem is on the lower path. The timing after the first buffer is 0,80,160, and the next buffer output timing is 0, 133. Why? Why the buffer did not send the signal at time 80 if the buffer was filled with enough data? Why send at 133.33 if acually no signal happend at that time? (See, that signal was generated at every integer time.)