CFO Model: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:Block Docs Category:Stub Docs This is the template for the "Page-per-block Docs". This first section should describe what the block...") |
No edit summary |
||
Line 1: | Line 1: | ||
[[Category:Block Docs]] | [[Category:Block Docs]] | ||
This block implements a carrier frequency offset model that can be used to simulate carrier frequency drift typically from mixer LO drift on either transmit or receive hardware. | |||
This | |||
A clipped gaussian random walk process is used. | |||
== Parameters == | == Parameters == | ||
(''R''): <span class="plainlinks">[https://wiki.gnuradio.org/index.php/GNURadioCompanion#Variable_Controls ''Run-time adjustable'']</span> | (''R''): <span class="plainlinks">[https://wiki.gnuradio.org/index.php/GNURadioCompanion#Variable_Controls ''Run-time adjustable'']</span> | ||
; | ; Sample rate Hz (''R''): Sample rate of the input signal in Hz | ||
: | |||
; | ; CFO standard deviation (Hz per sample) (''R''): Desired standard deviation of the random walk process every sample in Hz | ||
: | |||
; Max CFO bound Hz (''R''): Maximum carrier frequency deviation in Hz. | |||
; Seed : A random number generator seed for the noise source. | |||
== Example Flowgraph == | == Example Flowgraph == |
Revision as of 11:32, 1 August 2019
This block implements a carrier frequency offset model that can be used to simulate carrier frequency drift typically from mixer LO drift on either transmit or receive hardware.
A clipped gaussian random walk process is used.
Parameters
(R): Run-time adjustable
- Sample rate Hz (R)
- Sample rate of the input signal in Hz
- CFO standard deviation (Hz per sample) (R)
- Desired standard deviation of the random walk process every sample in Hz
- Max CFO bound Hz (R)
- Maximum carrier frequency deviation in Hz.
- Seed
- A random number generator seed for the noise source.
Example Flowgraph
Insert description of flowgraph here, then show a screenshot of the flowgraph and the output if there is an interesting GUI. Currently we have no standard method of uploading the actual flowgraph to the wiki or git repo, unfortunately. The plan is to have an example flowgraph showing how the block might be used, for every block, and the flowgraphs will live in the git repo.
Source Files
- C++ files
- TODO
- Header files
- TODO
- Public header files
- TODO
- Block definition
- TODO