Ask a Question
GoPro Support Hub Ask a question. Share an answer. Find a solution. Stay stoked.
Is your GoPro gear up to date? Check to see If it is on our Update page.
Posts: 0

Re: Hero5 Session Telemetry

Well I loaded a video from  my HERO5 Session up into the latest version of dasware and it loaded in teh telementary data and exported it into a CSV file


Here is a small sample of what was in the data file.


Posts: 947

Re: Hero5 Session Telemetry

That's cool, However, when I try to import data into RaceRender it says I'm exceedind the limits of the demo... so I don't know how well it works. From what you share, it looks like data might not be 100% accurate, numbers look too round. That might be a problem when it comes to stabilising footage and things like that. When I export the metadata with Stilldavid's tools, I get something like:




I've written some code to use this info to stabilise the image, and the result is pretty good. Maybe still not as good as the builtin EIS, but you can tweak it and, especially, decide whether you want it or not at home, after shooting. That and some work on after effects can give us lots of useful extra pixels to work with.


I owe you guys a tutorial whenever I've got spare time.

By the way, don't update to the new v2.00 firmware. Metadata is broken for me, and also the shutter speed menu and iso mode menus disappeared.

Posts: 5

Re: Hero5 Session Telemetry

I'd love to see a brief description of what all of these are actually logging.  Many are obvious, but I'm curious about some others.  For example, I see 8 different rpm logs.  I would assume 4 of those are propeller RPMs, but what are the other 4?  Also, GoPro Karma v1.0:KBAT[14] (%) would appear to be remaining battery life %, but it would be nice to know for certain.


Does anyone know if that info is available or maybe know what some of the things like ESCS, ATTD, GLPI, VFRH, etc stand for?  


GoPro Karma v1.0:TSMP[Time]
GoPro Karma v1.0:TSMP[0]
GoPro Karma v1.0:FWVS[Time]
GoPro Karma v1.0:FWVS[0]
GoPro Karma v1.0:KBAT[Time]
GoPro Karma v1.0:KBAT[0] (A)
GoPro Karma v1.0:KBAT[1] (Ah)
GoPro Karma v1.0:KBAT[2] (J)
GoPro Karma v1.0:KBAT[3] (degC)
GoPro Karma v1.0:KBAT[4] (V)
GoPro Karma v1.0:KBAT[5] (V)
GoPro Karma v1.0:KBAT[6] (V)
GoPro Karma v1.0:KBAT[7] (V)
GoPro Karma v1.0:KBAT[8] (s)
GoPro Karma v1.0:KBAT[9] (%)
GoPro Karma v1.0:KBAT[10] ()
GoPro Karma v1.0:KBAT[11] ()
GoPro Karma v1.0:KBAT[12] ()
GoPro Karma v1.0:KBAT[13] ()
GoPro Karma v1.0:KBAT[14] (%)
GoPro Karma v1.0:GPRI[Time]
GoPro Karma v1.0:GPRI[0] (s)
GoPro Karma v1.0:GPRI[1] (deg)
GoPro Karma v1.0:GPRI[2] (deg)
GoPro Karma v1.0:GPRI[3] (m)
GoPro Karma v1.0:GPRI[4] (m)
GoPro Karma v1.0:GPRI[5] (m)
GoPro Karma v1.0:GPRI[6] (m/s)
GoPro Karma v1.0:GPRI[7] (deg)
GoPro Karma v1.0:GPRI[8] ()
GoPro Karma v1.0:GPRI[9] ()
Distance Feet
Distance Meters
Distance Miles
Distance Kilometers
GoPro Karma v1.0:ATTD[Time]
GoPro Karma v1.0:ATTD[0] (s)
GoPro Karma v1.0:ATTD[1] (rad)
GoPro Karma v1.0:ATTD[2] (rad)
GoPro Karma v1.0:ATTD[3] (rad)
GoPro Karma v1.0:ATTD[4] (rad/s)
GoPro Karma v1.0:ATTD[5] (rad/s)
GoPro Karma v1.0:ATTD[6] (rad/s)
GoPro Karma v1.0:ATTD[7] ()
GoPro Karma v1.0:GLPI[Time]
GoPro Karma v1.0:GLPI[0] (s)
GoPro Karma v1.0:GLPI[1] (deg)
GoPro Karma v1.0:GLPI[2] (deg)
GoPro Karma v1.0:GLPI[3] (m)
GoPro Karma v1.0:GLPI[4] (m)
GoPro Karma v1.0:GLPI[5] (m/s)
GoPro Karma v1.0:GLPI[6] (m/s)
GoPro Karma v1.0:GLPI[7] (m/s)
GoPro Karma v1.0:GLPI[8] (deg)
GoPro Karma v1.0:VFRH[Time]
GoPro Karma v1.0:VFRH[0] (m/s)
GoPro Karma v1.0:VFRH[1] (m/s)
GoPro Karma v1.0:VFRH[2] (m)
GoPro Karma v1.0:VFRH[3] (m/s)
GoPro Karma v1.0:VFRH[4] (deg)
GoPro Karma v1.0:VFRH[5] (%)
Elevation Meters
Elevation Feet
Speed KPH
Speed MPH
Total Ascent Meters
Total Descent Meters
Altitude Min Meters
Altitude Max Meters
Total Ascent Feet
Total Descent Feet
Raw GPS AccelGs
Raw GPS LatGs
GPS AccelGs
GoPro Karma v1.0:SYST[Time]
GoPro Karma v1.0:SYST[0] (s)
GoPro Karma v1.0:SYST[1] (s)
Epoch Time
GoPro Karma v1.0:BPOS[Time]
GoPro Karma v1.0:BPOS[0] (deg)
GoPro Karma v1.0:BPOS[1] (deg)
GoPro Karma v1.0:BPOS[2] (m)
GoPro Karma v1.0:BPOS[3] (deg)
GoPro Karma v1.0:BPOS[4] (deg)
GoPro Karma v1.0:BPOS[5] (m)
GoPro Karma v1.0:BPOS[6] (m)
GoPro Karma v1.0:BPOS[7] (m)
GoPro Karma v1.0:ATTR[Time]
GoPro Karma v1.0:ATTR[0] (s)
GoPro Karma v1.0:ATTR[1] (rad)
GoPro Karma v1.0:ATTR[2] (rad)
GoPro Karma v1.0:ATTR[3] (rad)
GoPro Karma v1.0:ATTR[4] ()
GoPro Karma v1.0:SIMU[Time]
GoPro Karma v1.0:SIMU[0] (s)
GoPro Karma v1.0:SIMU[1] (g)
GoPro Karma v1.0:SIMU[2] (g)
GoPro Karma v1.0:SIMU[3] (g)
GoPro Karma v1.0:SIMU[4] (rad/s)
GoPro Karma v1.0:SIMU[5] (rad/s)
GoPro Karma v1.0:SIMU[6] (rad/s)
GoPro Karma v1.0:SIMU[7] (T)
GoPro Karma v1.0:SIMU[8] (T)
GoPro Karma v1.0:SIMU[9] (T)
GoPro Karma v1.0:ESCS[Time]
GoPro Karma v1.0:ESCS[0] (s)
GoPro Karma v1.0:ESCS[1] (rpm)
GoPro Karma v1.0:ESCS[2] (rpm)
GoPro Karma v1.0:ESCS[3] (rpm)
GoPro Karma v1.0:ESCS[4] (rpm)
GoPro Karma v1.0:ESCS[5] (rpm)
GoPro Karma v1.0:ESCS[6] (rpm)
GoPro Karma v1.0:ESCS[7] (rpm)
GoPro Karma v1.0:ESCS[8] (rpm)
GoPro Karma v1.0:ESCS[9] (degC)
GoPro Karma v1.0:ESCS[10] (degC)
GoPro Karma v1.0:ESCS[11] (degC)
GoPro Karma v1.0:ESCS[12] (degC)
GoPro Karma v1.0:ESCS[13] (V)
GoPro Karma v1.0:ESCS[14] (V)
GoPro Karma v1.0:ESCS[15] (V)
GoPro Karma v1.0:ESCS[16] (V)
GoPro Karma v1.0:ESCS[17] (A)
GoPro Karma v1.0:ESCS[18] (A)
GoPro Karma v1.0:ESCS[19] (A)
GoPro Karma v1.0:ESCS[20] (A)
GoPro Karma v1.0:ESCS[21] ()
GoPro Karma v1.0:ESCS[22] ()
GoPro Karma v1.0:ESCS[23] ()
GoPro Karma v1.0:ESCS[24] ()
GoPro Karma v1.0:ESCS[25] ()
GoPro Karma v1.0:ESCS[26] ()
GoPro Karma v1.0:ESCS[27] ()
GoPro Karma v1.0:ESCS[28] ()
GoPro Karma v1.0:ESCS[29] ()
GoPro Karma v1.0:EMPT[Time]
GoPro Karma v1.0:EMPT[0]
GoPro Karma v1.0:LNED[Time]
GoPro Karma v1.0:LNED[0] (s)
GoPro Karma v1.0:LNED[1] (m)
GoPro Karma v1.0:LNED[2] (m)
GoPro Karma v1.0:LNED[3] (m)
GoPro Karma v1.0:LNED[4] (m/s)
GoPro Karma v1.0:LNED[5] (m/s)
GoPro Karma v1.0:LNED[6] (m/s)
GoPro Karma v1.0:CYTS[Time]
GoPro Karma v1.0:CYTS[0] (s)
GoPro Karma v1.0:CYTS[1] ()
GoPro Karma v1.0:CYTS[2] ()
GoPro Karma v1.0:CYTS[3] ()
GoPro Karma v1.0:CYTS[4] ()
GoPro Karma v1.0:CYTS[5] (rad)
GoPro Karma v1.0:CYTS[6] (rad)
GoPro Karma v1.0:CYTS[7] (rad)
GoPro Karma v1.0:CYTS[8] ()
GoPro Karma v1.0:CYTS[9] ()
GoPro Karma v1.0:CSEN[Time]
GoPro Karma v1.0:CSEN[0] (s)
GoPro Karma v1.0:CSEN[1] (rad/s)
GoPro Karma v1.0:CSEN[2] (rad/s)
GoPro Karma v1.0:CSEN[3] (rad/s)
GoPro Karma v1.0:CSEN[4] (g)
GoPro Karma v1.0:CSEN[5] (g)
GoPro Karma v1.0:CSEN[6] (g)
GoPro Karma v1.0:CSEN[7] ()
GoPro Karma v1.0:CSEN[8] ()
GoPro Karma v1.0:CSEN[9] ()
GoPro Karma v1.0:CSEN[10] ()
GoPro Karma v1.0:SCPR[Time]
GoPro Karma v1.0:SCPR[0] (s)
GoPro Karma v1.0:SCPR[1] (Pa)
GoPro Karma v1.0:SCPR[2] (Pa)
GoPro Karma v1.0:SCPR[3] (degC)

Posts: 5

Re: Hero5 Session Telemetry

I just realized my previous post is in the Hero 5 Session forum, my apologies.
Posts: 583

Re: Hero5 Session Telemetry

Where did you get this list (of paremeters to be logged) from?

Posts: 5

Re: Hero5 Session Telemetry

I got this list using DashWare.  I've been using DashWare for years for track/autocross overlays, but I'm new to the drone world.  My inner geek thinks it would be cool to overlay things like propeller RPM or whatever other nifty things might be tucked away in the logs.  I'm just curious to know what all the less obvious parameters are actually logging.

Posts: 947

Re: Hero5 Session Telemetry

Here's a detailed tutorial on how to extract metadata from the Hero5 Session (and the H5 Black with a small tweak). Most video modes of the session record gyroscope, accelerometer and temperature data. These can be useful for visualising info or tweaking the image, for example to stabilise in post-production. Theoretically, the latest firmware update added ISO and shutter-speed metadata. BUT...


- Note1: For me, firmware v2.00 broke all the metadata, and other functions such as manual shutter speed for video, iso modes, external mic... I had to revert back to v1.50. So if you are interested in this, don't update your camera just yet.
- Note2: I learnt all these steps through my own experimentation. They are for advanced users and there might be more professional ways of doing this. This workflow is slow and won't suit most users' needs.
- Note3: This guide is for Windows but I think all the steps can be done in other OSs.
- Note4: I take the time to explain this because I want more people to start playing with these data and come up with new ways of extracting it and displaying it. Please share your ideas too.


Most of the work necessary to extract the data has been done by stilldavid.


1: Download ffmpeg and uncompress it somewhere in your hard drive:
2: Download and install Go Programming Language: (don't worry, you don't need to know coding to get the data out). Make sure to download a Windows build if you are on Windows
3: Create a folder in %USERPROFILE%\go\src\\stilldavid\ (replace %USERPROFILE% with you user profile folder, usually something like c:\Users\yourName\) You can get more help on this here:
4: Download the gopro-utils from by clicking on the green "Clone or download" button. Download as zip.
5: Unzip what you just downloaded, open the new folder and copy its content (it's also a folder named "gopro-utils-master") in the \stilldavid\ folder that you just created.
6: Remove the "-master" part from the folder name, so that it becomes "gopro-utils"
7: Like before, create a folder called %USERPROFILE%\go\src\\paulmach\ and repeat steps 4, 5 and 6 with these projects that gopro-utils needs to work: and


- Note5: If you just want to extract GPS data the way stilldavid conceived it, you're almost set up. I modified one of the files so that the Gyro, Accel and Temp information can be extracted in spreadsheet format.


8: Go to your folder \go\src\\stilldavid\gopro-utils\bin\gpmdinfo\ and replace the file gpmdinfo.go with my modified version of it: (you can do it by "saving as" from your browser or by editing the gpmdinfo.go in notepad and pasting the modified content).


- Note6: If you own a H5 Black (I don't), you can modify my file so that it also saves GPS data by uncommenting the GPS parts, that is, removing all the /* and */ lines and then saving the file. More data can be retrieved if you look into the gopro-utils code.


9: Still in the \gpmdinfo\ folder, unselect any file and do **bleep**F+RIGHT MOUSE CLICK and select "Open command window here"
10: In the command prompt, write "go build", withouth the quotes and press ENTER. This should create a gpmdinfo.exe file. If you did it all right, you won't need to repeat the previous steps.


-- Repeat from here for additional video files


11: Copy your gopro video file and open the \ffmpeg\ folder that you created in step 1. There, open the folder called \bin\ and paste your video file
12: Open a command prompt like in step 9 and type: "ffmpeg -y -i filename.MP4 -codec copy -map 0:3 -f rawvideo filename.bin" without quotes, where filename must be replaced with the name of your file. This will produce a .bin file.
13: Cut both the .bin and your .mp4 video files and go back to the \gpmdinfo\ folder of step 8. Paste them.
14: Open a command prompt and type: "gpmdinfo -i filename.bin". This will create 3 files accl.csv, gyro.csv and temp.csv. These are the data you were after. Open them with Excel or any similar software or create whatever you want with them. Copy them somewhere safe with the original video file, as the next file you process will overwrite them.


One simple thing you can do with all this is see the G-forces that the camera or yourself experienced during the shot.
I have also been playing with the data and it is really useful for stabilising the image, for example, without having to enable that setting in the camera and, therefore, without losing quality or field of view. Data is being recorded even in 4K, which means we can stabilise 4k footage! Will share my work on that later on. Unfortunately, it seems like nothing is recorded on framerates above 60fps. But I don't see why that wouldn't come in a future firmware update, if people start using these features.

Posts: 13,000

Re: Hero5 Session Telemetry

This information is great! Can you please create a group (the option is on the front page of support-right side-GROUPS) and post this information there. This thread will keep getting knocked down by new post and will eventually get lost without replies. If you make a group, it will be much easier to find.