[time-nuts] Strange problem with LH 5.0
If you can build the code (probably just Linux users), I can send you the latest source code to try. Probably a couple of months before the public release. I am currently adding support for the TAPR TICC (or other time interval counters) and also the HP5071A cesium beam oscillator. The TICC/counter can be used as either the main input device instead of a GPS unit or as an auxiliary input device for calculating true adevs from a receiver instead of the "bogo-adevs" derived from the GPSDO's self referenced loop parameters. Speaking of bogo-adevs... I fixed up the adev code and the Tbolt bogo-adevs now agree remarkably well to the TICC derived values. The OSC adevs are almost a perfect match. The PPS adevs diverge a little bit below tau=30. Z3801A bogo-adevs are within a factor of 2 of the true adevs, but Heather can only fetch the receiver TINTerval values every 10 seconds so Z3801A derived bogo-adves have a minimum tau of 10 seconds. -- > Any idea when the next release will be out? ___ 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.
Re: [time-nuts] Strange problem with LH 5.0
Thanks for that info--I feel better now about my setup! Any idea when the next release will be out? Regards, Stan -Original Message- At 33 seconds past the minute Heather requests the SYST:STATUS? info from SCPI receivers which takes 3 seconds for the device to send. The clock does not update while Heather is reading the status info because the receiver is not sending any time messages. The next release "fakes" the missing seconds so the clocks appear to keep ticking even though the receiver is not sending time codes. -- ___ 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] Strange problem with LH 5.0
At 33 seconds past the minute Heather requests the SYST:STATUS? info from SCPI receivers which takes 3 seconds for the device to send. The clock does not update while Heather is reading the status info because the receiver is not sending any time messages. The next release "fakes" the missing seconds so the clocks appear to keep ticking even though the receiver is not sending time codes. ___ 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] Strange problem with LH 5.0
Hello, I am running Lady Heather 5.0 on my Win 7 PC, connected to an HP 58503A through a dedicated hardware serial port. Everything seems to be working and updating as it should, EXCEPT every minute at the 33 second mark, the window freezes and nothing updates until the 37 second mark, then everything updates once a second as it should until the next 33 second mark. I've looked at the Win 7 clock and run SatStat, and both count smoothly and update every second. I'm hoping it's just a configuration issue with LH, but I'm not sure. Everything else about LH seems to be working as it should. Any ideas? Thanks, Stan ___ 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.
