<div dir="ltr">Agreed,<div><br></div><div> Make a suggested sensor design and send it to Masten. They are accepting suggestions on the sensors for the sensor suite. They will conclude the final design of their choice and build and install it on the vehicle. You guys provide the finalized code.</div>
<div><br></div><div> - Ethan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 16, 2014 at 6:49 PM, Stephan Henning <span dir="ltr"><<a href="mailto:shenning@gmail.com" target="_blank">shenning@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">David is correct, unless you are using a very very high end GPS module (which most likely would have an internal IMU at this point), do not rely on its data for altitude unless you have to. There are sensors out there with better resolution, , update rate. and are nice and cheap that would work just as well. GPS can be very finicky, redundant data sources is a very good thing to have. <div>
<br></div><div>I haven't been paying very close attention to this conversation thread, but if the sensor package can be built cheap enough, it may not be a bad idea to have two. I would be worth spending some time to make sure all the sensor data timing is well understood and synchronized. You never know what you might be able to learn from a successful (or failed) flight if you have accurate time data attached to the sensor measurements. </div>
<div><br></div><div>It might be worth investigating having a redundant memory storage device, maybe back it up on a 'rugged' usb drive that might have a chance of surviving a flight failure. </div><span class="HOEnZb"><font color="#888888"><div>
<br></div>
<div>
-stephan</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 16, 2014 at 7:28 PM, david <span dir="ltr"><<a href="mailto:ainut@knology.net" target="_blank">ainut@knology.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
There are 9+ (so-called) DOF sensors on the market now in a single
package (some under $40), obviating the need for a separate
accelerometer. It would definitely be interesting to see the
G-forces as applied all along the track.<br>
Unless someone in the project is married to the RPi, the BeagleBone
Black (BBB) has a lot more compute power and functionality.<br>
<br>
Don't count on the accuracy of GPS altitude unless you have a
confirmed WAAS (or equivalent) signal all during the flight. GPS
antenna is a major concern in this type of environment. Some GPS
modules can use signals besides just the ones from the US, but the
other countries' WAAS-equivalents are even more flaky than ours! :)
The MTK3339 GPS (like used in Adafruit's Ultimate GPS products)
seems to be robust. I'm just beginning to program it now. Very low
power and can be had for under $16 in small quantities, or with
circuit board and glue for about $40 from Adafruit.<br>
<br>
For recording video and metadata, again, the BBB is a good choice as
I have confirmed it works with a 32 Gb SD card. By the weekend,
I'll know it if works with the newer 64 Gb SD cards.<br>
<br>
David M.<div><div><br>
<br>
<br>
<div>On 07/16/2014 05:49 PM, Ethan Chew
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Cool!
<div><br>
</div>
<div> So we are talking about the following things we want
to do:</div>
<div>
<ul>
<li>In-Flight Automated Photography</li>
<ul>
<li>Overlay in-flight metadata from on-board sensors; <span style="font-family:arial,sans-serif;font-size:13px">GPS
coordinates, altitude, temperature, air pressure, CO2,
speed, and time from launch (T+).</span></li>
<li><span style="font-family:arial,sans-serif;font-size:13px">Can
be done either in-flight or as post-processing (encode
flight data as exif, add overlay in post).</span></li>
</ul>
<li>Record flight data for post-flight modelling and
visualization opportunities.</li>
<ul>
<li>Record 6-dof, acceleration and skin temperature data
in-flight.</li>
<li>Calculate ballistic coefficient to add to
visualization opportunities.</li>
</ul>
</ul>
</div>
<div> And that would mean the following sensors:</div>
<div>
<ul>
<li>Video/Photo Camera</li>
<li>GPS (speed & altitude can be derived from GPS data.)</li>
<li>Altimeter</li>
<li>Thermometer (setup for ambient and skin temperature
readings)</li>
<li>Barometer</li>
<li>CO2 Gas Sensor</li>
<li>Clock (can be done by the Raspberry Pi.)</li>
<li>6-dof sensing</li>
<li>Accelerometers</li>
</ul>
</div>
<div>Made a wiki: <a href="https://256.makerslocal.org/wiki/Flight_Code_Project" target="_blank">https://256.makerslocal.org/wiki/Flight_Code_Project</a></div>
<div><br>
</div>
<div> - Ethan</div>
<div><br>
</div>
<div>P.S. Of administrative note; I got a clarification from
Masten about educational institutions flying for free. At
this point in time, the Prometheus Project is open only to
educational institutions as Masten is seeking to encourage
high school and college students to get into engineering.
Therefore, the project would have to involve students in <span style="color:rgb(0,0,0);font-family:sans-serif;font-size:13px;line-height:19.049999237060547px">designing,
building, and programming the flight experiments. The
project could either be run as a class and teaches UAH and
other Huntsville high school students or the makers involved
would academically advise a student team. </span></div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:13px;line-height:19.049999237060547px"><br>
</span></div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:13px;line-height:19.049999237060547px">Kix,
taking a page out of your book, how did you run your program
with FIRST Robotics when you were in the Makers Local 256
shop?</span></div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jul 16, 2014 at 8:05 AM,
Phillip Showers <span dir="ltr"><<a href="mailto:phillip.showers@gmail.com" target="_blank">phillip.showers@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>you definitely want 6-dof for post flight modelling
as well. tie in a common variable like time and pump in
stuff like 6-dof, acceleration and skin temp. You can
probably just calculate the ballistic coefficient from
cad but that gets you started on some really fun
visualization opportunities.<br>
</div>
<br>
Phil<br>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jul 16, 2014 at 8:34
AM, Satyam Nayak <span dir="ltr"><<a href="mailto:nayaksatyam@gmail.com" target="_blank">nayaksatyam@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I ++1 Josh's suggestion about
adding metadata to the picture. </div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jul 16,
2014 at 8:57 AM, WebDawg <span dir="ltr"><<a href="mailto:webdawg@gmail.com" target="_blank">webdawg@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Even better to have it
upload that data somewhere after the
launch for viewing after.<br>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed,
Jul 16, 2014 at 8:51 AM, Joshua
Pritt <span dir="ltr"><<a href="mailto:ramgarden@gmail.com" target="_blank">ramgarden@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">It would be
neat to overlay some data on
each photo like GPS coords,
altitude, temperature, air
pressure, CO2, speed, and
time from launch (T+).</div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
On Wed, Jul 16, 2014
at 8:38 AM, Ethan Chew
<span dir="ltr"><<a href="mailto:spacefelix@gmail.com" target="_blank">spacefelix@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Just suggested to
Masten that they
add a
picture/video
camera (of the
size and quality
level of the one
in your cell
phone) to the
sensor suite. ;)</p>
<div>
<div>
<div class="gmail_quote">On
Jul 16, 2014
5:08 AM,
"Satyam Nayak"
<<a href="mailto:nayaksatyam@gmail.com" target="_blank">nayaksatyam@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I
was thinking
of doing
something
similar to
HSIS where we
put a camera
on auto
trigger and
took a bunch
of pictures of
the flight.</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On
Wed, Jul 16,
2014 at 6:40
AM, WebDawg <span dir="ltr"><<a href="mailto:webdawg@gmail.com" target="_blank">webdawg@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Anyone
plan to put
any effort
into this?<br>
</div>
<div>
<div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On
Wed, Jul 16,
2014 at 4:37
AM, Ethan Chew
<span dir="ltr"><<a href="mailto:spacefelix@gmail.com" target="_blank">spacefelix@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">P.S.
Note on the
sensor suite;
the hardware
in the suite
will be
determined by
Masten.
However, at
this point in
time of
Project
Prometheus,
Masten is open
to input on
what sensor
hardware to
install.
Please send
sensor
hardware
suggestions
to <font style="font-family:arial,sans-serif;font-size:13px" face="arial,
sans-serif"><a href="mailto:prometheus@masten.aero" target="_blank">prometheus@masten.aero</a>.</font></div>
<div class="gmail_extra">
<div>
<div><br>
<br>
<div class="gmail_quote">On
Tue, Jul 15,
2014 at 6:42
AM, Ethan Chew
<span dir="ltr"><<a href="mailto:spacefelix@gmail.com" target="_blank">spacefelix@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Hello!</p>
<div>
<p>On Jul 15,
2014 6:34 AM,
"Jeff Cotten"
<<a href="mailto:omegix@gmail.com" target="_blank">omegix@gmail.com</a>>
wrote:<br>
><br>
><br>
> Hey
Ethan, will
the raspberry
pi be
connected to
the internet
during the
test?</p>
</div>
<p>Sorry, no.
To avoid
interfering
with Xombie's
control
system, the
crew has told
me no
transmitters
are allowed.</p>
<div>
<p>><br>
> If I
wrote a piece
of code that
logged into
#makerslocal
and reported
back the
altitude,
would it it be
able to reach
the freenode
server?</p>
</div>
<p>You'd need
to make an
isolated
flight data
recorder. Due
to the
restriction on
transmitters,
you can only
download your
data off a
shore
connection
when the
vehicle is
back on the
ground.</p>
<span><font color="#888888">
<p> -
Ethan</p>
</font></span>
<div>
<div>
<p>><br>
><br>
> On Tue,
Jul 15, 2014
at 12:08 AM,
Ethan Chew
<<a href="mailto:spacefelix@gmail.com" target="_blank">spacefelix@gmail.com</a>>
wrote:<br>
>><br>
>>
Hello,<br>
>><br>
>>
Take note, it
is my current
understanding
that
educational
institutions
get to fly for
free.<br>
>><br>
>>
From Masten
Space Systems
in Mojave, CA
(<a href="http://masten.aero/" target="_blank">http://masten.aero/</a>), an
opportunity to
fly code on a
vertical
takeoff and
landing rocket
(such as
Xombie: <a href="http://youtu.be/A5b9LnzjGgU" target="_blank">http://youtu.be/A5b9LnzjGgU</a>)
on Project
Prometheus:<br>
>> <br>
>> <a href="http://masten.aero/2014/05/project-prometheus/" target="_blank">http://masten.aero/2014/05/project-prometheus/</a><br>
>><br>
>>
In summary;
there is a
Raspberry Pi
on board that
is connected
to a sensor
suite. Send
Masten some
code you want
to run during
a flight that
processes
inputs from
the sensors
during the
flight. The
project is for
the rapid,
streamlined
development of
tools relating
to; visual
navigation,
landing
detection,
mass
estimation
and position/attitude
estimation.
You can reach
them at <a href="mailto:prometheus@masten.aero" target="_blank">prometheus@masten.aero</a> with
input and
questions
about the
program. <br>
>><br>
>>
Quote:<br>
>><br>
>>>>
the Masten
Team has also
been thinking
about ways we
could engage
the broader
community and
increase
accessibility
to our VTVL
vehicles. One
of the largest
barriers to
entry for any
technology
developer
seeking to
conduct
aerospace
flight testing
is access to a
vehicle.
Limited access
to an
integrated
GPS/IMU
navigation
system,
flight-rated
computing
platforms, and
sensors
present
additional
challenges to
innovators. In
the spirit of
broadening
access to
aerospace
resources, we
have had a
project
cooking in the
background
called
Prometheus.<br>
>>>><br>
>>>><br>
>>>>
Project
Prometheus is
a Masten
program
designed to
foster the
development of
flight-test
ready
technologies
by innovators
in academic
and research
settings. By
implementing a
standardized
interface
between Masten
vehicles and
experimental
software and
hardware
tools,
Prometheus
will provide a
streamlined,
efficient path
for technology
maturation
throughout the
course of tool
conception,
development
and flight
test. Access
to uniform,
flight-tested
hardware and
software
development
framework for
innovators
will
ultimately
reduce
integration,
development
and other
flight test
costs.<br>
>><br>
>><br>
>><br>
>>
-
Ethan/spacefelix<br>
>><br>
>>
_______________________________________________<br>
>>
General
mailing list<br>
>> <a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
>> <a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
><br>
><br>
><br>
>
_______________________________________________<br>
> General
mailing list<br>
> <a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
> <a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</p>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
</div>
</div>
<div>-- <br>
<div dir="ltr">
<p>
V/r Ethan</p>
<p>Working
E-mail: <a href="mailto:spacefelix@gmail.com" style="color:rgb(17,85,204)" target="_blank">spacefelix@gmail.com</a><br>
Business
E-mail: <a href="mailto:shinen.chew@gmail.com" style="color:rgb(17,85,204)" target="_blank">shinen.chew@gmail.com</a><br>
LinkedIn: <a href="http://www.linkedin.com/in/ethanchew" style="color:rgb(17,85,204)" target="_blank">www.linkedin.com/in/ethanchew</a><br>
US Cell: <a value="+12177222103" style="color:rgb(17,85,204)">+12177222103</a><br>
Skype:
flyingfelix2</p>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General
mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General
mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
General
mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">
<p>
V/r Ethan</p>
<p>Working E-mail: <a href="mailto:spacefelix@gmail.com" style="color:rgb(17,85,204)" target="_blank">spacefelix@gmail.com</a><br>
Business E-mail: <a href="mailto:shinen.chew@gmail.com" style="color:rgb(17,85,204)" target="_blank">shinen.chew@gmail.com</a><br>
LinkedIn: <a href="http://www.linkedin.com/in/ethanchew" style="color:rgb(17,85,204)" target="_blank">www.linkedin.com/in/ethanchew</a><br>
US Cell: <a value="+12177222103" style="color:rgb(17,85,204)">+12177222103</a><br>
Skype: flyingfelix2</p>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
General mailing list
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org" target="_blank">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
General mailing list<br>
<a href="mailto:General@lists.makerslocal.org">General@lists.makerslocal.org</a><br>
<a href="http://lists.makerslocal.org/mailman/listinfo/general" target="_blank">http://lists.makerslocal.org/mailman/listinfo/general</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><p>
V/r Ethan</p><p>Working E-mail: <a href="mailto:spacefelix@gmail.com" style="color:rgb(17,85,204)" target="_blank">spacefelix@gmail.com</a><br>Business E-mail: <a href="mailto:shinen.chew@gmail.com" style="color:rgb(17,85,204)" target="_blank">shinen.chew@gmail.com</a><br>
LinkedIn: <a href="http://www.linkedin.com/in/ethanchew" style="color:rgb(17,85,204)" target="_blank">www.linkedin.com/in/ethanchew</a><br>US Cell: <a value="+12177222103" style="color:rgb(17,85,204)">+12177222103</a><br>
Skype: flyingfelix2</p></div>
</div>