Forcing the date on power up worked, although a bit strangely. I entered "2013,01,14" and got an "out of range" error. The date then showed as "14 Jan 2007" briefly, before showing "14 Jan 2013".
Joe Gray W5JG On Sun, Jan 13, 2013 at 9:17 PM, Joseph Gray <[email protected]> wrote: > I just tried manually putting the unit into holdover and setting the > date. Same error. I'll have to try power cycling. > > Joe Gray > W5JG > > On Sun, Jan 13, 2013 at 8:57 PM, Hal Murray <[email protected]> wrote: >> >> [email protected] said: >>> I did that command earlier, but got an error. I just tried it again and I >>> get the same error: >> >>> -221 "Settings conflict" >> >> I don't remember any troubles. I wasn't using anything complicated like >> SatStat. >> >> You might have to set the time when it doesn't know it. Try power cycling >> and set the time before it finds the satellites and time. >> >> >> -- >> These are my opinions. I hate spam. >> >> >> >> >> _______________________________________________ >> 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.
