To clarify, the Python user interface was written by a collaborator,
Ralf Gommers. I didn't intend to steal credit for that.
On Thu, Mar 17, 2011 at 6:02 PM, Aviv Keshet wrote:
> I sent a message along these lines to the list about a year ago, but
> just wanted to give a brief upd
27;ve recently posted the latest incarnation to github,
https://github.com/akeshet/USRP-PID-Controller . If anybody has
interest in using this, or questions about it, please feel free to
contact me.
Aviv Keshet
___
Discuss-gnuradio mailing list
Discuss-gnu
et me know.
Thank you,
Aviv Keshet
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
It's been pointed out that I have committed the sin of using undefined jargon.
For the record, PID stands for Proportional Integral Derivative.
PID is a ubiquitous type of feedback controller, mostly thanks to being
conceptually quite simple. The input is an error signal (or a measurement and
setp
I've posted my verilog sources. Here is my modified top-level usrp module:
http://web.mit.edu/~akeshet/www/USRP_PID/usrp_std.v
The PID feedback module is here:
http://web.mit.edu/~akeshet/www/USRP_PID/PIDfeedback.v
One more accessory module for doing arithmetic is here:
http://web.mit.edu/~akeshe
I've got my verilog code for a USRP-based PID controller to the stage where it
is more or less coherent, and commented. I made some modifications to the top
level file, and added a few small .v modules.
What is the reigning protocol on this mailing list about .v file attachments?
Can I just attach
This email is not a question, but more of a comment.
I've been working for about a week on re-purposing a USRP as a digital feedback
controller, rather than a software radio. The USRP hardware platform provides
you with quite a good starting point for this sort of general purpose digital
signal pr
