Changes between Version 23 and Version 24 of NDF


Ignore:
Timestamp:
Apr 18, 2018, 11:33:42 AM (6 years ago)
Author:
stoecker
Comment:

Add IRNSS

Legend:

Unmodified
Added
Removed
Modified

  • NDF

    v23 v24  
    3333
    3434||=Data field=||=DF NUMBER=||=DATA TYPE=||=NO. OF BITS=||=NOTES=||
    35 || Satellite system    || || uint5  ||  4 || 0 == GPS, 1 == GLONASS, 2 == Galileo, 3 = SBAS, 4 = QZSS, 5 = BDS ||
     35|| Satellite system    || || uint5  ||  4 || 0 == GPS, 1 == GLONASS, 2 == Galileo, 3 = SBAS, 4 = QZSS, 5 = BDS, 6 = IRNSS ||
    3636|| Satellite number    || || uint6  ||  6 || Satellite ID, index from MSM satellite mask bit field (0..63, see DF394) ||
    3737|| Extended Sat Info   || || uint4  ||  4 || Specific for each GNSS system, Frequency number+7 for GLONASS ||
    … …  
    5555|| QZSS || DF428 || equals GPS ||
    5656|| BDS || DF427 || similar to GPS, but with a 14 leap second difference ||
     57|| IRNSS || || equals GPS ||
    5758
    5859== Frame Data (implementation recommendation) ==
    … …  
    8182* GLONASS:
    8283 * 85 bits
     84* IRNSS:
     85 * 292 bits
    8386
    8487Data senders need to decide whether data with bad checksum is transferred or not. While generally data with a bad checksum may be discarded, in disturbed environments even such data may be useful, in particular when parts of the message are common to multiple satellites, or when a portion of the data is already known.