The images were auto triggered by the Altum to allow for 80% frontlap and 80% sidelap. The flights were conducted at 120 m static altitude above ground surface, at a velocity of 10.7 m/s. The max image rate for the Altum is 1.5 Hz. I have not investigated where the missing images are from yet…
Tobias…is it the GLONASS AR MODE off, or the Elevation mask angle (15 vs 20) or SNR mask (30 vs 35)?
This. If no solution an event will not record.
The only settings relevant for logging/PPK are the satellites. You should choose less satellites in order to log with 5 Hz.
The rest of the settings are for RTK.
What would you recommend? GPS only at 10 Hz, GPS/Galileo at 5 Hz, or GPS/GLONASS at 5 Hz?
5 Hz and satellites according to your region. Maybe GPS and Galileo. I used GPS + GLONASS + QZSS for a long time but the GLONASS data quality was always lower then the GPS data quality. I will try GPS and GALILEO from now on.
Sorry @RTK_Hunter, I did not realize you are situated in US too, all this names with RTK.
I currently run GPS, GLONASS, Galileo and SBAS. I have yet to try Beidou in my area as @timd1971 has brought up. By running all I can view the statistics during PPK and remove constellations if they are weak. Since running the Emlid equipment I have seen that there are some fairly consistent issues with GLONASS. Central Texas here.
I agree with suggestions above and think that the main issue is GNSS selection and update rate.
May I ask you to upload it to any file transfer service and post the link here? I got not all the logs in email because of its size.
I emailed the UBX logs to you directly, individually they are all smaller than the 20 MB limit. Is there a way to post process the current data that I have, or will I need to change the GNSS selection and Update Rate? For Montana in the USA what would you recommend as a starting point? GPS only at 10 Hz, GPS/Galileo at 5 Hz, or GPS/GLONASS at 5 Hz? Per Tobias recommendations I will try the next data collect with GPS/Galileo at 5 Hz.
You should turn ON only GPS and Glonass if you want to use 5 ghz rate.
GPS + GLO @5hz for U.S. You can try Galilieo but I don’t always have high number of satellites.
Use this to see what sattelites are actually in the sky where you are at: https://play.google.com/store/apps/details?id=com.nec.android.qzss.gnssview&hl=en_US
OK thanks everyone. We will try the GPS + GLO @ 5 Hz for the next test. Regarding the GLO AR Mode…Off or ON?
Another question…When post processing the data, if we setup the Reach RS+ head on a 2 m pole on a known surveyed location. Can this be entered in the RTKPOST app in OPTIONS --> POSITIONS? Enter the DMS for the Lat and Long of the surveyed point? Would the Height be the elevation of the point on the ground or ground elevation plus 2.087 m (2 m for pole, 0.022 for the 1/4" to 5/8" adapter, and 0.065 for the distance between the bottom of the Reach RS unit and the center mark).
I’ve checked your raw data logs, and they look fine. I believe the main issue with time marks is wrong settings.
At the moment, it’s not possible to recover missed time marks, I’m afraid.
You can specify the base antenna height in Delta U field.
GLONASS AR should be on. I would highly recommend turning on Galileo as well. As long as you have 3 good satellites you are getting triangulation and they can always be dismissed in processing.
I am going to try these settings for my next test today, exact settings applied to my base and rover units:
Thanks Tatianan for the infor regarding the base information. I will input this in my next post processing.
If you have 2 units you could test GPS and GLO vs GPS and GAL. I think the second is the better configuration.
@wsurvey recommends to use BEIDOU as well (GPS, GAL & BDU) and fix probably missing events in post processing. He recommends GeoAdjusd which works for P4P images from DJI and I have writtem a tool to match images and events regardless of the camera manufacturer and the time settings. I have greatly profited from @wsurvey earlier recommendations and will adapt these settings for my next campaign. I will have the possibility to check against a Leica device and will report.
I performed 12 flights over two days last week with the Altum and the Reach M+/RS+ system. I plan to begin the Reach processing today, then import the data into Pix4d for processing. I have a question regarding setting the RS+ antenna height in RTKPOST ver 2.4.3. I am in OPTIONS window as seen below:
I have the coordinates of the base station location collected from an L1/L2 GNSS CHC system, processed in OPUS in the USA. I have the Easting, Northing, and Orthometric height of the surface point on the ground where the base was located. I put my RS+ on a 2 meter pole at this location. If the ground base location is 1531.0145 m (orthometric height) should I enter the height in the Delta U as the ground elevation, ground elevation plus 2 meters (for pole), ground elevation plus 2.022 (2 m for pole and 0.022 for 1/4" to 5/8" adapter), or ground elevation plus 2.087 meters (2 m for pole, 0.022 for the 1/4" to 5/8" adapter, and 0.065 for the distance between the bottom of the Reach RS unit and the center mark?
In addition for the Easting and Northing location to I enter this in the Delta E/N/U (m) field or in the Lat/Lon/Height (DMS/M) field? I tried entering this info in the Delta E/N/U and recieved an empty position file from the output. Thanks everyone for your help.
Delta is for the antenna offset. That is your pole only. You need to convert your coordinates. You can use the height without conversion, I think. You also need to read the manual… .
I think the ground elevation and pole offset should have either been accounted for in in Reachview or whatever data collection software you used making the drone relative to that ground elevation. All you should have to do is enter the antenna offset for the rover (drone) and the base ground elevation converted to meters. I would put the base position in QGIS as a point with your XYZ (State Plane?) coordinates and export it back out as WGS84 - unless you have another converter.
Hello, from RTKLIB manual 2.4.4
(5) Position (pag. 43-44)
Lat/Lon/Heig ht (deg/m)
Set the position of the base‐station antenna.
‐ Lat/Lon/Height (deg/m): Latitude/longitude/height in degree and m
‐ Lat/Lon/Height (dms/m): Latitude/longitude/height in degree/minute/second and m
‐ X/Y/Z‐ECEF (m): X/Y/Z components in ECEF frame.
‐ RTCM Station Position: Use the antenna positionincluded in RTCM messages
‐ Average of Single‐Pos: Use the average of singlepoint solutions
‐ Get from Position File: Use the position in theposition file. The station is searched by using the head 4‐character ID of the rover observation data file
‐ RINEX Header Position: Use the approximate position in RINEX OBS header.
Set the delta position of the base‐station antenna as E/N/U offsets of ARP position with refer to the marker (m).
Reach RS+ U (m): 0.065 (ARP to L1)* + 0.0215 (adapter 5/8" to 1/4") + heigth of rod and other adapters
*As RS+ is not included in the IGS antenna file, it must be added
Greetings to all
Saludos a todos