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. Re: ERROR_CODE_BAD_PACKET after resuming a flowgraph
(Jared Dulmage via USRP-users)
2. Re: ERROR_CODE_BAD_PACKET after resuming a flowgraph
(Marcus D. Leech via USRP-users)
3. Re: Sampling + Clock rates (Was: (no subject))
(jason sam via USRP-users)
4. Re: Sampling + Clock rates (Was: (no subject))
(Mike Jameson via USRP-users)
5. Re: Sampling + Clock rates (Was: (no subject))
(jason sam via USRP-users)
6. Re: Can't get a signal from USRP B200
(Michal Jakubiak via USRP-users)
7. Underrun using USRP B210 (jason sam via USRP-users)
8. Re: Underrun using USRP B210 (Martin Braun via USRP-users)
9. Re: Underrun using USRP B210 (jason sam via USRP-users)
10. Re: Can't get a signal from USRP B200
(Claudio Cicconetti via USRP-users)
11. Re: B210 channel assignment (Martin Braun via USRP-users)
----------------------------------------------------------------------
Message: 1
Date: Tue, 13 May 2014 16:02:34 -0700
From: Jared Dulmage via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] ERROR_CODE_BAD_PACKET after resuming a
flowgraph
Message-ID:
<of776b1dd0.58a4f16f-on88257cd7.007e93ed-88257cd7.007e9...@notes.aero.org>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140513/c5370502/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 13 May 2014 19:12:23 -0400
From: "Marcus D. Leech via USRP-users" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] ERROR_CODE_BAD_PACKET after resuming a
flowgraph
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 05/13/2014 03:56 AM, Martin Braun via USRP-users wrote:
> On 12.05.2014 20:33, Jared Dulmage via USRP-users wrote:
>> Using the C++ api, I create a flowgraph (starting with a usrp_source
>> block) to estimate the frequency offset of an received signal, stop
>> the flowgraph, adjust the RX center frequency of the usrp and then
>> restart to measure the residual offset. Upon restarting the
>> flowgraph I get a limitless list of errors:
>>
>> UHD Error: The receive packet handler caught an exception.
>> RuntimeError: usb rx6 transfer status: 3 UHD source block got error
>> code 0xf
>>
>> Debugging the program, the error code is ERROR_CODE_BAD_PACKET.
>>
>> There was no resolution (that I could find posted) to the issue
>> reference above. I have confirmed the issue exists with Windows 7.
>>
>> I appreciate any advice on resolving or further debugging this
>> issue.
>
> Hi Jared,
>
> a couple of questions:
>
> - Is there are reason to use 3.5.3? If you use a more recent version,
> do things become more stable?
> - When you say you stop and restart the flow graph, do you actually do
> a start(), stop(), wait(), start() on the same flow graph object?
>
> Thanks!
>
> Martin
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
Also, this is on a USRP1, where it doesn't *actually* have all the same
semantics as other UHD devices--the device-side code was frozen years
and years ago, prior to UHD being born, and so the UHD adaptation
layer isn't really able to support all the same semantics as other,
"true" UHD devices. Just wondering out loud if that has something to
do with the observed effects.
--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org
------------------------------
Message: 3
Date: Wed, 14 May 2014 09:28:38 +0500
From: jason sam via USRP-users <[email protected]>
To: Martin Braun <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Sampling + Clock rates (Was: (no subject))
Message-ID:
<CAEhLvxSfsq4QAd4XXRDofPMfvhzB58v+=rm6jd9txanfsjb...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
The sample rate should be double of RX or TX bandwidth?
On Tue, May 13, 2014 at 12:59 PM, Martin Braun via USRP-users <
[email protected]> wrote:
> On 13.05.2014 09:45, asad umer via USRP-users wrote:
>
>> What is the range of sample rate for B210??I knew it to be
>> 5-61.44MHz,but when i gave the rate of 50MHz i got the following
>> warning in GRC:
>>
>
> Right now, if you want to sample at 50 Msps, you need to set the clock as
> well, e.g.:
>
> $ benchmark_rate --args master_clock_rate=50e6 --tx_rate 50e6
>
> This will only work across USB3.
>
> Martin
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140514/353347f7/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 14 May 2014 07:56:29 +0100
From: Mike Jameson via USRP-users <[email protected]>
To: jason sam <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Sampling + Clock rates (Was: (no subject))
Message-ID:
<cajcjmiqp6a9chgthmophcfdf1e0x39fb0kniun_mjy6u0dw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
The sample rate is the same as the receive bandwidth as it uses complex
sampling.
So 1MHz receive bandwidth can be achieved with a sample rate of 1e6.
Mike
--
Mike Jameson M0MIK BSc MIET
Ettus Research Technical Support
Email: [email protected]
Web: http://ettus.com
On Wed, May 14, 2014 at 5:28 AM, jason sam via USRP-users <
[email protected]> wrote:
> The sample rate should be double of RX or TX bandwidth?
>
>
> On Tue, May 13, 2014 at 12:59 PM, Martin Braun via USRP-users <
> [email protected]> wrote:
>
>> On 13.05.2014 09:45, asad umer via USRP-users wrote:
>>
>>> What is the range of sample rate for B210??I knew it to be
>>> 5-61.44MHz,but when i gave the rate of 50MHz i got the following
>>> warning in GRC:
>>>
>>
>> Right now, if you want to sample at 50 Msps, you need to set the clock as
>> well, e.g.:
>>
>> $ benchmark_rate --args master_clock_rate=50e6 --tx_rate 50e6
>>
>> This will only work across USB3.
>>
>> Martin
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140514/e2132ba0/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 14 May 2014 12:34:46 +0500
From: jason sam via USRP-users <[email protected]>
To: Mike Jameson <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Sampling + Clock rates (Was: (no subject))
Message-ID:
<caehlvxsjr5wgskz7fr8ohbe1cmxq+oo89cqpmqfppe+b9n4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thank you Mike
On Wed, May 14, 2014 at 11:56 AM, Mike Jameson <[email protected]>wrote:
> The sample rate is the same as the receive bandwidth as it uses complex
> sampling.
>
> So 1MHz receive bandwidth can be achieved with a sample rate of 1e6.
>
> Mike
>
> --
> Mike Jameson M0MIK BSc MIET
> Ettus Research Technical Support
> Email: [email protected]
> Web: http://ettus.com
>
>
> On Wed, May 14, 2014 at 5:28 AM, jason sam via USRP-users <
> [email protected]> wrote:
>
>> The sample rate should be double of RX or TX bandwidth?
>>
>>
>> On Tue, May 13, 2014 at 12:59 PM, Martin Braun via USRP-users <
>> [email protected]> wrote:
>>
>>> On 13.05.2014 09:45, asad umer via USRP-users wrote:
>>>
>>>> What is the range of sample rate for B210??I knew it to be
>>>> 5-61.44MHz,but when i gave the rate of 50MHz i got the following
>>>> warning in GRC:
>>>>
>>>
>>> Right now, if you want to sample at 50 Msps, you need to set the clock
>>> as well, e.g.:
>>>
>>> $ benchmark_rate --args master_clock_rate=50e6 --tx_rate 50e6
>>>
>>> This will only work across USB3.
>>>
>>> Martin
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140514/1ab83884/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 14 May 2014 12:05:24 +0300
From: Michal Jakubiak via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Can't get a signal from USRP B200
Message-ID:
<cadjeeefo-6lzuizg-8wsrsj3svh5nfyqojrjcgbruqy2gfw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Pretty much the same thing happens. I've noticed that it crashes when I
tweak the sampling rate. The last message is printed when I close the
window. Until then the terminal prints 'usb rx6 transfer status: 5'
messages.
For the controller - I have Intel 7 Series/C210 Series. Is it known to
cause problems?
I've tried it with USB 2.0 port. It doesn't crash so that is an upside, but
I still can't see any signals.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140514/afc6c58a/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 14 May 2014 14:07:24 +0500
From: jason sam via USRP-users <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Underrun using USRP B210
Message-ID:
<CAEhLvxRDdbt7bLgifp7SncDrY8aOrP29Aie6tNtSpZ=8-hz...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I am using B210 to TX a signal..i have changed the clock to 56MHz and the
sample rate is also equal to 56MHz...but when i execute the flow graph i
get the message of under run:
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
what is the problem?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140514/84f88171/attachment-0001.html>
------------------------------
Message: 8
Date: Wed, 14 May 2014 11:20:58 +0200
From: Martin Braun via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Underrun using USRP B210
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 14.05.2014 11:07, jason sam via USRP-users wrote:
> I am using B210 to TX a signal..i have changed the clock to 56MHz and
> the sample rate is also equal to 56MHz...but when i execute the flow
> graph i get the message of under run:
>
> UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
>
> what is the problem?
Your computer isn't producing samples fast enough.
56 MHz is a lot for most machines, so this is not surprising.
The simplest flow graph would be to pre-calc your signal, and load it
into a vector sink, then pipe that directly to your USRP. If that
doesn't work, your PC just can't handle the load.
M
------------------------------
Message: 9
Date: Wed, 14 May 2014 14:29:14 +0500
From: jason sam via USRP-users <[email protected]>
To: Martin Braun <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Underrun using USRP B210
Message-ID:
<CAEhLvxQ4=traktsfaa-7lrbtbpvjppwlhpwwfaif1k9e7uu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I have added the vector sink before USRP block...now what do i do?Actually
i don't know about how to use vector sink..
On Wed, May 14, 2014 at 2:20 PM, Martin Braun via USRP-users <
[email protected]> wrote:
> On 14.05.2014 11:07, jason sam via USRP-users wrote:
>
>> I am using B210 to TX a signal..i have changed the clock to 56MHz and
>> the sample rate is also equal to 56MHz...but when i execute the flow
>> graph i get the message of under run:
>>
>> UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
>>
>> what is the problem?
>>
>
> Your computer isn't producing samples fast enough.
> 56 MHz is a lot for most machines, so this is not surprising.
>
> The simplest flow graph would be to pre-calc your signal, and load it into
> a vector sink, then pipe that directly to your USRP. If that doesn't work,
> your PC just can't handle the load.
>
> M
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140514/2ec9acbb/attachment-0001.html>
------------------------------
Message: 10
Date: Wed, 14 May 2014 11:42:22 +0200
From: Claudio Cicconetti via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Can't get a signal from USRP B200
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Same here with a B210. Controller is Intel 8 Series/C220 (rev 05).
Distribution is Ubuntu 14.04 with UHD 3.7.1.
Is there any controller that is known to work flawlessly?
Best regards,
Claudio
On 05/14/2014 11:05 AM, Michal Jakubiak via USRP-users wrote:
> Pretty much the same thing happens. I've noticed that it crashes when I
> tweak the sampling rate. The last message is printed when I close the
> window. Until then the terminal prints 'usb rx6 transfer status: 5'
> messages.
>
> For the controller - I have Intel 7 Series/C210 Series. Is it known to
> cause problems?
> I've tried it with USB 2.0 port. It doesn't crash so that is an upside, but
> I still can't see any signals.
------------------------------
Message: 11
Date: Wed, 14 May 2014 11:50:31 +0200
From: Martin Braun via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] B210 channel assignment
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 13.05.2014 11:03, Stefan Ereth via USRP-users wrote:
> Hi all, I try to capture samples of both channels from a B210 and
> save them in separate files. The Problem is that the channel
> assignment is different after retuning. I connected a signal
> generator to channel 1 and let channel 2 open. Normally the file
> "measure0" should always contain my signal and "measure1" noise. But
> out of 20 times the signal is 17 times in "measure0" and 3 times in
> "measure1". I appreciate any advice on resolving or further debugging
> this issue. Stefan
Hi Stefan,
do you mean you restart your app 20 times, and sometimes it switches?
Also, what makes you think this is due to re-tuning?
Do you have access to GNU Radio (or something similar)? If so, you could
try observing the output of the individual ports of a UHD Source (like
this: http://imgur.com/tJO4nOo). I just ran this at least 20 times, and
the output is reliably mapped to the same port every time.
Martin
------------------------------
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 45, Issue 13
******************************************
