Difference between revisions of "Hackers in space"

From Baltimore Node Wiki
Jump to navigationJump to search
(Created page with 'Place your notes on the hackerspace in space project here:')
 
 
(19 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
Place your notes on the hackerspace in space project here:
 
Place your notes on the hackerspace in space project here:
 +
 +
Here is some preliminary resources suggested by Scott Foerster:
 +
 +
===Others attempting the project===
 +
* [http://www.wired.com/gadgetlab/2009/09/the-150-space-camera-mit-students-beat-nasa-on-beer-money-budget/ Wired article on MIT balloon project]
 +
* [http://www.telegraph.co.uk/news/newstopics/howaboutthat/5005022/Teens-capture-images-of-space-with-56-camera-and-balloon.html Teens in Spain attempting the project]
 +
* [http://bear.sbszoo.com/bear3-4/bear4.htm Canadians in space]
 +
* [http://www.srcf.ucam.org/~cuspaceflight/media.php Cambridge University team]
 +
* [https://www.noisebridge.net/wiki/Spacebridge Noise Bridge Hacker Space]
 +
===Useful links===
 +
* [http://www.eoss.org/pubs/far_annotated.htm FAA regulations regarding weather balloons]
 +
 +
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=ea968eea871ed9ab2380f6d979eaa7a6&rgn=div5&view=text&node=14:2.0.1.3.15&idno=14 Interpretations of FAA regulations]
 +
 +
http://weather.uwyo.edu/polar/balloon_traj.html
 +
http://www.srcf.ucam.org/~cuspaceflight/wiki/doku.php#welcome_to_the_cu_spaceflight_wiki
 +
http://www.srcf.ucam.org/~cuspaceflight/predict/
 +
 +
http://pypi.python.org/pypi/pygrib/1.0
 +
http://showcase.netins.net/web/wallio/GPSrcvrsvs60kft.htm
 +
===Questions for Workshop88 competition===
 +
 +
'''Does the cost refer just to the payload or payload + balloon and recovery equipment?'''
 +
 +
'''When does the 45 minute clock start?'''
 +
 +
==== From the FAQ: ====
 +
 +
'''Can I used donated items to offset the cost of my balloon?'''
 +
*No, even if an item is donated you need to assign a universally accepted value to it.  IE: MSRP, average eBay price, etc...
 +
 +
'''Why do I have to count the value of donated item'''
 +
*A meaningful price cap levels the playing field for all groups and pushes them to innovate.
 +
 +
'''Is there a prize? Can we make a donation of an item or cash as part of the pot? What do we get if we win?'''
 +
*Bragging rights, a cool trophy made by the members of Workshop 88, and the honor of building next year's trophy.
 +
 +
===Goals of Node Space Shot===
 +
 +
Why we should go to near space:
 +
 +
It's a spectacular and achievable goal with lots of design challenges requiring robust methods and coordinated work.
 +
 +
The challenges include extreme cold, condensation, extreme force, unreliable data and luck.
 +
 +
With other hacker spaces working on the Workshop88 competition and general interest this is an opportunity to both collaborate with other hacker spaces and to establish Node's own style. Opportunities exist for developing methods for payload data recording, tracking and recovery methods.
 +
 +
Near space cooled shot of vodka.
 +
 +
Objective:
 +
Send stuff to near space by baloon, recover stuff relatively intact. Use easily available materials when possible. Create software and methods easily available for other groups to repeat.
 +
 +
Launch:
 +
We need to learn the methods for inflating and handling the baloon to allow for optimal and controlled release.
 +
 +
Location location location. Brief experimentation with ucam.org's tools shows a launch in Baltimore County will land 100 miles in to the ocean parallel to NJ. A launch in Pittsburgh would land in Philly or DC depending on latitude. MD and the east coast in general is lousy for a launch effort because of the jet stream and not so great for recovery because the terrain is primarily wooded/urban.
 +
 +
Launch Proposal: using google maps and google charts, python, GRIB data, google apps/amazon develop applications for landing predictions and embedded unix based flight control software.
 +
 +
We should prepare to use a launch and recovery site not in state. This is kind of a bummer because space is just above us, but also a boon because A) collaboration with other hacker spaces for using members and resources. B) ROAD TRIP!
 +
 +
Payload:
 +
The goals of the payloads goals are to gather information and return them safely through low temperatures, moisture and recoverable from  falling to earth.
 +
 +
There is a richness of materials to work with available in consumer items for this requirement. Data must be stored in a way that will be recoverable after power interruptions and extreme physical duress.
 +
 +
Payload proposal:
 +
Using ziplock bags, styrofoam, thermal blankets and a spraying of electronics with non conductive oils, use arduino with SD card to record data.
 +
 +
Telematics (Telemetry):
 +
XYZ
 +
 +
Accurate measurements and reporting of position and height through out flight. Consumer electronics are easily available but limited in scope. GPS position and altitude are measurable by a variety of methods.
 +
 +
Avionics:
 +
Get up and then get down!
 +
 +
Getting up is relatively straight forward, but leaves a lot to experimentation. Balloons need to be properly inflated not to swell too much and pop at altitude. Proper handling of the balloon is essential to optimal performance.
 +
 +
Getting down will happen, the key is to choosing how predictably and violently the trip down goes.
 +
 +
Recovery:
 +
Let's try and not drop a payload from near space at terminal velocity on someone's head.  Oh, and littering is bad mkay?
 +
 +
Deploying a chute too early will cause the craft to drift with the wind recovery area can be reported by gps enabled cellphone and refined by RF beacon signal and audible beacon.
 +
 +
Idea: lifting body and active avionics can guide the payload back to a easier to identify area.
 +
 +
Phase I
 +
construct avionics and telemetry systems.
 +
 +
Phase II
 +
drop stuff off building, stick in freezer.
 +
 +
Phase III
 +
drop stuff off of lower altitude balloon.
 +
 +
Phase IIII
 +
test flight to test and calibrate systems.
 +
 +
Phase IV
 +
Flights for extreme capacities for contest and other goals.

Latest revision as of 00:57, 28 February 2010

Place your notes on the hackerspace in space project here:

Here is some preliminary resources suggested by Scott Foerster:

Others attempting the project[edit | edit source]

Useful links[edit | edit source]

http://weather.uwyo.edu/polar/balloon_traj.html http://www.srcf.ucam.org/~cuspaceflight/wiki/doku.php#welcome_to_the_cu_spaceflight_wiki http://www.srcf.ucam.org/~cuspaceflight/predict/

http://pypi.python.org/pypi/pygrib/1.0 http://showcase.netins.net/web/wallio/GPSrcvrsvs60kft.htm

Questions for Workshop88 competition[edit | edit source]

Does the cost refer just to the payload or payload + balloon and recovery equipment?

When does the 45 minute clock start?

From the FAQ:[edit | edit source]

Can I used donated items to offset the cost of my balloon?

  • No, even if an item is donated you need to assign a universally accepted value to it. IE: MSRP, average eBay price, etc...

Why do I have to count the value of donated item

  • A meaningful price cap levels the playing field for all groups and pushes them to innovate.

Is there a prize? Can we make a donation of an item or cash as part of the pot? What do we get if we win?

  • Bragging rights, a cool trophy made by the members of Workshop 88, and the honor of building next year's trophy.

Goals of Node Space Shot[edit | edit source]

Why we should go to near space:

It's a spectacular and achievable goal with lots of design challenges requiring robust methods and coordinated work.

The challenges include extreme cold, condensation, extreme force, unreliable data and luck.

With other hacker spaces working on the Workshop88 competition and general interest this is an opportunity to both collaborate with other hacker spaces and to establish Node's own style. Opportunities exist for developing methods for payload data recording, tracking and recovery methods.

Near space cooled shot of vodka.

Objective: Send stuff to near space by baloon, recover stuff relatively intact. Use easily available materials when possible. Create software and methods easily available for other groups to repeat.

Launch: We need to learn the methods for inflating and handling the baloon to allow for optimal and controlled release.

Location location location. Brief experimentation with ucam.org's tools shows a launch in Baltimore County will land 100 miles in to the ocean parallel to NJ. A launch in Pittsburgh would land in Philly or DC depending on latitude. MD and the east coast in general is lousy for a launch effort because of the jet stream and not so great for recovery because the terrain is primarily wooded/urban.

Launch Proposal: using google maps and google charts, python, GRIB data, google apps/amazon develop applications for landing predictions and embedded unix based flight control software.

We should prepare to use a launch and recovery site not in state. This is kind of a bummer because space is just above us, but also a boon because A) collaboration with other hacker spaces for using members and resources. B) ROAD TRIP!

Payload: The goals of the payloads goals are to gather information and return them safely through low temperatures, moisture and recoverable from falling to earth.

There is a richness of materials to work with available in consumer items for this requirement. Data must be stored in a way that will be recoverable after power interruptions and extreme physical duress.

Payload proposal: Using ziplock bags, styrofoam, thermal blankets and a spraying of electronics with non conductive oils, use arduino with SD card to record data.

Telematics (Telemetry): XYZ

Accurate measurements and reporting of position and height through out flight. Consumer electronics are easily available but limited in scope. GPS position and altitude are measurable by a variety of methods.

Avionics: Get up and then get down!

Getting up is relatively straight forward, but leaves a lot to experimentation. Balloons need to be properly inflated not to swell too much and pop at altitude. Proper handling of the balloon is essential to optimal performance.

Getting down will happen, the key is to choosing how predictably and violently the trip down goes.

Recovery: Let's try and not drop a payload from near space at terminal velocity on someone's head. Oh, and littering is bad mkay?

Deploying a chute too early will cause the craft to drift with the wind recovery area can be reported by gps enabled cellphone and refined by RF beacon signal and audible beacon.

Idea: lifting body and active avionics can guide the payload back to a easier to identify area.

Phase I construct avionics and telemetry systems.

Phase II drop stuff off building, stick in freezer.

Phase III drop stuff off of lower altitude balloon.

Phase IIII test flight to test and calibrate systems.

Phase IV Flights for extreme capacities for contest and other goals.

Retrieved from "https://wiki.baltimorenode.org/index.php?title=Hackers_in_space&oldid=1630"