What do the GoPro 3+ and 4 connectors on the gimbal do?

Joined
Nov 5, 2018
Messages
8
Likes
0
Age
54
#1
Hi,

Can I have a high level detailed explanation of the two connectors on my gimbal do? There is the big one and the little one. Can the HDMI communicate in both directions? Is there a specification on the web?

Is it possible to geotag the images through hdmi instead of the the manual ftp geotagging?

Thanks,
TFPJ
 
Last edited:
Joined
Aug 31, 2017
Messages
445
Likes
194
Location
USA
#4
Clarification:
The "small" cable on the side of the gimbal in the rubber protector is a micro-HDMI. It is not bi-directional in any meaningful way, except that the HDMI specification allows for device capability enumeration (a basic "hi, I'm a video device and this is the type of video I send", nothing more).

The larger, fixed bus connector INSIDE the gimbal's GoPro frame is the GoPro Hero Port bus. This is bi-directional. This supplies sufficient power to prevent the GoPro from running down in usage, and allows for commands to go from the Solo to the GoPro. Conceivably, if there was support in the GoPro Hero Port API and on the Solo, feedback/commands from the GoPro could go upstream.

Currently there is no way to directly write metadata to the images stored on the GoPro through the Hero Port.
 
Joined
Nov 5, 2018
Messages
8
Likes
0
Age
54
#5
Thank you Naib! That is the answer I was looking for ... It seems that an app can be written to find the log files on the solo and add the geocoding ... The app would have to run on a/the PC once the files are uploaded ... The underlying question is 'why this has been done', and you answered the 'why' ...

That would be a fun project to write if I were younger and had the energy ...

TFPJ
 
Joined
Aug 31, 2017
Messages
445
Likes
194
Location
USA
#6
Thank you Naib! That is the answer I was looking for ... It seems that an app can be written to find the log files on the solo and add the geocoding ... The app would have to run on a/the PC once the files are uploaded ... The underlying question is 'why this has been done', and you answered the 'why' ...

That would be a fun project to write if I were younger and had the energy ...

TFPJ
There are a number of solutions for the geotagging currently. You have Mission Planner (via the godmode menu, CTRL+F), GeoSetter (my favorite), and through an add-on purchase within Solex (I have no experience with this quite yet).

There are a number of changes happening in upstream ArduPilot/ArduCopter which will hopefully improve the accuracy of the geotagging results regardless of which method you choose.
1) A number of users reported poor/variable logging and timestamping, and this has been iterated upon in AP, which should result in more deterministic differences between logged time and "triggered" time. I don't have the PRs on hand for this, but if I recall correctly, this issue is being addressed from about 3 different angles. Final result should be that logged time is deterministically offset from actual time by about 40ms, and trigger events reflect this, so timestamps attached to events are actually the timestamps that should be attached, not something about 20-400ms in the past (currently).
2) Matt has written some updates to OpenSolo that will force a GoPro clock sync to the GPS on the Solo at boot/arm. This should help with another huge source of error in the geotagging process, the systematic offset of timestamps between the GPS/log data and the time the GoPro is synced/set to. I've asked about triggering this sync prior to each photo and was informed that:
A) it might not be feasible time-wise depending upon photo interval
B) GoPro clock doesn't drift meaningfully during 10-20min periods while powered on
C) GoPro clock has an internal resolution of 1s, so there is little benefit to constantly re-syncing to the GPS since it is so coarse

So, hopefully soon, even if the process doesn't necessarily change, our results should be far more robust. I'm super excited.
 
Likes: Wetstone

New Threads

Members online

Forum statistics

Threads
11,768
Messages
138,509
Members
13,543
Latest member
lincoln57