Differences

This shows you the differences between two versions of the page.

--- report [2023/06/18 15:28] – [7.5 Prototype] team5
+++ report [2023/06/21 18:13] (current) – [1.2 Motivation] team5
@@ Line 87: / Line 87: @@
 As a group, we looked over a number of project ideas and decided that the outdoor blimp was the most exciting one. It was a new idea that most of us had never really heard of before, while we were aware of large commercial or private zeppelins, we were unaware of any that could perform smaller duties. We were intrigued by the concept, and it inspired our creativity, which resulted in a wide range of potential uses. The options were limitless, ranging from use of transportation to directions in any city to even serving as props on film shoots. But we were all driven by a desire to build something that could actually improve people's lives.
-Throughout our brainstorming sessions, we concentrated on identifying the global challenges that needed to be resolved. When we conducted our study and brainstorming, we came to the conclusion that many places of the world, such as rural Africa, the high mountains, the deserts, and other distant areas have a lack of network access or even none at all. This insight gave us the idea to design a blimp that may improve network coverage in such regions.
+During our brainstorming sessions, we focused on identifying global challenges that required resolution. As we conducted our study, we discovered a significant issue in Australia: the vast size of cattle farms and the difficulty in effectively monitoring livestock on such large scales.
+This discovery inspired us to think about potential fixes for the issue. We discovered that in these large farmed areas, standard monitoring equipment frequently failed to provide complete coverage and real-time data. This insight motivated us to look into new approaches, which is how we came up with the concept of using a blimp as a surveillance tool for Australian cattle farms.
-As we continued to explore the possibilities, we also considered the potential for our blimp to be used in emergency situations, such as during forest fires or when people are lost in the wilderness. Combining these two ideas, we decided to create a blimp that could both enhance network connectivity in remote areas and provide guidance in emergency situations.
+The limits of traditional monitoring techniques are intended to be overcome by the deployment of a blimp equipped with cutting-edge sensors and technology. Through the introduction of a more effective and comprehensive method of monitoring the welfare and movement of cattle throughout Australia's vast farming landscapes, this technology has the potential to revolutionize livestock monitoring.
@@ Line 671: / Line 671: @@
 <caption>Labor cost</caption>
 <WRAP box 1000px center>
-^ Name                          ^ Salary (month)  ^ Income tax (14.5 %)  ^ Social security employee (11 %)  ^ Social security employer (23.75 %)  ^ Salary after income tax and social security (month)  ^ Salary (year)    ^
+^ Name                          ^ Salary (month)  ^ Income tax ( 14.5 % )  ^ Social security employee ( 11 % )  ^ Social security employer ( 23.75 % )  ^ Salary after income tax and social security (month)  ^ Salary (year)    ^
 | Sonia Gupta                   | 2000 €           | 200 €                | 220 €                            | 475 €                               | 1015 €                                                | 12 180 €           |
 | Krijn Blommestijn             | 2000 €           | 200 €                | 220 €                            | 475 €                               | 1015 €                                                | 12 180 €           |
@@ Line 3270: / Line 3270: @@
 ==== - Prototype ====
-Refer main changes in relation to the designed solution.
 === - Structure===
-Detail and explain any changes made in relation to the designed solution, including structural downscaling, different materials, parts, etc.
 In relation to the designed solution several changes were made. Most of them regarding the design of the parts due to the different manufacturing technique. The designed solution will be manufactured through injection molding while the prototype is 3D-printed.
 Because of that the printability of the parts is a limiting factor in terms of shape.
 Figure {{ref>flabelblimpassembly}} conveys the overall design.
-<WRAP leftalign>
+<WRAP centeralign>
 <figure flabelblimpassembly>
-{{:animo_prototype_blimp_assembly_colour-1.png?600 |}}
+{{ :animo_prototype_blimp_assembly_colour-1.png?400 |}}
 </caption>Structural draft of the blimp prototype</caption>
 </figure>
@@ Line 3290: / Line 3286: @@
 In addition, in certain areas of the lid material was removed in such a way, that the lid of the prototype is thinner with some reinforcing struts that have the same thickness as the original part. So the overall mass is lower, but the stiffness and strength are approximately the same. This design is also benefitial for the process of 3D-printing the part, because the probability of warping is significantly lower.
-<WRAP leftalign>
+<WRAP centeralign>
 <figure flabelprotogondola>
-{{:animo_prototype_gondola_colour-1.png?600|}} {{:animo_prototype_lid_colour-1.png?600 |}}
+{{:animo_prototype_gondola_colour-1.png?400|}} {{:animo_prototype_lid_colour-1.png?400|}}
 </caption>Structural drafts of the gondola and the detachable bottom, named lid</caption>
 </figure>
@@ Line 3299: / Line 3295: @@
 The same design principle was applied to the servo motor mounting plate (figure {{ref>flabelsmmounting}}.
-<WRAP leftalign>
+<WRAP centeralign>
 <figure flabelsmmounting>
-{{:animo_prototype_sm_mounting_colour-1.png?600 |}}
+{{ :animo_prototype_sm_mounting_colour-1.png?400 |}}
 </caption>Structural draft of the adjustable mounting for the servo motor</caption>
 </figure>
@@ Line 3310: / Line 3306: @@
 Like in the original design the arms are slided into the ends of the hollow coupling and mounted with screws and nuts as shown on the left of figure {{ref>flabelarmassembly}}.
-<WRAP leftalign>
+<WRAP centeralign>
 <figure flabelarmassembly>
-{{:animo_prototype_arm_assembly_colour-1.png?600 |}}
+{{:animo_prototype_arm_assembly_colour-1.png?400|}} {{:animo_prototype_coupling_colour-1.png?400|}}
-{{:animo_prototype_coupling_colour-1.png?600 |}}
 </caption>Structural drafts of the assembly of the arm-coupling subassembly and the coupling itself</caption>
 </figure>
@@ Line 3320: / Line 3315: @@
 === - Hardware ===
-Detail and explain any change made in relation to the designed solution.
-In case there are changes regarding the hardware, present the detailed schematics of the prototype.
+Regarding the original product, a few hardware changes have been made.
+The microcontroller has been replaced with the less powerful Zero W. The original product's two batteries have been replaced with a single, but heavier one. For the sake of simplicity, ready-made propeller modules were used as the propulsion units for the prototype. Another GNSS sensor is also used.
+This way most of the functionalities of the blimp can be realized in a cost reducing manner.
+The wiring of the components is displayed in figure {{ref>flabelhardwareproto}}.
+<WRAP centeralign>
+<figure flabelhardwareproto>
+{{ :20230619_system_schematics_prototype.png?700 |}}
+</caption>System schematics of the ANIMO prototype</caption>
+</figure>
+</WRAP>
+The parts in the following table were used for the prototype.
 **Electronic Components for the Prototype**
@@ Line 3340: / Line 3347: @@
 === - Software ===
-Detail and explain any changes made in relation to the designed solution, including different software components, tools, platforms, etc.
-The code developed for the prototype (smart device and apps) is described here using code flowcharts.
+For the prototype app, we used the same technologies as the designed solution. However, we made a slight alteration by employing web sockets instead of a cloud-based service like AWS. This decision was primarily driven by budget constraints and the simplicity it offered during the prototype phase.
-For the prototype app, we utilised the same technologies as the designed solution. However, we made a slight alteration by employing web sockets instead of a cloud-based service like AWS. This decision was primarily driven by budget constraints and the simplicity it offered during the prototype phase.
 The app's functionality includes:
@@ Line 3359: / Line 3363: @@
 This comprehensive functionality allows users to seamlessly interact with the app, managing their blimps and monitoring their locations in real-time.
-=== - Tests & Results ===
+The flow of the app is shown in table {{ref>fsoftwareflowprototpe}} below, which illustrates the sequence of actions and interactions within the application. This flow showcases the logical progression and functionality of the app.
-== Hardware tests ==
+<WRAP centeralign>
-Perform the hardware tests specified in **1.6 Functional Tests**. These results are usually presented in the form of tables with two columns: Functionality and Test Result (Pass/Fail).
+<figure fsoftwareflowprototpe>
+{{ :softwareprototype.png?600 |}}
+<caption>Flowchart prototype app</caption>
+</figure>
+</WRAP>
+The code for creating the prototype app can be found in the following link: [[https://github.com/Sonia200108/ANIMO|Github repository]]
+The visual representation of the app can be found in the below figures {{ref>fmockupprotoype1}} {{ref>fmockupprotoype2}} {{ref>fmockupprotoype3}}. below. This image provides a visual overview of the app's user interface and design.
+<WRAP centeralign>
+<figure fmockupprotoype1>
+{{ :mockupprototype1.png?600 |}}
+<caption>Prototype visual 1</caption>
+</figure>
+</WRAP>
+<WRAP centeralign>
+<figure fmockupprotoype2>
+{{ :mockupprototype2.png?600 |}}
+<caption>Prototype visual 2</caption>
+</figure>
+</WRAP>
+<WRAP centeralign>
+<figure fmockupprotoype3>
+{{ :mockupprototype3.png?600 |}}
+<caption>Prototype visual 3</caption>
+</figure>
+</WRAP>
+=== - Tests & Results ===
 == Software tests ==
-Software tests comprise:
+The results of our API functionality and performance tests, specifically focusing on latency, can be found in Table {{ref>tab_softwaretest}} . Using Postman, we measured the response times and throughput of the API in various scenarios. The captured data allowed us to analyse and optimise the API speed and reliability, ensuring that the observed latency remained within acceptable limits. Table {{ref>tab_softwaretest}} provides a comprehensive overview of the latency results, highlighting the efficiency of the API in delivering timely responses.
-(i) functional tests regarding the identified use cases / user stories;
-(ii) performance tests regarding exchanged data volume, load and runtime (these tests are usually repeated 10 times to determine the average and standard deviation results);
+<WRAP centeralign>
-(iii) usability tests according to the [[https://www.usability.gov/how-to-and-tools/methods/system-usability-scale.html|System Usability Scale]].
+<table tab_softwaretest>
+<caption>API: Functional and performance results</caption>
+<WRAP box 900px center>
+{{tablelayout?rowsHeaderSource=Auto&colwidth=",,,,"}}
+^                      ^         |         |             ^ Latency         ^^
+^ Functionality        ^ Method  ^ Result  ^ Size ( B )  ^ μ        ^ σ     ^
+| Address              |         |         |             |          |       |
+| /api/addresses       | GET     | OK      | 465         | 10,20    | 1,30  |
+| /api/addresses       | POST    | OK      | 347         | 12,00    | 3,54  |
+| /api/addresses       | PUT     | OK      | 353         | 9,00     | 1,41  |
+| /api/addresses/{id}  | DELETE  | OK      | 257         | 12,20    | 3,70  |
+| /api/addresses/{id}  | GET     | OK      | 366         | 9,20     | 5,54  |
+|                      |         |         |             |          |       |
+| Blimp                |         |         |             |          |       |
+| /api/blimps          | GET     | OK      | 716         | 8,80     | 3,63  |
+| /api/blimps          | POST    | OK      | 405         | 10,60    | 4,04  |
+| /api/blimps          | PUT     | OK      | 482         | 9,60     | 1,95  |
+| /api/blimps/{id}     | DELETE  | OK      | 257         | 11,00    | 5,39  |
+| /api/blimps/{id}     | GET     | OK      | 484         | 9,60     | 4,34  |
+|                      |         |         |             |          |       |
+| Farm                 |         |         |             |          |       |
+| /api/farms           | GET     | OK      | 554         | 10,80    | 7,46  |
+| /api/farms           | POST    | OK      | 405         | 11,40    | 5,68  |
+| /api/farms           | PUT     | OK      | 398         | 8,80     | 2,95  |
+| /api/farms/{id}      | DELETE  | OK      | 257         | 12,80    | 8,04  |
+| /api/farms/{id}      | GET     | OK      | 399         | 7,40     | 2,70  |
+|                      |         |         |             |          |       |
+| User                 |         |         |             |          |       |
+| /api/users           | GET     | OK      | 1003        | 8,40     | 2,51  |
+| /api/users           | POST    | OK      | 506         | 12,20    | 5,02  |
+| /api/users           | PUT     | OK      | 499         | 11,40    | 5,13  |
+| /api/users/{id}      | DELETE  | OK      | 257         | 8,20     | 1,79  |
+| /api/users/{id}      | GET     | OK      | 502         | 8,40     | 5,94  |
+</WRAP>
+</table>
+</WRAP>
+To evaluate the performance of our API under different load conditions, we conducted comprehensive load testing. By identifying the API endpoint with the highest latency, we focused our analysis on its behaviour under increasing load levels, specifically with batches of 10, 100, and 1000 requests. These load testing results, including the latency measurements, can be found in Table {{ref>tab_sofloadtest}}, providing valuable insights into the scalability and responsiveness of the API and guiding our optimisation efforts to ensure a reliable experience for our users.
+<WRAP centeralign>
+<table tab_sofloadtest>
+<caption>API: load results</caption>
+<WRAP box 900px center>
+{{tablelayout?rowsHeaderSource=Auto&colwidth=",,,,"}}
+|          |                 |         |          |             ^ Latency         ^^
+^ Request  ^ Functionality   ^ Method  ^ Results  ^ Size ( B )  ^ μ        ^ σ     ^
+| 10       | /api/farms/id   | DELETE  | 10       | 257         | 6,00     | 2,31  |
+| 100      | /api/farms/id   | DELETE  | 100      | 257         | 4,73     | 1,02  |
+| 1000     | /api/farms/id   | DELETE  | 1000     | 257         | 3,66     | 0,64  |
+</WRAP>
+</table>
+</WRAP>
 ==== - Conclusion ====
-//Provide here the conclusions of this chapter and introduce the next chapter.//
+In conclusion, Chapter 7 takes us through the pivotal stages of ideation, concept development, design, and prototyping, which collectively form the foundation of our project's development.
+During the ideation phase, our team engaged in extensive research and analysis to identify gaps in the market and generate innovative ideas. Through this process, we harnessed creativity and critical thinking to address specific problems and meet user needs effectively.
+The concept development phase enabled us to refine and shape our ideas, considering feasibility factors and aligning them with our overarching goals. Collaborative efforts and a diverse range of expertise were instrumental in ensuring the practicality and viability of the proposed concepts.
+The subsequent design and prototyping stages involved translating our conceptualized ideas into tangible representations. Through sketches, diagrams, and computer-aided design tools, we meticulously crafted the visual and functional aspects of our project. Iterative prototyping allowed us to evaluate and refine our designs, ultimately resulting in a functional prototype that was thoroughly tested for performance, functionality, and user experience.
+Overall, Chapter 7 underscores the importance of a systematic and iterative approach in transforming initial ideas into tangible outcomes. It highlights the significance of creativity, research, collaboration, attention to detail, and feasibility considerations in the development process. The insights gained from this chapter provide a strong foundation for the subsequent chapters, where we will delve deeper into the results, analysis, and advancements of our project.
+The next chapter, "Conclusions," will provide a comprehensive discussion of the project's outcomes, implications, and future development prospects.
 ===== - Conclusions =====
 ==== - Discussion ====
@@ Line 3400: / Line 3496: @@
 ===== Bibliography =====
-//Will be added automatically by citing, in the body of the report, entries specified in BibTeX format and stored in the https://www.eps2023-wiki5.dee.isep.ipp.pt/doku.php?id=refnotes:bib file//
-PS - //If you have doubts on how to make citations, create captions, insert formulas, etc. visit this [[https://www.eps2023-wiki5.dee.isep.ipp.pt/doku.php?id=example | page]] with examples and select "Show pagesource" to see the source code.//