Python Block Message Passing: Difference between revisions
Jump to navigation
Jump to search
Mattcarrick (talk | contribs) No edit summary |
Mattcarrick (talk | contribs) No edit summary |
||
Line 6: | Line 6: | ||
== Message Passing Overview == | == Message Passing Overview == | ||
Messages are an asynchronous way to send information between blocks. There is no sample-clock based guarantee when they will arrive and messages are not associated with a specific sample like a tag. | Messages are an asynchronous way to send information between blocks. Messages are good at conveying control data, maintaining a consistent state across blocks and providing some forms of non-data feedback to blocks in a flowgraph. There is no sample-clock based guarantee when they will arrive and messages are not associated with a specific sample like a tag. | ||
== PMT == | == PMT == |
Revision as of 21:00, 21 January 2022
The previous tutorial, Creating Your First Block, demonstrates how to create a Python block using the Embedded Python Block. The next tutorial, Low Pass Filter Example, demonstrates how to use filtering blocks in GNU Radio.
Message Passing Overview
Messages are an asynchronous way to send information between blocks. Messages are good at conveying control data, maintaining a consistent state across blocks and providing some forms of non-data feedback to blocks in a flowgraph. There is no sample-clock based guarantee when they will arrive and messages are not associated with a specific sample like a tag.
PMT
describe basic PMT types
link against other PMT pages
- message ports to have to be connected like stream/vector ports
The next tutorial, Low Pass Filter Example, demonstrates how to use filtering blocks in GNU Radio.