Hey Marcus,
I think the Selector block works well with my setup.
But I need a solution with which I can do a dynamic change in the input/output index. Can you let me know how is this possible
Ayaz
From: Ayaz Mahmud
Sent: Tuesday, July 17, 2018 4:39 PM
To: Marcus D. Leech; "Müller, Marcus (CEL)"; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Enable/Disable TX ports in B210 in 2x2 setup
Hi Marcus,
The situation still is same.
By browsing the archive I found some switching of blocks with SELECTOR. Is there any example that will be helpful on how this block actually functions ?
Thanks
Ayaz
From: Marcus D. Leech
Sent: Monday, July 16, 2018 1:26 PM
To: Ayaz Mahmud; "Müller, Marcus (CEL)"; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Enable/Disable TX ports in B210 in 2x2 setup
On 07/16/2018 02:05 PM, Ayaz Mahmud wrote:
Hi Marcus,
The issue is even I put the vector source toggling with 1 and 0s it transmit a signal. So I need something that will not transmit at all and switch between these 2 radio chains.
Thanks,
Ayaz
You're probably seeing the residual LO leakage during periods of "no transmit".
You can try using offset-tuning to move the leakage out-of-band:
Use:
uhd.tune_request(frequency,offset)
In the UHD sink for the "frequency" field.
From: Marcus D. Leech
Sent: Saturday, July 14, 2018 8:15 PM
To: Ayaz Mahmud; "Müller, Marcus (CEL)"; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Enable/Disable TX ports in B210 in 2x2 setup
On 07/14/2018 06:40 PM, Ayaz Mahmud wrote:
Hi Muller / Marcus,
I got the testing right now, but unfortunately it doesn't work while I put it in my original file.
Here is the attached .grc where I have used vector source as input and multiply a period with 1 and then with zeros on one radio channel and opposite on the other.
Can you please have a look, and check if I am doing anything wrong ?
Ayaz
You're asking us to debug a very complex signal flow.
Why don't you try something a *lot* simpler to get the TX-flow-switching-logic correct first, and then work up from there.
No comments:
Post a Comment