Get GCP's processing PPK using RS2 as Base and RS+ as Rover

jpgayoso · September 6, 2023, 6:40pm

Dears

I tested my RS2 as base and RS+ as Rover. My plan was to create GCPs with PPK postprocessing. Using “Stop to Go " processing with Emlid Studio, the PPK process seems to result in good shape, showing the path with the fix%,Float% and Single%; but when tried to correct the “points” from the CSV file, appear the message: " 0 points out of 3 were averaged in SINGLE, FLOAT , FIX”. If a review the CSV the 3 points are there, but for some reason They are not corrected. It is the setup of my base and Rover:

base RS2>

Rover RS+>

As you can see both use the positioning Mode: Kinematic.

You can get the data for here: myQNAPcloud

thank you so much for your support.

jpgayoso · September 6, 2023, 6:43pm

Dears

I tested my RS2 as base and RS+ as Rover. My plan was to create GCPs with PPK postprocessing. Using “Stop to Go " processing with Emlid Studio, the PPK process seems to result in good shape, showing the path with the fix%,Float% and Single%; but when tried to correct the “points” from the CSV file, appear the message: " 0 points out of 3 were averaged in SINGLE, FLOAT , FIX”. If a review the CSV the 3 points are there, but for some reason They are not corrected. It is the setup of my base and Rover:

base RS2>

Rover RS+>

As you can see both use the positioning Mode: Kinematic.

You can get the data for here: myQNAPcloud

thank you so much for your support.

kirill.pavlyuchuk · September 7, 2023, 11:13am

Hi Juan,

Your points weren’t processed because they were collected instantly without averaging in Emlid Flow. For Stop & Go workflow, it’s essential to average points. Otherwise, you’ll get zero points processed.

I’ve fixed your CSV file by adding one second to the time stamps of the averaging end. Then I used the following settings in Emlid Studio

and got 28.1% of the FIX solutions in the pos file.

I processed the fixed CSV file using this pos file, and 2 points of 3 were improved to the FIX solutions.

Such a result is expected because the log’s quality shows that you worked in pretty harsh conditions for the single-band device:

These alternating grey and red bars show parity unknown flags and cycle clips, respectively. They appear when the signal is interrupted and the half-cycle ambiguities in carrier-phase aren’t resolved. When they’re not resolved, you get the FLOAT solutions presented during most of your log.

I’ve attached the resulting pos and CSV files to the zip archive below.
Juan Pablo.zip (265.9 KB)

kirill.pavlyuchuk · September 7, 2023, 11:17am

Hi Juan,

A small update: once I set the Integer ambiguity resolution for GLONASS satellites to ON, I received 35.3% of FIX solutions in the pos file and all three points were improved to the FIX.

The zip archive with the resulting files is attached.
Juan Pablo final solution.zip (259.6 KB)

jpgayoso · September 8, 2023, 4:05am

Thank you so so much, Kirill. 2 questions, please:

In order to collect points with averaging, so I need to change the setup in Emlid Flow?. I don’t know why the RS+ leave to average the data.
I select GPS, GLONASS, QZSS, only. With this combination is better to include GALILEO and BEIDOU, too. ?, i need to change the “Update Rate” value ?

Thank you, again.

kirill.pavlyuchuk · September 8, 2023, 7:23am

Hi Juan,

You need to click on the gear in the Collector tab

and configure the averaging timer:

All constellations will give you a higher chance of receiving the FIX solution. You can leave the Update rate as is, I suppose it’s the 5 Hz for both base and rover.

jpgayoso · September 10, 2023, 3:45am

Thank you so much, Kirill.