<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-19T08:52:00Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/67186" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/67186</identifier><datestamp>2022-01-13T07:54:11Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">David W. Miller and Michael C. Johnson.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Han, Christopher J. (Christopher Jinhyun)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Dept. of Aeronautics and Astronautics.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Aeronautics and Astronautics</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2011-11-18T20:57:44Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2011-11-18T20:57:44Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2011</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2011</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/67186</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">758505113</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Aeronautics and Astronautics, 2011.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 117-120).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Hoppers have recently emerged as a viable means for planetary exploration, and as with any new vehicle, significant testing is required to validate guidance, navigation, and control (GNC) algorithms. Furthermore, the structure, organization, and timing of the real-time software must be planned before software development begins in order to design an architecture which can match the needs and requirements of the vehicle as they evolve throughout its lifecycle. These issues are compounded in an academic environment, where software knowledge is not necessarily present and must be obtained and practiced before it can be applied. In addition, high student turnover rates can result in difficulty retaining institutional knowledge of the working software and causes further development delays while new students are trained. These problems were addressed by the TALARIS software team by implementing a flexible, modular software solution in LabVIEW on the National Instruments Real-Time Input/Output (RIO) board. After a brief introduction to the TALARIS testbed, the theory of flexibility and modularity is described as applied to the TALARIS software. In particular, the unique FPGA + PowerPC architecture and its importance to precise, real-time GNC execution are explored. Various software modules are isolated and analyzed, and several test cases are presented to illustrate the benefits of modular software with regard to development time, testing procedure, and debugging. Examples from software development, actuator characterization, and test campaigns illustrate the gradual evolution of the prototype software. Finally, a discussion of the conclusions from the work and future work is presented.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Christopher J. Han.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">137 p.</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by 
copyright. They may be viewed from this source for any purpose, but 
reproduction or distribution in any format is prohibited without written 
permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Aeronautics and Astronautics.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Development of modular real-time software for the TALARIS lunar hopper testbed</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="1807d562-1a93-475f-9426-c1fc7873374d">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>Development of modular real-time software for the TALARIS lunar hopper testbed&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2011&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author&gt;
        	&lt;DisplayName>Han, Christopher J. (Christopher Jinhyun)&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>Aeronautics and Astronautics.&lt;/Keyword>
   	&lt;Abstract>Hoppers have recently emerged as a viable means for planetary exploration, and as with any new vehicle, significant testing is required to validate guidance, navigation, and control (GNC) algorithms. Furthermore, the structure, organization, and timing of the real-time software must be planned before software development begins in order to design an architecture which can match the needs and requirements of the vehicle as they evolve throughout its lifecycle. These issues are compounded in an academic environment, where software knowledge is not necessarily present and must be obtained and practiced before it can be applied. In addition, high student turnover rates can result in difficulty retaining institutional knowledge of the working software and causes further development delays while new students are trained. These problems were addressed by the TALARIS software team by implementing a flexible, modular software solution in LabVIEW on the National Instruments Real-Time Input/Output (RIO) board. After a brief introduction to the TALARIS testbed, the theory of flexibility and modularity is described as applied to the TALARIS software. In particular, the unique FPGA + PowerPC architecture and its importance to precise, real-time GNC execution are explored. Various software modules are isolated and analyzed, and several test cases are presented to illustrate the benefits of modular software with regard to development time, testing procedure, and debugging. Examples from software development, actuator characterization, and test campaigns illustrate the gradual evolution of the prototype software. Finally, a discussion of the conclusions from the work and future work is presented.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>