Ah, I think I see where you're going :)
So, here, we're really talking about digital clock division! That is, a
counter :)
While that'd be totally possible to piece together (counting edges,
then emitting an edge every N input edges), it's not how DSP works: the
things you handle *are* already wit
On Thu, Jun 20, 2019 at 6:24 AM Ramazan Çetin
wrote:
> At the end, i decided to give some gap between transmitters. So, 36 to
> 90 and -36 to -90 are assigned to transmitters. But, result is same. I
> have attached two pictures of spectrum. They represents state of one and
> two transmitters are
Hi Barry,
On Thu, 2019-06-20 at 09:27 -0400, Barry Duggan wrote:
> Marcus,
>
> Thank you for that. So now I have three questions:
> 1) Does it matter if one uses [brackets] or (parentheses) to enclose a
> vector? It appears not.
That's Python syntax; [] means Python list (a mutable sequence of
Marcus,
Thank you for that. So now I have three questions:
1) Does it matter if one uses [brackets] or (parentheses) to enclose a
vector? It appears not.
2) What determines the rate at which the vector contents are presented
to the output?
3) If one were to add a 'throttle', where would it go?
Hi Jale - OK; thanks for the updates & for translating to English :) In the
future, please "reply all" to include the GNU Radio discussion list: more eyes
on your issue are more likely to help you.
Suppose you create a GRC flowgraph where the OFDM Mod goes through a virtual
channel (there's a G
Hi Ramazan - My primary wondering about your specific OFDM setup is whether the
sync preambles are abiding by your carrier separation (256 carriers: -120:-1
for one Tx and 1:120 for the other). It certainly looks from the images that
the payload portion is working as you desire. Depending on the
OK, I think I understand all that (it IS a shift in mind-set from my
history;), BUT, at some point I need to send the bits at a fixed baud
rate (e.g. 45.45). That is what was behind my question #2. Where / how
can I do that?
---
Barry Duggan
On 2019-06-20 09:55, Müller wrote:
Hi Barry,
On
ha! That's easier than I think you think it is :)
So, you have some hardware to actually transmit. Let's, for the time
being, assume we're doing an acoustocoupler using your soundcard.
That's cool, because a) you very likely have that and b) it's easy to
observe :D
So, you use GNU Radio's Audio S
Hi Ramazan - Hmmm ... I'm not coming up with anything greatly useful when using
a single OFDM block for Tx. Alternatively you could use a 2 channel PFB
synthesizer on Tx, with 2 separate OFDM Tx and feed them into the synthesizer.
On Rx use a PFB channelizer and take its 2 outputs to 2 separate
Hello,
Thanks for the reply! More specifically, what I'm aiming for is to change
frequency after transmitting some number of samples. I've tried having the
sink call the set frequency commands each time 'work' is run, but that
doesn't seem to help me set the length. I've tried using message passin
Marcus,
OK, so that works. Now I have more questions!
1) Since the vector source has a repeat option, why use the Repeat
block? Does it still need a 'vector to stream' function?
2) What criteria did you use to pick the 4,545 sample rate? If there
were no repeat, what would you do? The repeat o
Hi Barry,
on my way to bed, so really quick:
On Thu, 2019-06-20 at 17:48 -0400, Barry Duggan wrote:
> Marcus,
>
> OK, so that works. Now I have more questions!
>
> 1) Since the vector source has a repeat option, why use the Repeat
> block? Does it still need a 'vector to stream' function?
The
12 matches
Mail list logo
