I don’t have any SkyTraq navigation modules, but I power cycled a couple of my clocks (with the timing modules) and they came back up as they usually do, so I can tentatively confirm that in survey-and-hold mode they don’t appear to have any problems getting a fix. TBD is vetting the results to insure there’s no loss of accuracy, but I haven’t seen any weirdness from any of my GPSDOs at least.
Sent from my iPhone > On Sep 27, 2017, at 4:59 AM, Azelio Boriani <[email protected]> wrote: > > Maybe this can be useful: > > <https://www.navcen.uscg.gov/pdf/gps/IDOC_IODE_Final_Response_150814.pdf> > >> On Wed, Sep 27, 2017 at 5:58 AM, Scott Newell <[email protected]> >> wrote: >> At 05:20 PM 9/26/2017, Tom Van Baak wrote: >>> >>> An interesting note from Said, below... >>> I've sent a couple of queries out to GPS professionals. >>> Feel free to comment if you have concrete information that would help. >>> Also, if during the past week any of you were logging almanacs or >>> continuously recording the 50 bps raw data from any GPS/SV, please let me >>> know. >> >> >> I have ublox LEA-6T data logged from 18:30 on 8-26 through 05:30 on 9-18. It >> includes the RXM-SFRB subframe buffer messages. Would that be of any help, >> or did I shut it off too early? >> >> -- >> newell N5TNL >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
