well here's the thing: I need to transmit a burst every 7ms. From what
you've written about tuning times, i got somewhat pessimistic as to
whether this is enough time to retune. Or would you say that this should
be enough?
--
Posted via http://www.ruby-forum.com/.
hey man,
many many thanks for the detailed reply! Based on it, I decided to
achieve frequency hopping not by changing the centre frequency of the
USRP, but by multiplying my signal with a sine of a certain frequency
offset and then transmit that signal over the USRP with a fixed USRP.
Unfortun
Dear all,
After quite some searching, I wasn't able to find information about how
long it takes to retune a USRP (say, change the centre frequency). Do
you guys know anything about that? Specifically, I'm using a USRP X300
with a UBX160 daughterboard. Does anyone know how long it takes in this
spe
Martin Braun wrote in post #1177442:
> Are you doing bursty transmission (i.e. using eob/sob tags, or using
> tagged streams)?
>
> M
yes, I'm using eob/sob tags. I'm assuming that the tx_time tag should be
on the same item as tx_eob?
--
Posted via http://www.ruby-forum.com/.
__
hi all
I've one more tag related question:
I want to sent packets in burst over a usrp_sink. the time between two
consecutive bursts should be 7ms. thus, I want to use a tx_time_tag
along with every first item of a packet so that the usrp waits for 7ms
before transmitting it. However, it seems th
hi guys,
is there a comprehensive list of return/error messages by the usrp_sink?
1.When I try to send an item to the USRP sink with a tx_time tag, I get
a flood of "GtGtGtGt"
2. when I send an item to usrp_sink with the packet_len tag, again I get
"GtGtGtGt"
3. when I send an item to the usrp_
I'm guessing something went wrong here? :) the post is empty
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
hey Martin,
many thanks for the reply! one more question about this though: every
time the work function is called in the PACKET_CREATOR, it reads 28
bytes and outputs 37 bytes (as confirmed by nitems_read(0) and
nitems_written(0)). From what you were saying, and from what I've read
from other sou
hi all,
I have three blocks:
1. MESSAGE_LOADER
reads a binary file and outputs it byte by byte to the next block
(PACKET_CREATOR). On every 28th byte (and on the 0th byte) it adds tags
denoting the start of a PDU
2. PACKET_CREATOR (tagged_stream_block)
waits for 28 bytes to arrive. once this is
