- Firmware image and ReachView version v2.7.2 and earlier.
- Detailed problem description.: ReachView performance much worse than RTKNAVI
- Your step by step actions.: If I use ReachView, I almost always get poor FIXes and erratic FLOAT with ReachView in obstructed skyview.
Using RTKNAVI on same Rover-Base, I get much better FIX and FLOAT performance.
I have ignored the problem until now as I have been using PPK mostly.
The only thing that seems different is that in RTKNAVI, the Base Correction is provided in UBX format while .in ReachView the correction is RTCM3.
I know that RTKLIBExplorer added some fixes to RTKCONV saying that a lot of fixes were in the conversion from ubx to RTCM3, but don’t know if these are related.
It is not a big problem for me, as I can use a PC or tablet & run RTKNAVI for realtime solutions, but I can’t see why I would have the problem if others don’t… Using the smartphone certainly has advantages of reducing the weight of equipment.