Stop & Go Survey correction

Hi Team,

My set up is in India, I have used RS2 as the base and the RS3 as the rover. i have used ntrip via my phone Bluetooth at RS3 and WiFi for RS2. After completing the survey with proper fixes throughout, when I am using Emlid studio to do correction with CORS network in India. studio could not get any fixes. what am I doing wrong ?

Was the acquisition time set to instant in Emlid Flow?

If so, you’ll need to tweak the output csv from the app (add 1/100 second to the end time, for example). Emlid Studio can’t deal with the start and end time fields having the same value and skips processing any point collected that way.

1 Like

Hi Sanjeeth,

Welcome to our community!

First of all, @Gabriel_C is right. The points need to be collected with averaging for Stop & Go. Were they collected this way?

If so, I’d like to check your data in more detail to see why the post-processing doesn’t give FIX solutions. Could you please send the base logs, the rover logs and your CSV file to support@emlid.com?

If you have FIX throughout the whole survey, it’s not strictly necessary to perform PPK as well. Or do you need it for some particular reason?

Thank you, for your kind clarification. Yes this was instantaneous fix in most of the places, only average was in place where there was no cellular coverage. The reason i wanted to correct was because of my assumption that, if i am correcting the base via CORS, rest of the data that i have collected via stop and go also would have to be corrected. One question i still have is, if this was instantaneous fix as was in my case, what would be accuracy and repeatability of the points that i have collected ?

Yes, you are right it was instant fix

Relative to your own locally placed base, the specs of the receivers: 14mm+1ppm in ideal environmental conditions.

Then you can compound it with the inaccuracy of the base relative to your CORS after post-processing.

Hi Sanjeeth,

In good environmental conditions, a FIX solution should provide centimetre accuracy even with instant collection. But if you have locations where the RTK connection isn’t working due to the lack of cellular coverage, it’s indeed worth performing Stop&Go.

Please feel free to email the logs and the CSV to support@emlid.com, and I’ll take a look at the post-processing. Thanks!