On 02/22/2019 08:15 AM, Jorge Chen wrote:
Hi Marcus
Thanks for your reply.
Since I thought it works in the case using channel 0,4 with default
subdev spec setup(“A:0 A:1 B:0 B:1”), so I ignore setting the subdev spec.
However, I add the subdev spec setting and test again, but still
failed to
Hi Marcus
Sorry for the confusion, the problem is no signal at all, and the
application just hang without any message.
Thanks
Jorge
Marcus D. Leech 於 2019年2月22日 週五，下午10:09寫道：
> On 02/22/2019 08:15 AM, Jorge Chen wrote:
>
> Hi Marcus
>
> Thanks for your reply.
>
> Since I thought it works in th
On 02/22/2019 08:15 AM, Jorge Chen wrote:
Hi Marcus
Thanks for your reply.
Since I thought it works in the case using channel 0,4 with default
subdev spec setup(“A:0 A:1 B:0 B:1”), so I ignore setting the subdev spec.
However, I add the subdev spec setting and test again, but still
failed to
Hi Marcus
Thanks for your reply.
Since I thought it works in the case using channel 0,4 with default subdev
spec setup(“A:0 A:1 B:0 B:1”), so I ignore setting the subdev spec.
However, I add the subdev spec setting and test again, but still failed to
transmit synchronized signal from 2 N310s.
Any
On 02/21/2019 10:18 AM, Jorge Chen via USRP-users wrote:
Hi USRP Users
I tried to synchronize 2 N310s throught the external PPS and reference
clock, and tested by the application below.
*/tx_waveforms.exe --args
"addr0=192.168.30.3,addr1=192.168.40.3,clock_source=external,time_source=external
Hi USRP Users
I tried to synchronize 2 N310s throught the external PPS and reference
clock, and tested by the application below.
*tx_waveforms.exe --args
"addr0=192.168.30.3,addr1=192.168.40.3,clock_source=external,time_source=external,master_clock_rate=122.88e6"
--rate 30.72e6 --freq 3.5e9 --wav
Hi Michael,
halleluja! that was it! Thanks for spotting this.
Florian.
On 20/12/2018 02:34, Michael West wrote:
Hi Florian,
The device arguments are "clock_source" and "time_source". I noticed
in your command you had them as "clock_src" and "time_src". That may
be the source of the problem
Hi Florian,
The device arguments are "clock_source" and "time_source". I noticed in
your command you had them as "clock_src" and "time_src". That may be the
source of the problem.
Regards,
Michael
On Mon, Dec 10, 2018 at 11:33 AM Florian Kaltenberger via USRP-users <
usrp-users@lists.ettus.com
Dear Nate,
no it says something like this is not supported with the N310 and I
should pass it using the args options. Sorry, I don't have access to the
N310 right now, so I can't give you the exact message, but I have tried
that.
Florian.
On 10/12/2018 19:00, Nate Temple wrote:
Hi Florian,
Hi Florian,
If you pass the arg "--ref external" to tx_waveforms, does it resolve this
frequency offset?
https://github.com/EttusResearch/uhd/blob/master/host/examples/tx_waveforms.cpp#L62
Regards,
Nate Temple
On Thu, Dec 6, 2018 at 12:22 AM Florian Kaltenberger via USRP-users <
usrp-users@lis
Hi Marcus,
I have measured this with a spectrum analyzer simply by setting markers
to the peak of the sinusoid (one marker per measured USRP) and then
taking the delta.
Could it be that the USRP is ignoring the external reference when used
alone? Remember, I am doing the test with one USRP a
oh! That means 341 ppb frequency error, which *really* shouldn't be
happening.
I'd like to get some statistics of that error, how are you measuring
it?
Best regards,
Marcus
On Wed, 2018-12-05 at 12:55 +0100, Florian Kaltenberger wrote:
> Sorry typo. I did use a frequency of 3.51GHz.
>
> > On 5
Sorry typo. I did use a frequency of 3.51GHz.
> On 5 Dec 2018, at 12:54, Marcus Müller wrote:
>
> Hi Florian,
>
> trying to get my head to understand the order of problems here:
> Could you try to use a higher frequency (say, --freq 2e9 instead of
> 3.5e6)?
> I'd thing 3.51 MHz is out of rang
Hi Florian,
trying to get my head to understand the order of problems here:
Could you try to use a higher frequency (say, --freq 2e9 instead of
3.5e6)?
I'd thing 3.51 MHz is out of range for the N310, anyway?
Best regards,
Marcus
On Wed, 2018-12-05 at 11:49 +0100, Florian Kaltenberger via USRP-
So I can confirm that there is a frequency offset between the two USRP
N310s when using only an octoclock (10MHz + PPS) to synchronize. I have
measured with the tx_waveforms program
./tx_waveforms --args
"addr=192.168.x.2,time_src=external,clock_src=external,master_clock_rate=122.88e6"
--rate
Hi Marcus and Robin,
thanks for your answers, this is helpful information. I should add, that
I actually tried the synchronization with an octoclock (10MHz + PPS),
but it did not give me the expected results, i.e., I saw some residual
frequency offsets. But maybe I screwed up at some point. Le
On 12/04/2018 10:14 AM, Florian Kaltenberger via USRP-users wrote:
Hi there,
I just discovered that in addition to the external 10MHz reference in,
the USRP N310 also has external local oscilator inputs, one for each
daughterboard and each TX/RX. So does that mean that in order to
synchroniz
sers] synchronizing multiple USRP N310
Hi there,
I just discovered that in addition to the external 10MHz reference in, the USRP
N310 also has external local oscilator inputs, one for each daughterboard and
each TX/RX. So does that mean that in order to synchronize multiple N310 in
frequency, p
Hi there,
I just discovered that in addition to the external 10MHz reference in,
the USRP N310 also has external local oscilator inputs, one for each
daughterboard and each TX/RX. So does that mean that in order to
synchronize multiple N310 in frequency, phase, and time, it is no longer
suffi
19 matches
Mail list logo
