First of all, please read again the manual and the release notes (refer RTFM as well.) If they do not solve your problem(s), send the e-mail to the following address. (It may take a long time to receive the answer due to lack of our time for support.)
rtklib_support(a)gpspp.sakura.ne.jp (replace (a) by @)
Bug and Known Problem List
No.90 Some problems to port RTKLIB to Android (RTKRCV, CONVBIN, STR2STR ver.2.4.2)
Some problems are pointed out as the issues #2 - #8.
These problems are fixed. Apply the patch rtklib_2.4.2_p3.zip. (2013/06/02)
No.89 Unable to read Galileo navigation data for NovAtel OEM6 (RTKNAV, RTKCONV, STRSVR, RTKRCV, CONVBIN, STR2STR, RTKRCV ver. 2.4.2)
The Galileo navigation data message GALEPHEMERISB, GALALMANACB, GALIONOB and GALCLOCKB for NovAtel OEM6 cannot be properly read by message length errors.
Due to bugs in src/rcv/novatel.c. The patch will be released. Apply the patch rtklib_2.4.2_p3.zip. (2013/06/02)
No.88 Unable playback of log file with time-tags in 64-bit environement (STR2STR, RTKRCV ver. 2.4.2)
A Log file with time-tags cannot be properly playbacked by STR2STR or RTKRCV which is built in 64-bit environment.
Due to a bug in src/stream.c. File pointers in the time-tag file is not properly read because the program assumes 32-bit pointers. It does not affect to 32-bit APs. Windows binary APs included in the RTKLIB package also have no problem. The patch will be released. Apply the patch rtklib_2.4.2_p3.zip. (2013/06/02)
No.87 Invalid read of RTCM MSM stream with BeiDou data (RTKNAV, RTKCONV, STRSVR, CONVBIN, STR2STR ver.2.4.2)
If a RTCM MSM stream contains BeiDou measurement data, the time-tag indicates 14s offset. The MSM messages for other navigation systems are not able to be read in this case.
The current version assumes the epoch time of BeiDou MSM messages based on GPST. If the epoch time is based on BDT, the time offset of 14s between GPST and BDT induces invalid data read of MSM stream. Apply the patch rtklib_2.4.2_p3.zip. (2013/06/02)
No.86 Unable automatic update of real-time solution plot after the real-time buffer full. (RTKPLOT ver.2.4.2)
After the real-time ring-buffer of solution reaches full, the solution plot stops to be updated.
Due to a bug in app/rtkplot/plotmain.cpp. Apply the patch rtklib_2.4.2_p2.zip. (2013/05/18)
No.85 Unable decoding of BINEX message 0x7f-05 (RTKNAVI, RTKCONV, STRSVR, CONVBIN, STR2STR ver.2.4.2)
The BINEX message 0x7f-05 cannot propery decoded in case that the obsflags(1) does not follow obsflags(0).
Due to a bug in src/rcv/binex.c. Apply the patch rtklib_2.4.2_p2.zip. (2013/05/18)
No.84 Some minor bugs in v.2.4.2 (ALL ver.2.4.2)
The following minor bugs are found in ver. 2.4.2.
(1) Invalid standard deviation computation of precise clocks. (src/preceph.c)
(2) Invalid week number of Galileo ephemeris in RINEX for Javad. (src/rcv/javad.c)
(3) Invalid nutation coefficient table for ast_args(). (src/rtkcmn.c)
(4) Unable to select GLO, GAL, QZS and GEO nav files for RINEX ver. 2.12 in RTKCONV. (app/rkconv/convmain.cpp)
(5) Unable to build rnx2rtkp in Linux environment. (app/rnx2rtkp/gcc/makefile)
Apply the patch rtklib_2.4.2_p1.zip. (2013/05/08)
No.83 One second offset in converting Javad stream to RTCM 3 (STRSVR, STR2STR ver.2.4.2)
In case of converting a JAVAD raw stream to a RTCM 3 stream by STRSVR or STR2STR, one second offset is introduced in the time-tag of observation data.
Due to a bug in src/streamsvr.c. Apply the patch rtklib_2.4.2_p1.zip. (2013/05/08)
No.82 Unable to read GLONASS and GEO ephemerides in RINEX 3 (RTKPOST, RTKPLOT, RTKCONV, RNX2RTKP, CONVBIN ver.2.4.2)
GLONASS and GEO ephemerides in RINEX 3 can not be read. GLONASS and SBAS (ranging signal) satellites cannot be used for processing without ephemerides.
Due to a bug in src/rinex.c. Apply the patch rtklib_2.4.2_p1.zip. (2013/05/08)
Support Information for ver.2.4.1
Support Information for ver.2.4.0
Support Information for ver.2.3.0
Support Information for ver.2.2.2
Support Information for ver.2.2.1
Support Information for ver.2.2.0
How to apply a patch
(1) Extract zip file of the patch. Copy and overwrite it to the AP(s) and source program(s) in RTKLIB directory.
(2) From ver.2.3.0, all the patches include the executable binary AP(s) for Windows as well as source program(s). So usually you do not need to rebuild AP on Windows. If you want to build AP by yourself, try the following procedure.
(a) Execute Borland Turbo C++ (http://www.turboexplorer.com). Open the project file (*.bdsproj) in the application program directory (rtklib_<ver>\app\<ap>) and rebuild the application program.
(b) Execute install.bat in the application program directory. It copies the new program to the directory of binaries (rtklib_<ver>\bin).
|Copyright (C) 2009-2013 by T.TAKASU, All rights reserved.|