Michael Dickens wrote:
On Dec 29, 2007, at 4:03 PM, Matt Ettus wrote:
Your message stated you wanted to do "simultaneous TX/RX". If you
want to switch back and forth, then you do not want simultaneous,
which is a good thing. You want to use the auto t/r switching mode.
Just to clarify, and
On Tue, Jan 08, 2008 at 08:26:43PM -0800, Wee Shinhan wrote:
> Hi guys,
>
> I'm using the vector_sink block to capture complex
> data from the receiver USRP (in the hope to be able to
> predict the wireless channel coeff) I printed the
> recevied complex data using the rx_callback function
> in re
Hi guys,
I'm using the vector_sink block to capture complex
data from the receiver USRP (in the hope to be able to
predict the wireless channel coeff) I printed the
recevied complex data using the rx_callback function
in receive_path.py script. The problem is the
vector_sink produces endless amoun
On Tue, Jan 08, 2008 at 04:10:46PM +0100, [EMAIL PROTECTED] wrote:
> Hi,
> I've observed that all URB allocated in the Tx side are correctly proccesed.
> For example:
> Data -> 25 Byte (from a mpg file)
> Total payload -> 80 Byte (Data + CRC + Padding + Header + )
>
> Total Byte to transfer wi
Hi,
I've observed that all URB allocated in the Tx side are correctly proccesed.
For example:
Data -> 25 Byte (from a mpg file)
Total payload -> 80 Byte (Data + CRC + Padding + Header + )
Total Byte to transfer with a BPSK modulator -> 80 * 8 (bit of a char) * 6
(sample per symbol) * 4 (Byte -
