Re: [time-nuts] TICC / TimeLab fun

2020-04-30 Thread Taka Kamiya via time-nuts
I can concur with this.  When I have to measure 2 inputs using TICC, I always use lady heather for this reason.  Either that dump TICC output into a text file, check it first, then feed it into other tools.  --- (Mr.) Taka Kamiya KB4EMF / ex JF2DKG

[time-nuts] TICC / TimeLab fun

2020-04-29 Thread Mark Sims
Lady Heather's TICC parser does not expect alternating ABAB readings and handles the ABAB vs ABBA situation properly. ___ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to

Re: [time-nuts] TICC / TimeLab fun

2020-04-29 Thread Bob kb8tq
Hi You have three inputs to the TICC: 1) The “frequency standard” input that delivers 10 MHz to the device. 2) The (likely pps) to channel A 3) the (likely also pps) to channel B The device runs a continuous time count based on the frequency standard input. Each edge it sees on channel A

Re: [time-nuts] TICC / TimeLab fun

2020-04-29 Thread John Moran, Scawby Design
Chris I don't have any of that kit yet but it seems to me that the two units have locked to each other somehow, a bit like the question I raised a while ago about crystals locking to each other. Just a pure guess though. John ___ time-nuts mailing

Re: [time-nuts] TICC / TimeLab fun

2020-04-29 Thread John Ackermann N8UR
Hi Chris -- Two possibilities: 1. Make sure you have TimeLab set for the correct mode (timestamp vs time interval), for two channels, and for the right scaling factor (for timestamps, scale by 1). Any of those can cause 1e0-type results. 2. If the two channels have timestamps that are within