Protocol Formatter: Difference between revisions
No edit summary |
|||
Line 16: | Line 16: | ||
== Example Flowgraph == | == Example Flowgraph == | ||
This flowgraph can be found at [https://github.com/gnuradio/gnuradio/blob/master/gr-digital/examples/ofdm/tx_ofdm.grc]. | |||
[[File:Tx_ofdm_fg.png|800px]] | |||
== Source Files == | == Source Files == |
Revision as of 03:03, 30 November 2020
Uses a header format object to create a header from a tagged stream packet.
This block takes in tagged stream and creates a header, generally for MAC-level processing. Each received tagged stream is assumed to be its own frame, so any fragmentation would be done upstream in or before the flowgraph.
The header that is created and transmitted from this block. The payload should then be sent as a parallel tagged stream to be muxed together later. The header is based entirely on the object, which is an object derived from the header_format_base class. All of these packet header format objects operate the same: they take in the payload data as well as possible extra metadata info about the PDU; the format object then returns the output and metadata info. This block then transmits the header vector and attaches and metadata as tags at the start of the header.
Parameters
- Format Obj.
- The format object to use when reading the header. This block uses a format object derived from a header_format_base class.
- Length tat name
- The tagged stream length key.
Example Flowgraph
This flowgraph can be found at [1].
Source Files
- C++ files
- [2]
- Header files
- [3]
- Public header files
- [4]
- Block definition
- [5]