Josh,
Thanks very much.
When I use UHD transmitting packets, after each packet, there is a "U"
printed out. Would you tell me what "U" means?
In early GNU Radio versions, "U" means CPU underrun--GNU Radio not
sending data fast enough to a sink, either a USRP or an audio. But UHD
uses UDP packets, so I cannot correlate "U" with CPU underrun.
Andrew
On 02/16/2011 12:00 PM, discuss-gnuradio-requ...@gnu.org wrote:
Message: 10
Date: Tue, 15 Feb 2011 11:59:17 -0800
From: Josh Blum<j...@ettus.com>
Subject: Re: [Discuss-gnuradio] details on changing singleusrp buffer
allocations
To:discuss-gnuradio@gnu.org
Message-ID:<4d5adb15.5040...@ettus.com>
Content-Type: text/plain; charset=ISO-8859-1
Pass them in with the device arguments, just like addr, serial and the
rest. Its just more optional key/value string pairs
device_address["recv_frame_size"] = "1024"
-josh
On 02/15/2011 10:57 AM, Feng Andrew Ge wrote:
> Could anybody please tell me how to set the following parameters? I am
> working on supporting UHD in the Python digital communication example
> and hopefully I can soon share my code with the list.
>
> * *recv_frame_size:* The size of a single receive buffer in bytes
> * *num_recv_frames:* The number of receive buffers to allocate
> * *send_frame_size:* The size of a single send buffer in bytes
> * *num_send_frames:* The number of send buffers to allocate
> * *concurrency_hint:* The number of threads to run the IO service
>
>
> Andrew
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
