Mars Lander Simulation

DeVry UniversityCIS 470 Team AOctober 22, 2016Prof. Scott Howell

Arron ThorntonLouis Sanders

Michael WeaverNicholi Gray

Team A Members

•Project Overview•Requirements •Design •Construction •Test Results •Problems and Lessons Learned

•Application Demonstration

Agenda

Project Description• The Mars Lander application is real-world software that simulates the descent

and landing of a Mars Lander vehicle.

• The Lander is equipped with on-board sensors, a trajectory database, and logging database to store and access data needed to perform the descent. The goal is to be able to land with a 95% success rate.

• The GCS system obtains all sensor data and uses that data in order to calculate which engines should fire and for how long in order to correct attitude, or adjust landing velocity.

• In each of the 5 phases of decent, the GCS module will be able to differentiate between landing velocity change based on the use of the parachute, or the engine controls. Attitude is maintained through use of the engine controls as well.

• Users with administrator authority will be able to enter a beginning set of sensor readings to track a new trajectory.

• Each action taken by the GCS module will be written to the real-time display to allow the user to track the status of the lander during the landing process.

System Requirements

• Windows 7 or higher

• .NET framework 4.5.1

• MySQL

Software required to install and run the simulation software.

Simulator Requirements• Provide guidance and engine control of the lander vehicle during its terminal phase of descent onto the

planet's surface.

• Communicate sensory information, to an orbiting platform, about the vehicle and its descent.

• Reach a landing simulation success rate of at least 95%.

• Control access to software, hardware and data based on user level.

• The simulation software will provide a real-time display of lander’s status. The real-time display will track the following:

1.Temperature2.Attitude 3.Altitude4.Parachute5.Gyroscopes6.Speed/Velocity7.Acceleration/Deceleration8.Trajectory9.Current Phase10.Roll Engine Status11.Thrust Engine Status

The 5 Phases of DescentPhase 1

• The parachute is deployed.• The parachute determines the lander’s

change in velocity and attitude.• GCS begins monitoring sensor data

Phase 2• Engines ignite and begin warming up.• Parachute continues to control lander’s

descent velocity and attitude.Phase 3

• Engines reach desired temperature• Parachute is detached from lander.• GCS fires engines based on sensor

readings in order to control lander attitude and descent velocity.

Phase 4• GCS detects nominal descent velocity

and attitude• Engines are shut off.• Lander free-falls to surface

Phase 5• Lander makes contact with surface.• Success or failure based on descent

velocity at time touch down sensor activates or altitude equals 0

Access controlUser/Guest Login Administration

Login• Basic access is

granted to the user by simply choosing the ‘Guest Access’ button.

• Basic access allows user to start the simulation, observe the real-time display, or stop the simulation.

• With a proper username and password a user will be granted administrator access.

• A user can only be granted administrator access by an authorized administrator level user.

• Administrator access allows the user to create new admin users, control information stored in the simulation databases, and to change initial lander simulation trajectory settings.

Design

oSystem Hierarchy

oProgram Architecture

System Hierarchy

System Architecture

Simulator ComponentsPhysical Components

1. Computer to install and run simulation software2. Keyboard and mouse to interact with CPU3. Monitor for observation of real-time display

Virtual Components

4. Doppler Radar5. Touch-down Sensor6. Altimeter7. Temperature sensor ( 2 )8. Accelerometer - one per axis ( 3 )9. Gyroscope – one per axis ( 3 )10.Thrust Engines ( 3 )11.Roll Engines – one pair per axis ( 3 pairs )12.Parachute actuator

Component Interfaces1.Inputs:

• User login page determines if user is admin level or basic access level.• Admin level user enters all beginning trajectory information, including initial sensor

readings.• Admin level users have the ability to input data into the database• Basic access level allows user to start/stop the simulation and view the real-time display• Sensor and trajectory readings are input into the GCS module from a local database

2.Outputs:

• Local monitor used to display real-time simulation data• GCS computer writes simulation database and landing log to external database.• Report generated to show sensor readings during simulation, a record of commands

issued, and whether or not the simulation depicted a successful landing attempt.

Construction

•User ERD•Access Control

•Administrator Control•Real Time Display

•Database

User ERD

Access Control• This access control window

determines if user has basic access or admin level access.

• If user has not been given admin credentials, they should choose the ‘Guest Access’ button. This will allow them to run the simulation.

• If admin credentials have been granted, they are entered on this screen to be able to control the simulation.

Access control

Admin credentials entered incorrectly are informed that the credentials are not found.

Any attempt to login using administrator credentials will be validated. Verification results will be displayed to the user.

Authorized access as admin is confirmed if credentials are correct.

Administrator Control• In the admin account, there is

an option to add a new user to become an admin

• This is for users that will gain admin access to change settings within the simulation

• A normal User or Guest will not be able to access this window because of the access controls.

• Before adding a new user, the admin can click the ‘Load Users’ button to see who is already in the system.

• Once the new user is added the admin can save the user but clicking the ‘Save User’ button.

Administrator ControlAdmin has the options to access many different parts of the system.

The admin will be ale to set:

• Trajectory• Changed/Add Users• View Onboard Log• Platform Log • Run the Simulation• Exit to Login.

Administrator ControlIn initial Trajectory Settings, the admin is able to change around numbers before running the simulation to try and get the Mars lander to land with a 95% success rate.

Allowing the Admin to change trajectory setting will make the simulation different every time it run.

Once the button ‘UpdateData’ is clicked, the settingswill send a message to showthe update was complete.

Real Time DisplayClick Start to begin the real time simulation.

Trajectory inputs are read into the GCS.

The GCS calculates changes in lander attitude, altitude, and velocity based on sensor readings and calculations.

Using a timer, the real-time display is updated at regular intervals to show changes in landing trajectory.

Real Time DisplayThe real time display is used to show changes in the following:

System TimeAltitudeDescent VelocityTemperatureThrust Engine Throttle %GCS Status messages

Database There are 4 main parts to the database that run the software. Each database will hold a certain part of the log data.

1. User DB User Table Stores all login credentials:

2. Trajectory DB Predefined Data Table. This table holds the simulation startup parameters:

Database3. Online Log DB Actuator Table after running a simulation

Database4. Online Log DB Sensor Table after running a simulation

Test ResultsDuring testing there were some components to the coding that needed a requirement to be able to run and test.

Each team member needed to have a system matching the requirements in order to install and run the simulation. This includes MySQL for database queries.

The database is one of the largest components because all data is stored in a table and they queried to find the needed data.

Each step in the coding process was tested as it was completed. This included not only connecting to a database, but verifying that information could be read from and written to that database.

Problems and Lessons Learned• The biggest problem and lesson we learned is, the

amount of time we had along with our knowledge of what we were working on.

• We learned really fast that we didn’t know the knowledge to be able to complete this project especially with the limited amount of time.

• The problems were meeting with a group that lived in different time zones and different availabilities.

• We learned a lot about how to lead, project manage, time manage, and develop the project.

• This process has been fun but challenging and stressful at times.

ConclusionWe feel that this project was one of the most challenging options offered in this course.

We understood it would be complex, but until we started digging into the project we had no idea just how true that was.

As a team we came together, and building on each other’s strengths were able to complete a project that we were all happy with.

Thank you for the opportunity, and remember……

Team A Rocks !

Mike, Arron, Nick, and Greg