Customer Service Center

• PosApp
• GLONASS enabled scenario
• GLONASS nav data extract utility
• 'Dump navigation data' enabled

 What is a P1 flag? - Click here to find more information, or consult the GLONASS ICD

• In the example below the scenario starts 10 minutes before an upload is due
• The P1 flag is set to "01" (30 minute (1800 second) intervals)
• At time into run 600 seconds (10mins) an upload occurs
• It takes an additional 16 seconds for the SV to broadcast information about the P1 flag status
• Therefore the P1 flag will read “P1  :30 (minutes)” at time into run 616 seconds
  • Uploads are repeated at 1800 second intervals throughout the scenario
    • In this example, they occur at 2416, 4216, 6016 and so on

Glonass string for svid 3: (SF6, F1, S1), Seconds Into Run: 616

  Pure bits: 0101 0101 1010 1010 0101  0101 1001 0101 0101 0101 (55AA5 59555)

             0110 1010 1010 1001 0110  0101 0110 1001 0110 0101 (6AA96 56965)

             1001 1001 1010 1010 1010  0101 1010 0101 0110 0110 (99AAA 5A566)

             0110 0110 0101 0101 0110  0110 0101 0110 0101 0101 (66556 65655)

             1010 1010 0111 1110 0011  0111 0101 0000 1001 0110 (AA7E3 75096)

  Zero bit:  0

  Data bits: 0001 0001 0001 1000 0000  1000 0010 1100 1010 1101 (11180 82CAD)

             1111 0000 0101 0100 1111  1111 0000 1111 0011      (F054F F0F3)

  Hamming:   0001 0001 (11)

  m: 1 (dimensionless)

  Reserved (bit 6 through 7, length = 2): 0x0

  P1: 30 (minutes)

• For any timestamps that do not fall on an 1800 second epoch the P1 flag will be ‘0 minutes’
• If the P1 flag were set to "11" to specify a 60 minute interval between updates, the flag would be seen at 3600 second intervals
  • In this example, it would first be seen at 616 seconds into run
    • Then at 4216, 7816 and so on