IS-GPS-800A - US Coast Guard Navigation Center

IS-GPS-800A - US Coast Guard Navigation Center IS-GPS-800A - US Coast Guard Navigation Center

navcen.uscg.gov
from navcen.uscg.gov More from this publisher
13.07.2015 Views

3.5.3.1 Transmission Week NumberBits 1 through 13 of subframe 2 shall contain 13 bits that are a modulo-8192 binary representation of the currentGPS week number at the start of the data set transmission interval (see paragraph 6.2.2).3.5.3.2 ITOWBits 14 through 21 of subframe 2 shall contain 8 bits representing ITOW count defined as being equal to the numberof two-hour epochs that have occurred since the transition from the previous week. The count is short-cycled suchthat the range of the ITOW-count is from 0 to 83 2-hour epochs (equaling one week) and is reset to zero at the endof each week. The ITOW-count's zero state is defined as that 2-hour epoch which is coincident with the start of thepresent week. This epoch occurs at (approximately) midnight Saturday night-Sunday morning, where midnight isdefined as 0000 hours on the UTC scale that is nominally referenced to the Greenwich Meridian. The occurrence ofthe “zero state epoch” may differ by a few seconds from 0000 hours on the UTC scale since UTC is periodicallycorrected with leap seconds while GPS time is continuous without such correction.3.5.3.3 Data Predict Time of WeekBits 22 through 32 of subframe 2 shall contain the data predict time of week (t op ). The t op term provides the epochtime of week of the state estimate utilized for the prediction of satellite quasi-Keplerian ephemeris parameters.3.5.3.4 L1C Signal HealthThe one-bit health indication in bit 33 of subframe 2 refers to the L1C signal of the transmitting SV. The health ofthe signal is indicated by:0 = Signal OK,1 = Signal bad or unavailable.The predicted health data will be updated at the time of upload when a new data set has been built by the CS. Thetransmitted health data may not correspond to the actual health of the transmitting SV. In real time, if the L1Csignal becomes unhealthy, the status change will normally be indicated by the broadcast of non-standard code or beindicated by the health bits as described in subframe 2.Additional SV health data are given in the almanac in subframe 3, pages 3 and 4. The data given in subframe 2 maydiffer from that shown in other messages of the transmitting SV and/or other SVs since the latter may be updated ata different time. Subframe 2 data is the most reliable; subframe 3 data is intended only to aid acquisition.3.5.3.5 SV AccuracyBits 34 through 38 of subframe 2 shall contain the ephemeris User Range Accuracy (URA oe ) index of the SV.URA oe index shall provide the ephemeris-related user range accuracy index of the SV as a function of the current42 IS-GPS-800A8 June 2010

ephemeris message curve fit interval. While the ephemeris-related URA may vary over the ephemeris messagecurve fit interval, the URA oe index (N) in subframe 2 shall correspond to the maximum URA oe expected over theentire curve fit interval.The URA oe index is a two’s complement representation of a signed integer in the range of +15 to –16 and has thefollowing relationship to the ephemeris URA:URA oe IndexURA oe (meters)15 6144.00 < URA oe14 3072.00 < URA oe 6144.0013 1536.00 < URA oe 3072.0012 768.00 < URA oe 1536.0011 384.00 < URA oe 768.0010 192.00 < URA oe 384.009 96.00 < URA oe 192.008 48.00 < URA oe 96.007 24.00 < URA oe 48.006 13.65 < URA oe 24.005 9.65 < URA oe 13.654 6.85 < URA oe 9.653 4.85 < URA oe 6.852 3.40 < URA oe 4.851 2.40 < URA oe 3.400 1.70 < URA oe 2.40-1 1.20 < URA oe 1.70-2 0.85 < URA oe 1.20-3 0.60 < URA oe 0.85-4 0.43 < URA oe 0.60-5 0.30 < URA oe 0.43-6 0.21 < URA oe 0.30-7 0.15 < URA oe 0.21-8 0.11 < URA oe 0.15-9 0.08 < URA oe 0.11-10 0.06 < URA oe 0.08-11 0.04 < URA oe 0.06-12 0.03 < URA oe 0.04-13 0.02 < URA oe 0.03-14 0.01 < URA oe 0.02-15 URA oe 0.01-16 No accuracy prediction available—use at own risk43 IS-GPS-800A8 June 2010

3.5.3.1 Transmission Week NumberBits 1 through 13 of subframe 2 shall contain 13 bits that are a modulo-8192 binary representation of the current<strong>GPS</strong> week number at the start of the data set transmission interval (see paragraph 6.2.2).3.5.3.2 ITOWBits 14 through 21 of subframe 2 shall contain 8 bits representing ITOW count defined as being equal to the numberof two-hour epochs that have occurred since the transition from the previous week. The count is short-cycled suchthat the range of the ITOW-count is from 0 to 83 2-hour epochs (equaling one week) and is reset to zero at the endof each week. The ITOW-count's zero state is defined as that 2-hour epoch which is coincident with the start of thepresent week. This epoch occurs at (approximately) midnight Saturday night-Sunday morning, where midnight isdefined as 0000 hours on the UTC scale that is nominally referenced to the Greenwich Meridian. The occurrence ofthe “zero state epoch” may differ by a few seconds from 0000 hours on the UTC scale since UTC is periodicallycorrected with leap seconds while <strong>GPS</strong> time is continuous without such correction.3.5.3.3 Data Predict Time of WeekBits 22 through 32 of subframe 2 shall contain the data predict time of week (t op ). The t op term provides the epochtime of week of the state estimate utilized for the prediction of satellite quasi-Keplerian ephemeris parameters.3.5.3.4 L1C Signal HealthThe one-bit health indication in bit 33 of subframe 2 refers to the L1C signal of the transmitting SV. The health ofthe signal is indicated by:0 = Signal OK,1 = Signal bad or unavailable.The predicted health data will be updated at the time of upload when a new data set has been built by the CS. Thetransmitted health data may not correspond to the actual health of the transmitting SV. In real time, if the L1Csignal becomes unhealthy, the status change will normally be indicated by the broadcast of non-standard code or beindicated by the health bits as described in subframe 2.Additional SV health data are given in the almanac in subframe 3, pages 3 and 4. The data given in subframe 2 maydiffer from that shown in other messages of the transmitting SV and/or other SVs since the latter may be updated ata different time. Subframe 2 data is the most reliable; subframe 3 data is intended only to aid acquisition.3.5.3.5 SV AccuracyBits 34 through 38 of subframe 2 shall contain the ephemeris User Range Accuracy (URA oe ) index of the SV.URA oe index shall provide the ephemeris-related user range accuracy index of the SV as a function of the current42 <strong>IS</strong>-<strong>GPS</strong>-<strong>800A</strong>8 June 2010

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!