Throttle: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:
A throttle block should be used if and only if your flowgraph includes no rate limiting block, which is typically hardware (e.g., an SDR, speaker, microphone). It is not intended nor effective at precisely controlling the rate of samples. That should be controlled by a source or sink tied to sample clock. E.g., a USRP or audio card.
A throttle block should be used if and only if your flowgraph includes no rate limiting block, which is typically hardware (e.g., an SDR, speaker, microphone). It is not intended nor effective at precisely controlling the rate of samples. That should be controlled by a source or sink tied to sample clock. E.g., a USRP or audio card.


The Throttle Block is typically attached directly to the output of a source block (e.g. [[Signal Source]]).
The Throttle Block is typically attached directly to the output of a non-hardware source block (e.g. [[Signal Source]]), in order to limit the rate at which that source block creates samples.


== Example Flowgraph ==
== Example Flowgraph ==

Revision as of 18:36, 14 May 2019

Throttle flow of samples such that the average rate does not exceed the specific rate (in samples per second).

A throttle block should be used if and only if your flowgraph includes no rate limiting block, which is typically hardware (e.g., an SDR, speaker, microphone). It is not intended nor effective at precisely controlling the rate of samples. That should be controlled by a source or sink tied to sample clock. E.g., a USRP or audio card.

The Throttle Block is typically attached directly to the output of a non-hardware source block (e.g. Signal Source), in order to limit the rate at which that source block creates samples.

Example Flowgraph

In this example flowgraph, if you remove the Throttle block the output will look the same, but your CPU will be at 100% and GNU Radio might crash.

Signal-source-ex.png