On 03/24/2020 12:24 AM, Lukas Haase wrote:
Hi Marcus,
I would have two possible solutions but both of them are non-trivial:
1. As you say, parallelism. For each of N supported timed commands, the
decoding of the timed commands is cloned
2. If the timed commands are enough clock cycles in the f
Hi Marcus,
> Von: "Marcus D. Leech"
> On 03/23/2020 11:53 PM, Lukas Haase wrote:
> >> Von: "Marcus D. Leech"
> >> On 03/23/2020 11:08 PM, Lukas Haase wrote:
> >>> Hi Marcus,
> Von: "Marcus D. Leech"
> On 03/13/2020 10:52 AM, Lukas Haase wrote:
> > Hi again Rob,
> >
> > Yes
On 03/23/2020 11:53 PM, Lukas Haase wrote:
Hi Marcus,
Gesendet: Montag, 23. März 2020 um 23:35 Uhr
Von: "Marcus D. Leech"
An: "Lukas Haase"
Cc: "Rob Kossler" , "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on
Hi Marcus,
> Gesendet: Montag, 23. März 2020 um 23:35 Uhr
> Von: "Marcus D. Leech"
> An: "Lukas Haase"
> Cc: "Rob Kossler" , "USRP-users@lists.ettus.com"
>
> Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using
On 03/23/2020 11:08 PM, Lukas Haase wrote:
Hi Marcus,
Gesendet: Freitag, 13. März 2020 um 13:29 Uhr
Von: "Marcus D. Leech"
An: "Lukas Haase" , "Rob Kossler"
Cc: "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on
Hi Marcus,
> Gesendet: Freitag, 13. März 2020 um 13:29 Uhr
> Von: "Marcus D. Leech"
> An: "Lukas Haase" , "Rob Kossler"
> Cc: "USRP-users@lists.ettus.com"
> Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using a
one (tested): http://paste.ubuntu.com/p/VsGRmsbZQ5/
>>>>
>>>>
>>>> Thanks for reporting your results very interesting!
>>>>
>>>> Why do you think second mode makes sense to you? (assuming you are
>>>> using timed commands to to
_USRP_Events_Using_Timed_Commands_in_UHD) I have not read about it. Can you elaborate on this?
Thanks again,
Lukas
Gesendet: Freitag, 20. März 2020 um 13:44 Uhr
Von: "Rob Kossler"
An: "Lukas Haase" , usrp-users
Betreff: Re: [USRP-users] USRP X310 ignored DSP retunin
e at that point.
Great idea with the multiply_conjugate_cc block, I haven't thought of this yet. Thank for for sending your updated code ... I will continue with that now ...
Best,
Lukas
Gesendet: Freitag, 20. März 2020 um 12:04 Uhr
Von: "Rob Kossler"
An: "L
e things are reset when streaming starts/ends but not when
>>> re-tuning?
>>>
>>> Maybe this is what Marcus was mentioning: resetting phase accumulator
>>> vs. "increment register is updated with the new phase increment"?
>>>
>>> MAYBE
;t reset anything. But still, my question is left why
>> this would result in a random phase offset between DUC and DDC.
>>
>> Thanks again!!
>> Lukas
>>
>>
>> *Gesendet:* Donnerstag, 19. März 2020 um 19:16 Uhr
>> *Von:* "Rob Kossler"
>
code is here: http://paste.ubuntu.com/p/MbCJfPGzYW/ . I'm not sure
>>>>>if you have gnuradio(and QT) installed but if yes, simply "python2
>>>>>switch_on_click.py" should do. Let me quickly elaborate how it works:
>>>>>
On 03/19/2020 08:16 PM, Lukas Haase via USRP-users wrote:
Hi Rob,
Sorry I really should have ran the python file before uploading. The
issue was that I combined to files into one and forgot to remove the
imported file.
Here is a new one (tested): http://paste.ubuntu.com/p/VsGRmsbZQ5/
Thanks fo
ult in a random phase offset between DUC and DDC.
Thanks again!!
Lukas
Gesendet: Donnerstag, 19. März 2020 um 19:16 Uhr
Von: "Rob Kossler"
An: "Lukas Haase"
Cc: "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when
t;>>> - It also uses a custom module together with buttons and a probe
>>>> block to call functions upon clicking on a button
>>>> - The callback functions are defined in class "blk"
>>>> - The most important is
now = usrp_sink.get_time_now()
>>>> when = now + uhd.time_spec(1.0)
>>>>
>>>> usrp_sink.set_command_time(when)
>>>> usrp_source.set_command_time(when)
>>>> res1 = usrp_sink.set_center_freq(tune_req_tx, 0)
nd "rf_freq"). When
>>clicking, I jump between dsp_freq=0 and dsp_freq=500e3. As to my waveform,
>> you can infer from my screenshots and code above: I am transmitting and
>>receiving a 1MHz waveform (which acts as an additional "IF stage"). The
>&
m 1MHz to DC. I use 5 MSsps
>sampling rate.
>
>
> Again, thank you SO much.
>
> Best,
> Lukas
>
>
> *Gesendet:* Donnerstag, 19. März 2020 um 10:43 Uhr
> *Von:* "Rob Kossler"
> *An:* "Lukas Haase"
> *Cc:* "USRP-users@lists.ettus.com
Uhr
Von: "Rob Kossler"
An: "Lukas Haase"
Cc: "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using a timed command
Hi Lukas,
So, the conclusion is that your Rx0-to-Rx1 relative phase is nearly constant such that it seems
> Sorry I can't think of better ideas.
> Rob
>
> On Fri, Mar 13, 2020 at 12:12 PM Lukas Haase wrote:
>
>> Hi Rob,
>>
>> 1.) yes, works(*)
>> 2.) yes, works(*)
>>
>> (*): qualitatively. I set the timed command to "get_current_time() +
>
Hi Marcus,
> Gesendet: Freitag, 13. März 2020 um 13:29 Uhr
> On 03/13/2020 10:52 AM, Lukas Haase wrote:
> > Hi again Rob,
> >
> > Yes, I confirm:
> >
> > 1.) Finally I get the commands to execute at the same time (TX and RX
> > individually and both at the same time)
> > 2.) Yes, the phase is ran
alues (and in TX as well), they may be set to a different, random value.
However, I don't really know how to test these.
Thanks,
Lukas
Gesendet: Freitag, 13. März 2020 um 12:27 Uhr
Von: "Rob Kossler"
An: "Lukas Haase"
Cc: "Marcus D Leech" , "USRP-us
t;Marcus D Leech" , "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using a
timed command
Also, is it true that now you can successfully tune both RF and DSP at the
desired command time (but the remaining problem is that the Rx phas
t; Luke
>
>
> Gesendet: Freitag, 13. März 2020 um 11:08 Uhr
> Von: "Rob Kossler"
> An: "Lukas Haase"
> Cc: "Marcus D Leech" , "
> USRP-users@lists.ettus.com"
> Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when
to:rkoss...@nd.edu]>
An: "Lukas Haase" mailto:lukasha...@gmx.at]>
Cc: "Marcus D Leech" mailto:patchvonbr...@gmail.com]>,
"USRP-users@lists.ettus.com[mailto:USRP-users@lists.ettus.com]";
mailto:usrp-users@lists.ettus.com]>
Betreff: Re: [USRP-users] USRP X310 ignor
I see no signal until 10s, as expected
> - I experimented with "tx_time" and stream tags but for some reason many
> timed I get flooded with L's
>
>
> Can it be that there is another bug lurking somewhere deep in the USRP
> firmware?
>
> Thanks,
> Lukas
>
&
"
An: "Lukas Haase"
Cc: "Marcus D Leech" , "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using a
timed command
Also, is it true that now you can successfully tune both RF and DSP at the
desired command time (
ukas Haase"
Cc: "Marcus D Leech" , "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using a
timed command
Lukas,
Can you confirm the exact git hash for both UHD and the FPGA image you are
using? Perhaps the easiest way is to
e/Sink). This should ensure that stream start time is
>> set! (tested)
>> - Even if not, I also used explicitely
>>tb.uhd_usrp_source_0.set_start_time(uhd.time_spec(10))
>>tb.uhd_usrp_sink_0.set_start_time(uhd.time_spec(10))
>> at the beginning of my flow graph.
10s, as expected
> - I experimented with "tx_time" and stream tags but for some reason many
> timed I get flooded with L's
>
>
> Can it be that there is another bug lurking somewhere deep in the USRP
> firmware?
>
> Thanks,
> Lukas
>
>
>
> Gesend
omewhere deep in the USRP firmware?
Thanks,
Lukas
Gesendet: Mittwoch, 04. März 2020 um 19:27 Uhr
Von: "Marcus D Leech"
An: "Rob Kossler"
Cc: "Lukas Haase" , "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when
ock. So, when you provide a timed command to the Radio
>>> block (such as for tuning the RF) it can implement the command at the
>>> specified time by comparing to the device clock. The DUC block does not
>>> have access to the MB clock and so when you give it a timed c
ever, how do I address "RX2"? Intuitively "A:0
>>> A:1 B:0 B:1" but as said, both "TX/RX" and "RX2" are named "0".
>>> What would I do if I wanted to transmit from "TX/RX" of the second UBX
>>> and receive on a
n the USRP Sink: "B:0"
>> On the USP Source intuitively: "A:0 A:1 B:1" but that's wrong.
>>
>> 3.b.) In gr, there will be two multi_usrp objects: One for the receiver
>> (member variable of USRP Source) and one for the transmitter (member
>> var
c by the number of samples sent
> _metadata.time_spec += ::uhd::time_spec_t(0, num_sent, _sample_rate);
> GR_LOG_DEBUG(d_debug_logger, boost::format("Setting metadata
> time_spec: %d:%f") % _metadata.time_spec.get_full_secs() %
> _metadata.time_spec.get_frac_secs());
>
ttempt to use the tagged stream ... but then I will have the issue
that I need to tune TX *plus* RX at the same time! Furthermore, the streaming
tags API is super rudimentary. Also, skimming the source code for the tag
processing, I am not sure if this would change anything.
Gesendet: D
ecs() %
> _metadata.time_spec.get_frac_secs());
> _metadata.has_time_spec = true;
>
>
> To my understanding, gr-uhd now passes the correct timestamps on to UHD.
> However, the timed command is still ignored.
>
>
> Thanks,
> Lukas
>
>
> PS: I will attempt to use the tagged stream ..
lso, skimming the source code for the tag
processing, I am not sure if this would change anything.
Gesendet: Dienstag, 03. März 2020 um 13:25 Uhr
Von: "Sam Reiter"
An: "Rob Kossler"
Cc: "Lukas Haase" , "USRP-users@lists.ettus.com"
Betreff: Re
t;>> in parallel do the retuning.
>>> I am not too familiar with UHD on its own but I assume this would be
>>> very complicated, require multithreading etc.
>>> Do you have any demo code that could be easily modified for this
>>> scenario?
>>>
>&
cated, require multithreading etc.
>> Do you have any demo code that could be easily modified for this scenario?
>>
>> Best,
>> Lukas
>>
>>
>> Gesendet: Dienstag, 03. März 2020 um 12:08 Uhr
>> Von: "Sam Reiter"
>> An: "Rob Kossler&
Hi Marcus,
I'm pretty sure that the DDC and DUC don't have access to the MB clock and
thus have no option but to executed timed commands using the time stamp in
the sample stream.
Rob
On Tue, Mar 3, 2020 at 12:41 PM Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 03/03/20
>
> Gesendet: Dienstag, 03. März 2020 um 12:08 Uhr
> Von: "Sam Reiter"
> An: "Rob Kossler"
> Cc: "Lukas Haase" , "USRP-users@lists.ettus.com" <
> usrp-users@lists.ettus.com>
> Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX w
On 03/03/2020 12:08 PM, Sam Reiter via USRP-users wrote:
For what it's worth, I was able to reproduce the behavior described
here, but didn't get to dig into it much. My leading suspicion would
be what Rob mentioned about timestamping. Lukas' code sets a command
time, but I'm not clear on how t
m 12:08 Uhr
Von: "Sam Reiter"
An: "Rob Kossler"
Cc: "Lukas Haase" , "USRP-users@lists.ettus.com"
Betreff: Re: [USRP-users] USRP X310 ignored DSP retuning on TX when using a
timed command
For what it's worth, I was able to reproduce the behavior des
For what it's worth, I was able to reproduce the behavior described here,
but didn't get to dig into it much. My leading suspicion would be what Rob
mentioned about timestamping. Lukas' code sets a command time, but I'm not
clear on how timestamp metadata for packets being sent to the radio are
han
I wonder if the issue is related to a missing time stamp on the baseband
samples going from GR to UHD. If the stream does not have a time stamp,
the DUC is unable to apply the timed command because the DUC does not
really know the time - it must pull the time from the streaming samples.
This is in
Hi Marcus,
Thank you that would be amazing!
I followed the tutorial and built everything from source:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
$ uname -a
Linux sdr 5.3.0-40-generic #32~18
On 02/28/2020 01:01 PM, Lukas Haase via USRP-users wrote:
Hi again,
I created a minimum example (gnuradio) that shows the issue described below.
To summarize: Retuning to a different dsp frequency on an USRP X310 (+UBX160)
does not work (command ignored) ONLY if a timed command (in future is us
Hi again,
I created a minimum example (gnuradio) that shows the issue described below.
To summarize: Retuning to a different dsp frequency on an USRP X310 (+UBX160)
does not work (command ignored) ONLY if a timed command (in future is used).
The code shows it in a simple manner. Commenting out th
49 matches
Mail list logo
