Arduino Data Logger idea for Video Ride Creator

Any Arduino guys have time for a project?
We need a simple way to collect DOF data for live videos.
This way we can use the DOF data files with the up and coming Video Ride Creator / Player.
And make our own ride videos for our simulators!

The idea is to attach this device to a video camera and record the DOF data along with the video.
You then sync the data file up to the video file in the Video Ride Creator, and the next thing you know, you have a video ride to share!

What we need is a simple data logger that allows us to set the number of “captures per second”.
So we can sync it up nicely to the captured video.
(I would need to add a “Data Point Offset” to the app, as to allow the users to sync the video.
And then a “write final telemetry file” button to process the final telemetry file. Should not be to hard I think)

I see a device with one button, one led, a piezo buzzer and a 9v battery, along with the stuff listed below.
(You’ll need a SD card too) - besides the ard listed below, the other 2 parts cost about $10 usd!

Arduino Uno


Data Recorder Shield (SD Card)
http://www.amazon.com/SODIAL-Recorder-Shield-Logging-Arduino/dp/B00YM2SGR6/ref=sr_1_1?ie=UTF8&qid=1458373024&sr=8-1&keywords=Hot+Data+Recorder+Shield



3 Axis Gyroscope & Accelerometer
http://www.amazon.com/WYPH-GY-521-MPU-6050-Gyroscope-Accelerometer/dp/B00R5SYRS6/ref=sr_1_6?ie=UTF8&qid=1458373142&sr=8-6&keywords=MPU-6050


The way I see it working is like this:
When you initially turn on the unit with a blank formatted SD card inserted, the unit looks for a file called “cps.cfg” (or something like that) with the number of “captures per second” you would like to use. If it does not find this file it creates it with the default value of 100 written in it, and sets the “captures per second” to 100. The unit then blinks the led 3 times to show that it’s ready for operation. (This value can now be edited on the SD card to any value the user wishes to use)

The next time the unit is powered on, the unit will find the file “cps.cfg” and simply load the current value from the file. Then blink the led 3 times to show that it’s ready for operation.

When the button is pressed, the piezo buzzer chirps and the unit starts recoding data to the SD card. The led turns on, but blinks off occasionally.
(The piezo buzzer chirp is used to help sync the data being recorded to the video)
When it’s pressed again, the piezo buzzer chirps, it stops recording and the led turns off.

File Naming
The file should be named “1(30,Space).cfg”.
Where ‘1’ is the file count, then next file saved would be “2(30,Space).cfg”.
And where ‘30’ is the number of “captures per second”.
And just so you know, the ‘Space’ is the delimiter between the captured data points in the file. (In my Video Ride Creator app you can use Space, Tab or Comma)

So if there is no data files on the SD card, and they use the default number of “captures per second” and the device uses Space as the delimiter between data points, the file name would be “1(100,Space).cfg”. (of course you can do something different, say like a time stamp for the file name, but the end of the file should look like this “(100,Space).cfg” for the example above.

How to Save Data in the File
Save the data in this order with a Space, Tab or Comma between each value.
“Roll Pitch Heave Yaw Sway Surge”

(If you use Tab, the file ending would look like this (100,Tab).cfg
(Maybe make if configurable in the cps.cfg file?)
(Maybe the file should be called settings.cfg - lol)

And you will end up with a file that looks like this with Space as the delimiter:
193.55 0 -1.96 0 0 0
68.87 0 689.68 0 0 0
22.85 0 534.64 0 0 0
7.51 0 -1329.41 0 0 0
2.61 0 -3613.21 0 0 0
0.98 0 -1471.07 0 0 0
0.33 0 676.95 0 0 0
0 0 927.29 0 0 0
0 0 41.78 0 0 0
0 0 -3250.59 0 0 0
0 0 -2670.91 0 0 0

So, does anyone have time to help out?
The community will love you for it!
Have your name stamped on the beginnings of something really cool?

I could offer access to the SimTools 2.0 beta crew?
And I will through in a PRO key for SimTools 2.0 if you create a “How to Build” thread on the forums with pictures, so people can easily build your Data Logger?
yobuddy

@bruce stephen, (thx for all your posts on this buddy!)
May I ask you a question since you have experience with this stuff.
Since we don't need live feedback, wouldn't the $5 usd one I link do the job just fine?
And it should be enough to get all the data we need I believe?

Roll - degree data
Pitch - degree data
Yaw - degree data
Heave - acceleration data
Sway - acceleration data
Surge - acceleration data

-----------------------------

I think the cheaper they are, and the simpler they are to make, the more ride videos we will have.
A lot of tinkers have an arduino laying around collection dust.
And if the rest of the parts were under 15 usd, we would be golden!
Also, it would wright the file in a way the Video Ride Creator knows how to use.
(loads the files options from the naming scheme)
(And all the data is in the right order, right outa the box.)
(it's really had to tell what line of data is roll for instance, if its not properly synced to the video to begin with.)

Plus, people could add on new features.
Maybe we could configure which way is Up in software or something.
(how you mount the recorder to the cam, like if you wanted to set it on it side, but have that be Up)

And if everyone uses the same recorder, its so much easier to make tools for the output.
For instance, all I need to know is what is the max value is for the degree data and the acceleration data.
And in my app I can adjust the saved data to be used with SimTools with a single button click, and the user does need to mess with any settings etc..
(basically, normalizing and fixing the amplitude of the input data for Video Ride Player.)

Also if we make it with an arduino, there are a lot of options for the builder. (and they are available around the world)
I posted links to the parts that I thought would make it the easiest to build.
And I really like designing things so they are easily accessible by the most people.
But using a nano, you could build a tiny unit if you wanted to.

@cgodwin,
Thx buddy!
It could always be a team project also, should someone want to take the lead.
I would be just fine with that! (someone do hardware and the build thread, someone code or something)
I don't even mind throwing in a few bucks on the project, I just don't have a lot of time right now with the SimTools 2.0 beta going on.

I think I have a initial plan on paper now, but that does not mean it has to work exactly how I stated above.
It's just the initial idea that I believe covers what we need. (others may have better ideas)

Thanks all!
yobuddy

Although I don't know yet what exactly we need for the module.
Here is another low cost option. its 9dof like the one in the vid above. ($11.46 usd)
http://www.ebay.com/itm/like/281969078236?lpid=82&chn=ps&ul_noapp=true
maybe others that have used there things can chime in here...
yobuddy

@Blame73,
Its not a bad idea, but it would make the whole thing bigger.
And sort of tie it to that display, or the one selected.
And then there is cost and would it may reduce the speed of the recorder etc...

A little settings app could be made to read, display and edit all the settings easily.
Possibly built into the Video Ride Creator.

There are some cheep ways to add some of the info you have posted thou.
because these are good ideas!
but maybe not for version 1 is all I'm saying.

like we could add a led that blinks when space it getting low. (out of storage warning)
And maybe this level can be set in the settings.cfg file.
(Anyone know if the arduinos work with xml files? maybe settings.xml is better?)
So the warning is selectable of when it should trigger. (10% left etc.)

Honestly, once the basic stuff is done. (call it the cheap as it can be version)
Anyone could add onto to it and we could have many versions a user can build.
With the controls they want and as fancy as they can make it.

Maybe we could try to think of all of the editable settings we would want in the settings.cfg file and make a list.
Even if we don't use these settings now for version 1, we would not have to update the app later for the new additions.
And it would be easier for users to modify later I would imagine.

I can think of these:
Capture Fames PerSec
Low Space Alarm Limit (Percent)
Led Brightness
LCD Backlight OnOff
Buzzer Volume

Maybe some settings for the module: (im guessing on these)
Sensitivity X
Sensitivity Y
Sensitivity Z
Orientation X
Orientation Y
Orientation Z

And maybe a few optional entries (incase a build needs something we don't have)
Extra1 Name "Tell the user what they are editing" - reports to pc app / maybe gets shown on a lcd etc..
Extra1 Value 0
Extra2 Name "Example - Second Buzzer Volume"
Extra2 Value 10
Extra3 Name "Second led brightness"
Extra3 Value 90

So what am I missing anything someone may want to use in the future???
Maybe there is a better way to do this?

Remember, either a app on a pc could change these settings.
Or the hardware on the device itself.
And a updated version of the ardiono file could always display stuff in all sorts of ways.
(Like the lcd unit you have posted!)

We should definitely keep it simple to start with.
a lot of this may be clearer once the project has started.
yobuddy

btw, Maybe holding the button down for 5 seconds chirps the buzzer, and if you let go of the button, it erases the last file saved to the sd card?
Keep holding the button for 12 seconds and it chirps 3 times, let go of the button and it erase all of the files on the sd card?

Very Cool!

The only problem I see with the phone idea, is that some phones cost a ton! lol
Mine sux, but a lot of people spend way to much on them.
Not sure I'd want to strap it to a roller coaster for instance.
But a cheep GoPro and a 50$ device I would.

But I'd love the option of having both lol
Dustin

Then again, if its runs on android, any android device with these 3 sensors would work!
So I think this could work!

Right on you guys!
I think your on to something here!
Dustin