Joe I see that your antenna height on the rover is .23 m. My height from the base of the antenna to the center of the camera on my Metta PPK Kit/Phantom 4 Pro is .17 m. Then I add .035m for the phase center of the antenna for a total of .205m. Was that a typo or are you using a different antenna?
I hadnāt measured the antenna yet, I assumed it was done when you take a photo on the GCP? Using the height of the GCP (measured with a RS2), youād take away the elevation PPK result of the photo and that would be your height?
In PPK each photo trigger is a measurement at the phase center of the GNSS antenna. You apply the offset to get the accurate photo center. In my case it is .205m. Iām still testing and need to determine the forward offset due to the angle of forward tilt of the drone. Iām surprised not to find more info on this topic as I would expect a lot of these PPK kits are out there on P4Pros.
As for the camera shot while on the target that is where you would add an additional measurement from the center of the camera to the bottom of the drone base and would subtract that value from the height obtained in the events file for that event to determine the accuracy of that measurement compared to the surveyed value.
It might be best if ES match photos not just by order but also by times. This might solve problem of number of photos not equal to number of PPK points.
ES Match?
Hi Joe,
If you put in measured antenna height when you set raw data recording, you donāt need to add it in Emlid Studio. This value is already in the RINEX header.
I need a bit more time to check out. Iāll analyze your logs and get back to you soon.
I didnt get a reply on why it wouldnāt accept the number of photos?
@wizprod PMād me and told me that I had alot of noise - something I had with the Tuffwing kit as well. I will be starting a new thread on noise.
When this is all done, Iām going write a detailled document on all these issues and the correct way to set this up, troubleshooting etcā¦ There doesnāt appear to be much documentation.
Hi Joe,
Iāve checked your logs and post-processed them in Emlid Studio. I got 890 events: 888 in Fix, 1 in Float, and 1 in Single. The same as your result, I suppose.
Iāve also found 889 time marks in your log and 1 invalid time mark. So, their total quantity equals 890. Itās the same as the eventās quantity from Emlid Studio.
Invalid time marks are a very rare issue. Usually, they are caused by hardware setup. In your case, it may happen because of the connection between the droneās camera and Reach. We can hardly comment on that setup because itās a non-standard way of integration.
How do you spot these?
So, that means that it is a manual procedure of string-searching in the rinex file, or ?
Yes, it is manual searching.
is it possible to add this functionality to the studio, ie it brings up a warning if this is the case?
Seems like an obvious way to help the user 
I sure this is a silly question but the Mettatech website doesnāt mention the V2 only the V1. Is it now compatible with the Pro V2? Iām looking at purchasing the kit as well. Thanks
Itās compatible with any Phantom 4 (standard, advanced, Pro, Pro V2.0). Ideally youāll be using it with at a P4 Advanced, Pro or Pro V2.0 that have the 1-inch sensor camera
Hi Joe,
It looks like a mismatch between the number of photos and time marksā quantity in Emlid Studio. We consider such cases and help each user individually cause hardware setups may be quite different.
I really appreciate your posts. I had doubts between getting Tuffing or Mettaās one. Now I know I can trust more in Mettaās Kit. Iāve read recently that theyāre also selling a GNSS Base based on M2 and a big anthenna. Iāll try working with both products.
Dear Luis, I had Tuffwing initially and then I bought the PPK kit from Metta because it works with the Tallysman antenna which allowed me to have a better solution compared to the Tuffwing antenna. About Mettaās Gnss antenna with M2 module, I already bought it and Iām waiting for it to arrive so I can test it.
For Metta or Tuffwing phantom 4 Pro PPK KIT users, you can correct the delay (0.3) of the photosensor with āUAV - PPKā and further improve the accuracy of the cameras. I recommend it if you want to work without photogrammetric Support Points.
