Rtklibexplorer does really great improvements. We are testing them and slowly merging into what is running on Reach. For example a recent fix regarding the solution loss when a new satellite would appear.
Rabun: Made a copy of config file for RTKPOST, but been too busy to post it. Will try to get it uploaded.
Igor: I’ve run some additional tests using the latest RTKLIB development releases and seem to do better with the RTKPOST processing on static AR Fix and Hold. I’ve recently got good results on a 2 meter baseline survey. With the Reach real-time RTK setup, I rarely get a good fix. With proper setup, I can get good fixes with obstructed sky views( Pine trees, etc.)
Johannes_Eberenz: The emphasis on improving the single carrier processing appears to be on identifying the possible slips and identifying how to lessen the effect on the resulting calculations. This is more difficult with the real-time processing, I can watch the coordinates zero in on a solution with Reach in float mode and then jump to start converging once again without getting into fix mode.
This subject is more likely to be of interest where the sky views are obstructed.
I use the sky view in RTKPLOT to identify satellites with slips. First, I make sure the receiver position in RTKPLOT is identified properly. Otherwise you may not get good satellite visibility plots.
I look at the RINEX files (Square Button to upper right of ,OBS files in RTKPOST). Look at the signal levels. The values will vary depending on the receiver and antenna. I try to set the minimum value of SNR a few db below the maximum levels of the weakest receiver. The assumption here is that bad data is likely to have a lower SNR.
Next, go to the satellite visibility buttom (The Round Button to the upper right of the .OBS file names in RTKPOST). This will bring up the satellites in view with their potential cycle slips. Find all the satellites with slips and reject them in RTKPOST configuration. If there are enough good satellites left(recommend GPS + GLO), your chance of a good fix is enhanced considerably.
These new versions of RTKLIB are developmental, so no guarantees.
Yes, the jumps in fix/float mode appear to have not been as much in Reach real time mode lately. It seems as though the trend toward the fix mode gets better.
The Demo4 version has been doing well for me in post processing.
It seems that the cycle slips and satellite changes were significant
in compromised environments. UAVs get a pass in clear skies, but anything to help ground vehicles, bikers, surveyors, UAVs that get too close to trees etc., seems like a good deal to me and hopefully to the RTKLIB / Emlid community.
Since this topic was started, several improvements have been added by Emlid. RTKLIBEXPLORER has just posted the latest developmental version to provide improved FIX results. I know that several members on the Emlid forum follow those improvements and help with feedback.
This latest change appears to help in FIX retention. If anyone can test the DEMO5 latest code, it would be interesting to see the results.
Great improvements in last year. Do most of my RTKPOST with latest version. Emlid also has upgraded with improvements. See the DOCs. I must admit that i have not tested the Emlid upgrade because I get good results. For short baselines, I typically get 1 mm STATIC resolutions in reasonable skyviews and with less than 1 hour of data. Marginal locations are free of earlier data glitches.
Emlid version appears to have most upgraded versions, but the time corrections of last RTKExplorer binaries may not be there. (I don’t use time tags, so I would would watch out for possible time related effects after this change.) The latest version I have relates to improving realtime results. It seems to give better results on maintaining FIX in post-processing. I have not tried RTKNavi, so I don’t know if the improvements are there in realtime. I am using ReachView realtime which satisfies my needs.
One area that appeared to be improved in latest RTKExplorer was Combined forward-backward results. This is no help in realtime, but the data trend toward convergence and lock appears better in post-processing, so I don’t know why RTKNavi would not be be improved.
RTKLIB and RTKExplorer versions are similar , but not necessarily the same.
Environment: Poor Skyview both ROVER and Base. Much of sky blocked by Pine trees. Notice varying signal levels and SBAS blocked satellite.
Post Processing: forward + reverse ; 100% GPS+GLONASS+GAL+SBAS