Understanding ZMQ Blocks: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
Line 38: Line 38:


=== Separate GR flowgraphs on Same Computer ===
=== Separate GR flowgraphs on Same Computer ===
When the ZMQ blocks are in separate flowgraphs but on the same computer, the IP address should be `127.0.0.1` for localhost. It has less overhead than a full IP.
These flowgraphs, using the PUB / SUB pair, are taken from [[Simulation_example:_AM_transmitter_and_receiver]].
[[File:AM_transmit_fg.png|800px]]
<hr>
[[File:AM_receive_fg.png|800px]]


=== Separate GR flowgraphs on Different Computers ===
=== Separate GR flowgraphs on Different Computers ===

Revision as of 13:34, 15 January 2021

This tutorial is under construction.

This tutorial presents the GNU Radio ZMQ blocks. It is a set of six Source Blocks and six Sink Blocks. The naming convention follows other source and sink blocks in that a source block provides data entering a GNU Radio flowgraph and a sink block sends data out of the flowgraph. It is a flowgraph-oriented perspective.

From the ZeroMQ website: "ZeroMQ (also known as ØMQ, 0MQ, or zmq) looks like an embeddable networking library but acts like a concurrency framework. It gives you sockets that carry atomic messages across various transports like in-process, inter-process, TCP, and multicast."

Prerequisites

Types of ZMQ Blocks

For GNU Radio, the two basic groups of ZMQ blocks are those which transport stream data, and those which transport messages. They are described below.

ZMQ blocks come in pairs:

  • PUB - SUB
  • PUSH - PULL
  • REQ - REP

The PUB, PUSH, and REP blocks are always sink blocks; the others are source blocks. Choosing which pair to use depends on your system architecture.

  • The PUB - SUB pair can be compared to broadcasting. The PUBlish sink sends out data which can be received by one or more SUBscribers.
  • The PUSH - PULL pair is a point to point link of equal peers.
  • The REQ - REP pair is a point to point link which operates in lock-step: one REQuest input gives one REPly output. This case changes the perspective somewhat in that the flowgraph is acting as a server for a remote client.

Data Blocks

ZMQ data blocks transport raw stream data; there is no formatting. The data type and the sample rate are determined by the flowgraph feeding the ZMQ Sink. Therefore the flowgraph or program receiving the data must know those parameters in order to interpret the data correctly.

Message Blocks

Unlike the generic ZeroMQ strings, GNU Radio ZMQ Message Blocks utilize Polymorphic_Types_(PMTs) to encode/decode the data. See also Message_Passing.

Using ZMQ Blocks

The cases described below explain the differences in the block addressing. To conform to port addressing defined by the Internet Assigned Numbers Authority (IANA), private ports can be assigned in the range 49152–65535.

Separate GR flowgraphs on Same Computer

When the ZMQ blocks are in separate flowgraphs but on the same computer, the IP address should be `127.0.0.1` for localhost. It has less overhead than a full IP.

These flowgraphs, using the PUB / SUB pair, are taken from Simulation_example:_AM_transmitter_and_receiver.

AM transmit fg.png


AM receive fg.png

Separate GR flowgraphs on Different Computers

Python Program as Destination of ZMQ Block

Python Program as Source to ZMQ Block