Packet Header Parser: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
In a sense, this is the inverse block to [[Packet Header Generator]]. The difference is, the parsed header is not output as a stream, but as a PMT dictionary, which is published to message port with the id "header_data". | In a sense, this is the inverse block to [[Packet Header Generator]]. The difference is, the parsed header is not output as a stream, but as a PMT dictionary, which is published to message port with the id "header_data". | ||
The dictionary consists of the tags created by the header formatter object. | The dictionary consists of the tags created by the header formatter object, as well as the tags already present at the input of this block. | ||
Note that if several tags (created and already present) have the same key (name), only one, the last, will be output. And that may cause conflicts that are hard to investigate. | |||
== Parameters == | == Parameters == | ||
; Formatter Object | ; Formatter Object | ||
: Header object. This should be the same as used for [[Packet Header Generator]]. | : Header object. This should be the same as used for [[Packet Header Generator]] on the transmitter side. | ||
== Example Flowgraph == | == Example Flowgraph == | ||
Latest revision as of 13:54, 8 August 2023
Post header metadata as a PMT. In a sense, this is the inverse block to Packet Header Generator. The difference is, the parsed header is not output as a stream, but as a PMT dictionary, which is published to message port with the id "header_data".
The dictionary consists of the tags created by the header formatter object, as well as the tags already present at the input of this block. Note that if several tags (created and already present) have the same key (name), only one, the last, will be output. And that may cause conflicts that are hard to investigate.
Parameters
- Formatter Object
- Header object. This should be the same as used for Packet Header Generator on the transmitter side.
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
- [1]
- Header files
- [2]
- Public header files
- [3]
- Block definition
- [4]