Bookmark this page:
If you were Registered and logged in, you could reply and use other advanced thread options
How Many? 32: SVN23/PRN32 to be Set to Healthy
http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
Feb 7, 2008
GPS World
The U.S. military announced earlier this week that GPS satellite
SVN23, transmitting L-band code as PRN32, will be set to usable
status on Feb. 19.
This is notable for a couple of reasons, but namely because it is the
first time that the PRN32 designation will be used by an operational,
healthy GPS satellite.
GPS receivers initially were built to accommodate up to 31 satellite
signals, and a PRN designated with the number 32 can't be tracked by
some manufacturers' devices that look for PRNs numbered 0 through 31.
The U.S. Air Force began testing the PRN32 designation late in 2006
-- while SVN23/PRN32 was set to unhealthy and not included in the
operational GPS constellation almanac, some all-in-view GNSS tracking
stations received the L-band signal.
As of January 2007, SVN23 has been broadcasting but set to unhealthy
and not included in the almanac. Nevertheless, a number of civilian
users have reported being able to track PRN32 since then.
The setting of satellite SVN23/PRN32 to healthy is also notable
because in GPS satellite terms, it's coming back from the dead, or at
least from decommissioning. It is the first Block IIA satellite,
launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
2004, after more than 13 years of service. Apparently the U.S. Air
Force reactivated it at some point and set it to broadcast a
non-standard code that could not be tracked by standard GPS
receivers. However, on Dec. 2, 2006, it started to transmit the
standard PRN32 code as part of the Air Force's initial test.
I just downloaded and installed the latest Trimble Planning software
(http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
The software only shows up to PRN 31. I cant tell what the currency of the
almanac is though, it does appear to show PRN 32, but it looks like there
may be a flag, 'ff', that perhaps means that it is out of service.
Haven't yet seen PRN 32 on my GPSmap60CSx.
BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat somewhere
off the west coast of Africa.
>> How Many? 32: SVN23/PRN32 to be Set to Healthy
>>
>> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
>> Feb 7, 2008
>> GPS World
>> The U.S. military announced earlier this week that GPS satellite
>> SVN23, transmitting L-band code as PRN32, will be set to usable
>> status on Feb. 19.
>> This is notable for a couple of reasons, but namely because it is the
>> first time that the PRN32 designation will be used by an operational,
>> healthy GPS satellite.
>> GPS receivers initially were built to accommodate up to 31 satellite
>> signals, and a PRN designated with the number 32 can't be tracked by
>> some manufacturers' devices that look for PRNs numbered 0 through 31.
>> The U.S. Air Force began testing the PRN32 designation late in 2006
>> -- while SVN23/PRN32 was set to unhealthy and not included in the
>> operational GPS constellation almanac, some all-in-view GNSS tracking
>> stations received the L-band signal.
>> As of January 2007, SVN23 has been broadcasting but set to unhealthy
>> and not included in the almanac. Nevertheless, a number of civilian
>> users have reported being able to track PRN32 since then.
>> The setting of satellite SVN23/PRN32 to healthy is also notable
>> because in GPS satellite terms, it's coming back from the dead, or at
>> least from decommissioning. It is the first Block IIA satellite,
>> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
>> 2004, after more than 13 years of service. Apparently the U.S. Air
>> Force reactivated it at some point and set it to broadcast a
>> non-standard code that could not be tracked by standard GPS
>> receivers. However, on Dec. 2, 2006, it started to transmit the
>> standard PRN32 code as part of the Air Force's initial test.
>>
>> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
>> Feb 7, 2008
>> GPS World
>> The U.S. military announced earlier this week that GPS satellite
>> SVN23, transmitting L-band code as PRN32, will be set to usable
>> status on Feb. 19.
>> This is notable for a couple of reasons, but namely because it is the
>> first time that the PRN32 designation will be used by an operational,
>> healthy GPS satellite.
>> GPS receivers initially were built to accommodate up to 31 satellite
>> signals, and a PRN designated with the number 32 can't be tracked by
>> some manufacturers' devices that look for PRNs numbered 0 through 31.
>> The U.S. Air Force began testing the PRN32 designation late in 2006
>> -- while SVN23/PRN32 was set to unhealthy and not included in the
>> operational GPS constellation almanac, some all-in-view GNSS tracking
>> stations received the L-band signal.
>> As of January 2007, SVN23 has been broadcasting but set to unhealthy
>> and not included in the almanac. Nevertheless, a number of civilian
>> users have reported being able to track PRN32 since then.
>> The setting of satellite SVN23/PRN32 to healthy is also notable
>> because in GPS satellite terms, it's coming back from the dead, or at
>> least from decommissioning. It is the first Block IIA satellite,
>> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
>> 2004, after more than 13 years of service. Apparently the U.S. Air
>> Force reactivated it at some point and set it to broadcast a
>> non-standard code that could not be tracked by standard GPS
>> receivers. However, on Dec. 2, 2006, it started to transmit the
>> standard PRN32 code as part of the Air Force's initial test.
> I just downloaded and installed the latest Trimble Planning software
> (http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
> The software only shows up to PRN 31. I cant tell what the currency of
> the almanac is though, it does appear to show PRN 32, but it looks like
> there may be a flag, 'ff', that perhaps means that it is out of service.
> Haven't yet seen PRN 32 on my GPSmap60CSx.
> BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat somewhere
> off the west coast of Africa.
An update: I modified the almanac file and changed the PRN 32 'ff' field to
> (http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
> The software only shows up to PRN 31. I cant tell what the currency of
> the almanac is though, it does appear to show PRN 32, but it looks like
> there may be a flag, 'ff', that perhaps means that it is out of service.
> Haven't yet seen PRN 32 on my GPSmap60CSx.
> BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat somewhere
> off the west coast of Africa.
' 0'. Now PRN 32 shows up in the Trimble planning software. According to
that I should be able to see PRN 32, but no joy so far. I'm looking at
firmware updates.
>>> How Many? 32: SVN23/PRN32 to be Set to Healthy
>>> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
>>> Feb 7, 2008
>>> GPS World
>>> The U.S. military announced earlier this week that GPS satellite
>>> SVN23, transmitting L-band code as PRN32, will be set to usable
>>> status on Feb. 19.
>>> This is notable for a couple of reasons, but namely because it is the
>>> first time that the PRN32 designation will be used by an operational,
>>> healthy GPS satellite.
>>> GPS receivers initially were built to accommodate up to 31 satellite
>>> signals, and a PRN designated with the number 32 can't be tracked by
>>> some manufacturers' devices that look for PRNs numbered 0 through 31.
>>> The U.S. Air Force began testing the PRN32 designation late in 2006
>>> -- while SVN23/PRN32 was set to unhealthy and not included in the
>>> operational GPS constellation almanac, some all-in-view GNSS tracking
>>> stations received the L-band signal.
>>> As of January 2007, SVN23 has been broadcasting but set to unhealthy
>>> and not included in the almanac. Nevertheless, a number of civilian
>>> users have reported being able to track PRN32 since then.
>>> The setting of satellite SVN23/PRN32 to healthy is also notable
>>> because in GPS satellite terms, it's coming back from the dead, or at
>>> least from decommissioning. It is the first Block IIA satellite,
>>> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
>>> 2004, after more than 13 years of service. Apparently the U.S. Air
>>> Force reactivated it at some point and set it to broadcast a
>>> non-standard code that could not be tracked by standard GPS
>>> receivers. However, on Dec. 2, 2006, it started to transmit the
>>> standard PRN32 code as part of the Air Force's initial test.
>>> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
>>> Feb 7, 2008
>>> GPS World
>>> The U.S. military announced earlier this week that GPS satellite
>>> SVN23, transmitting L-band code as PRN32, will be set to usable
>>> status on Feb. 19.
>>> This is notable for a couple of reasons, but namely because it is the
>>> first time that the PRN32 designation will be used by an operational,
>>> healthy GPS satellite.
>>> GPS receivers initially were built to accommodate up to 31 satellite
>>> signals, and a PRN designated with the number 32 can't be tracked by
>>> some manufacturers' devices that look for PRNs numbered 0 through 31.
>>> The U.S. Air Force began testing the PRN32 designation late in 2006
>>> -- while SVN23/PRN32 was set to unhealthy and not included in the
>>> operational GPS constellation almanac, some all-in-view GNSS tracking
>>> stations received the L-band signal.
>>> As of January 2007, SVN23 has been broadcasting but set to unhealthy
>>> and not included in the almanac. Nevertheless, a number of civilian
>>> users have reported being able to track PRN32 since then.
>>> The setting of satellite SVN23/PRN32 to healthy is also notable
>>> because in GPS satellite terms, it's coming back from the dead, or at
>>> least from decommissioning. It is the first Block IIA satellite,
>>> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
>>> 2004, after more than 13 years of service. Apparently the U.S. Air
>>> Force reactivated it at some point and set it to broadcast a
>>> non-standard code that could not be tracked by standard GPS
>>> receivers. However, on Dec. 2, 2006, it started to transmit the
>>> standard PRN32 code as part of the Air Force's initial test.
>> I just downloaded and installed the latest Trimble Planning software
>> (http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
>> The software only shows up to PRN 31. I cant tell what the currency of
>> the almanac is though, it does appear to show PRN 32, but it looks like
>> there may be a flag, 'ff', that perhaps means that it is out of service.
>> Haven't yet seen PRN 32 on my GPSmap60CSx.
>> BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat
>> somewhere off the west coast of Africa.
>> (http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
>> The software only shows up to PRN 31. I cant tell what the currency of
>> the almanac is though, it does appear to show PRN 32, but it looks like
>> there may be a flag, 'ff', that perhaps means that it is out of service.
>> Haven't yet seen PRN 32 on my GPSmap60CSx.
>> BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat
>> somewhere off the west coast of Africa.
> An update: I modified the almanac file and changed the PRN 32 'ff' field
> to ' 0'. Now PRN 32 shows up in the Trimble planning software. According
> to that I should be able to see PRN 32, but no joy so far. I'm looking at
> firmware updates.
woops, snafu. Trimble does show PRN 32 as I mentioned, however I did not
> to ' 0'. Now PRN 32 shows up in the Trimble planning software. According
> to that I should be able to see PRN 32, but no joy so far. I'm looking at
> firmware updates.
save my station settings so when I restarted Trimble it was at the wrong
station. The correct station shows PRN 32 coming into view starting at 6 PM
EST. I also checked my firmware version and it is up to date.
Bruce wrote:
>>>> How Many? 32: SVN23/PRN32 to be Set to Healthy
>>>> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
>>>> Feb 7, 2008
>>>> GPS World
>>>> The U.S. military announced earlier this week that GPS satellite
>>>> SVN23, transmitting L-band code as PRN32, will be set to usable
>>>> status on Feb. 19.
>>>> This is notable for a couple of reasons, but namely because it is the
>>>> first time that the PRN32 designation will be used by an operational,
>>>> healthy GPS satellite.
>>>> GPS receivers initially were built to accommodate up to 31 satellite
>>>> signals, and a PRN designated with the number 32 can't be tracked by
>>>> some manufacturers' devices that look for PRNs numbered 0 through 31.
>>>> The U.S. Air Force began testing the PRN32 designation late in 2006
>>>> -- while SVN23/PRN32 was set to unhealthy and not included in the
>>>> operational GPS constellation almanac, some all-in-view GNSS tracking
>>>> stations received the L-band signal.
>>>> As of January 2007, SVN23 has been broadcasting but set to unhealthy
>>>> and not included in the almanac. Nevertheless, a number of civilian
>>>> users have reported being able to track PRN32 since then.
>>>> The setting of satellite SVN23/PRN32 to healthy is also notable
>>>> because in GPS satellite terms, it's coming back from the dead, or at
>>>> least from decommissioning. It is the first Block IIA satellite,
>>>> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
>>>> 2004, after more than 13 years of service. Apparently the U.S. Air
>>>> Force reactivated it at some point and set it to broadcast a
>>>> non-standard code that could not be tracked by standard GPS
>>>> receivers. However, on Dec. 2, 2006, it started to transmit the
>>>> standard PRN32 code as part of the Air Force's initial test.
>>> I just downloaded and installed the latest Trimble Planning software
>>> (http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
>>> The software only shows up to PRN 31. I cant tell what the currency of
>>> the almanac is though, it does appear to show PRN 32, but it looks like
>>> there may be a flag, 'ff', that perhaps means that it is out of service.
>>> Haven't yet seen PRN 32 on my GPSmap60CSx.
>>> BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat
>>> somewhere off the west coast of Africa.
>>>> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
>>>> Feb 7, 2008
>>>> GPS World
>>>> The U.S. military announced earlier this week that GPS satellite
>>>> SVN23, transmitting L-band code as PRN32, will be set to usable
>>>> status on Feb. 19.
>>>> This is notable for a couple of reasons, but namely because it is the
>>>> first time that the PRN32 designation will be used by an operational,
>>>> healthy GPS satellite.
>>>> GPS receivers initially were built to accommodate up to 31 satellite
>>>> signals, and a PRN designated with the number 32 can't be tracked by
>>>> some manufacturers' devices that look for PRNs numbered 0 through 31.
>>>> The U.S. Air Force began testing the PRN32 designation late in 2006
>>>> -- while SVN23/PRN32 was set to unhealthy and not included in the
>>>> operational GPS constellation almanac, some all-in-view GNSS tracking
>>>> stations received the L-band signal.
>>>> As of January 2007, SVN23 has been broadcasting but set to unhealthy
>>>> and not included in the almanac. Nevertheless, a number of civilian
>>>> users have reported being able to track PRN32 since then.
>>>> The setting of satellite SVN23/PRN32 to healthy is also notable
>>>> because in GPS satellite terms, it's coming back from the dead, or at
>>>> least from decommissioning. It is the first Block IIA satellite,
>>>> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
>>>> 2004, after more than 13 years of service. Apparently the U.S. Air
>>>> Force reactivated it at some point and set it to broadcast a
>>>> non-standard code that could not be tracked by standard GPS
>>>> receivers. However, on Dec. 2, 2006, it started to transmit the
>>>> standard PRN32 code as part of the Air Force's initial test.
>>> I just downloaded and installed the latest Trimble Planning software
>>> (http://www.trimble.com/planningsoftware_ts.asp ) and the latest almanac.
>>> The software only shows up to PRN 31. I cant tell what the currency of
>>> the almanac is though, it does appear to show PRN 32, but it looks like
>>> there may be a flag, 'ff', that perhaps means that it is out of service.
>>> Haven't yet seen PRN 32 on my GPSmap60CSx.
>>> BTW I have been occasionaly seeing PRN 33, which is an EGNOS sat
>>> somewhere off the west coast of Africa.
>> An update: I modified the almanac file and changed the PRN 32 'ff' field
>> to ' 0'. Now PRN 32 shows up in the Trimble planning software. According
>> to that I should be able to see PRN 32, but no joy so far. I'm looking at
>> firmware updates.
>> to ' 0'. Now PRN 32 shows up in the Trimble planning software. According
>> to that I should be able to see PRN 32, but no joy so far. I'm looking at
>> firmware updates.
> woops, snafu. Trimble does show PRN 32 as I mentioned, however I did not
> save my station settings so when I restarted Trimble it was at the wrong
> station. The correct station shows PRN 32 coming into view starting at 6 PM
> EST. I also checked my firmware version and it is up to date.
>
>
> save my station settings so when I restarted Trimble it was at the wrong
> station. The correct station shows PRN 32 coming into view starting at 6 PM
> EST. I also checked my firmware version and it is up to date.
>
>
:-)
> http://sidt.gpsworld.com/gpssidt/content/printContentPopup.jsp?id=490027
> Feb 7, 2008
> GPS World
> The U.S. military announced earlier this week that GPS satellite
> SVN23, transmitting L-band code as PRN32, will be set to usable
> status on Feb. 19.
> This is notable for a couple of reasons, but namely because it is the
> first time that the PRN32 designation will be used by an operational,
> healthy GPS satellite.
> GPS receivers initially were built to accommodate up to 31 satellite
> signals, and a PRN designated with the number 32 can't be tracked by
> some manufacturers' devices that look for PRNs numbered 0 through 31.
> The U.S. Air Force began testing the PRN32 designation late in 2006
> -- while SVN23/PRN32 was set to unhealthy and not included in the
> operational GPS constellation almanac, some all-in-view GNSS tracking
> stations received the L-band signal.
> As of January 2007, SVN23 has been broadcasting but set to unhealthy
> and not included in the almanac. Nevertheless, a number of civilian
> users have reported being able to track PRN32 since then.
> The setting of satellite SVN23/PRN32 to healthy is also notable
> because in GPS satellite terms, it's coming back from the dead, or at
> least from decommissioning. It is the first Block IIA satellite,
> launched on Nov. 26, 1990, and initially decommissioned on Feb.13,
> 2004, after more than 13 years of service. Apparently the U.S. Air
> Force reactivated it at some point and set it to broadcast a
> non-standard code that could not be tracked by standard GPS
> receivers. However, on Dec. 2, 2006, it started to transmit the
> standard PRN32 code as part of the Air Force's initial test.