Sorry for this question but the problem is found: that was a cable from the
1PPS source
which was broken...
To answer your question: it is a self made 1PPS/10MHz source with 10ns accuracy.
regards,
olivier
Le 24/03/2020 à 18:08, Marcus D. Leech via USRP-users a écrit :
> On 03/24/2020 12:49 PM,
On 03/24/2020 12:49 PM, Olivier Ravard via USRP-users wrote:
Hi,
In order to synchronize several devices, We used to use an external PPS and
10MHz
reference and call set_next_time_pps.
This works fine since many years using UHD 3.9 and N210. We recently use X300 +
TwinRx
using UHD 3.10.3 and
Hi,
In order to synchronize several devices, We used to use an external PPS and
10MHz
reference and call set_next_time_pps.
This works fine since many years using UHD 3.9 and N210. We recently use X300 +
TwinRx
using UHD 3.10.3 and it seems
that it does not work.
It seems that set_time_next_pp
Marcus, I don’t think any action is required at present, it’s been working
“fine" for many years.
But as you say the firmware as written thinks things are working on a different
timescale.
Luckily their is nothing real time or timing critical in there
-Ian
> On Mar 24, 2020, at 6:56 AM, Marcus M
Hi Ian,
always good to hear from you, but, puh, this is awakening old memories,
and I'm not even sure those are the good ones.
Yeah, I remember, the interval for the Gratuitious ARP packets isn't
what it's supposed to be according to firmware comments. Uh. Maybe we
just clocked the CPU core lower
Hey Jeff,
What type of GPS antenna are you using? 3.3V or 5V? If it's compatible with
X310 & other USRPs, I would imagine you'll be good to go with the E320...
Do you see the locked / unlocked status change between consecutive runs of
something like gpsmon on the E320?
There were some early-ish r
