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
7 Ongoing and Future Work There are three main thrusts of ongoing and future work for the TALARIS CGSE. The first is validation testing of the CGSE, which couples further hardware testing with tests of GNC algorithms. The second is more complete characterization of the existing CGSE system’s capabilities as well as the development of best practices for its operation. The third is making changes to improve the TALARIS spacecraft emulator propulsion system. This work could range in scope from relatively small changes, like swapping out parts in the CGSE, to a full redesign of the system to utilize hydrogen peroxide as a monopropellant. 7.1 Validation Testing The single-stream component tests as well as the static characterization tests of the CGSE flight system had all been performed for verification; that is, to ensure that the CGSE met the derived technical performance requirements laid out in section 3.1.4. The next step was to check that these requirements added up to a system that performed the original top-level goals for which it was designed, and the way to accomplish this was through validation testing. As the NASA Systems Engineering Handbook says, “Validation testing is conducted under realistic conditions (or simulated conditions) on any end product to determine the effectiveness and suitability of the product for use in mission operations by typical users and to evaluate the results of such tests” [60]. For the TALARIS CGSE, validation means proving that it can propel and control the vehicle through all phases of a hover hop. However, it would be a very large leap to go directly from static characterization testing to unrestrained free flight, and due to its limited budget and rigorous safety constraints, the TALARIS project cannot tolerate a crash or other destructive failure. Thus, an incremental validation testing program was developed. It was planned that in the first few tests, the hopper would have some of its degrees of freedom (DOFs) restricted so that it could only move in certain ways. Closed-loop CGSE control could progressively be applied to more and more degrees of freedom, with a greater chance of catching any major problems early in a more controlled environment, until enough confidence had been developed in both the hardware and the software to permit 6-DOF free flight hopping. The execution of this plan is in progress at the time of writing this thesis. 7.1.1 Horizontal Traverse and Roll Testing When validation testing for the TALARIS CGSE began, the EDF weight-relief propulsion system was being upgraded and was not available for flight. Thus, the first CGSE validation tests focused on the horizontal 106
traverse phase of a hop and involved only the horizontal thrusters. For the very earliest tests, the two parts of the static test stand shown in Figure 6-7 were separated from the load cell, and wheels were bolted onto the bottom of the cradle. This formed a sort of cart into which the TALARIS hopper could be locked for 1-DOF horizontal testing, as shown in Figure 7-1. Figure 7-1. CGSE 1-DOF horizontal traverse testing on wheels. By firing its horizontal thrusters, the TALARIS hopper was free to roll back and forth across the floor parallel to the hopper’s Z axis, but it could not move in any other dimensions. However, it was soon found that there was a great deal of friction in the wheels, so the cart was not providing an accurate simulation of the transit phase of a hop. To reduce friction with the floor, the wheels were replaced with an air bearing of the sort used to help move vending machines or large pieces of furniture. This improved apparatus is pictured in Figure 7-2. 107
- Page 57 and 58: that of helium (0.227 MPa = 32.9 ps
- Page 59 and 60: thruster solenoid valve, and chambe
- Page 61 and 62: where
- Page 63 and 64: discussed later in section 6.3.4, t
- Page 65 and 66: The flight profile begins with maxi
- Page 67 and 68: hop, any given valve or regulator o
- Page 69 and 70: esponse time was an important perfo
- Page 71 and 72: directly opens and closes the main
- Page 73 and 74: If 1D isentropic flow is assumed, t
- Page 75 and 76: 5 Single-Stream Component Testing A
- Page 77 and 78: the solenoid valve, and a pressure
- Page 79 and 80: As indicated in Figure 5-3, initial
- Page 81 and 82: Figure 5-5. CGSE high side as const
- Page 83 and 84: Figure 5-7 illustrates several aspe
- Page 85 and 86: 6 Full Eight-Thruster Flight System
- Page 87 and 88: Figure 6-2. TALARIS CGSE assembled
- Page 89 and 90: stream tests revealed that changes
- Page 91 and 92: Figure 6-5. Original CGSE control c
- Page 93 and 94: other constraints. This was difficu
- Page 95 and 96: variables (such as number of thrust
- Page 97 and 98: One solution to this problem would
- Page 99 and 100: One of the characterization tests w
- Page 101 and 102: or more thrusters were firing toget
- Page 103 and 104: Table 6-3. Valve timing metrics dur
- Page 105 and 106: Figure 6-11. Redesigned CGSE contro
- Page 107: The imaginary simplified thruster c
- Page 111 and 112: Figure 7-3. GNC data from 3-DOF tes
- Page 113 and 114: Tests on this vertical stand demons
- Page 115 and 116: control the belay line can be put u
- Page 117 and 118: accounting for changes in thrust le
- Page 119 and 120: development under the supervision o
- Page 121 and 122: documenting progress takes time whi
- Page 123 and 124: were encountered, it was harder to
- Page 125 and 126: [10] Bryant, K. M., Knight, C. J.,
- Page 127 and 128: [31] Canadian Centre for Occupation
7 Ongoing and Future Work<br />
There are three main thrusts <strong>of</strong> ongoing and future work <strong>for</strong> <strong>the</strong> TALARIS CGSE. The first is validation<br />
testing <strong>of</strong> <strong>the</strong> CGSE, which couples fur<strong>the</strong>r hardware testing with tests <strong>of</strong> GNC algorithms. The second is<br />
more complete characterization <strong>of</strong> <strong>the</strong> existing CGSE system’s capabilities as well as <strong>the</strong> development <strong>of</strong><br />
best practices <strong>for</strong> its operation. The third is making changes to improve <strong>the</strong> TALARIS spacecraft emulator<br />
propulsion system. This work could range in scope from relatively small changes, like swapping out parts<br />
in <strong>the</strong> CGSE, to a full redesign <strong>of</strong> <strong>the</strong> system to utilize hydrogen peroxide as a monopropellant.<br />
7.1 Validation Testing<br />
The single-stream component tests as well as <strong>the</strong> static characterization tests <strong>of</strong> <strong>the</strong> CGSE flight system<br />
had all been per<strong>for</strong>med <strong>for</strong> verification; that is, to ensure that <strong>the</strong> CGSE met <strong>the</strong> derived technical<br />
per<strong>for</strong>mance requirements laid out in section 3.1.4. The next step was to check that <strong>the</strong>se requirements<br />
added up to a system that per<strong>for</strong>med <strong>the</strong> original top-level goals <strong>for</strong> which it was designed, and <strong>the</strong> way<br />
to accomplish this was through validation testing. As <strong>the</strong> NASA <strong>System</strong>s Engineering Handbook says,<br />
“Validation testing is conducted under realistic conditions (or simulated conditions) on any end product<br />
to determine <strong>the</strong> effectiveness and suitability <strong>of</strong> <strong>the</strong> product <strong>for</strong> use in mission operations by typical<br />
users and to evaluate <strong>the</strong> results <strong>of</strong> such tests” [60].<br />
For <strong>the</strong> TALARIS CGSE, validation means proving that it can propel and control <strong>the</strong> vehicle through all<br />
phases <strong>of</strong> a hover hop. However, it would be a very large leap to go directly from static characterization<br />
testing to unrestrained free flight, and due to its limited budget and rigorous safety constraints, <strong>the</strong><br />
TALARIS project cannot tolerate a crash or o<strong>the</strong>r destructive failure. Thus, an incremental validation<br />
testing program was developed. It was planned that in <strong>the</strong> first few tests, <strong>the</strong> hopper would have some<br />
<strong>of</strong> its degrees <strong>of</strong> freedom (DOFs) restricted so that it could only move in certain ways. Closed-loop CGSE<br />
control could progressively be applied to more and more degrees <strong>of</strong> freedom, with a greater chance <strong>of</strong><br />
catching any major problems early in a more controlled environment, until enough confidence had been<br />
developed in both <strong>the</strong> hardware and <strong>the</strong> s<strong>of</strong>tware to permit 6-DOF free flight hopping. The execution <strong>of</strong><br />
this plan is in progress at <strong>the</strong> time <strong>of</strong> writing this <strong>the</strong>sis.<br />
7.1.1 Horizontal Traverse and Roll Testing<br />
When validation testing <strong>for</strong> <strong>the</strong> TALARIS CGSE began, <strong>the</strong> EDF weight-relief propulsion system was being<br />
upgraded and was not available <strong>for</strong> flight. Thus, <strong>the</strong> first CGSE validation tests focused on <strong>the</strong> horizontal<br />
106