<node id="585837">
  <nid>585837</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1484149060</created>
  <changed>1484149060</changed>
  <title><![CDATA[PhD Proposal by Peter Zane Schulte]]></title>
  <body><![CDATA[<div>
<p><strong>Ph.D. Dissertation Proposal</strong></p>

<p>by</p>

<p>Peter Zane Schulte</p>

<p>Advisor: Dr. David Spencer</p>

<p>&nbsp;</p>

<p><strong>A State Machine architecture </strong></p>

<p><strong>for aerospace vehicle fault protection</strong></p>

<p>&nbsp;</p>

<p>12:30 PM, Monday, January 30, 2017</p>

<p><em>Montgomery Knight Building</em></p>

<p><em>Room 317</em></p>

<p><strong>ABSTRACT:</strong></p>

<p>Because of their complexity and the unforgiving environment in which they operate, aerospace vehicles are vulnerable to mission-critical failures. In order to prevent these failures, aerospace vehicles often employ Fault Detection, Isolation, and Recovery (FDIR) systems to detect, identify the source of, and recover from faults. Typically, aerospace systems use a rule-based paradigm for FDIR where telemetry values are monitored against specific logical statements such as static upper and lower limits. The model-based paradigm allows more complex decision logic to be used for FDIR. State machines are a particular tool for model-based FDIR that have been explored by industry but not yet widely adopted. This study develops a generic and modular state machine FDIR architecture that is portable to flight software. The study will focus on FDIR for the Guidance, Navigation, &amp; Control subsystem, but it will be presented in a manner that is applicable to all vehicle subsystems. This architecture applies to a wide variety of missions and vehicles and contains components that can be rearranged, added, or removed easily. The architecture is developed in a way that is straightforward to export to flight software via autocoding. Two specific case studies are employed to demonstrate the architecture. The first is a terrestrial application of unmanned aerial vehicles for 3D scanning and mapping, which is validated through flight testing. The second is a space-based application of automated close approach and capture for a Mars sample return mission, which is validated through processor-in-the-loop testing with flight-like avionics components.</p>
</div>

<p>&nbsp;</p>

<div>
<p>Committee Members:</p>
</div>

<p>&nbsp;</p>

<p>Dr. E. Glenn Lightsey</p>

<p>Aerospace Engineering</p>

<p><em>Georgia Institute of Technology</em></p>

<p>&nbsp;</p>

<p>Dr. Mark Costello</p>

<p>Aerospace Engineering</p>

<p><em>Georgia Institute of Technology</em></p>

<p>&nbsp;</p>

<p>Dr. Neil Smith</p>

<p>Visual Computing Center</p>

<p><em>King Abdullah University of Science and Technology</em></p>

<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p>Mr. Paul Rosendall</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[A STATE MACHINE ARCHITECTURE FOR AEROSPACE VEHICLE FAULT PROTECTION]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2017-01-30T12:30:00-05:00]]></value>
      <value2><![CDATA[2017-01-30T14:30:00-05:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>102851</tid>
        <value><![CDATA[Phd proposal]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
