Hi,
I'm studying the example packet_tx and uhd_packet_tx in
/usr/local/share/gnuradio/examples/digital/packet. I have some questions
regarding the process of packet transmission and the flow graph.
Why burst shaper block is needed? How do its parameters affect tx/rx?
Why polyphase arbitrary resa
7;re using (lspci might help)?
>
> Best regards,
>
> Marcus
>
> On 08/02/2017 06:01 PM, Rui ZOU wrote:
>
> Sorry for the confusion, because I thought whenever a hardware is not used
> throttle block must be used.
>
> This time, no USRP, no throttle block, the
Throttle block is NEVER in use when USRP Sink is used.
On Wed, Aug 2, 2017 at 11:08 AM, Rui ZOU
wrote:
> USRP sink
>
> On Wed, Aug 2, 2017 at 11:08 AM, Rui ZOU
> wrote:
>
>> My previous email shows the rate WITHOUT
>>
>> On Wed, Aug 2, 2017 at 11:05 AM,
USRP sink
On Wed, Aug 2, 2017 at 11:08 AM, Rui ZOU
wrote:
> My previous email shows the rate WITHOUT
>
> On Wed, Aug 2, 2017 at 11:05 AM, Marcus Müller wrote:
>
>> WAIT! Throttle? I didn't see that in either of the flow graphs you sent
>> me first (twoparatx, onefi
se
> Throttle together with hardware if you have both Throttle and a USRP sink.
>
> Remove the Throttle, and try again.
>
>
>
> On 08/02/2017 05:00 PM, Rui ZOU wrote:
>
> Changed to null source, the rate is still around twice the sample rate
> (390.625k)
graph, run "top" in a terminal, check that the python process
> and its spawned child threads really consume most of the CPU. If that's not
> the case, you've got something else eating away on your CPU.
>
> Best regards,
>
> Marcus
>
> On 08/02/2017 04:22 PM,
USRP after it should – but
> that's unlikely, you'd get a "U" instead.
>
> ² at least on my machine, most of the time is spent in the FM modulator.
> Which is kind of annoying, because looking into that, what costs most time
> is the "keeping the phase within 0
is so low. Of course, having a flat channel is nice :) but it
> also means that it might be quite hard to get any actual MIMO gain, because
> the two RX antennas might be very correlated. If in doubt, increase
> bandwidth. Be agressive with roll-off / Bandwidth factors of your GMSK.
>
ata you want to transmit, rather than the Random PDU block!
>
> I don't really know if that is the way to go. What is it, that you want to
> build? Maybe the mailing list can advise?
>
> Best regards,
>
> Marcus
>
> On 08/01/2017 05:26 PM, Rui ZOU wrote:
>
> He
very likely something
> wrong with the GNU Radio flowgraph you're using. Maybe you'd want to share
> that!
>
> Best regards,
>
> Marcus
>
> On 08/01/2017 04:59 PM, Rui ZOU wrote:
>
> Hi Marcus,
>
> Sorry for leaving the title empty, that's th
Hi Marcus,
Sorry for leaving the title empty, that's the first time to post to a
mailing list. This is also the first time to reply, no sure if I replied
correctly.
I use 390.625k as the sampling rate because this is the lowest I can get
using the Ettus X310 without giving me a warning saying tha
Hi there,
I'm using USRP X310 and the host is Dell OptiPlex 7040. The application is
built using GNURadio companion 3.7.10.1
trying to transmit using both the daughter boards.
When two channels transmit the same file, the transmission can last for a
while before producing U and L and get stuck.
hd/examples/ .
Greetings,
Marcus
[1] http://gnuradio.org/doc/doxygen/page_stream_tags.html
[2] http://gnuradio.org/doc/doxygen/page_stream_tags.html
On 12/16/2014 05:21 PM, Rui Zou wrote:
Hello,
I would like to implement the process as follows at the Rx side:
Record the time when the first sample arrived, and th
Hello,
I would like to implement the process as follows at the Rx side: Record
the time when the first sample arrived, and then wait for a certain
interval and then send ack back to Tx. Meanwhile, finish the cfo
calculating and compensating.
Here is my whole flow graph design. (Each means a bl
14 matches
Mail list logo
