Changes between Version 33 and Version 34 of NDF


Ignore:
Timestamp:
Dec 20, 2018, 3:14:46 PM (5 years ago)
Author:
stoecker
Comment:

Message number updates

Legend:

Unmodified
Added
Removed
Modified

  • NDF

    v33 v34  
    22= Preface =
    33
    4 Many users need all the information contained in the data transmission by the satellite in an unmodified form. Lots of receivers and services already support output of raw frames, but there exists no standard. This message tries to solve this situations – a transport format for raw Navigation Data Frames (NDF).
     4Many users need all the information contained in the data transmission by the satellite in an unmodified form. Lots of receivers and services already support output of raw frames, but there exists no standard. This message tries to solve these situations – a transport format for raw Navigation Data Frames (NDF).
    55
    66This message is in line with lately introduced MSM observation messages. MSM messages are generic and Message Type numbers are reserved for up to 16 GNSS systems. Similarly, NDF data messages are also claimed as generic, i.e. their high level structure is the very same for each GNSS and Signal.
    … …  
    1414== Message header ==
    1515||=Data field=||=DF NUMBER=||=DATA TYPE=||=NO. OF BITS=||=NOTES=||
    16 || Message Number       || DF002 || uint12 || 12 || 4075 (proprietary number for this purpose) ||
     16|| Message Number       || DF002 || uint12 || 12 || 99 (pre-standard number) ~~4075 (proprietary number for this purpose)~~ ||
    1717|| Reference Station ID || DF003 || uint12 || 12 || stream identification ||
    18 || Reserved field       ||       || uint2  ||  2 || reserved bits, maybe used to separate different type 4075 message, always 0 for NDF ||
     18|| ~~Reserved field~~       ||       || ~~uint2~~  ||  ~~2~~ || ~~reserved bits, maybe used to separate different type 4075 message, always 0 for NDF~~ ||
    1919|| Frame Count (FC)     ||       || uint6  ||  6 || Number of frame entries to follow ||
    2020|| Frame Entry          ||       ||        || depends on FC and frame size || frame data according to following table ||
    … …  
    107107== Implementation
    108108
    109 * For ephemeris usage set "Reserved field" to 1.
     109* For ephemeris usage set "Message Number" field to 100 (pre-standard number).
     110* ~~For ephemeris usage set "Reserved field" to 1.~~
    110111* Only one satellite is allowed per message.
    111112* Complete matching and valid frames for one ephemeris set must be included in correct order: