my fisrt concern is if I can trigger the camera via USB.directly from Reach M+? If not, what kind of cable I need to trigger a Sony a7r iii, and get events via HSA?
Answering and giving you a scope of objetives
I got GPS/GNSS recivers for PPK
I plan to use a Reach RS as base for RTK,
(Alternatively, I can use a Reach m+ with RDF900 for long range corrections,
but that not be adressed at this step)
I don’t belive tat NTRIP could be a solution in an airplane, or in my area (NE of Argentina),
Te central idea is mount everithing in a plane (not a drone),
so there is no autopilot in the project.
I got a Reach M+.
The consecutive planning steps in my developement are:
test triggering from Reach M+
test events from HSA.
Integrate Hardware in a Pod appropiated for airplanes
Air test with RTK corrections
Software development of a tablet application with:
Logging data in the Reach M+ and RTK fix (if available)
get Location from Reach M+ (mock?)
Status of the location (FIxed or Autonomous for PPK)
Show pre loaded fligth plan to assist pilot
Show camera status (if I can wire via USB, but this is not mandatory)
Start and stop triggering based on location (triggering will be time based in te first developements)
This is for avoid photos during turns
export logged data
In a second version of the app I wish to get IMU data from Reac M+, so the final output could be position and attitude of the camera in each photo event
Sony A7RIII has a hot shoe, so you can use our adapter for making timestamps.
As for triggering the camera with M+, it requires creating a separate cable depending on the camera model. However, you can just configure time lapse on your camera. In that case, there’s no need in any separate cables.
Note, that IMU is on our to-do list, however, it is not yet implemented in ReachView. The good news is that the driver for the sensor is installed and you make use of it if you know Linux and programming.