We are looking for information about the integration of the reach gps in order to get precise geotagging for two well known sensors in the UAV community: micamsense rededge and flir VUE pro R. There is good documentation regarding the integration of RGB camera with hotshoe but I did not find a lot of info for other well used sensors like micamsense rededge or flir VUE pro R .
For the integration of micasense, I found two old topics:
In these topics @igorvereninov mentioned that emlid was in contact with micasense… @igorvereninov , have you some updates about theses exchanges with micasense?
As a first approach, as Micasense and flir allow to use external gps info, we though to connect reach to the camera in order to be used for the geotagging in the exif during the flight. Back to office, we intend to perform PPK on the raw logs and then replace the XYZ in exiff wth the corrected ones (using XYZ and time matching). What do you guys think about this approach?
I’ll answer for Igor and seems like there’s not much progress there. However, I don’t see why you can’t use the normal workflow used with standard cameras - connect Reach to your camera, record events during your flight. Process the logs and get a CSV with the coordinates of the photos in chronological order.
@egor.fedorov, what do you think of the alternative solution where reach gps in RTK mode is connected to the gps port of micasense or FLIR vue pro ? It would allow in-flight precise geotagging … Correct me if I am wrong (or I am missing wiring or timesync issues that I don’t know) but this method is absolutely equivalent right?
Looking at the docs, I don’t really see a way to sync with the hotshoe without getting inside. Moreover, it seems like they only accept UBX protocol as an input for tagging pictures which is also not really nice. Something standard like NMEA would do the job.
PPK has the following advantages:
Most importantly, depending on the speed of your aircraft, update rate may become a limitation. Our PPK routine includes interpolating event positions, while the camera will(very likely) just use the last one available, increasing the error.
You don’t need to provide a correction link for RTK corrections
If you require absolute precision, it’s easier to get via PPK. If you want to have everything immediately(to not retag pictures, for example), you’ll need to worry about settings up a base and getting its true position.
RTK, on the other hand, will provide:
Cool and smooth RTK data for you to fly with
Images tagged with the locations, so you don’t have to do it manually.
Thanks for your return. @egor.fedorov, could you please confirm through the following questions that we understood you well?
How can we set reach gps position output from reach to work with micasense rededge? I am a bit confused because UBX is not an output position format
it is not possible to connect the micasense to the reach in order to get a message in reach log when a set of pictures are taken (like we do with hot shoe and rgb dslr camera). right?
If 2) is indeed not possible, we have to deal with direct geotagging during the flight through reach position output. If we can provide input correction to our reach gps, we have RTK geotagging.
But if we want PPK, we have to match gps time in image geotags to gps time in reach log (previously postprocessed)…
Oh. I wasn’t quite clear on this. It seems like the camera only accepts UBX, and we can’t output that. I was trying to say they should have stuck to something vendor-neutral. Sorry for the confusion.
I guess it is for you to figure out. The docs don’t seem to reveal a way to sync camera trigger to Reach by default or by design. I think you have a good chance of hacking something together if you disassemble the camera, but it’s up to you to decide whether you want to take the risk with expensive equipment.
We found a nice solution for the red edge using the link provided by @Seb_B to configure the PPS pin to work as an output which will be recorded as _event by your reach unit.
Simply use an external power source and PWM output (using pixhawk in our case) and plug the 6 pin cable from micasense to the underside 6 pin slot of the reach, the one with the time mark pin. This will allow you to use the ‘hotshoe’ protocol.