ZMQ SUB Source: Difference between revisions
Jump to navigation
Jump to search
(clarify address) |
(add note about IP addresses) |
||
Line 9: | Line 9: | ||
; Address | ; Address | ||
: ZMQ socket address specifier. The format of the address is <code>tcp://*:port</code> where * should be 127.0.0.1 for localhost.<br> | : ZMQ socket address specifier. The format of the address is <code>tcp://*:port</code> where * should be 127.0.0.1 for localhost.<br> | ||
: <b>Note:</b> If the Source and Sink blocks are on two different computers on the same LAN, then the IP and port number of the Sink block must be specified on each end of that connection. For example, if the Sink is on IP 192.168.2.14:5678 and the Source is on IP 192.168.2.5, both Source and Sink blocks must specify the Sink IP and port (192.168.2.14:5678). | |||
; Timeout | ; Timeout | ||
: Receive timeout in milliseconds, default is 100ms. | : Receive timeout in milliseconds, default is 100ms. |
Revision as of 15:30, 26 March 2020
Receive messages on ZMQ SUB socket and source stream.
This block will connect to a ZMQ PUB socket, then produce all incoming messages as streaming output.
Parameters
(R): Run-time adjustable
- Address
- ZMQ socket address specifier. The format of the address is
tcp://*:port
where * should be 127.0.0.1 for localhost. - Note: If the Source and Sink blocks are on two different computers on the same LAN, then the IP and port number of the Sink block must be specified on each end of that connection. For example, if the Sink is on IP 192.168.2.14:5678 and the Source is on IP 192.168.2.5, both Source and Sink blocks must specify the Sink IP and port (192.168.2.14:5678).
- Timeout
- Receive timeout in milliseconds, default is 100ms.
- Pass Tags
- Whether source will look for and deserialize tags.
- Hign Watermark
- High Watermark to configure the socket to (-1 => zmq's default)
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