User:Muaddib: Difference between revisions
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
==Introduction: ''What does XMLRPC do in GNURadio and Why Should I Care?''== | ==Introduction: ''What does XMLRPC do in GNURadio and Why Should I Care?''== | ||
WHAT: XMLRPC is an '''XML'''-based '''R'''emote '''P'''rotocol '''C'''ontrol mechanism that does just that. A client with access to the server may use SET commands to change a parameter on the server or GET commands to obtain the value of a parameter on the server. | WHAT: XMLRPC is an '''XML'''-based '''R'''emote '''P'''rotocol '''C'''ontrol mechanism that does just that. A client with access to the server may use SET commands to change a parameter on the server or GET commands to obtain the value of a parameter on the server. | ||
WHY: In many cases, | WHY: In many cases, we have need to adjust the variables of a flowgraph at runtime.We usually do this with a QT GUI block. But what if you want to have the same control, but want to have the controller on a different computer? XMLRPC will allow you to run one flowgraph and control all of its variables from a second flowgraph. In fact, the second flowgraph doesn't even have to be on the same computer! | ||
* | |||
A few examples where this might come into play are: | |||
* Remote Narrow Band FM Receiver Station. You have a roof antenna with a short cable run going into a weatherproof box. In the box is an RTL-SDR dongle connected to a Raspberry PI 4 running the flowgraph from the Narrow band FM receiver tutorials. You can hear the audio, but would like to change the frequency at runtime. You'd also like to adjust the gain settings and squelch level while it's running. You can of course use an application to | |||
*control from inside, full visualization (good enough), low-data rate | *control from inside, full visualization (good enough), low-data rate | ||
Revision as of 01:08, 22 November 2021
Understanding XMLRPC Blocks
This tutorial presents the GNU Radio XMLRPC blocks. There are two blocks in this collection: XMLRPC Client and XMLRPC Server. Both blocks have IP address/port fields while the client block also has callback and variable fields. The blocks are simple implementations of the Python XMLRPC module and use a limited subset of the full features of XMLRPC.
To understand how GNURadio implements XMLRPC, look at the block documentation linked in the paragraph above.
To understand the XMLRPC protocol and Python implementation in detail, the reference links below are a good starting point.
Reference Links
http://xmlrpc.com/ https://docs.python.org/3.8/library/xmlrpc.html
Prerequisites
Introduction: What does XMLRPC do in GNURadio and Why Should I Care?
WHAT: XMLRPC is an XML-based Remote Protocol Control mechanism that does just that. A client with access to the server may use SET commands to change a parameter on the server or GET commands to obtain the value of a parameter on the server. WHY: In many cases, we have need to adjust the variables of a flowgraph at runtime.We usually do this with a QT GUI block. But what if you want to have the same control, but want to have the controller on a different computer? XMLRPC will allow you to run one flowgraph and control all of its variables from a second flowgraph. In fact, the second flowgraph doesn't even have to be on the same computer!
A few examples where this might come into play are:
- Remote Narrow Band FM Receiver Station. You have a roof antenna with a short cable run going into a weatherproof box. In the box is an RTL-SDR dongle connected to a Raspberry PI 4 running the flowgraph from the Narrow band FM receiver tutorials. You can hear the audio, but would like to change the frequency at runtime. You'd also like to adjust the gain settings and squelch level while it's running. You can of course use an application to
- control from inside, full visualization (good enough), low-data rate
<talk about XMLRPC server/client>
Simple Example
<run the source examples>
Headless DSP/GUI Control
- Run on localhost
- Run on separate machines
*<ssh -L vs. direct IP> *notes about streaming IQ vs Decimated I/Q *show data usage of I/Q vs. decimated I/Q