GPS Units in Z3801A
I have a Z3801A that has lost contact with GPS. The GPS module is working -
the list of not-tracking satellites changes occasionally, but it never
tracks anything. I've tried swapping antennas and such but that hasn't
helped.
How often does the front end of the GPS module die?
Will the newer 8 channel modules work in the Z3801A or do I need to locate an
old 6 channel version?
Is there a tells-all web page or message to this list about GPS modules for
the Z3801A? I'd expect one, but I haven't found it.
I noticed that the UTC time from the status page is different from the T2
time.
T2201707100009039300141
The UTC clock seems to have gone crazy. From the status page:
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 01 Nov
2018
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 22 Aug
2019
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 19 Dec
2019
The T2 time is a day old. My guess is that it pulled the time it's using for
T2 from wherever it stores the log slots.
--
These are my opinions. I hate spam.
Hi
I’ve swapped out the GPS on a couple of them. Not 100% sure what went wrong.
Swapping out a cheap GPS was a pretty easy decision compared to trying to
board level troubleshoot an undocumented GPS. When the swap out fixed the problem,
I moved on.
Bob
On Jul 11, 2017, at 6:27 PM, Hal Murray hmurray@megapathdsl.net wrote:
I have a Z3801A that has lost contact with GPS. The GPS module is working -
the list of not-tracking satellites changes occasionally, but it never
tracks anything. I've tried swapping antennas and such but that hasn't
helped.
How often does the front end of the GPS module die?
Will the newer 8 channel modules work in the Z3801A or do I need to locate an
old 6 channel version?
Is there a tells-all web page or message to this list about GPS modules for
the Z3801A? I'd expect one, but I haven't found it.
I noticed that the UTC time from the status page is different from the T2
time.
T2201707100009039300141
The UTC clock seems to have gone crazy. From the status page:
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 01 Nov
2018
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 22 Aug
2019
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 19 Dec
2019
The T2 time is a day old. My guess is that it pulled the time it's using for
T2 from wherever it stores the log slots.
--
These are my opinions. I hate spam.
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.
Got this from a friend whose MN license plate is UNIX.
Begin copy of note
I'm curious if your friends on the time wizards mailing list have
noticed that an important moment in computer history approaches.
On Thursday night, 21:40 PM CST, it will be exactly 1.5 billion seconds
since Jan 1, 1970 UT, the Unix EPOCH. At that instant, billions of
Linux and Unix computers and devices, everywhere on the planet, will all
return time() == 1500000000. It will not be until 2033 when that number
reaches 2 Billion. The Thursday date is computed as follows:
% cat >epoch.c
#include <time.h>
#include <stdio.h>
#include <stdlib.h>
int main(int argc, char **argv) {
const time_t gsec = 1.5e9;
struct tm thursday = *localtime(&gsec);
char buf[100];
strftime(buf, sizeof(buf), "%m/%d/%y %H:%M:%S", &thursday);
printf("Epoch + 1.5B seconds = %s\n", buf);
return 0;
}
% gcc -Wall epoch.c
% ./a.out
Epoch + 1.5B seconds = 07/13/17 21:40:00
%
And if they haven't noticed, it might be a good time to point it out.
End copy of note
Some of us are impressed by long strings of zeros, so here I am,
pointing it out.
Bill Hawkins
In message F81132F1D0FB46429C7D5C2FA77F65C6@system072, "Bill Hawkins" writes:
On Thursday night, 21:40 PM CST, it will be exactly 1.5 billion seconds
since Jan 1, 1970 UT, the Unix EPOCH.
We threw a big "uptime(1)" party for the entire UNIX ecosystem
here in Denmark back when 1e9 seconds rolled around :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
Hi Bill,
Got this from a friend whose MN license plate is UNIX.
Join the club! There's ~50 of us in the US: http://leapsecond.com/pages/unix/
At that instant, billions of Linux and Unix computers and devices
Plus embedded devices, such as Arduino, where 31-bit time_t C libraries are also used...
return time() == 1500000000. It will not be until 2033 when that number reaches 2 Billion.
Thanks for the notice. Add these to your list:
1414213562 0x544b2fba Sat Oct 25 06:06:02 2014 GMT (sqrt 2)
1415926535 0x54655307 Fri Nov 14 00:55:35 2014 GMT (pi)
1420405752 0x54a9abf8 Sun Jan 04 21:09:12 2015 GMT (H-maser Hz)
1500000000 0x59682f00 Fri Jul 14 03:40:00 2017 GMT (1.5 billion)
1616161616 0x6054ab50 Fri Mar 19 13:46:56 2021 GMT (pretty in dec)
1616928864 0x60606060 Sun Mar 28 10:54:24 2021 GMT (pretty in hex)
1717171717 0x6659f605 Fri May 31 17:08:37 2024 GMT (dec looking like oct)
1886417008 0x70707070 Thu Oct 11 13:43:28 2029 GMT (pretty in hex)
1985229328 0x76543210 Sun Nov 28 04:35:28 2032 GMT (hex digit countdown)
2000000000 0x77359400 Wed May 18 04:33:20 2033 GMT (2 billion)
2004318071 0x77777777 Thu Jul 07 04:01:11 2033 GMT (pretty in hex)
2147483647 0x7fffffff Tue Jan 19 03:14:07 2038 GMT (end of time)
2147483648 0x80000000 Tue Jan 19 03:14:08 2038 GMT (you survived)
While we're at it, we have a rare T&F MJD event coming in 2023:
1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 2440000.5 = MJD 40000.0
1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 2450000.5 = MJD 50000.0
2023-02-25 00:00:00 UTC (DOY = 56, Sat) = JD 2460000.5 = MJD 60000.0
/tvb
My spouse's license plate is BEFUNGE.
On Wednesday, July 12, 2017, Tom Van Baak tvb@leapsecond.com wrote:
Hi Bill,
Got this from a friend whose MN license plate is UNIX.
Join the club! There's ~50 of us in the US: http://leapsecond.com/pages/
unix/
At that instant, billions of Linux and Unix computers and devices
Plus embedded devices, such as Arduino, where 31-bit time_t C libraries
are also used...
return time() == 1500000000. It will not be until 2033 when that number
reaches 2 Billion.
Thanks for the notice. Add these to your list:
1414213562 0x544b2fba Sat Oct 25 06:06:02 2014 GMT (sqrt 2)
1415926535 0x54655307 Fri Nov 14 00:55:35 2014 GMT (pi)
1420405752 0x54a9abf8 Sun Jan 04 21:09:12 2015 GMT (H-maser Hz)
1500000000 0x59682f00 Fri Jul 14 03:40:00 2017 GMT (1.5 billion)
1616161616 0x6054ab50 Fri Mar 19 13:46:56 2021 GMT (pretty in dec)
1616928864 0x60606060 Sun Mar 28 10:54:24 2021 GMT (pretty in hex)
1717171717 0x6659f605 Fri May 31 17:08:37 2024 GMT (dec looking like oct)
1886417008 0x70707070 Thu Oct 11 13:43:28 2029 GMT (pretty in hex)
1985229328 0x76543210 Sun Nov 28 04:35:28 2032 GMT (hex digit countdown)
2000000000 0x77359400 Wed May 18 04:33:20 2033 GMT (2 billion)
2004318071 0x77777777 Thu Jul 07 04:01:11 2033 GMT (pretty in hex)
2147483647 0x7fffffff Tue Jan 19 03:14:07 2038 GMT (end of time)
2147483648 0x80000000 Tue Jan 19 03:14:08 2038 GMT (you survived)
While we're at it, we have a rare T&F MJD event coming in 2023:
1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 2440000.5 = MJD 40000.0
1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 2450000.5 = MJD 50000.0
2023-02-25 00:00:00 UTC (DOY = 56, Sat) = JD 2460000.5 = MJD 60000.0
/tvb
time-nuts mailing list -- time-nuts@febo.com javascript:;
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
--
William H Fite, PhD
Independent Consultant
Statistical Analysis & Research Methods
Hi Tom
I passed this along to two of my old time computer gurus - I am sure they will want to celebrate!!
73,
Bill, WA2DVU
Cape May
-----Original Message-----
From: time-nuts [mailto:time-nuts-bounces@febo.com] On Behalf Of Tom Van Baak
Sent: Wednesday, July 12, 2017 8:19 AM
To: Discussion of precise time and frequency measurement time-nuts@febo.com
Subject: Re: [time-nuts] A milestone approaches
Hi Bill,
Got this from a friend whose MN license plate is UNIX.
Join the club! There's ~50 of us in the US: http://leapsecond.com/pages/unix/
At that instant, billions of Linux and Unix computers and devices
Plus embedded devices, such as Arduino, where 31-bit time_t C libraries are also used...
return time() == 1500000000. It will not be until 2033 when that number reaches 2 Billion.
Thanks for the notice. Add these to your list:
1414213562 0x544b2fba Sat Oct 25 06:06:02 2014 GMT (sqrt 2)
1415926535 0x54655307 Fri Nov 14 00:55:35 2014 GMT (pi)
1420405752 0x54a9abf8 Sun Jan 04 21:09:12 2015 GMT (H-maser Hz)
1500000000 0x59682f00 Fri Jul 14 03:40:00 2017 GMT (1.5 billion)
1616161616 0x6054ab50 Fri Mar 19 13:46:56 2021 GMT (pretty in dec)
1616928864 0x60606060 Sun Mar 28 10:54:24 2021 GMT (pretty in hex)
1717171717 0x6659f605 Fri May 31 17:08:37 2024 GMT (dec looking like oct)
1886417008 0x70707070 Thu Oct 11 13:43:28 2029 GMT (pretty in hex)
1985229328 0x76543210 Sun Nov 28 04:35:28 2032 GMT (hex digit countdown)
2000000000 0x77359400 Wed May 18 04:33:20 2033 GMT (2 billion)
2004318071 0x77777777 Thu Jul 07 04:01:11 2033 GMT (pretty in hex)
2147483647 0x7fffffff Tue Jan 19 03:14:07 2038 GMT (end of time)
2147483648 0x80000000 Tue Jan 19 03:14:08 2038 GMT (you survived)
While we're at it, we have a rare T&F MJD event coming in 2023:
1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 2440000.5 = MJD 40000.0
1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 2450000.5 = MJD 50000.0
2023-02-25 00:00:00 UTC (DOY = 56, Sat) = JD 2460000.5 = MJD 60000.0
/tvb
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.
I may have more of replacement Motorola GPS receiver modules. I had been
sorting out stuff in storage
and ran across some boxes that came from the same source the last batch
came from. It maybe a couple
weeks before I can find out. My dance card is pretty full for the next
couple weeks and weekends.
The pictures from last year
http://petelancashire.com/gallery/main.php?g2_itemId=5249
-pete
On Tue, Jul 11, 2017 at 3:27 PM, Hal Murray hmurray@megapathdsl.net wrote:
I have a Z3801A that has lost contact with GPS. The GPS module is working
the list of not-tracking satellites changes occasionally, but it never
tracks anything. I've tried swapping antennas and such but that hasn't
helped.
How often does the front end of the GPS module die?
Will the newer 8 channel modules work in the Z3801A or do I need to locate
an
old 6 channel version?
Is there a tells-all web page or message to this list about GPS modules for
the Z3801A? I'd expect one, but I haven't found it.
I noticed that the UTC time from the status page is different from the T2
time.
T2201707100009039300141
The UTC clock seems to have gone crazy. From the status page:
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 01 Nov
2018
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 22 Aug
2019
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 19 Dec
2019
The T2 time is a day old. My guess is that it pulled the time it's using
for
T2 from wherever it stores the log slots.
--
These are my opinions. I hate spam.
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.
Well that's handy to know, I've got a box of those I picked up from a
hamfest. I'll have to dig them out and test them
On 12 Jul 2017 2:55 pm, "Pete Lancashire" pete@petelancashire.com wrote:
I may have more of replacement Motorola GPS receiver modules. I had been
sorting out stuff in storage
and ran across some boxes that came from the same source the last batch
came from. It maybe a couple
weeks before I can find out. My dance card is pretty full for the next
couple weeks and weekends.
The pictures from last year
http://petelancashire.com/gallery/main.php?g2_itemId=5249
-pete
On Tue, Jul 11, 2017 at 3:27 PM, Hal Murray hmurray@megapathdsl.net
wrote:
I have a Z3801A that has lost contact with GPS. The GPS module is
working
the list of not-tracking satellites changes occasionally, but it never
tracks anything. I've tried swapping antennas and such but that hasn't
helped.
How often does the front end of the GPS module die?
Will the newer 8 channel modules work in the Z3801A or do I need to
locate
an
old 6 channel version?
Is there a tells-all web page or message to this list about GPS modules
for
the Z3801A? I'd expect one, but I haven't found it.
I noticed that the UTC time from the status page is different from the T2
time.
T2201707100009039300141
The UTC clock seems to have gone crazy. From the status page:
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 01
Nov
2018
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 22
Aug
2019
Tracking: 0 Not Tracking: 6 UTC 06:28:15 [?] 19
Dec
2019
The T2 time is a day old. My guess is that it pulled the time it's using
for
T2 from wherever it stores the log slots.
--
These are my opinions. I hate spam.
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.
2038 could be an "interesting" year - on the 22nd of April, the MJD hits
65535 (2^16-1) !
On 12 July 2017 at 13:19, Tom Van Baak tvb@leapsecond.com wrote:
Thanks for the notice. Add these to your list:
....
2147483648 0x80000000 Tue Jan 19 03:14:08 2038 GMT (you survived)
While we're at it, we have a rare T&F MJD event coming in 2023:
1968-05-24 00:00:00 UTC (DOY = 145, Fri) = JD 2440000.5 = MJD 40000.0
1995-10-10 00:00:00 UTC (DOY = 283, Tue) = JD 2450000.5 = MJD 50000.0
2023-02-25 00:00:00 UTC (DOY = 56, Sat) = JD 2460000.5 = MJD 60000.0
/tvb