[time-nuts] GPS PRN 32

2016-01-28 Thread Charles Curry
This just came in Air Force Official Press Release - GPS Ground System Anomaly On 26 January at 12:49 a.m. MST, the 2nd Space Operations Squadron at the 50th Space Wing, Schriever Air Force Base, Colo., verified users were experiencing GPS timing issues. Further investigation revealed an issue i

Re: [time-nuts] GPS PRN 32

2016-01-28 Thread Martin Burnicki
Magnus Danielson wrote: > Charles, > > Considering how the UTC parameters (IS-GPS-200H, Table 20-IX and section > 20.3.3.5.2.4) got upset for some of the SVNs, the correction from GPS > time (as corrected for that PRN) into UTC got a shift of almost 13,7 us. > As a GPS receiver receives informatio

Re: [time-nuts] GPS PRN 32

2016-01-27 Thread Magnus Danielson
Charles, Considering how the UTC parameters (IS-GPS-200H, Table 20-IX and section 20.3.3.5.2.4) got upset for some of the SVNs, the correction from GPS time (as corrected for that PRN) into UTC got a shift of almost 13,7 us. As a GPS receiver receives information, solves for position and time

[time-nuts] GPS PRN 32

2016-01-27 Thread Charles Curry
Update on PRN 32 / SVN 23 According to the NANU this was decommissioned at 22:00 on the 25th. It was 25 years old http://archive.is/a8GI Some timing receivers experienced problems, some did not. Don't know why that is yet. So far our count is 8 different GPS timing receivers experiencing probl

Re: [time-nuts] GPS PRN 32

2016-01-26 Thread Charles Steinmetz
Magnus wrote: Interestingly enough they did not experience issues at the same time, it just started about the same time. Presumably, each rx would be affected when it added one or more corrupted satellites to the constellation it was using for its solution. Since each rx makes those decisio

Re: [time-nuts] GPS PRN 32

2016-01-26 Thread Magnus Danielson
Hi, It seems that several SVNs (PRN 2, 6, 7, 9 and 23) got feed bad data. This is not the first instance, it seems that single SVNs have had bad data the last couple of days. When our 4 GPS receivers at work got "hit" at midnight, it got our attention. Interestingly enough they did not exper

Re: [time-nuts] GPS PRN 32

2016-01-26 Thread Charles Curry
Tom This is what I sent unchecked Rich Text (HTML) now Has anyone noticed GPS problems today? It looks like PRN32 / SVN 23 went faulty yesterday and was taken out of service last night at 22:00 ZULU http://www.navcen.uscg.gov/?Do=gpsShowNanu&num=2016008 We've seen issues with a number of

Re: [time-nuts] GPS PRN 32

2008-02-11 Thread Tom Van Baak
> One more comment on this, SV 32/PRN 32 was briefly in use in 1992-3. > > "SV-32 has been active since Dec 11. [1992]" - > http://igscb.jpl.nasa.gov/mail/igsreport/1992/msg00054.html > > "On 28 January (day 028) [1993], SV-32's PRN number has been changed > from PRN#32 to PRN#01 sometimes bet

Re: [time-nuts] GPS PRN 32

2008-02-11 Thread Mike S
One more comment on this, SV 32/PRN 32 was briefly in use in 1992-3. "SV-32 has been active since Dec 11. [1992]" - http://igscb.jpl.nasa.gov/mail/igsreport/1992/msg00054.html "On 28 January (day 028) [1993], SV-32's PRN number has been changed from PRN#32 to PRN#01 sometimes between UTC 20:55

Re: [time-nuts] GPS PRN 32

2008-02-10 Thread Magnus Danielson
From: [EMAIL PROTECTED] (Mike S) Subject: Re: [time-nuts] GPS PRN 32 Date: Sat, 09 Feb 2008 21:52:59 -0500 Message-ID: <[EMAIL PROTECTED]> > At 07:42 PM 2/9/2008, Bruce Griffiths wrote... > >The Jupiter documentation indicates that PRN range is 1-32 with 0 used > >to in

Re: [time-nuts] GPS PRN 32

2008-02-09 Thread Mike S
At 07:42 PM 2/9/2008, Bruce Griffiths wrote... >The Jupiter documentation indicates that PRN range is 1-32 with 0 used >to indicate all satellites. You should be good, then, since the developers obviously accommodated a PRN 32. The statement quoted from the original article ("GPS receivers init

Re: [time-nuts] GPS PRN 32

2008-02-09 Thread Bruce Griffiths
The Novatel Superstar GPS receiver should also be OK for receiving PRN32. The supplied software has provision for monitoring the health of all 32 possible satellites. It also has provision for selectively ignoring any of the 32 possible satellites. Bruce __

Re: [time-nuts] GPS PRN 32

2008-02-09 Thread Tom Van Baak
> The Jupiter documentation indicates that PRN range is 1-32 with 0 used > to indicate all satellites. > So you may have some luck with that receiver. > > Bruce Bruce, An actual test is in order, of course, but speaking as a software engineer, anytime you hear "0 indicates all" and "1 to 32" it'

Re: [time-nuts] GPS PRN 32

2008-02-09 Thread Bruce Griffiths
Chris Kuethe wrote: > On Feb 8, 2008 2:07 PM, Bruce Griffiths <[EMAIL PROTECTED]> wrote: > >> My Z3815A sees PRN 32 now albeit as unhealthy. >> > > My Ublox AEK-4T has an almanac for PRN32, but no ephemeris (duh.) > > haven't tried my AC12, Lassen iQ, itrax03, gps18/lvc, UT+, GT+ or Jupiter

Re: [time-nuts] GPS PRN 32

2008-02-09 Thread Chris Kuethe
On Feb 8, 2008 2:07 PM, Bruce Griffiths <[EMAIL PROTECTED]> wrote: > My Z3815A sees PRN 32 now albeit as unhealthy. My Ublox AEK-4T has an almanac for PRN32, but no ephemeris (duh.) haven't tried my AC12, Lassen iQ, itrax03, gps18/lvc, UT+, GT+ or Jupiter yet... CK -- GDB has a 'break' feature

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Bruce Griffiths
Bruce Griffiths wrote: > Poul-Henning Kamp wrote: > >> In message <[EMAIL PROTECTED]>, Bruce Griffiths writes: >> >> >>> Bruce Griffiths wrote: >>> >>> Tom My Z3815A sees PRN 32 now albeit as unhealthy. Bruce >>>

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Dan Rae
My Thunderbolt (nor any of the others, of course) cannot see this one at present, but TBolt Mon is showing a yellow button indicating "incomplete or incorrect almanac". So it knows something's up! dr ___ time-nuts mailing list -- time-nuts@febo.com

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Bruce Griffiths
Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Bruce Griffiths writes: > >> Bruce Griffiths wrote: >> >>> Tom >>> >>> My Z3815A sees PRN 32 now albeit as unhealthy. >>> >>> Bruce >>> >>> >>> >> My M12+ T doesn't see SVN 23 (PRN32) although its shares the same antenna.

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Bruce Griffiths
Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Bruce Griffiths writes: > >> Bruce Griffiths wrote: >> >>> Tom >>> >>> My Z3815A sees PRN 32 now albeit as unhealthy. >>> >>> Bruce >>> >>> >>> >> My M12+ T doesn't see SVN 23 (PRN32) although its shares the same antenna.

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Bruce Griffiths writes: >Bruce Griffiths wrote: >> Tom >> >> My Z3815A sees PRN 32 now albeit as unhealthy. >> >> Bruce >> >> >My M12+ T doesn't see SVN 23 (PRN32) although its shares the same antenna. By default the M12 will not track an unhealty satellite if it

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Bruce Griffiths
Bruce Griffiths wrote: > Tom > > My Z3815A sees PRN 32 now albeit as unhealthy. > > Bruce > > My M12+ T doesn't see SVN 23 (PRN32) although its shares the same antenna. Bruce ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to http

Re: [time-nuts] GPS PRN 32

2008-02-08 Thread Bruce Griffiths
Tom Van Baak wrote: > Which time-nut will be the first to see PRN 32 on Feb 19? > I wonder what old GPS receivers won't be able to see it? > > This is from GPS World via NavtechGPS News... > > > "The U.S. military announced earlier this week that GPS satellite SVN23, > transmitting L-band code

[time-nuts] GPS PRN 32

2008-02-08 Thread Tom Van Baak
Which time-nut will be the first to see PRN 32 on Feb 19? I wonder what old GPS receivers won't be able to see it? This is from GPS World via NavtechGPS News... "The U.S. military announced earlier this week that GPS satellite SVN23, transmitting L-band code as PRN32, will be set to usable s