# PRE2020 4 Group5

(Difference between revisions)
 Revision as of 14:29, 13 May 2021 (view source) (→Research:)← Older edit Revision as of 15:29, 13 May 2021 (view source) (→Rocket Specifications)Newer edit → Line 285: Line 285: ==Rocket Specifications== ==Rocket Specifications== + + In order to reach Titan's orbit, a sufficiently large exit velocity is required (to escape Earth's gravitational pull). To do this, some rudimentary calculations are needed. This will broken down into several categories starting with computing the required escape velocity. After this we will determine the power output required to do so, and how much fuel this would consume. Lastly, we will select a rocket which can meet all of these conditions. Using this information, we use the payload capsule volume available to select a deliverable which suits these dimensions. + + ===Escape Velocity=== + + The escape velocity can be computed with the following equation: ==Payload Specifications== ==Payload Specifications==

# Team:

Members Student ID Faculty E-mail
Ive Harzing 1325094 AP i.harzing@student.tue.nl
Tim Kolen 1311506 AP t.kolen@student.tue.nl
Peter Duel 1236313 ME p.m.duel@student.tue.nl
Quentin Missinne 1435957 ME q.missinne@student.tue.nl
Johan van Tien 1455788 ME f.j.m.v.tien@student.tue.nl

# Topic

Image of Titan in true colour

The great unknowns of space might soon be less unknown; various government and private space exploration companies have started projects to discover Mars, the nearest planet where life might be possible. But, it might not the only one, as possible conditions for primitive life can be found on a moon of Saturn as well: Titan.

Titan features a dense atmosphere of nitrogen and methane. It is the only other spacial body to have surface liquids (beside Earth). Beneath its surface, it possibly features a layer of ice and liquid water. Although the conditions are not perfect for earth-like life, it could form the base for lifeforms of other kinds.

The goal of this project is to design a system to search for life (or traces thereof) on the surface of Titan. As Titan is far away from earth, communication is restricted; this means the system will have to independently be able to discover the unknowns of the planet. Using AI the device will have to navigate, identify points-of-interest, and hopefully discover life on Titan.

## Project Description

The conditions on Titan are harsh. [...]

Since Titans distance from earth, communication is delayed by 70 to 90 minutes.[1] This means that if the vehicle gets stuck, it will cost over an hour before that information arrives on earth, and then double it before commands to get unstuck arrives back at the device. This complicates control of the device, thus it will have to be able to navigate and discover independently, with as few human interventions as possible.

## Project Objectives

The device should be able to do the following:

• To safely arrive at Titan
• Move around on Titan without need of human intervention
• Identify (evidence of) lifeforms
• Communicate findings back to earth, possibly via a satellite or other external device

## Path planning

This paper describes GESTALT, a program used to autonomously navigate the Martian surface.

There is blind-drive, which is the simplest method to reach a goal. It speaks for itself, it is a blind drive, there is no hazard detection.

With the AutoNav, the rover detects obstacles and hazards and autonomously avoids this. The paper then goes more in-debt about AutoNav. The approach has its similarities with the Robots and AI course NetLogo assignment.

An idea for a deliverable is to try and alter/expand/improve that assignment or use it as a base to come up with a path-finding algorithm. Another idea is to chose an instrument we like, and further work on that. For example further investigate the SAM, and maybe try to improve on its size. Which now has the size of a microwave.

## USEr's

(TBD)

### USE

In space exploration, the lines between User, Society and Enterprise are often more vague than in other fields. This is because one entity can be in all three groups at once, with the main example being NASA.

NASA is a User of the satellites and spacecrafts that are in space, using them to conduct research in many different topics.

NASA is also Society, since it is a government driven and funded entity. NASA has its own administrator, but the decision making is also heavily influenced by Congress.

Lastly, NASA has a major role in Enterprise, not to make profit themselves (since they’re funded by the Government), but to fund other companies that build rockets and satellites.

So the Governmental space administrations usually fall in all three categories. Besides that, there are the companies, who usually fall in the groups User and Enterprise, and the scientists, who fall in the groups User and Society.

User:

• Space agencies
• Governmental: NASA, ESA, JAXA, Roscosmos
• Commercial:
• rockets: ULA, SpaceX, Boeing, Blue Origin
• satelites: JPL, Lockheed Martin, Orbital ATK, Universities
• astrophysicists

### Society

(To be edited) Satisfying our curiosity further our understanding of

• planetary biochemistry
• formation of planets/moons

Long term: Everyone

### Enterprise

(to be edited) Enterprise:

• Space agencies
• Governmental: NASA, ESA, JAXA, Roscosmos)
• Commercial: SpaceX, Blue Origin
• astrophysicists

# Project Plan

## Milestones

To approach the project, milestones are created in hopes of setting realistic goals which can be acheived on a weekly basis. These goals will span for the entirety of the project timeline. Note, these will change throughout the project, as the type of deliverable is still not set in concrete. Once this is decided many of the milestones can be removed or ammended. Below the milestones can be found in a chronological order. These will be used later to create a project plan which can be modified throughout the project.

Week 1

• Project Decision
• Project Plan
• Research (25 papers - 5 P.P.):
• Complete USEr research

Week 2:

• List of topics for WIKI
• RPC List
• Start looking into design solutions
• Specify Deliverable

week 3:

• Research
• Prototype/deliverable development of idea
• potential deliverable programs/software
• what would be used to create deliverable/software.
• Update project plan for prototype/deliverable

Week 4:

• Begin developping prototype
• Addapt WIKI page with new information

Week 5:

• Run primary test on prototype
• Fix any issues with prototype and further develop it

Week 6:

• Complete Prototype
• Test Prototype deliverable

Week 7:

• Final testing of deliverable
• Fill in missing information from WIKI

Week 8:

• Presentation
• Finalize WIKI

## RPC List

Requirements

• Get to Titan, the device must be able to reach Titan.
• Durability, the materials the device is made of must be able to sustain the environment, meaning it should not erode quickly or react chemically with Titan's atmosphere or surface.
• Survivable, the device should be able to handle temperatures as low as 90K, and be able to deal with winds of up to 34m/s (122km/h)
• Longevity, there must be an energy source on the device that enables the device to collect sufficient data.
• Autonomy, with light having to travel 60 to 90 minutes from Earth to Titan the device must be able to operate (partly) autonomously since it cannot be directly controlled from earth due to the massive 'input lag' caused by the distance between Earth and Titan.
• Consistent communication, the device should be able to communicate in a consistent format with Earth.
• Navigation, the device should be able to navigate Titan without getting itself stuck.
• Ethical treatment, when life is encountered the device should be able to recognize this and act accordingly.

Preferences

• Flexible ways of travel, the device should be able to travel across both land and lakes/rivers and should be able to traverse canyons as well.
• Redundancy, when vital components stop working, it should have redundant backup parts such that it is able to function again afterwards.
• Simulation, the device should have a proper model to simulate the device's behavior on Earth for verification.
• Obtaining data, the device should be able to obtain data via camera, infrared, and XXX(?).
• In case of rover: Geo-locate, the device should be able to identify its location on the surface.
• In case of Satellite: Orbital-location, the device should be able to identify its current position with reference to its orbit.
• Use ready data: data obtained from the device should be formatted in a way that it is ready for use. E.g. maps should be directly renderable in GIS.
• Constant data flow, such that information passes to and from the device continuously.
• sustainability, the material used should have the potential of being recovered, and if not, should be safe to leave on titan without causing damage to the enviroment, or when in orbit would not create space debris.
• Universal Program, the code written for the operation of the device (in all cases) should not restrict the availability of potential imput from other software, and should allow a large range of possible contribution.

Constraints

• Maximum size, the device must fit into the rocket so it can be transported.
• Maximum weight, the device cannot weigh more than (to be determined) in order for the rocket to launch properly.
• Cost/Realizability, the device/mission has to be approved by a governmental Space Agency (probably NASA), to get funding.

## Logbook and Structure:

For a thoroughly catalogued timetable of the work contributed by team members, the Logbook Group 5 is used.

The hours mentioned within this logbook correspond to the Project Plan Adaptable Structure, where-in a continuously modified to-do list is given, as well as the priority of each task, and how far developped these tasks are.

# Research:

## Conditions of Life

To be able to 'find life', the priliminary problem is determining how this can be done. Therefore, before describing how we can find life on Titan, an investigation into what signs of life are has to be made. The following subsection is dedicated to this, as well as elaborating on the different forms of life. Once this has been thoroughly covered, the instruments used to do this can be further explained.

## Instruments

NASA’s curiosity rover is equipped with several cameras and sensors. Generally speaking they consist of the following:

• Cameras
• Spectrometers
• Environmental sensors
• Atmospheric sensors

The cameras are used for visualization and orientation during descent and exploration.

• Mahli – microscopic imaging – Identify minerals in a rock or debris->Indication of life
• Mardi - provides view during descent for better exploration path planning – For NASA data is send back to earth after landing so the so-called Earthbound planners can plan the route for the rover. This could be an interesting part to further look into as this could possibly be extended with some AI-features. Like recognizing patterns and planning the route itself.

Spectrometers are commonly used in chemical analysis. These devices can separate matter by their mass for example.

• APXS – radiation detection for types of elements
• ChemCam – uses laser and spectrometer to vaporize and analyze the chemicals
• CheMin – spectrometer

SAM (sample analysis)

• Gas chromatograph
• Mass spectrometer
• Tunable Laser Spectrometer

• DAN – detection subsurface water

Environmental sensor

• REMS – weather station

Atmospheric sensor

• MEDLI – collect engineering data during descent into atmosphere – material study

Conclusions that can be drawn from this, is that there are different sensors for different end-goals. Observation, navigation, material study via various ways(taking samples or collecting data on radiation), a weather station and collecting data entering the atmosphere. Keep in mind this is only from NASA’s Curiosity rover. NASA’s perseverance rover is an upgraded version with solar-powered drone, which I have not looked into much deeper.

From what we have discussed so far, it is best to focus our interest in the material study and navigation.

### Further investigation into Ingenuity (the mars helicopter)

Because Ingenuity is only built to test if a 'drone' of sorts can fly on Mars, it does not have the same collection of sensors and cameras as the curiosity rover or preservance. That being said, there is an extremely high level of engineering dedicated to the flight of Ingenuity, which could be taken into account when considering our own hardware end product. Whilst Ingenuity is the pinacle of technological advancements (considering it is the first UAV to fly on Mars), it is still quite rudementary with the following Hardware:

• Dimensions:
• Body: 0.136 m x 0.195m x 0.163m (cubic shape)
• Landing 'legs' 0.384 m (length)
• Rotor Diameter: 1.2m
• Height: 0.49 m
• Landing mass: 1.8 kg with 273 g tatal mass of batteries
• Power output: 350 W

Further investigation into Ingenuity Gives the following flight characteristics:

• Rotor speed: 2400 rpm
• Blade tip speed: <0.7 mach
• Operation time: 1-5 flights within 30 sols
• Flight time: Max. 120 seconds per flight.
• Maximum flight range: 600 m
• Maximum radio range: 1000 m
• Maximum planned attitude: 10 m
• Maximum speed:
• Horizontal: 10 m/s
• Vertical: 3 m/s
• Battery capacity: 35-40 Wh

From these fundemental statistics of the Ingenuity copter, we can conclude the following. Whilst this is an impressive feat to achieve (flight on Mars of a UAV), it is not nearly sufficient for what we would be planning and therefore several adaptations would need to be made. Most notably, as greater flight times would be expected (with greater max. alttitude & range), a greater radio communication range would be required. For any of this to be implemented, greater dimensions would be required. This also means that greater batteries would be needed, and much larger rotor speeds would be almost manditory. Therefore, further investigation into how this can be done needs to be made.

## Approach

In hopes of satisfying the USEr, we want to focus on key aspects of the project, most notably the deliverable. This can be done by taking several assumptions, most notably the spacecraft used, the size of the payload, the weight of the payload and any other details which would prove relvant to the problem, but irrelevant to the final deliverable. In hopes of doing this, the assumptions made will be further elaborated here.

## Rocket Specifications

In order to reach Titan's orbit, a sufficiently large exit velocity is required (to escape Earth's gravitational pull). To do this, some rudimentary calculations are needed. This will broken down into several categories starting with computing the required escape velocity. After this we will determine the power output required to do so, and how much fuel this would consume. Lastly, we will select a rocket which can meet all of these conditions. Using this information, we use the payload capsule volume available to select a deliverable which suits these dimensions.

### Escape Velocity

The escape velocity can be computed with the following equation:

# References

## Test section

``` Test 1<ref name="test"> Test reference. </ref> Test 2<ref name="test"></ref>. Test 3<ref name="what"> Another test.</ref>. ``` Yields:

Test 1[2] Test 2[2]. Test 3[3].

## Citations

1. FAQ on the Dragonfly rotorcraft destined for Titan [1]
2. 2.0 2.1 Test reference.
3. Another test.

## Uncited sources

• Nature (magazine) on Lakes On Titan - link
• Nature (journal) on Lakes On Titan - link
• On Terrain features on a part of Titan - link
• On extremophiles in astrobilogy - link
• On finding evidence of fossilized bacteria (on earth) - link
• Image based species identification - link
• On rover-to-orbiter communication - link
• DragonFly mission concept - link
• Space exploration for life - link
• The (progress of) development of autonomy technologies required to explore Titan - link
• Impervious surface mapping - link
• Achievements in space robotics - link
• Dragonfly mission page - link
• Gravity assisted space travel - link
• The Oberth effect - link
• NASA Scientists Discover ‘Weird’ Molecule in Titan’s Atmosphere - link
• Pictures of Saturn and Titan - link
• Modular Software for an Autonomous Space Rover - link
• Real time map building - link
• ESA Cassini-Huygens page - link
• DragonFly concept paper - link
• NASA Curiosity rover - link