time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

Re: [time-nuts] Bad TBolt Crashing LH?

Dave B

Tue, Aug 29, 2017 4:41 PM

Windows or ???

If Windows, check the OS's power settings, and make sure that it's not
sending peripherals to sleep after a period of "Inactivity" (judged by a
lack of keyboard/mouse activity, NOT the existence of any running
programs, or screen updates.)

Regards.

Dave B.

On 29/08/17 17:00, time-nuts-request@febo.com wrote:

Message: 1
Date: Tue, 29 Aug 2017 11:30:46 -0400
From: "Jerry" jsternmd@att.net
To: "Discussion of precise time and frequency measurement"
time-nuts@febo.com
Subject: [time-nuts] Bad TBolt Crashing LH?
Message-ID: 008901d320db$cb616240$622426c0$@att.net
Content-Type: text/plain; charset="us-ascii"

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

Windows or ??? If Windows, check the OS's power settings, and make sure that it's not sending peripherals to sleep after a period of "Inactivity" (judged by a lack of keyboard/mouse activity, NOT the existence of any running programs, or screen updates.) Regards. Dave B. On 29/08/17 17:00, time-nuts-request@febo.com wrote: > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 29 Aug 2017 11:30:46 -0400 > From: "Jerry" <jsternmd@att.net> > To: "Discussion of precise time and frequency measurement" > <time-nuts@febo.com> > Subject: [time-nuts] Bad TBolt Crashing LH? > Message-ID: <008901d320db$cb616240$622426c0$@att.net> > Content-Type: text/plain; charset="us-ascii" > > 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 > >