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: scheduled transmission using tx_timed_samples.cpp (Sam mite)
2. Re: scheduled transmission using tx_timed_samples.cpp (Josh Blum)
3. QPSK Demodulator using GRC (ZaInzAiN Jj)
4. Re: QPSK Demodulator using GRC (Manu T S)
5. Re: QPSK Demodulator using GRC (Azza Ben Mosbah)
----------------------------------------------------------------------
Message: 1
Date: Mon, 6 May 2013 10:12:44 +0500
From: Sam mite <[email protected]>
To: [email protected]
Cc: [email protected], "[email protected]"
<[email protected]>
Subject: Re: [USRP-users] scheduled transmission using
tx_timed_samples.cpp
Message-ID:
<caphw9ttpu4r5u03rxdecrm30uevgxb3anvuhdr78fsem2kr...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
> Setting device timestamp to 0...
> > Start time is 0 7.801e-05
> > Sent packet: 363 samples
> > Sent packet: 363 samples
> > .....
> > .....
> > Sent packet: 363 samples
> > Sent packet: 363 samples
> > Sent packet: 199 samples
> >
>
> You will see the prints ASAP because the packets go out to the device
> ASAP. This means sent to device, not necessarily transmitted.
>
> > However, effect is observed on the following output
> >
> > Waiting for async burst ACK... success
> > Done!
> >
> > End time is 5 0.00197141.
>
> The time printed here after the ack is a little larger than 5 seconds,
> so you can see that the USRP must have held off transmission until 5
> seconds and then send the ACK for the end of burst.
>
> -josh
>
> Thanks josh, I got the idea. Also, I verified by looking at the LED "A" on
USRP N210, which lights almost after 5 seconds. :)
I thought this should be discussed on gnruadio, so added gnuradio list. I
want to convert tx_timed_samples.cpp into python. Can I do that? How can I
make a "multi_usrp" ? Also, How can I use a block's data instead of buffer ?
e.g
tx_stream->send(DATA_FROM_SOME_BLOCK_IN_FLOWGRPAH, samps_to_send, md,
timeout);
Further, what could be the minimum value of "seconds_in_future" ? In my
case, When I set it to 0.3 or below I get following
Waiting for async burst ACK... fail
What does it mean ?
Thanks
--
Regards,
Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130506/1687c1e2/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 06 May 2013 00:37:32 -0500
From: Josh Blum <[email protected]>
To: Sam mite <[email protected]>
Cc: [email protected], "[email protected]"
<[email protected]>
Subject: Re: [USRP-users] scheduled transmission using
tx_timed_samples.cpp
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
>>
>> Thanks josh, I got the idea. Also, I verified by looking at the LED "A" on
> USRP N210, which lights almost after 5 seconds. :)
>
> I thought this should be discussed on gnruadio, so added gnuradio list. I
> want to convert tx_timed_samples.cpp into python. Can I do that? How can I
> make a "multi_usrp" ? Also, How can I use a block's data instead of buffer ?
> e.g
> tx_stream->send(DATA_FROM_SOME_BLOCK_IN_FLOWGRPAH, samps_to_send, md,
> timeout);
>
The gr-uhd blocks that come with gnuradio integrate the USRP streaming
into gnuradio's data flow. You can create gnuradio blocks or use
existing blocks to interact with the USRP data streams. In addition, the
stream tags are used to control things like transmit time:
I think you will find some of the links here informative:
http://code.ettus.com/redmine/ettus/projects/uhd/wiki/GNU_Radio_UHD#Using-UHD-Software-with-GNU-Radio
> Further, what could be the minimum value of "seconds_in_future" ? In my
> case, When I set it to 0.3 or below I get following
>
> Waiting for async burst ACK... fail
>
> What does it mean ?
>
The time delta between time on the device and time on a packet about to
be sent can actually be on the order of 100s of microseconds. However,
in this example, there is an expensive operation of setting up the
transmit streamer thats happening with in the time specified, so I think
thats why you are seeing 300 milliseconds fail. I think the transmit
time in this case has become "late" when the USRP interprets the packet.
-josh
------------------------------
Message: 3
Date: Mon, 6 May 2013 16:23:52 +0800 (SGT)
From: ZaInzAiN Jj <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] QPSK Demodulator using GRC
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Dear all,
I get a block diagram of the QPSK demodulator from gnuradio.org like the
attachment.
At the block there are Frequency sync and Matched filter. If I use GRC, What is
the name of the block that I use? I am a beginner using GRC.
I use qpsk modem?like the attachment,?but the file. txt which sent is null at
receiver.
What wrong with my QPSK modem blocks? My be there?suggestion for solved it?
I welcome any suggestions you.
Thanks,
Zai
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130506/abe4e482/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qpsk demodulator.png
Type: image/png
Size: 133959 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130506/abe4e482/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qpsk tx.png
Type: image/png
Size: 206928 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130506/abe4e482/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qpsk rx.png
Type: image/png
Size: 235551 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130506/abe4e482/attachment-0005.png>
------------------------------
Message: 4
Date: Mon, 6 May 2013 19:30:53 +0530
From: Manu T S <[email protected]>
To: ZaInzAiN Jj <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] QPSK Demodulator using GRC
Message-ID:
<cacjh7qxfb+ryozjexvo3zngxtsq6eez8dr_9ozct87xmzu3...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
The psk modulator in GNU Radio has a frequency sync block and matched
filter block within it. To my knowledge, they are fll_band_edge [1] and
pfb_clock_sync [2] blocks respectively. I'm not sure why you receive a null
file.
[1] http://gnuradio.org/doc/doxygen/classdigital__fll__band__edge__cc.html
[2] http://gnuradio.org/doc/doxygen/classdigital__pfb__clock__sync__ccf.html
On Mon, May 6, 2013 at 1:53 PM, ZaInzAiN Jj <[email protected]> wrote:
> Dear all,
> I get a block diagram of the QPSK demodulator from gnuradio.org like the
> attachment.
> At the block there are Frequency sync and Matched filter. If I use GRC,
> What is the name of the block that I use? I am a beginner using GRC.
>
> I use qpsk modem like the attachment, but the file. txt which sent is
> null at receiver.
> What wrong with my QPSK modem blocks? My be there suggestion for solved it?
>
> I welcome any suggestions you.
> Thanks,
>
> Zai
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
--
Manu T S
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130506/11dc70fa/attachment-0001.html>
------------------------------
Message: 5
Date: Mon, 6 May 2013 16:18:02 +0200
From: Azza Ben Mosbah <[email protected]>
To: Manu T S <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] QPSK Demodulator using GRC
Message-ID:
<cah-1rog+vzk2oou8qrxdu4gd02jgwy9jaekxcb5yzc23p8k...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello Zain,
I almost have the same problem (a null file). And I can't find an
appropriate solution.
I would be gratefull if you share with me the solution when finded.
Thanks in advance.
Best Regards,
Azza.
On Mon, May 6, 2013 at 4:00 PM, Manu T S <[email protected]> wrote:
> The psk modulator in GNU Radio has a frequency sync block and matched
> filter block within it. To my knowledge, they are fll_band_edge [1] and
> pfb_clock_sync [2] blocks respectively. I'm not sure why you receive a null
> file.
>
> [1] http://gnuradio.org/doc/doxygen/classdigital__fll__band__edge__cc.html
> [2]
> http://gnuradio.org/doc/doxygen/classdigital__pfb__clock__sync__ccf.html
>
>
> On Mon, May 6, 2013 at 1:53 PM, ZaInzAiN Jj <[email protected]>wrote:
>
>> Dear all,
>> I get a block diagram of the QPSK demodulator from gnuradio.org like the
>> attachment.
>> At the block there are Frequency sync and Matched filter. If I use GRC,
>> What is the name of the block that I use? I am a beginner using GRC.
>>
>> I use qpsk modem like the attachment, but the file. txt which sent is
>> null at receiver.
>> What wrong with my QPSK modem blocks? My be there suggestion for solved
>> it?
>>
>> I welcome any suggestions you.
>> Thanks,
>>
>> Zai
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
>
>
> --
> Manu T S
>
> _______________________________________________
> 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/20130506/2a8083fe/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 33, Issue 5
*****************************************
