Changes between Version 10 and Version 11 of NDF


Ignore:
Timestamp:
Jun 25, 2014, 10:54:09 AM (8 years ago)
Author:
stoecker
Comment:

Adapt satellite ID to match MSM directly, don't use DF fields

Legend:

Unmodified
Added
Removed
Modified
  • NDF

    v10 v11  
    3535|| Satellite system    || || uint5  ||  4 || 0 == GPS, 1 == GLONASS, 2 == Galileo, 3 = SBAS, 4 = QZSS, 5 = BDS ||
    3636|| Satellite number    || || uint6  ||  6 || Satellite ID, specific for the satellite system always 6 bits (see table below) ||
    37 || Signal Type         || || uint5  ||  5 || Signal type specification, index from MSM signal mask bit field (see DF395) ||
    38 || Epoch Time          || || uint30 || 30 || Epoch time, specific for the satellite system always 30 bits (see table below) ||
     37|| Signal Type         || || uint5  ||  5 || Signal type specification, index from MSM signal mask bit field (0..31, see DF395) ||
     38|| Epoch Time          || || uint30 || 30 || Epoch time, specific for the satellite system always 30 bits (0..63, see DF394) ||
    3939|| Continuous Tracking || || bit(1) ||  1 || Tracking this satellite frame data was continous (1 = continous, 0 not continues or unset) ||
    4040|| Frame Data Size (N) || || uint12 || 12 || Number of bits to follow ||
     
    4444
    4545Layout of a frame block always follows this structure, so unknown satellite systems or satellites can be skipped in messages with more than one frame.
    46 
    47 == Satellite ID (equal to MSM) ==
    48 
    49 ||=Satellite system=||=DF NUMBER(s)=||=NOTES=||
    50 || GPS || DF068 || 1 .. 32 ||
    51 || GLONASS || DF384 (with 6 bit) || 1 .. 24 ||
    52 || Galileo || DF252 || 1 .. 36 ||
    53 || SBAS || || 120 == 1, ... ||
    54 || QZSS || DF429 (with 6 bit) || 192 == 1, ... 202 == 10 ||
    55 || BDS ||  || 1 .. 37 ||
    5646
    5747== Epoch Time (accuracy in milli seconds, equal to MSM) ==