System Architecture MSD19: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
</div> | </div> | ||
__TOC__ | __TOC__ | ||
Contents | |||
Autonomous drone referee system architecture has been implemented by taking into account both CAFCR[1] and SafeRobots[2] frameworks. The focus in the project has been heavily concentrated towards the design and implementation having derived the requirement specifications and hardware resources available | Autonomous drone referee system architecture has been implemented by taking into account both CAFCR[1] and SafeRobots[2] frameworks. The focus in the project has been heavily concentrated towards the design and implementation having derived the requirement specifications and hardware resources available | ||
| Line 11: | Line 15: | ||
In the operational space covers the process of developing tangible deliverables that satisfy functional and non-functional requirements that were initially prescribed. | In the operational space covers the process of developing tangible deliverables that satisfy functional and non-functional requirements that were initially prescribed. | ||
The overall methodology of our roadmap can be found in the table below: | The overall methodology of our roadmap can be found in the table below: | ||
=Architectural Framework= | |||
<span style="color:black"> | |||
'''Autonomous drone referee system architecture has been implemented by taking into account both CAFCR[1] and SafeRobots[2] frameworks. The focus in the project has been heavily concentrated towards the design and implementation having derived the requirement specifications and hardware resources available | |||
As a tailored approach to our goal the team developed the system level reasoning based on abstract knowledge defined in the Problem space. These were the requirement chosen to be most critical, the context of the problem and which problems we strive most to address. | |||
Then design choices were made based on thereof to define the Solution Space consisting of hardware and other tools to utilise, algorithms for path planning and communication protocols. This namely was the design time and opportunity to mitigate uncertainties. | |||
In the operational space covers the process of developing tangible deliverables that satisfy functional and non-functional requirements that were initially prescribed. | |||
The overall methodology of our roadmap can be found in the table below:''' | |||
</span> | |||
==Manual Flight== | |||
This section explains in detail on how to setup a Crazyflie 2.X drone starting from hardware assembly to first manual flight. We used Windows to continue with initial setup of the software part for manual flight. However, Linux (Ubuntu 16.04) was preferred for the autonomous flight. Following additional hardware is required to setup first manual flight. | |||
* Bitcraze Crazyradio PA USB dongle | |||
* A remote control (PS4 Controller or Any USB Gaming Controller) | |||
Revision as of 13:55, 24 March 2020
Contents
Autonomous drone referee system architecture has been implemented by taking into account both CAFCR[1] and SafeRobots[2] frameworks. The focus in the project has been heavily concentrated towards the design and implementation having derived the requirement specifications and hardware resources available As a tailored approach to our goal the team developed the system level reasoning based on abstract knowledge defined in the Problem space. These were the requirement chosen to be most critical, the context of the problem and which problems we strive most to address. Then design choices were made based on thereof to define the Solution Space consisting of hardware and other tools to utilise, algorithms for path planning and communication protocols. This namely was the design time and opportunity to mitigate uncertainties. In the operational space covers the process of developing tangible deliverables that satisfy functional and non-functional requirements that were initially prescribed. The overall methodology of our roadmap can be found in the table below:
Architectural Framework
Autonomous drone referee system architecture has been implemented by taking into account both CAFCR[1] and SafeRobots[2] frameworks. The focus in the project has been heavily concentrated towards the design and implementation having derived the requirement specifications and hardware resources available As a tailored approach to our goal the team developed the system level reasoning based on abstract knowledge defined in the Problem space. These were the requirement chosen to be most critical, the context of the problem and which problems we strive most to address. Then design choices were made based on thereof to define the Solution Space consisting of hardware and other tools to utilise, algorithms for path planning and communication protocols. This namely was the design time and opportunity to mitigate uncertainties. In the operational space covers the process of developing tangible deliverables that satisfy functional and non-functional requirements that were initially prescribed. The overall methodology of our roadmap can be found in the table below:
Manual Flight
This section explains in detail on how to setup a Crazyflie 2.X drone starting from hardware assembly to first manual flight. We used Windows to continue with initial setup of the software part for manual flight. However, Linux (Ubuntu 16.04) was preferred for the autonomous flight. Following additional hardware is required to setup first manual flight.
- Bitcraze Crazyradio PA USB dongle
- A remote control (PS4 Controller or Any USB Gaming Controller)