Message Debug: Difference between revisions
Jump to navigation
Jump to search
m (→Source Files: Updated source links) |
mNo edit summary |
||
| Line 8: | Line 8: | ||
* print: prints the message directly to standard out. | * print: prints the message directly to standard out. | ||
* store: stores the message in an internal vector. May be access using the get_message function. | * 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). | * print_pdu: specifically designed to handle formatted PDUs (see pdu.h). Discards messages that aren't PDU pairs (or are null). | ||
== Parameters == | == Parameters == | ||
Revision as of 22:35, 19 November 2021
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). Discards messages that aren't PDU pairs (or are null).
Parameters
None
Example Flowgraph
In this example, a Message Strobe block sends the string "Demo" once per second. It is displayed on the user terminal by the Message Debug block.
Source Files
- C++ files
- [1]
- Header files
- [2]
- Public header files
- [3]
- Block definition
- [4]