[time-nuts] Re: TAPR TIC: TimeLab mode question (John Ackermann N8UR)

John Ackermann N8UR jra at febo.com
Thu Mar 18 13:08:42 UTC 2021


Hi Christophe and Matthias --

The "TimeLab" mode code was broken with the seemingly-minor change in 
the 2020 version of allowing varyiable numbers of decimal places in the 
results (with the default of 11) I had to rework the TimeLab mode code 
and I screwed it up.

I spent some time on this last week and have implemented a hopefully 
much simpler and cleaner routine that will work properly. 
Unfortunately, I had to go out of town and won't be able to test the 
changes until I get back later next week.  I'll post a note to the list 
when I've done that and a new binary version is available.

Sorry for the regression.

John
----

On 3/18/21 6:11 AM, Christoph Guenther via time-nuts wrote:
> Hi John, hi Matthias
> 
> I have the same problem with the channel C output of the TICC with the
> latest firmware.
> John, we already had direct email contact therefore from the end of April
> to early May 2020. I had already tested all available versions in
> conjunction with Timelab. Here are the data with version 2017, which in my
> opinion works hard-free, but without the improvements in recent versions.
> 
> # TAPR TICC Timestamping Counter
> 
> # Copyright 2017 N8UR, K9TRG, NH6Z, WA8YWQ
> 
> #####################
> # TICC Configuration:
> # Measurement Mode: TimeLab 3-channel
> Debug
> 
> # EEPROM Version: 7, Board Version: D
> 
> # Software Version: 20170108.1
> 
> # Board Serial Number: 1FBD4D12
> 
> # Clock Speed: 10000000
> 
> # Coarse tick (ps): 100000000
> 
> # Cal Periods: 20
> 
> # SyncMode: M
> 
> # Timeout: 0x04
> 
> # Time Dilation: 2500 (chA), 2500 (chB)
> 
> # FIXED_TIME2: 1283 (chA), 1256 (chB)
> 
> # FUDGE0: 0 (chA), 360 (chB)
> 
> #####################
> 
> # Type any character for config menu
> 
> # ............................
> 
> 
> # timestamp chA, chB; interval chA->B (seconds)
> 
> 1.533148076819 chA
> 
> 1.533148080106 chB
> 
> 2.000000003286 chC (B-A)
> 
> 2.533148076981 chA
> 
> 2.533148080163 chB
> 
> 3.000000003181 chC (B-A)
> 
> 3.533148077646 chA
> 
> 3.533148080380 chB
> 
> 4.000000002733 chC (B-A)
> 
> 4.533148078019 chA
> 
> 4.533148080491 chB
> 
> 5.000000002471 chC (B-A)
> 
> 5.533148077533 chA
> 
> 5.533148080328 chB
> 
> 6.000000002794 chC (B-A)
> 
> 6.533148077378 chA
> 
> 6.533148080264 chB
> 
> 7.000000002885 chC (B-A)
> 
> 7.533148077413 chA
> 
> 7.533148080327 chB
> 
> 8.000000002913 chC (B-A)
> 
> 8.533148077962 chA
> 
> 8.533148080590 chB
> 
> 9.000000002627 chC (B-A)
> 
> Did other time-nuts have found this problem and possibly a solution?
> It would be great if John would process the problem again.
> Many Thanks
> 
> Best regards,
> Christoph
> 
> 
> 
> 
> 
> 
>> Message: 4
>> Date: Sun, 14 Mar 2021 14:51:58 -0400
>> From: John Ackermann N8UR <jra at febo.com>
>> Subject: [time-nuts] Re: TAPR TIC: TimeLab mode question
>> To: time-nuts at lists.febo.com
>> Message-ID: <a34bc5e0-4cf0-14c7-8741-bab539a2ac66 at febo.com>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> Hi Matthias --
>>
>> I just took a look at the source and the "Debug" is meaningless...
>> stupid program error (missing a "break" in a case statement) caused that
>> to be printed when it shouldn't be.  Easy fix.
>>
>> But why you're seeing the bogus chC results will take a little more
>> investigation.  I suspect it's something that broke when I made changes
>> to the print routine in the latest version.  I'll see if I can figure it
>> out, and if/when I do I'll push changes to the github repository.
>>
>> Thanks for letting me know about the problems!
>>
>> John
>> ----
>>
>> On 3/14/21 5:29 AM, Matthias Jelen wrote:
>>> Hello Time-Nuts,
>>>
>>> after I finally managed to get my TAPR TIC into a case,
>>> together with two 1PPS dividers, I wanted to give the 3
>>> channel measurement a try. I remember that I successfully
>>> used the TimeLab mode some years ago, but this time I can´t
>>> get it to work. I installed the lasted firmware (binary from
>>> github).
>>>
>>> Channel A and B work fine, but the (B-A) doens´t seem to be
>>> calculated - see output from TIC below.
>>>
>>> Should the line reading "debug" in the TIC Configuration
>>> make me nervous?
>>>
>>> Any help highly appreciated...
>>>
>>> Thanks & have a nice weekend,
>>>
>>> Matthias
>>>
>>> # TAPR TICC Timestamping Counter
>>> # Copyright 2016-2020 N8UR, K9TRV, NH6Z, WA8YWQ
>>>
>>> #####################
>>> # TICC Configuration:
>>> # Measurement Mode: TimeLab 3-channel
>>> Debug
>>> # Poll Character: none
>>> # EEPROM Version: 10, Board Version: D
>>> # Software Version: 20200412.1
>>> # Board Serial Number: A92D670B
>>> # Clock Speed: 10.000000 MHz
>>> # Coarse tick: 100.000000 usec
>>> # Cal Periods: 20
>>> # Timestamp Wrap:  0
>>> # SyncMode: M
>>> # Ch Names: A/B
>>> # PropDelay: 0 (ch0), 0 (ch1)
>>> # Timeout: 0x05
>>> # Trigger Edge: R (ch0), R (ch1)
>>> # Time Dilation: 2500 (ch0), 2500 (ch1)
>>> # FIXED_TIME2: 0 (ch0), 0 (ch1)
>>> # FUDGE0: 0 (ch0), 0 (ch1)
>>> #####################
>>>
>>> # Type any character for config menu
>>> # ............................
>>>
>>> # timestamp chA, chB; interval chA->B (seconds with 11
>>> decimal places)
>>> 1.14527049228 A
>>> 0.16498914776 B
>>> 2.00000000001chC (B-A)
>>> 2.14527049186 A
>>> 1.16498914789 B
>>> 3.00000000001chC (B-A)
>>> 3.14527049132 A
>>> 2.16498914799 B
>>> 4.00000000001chC (B-A)
>>> 4.14527049068 A
>>> 3.16498914839 B
>>> 5.00000000001chC (B-A)
>>> 5.14527049019 A
>>> 4.16498914834 B
>>> 6.00000000001chC (B-A)
>>> 6.14527048961 A
>>> 5.16498914850 B
>>> 7.00000000001chC (B-A)
>>> 7.14527048907 A
>>> 6.16498914865 B
>>> 8.00000000001chC (B-A)
>>> 8.14527048859 A
>>> 7.16498914890 B
>>> 9.00000000001chC (B-A)
>>> 9.14527048800 A
>>> 8.16498914895 B
>>> 10.00000000001chC (B-A)
>>> 10.14527048751 A
>>> 9.16498914913 B
>>> 11.00000000001chC (B-A)
>>> 11.14527048687 A
>>> 10.16498914928 B
>>> 12.00000000001chC (B-A)
>>> 12.14527048644 A
>>> 11.16498914941 B
>>> 13.00000000001chC (B-A)
>>> 13.14527048602 A
>>> 12.16498914966 B
>>> 14.00000000001chC (B-A
>>>
>>
>>
>>
> _______________________________________________
> time-nuts mailing list -- time-nuts at lists.febo.com -- To unsubscribe send an email to time-nuts-leave at lists.febo.com
> To unsubscribe, go to and follow the instructions there.
> 




More information about the Time-nuts_lists.febo.com mailing list