- Timestamp:
- Sep 10, 2012, 4:01:46 PM (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r4721 r4726 101 101 <li>RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS, GLONASS, SBAS, Galileo, COMPASS and QZSS,</li> 102 102 <li>RTCM Version 3 'State Space Representation' (SSR) messages for GPS, GLONASS and Galileo,</li> 103 <li>Drafted RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM),</li>104 103 <li>RTNET, a plain ASCII format defined within BNC to receive orbits and clock from a serving GNSS engine. 105 104 </ul> 106 Note that up to now basic QZSS support follows a draft for RTCM MSM messages agreed by JAXA, BKG and DLR. Support of certain extra QZSS messages and support of COMPASS so far only follows an internal agreement between BKG and DLR. 107 </p> 108 <p> 109 Furthermore, BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 105 </p> 106 107 <p> 108 Note that up to now decoding RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM) in BNC for 109 <ul> 110 <li>GPS, GLONASS and Galileo follows the latest RTCM draft,</li> 111 <li>QZSS follows a JAXA proposal,</li> 112 <li>X tracking mode follows an agreement between BKG, Alberding and DLR,</li> 113 <li>COMPASS follows an agreement between BKG, Alberding and DLR,</li> 114 <li>SBAS follows an agreement between BKG, Alberding and DLR.</li> 115 </ul> 116 </p> 117 118 <p> 119 Note further that BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 110 120 </p> 111 121
Note:
See TracChangeset
for help on using the changeset viewer.