26.12.2012 Views

Development of a Cold Gas Propulsion System for the ... - SSL - MIT

Development of a Cold Gas Propulsion System for the ... - SSL - MIT

Development of a Cold Gas Propulsion System for the ... - SSL - MIT

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

8 Conclusion<br />

The TALARIS CGSE is an application <strong>of</strong> mature technology to a very specific purpose. While cold gas<br />

propulsion has been used <strong>for</strong> decades, and several small robotic lunar lander testbeds have recently<br />

been designed and flown with cold gas propulsion systems, <strong>the</strong> requirements and constraints <strong>of</strong> <strong>the</strong><br />

TALARIS program made <strong>the</strong> CGSE unique. Hopping as a mode <strong>of</strong> transportation <strong>for</strong> lunar or planetary<br />

surface exploration is a relatively new and untried idea, and <strong>the</strong> hover hop in particular is a maneuver<br />

which few if any space exploration vehicles have been purposely designed and built to per<strong>for</strong>m. In<br />

addition, <strong>the</strong> dual role <strong>of</strong> TALARIS as testbed and demonstrator drove a unique design philosophy <strong>for</strong><br />

<strong>the</strong> CGSE. Finally, <strong>the</strong> limited budget, aggressive schedule, core <strong>of</strong> student participation, and exceptional<br />

focus on safety all contributed to setting TALARIS and <strong>the</strong> CGSE apart from similar projects.<br />

<strong>Development</strong> <strong>of</strong> <strong>the</strong> CGSE to fit <strong>the</strong> unique conditions <strong>of</strong> TALARIS was a process that required <strong>the</strong><br />

application <strong>of</strong> many tools and techniques. Familiarization with existing technologies was necessary to<br />

understand <strong>the</strong> baselines from which to create a design. Modeling was an essential tool <strong>for</strong> applying<br />

science to designing <strong>the</strong> CGSE, but it was important to understand <strong>the</strong> model’s limitations and to<br />

analyze its results in <strong>the</strong> context <strong>of</strong> real-world considerations and imperfections. Testing was critical <strong>for</strong><br />

characterizing <strong>the</strong> per<strong>for</strong>mance <strong>of</strong> <strong>the</strong> CGSE but also <strong>for</strong> pointing out ways to iterate on <strong>the</strong> original<br />

design and improve <strong>the</strong> functioning <strong>of</strong> <strong>the</strong> system. And throughout <strong>the</strong> entire development process, it<br />

was necessary to keep track <strong>of</strong> requirements, to ensure not only that <strong>the</strong> CGSE could per<strong>for</strong>m to meet<br />

set standards, but also that it was able to fulfill <strong>the</strong> overarching objectives <strong>for</strong> which it was originally<br />

designed.<br />

In <strong>the</strong> process <strong>of</strong> completing <strong>the</strong> work documented in this <strong>the</strong>sis, several lessons were learned which<br />

seemed to have broader significance beyond <strong>the</strong> development <strong>of</strong> <strong>the</strong> CGSE. They are presented briefly<br />

here, in hopes <strong>of</strong> positively influencing work on o<strong>the</strong>r parts <strong>of</strong> TALARIS or perhaps any project involving<br />

<strong>the</strong> design <strong>of</strong> a subsystem to be integrated into a larger system.<br />

Documentation is important.<br />

Many parts <strong>of</strong> <strong>the</strong> process <strong>of</strong> developing <strong>the</strong> CGSE, such as selecting <strong>the</strong> basic system architecture and<br />

writing <strong>the</strong> MATLAB model to name just two, were built on work started by previous students, and it<br />

was invaluable to have a record <strong>of</strong> not only <strong>the</strong> results <strong>of</strong> <strong>the</strong>ir work but <strong>the</strong> thought processes and<br />

assumptions that went into it. Documentation can help prevent <strong>the</strong> duplication <strong>of</strong> previous ef<strong>for</strong>ts,<br />

troubleshoot problems, and suggest (even through omission) possible new directions <strong>of</strong> work. Properly<br />

118

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!