mirror of
https://gitlab.com/lander-team/site.git
synced 2025-06-15 14:46:39 +00:00
content
This commit is contained in:
parent
6b70d0ec57
commit
f8949b29a4
@ -20,7 +20,7 @@ header div img {
|
||||
margin-top: 5vh;
|
||||
}
|
||||
|
||||
@media (max-width: 992px) {
|
||||
/* @media (max-width: 992px) {
|
||||
.p-5 {
|
||||
padding: 3rem;
|
||||
padding-bottom: 1rem;
|
||||
@ -29,7 +29,7 @@ header div img {
|
||||
div.col-lg-6 {
|
||||
text-align: center;
|
||||
}
|
||||
}
|
||||
} */
|
||||
|
||||
a {
|
||||
word-break: break-all;
|
||||
|
78
index.html
78
index.html
@ -80,7 +80,7 @@
|
||||
</nav>
|
||||
<header class="text-center">
|
||||
<div class="container">
|
||||
<img src="img/logo.png" class="img-fluid" alt="LANDER Logo" />
|
||||
<img src="img/logo.png" class="img-fluid" alt="LANDER Team Logo" />
|
||||
</div>
|
||||
<a class="scroll" href="#scroll"
|
||||
><img src="img/chevrons-down.svg" style="width: 75px"
|
||||
@ -96,20 +96,21 @@
|
||||
<p>
|
||||
As interest in colonizing the Moon increases, developing a
|
||||
sustainable method of transporting equipment and resources to
|
||||
and from the lunar surface will be necessary. LANDER's
|
||||
and from the lunar surface will be necessary. LANDER’s
|
||||
approach to this problem is a system that uses one thruster
|
||||
capable of vectoring thrust to control vehicle attitude and
|
||||
perform propulsive landings with minimal fuel use. However,
|
||||
key to the design challenge is creating a suitable test
|
||||
environment for such a system that can simulate variables,
|
||||
such as lunar gravity and a lack of atmosphere. Project LANDER
|
||||
perform propulsive landings with minimal fuel use. The key to
|
||||
the design challenge is creating a suitable test environment
|
||||
for a system that can simulate variables such as lunar gravity
|
||||
and a lack of atmosphere while on Earth. Project LANDER
|
||||
endeavored to provide a potential solution by designing a
|
||||
complex simulation utilizing live data. Due to an abbreviated
|
||||
timetable and low-quality components, LANDER did not meet all
|
||||
of its requirements for the Thrust Vector Control Test and
|
||||
Operational Demonstration. However, while LANDER was a
|
||||
proof–of-concept system, the team hopes to lay the foundation
|
||||
for future development in this area.
|
||||
complex simulation utilizing live data from a
|
||||
hardware-in-the-loop system. Unfortunately, due to an
|
||||
abbreviated timetable and low-quality components, LANDER did
|
||||
not meet all its requirements for a successful Operational
|
||||
Demonstration. However, LANDER was a proof-of-concept system,
|
||||
and the team hopes to lay the foundation for future
|
||||
development in this area.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
@ -137,13 +138,13 @@
|
||||
<div>
|
||||
<h2 class="display-4">Test Stand Setup</h2>
|
||||
<p>
|
||||
The fully assembled system and the CAD of the system can be
|
||||
seen on the figure to the right. LANDER consists of 5
|
||||
subsystems, Control Software, Avionics, Control Mechanisms,
|
||||
Structure, and Test Stand. These subsysems all come together
|
||||
to produce a test stand capable of simulating a vehicle
|
||||
landing on the lunar surface. The test stand involves a
|
||||
complex hardware in the loop computer simulation running on a
|
||||
The fully assembled system and the system's CAD can be seen in
|
||||
the following figure. LANDER consists of 5 subsystems, Control
|
||||
Software, Avionics, Control Mechanisms, Structure, and Test
|
||||
Stand. These subsystems all come together to produce a test
|
||||
stand capable of simulating a vehicle landing on the lunar
|
||||
surface. The test stand involves a complex
|
||||
hardware-in-the-loop computer simulation running on a
|
||||
microcontroller.
|
||||
</p>
|
||||
</div>
|
||||
@ -153,7 +154,7 @@
|
||||
<img
|
||||
class="img-fluid"
|
||||
src="img/assemblyCAD.png"
|
||||
alt="Picture of people gathered at an SAE International Event"
|
||||
alt="Picture of the assembled test stand vehicle next to the CAD of the vehicle."
|
||||
/>
|
||||
</div>
|
||||
</div>
|
||||
@ -175,12 +176,11 @@
|
||||
title="proportional–integral–derivative controller is a control loop mechanism for driving an error in state (vehicle deflection) to zero."
|
||||
>PID</abbr
|
||||
>
|
||||
which gives commands to the simulated vehicle; the commands
|
||||
are then translated back into hardware as TVC commands. The
|
||||
physical vehicle encompasses the avionics, TVC, and load
|
||||
cells. The physical vehicle receives commands from the
|
||||
simulated vehicle and returns, calculated thrust data back to
|
||||
the control software.
|
||||
that gives the simulated vehicle commands; the commands are
|
||||
then rendered into hardware as TVC commands. The physical
|
||||
vehicle encompasses the avionics, TVC, and load cells. The
|
||||
physical vehicle receives commands from the simulated vehicle
|
||||
and returns calculated thrust data to the control software.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
@ -189,7 +189,7 @@
|
||||
<img
|
||||
class="img-fluid"
|
||||
src="img/conops.png"
|
||||
alt="Picture of people gathered at an SAE International Event"
|
||||
alt="Concept of Operations for the LANDER software and hardware control loop."
|
||||
/>
|
||||
</div>
|
||||
</div>
|
||||
@ -205,18 +205,21 @@
|
||||
<h2 class="display-4">Operational Demonstration Results</h2>
|
||||
<p>
|
||||
The experimental thrust curve shows that the four load cells
|
||||
managed to match the thrust curve for the
|
||||
matched the thrust curve for the
|
||||
<a href="https://www.thrustcurve.org/motors/Estes/F15/"
|
||||
>Estes F15</a
|
||||
>
|
||||
within 6.2 Newton Seconds or 13.2% of expected. Due to
|
||||
multiple changes in project and scope LANDER initially chose
|
||||
very cheap load cells since the test stand demonstration was
|
||||
originally mean't to be a verification for much larger goals.
|
||||
Acquiring usable data from the load cells ended up taking much
|
||||
more time and resources than the team initially expected, but
|
||||
thanks to proper risk mitigation the team was able to overcome
|
||||
the challenge and find a real solution.
|
||||
within 6.2 Newton Seconds or 13.2% of expected. Unfortunately,
|
||||
due to multiple changes in project and scope, LANDER initially
|
||||
chose very cheap load cells since the test stand demonstration
|
||||
originally only served as verification for much more extensive
|
||||
goals, such as an actual propulsive landing. Therefore,
|
||||
acquiring usable data from the load cells took much more time
|
||||
and resources than the team initially expected. This time sink
|
||||
could have easily been mitigated if the team had spent more
|
||||
money on load cells to handle the new mission profile.
|
||||
However, the team overcame the challenge thanks to proper risk
|
||||
mitigation.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
@ -291,9 +294,10 @@
|
||||
<h1 class="display-4">Final Report</h1>
|
||||
<p class="lead">
|
||||
At the conclusion and verification of the Operational
|
||||
Demonstration LANDER has compiled a Final Report for the project.
|
||||
Demonstration, LANDER has compiled a Final Report for the project.
|
||||
The Final Report compiles two semesters of work into one succinct
|
||||
document that highlights all of the findings from the project.
|
||||
Open FinalReport.pdf
|
||||
</p>
|
||||
|
||||
<!-- Button trigger modal -->
|
||||
|
Loading…
x
Reference in New Issue
Block a user