Bug and Known Problem List for ver.2.2.0

No.11 A wrong deg-min-sec format in the south latitude or in the west longitude (RTKNAV etc. ver.2.2.0)

The deg-min-sec format of latitude/longitude is not proper on the RTKNAVI panel at the position in the south latitude or in the west longitude.

Bug of the function degtodms() in src/solution.c and app/rtknavi/navimain.cpp. Apply the patch rtklib_2.2.0_p5.zip and rebuild the APs with the issue. Fixed in ver.2.2.1.

No.10 Illegal velocity estimation for Crescent receiver (RTKNAVI etc. ver.2.2.0)

Estimation of the rover velocity is not proper in case of using Crescent receiver.
Bug in src/rcv/crescent.c to decode raw doppler measurement data. Apply the patch rtklib_2.2.0_p4.zip and rebuild the APs with the issue. Fixed in ver.2.2.1.

No.9 Illegal L2 SNR on RTKNAVI SNR panel for Superstar II or Crescent receiver (RTKNAVI etc. ver.2.2.0)

RTKNAVI SNR panel indicates Illegal L2 values for Superstar II or Crescent receiver.
Bug in src/rcv/ss2.c or src/rcv/crescent.c to decode raw observation data. Apply the patch rtklib_2.2.0_p4.zip and rebuild the APs with the issue. Fixed in ver.2.2.1.

No.7 Illegal observation time stamp for Superstar II receiver (RTKNAVI etc. ver.2.2.0)

When executing RTKNAVI connecting Superstar II receiver, it is not able to get proper positioning solutions by illegal time stamp of observation data.

Bug in src/rcv/ss2.c to decode the message id#21. Apply the patch rtklib_2.2.0_p4.zip and rebuild the APs with the issue. Fixed in ver.2.2.1.

No.6 One hour time offset during summer time applied (RTKLIB etc ver.2.2.0)

On the PC where the timezone involves summer time and the automatic summer time adjustment enabled, the output time in calendar time has 1 hour offset during the summer time applied.

Bug in src/rtkcmn.c. The function time2epoch() does not consider summer time and causes 1 hour offset when converting internal time to calendar time. Apply the patch: rtklib_2.2.0_p3.zip and rebuild the application programs with the issue. Fixed in ver.2.2.1.

No.5 Error stop of RTKPOST or RTKPLOT under the timezone of EST (GMT-5) (RTKPOST etc. ver.2.2.0)

On the PC where the timezone is set to EST (GMT-5), when executing RTKPOST or RTKPLOT, the program stops by error at the beginning.

Bug in src/rtkcmn.c. The standard localtime(0) returns NULL if the timezone set to GMT- (minus). In this case, the function time2epoch() refers NULL pointer and rises address exception. Apply the patch: rtklib_2.2.0_p3.zip and rebuild the application programs with the issue. Fixed in ver.2.2.1

No.4 Error stop of RTKNAVI when GLONASS observations in NovAtel raw data (RTKNAVI etc. ver.2.2.0)

When executing RTKNAVI with the setting of Input Rover/Base Station Format=NovAtel Raw, an address exception occurs and stops the program if the NovAtel raw input contains GLONASS observation data.

Bug in src/rcv/novatel.c. Lack of the satellite PRN number range check. Apply the patch rtklib_2.2.0_p4.zip and rebuild the APs with the issue. Fixed in ver.2.2.1.

No.3 Memory leakage (RTKNAVI etc. ver.2.2.0)

Memory leakage in the function solve() in src/rtkcmn.c. The function is used in the function lambda() in src/lambda.c. It may cause out-of-memory with very long continuous RTK-GPS operation with RTKNAVI.

Fixed in ver.2.2.1.

No.1 DOMAIN error with RTKPOST using old SP3(a) precise ephemerides (RTKPOST, RTKPOST_MKL ver.2.2.0)

When executing RTKPOST using old SP3(a) format precise ephemerides, "pow: DOMAIN error" occurs and unable to continue the analysis.

Bug in src/preceph.c. SP3a does not include standard deviation fields which are included in SP3c format. RTKPOST tries to read null field and causes the numerical error. Apply the patch: rtklib_2.2.0_p1.zip and rebuild rtkpost.exe or rtkpost_mkl.exe. Fixed in ver.2.2.1.