Josh,
I tried your application on Fedora Core 3.
I get the following error.
Not sure if it is something easy to fix though.
Any suggestions are welcome...
Achilleas
PS: the screenshots look great!
---
Traceback (most recent call last):
File ./Main.py, line 7, in ?
import
Josh,
I commented out the part you suggested and then it gave me the following
message:
---
Traceback (most recent call last):
File ./Main.py, line 7, in ?
import ActionHandler
File /home/anastas/grc_0.50/src/ActionHandler.py, line 14, in ?
import Dialogs
File
Thanks for pointing out all theses raw files
for testing the usrp_tv_rcv.py application.
I tried a couple of them and they work fine.
Now I have the following question:
Why is it that the video shown on sdl moving
slowly to the right?
The fact that there is no vertical or horizontal
by a
drift/jitter of the ADC on the order of 25ppm
Is this within the drift/jitter specs of the ADC?
Thanks
Achilleas
On Tue, 23 Jan 2007, Anastasopoulos Achilleas wrote:
Thanks for pointing out all theses raw files
for testing the usrp_tv_rcv.py application.
I tried a couple of them
Josh,
I imported some blocks from gr-trellis on GRC.
However there seems to be a problem.
The graph does not run and exits with something like:
...
flow graph save
SRC_DIR: /net/ernesto/home/anastas/grc_mine/src
DATA_DIR: /net/ernesto/home/anastas/grc_mine/data
FILE_PATH:
Tim,
If the number of additional bits is not significantly
bigger than the fixed packet length (in your example 200),
then you can instantiate the VA with the MAXIMUM expected
length (eg, K=200+10). For this to work you have to
1) put a block before it that appends 0's (or something else)
in
Brian,
Yes it can!
You need to set a decision delay D and then it would operate in a
fixed-delay mode, ie, it would spit out a decision at every time instance
with a delay of D compared to the input sample.
The survivor matrix (of size DxS) will need to be updated at every
time instance in
Hi there,
I am trying to install gnuradio in an environment where I do not have
root priviledges, so
everything has to go in my user space.
I went through the regular cycle using the ./configure
--prefix=/n/wellington/x/anastas/local
so that everything is installed under my ~/local
I am running it on a Fedora Core 5.
This was the latest trunk.
Thanks
Achilleas
On Wed, 21 Feb 2007, Eric Blossom wrote:
On Wed, Feb 21, 2007 at 05:59:59PM -0500, Achilleas Anastasopoulos wrote:
Hi there,
I am trying to install gnuradio in an environment where I do not have
root
Hi,
I am trying to understand how the message source works
and how I can use it from within my python code.
So I wrote a simple script with a message source and a null sink.
I wanted the following behavior:
every time I press a button on my keybord to send a constant message in
the queue and
Dan,
thanks for the info you provided; it was ver helpful!
I think I got the basic understanding of the message_source/sink.
I wrote my first toy code based on this:
The Tx queues 100 packets and the Rx waits until
it receives everything (broken into different number of packets)
The Rx
Hi,
I am running a simple graph in GRC-0.65 with complex USRP as source
(with TVRX at the B side) and a complex FFT as a sink.
What I see is not expected: I see the FFT of a real signal
(symmetric around 0).
When I run the python example usrp_fft.py I get
the expected result.
./usrp_fft.py -RB
Hi,
I noticed that the Gaussian pulse is convolved with a rectangular window
in the GMSK modulator. Why is that so?
Thanks
Achilleas
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
, Matt Ettus wrote:
Anastasopoulos Achilleas wrote:
Hi,
I noticed that the Gaussian pulse is convolved with a rectangular window
in the GMSK modulator. Why is that so?
The pulse is convolved with a rectangular window because the incoming data is
not.
For example, if you wanted to send 1011
Dear all,
I received the USRP, followed the WiKi instruction and
it seems to be working since I get meaningful result when I run
test_usrp_standard_tx and test_usrp_standard_rx.
I have also updated my gnuradio installation using
tarballs 2.5
However I have problems running any of the python
I know this is not the right list for this, but
I wonder if anyone else had the same experience.
In python (ver 2.3) when I do
import wx
it loads the package without complaining.
Then when I do
help(wx)
it gives error messages and a segmentaion fault.
All errors relate to Glib and Gtk.
Has
Dear all,
After updating my FC3 and reinstalling the
latest tarballs I think I have a distribution with a
working USRP module (with Basic Rx,Tx and 4937 daughterboards).
Thanks for the comments/suggestions.
However there are still some issues that I have not resolved:
benchmark_usb.py works
Is this comment relevant for the Tx only
or for both TX and Rx ?
Just one minor correction from what I said before. The way you show the
multipliers and the NCO is not quite correct. It is doing a full
complex
multiplication. The CORDIC does the NCO and the multiplication
together.
Your
Now that I understand how the basic Tx and usrp_siggen works,
I am trying to get a handle on the basic Rx and the usrp_fft.py script.
Here are a couple of observations/questions:
1) If nothing is connected to the basic Rx I get a strong DC term
on the fft display. Where is this coming from?
I apologize for the confusion:
I meant the file
tvrx_wfm_rcv_gui.py
Achilleas
According to usrp_wfm_gui.py the correct MUX seting
for listening to
FM is0x f0 f0 f0 f2.
Could you please point me to this file ? Im not able
to locate it in my code. Or did you mean
wfm_rcv_gui.py ?
Javs
Are the connections from the daughterboards to the
ADC's
hardwired in the USRP the way it is shown in the
figure,
ie, RX-A to ADC-0, RX-B to ADC-1 and the IF output
of the
TV-RX to both ADC-2 and ADC-3 ?
I think this is the default wiring:
RxA (Jumper 19 )-ADC 0
RxB (Jumper 18 )-ADC 1
Guys, I remember someone gave me an answer to
a similar question in the past regarding the Digital upconverter
in the TX path that is implemented inside the ADC chip.
I have a similar question for the DDC in the RX path which is implemented
in the FPGA:
On the receiver path, the DDCs perform
Oliver,
You are right:
Trellis implementation supports multi-dimensional constellations etc
(through the metric calculation block abstraction, etc), however,
in the examples and the supporting fsm_utils.py files
I have not included support for GMSK, and the automatic
generation of lookup tables
it? Is there any published
literature on this that I could base it on?
Kind Regards,
Toby
Anastasopoulos Achilleas wrote:
Oliver,
You are right:
Trellis implementation supports multi-dimensional constellations etc
(through the metric calculation block abstraction, etc), however,
in the examples
From your reply I think you are referring to problem 1B.
I am indeed.
This is great. I did not know you had checked in the siso code in
gr_trellis. I am now more anxious to go study it more carefully. I am glad
I commented.
As a side note, this algorithm is the basis of all
For an input sequence of length N and a filter with L taps
the output sequence should have N + L-1 samples.
It seems that the GnuRadio implementation produces exactly N
samples, ie, it does not generate the L-1 tail samples.
I guess the reason is that there is no way of knowing
when the input
26 matches
Mail list logo
