Framer Sink 1: Difference between revisions
(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]] | ||
Given a stream of bits and access_code flags, assemble packets. | |||
; Input: stream of bytes from digital_correlate_access_code_bb | |||
; output: none. Pushes assembled packet into target queue | |||
The framer expects a fixed length header of 2 16-bit shorts containing the payload length, followed by the payload. If the 2 16-bit shorts are not identical, this packet is ignored. Better algs are welcome. | |||
The input data consists of bytes that have two bits used. Bit 0, the LSB, contains the data bit. Bit 1 if set, indicates that the corresponding bit is the the first bit of the packet. That is, this bit is the first one after the access code. | |||
== Parameters == | == Parameters == | ||
; | ; Targe message queue | ||
: | : The message queue where frames go. | ||
== Example Flowgraph == | == Example Flowgraph == |
Latest revision as of 14:26, 11 September 2019
Given a stream of bits and access_code flags, assemble packets.
- Input
- stream of bytes from digital_correlate_access_code_bb
- output
- none. Pushes assembled packet into target queue
The framer expects a fixed length header of 2 16-bit shorts containing the payload length, followed by the payload. If the 2 16-bit shorts are not identical, this packet is ignored. Better algs are welcome.
The input data consists of bytes that have two bits used. Bit 0, the LSB, contains the data bit. Bit 1 if set, indicates that the corresponding bit is the the first bit of the packet. That is, this bit is the first one after the access code.
Parameters
- Targe message queue
- The message queue where frames go.
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