Sorry Marcus, I should have been more explicit, I did wait many minutes for the
GPS lock to be confirmed by query_gpsdo_sensors before proceeding with running
test_pps_input on either the master or mate.
Kind Regards,
John
From: Marcus D. Leech
Sent: Thursday, September 21, 2017 8:46 AM
To: John Shields
Cc: [email protected]
Subject: Re: [USRP-users] N200 MIMO PPS not being detected on mate...
On 09/20/2017 04:39 PM, John Shields wrote:
So, as a result of moving the Firefly to ...20.2 (red) :
Obs 1) when using query_gpsdo_sensors I occasionally received USRP NOT locked
to 10 MHz Reference but after a retry it finds it OK. I switched PPS/Ref cables
from the Firefly to USRP motherboard and the issue remained, occasionally, as a
10 MHz issue. I have not seen this when the Firefly was in 10.2 (blue) but I
have not needed to run the query_gpsdo_sensors very often on this unit.
Obs 2) After, query_gpsdo,sensors confirms lock on red, when I do a
test_pps_input (—source mimo) on blue, I still get no PPS.
As best I can tell, Obs 2) would indicate that the issue is not with either
N200? The only issue might be the MIMO cable? but it is a robust beast so I
would doubt that.
Being a BNR/Nortel pensioner, just buying a new N200 ($kiwi 2500.00) in the
hope that it would change the situation to a pleasant outcome would appear
imprudent. My gut feel is that using the MIMO cable with N200 is not that
common a config and there might be something gnarly going on?
Kind Regards,
John
The MIMO cable is just a SASI cable as I recall. But, agreed, seems like the
cable is unlikely to have failed.
I'd wait for the unit with the GPSDO in it to achieve solid GPS lock -- it may
be that it's not providing reliable PPS until it is locked.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
