You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there can be many reasons for this. Problems in the collected data, receiver performance, or the mode you use can lead to variations in estimation results.
Enable the error level of 3 and run it again, look at the errors for a good hint.
If I had to guess; you are in fact in autonomous mode (a least squares solution) and are not using the corrections source at all. It is possible you recorded this over the Sat-Sunday boundary and then entered the GPS week wrong? [In RTCM3 messages time is kept to 100nS on the current GPS week, that is why the tool is asking for what the apx date of the data is so it can determine the full time]
I made static measurements for 25 minutes, then when I post processing in rtkpos, I got 1.5 meters of error, what is the reason for this?
The text was updated successfully, but these errors were encountered: