Message Debug: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:
The message debug block is used to capture and print or store messages as they are received. Any block that generates a message may connect that message port to one or more of the three message input ports of this debug block.
The message debug block is used to capture and print or store messages as they are received. Any block that generates a message may connect that message port to one or more of the three message input ports of this debug block.


Please add information on the specificities of the various input message ports.
The message ports are:
 
* print: prints the message directly to standard out.
* store: stores the message in an internal vector. May be access using the get_message function.
* print_pdu: specifically designed to handle formatted PDUs (see pdu.h).
 


== Parameters ==
== Parameters ==

Revision as of 13:15, 6 September 2019

Debug block for the message passing system.

The message debug block is used to capture and print or store messages as they are received. Any block that generates a message may connect that message port to one or more of the three message input ports of this debug block.

The message ports are:

  • print: prints the message directly to standard out.
  • store: stores the message in an internal vector. May be access using the get_message function.
  • print_pdu: specifically designed to handle formatted PDUs (see pdu.h).


Parameters

None

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