Hot shoe and RTK/PPK work flow

Hi,

I have a drone set up with the reach RS2 as base. The R2 rover is set up with RTK corrections and the autopilot triggers the camera based on a flight plan. A hot shoe is connected back to the autopilot (cube) so that GPS raw coordinates can be logged precisely. The hot shoe needs to be connected to the reach GNNS directly in order to follow the suggested emlid-PKK workflow. My questions:

  • Is it advised to have the hot shoe connected to both the autopilot and the reach? I prefer also logging to the autopilot. I can possibly modify the hot shoe cable.
  • Can one accomplish similar accuracy using the RAW GPS that is logged from the autopilot, if so, does anybody have a suggested workflow for PPS where the autopilot records the CAM-events?

Any help appreciated, thanks!

Electrically, yes, recommended, nop.

It cannot, unless it has a PPK capable GNSS module inside.

Thanks for you quick reply, Christian

Can you elaborate on this? Are you suggesting this is not a good idea? One could add diodes downstream the hot-shoe split. I was thinking just to solder the signal and gnd wires and add to the reach unit with no additions.

Thanks!

Hi @atob,

Let the Reach do all time marking job. It’s designed for that.

Reach M2 records time marks from the camera to the raw data log. Recorded time marks don’t have any coordinates in the log, only time. Coordinates can be acquired during post-processing only.

The event marking with the modified cable will be unstable. You can lose time marks in the raw data with the described connection. So the camera should be connected straight to the Reach M2 without any additional connections.

3 Likes

2 posts were split to a new topic: PixHawk 2 with Reach M2

Hi, thanks for the response. I have purchased an emlid hotshoe cable and have received it now. Will start testing this workflow shortly.

Hi @atob,

Good news! Don’t forget to share the results of your tests :slight_smile:

1 Like