I have been transmitting random data using benchmark_tx and benchmark_rx. two
things happen
1. the first transmission will be successful. If i stop the command and
retry it immediately nothing happens. I have to unplug and plug the ursp
back again and it works. Any ideas as to why that happens an
John -
It is my understanding that the current FPGA image used for OpenBTS
will fail on the transmit side if the FPGA clock is slower than the
USB clock. The USB clock is 48 MHz.
Also, the GSM symbol clock is derived from 13 MHz, so if you use a
multiple-of-13 clock, you can simplify a l
Im not sure what this has to do with gr pager...
Did you follow the build guide? Your PYTHONPATH is probably not set. See
http://gnuradio.org/redmine/wiki/gnuradio/ReportingErrors
-Josh
On 01/16/2010 02:19 PM, sandeep mishra wrote:
Hi,
I have installed GNU radio in ubantu9.1 (karmic), but wh
Hi all,
I've seen posts about folks providing an external clock of 44 MHz to the
USRP, and with a few software tweaks, getting it to work. I'm wondering if
there is a floor as to how low this clock be reduced without causing
problems. I know some A/D converters have minimum sample rates, but the
Mattias Kjellsson wrote:
amarnath alapati wrote:
hi folks,
I am using BENCHMARK_TX.PY, BENCHMARK_RX.PY to test the
transmission and reception of signals. I have doubts regarding the
outpu that is appearing on the screen.
>>> gr_fir_fff: using SSE
socket(PF_PACKET, SOCK_RAW, htons(0x
Hi,
I have installed GNU radio in ubantu9.1 (karmic), but while i am running any
python program i use to get error "import error no gnuradio module" i
searched over internet but there is no fruitful result, I performed every
step as per mentioned over website on gnuradio ubantu installation, while
Unfortunately, I never got around to tracking down the problem - I
just disabled the build.
Sorry I have nothing helpful to add =(
Cheers,
Ben
On Sat, Jan 16, 2010 at 1:54 AM, Johnathan Corgan
wrote:
> On Fri, Jan 15, 2010 at 17:44, Veljko Pejovic wrote:
>
>> I got the same error:
>>
>> make[4
On Sat, 2010-01-16 at 10:57 -0800, Matt Ettus wrote:
> On 01/16/2010 10:46 AM, Eric Schneider wrote:
> > Just out of curiosity, was there a design decision made to not use the
> > DAC PGAs to adjust Tx gain?
>
>
> The issue is that changing the DAC PGA not only changes the differential
> amplitu
On 01/16/2010 09:03 AM, Tom Gross wrote:
Hi Matt,
I'll try hooking up my ttl line on Monday (I have done that but not
with our current configuration, so far only when I was playing around
with building custom firmware).
Here's the official description of what we are doing (I hope this helps!):
On 01/16/2010 10:46 AM, Eric Schneider wrote:
Just out of curiosity, was there a design decision made to not use the
DAC PGAs to adjust Tx gain?
The issue is that changing the DAC PGA not only changes the differential
amplitude (which is what you want), it also changes the DC bias point
(i.e
Just out of curiosity, was there a design decision made to not use the
DAC PGAs to adjust Tx gain?
On Sat, 2010-01-16 at 09:08 -0800, Josh Blum wrote:
> On 01/16/2010 01:36 AM, amarnath alapati wrote:
> > hi friends,
> > When I tried to print the Transmitter gain range by the following
> > com
On Fri, Jan 15, 2010 at 18:21, Yan Nie wrote:
> RuntimeError: can't open usrp
This is usually a cabling issue (easy to check) or a permissions issue
(more likely). The user you are running as needs to have rw
permission to the device node created for the USRP. This is done
automatically when i
On Thu, Jan 14, 2010 at 10:52, Yan Nie wrote:
> I'm trying build my own fpga bitstream by modifying usrp_sounder project.
> I've saveral questions on the module master_control.
The master_control module is actually a common file with the standard
build, not specific to the usrp_sounder image.
>
On Sat, Jan 16, 2010 at 03:06, amarnath_iitm wrote:
> Even I am facing the problem of packet loss.
> I have tried with all the packet sizes.
> Can u suggest what is the packet size to be used?
http://gnuradio.org/redmine/wiki/1/ReportingErrors
Johnathan
___
On 01/16/2010 01:36 AM, amarnath alapati wrote:
hi friends,
When I tried to print the Transmitter gain range by the following commands,
The output is as followss,
[r...@localhost digital]# python benchmark_tx.py -f 2412M
--show-tx-gain-range
gr_fir_fff: using SSE
Tx Gain Range: minimum = 0,
Hi Matt,
I'll try hooking up my ttl line on Monday (I have done that but not
with our current configuration, so far only when I was playing around
with building custom firmware).
Here's the official description of what we are doing (I hope this helps!):
We have two USRP2s sharing common clocks v
1)
Run:
sudo chmod u+s /usr/local/bin/usrp2_socket_opener
2) As root edit /etc/security/limits.conf and add the line:
@usrp - rtprio 50
If your not already in the USRP group add your user with:
useradd -G usrp username
(This will create the group if it doesn't already exist)
--
Tim
On Sa
amarnath alapati wrote:
hi folks,
I am using BENCHMARK_TX.PY, BENCHMARK_RX.PY to test the
transmission and reception of signals. I have doubts regarding the
outpu that is appearing on the screen.
>>> gr_fir_fff: using SSE
socket(PF_PACKET, SOCK_RAW, htons(0xBEEF)): Operation not perm
Whenever this comes up, I need to do
sudo make uninstall
for whatever reason. Something that is in /usr/local/lib/gnuradio ...
etc. gets in the way of the build. It is just too easy to do the
uninstall for me to take time to figure it out.
Bob
On 1/15/2010 8:54 PM, Johnathan Corgan wrot
Even I am facing the problem of packet loss.
I have tried with all the packet sizes.
Can u suggest what is the packet size to be used?
--
View this message in context:
http://old.nabble.com/RFX2400%2BUSRP-buffers-tp19415046p27188383.html
Sent from the GnuRadio mailing list archive at Nabb
hi friends,
When I tried to print the Transmitter gain range by the following commands,
The output is as followss,
[r...@localhost digital]# python benchmark_tx.py -f 2412M
--show-tx-gain-range
>>> gr_fir_fff: using SSE
Tx Gain Range: minimum = 0, maximum = 0, step size = 1
1) Why is the gain Mi
21 matches
Mail list logo
