GNU Radio 3.6.5 C++ API
|
#include <packet_headergenerator_bb_impl.h>
Public Member Functions | |
packet_headergenerator_bb_impl (const packet_header_default::sptr &header_formatter, const std::string &len_tag_key) | |
~packet_headergenerator_bb_impl () | |
void | remove_length_tags (const std::vector< std::vector< gr_tag_t > > &tags) |
int | calculate_output_stream_length (const gr_vector_int &ninput_items) |
Calculate the number of output items. | |
int | work (int noutput_items, gr_vector_int &ninput_items, gr_vector_const_void_star &input_items, gr_vector_void_star &output_items) |
Just like gr_block::general_work, but makes sure the input is valid. |
gr::digital::packet_headergenerator_bb_impl::packet_headergenerator_bb_impl | ( | const packet_header_default::sptr & | header_formatter, |
const std::string & | len_tag_key | ||
) |
gr::digital::packet_headergenerator_bb_impl::~packet_headergenerator_bb_impl | ( | ) |
int gr::digital::packet_headergenerator_bb_impl::calculate_output_stream_length | ( | const gr_vector_int & | ninput_items | ) | [inline, virtual] |
Calculate the number of output items.
This is basically the inverse function to forecast(): Given a number of input items, it returns the maximum number of output items.
You most likely need to override this function, unless your block is a sync block or integer interpolator/decimator.
Reimplemented from gr_tagged_stream_block.
void gr::digital::packet_headergenerator_bb_impl::remove_length_tags | ( | const std::vector< std::vector< gr_tag_t > > & | tags | ) | [inline] |
int gr::digital::packet_headergenerator_bb_impl::work | ( | int | noutput_items, |
gr_vector_int & | ninput_items, | ||
gr_vector_const_void_star & | input_items, | ||
gr_vector_void_star & | output_items | ||
) | [virtual] |
Just like gr_block::general_work, but makes sure the input is valid.
The user must override work to define the signal processing code. Check the documentation for general_work() to see what happens here.
Like gr_sync_block, this calls consume() for you (it consumes ninput_items[i] items from the i-th port).
A note on tag propagation: The PDU length tags are handled by other functions, but all other tags are handled just as in any other gr_block
. So, most likely, you either set the tag propagation policy to TPP_DONT and handle the tag propagation manually, or you propagate tags through the scheduler and don't do anything here.
noutput_items | The size of the writable output buffer |
ninput_items | The exact size of the items on every input for this particular PDU. These will be consumed if a length tag key is provided! |
input_items | See gr_block |
output_items | See gr_block |
Implements gr_tagged_stream_block.