| Both sides previous revision Previous revision Next revision | Previous revision |
| report [2024/06/25 14:02] – [7.2 Concept] team4 | report [2024/07/18 12:20] (current) – epsatisep |
|---|
| | Budget | 1200 | | | Budget | 1200 | |
| | **Expenses** | | | | **Expenses** | | |
| | Leaflets | 60 | [(360imprimirLeaflets)] | | | Leaflets | 60 | [(www360imprimirLeaflets)] | |
| | Posters | 70| [(360imprimirPosters)] | | | Posters | 70| [(www360imprimirPosters)] | |
| | Owned Media (Website) | 288| [(Shopifypricing)] | | | Owned Media (Website) | 288| [(Shopifypricing)] | |
| | Video Advertising (Youtube) | 100 | -- | | | Video Advertising (Youtube) | 100 | -- | |
| ==== - Ideation ==== | ==== - Ideation ==== |
| |
| Out of the second chapter of this report, the chapter on state of the art, the Scarabreed team concluded several drivers. Drivers are the very reason behind the design process. They are goals that are unique to the design process. Drivers are the force behind innovation. They are decided to serve a function, to meet some specific need, or to be useful in some way. | Based on the analysis of the state-of-the-art technologies presented in Chapter 2, the Scarabreed team identified several key design drivers. These drivers represent the essential goals that will guide the design process. Essentially, they are the forces that will propel innovation in this project. Each driver can be defined by its function, the specific need it addresses, or the utility it provides. |
| |
| In this project, one main driver changes the design of the product. Other drivers are still very relevant, however, they don’t determine the shape of the construction but stimulate technical innovation from within. This main design driver here is to design for modularity. A modular design allows the user of the product to scale, customize and transport easily. | In this project, one main driver changes the design of the product. Other drivers are still very relevant, however, they don’t determine the shape of the construction but stimulate technical innovation from within. This main design driver here is to design for modularity. A modular design allows the user of the product to scale, customize and transport easily. |
| </WRAP> | </WRAP> |
| |
| The fixture, see Figure {{ref>fixplac}}, has been chosen at this location because the weight of the other beetle breeders will be carried mainly at these two places if they are mounted on top of eachother. Furthermore, a point has been chosen to secure the BB V2 three-dimensionally as well. | The fixture, see Figure {{ref>fixplac}}, has been chosen at this location because the weight of the other beetle breeders will be carried mainly at these two places if they are mounted on top of each other. Furthermore, a point has been chosen to secure the BB V2 three-dimensionally as well. |
| |
| <WRAP centeralign > | <WRAP centeralign > |
| |
| == - Meshing == | == - Meshing == |
| After setting all settings, the mesh still needs to be determined. A small curvature-based mesh will be used in this study, as there are fillets and other details in the product that were unable to be deleted. Chosen mesh size is maximum 7mm and minimum 1mm. Everything in processing is now complete and the calculations can be started. | After setting all settings, the mesh still needs to be determined. A small curvature-based mesh will be used in this study, as there are fillets and other details in the product that were unable to be deleted. The mesh size chosen is a maximum of 7 mm and a minimum of 1 mm. Everything in processing is now complete and the calculations can be started. |
| == - Assessment == | == - Assessment == |
| The first test shows the integrity of the construction carrying other BB V2’s. This test is performed to simulate the mounting of four beetle breeders onto each other. The test simulates the bottom BB V2, carrying three other beetle breeders. | The first test shows the integrity of the construction carrying other BB V2’s. This test is performed to simulate the mounting of four beetle breeders onto each other. The test simulates the bottom BB V2, carrying three other beetle breeders. |
| <caption>Power consumption</caption> | <caption>Power consumption</caption> |
| <WRAP box center 600px> | <WRAP box center 600px> |
| ^ Component ^ Power consumption [Max] ^ | ^ Component ^ Power consumption [W] [Max] ^ |
| |Espressif32 (ESP32) |0.08 | | |Espressif32 (ESP32) |0.08 | |
| |LCD |1.32 | | |LCD |1.32 | |
| |Door contact |0.66 | | |Door contact |0.66 | |
| |Buzzer |0.5 | | |Buzzer |0.5 | |
| |**Power consumption**|**4.26 W**| | |**Total power consumption**|**4.26 **| |
| </WRAP> | </WRAP> |
| </table> | </table> |
| <WRAP centeralign > | <WRAP centeralign > |
| <table IDE> | <table IDE> |
| | <caption>IDE comparison</caption> |
| <WRAP box center 600px> | <WRAP box center 600px> |
| ^ IDE Platform ^ Advantage ^ Disadvantage^ | ^ IDE Platform ^ Advantage ^ Disadvantage^ |
| |ESP-IDF |* Optimized for ESP32\\ * Extensive Documentation\\ * Powerful Tools |* Wide knowledge required\\ * Manual Configuration\\ * Less Beginner-Friendly | | |ESP-IDF |* Optimized for ESP32\\ * Extensive Documentation\\ * Powerful Tools |* Wide knowledge required\\ * Manual Configuration\\ * Less Beginner-Friendly | |
| </WRAP> | </WRAP> |
| <caption>IDE comparison</caption> | |
| </table> | </table> |
| </WRAP> | </WRAP> |
| |
| As seen in {{ref>IDE}} the Arduino IDE is the best because it is easy to use, have extensive community support, and sufficient capabilities for a wide range of projects. This makes it an excellent choice for small project development. | As seen in Table {{ref>IDE}} the Arduino IDE is great because it is easy to use, have extensive community support, and sufficient capabilities for a wide range of projects. This makes it an excellent choice for small project development. |
| **Communication protocols** | **Communication protocols** |
| |
| <WRAP centeralign > | <WRAP centeralign > |
| <table PROT> | <table PROT> |
| | <caption>Communication protocols comparison</caption> |
| <WRAP box center 600px> | <WRAP box center 600px> |
| ^ Protocol ^ Advantage ^ Disadvantage^ | ^ Protocol ^ Advantage ^ Disadvantage^ |
| |MQTT |* Low Bandwidth Usage\\ * Lightweight and Efficient\\ * Publish/Subscribe Model|* Broker Dependency\\ * Security Configuration\\ * Quality of Service Trade-offs | | |MQTT |* Low Bandwidth Usage\\ * Lightweight and Efficient\\ * Publish/Subscribe Model|* Broker Dependency\\ * Security Configuration\\ * Quality of Service Trade-offs | |
| |HTTP |* Ubiquitous and Well-Understood\\ * Simple Request/Response Model\\ * Interoperability |* High Overhead\\ * ess Suitable for Real-Time Communication\\ * Resource Intensive | | |HTTP |* Ubiquitous and Well-Understood\\ * Simple Request/Response Model\\ * Interoperability |* High Overhead\\ * Less Suitable for Real-Time Communication\\ * Resource Intensive | |
| |CoAP |* Designed for IoT\\ * Low Overhead\\ * RESTful Interaction |* Less Mature Ecosystem\\ * Limited Security Options\\ * Niche Use Cases | | |CoAP |* Designed for IoT\\ * Low Overhead\\ * RESTful Interaction |* Less Mature Ecosystem\\ * Limited Security Options\\ * Niche Use Cases | |
| </WRAP> | </WRAP> |
| <caption>Communication protocols comparison</caption> | |
| </table> | </table> |
| </WRAP> | </WRAP> |
| |
| As seen in {{ref>PROT}} MQTT stands out due to its efficiency, scalability, and reliability, making it an ideal choice for applications involving the ESP32. Its low resource consumption and flexible communication model suits well with the needs of simple devices and complex IoT networks. | As seen in Table {{ref>PROT}} MQTT stands out due to its efficiency, scalability, and reliability, making it an ideal choice for applications involving the ESP32. Its low resource consumption and flexible communication model suits well with the needs of simple devices and complex IoT networks. |
| |
| |
| <WRAP centeralign > | <WRAP centeralign > |
| <table APPi> | <table APPi> |
| | <caption>App creators comparison</caption> |
| <WRAP box center 600px> | <WRAP box center 600px> |
| ^ Protocol ^ Advantage ^ Disadvantage^ | ^ Protocol ^ Advantage ^ Disadvantage^ |
| |Thunkable |* No-Code Development\\ * Cross-Platform Apps\\ * Community and Tutorials |* Limited IoT Integration\\ * Complexity in Advanced Features\\ * Subscription Model | | |Thunkable |* No-Code Development\\ * Cross-Platform Apps\\ * Community and Tutorials |* Limited IoT Integration\\ * Complexity in Advanced Features\\ * Subscription Model | |
| </WRAP> | </WRAP> |
| <caption>App creators comparison</caption> | |
| </table> | </table> |
| </WRAP> | </WRAP> |
| |
| as seen in {{ref>APPi}} Node-RED is the best choice for developing ESP32 applications due to its flexibility, powerful visual workflow management, and extensive ecosystem. These features make it a perfect choice for Scarabreed project. With this software it is easy to do from simple automation tasks to complex data processing. | As seen in Table {{ref>APPi}} Node-RED is the best choice for developing ESP32 applications due to its flexibility, powerful visual workflow management, and extensive ecosystem. These features make it a perfect choice for Scarabreed project. With this software it is easy to do from simple automation tasks to complex data processing. |
| <WRAP centeralign > | <WRAP centeralign > |
| <figure CHART> | <figure CHART> |
| </WRAP> | </WRAP> |
| |
| As seen in {{ref>CHART}} the user can adjust the preferences in the app. To make breeding as effective as possible user can adjust habitat for own preferences. | As seen in Figure {{ref>CHART}} the user can adjust the preferences in the app. To make breeding as effective as possible users can adjust settings for the best breeding conditions. |
| |
| |
| === - Lists of Materials for the Prototype === | === - Lists of Materials for the Prototype === |
| |
| All products for the prototype are shown in this table {{ref>tlabel5}}. The budget for the prototype is 100€. This must also include the transport costs and VAT. It is very difficult to build a reasonable prototype with this small budget. Despite the challenges, a satisfactory solution was ultimately reached. | All products for the prototype are shown in Table {{ref>tlabel5}}. The budget for the prototype is 100 €. This must also include the transport costs and VAT. It is very difficult to build a reasonable prototype with this small budget. Despite the challenges, a satisfactory solution was ultimately reached. |
| |
| <WRAP centeralign > | <WRAP centeralign > |
| ==== - Packaging ==== | ==== - Packaging ==== |
| |
| Scarabreed's packaging solution is designed with sustainability in mind, aiming to minimize waste and environmental impact. The packaging consists of three main parts: the box lid, the box fitment, and the bottom of the box. Each component is crafted from 3mm thick recycled cardboard, reducing the need for new raw materials and promoting a circular economy. | Scarabreed's packaging solution is designed with sustainability in mind, aiming to minimize waste and environmental impact. The packaging consists of three main parts: the box lid, the box fitment, and the bottom of the box. Each component is crafted from 3 mm thick recycled cardboard, reducing the need for new raw materials and promoting a circular economy. |
| |
| === - 3D Packaging === | === - 3D Packaging === |
| |
| |
| === - Sustanability features === | === - Sustainability features === |
| |
| Throughout the packaging design process, Scarabreed prioritizes sustainability by incorporating several key features: | Throughout the packaging design process, Scarabreed prioritizes sustainability by incorporating several key features: |
| |
| === - Software === | === - Software === |
| Detail and explain any changes made in relation to the designed solution, including different software components, tools, platforms, etc. | |
| |
| The software was developed with each component in mind and then integrated into a single code. The door contact was experiencing intermittent issues due to a lack of a pull-up resistor. Once this was rectified, the system was fully operational. One button is used to change the menu, while the other is a trigger for each functionality. The fan is functioning in conjunction with the LED stripe. When the fan is activated, the LED stripe turns blue, indicating that the status has been updated on the display. The door contact is integrated with the display and LED stripe. Upon opening the doors, the LED stripe is activated, updating the display in real-time. | The software was developed with each component in mind and then integrated into a single code. The door contact was experiencing intermittent issues due to a lack of a pull-up resistor. Once this was rectified, the system was fully operational. One button is used to change the menu, while the other is a trigger for each functionality. The fan is functioning in conjunction with the LED stripe. When the fan is activated, the LED stripe turns blue, indicating that the status has been updated on the display. The door contact is integrated with the display and LED stripe. Upon opening the doors, the LED stripe is activated, updating the display in real-time. |
| </WRAP> | </WRAP> |
| |
| As seen in {{ref>Cd1}} the libraries and enum type for menu list is created. In this fragment also all defines are defined. As seen in {{ref>Cd2}} I2C is created and all inputs and outputs are declared. In {{ref>Cd3}} the menu switching is declared and implemented. Plus there is logic for door contact. In {{ref>Cd4}} The toggle button is declared and all logic for presentation code is implemented. In {{ref>Cd5}} all the data is displayed on OLED. As seen at {{ref>Cd6}} declaration of wifi setup function. At {{ref>Cd7}} is displayed sending data to the mosquitto is implemented. | As seen in Figure {{ref>Cd1}} the libraries and enum type for the menu list are created. In this fragment also all definitions are defined. As seen in Figure {{ref>Cd2}} I2C is created and all inputs and outputs are declared. In Figure {{ref>Cd3}} the menu switching is declared and implemented. Plus there is logic for door contact. In Figure {{ref>Cd4}} The toggle button is declared and all logic for presentation code is implemented. In Figure {{ref>Cd5}} all the data is displayed on OLED. As seen in Figure {{ref>Cd6}} declaration of the wifi setup function. Figure {{ref>Cd7}} shows how sending data to the mosquito is implemented. |
| |
| **Data chart** | **Data chart** |
| </figure> | </figure> |
| </WRAP> | </WRAP> |
| as seen {{ref>SCH23}} monitoring app is sending the data to MQTT broker. | As seen in Figure {{ref>SCH23}} monitoring app is sending the data to MQTT broker. |
| |
| === - Tests & Results === | === - Tests & Results === |
| In this chapter all changes and progress with prototype are analyzed. Tables with Tests and results plus difference to final solution.\\ | In this Subchapter, all changes and progress with the prototype are analyzed. Tables with Tests and results plus the difference to the final solution.\\ |
| **Hardware tests** | **Hardware tests** |
| <WRAP centeralign > | <WRAP centeralign > |
| </WRAP> | </WRAP> |
| |
| As we can see in {{ref>SCH2}} for prototype there are used two power supplies. 5V power supply is for ESP32 and fan. 12V is for LED stripe. This could be done with voltage regulator to step down 12V to 5V. To control fan there is simple Darlington bridge with two transistors. As the budget was low the IR light, humidity spray and the buzzer were cut. Rest of the components are the same as in deliverable solution. | Figure {{ref>SCH2}} illustrates the use of two power supplies for the prototype. The 5 V power supply is designated for the ESP32 and fan, while the 12 V supply is allocated for the LED stripe. The implementation of a voltage regulator could facilitate the reduction of the 12V supply to 5 V. The fan control system employs a straightforward Darlington bridge configuration comprising two transistors. In consideration of the limited budgetary constraints, the infrared light, humidity spray, and buzzer were excluded from the final design. The remaining components are identical to those employed in the deliverable solution. |
| |
| |
| </WRAP> | </WRAP> |
| |
| Every connection was tested with multimeter. | Every connection was tested with a multimeter. |
| |
| **Software tests** | **Software tests** |
| |
| Software was tested with every component and than it was implemented in one code. The door contact was malfunctioning for most of the time because of the lack of pull-up resistor then it worked fine. One button is responsible for changing the menu and the other like a trigger for each functionality. | The software was tested with every component and then it was implemented in one source file. The door contact was malfunctioning for most of the time because of the lack of a pull-up resistor then it worked fine. One button is responsible for changing the menu and the other like a trigger for each functionality. |
| |
| <WRAP centeralign > | <WRAP centeralign > |
| </WRAP> | </WRAP> |
| Table {{ref>ol2}} displays the load results for the longest API request. These results show | Table {{ref>ol2}} displays the load results for the longest API request. These results show |
| that, when in production, the Web app must be hosted by an elastic server solu- | that, when in production, the Web app must be hosted by an elastic server solution to reduce the latency to values compatible with an acceptable user experience. |
| tion to reduce the latency to values compatible to an acceptable user experience. | |
| As expected, the exchanged data per request remains unchanged. | As expected, the exchanged data per request remains unchanged. |
| ==== - Conclusion ==== | ==== - Conclusion ==== |
| After analyzing existing brands and technologies, Scarabreed has successfully developed the BBV2 - Beetles Breeder Version 2, a solution for breeding endangered beetle species. | After analyzing existing brands and technologies, Scarabreed has successfully developed the BBV2 - Beetles Breeder Version 2, a solution for breeding endangered beetle species. |
| |
| The BBV2 features a modular design, allowing for easy scaling, customization, and transport. It has a trapezium form optimized for stability and space efficiency, and it provides dual access from both the front and back for convenient maintenance and monitoring. The technological compartment at the top monitors and controls environmental parameters. Built-in cable ducts enable seamless connection and scalability of multiple vivariums. The BBV2 is constructed from high-quality stainless steel for durability. The team uses a ESP32 microcontroller and a SHT21 sensor for precise humidity and temperature control. | The BBV2 features a modular design, allowing for easy scaling, customization, and transport. It has a trapezium form optimized for stability and space efficiency, and it provides dual access from both the front and back for convenient maintenance and monitoring. The technological compartment at the top monitors and controls environmental parameters. Built-in cable ducts enable seamless connection and scalability of multiple vivariums. The BBV2 is constructed from high-quality stainless steel for durability. The team uses an ESP32 microcontroller and an SHT21 sensor for precise humidity and temperature control. |
| |
| Technically, the team conducted Finite Element Analysis (FEA) to approximate system behavior and validated structural integrity through load testing, confirming the system withstands 588.6N which was ensured by structural reliability with mesh analysis. | Technically, the team conducted Finite Element Analysis (FEA) to approximate system behavior and validated structural integrity through load testing, confirming the system withstands 588.6 N which was ensured by structural reliability with mesh analysis. |
| For the realization of the vivarium, CAD models were made using SolidWorks, followed by a cardboard prototype to identify and correct potential issues. Additionally, lists of materials were made for both the prototype and the final product. The team also designed a reusable and sustainable packaging to minimize environmental impact. | For the realization of the vivarium, CAD models were made using SolidWorks, followed by a cardboard prototype to identify and correct potential issues. Additionally, lists of materials were made for both the prototype and the final product. The team also designed a reusable and sustainable packaging to minimize environmental impact. |
| |