Hi According to the guys at Lucent, there were numerous fixes / updates / enhancements of the code in the GPS cards they used. The number they tossed out was "hundreds". I suspect that was an exaggeration. Even if it was "only" dozens there likely are a number of different code images in the cards, each with it's own issues.
Bob On Aug 23, 2013, at 2:38 PM, Alan Kamrowski II <ala...@earthlink.net> wrote: > Hi Guido and mc235960, > > It stopped doing it all of a sudden and is now accepting the date properly. > I did numerous CPU resets on it and one power down/power up and it still did > it. Telling the unit the date was old (1/1/1994) took fine so I kept > increasing the year 1999, 2000, 2005, 2015 and finally back to 2013 and it > stayed ok. > > The Motorola @@ea command doesn't have the GPS week in it so I'm not sure how > the unit got where it was, but it does seem related to that somehow. I did > try to send it 2050 to see how far it would go because the Motorola spec ends > at 2017. Perhaps this triggered a "fix gps date" function in eeprom that > added to the date to try to correct for the number of week rollover issue? > > Thanks, > > Alan > > > -----Original Message----- > From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On > Behalf Of Guido Küppers > Sent: Friday, August 23, 2013 1:25 PM > To: Discussion of precise time and frequency measurement > Subject: Re: [time-nuts] RFTGm-II-Rb - can you gps discipline it without the > XO module? > > Hi Alan, > I haven't seen this behaviour yet, but then I have RFTG shut off for a couple > of months since. > 7168 is dividible by 7 and the result is 1024. You know the gps week wraps > over from 1023 (0x3ff) to 0. > Perhaps what you see is the consequence of some software workaround of this > problem, in other words the RFTG thinks a gps week rollover must have > happened and tries to correct the date. > Have fun > Guido > > Von Samsung Mobile gesendet > > Alan Kamrowski II <ala...@earthlink.net> hat geschrieben: > > Hi Guido, > > Do you have any idea why the unit interprets the date 7168 (0x1c00) days into > the future? If I send it today's date in the correct Motorola format, this > is how many days it adds to it. If I change the date to try another, it does > the same thing. Any idea why? I can correct for it by subtracting 0x1c00 > days before sending it, this just seems very odd. > > Thanks, > > Alan > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
