Task Force 141 - Space Apps Challenge

Task Force 141| Let's Connect

Let's Connect

For bigger spacecraft capable of executing bigger missions, some of the assembly may be done in space. Your challenge is to design a simple approach that enables components to be assembled in space.

D.A.B. (Docking and Assembly Bot)

Summary

This innovation was able to provide a new foundation for space engineering, assisting us in easier methods of in-space assembly and docking. The complete assembly process would require the help of autonomous robots, back-up methods of manually controlling and an uncomplicated way of independent assembly without the worry of a human being in danger. The examples we gave in the introduction also gave a basic understanding of the uprise of new technologies in the space sector, such as PULSAR and LUVOIR. Finally, we designed a complex, but simple resolution to the problem of space construction.

How We Addressed This Challenge

Connection. Exploration. Expansion.

The trio may look like three different words to the naked eyes, though they are interrelated, telling us a deep history of innate human tendencies. The co-dependent nature of human beings shows our longing for connectivity in all brackets of life. Paradoxically, we fear the unknown even though it evokes our curiosity to witness it.

Astronomers, astrophysicists, and scientists, in general, have recognized and focused on the critical nature of in-space assembly and docking. Humans are now expanding into uncharted territory – construction in-space. The technology required has been thought of, idealized per se, but not been tested practically in the correct environments and surroundings required. NASA launched its goal to reach the Moon by 2024, in May 2019; SpaceX’s goal is to reach Mars; the basic pattern visible is to explore and expand into the solar system.

For this, we need a mechanism, which will assist us in assembly and docking in space to manufacture megastructures, making it easier for us to travel from planet to planet.

Space construction is necessary because when something is too large to be transported to orbit or it’s delicate enough to break during launch. In-space assembly is a complicated procedure as we demand a method to construct in space rather than build on Earth and then launch it into space. Furthermore, there is an infinitive number of limitations and drawbacks of in-space assembly.

Regarding the current topic, the European Union recently established the Horizon 2020 programme for science research, setting up the “Space Robotic Technologies” Space Research Centre also known as the SRC. Under PERASPERA (It is a Program Support Activity for implementation of robotics in space), especially in the 2018 call [there were three calls designed for space robotics in 2016, 2018 and 2020], there was exceptional focalization on the coalescence of robotics in the space sector with special reference to planetary and orbital use. For example, the LUVOIR is a multi-wavelength telescope that would be too enormous to be constructed in space and then launched into geosynchronous orbit. Rather than doing that, it would have to be assembled by autonomous robots. These mechanical devices would not only help in fabricating telescopes, but would encompass the new era of space colonization, aiding us in building tremendous structures like the Death Star (maybe that’s an exaggeration, but okay). Another example would be the PULSAR project (which stands for “Prototype for an Ultra Large Structure Robot). It is a project initiated by Horizon 2020 to develop autonomous robots for construction of two 8m and 12m diameter mirrors, but the technology utilized would not be restricted to telescopes. It would cover different types of structures, benefitting us for being economical, structurally and functionally sound.

Since we’ve already talked about assembly, the other components of construction in space are docking and berthing. Docking, in layman’s term, refers to the joining of two free-flying space vehicles while berthing refers to the attachment of a passive structure to a space vehicle via a robotic arm. Most people confuse these two terms together due to inadequate knowledge about space engineering. Autonomous bots would make it easier for both, making connection easier for us. Potentially (if modified), these bots could also help with the engineering and repairing aspects of space construction.

We hope for a better-connected world, without any flaws. Perfection can never be achieved, nonetheless the race for perfection is never-ending.

How We Developed This Project

Thought Process

A few weeks ago, everyone in our school was told about the NASA Space Apps Hackathon which was to take place on the 3rd and 4th of October. Initially intimidated, we were discouraged to participate; but the next day we all decided to make an unofficial team until our official team was to be decided by the administration. After a few days, we were approved of our participation and held a few meetings to decide our challenge. We considered many such as Data Discovery for Earth Science, Orbital Sky, Sleep Shift Scheduling Tool and others, but finally we came to an agreement on Let's Connect due to it's uncharted nature. Over the last week before the hackathon, we analysed what other people had done and what we could do. During that time period, we figured out the topics we were meant to talk and write about. We started holding more and more meetings so that we could all be on the same track as each other, making sure no one was unsure or hesitant. During the hackathon weekend, we worked restlessly starting with the textual content and even naming our bot! Throughout the 48 hour timeline, we made a PPT to showcase our work in a simplistic and minimalistic manner, voiced over and presented by our member Shrey. We faced many difficulties such as -

Our spare time rarely collided, disabling us to work in a flow at all times.
We faced technical difficulties due to bad network connections.
Disturbances in our team due to personal issues.

But it was all overshadowed by our impeccable team communication and unity, helping us achieve our goal.

Roles

Swastik (Technical Designer and Planner)

Swastik was one of the first members of the team for the hackathon and took most of the initiative, making sure we reached our goal. He planned a lot of our decisions, expediting the entire process and lessening the number of worries we had. Nearly all the technical work was accomplished by him, such as the designing and modelling. A tech-savvy person always comes in need like Swastik.

Shrey (Team Manager)

Shrey was also one of the original members of Task Force 141, who too took a lot of initiative. He planned a lot of the topics we had to be prepared on, providing us with credible research. He managed the team well, ensuring that everyone was working skilfully and without any doubts. He kept the flow of communication faultless and made certain that no one was undecided. Not only did Shrey have the power, he was able to empower us.

Riddhima (Artist and Team Consultant)

Riddhima was a major integrant of the team, who was able to imagine a conceivable depiction of the mechanism. She sketched out blueprints for us to build upon, and gave us better ideas by finding the path when it seemed as if we had lost our way. She simplified our complications and made the oversimplified intricate.

Samvit (Tech Designer and Planner)

Samvit joined us later on during the last week, nonetheless he made his presence felt by giving us major advice and what we should focus on. He was able to create a paramount amount of righteous change in a few days and helped in maintaining a orderly dataset for us to store all of our references upon. He made our intelligence visible to others.

Jaskiran (Artist and Team Consultant)

Jaskiran was another notable constituent of the team, who also conceptualized and interpreted our basic design. She gave us an outsider perspective, as a result of her out of the box thinking. She established a fundamental understanding on the topic and clarified our uncertainties and obscurities.

How We Used Space Agency Data in This Project

Initially, we didn't know where to start. In an opening session of the boot camp, we got to know about the NASA open data. We utilized it to our full extent for resources looking for research papers and valid information about space engineering and autonomy in-space assembly and docking.

We mostly required a base to build to our project upon, so that we could let our creativity unravel. After a while, we found out about the NASA Exoplanet Program which contained an In-Space Assembly Archive. This enhanced our thinking further and enabled us to think out of the box.