Difference between revisions of "Energy Descramble"

From GNU Radio
Jump to: navigation, 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...")
 
Line 1: Line 1:
 
[[Category:Block Docs]]
 
[[Category:Block Docs]]
[[Category:Stub Docs]]
+
Energy descramble
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.
+
ETSI EN 300 744 - Clause 4.3.1.
 +
 
 +
; Input : Randomized MPEG-2 transport packets.
 +
; Output : MPEG-2 transport packets (including sync - 0x47).
 +
 
 +
We assume the first byte is a NSYNC.
 +
First sync in a row of 8 packets is reversed - 0xB8.  
 +
Block size is 188 bytes.
  
 
== Parameters ==
 
== Parameters ==
(''R''): <span class="plainlinks">[https://wiki.gnuradio.org/index.php/GNURadioCompanion#Variable_Controls ''Run-time adjustable'']</span>
 
 
; Param 1 (''R'')
 
: 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).
 
  
; Param 2
+
; Blocks : number of blocks.
: blah blah blah
 
  
 
== Example Flowgraph ==
 
== Example Flowgraph ==

Revision as of 15:08, 5 August 2019

Energy descramble

ETSI EN 300 744 - Clause 4.3.1.

Input 
Randomized MPEG-2 transport packets.
Output 
MPEG-2 transport packets (including sync - 0x47).

We assume the first byte is a NSYNC. First sync in a row of 8 packets is reversed - 0xB8. Block size is 188 bytes.

Parameters

Blocks 
number of blocks.

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