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 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
> 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 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 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
>
> #
>
> # towpps(sec) osc(
>> ppb)
> dac(V) temp(C) sats
>
> 14:27:28 224866 -8.51365e-008-0.023564
> 1.196032 42.6603588
>
>
>
> [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
>