Hi Bob, Mark, Tom, Thank you so much for your advice and support. My TBolt is fine. Using Bob's suggestion of a serial Y cable and 2 PC's running LH... I had one PC crash with evolving gibberish on the LH screen while the other PC running LH showed stable solid performance. So it either is a bad serial cable or more likely the Prolific adapter. I am now swapping to see which.
Jerry, NY2KW -----Original Message----- From: time-nuts [mailto:time-nuts-boun...@febo.com] On Behalf Of Bob kb8tq Sent: Wednesday, August 30, 2017 1:43 PM To: Discussion of precise time and frequency measurement <time-nuts@febo.com> Subject: Re: [time-nuts] Bad TBolt Crashing LH? - NOT TBOLT Hi I’d just set up your favorite terminal program (PUTTY or whatever ) on the second PC and let it do a log file to disk. Then go back and look at the “problem time”. If all of a sudden the lines are half as long or twice as long as they should be …. you found the problem. The kind of stuff that a defective serial port does is rarely subtle …. Bob > On Aug 30, 2017, at 12:26 PM, Jerry <jster...@att.net> wrote: > > Hi Bob, > > I have a Y 9pin serial splitter somewhere. When you say log do you mean > using LH to write a raw file on both PC's simultaneously? Is serial comm > between LH and PC all receive only - no handshaking that would get messed up > with a split Y serial cable? > > Jerry, NY2KW > > -----Original Message----- > From: time-nuts [mailto:time-nuts-boun...@febo.com] On Behalf Of Bob > kb8tq > Sent: Wednesday, August 30, 2017 11:20 AM > To: Discussion of precise time and frequency measurement > <time-nuts@febo.com> > Subject: Re: [time-nuts] Bad TBolt Crashing LH? > > Hi > > If you have a second PC, there’s a real quick shortcut. > > Make up a Y cable and log the output of the TBolt on the second machine. If > the TBolt really *is* sending junk, you’ll see it. If not, the TBolt is ok. > Swap the machine that is logging, if the same thing is still true, it’s not > the TBolt and it’s not the serial “stuff”. > > Bob > >> On Aug 30, 2017, at 8:52 AM, Jerry Stern <jster...@att.net> wrote: >> >> Thanks Ken, yea that was fun until i read aboit disabling it. >> Unfortunately not the problem. I swapped PC's and still happening so >> i am ledt with power supply, usb-serial adapter or Tbolt problems. >> In process of elimination now >> >> Jerry >> >> Sent from my iPhone >> >>> On Aug 30, 2017, at 6:35 AM, Ken Winterling <wa2...@gmail.com> wrote: >>> >>> You also want to disable the "Microsoft Serial BallPoint" mouse in >>> Windows Device Manager. If left enabled it causes your mouse >>> pointer to jump all over the screen every time the TBOLT sends data >>> to the computer; about once/second. That was "fun" the first time I >>> encountered it. It looks like your PC has been infected with a virus. >>> >>> Ken >>> WA2LBI >>> >>> >>> >>> >>> On Wed, Aug 30, 2017 at 4:28 AM, Stephen Tompsett >>> <step...@tompsett.net> >>> wrote: >>> >>>> For FTDI serial ports, in addition to ensuring that USB suspend is >>>> disabled in advanced power properties, it's worth disabling Serial >>>> Port Enumeration in the advanced properties for the com port. This >>>> will help prevent FTDI ports with data being gratuitously sent to >>>> them from being assumed to be a mouse or pointing device; >>>> Unfortunately this setting gets reset following most significant >>>> Windows updates, so you get used to clearing the setting every couple of >>>> months... >>>> >>>> >>>>> On 29/08/2017 19:28, Jerry wrote: >>>>> Thanks to all. I am using a high end laptop running Windows 7 Pro, >>>>> power >>>> settings are all max'ed for performance - no sleep modes. I >>>> thought it had a direct DB-9 serial but it does not so have to use >>>> an adapter. I have 3 different manufacturers USB-Serial but all >>>> use Prolific which I heard has counterfeits and driver problems. I >>>> just ordered an FTDI type recommended for my Flex radio. Fingers crossed >>>> not the TBolt. >>>>> >>>>> 73 >>>>> Jerry, NY2KW >>>>> >>>>> -----Original Message----- >>>>> From: time-nuts [mailto:time-nuts-boun...@febo.com] On Behalf Of >>>>> Ken >>>> Winterling >>>>> Sent: Tuesday, August 29, 2017 12:52 PM >>>>> To: Discussion of precise time and frequency measurement < >>>> time-nuts@febo.com> >>>>> Subject: Re: [time-nuts] Bad TBolt Crashing LH? >>>>> >>>>> Jerry, >>>>> >>>>> I agree, if you have a "real" RS-232 port available use it to >>>>> check if >>>> the TBOLT and LH communicate. If that works, then USB adapter is suspect. >>>>> Prolific has been problematic. When I had problems with my >>>>> Prolific >>>> adapters failing, usually after an "update" - particularly Windows >>>> - I switched to FTDI adapters and have never had a problem since. >>>>> >>>>> Ken >>>>> WA2LBI >>>>> >>>>> >>>>> >>>>> >>>>>> On Tue, Aug 29, 2017 at 12:38 PM, Jerry <jster...@att.net> wrote: >>>>>> >>>>>> Hi Bob, >>>>>> >>>>>> Thanks for the suggestions. I am using a Quadtech SS-100 direct >>>>>> USB-Serial cable with Prolific drivers as a direct connect from >>>>>> TBolt to PC. Maybe I should try a direct serial to serial >>>>>> without the USB >>>> adapter. >>>>>> If still an issue then I will reflow the DB9 connector in the TBolt. >>>>>> >>>>>> 73 >>>>>> Jerry, NY2KW >>>>>> >>>>>> -----Original Message----- >>>>>> From: time-nuts [mailto:time-nuts-boun...@febo.com] On Behalf Of >>>>>> Bob kb8tq >>>>>> Sent: Tuesday, August 29, 2017 12:08 PM >>>>>> To: Discussion of precise time and frequency measurement < >>>>>> time-nuts@febo.com> >>>>>> Subject: Re: [time-nuts] Bad TBolt Crashing LH? >>>>>> >>>>>> Hi >>>>>> >>>>>> I would blame the usual “coms error” stuff and dig into that. Bum >>>>>> cable / loose cable is number one on that list. Connectors (on >>>>>> either >>>>>> end) coming unsoldered from the pc board would be next …. >>>>>> >>>>>> Bob >>>>>> >>>>>>> On Aug 29, 2017, at 10:30 AM, Jerry <jster...@att.net> wrote: >>>>>>> >>>>>>> Need some more help figuring out why Lady Heather keeps crashing. >>>>>>> I think it may be a flaky Thunderbolt but I only own one. The >>>>>>> PC is an >>>>>>> i5 Intel with 8Gb memory and nothing running in background. The >>>>>>> log sequence before crash is first time stamp erros where the >>>>>>> log shows within 1 sec the TBolt jumps from 6 or 7 Sats to zero. >>>>>>> Then after a few more timestamp errors, the date gets corrupted >>>>>>> ending with bad RAM, Bad Osc, etc. If I open LH again (and do >>>>>>> nothing to the TBolt) >>>>>>> - everything looks good again for about 10-15 minutes and it all >>>>>>> repeats >>>>>> again. >>>>>>> >>>>>>> >>>>>>> This log began with: >>>>>>> >>>>>>> >>>>>>> >>>>>>> # 14:27:28.000 UTC 29 Aug 2017 - interval 1 seconds >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # tow pps(sec) osc( >>>> ppb) >>>>>>> dac(V) temp(C) sats >>>>>>> >>>>>>> 14:27:28 224866 -8.51365e-008 -0.023564 >>>>>>> 1.196032 42.660358 8 >>>>>>> >>>>>>> >>>>>>> >>>>>>> [similar as line above.....for about 10-15 mins] >>>>>>> >>>>>>> >>>>>>> >>>>>>> After skipping some time stamps it becomes: >>>>>>> >>>>>>> >>>>>>> >>>>>>> # 09:39:47.000 UTC 07 Mar 2019 - interval 1 seconds >>>>>>> >>>>>>> >>>>>>> >>>>>>> Then it goes back to current UTC sometimes with 7 Sats some >>>>>>> errors on >>>>>>> 0 or 3 >>>>>>> Sats: >>>>>>> >>>>>>> >>>>>>> >>>>>>> #! time stamp skipped. t=229340387000.000 >>>>>>> last=181406402001.000 >>>>>>> err:47933984999 ms >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # 09:39:47.000 UTC 07 Mar 2019 - interval 1 seconds >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # tow pps(sec) osc( >>>> ppb) >>>>>>> dac(V) temp(C) sats >>>>>>> >>>>>>> 09:39:47 225605 -8.1407e-008 0.110356 >>>>>>> 1.196165 42.362377 7 >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # 14:39:50.000 UTC 29 Aug 2017 - interval 1 seconds >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # tow pps(sec) osc( >>>> ppb) >>>>>>> dac(V) temp(C) sats >>>>>>> >>>>>>> 14:39:50 225608 -8.08732e-008 0.106356 >>>>>>> 1.196165 83.500000 0 >>>>>>> >>>>>>> #! time stamp skipped. t=181406392001.000 >>>>>>> last=181406390000.000 >>>>>>> err:2001 ms >>>>>>> >>>>>>> >>>>>>> >>>>>>> Then it goes into 'new receiver mode' and then 'new discipline mode' >>>>>>> while >>>>>>> 3-7 Sats are visible. This goes on for another few minutes >>>>>>> until finally it shows a series of further corruptions, with >>>>>>> minor alarms >>>>>> ending : >>>>>>> #! year error: 60404 >>>>>>> >>>>>>> #! time stamp skipped. t=1601332636481001.000 >>>>>>> last=181406509000.000 >>>>>>> err:1601151229972001 ms >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # 13:14:41.001 GPS 15 Feb 52756 - interval 1 seconds >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # tow pps(sec) osc( >>>> ppb) >>>>>>> dac(V) temp(C) sats >>>>>>> >>>>>>> 13:14:41 225728 -6.68514e-008 0.141315 >>>>>>> 1.196117 42.588669 5 >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # 14:41:58.001 UTC 29 Aug 2017 - interval 1 seconds >>>>>>> >>>>>>> # >>>>>>> >>>>>>> # tow pps(sec) osc( >>>> ppb) >>>>>>> dac(V) temp(C) sats >>>>>>> >>>>>>> 14:41:58 225736 -6.60375e-008 0.094983 >>>>>>> 1.185647 42.588669 0 >>>>>>> >>>>>>> #! year error: 1814 >>>>>>> >>>>>>> #! time stamp skipped. t=-6224635078999.000 >>>>>>> last=181406518001.000 >>>>>>> err:-6406041597000 ms >>>>>>> >>>>>>> 14:42:01 5898563 -1.49314e+006 -0.000000 >>>>>> 1.196108 >>>>>>> 42.278618 0 >>>>>>> >>>>>>> #! new gps status: TRAIM rejected fix: at tow 5898563 >>>>>>> >>>>>>> #! new discipline state: ?0B?: at tow 5898563 >>>>>>> >>>>>>> #! new minor alarm state 00E7: OSC age alarm Antenna open Survey >>>>>>> started No saved posn LEAP PENDING! : at tow 5898563 >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> .. >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> 14:43:27 225825 -5.45551e-008 0.064319 >>>>>>> 1.196070 40.071625 5 >>>>>>> >>>>>>> #! new critical alarm state AC00: : at tow 225825 >>>>>>> >>>>>>> #! new minor alarm state 0000: OSC age normal Antenna OK >>>> Discipline >>>>>> OK >>>>>>> Normal op mode Saved posn OK EEPROM data OK Almanac OK : at >>>> tow >>>>>>> 225825 >>>>>>> >>>>>>> 14:43:27 225825 -5.44649e-008 0.071280 >>>>>>> 1.196070 44.131538 5 >>>>>>> >>>>>>> #! new critical alarm state B375: ROM:BAD Power:BAD OSC: BAD: at >>>> tow >>>>>>> 225825 >>>>>>> >>>>>>> #! year error: 21719 >>>>>>> >>>>>>> #! year error: 45931 >>>>>>> >>>>>>> #! year error: 45932 >>>>>>> >>>>>>> #! year error: 11276 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks in advance for any help >>>>>>> >>>>>>> >>>>>>> >>>>>>> Jerry NY2KW >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 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 mailing list -- time-nuts@febo.com To unsubscribe, go >>>>>> to https://www.febo.com/cgi-bin/m ailman/listinfo/time-nuts and >>>>>> follow the instructions there. >>>>>> >>>>> _______________________________________________ >>>>> 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 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. >>>>> >>>> >>>> -- >>>> Stephen Tompsett >>>> >>>> _______________________________________________ >>>> 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 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 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 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 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 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 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.
