Index: trunk/BNC/src/bnchelp.html
===================================================================
--- trunk/BNC/src/bnchelp.html	(revision 4506)
+++ trunk/BNC/src/bnchelp.html	(revision 4507)
@@ -104,4 +104,7 @@
 <li>RTNET, a plain ASCII format defined within BNC to receive orbits and clock from a serving GNSS engine.
 </ul>
+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.
+</p>
+<p>
 Furthermore, BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files.
 </p>
@@ -437,6 +440,18 @@
 </p> 
 <p>
-It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available or it does not contain the required information.
-</p>
+It is important to understand that converting RTCM streams to RINEX files requires a-priori information on observation types for specifying a complete RINEX header. Regarding the RINEX Version 2 file header, BNC simply introduces all observation types defined in the Version 2 standard and later reports "0.000" for all observations which are not received. However, following this approach is not possible for RINEX Version 3 files from RTCM Version 3 MSM streams because of the huge number of observation types which might in principle show up. The solution implemented in BNC is to start with RINEX Version 3 observation type records from skeleton files (see section 'Skeleton Extension') and switch to a default selection of observation types when such skeleton file is not available or it does not contain the required information. The 'Default selection of observation types specified' for a RINEX Version 3 file would be as follows:
+</p>
+<pre>
+C   12 C2  L2  D2  S2  C6  L6  D6  S6  C7  L7  D7  S7       SYS / # / OBS TYPES
+E   20 C1  L1  D1  S1  C5  L5  D5  S5  C6  L6  D6  S6  C7   SYS / # / OBS TYPES
+       L7  D7  S7  C8  L8  D8  S8                           SYS / # / OBS TYPES
+G   20 C1C L1C D1C S1C C1P L1P D1P S1P C2C L2C D2C S2C C2P  SYS / # / OBS TYPES
+       L2P D2P S2P C5  D5  L5  S5                           SYS / # / OBS TYPES
+J   16 C1  L1  D1  S1  C2  L2  D2  S2  C5  L5  D5  S5  C6   SYS / # / OBS TYPES
+       D6  L6  S6                                           SYS / # / OBS TYPES
+R   16 C1C L1C D1C S1C C1P L1P D1P S1P C2C L2C D2C S2C C2P  SYS / # / OBS TYPES
+       L2P D2P S2P                                          SYS / # / OBS TYPES
+S    8 C1  L1  D1  S1  C5  L5  D5  S5                       SYS / # / OBS TYPES
+</pre>
 
 <p>