If an SDR receiver block or System object™ cannot keep up with the radio hardware, then the model or code is not processing data in real time. Burst mode enables you to buffer a set of contiguous samples without losing samples by setting the number of frames in a burst.
It is recommended that you enable burst mode when your application requires fresh samples from the hardware or guaranteed contiguous samples. To see if the received data is contiguous, enable the overflow indicator on the receiver block or object.
To determine if you need burst mode, see Detect Underruns and Overruns.
Use burst mode when your model loses samples because it cannot keep up with the real-time data received from the hardware. Burst mode enables you to buffer a minimum set of contiguous samples without losing samples. However, lost samples can still happen between bursts, especially with large burst sizes. If your model can keep up in real time, do not use burst mode. The default number of frames in a burst is 20.
The Pluto Receiver block has an Enable burst mode parameter. When you select this parameter, the block produces a set of contiguous frames without an overrun to the radio hardware. Enable burst mode to simulate models that cannot run in real time. Specify the amount of contiguous data using the Frames in burst parameter.
System object has an
EnableBurstMode property. When you set
this property to
true, the System object produces a set of contiguous frames without an overrun to the
radio hardware. This setting can help simulate models that cannot run in real
time. Specify the amount of contiguous data using the
EnableBurstMode: true NumFramesInBurst: 20
Burst mode requires a fresh set of samples from the hardware. Therefore, when you
call a receiver System object for the first time with burst mode enabled, the
overflow output argument is 1. Likewise, the first
time-step of a receiver block with burst mode enabled asserts the