Thanks again. Two more clarifications...
- When you say each "radio" has a separate queue, does that translate
into each "channel" has a separate queue? Assuming so, then I suppose a
streaming command that is for multiple channels will create an entry in
each of the queues.
- If
Hi Rob,
Yes. The queue is a simple FIFO and does no reordering, so the commands
must be in time order. Each radio has a separate command queue, so they
will not interfere with each other.
All commands go to the same queue, whether timed or not, so care must be
taken with all commands issued to
Thanks Michael,
So, do all "timed" commands sent to the command queue need to be in
strictly ascending order (in time)? In other words, will a disordered
queue always produce a Late error or does it depend on how much disordered?
Are there any other "timed" commands to worry about besides the
Hi Rob,
Yes, that would be a problem. There is a single command queue for both TX
and RX commands to the radio, so something has to collate the T/R switching
commands with the RX streaming command so none of the commands arrive late.
Regards,
Michael
On Thu, Oct 5, 2017 at 7:48 AM, Rob Kossler
Hi Mark,
Update UHD to a newer version. The head of the maint branch or the latest
3.10.2.0 release should work. The ADC self test is skipped when supplying
"recover_mb_eeprom" as of UHD 3.10.0.0.
Regards,
Michael
On Tue, Oct 10, 2017 at 12:32 PM, Mark Koenig via USRP-users <
Just following up on the message I sent out 8 days ago. Does anyone have any
resolution to this issue? I have seen other people have the problem, but have
yet to find a fix.
Thanks
Mark
From: Mark Koenig
Date: Monday, October 2, 2017 at 10:18 AM
To:
Hi ,
It would be great if any one could address this issue
I need to toggle between channels and collect data ,
by recreating the rx_streamer I am getting an assertion error.
I tried using rx_streamer.reset() but that didn't seem to destroy the
previous stream
Error: AssertionError:
Hello,
I apologize for my terrible English,
I have a problem with buffer overflow.
Tell me, please, what optimization measures do you use when working?
How the problem is observed:
I have 6 b205mini devices, and I noticed that I was up to a maximum of
205MHz per second. ie, either 5 devices on 41
The key issues was "square wave". Once that waveform is used, as opposed to
a sine wave, everything works as expected in a wider range of Vpp values.
Thanks,
Dario
On Tue, Oct 3, 2017 at 11:05 AM, Dario Fertonani
wrote:
> I'd like to assume that *OctoClock-G*'s 10