Editing Tagged Stream Blocks
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
traditional GNU Radio blocks, if we stream N bytes into a block, there's no way of | traditional GNU Radio blocks, if we stream N bytes into a block, there's no way of | ||
knowing the packet boundary. This might be relevant: Perhaps the modulator has to | knowing the packet boundary. This might be relevant: Perhaps the modulator has to | ||
− | prepend a | + | prepend a synchronisation word before every packet, or append a CRC. So while some |
blocks don't care about packet boundaries, other blocks do: These are tagged | blocks don't care about packet boundaries, other blocks do: These are tagged | ||
stream blocks. | stream blocks. | ||
These blocks are different from all the other GNU Radio block types (gr::block, | These blocks are different from all the other GNU Radio block types (gr::block, | ||
− | gr::sync_block etc.) in that they are driven by the input: The PDU length tag tells the block how to operate, whereas other blocks are output-driven (the scheduler tries to fill up the output buffer | + | gr::sync_block etc.) in that they are driven by the input: The PDU length tag tells the block how to operate, whereas other blocks are output-driven (the scheduler tries to fill up the output buffer are much as possible). |
=== How do they work? === | === How do they work? === |