Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. Airprobe *.cfile decoding problem (Marek Pleskot)
2. Re: USRP E100 (Josh Blum)
3. Detecting a carrier (Gonzalo Flores De La Parra)
4. How to automaticly segment span when exceeds USRP limit
(Juan Daniel Fernandez Martinez)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 Feb 2013 22:34:47 +0100
From: Marek Pleskot <[email protected]>
To: [email protected]
Subject: [USRP-users] Airprobe *.cfile decoding problem
Message-ID:
<cap2gspk0_02xoprs5hk46u2uuzmqi5nv0g48ktv-yw+eogf...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Hi,
I'm completely fresh in this matter. I'm going to buy some ettus device but
before that I would like to test how the airprobe and gnuradio works.
I wanted to decode *.cfile using airprobe.
I have the following installation:
gnuradio: git version from 2013.02.12
airprobe: newest available git veriosn
OS: ubuntu 12.04
The file which I wanted to decode is the following:
http://reflextor.com/vf_call6_a725_d174_g5_Kc1EF00BAB3BAC7002.cfile.gz
I did my trials in two attempts:
1. First with ?usrp? set in gsm_scan.py
2. Second with ?uhd? set in gsm_scan.py
But unfortunately I've encountered problems:
1. [USRP attempt] First problem occurred when I'v trying to decode *.cfile
file using gsm_scan.py with the following setting: "from gnuradio import
usrp". Below is shown what I got in this attempt:
parallels@parallels-Parallels-Virtual-Platform:~/airprobe/gsm-tvoid/src/python$
./go.sh vf_call6_a725_d174_g5_Kc1EF00BAB3BAC7002.cfile
go.sh <file.cfile> [decim==112]
Traceback (most recent call last):
File "./gsm_scan.py", line 21, in <module>
from gnuradio import usrp
ImportError: cannot import name usrp
parallels@parallels-Parallels-Virtual-Platform:~/airprobe/gsm-tvoid/src/python$
2.[UHD attempt] After failure with first (USRP) attempt I decided to change
approach. Second problem occurred when I was trying to decode *.cfile file
using gsm_scan.py with the following setting: "from gnuradio import uhd".
Below is shown what I got in this attempt:
parallels@parallels-Parallels-Virtual-Platform:~/airprobe/gsm-tvoid/src/python$
./go.sh vf_call6_a725_d174_g5_Kc1EF00BAB3BAC7002.cfile
go.sh <file.cfile> [decim==112]
0: ce WARN: packet to short
HEX l2_data_out_Bbis:462 Format Bbis DATA
000: ce 46 3b 10 48 00 d0 03 - 00 50 01 29 3c b5 15 f7
001: 00 00 00 00 00 00 00
0: ce 110011-- Pseudo Length: 51
1: 46 0------- Direction: From originating site
1: 46 -100---- 4 TransactionID
1: 46 ----0110 Radio Resouce Management
2: 3b ???????? UNKNOWN. FIXME
2: 3b XXXXXXXX UNKNOWN DATA (14 bytes)
2: 3b YYYYYYYY REST OCTETS (21)
% offset = 0.0 clock = 64000000.0
Reading data from: vf_call6_a725_d174_g5_Kc1EF00BAB3BAC7002.cfile
>>> gr_fir_ccc: using SSE
>>> gr_fir_ccf: using SSE
(python:27589): Gtk-CRITICAL **: IA__gtk_window_resize: assertion `width >
0' failed
Segmentation fault (core dumped)
parallels@parallels-Parallels-Virtual-Platform:~/airprobe/gsm-tvoid/src/python$
Maybe somebody could help me resolve these problems, both for first(usrp)
and second (uhd) attempts.
I'll appreciate for help.
Thanks in advance
Best regards,
Marek
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130221/edb5970b/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 21 Feb 2013 19:31:24 -0600
From: Josh Blum <[email protected]>
To: "McKeever, Kenneth R." <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] USRP E100
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 02/21/2013 07:59 AM, McKeever, Kenneth R. wrote:
> Hi Josh,
>
> I replaced the file and the problem still remained. However, it seemed to
> take a bit longer before the sequence errors kicked in.
>
When we added timed command support to E100 in 3.5.* it put some extra
routing strain on the GPMC bus, and the FPGA tools weren't told enough
to get it right.
The image I gave you yesterday was with the second DSP removed and some
buffering to reduce routing issues.
This image is the full image, but built with additional timing
constraints. It has so far passed on my unit. I hope it helps you too.
http://files.ettus.com/binaries/e100-misc/usrp_e100_fpga_v2_timing.bin
This fix should be in the 3.5.2 patch release, and will get distributed
in opkg as well.
-josh
> Thanks,
> Ken
>
> On 2/20/13 10:12 PM, "Josh Blum" <[email protected]> wrote:
>
>>
>>
>> On 02/20/2013 06:37 AM, Leonardo S. Cardoso wrote:
>>> Hello all,
>>>
>>> I've been having "S" (sequence) problems trying to transmit with my USRP
>>> e100. I've recently updated all of my GNU Radio (3.6.2) and UHD
>>> (UHD_003.005.000) installation, with no luck...
>>>
>>> Looking for info on the web, I've seen this error reported before for
>>> earlier versions of the UHD driver. I've tried all the versions of the
>>> UHD
>>> driver I could find online with no luck. Is there something I'm missing?
>>>
>>> Can anyone help?
>>
>> Sorry guys. Its looks like there is an unconstrained path. Can you try
>> this fpga image in place of the one on your system in
>> /usr/share/uhd/images (this is where opkg puts it)
>>
>> http://files.ettus.com/binaries/e100-misc/usrp_e100_fpga_v2.bin
>>
>> -josh
>>
>>>
>>> Thank you.
>>>
>>> Best,
>>>
>>> Leonardo S. Cardoso
>>> [email protected]
>>>
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>
------------------------------
Message: 3
Date: Fri, 22 Feb 2013 09:57:35 -0600
From: Gonzalo Flores De La Parra <[email protected]>
To: [email protected]
Subject: [USRP-users] Detecting a carrier
Message-ID:
<CACWyxXCHT-vALUGXG=mZghUyh8P+M=6+vop0nldsjcskvjb...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi list..
I'm implementing a FHSS and i have some trouble detecting my carriers, i
was triying to use the example usrp_spectrum_sense.py to see how they do it
but i'm still in the same trouble, does anyone knows a good reference or
have an explanation about how the detect the level of interference o
carriers?
i can see mi carriers on the uhd_fft without any troubles, but how can i
extract that value? and use it for my demod process?
Thanks
--
Ing. Gonzalo Flores De La Parra
Electr?nica en Comunicaciones
Universidad Aut?noma Metropolitana
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130222/21b8fe2c/attachment-0001.html>
------------------------------
Message: 4
Date: Fri, 22 Feb 2013 16:52:48 +0000
From: Juan Daniel Fernandez Martinez <[email protected]>
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: [USRP-users] How to automaticly segment span when exceeds
USRP limit
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Hi everyone,
I need to implement a mechanism that splits the span when is bigger than the
USRP limit. While I was looking for an example I found
"usrp_spectrum_sense.py". This script is old, so I want to know if there is an
updated way of spliting the span, or if I can rely in this example.
Juan Daniel Fernandez M
________________________________
Este documento puede contener informaci?n privilegiada o confidencial. Por
tanto, usar esta informaci?n y sus anexos para prop?sitos ajenos a los de la
Universidad Icesi, divulgarla a personas a las cuales no se encuentre destinado
este correo o reproducirla total o parcialmente, se encuentra prohibido en
virtud de la legislaci?n vigente. La universidad no asumir? responsabilidad
sobre informaci?n, opiniones o criterios contenidos en este correo que no est?n
directamente relacionados con la Icesi. Si usted no es el destinatario
autorizado o por error recibe este mensaje, por favor informe al remitente y
posteriormente b?rrelo de su sistema sin conservar copia del mismo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130222/2fb852b9/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 30, Issue 22
******************************************
