Bit Interleaver: Difference between revisions

From GNU Radio
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]]
[[Category:Stub Docs]]
Bit interleaves DVB-T2 FEC baseband frames.
This is the template for the [[:Category:Block_Docs|"Page-per-block Docs"]].  This first section should describe what the block does and how to use it, using however many paragraphs necessary.  Note that the title of the wiki page should match the block's name in GRC, i.e. the one defined in the block's .grc file.  Look at the [[FFT]] Block for a good example.


As this is a basic template, it's also in the [[:Category:Stub_Docs|"Stub Docs category"]]. Please improve it.
Input: Normal or short FEC baseband frames with appended LPDC (LDPCFEC).
 
Output: Bit interleaved (with column twist and bit to cell word de-multiplexed) cells.


== Parameters ==
== Parameters ==
(''R''): <span class="plainlinks">[https://wiki.gnuradio.org/index.php/GNURadioCompanion#Variable_Controls ''Run-time adjustable'']</span>
; FEC Frame Size
: FEC frame size (normal or short).


; Param 1 (''R'')
; Code Rate
: Description of parameter, provide any tips or recommended values.  Note that the name of the parameter above should match the param's label that shows up in grc (e.g. Sample Rate).
: FEC code rate.


; Param 2
; Constellation
: blah blah blah
: DVB-T2 constellation.


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

Revision as of 03:58, 27 July 2019

Bit interleaves DVB-T2 FEC baseband frames.

Input: Normal or short FEC baseband frames with appended LPDC (LDPCFEC).

Output: Bit interleaved (with column twist and bit to cell word de-multiplexed) cells.

Parameters

FEC Frame Size
FEC frame size (normal or short).
Code Rate
FEC code rate.
Constellation
DVB-T2 constellation.

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