Sorry, Ulli, if I'm not quite with it, today...
Which one is the bad guy now, the oven or the RX? We can't decide that,
can we? IMHO does neither the EFC nor the PPS TI response tell us,
whether the RX or the Crystal caused this peak, what we see is just the
difference time between them.
Or does the time constant reveal more?
Thank you
Volker
Am 29.11.2012 08:28, schrieb Ulrich Bangert:
Volker,
please note that much of the clear text in the status information is
generated by Z38XX itself to make it easier to read.
2012-11-28 10:01:40: The last Smartclock Status is undefined
2012-11-28 10:01:40: Starting with status LOCK
for example means that Z38XX is unaware of the receiver status and assumes
that the status is locked.
73s de Ulli, DF6JB
-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Volker Esper
Gesendet: Mittwoch, 28. November 2012 22:24
An: Discussion of precise time and frequency measurement
Betreff: [time-nuts] Z3805 incident
When looking at the PPS TI vs. time curve today I felt kind
of appalled
- a big incident peak (not an outlier) on the curve! See picture.
What happened to my Z3805? Any idea?
No entry in the error log, the staus log says
2012-11-28 10:01:30: The Smartclock Status has changed to LOC
2012-11-28 10:01:40: The last Smartclock Status is undefined
2012-11-28 10:01:40: Starting with status LOCK
Thanks
Volker
_______________________________________________
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.
