Differences

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

--- report:dvp [2026/04/12 19:34] – [Software] team6
+++ report:dvp [2026/04/30 14:14] (current) – [Smart System] team6
@@ Line 3: / Line 3: @@
 ==== Introduction ====
 //Provide here an overview of the contents (structure) of this chapter.//
-The
+\\
+This chapter contains our project's evolution, in particular, you can find currently the concept, designs, smart system, structure and also the materials chosen for the Healing Cocoon.
 ==== Ideation ====
-The idea of the //Healing Cocoon// came to us after reflection and several brainstorming sessions. First, we tried to recall events we had experienced and heard about in the fields of health and well-being. We quickly focused on the impact of the medical environment (hospitals or waiting rooms) and agreed to work on a solution to improve experiences in medical settings.
+The idea of the Healing Cocoon came to us after reflection and several brainstorming sessions. First, we tried to recall events we had experienced and heard about in the fields of health and well-being. We quickly focused on the impact of the medical environment (hospitals or waiting rooms) and agreed to work on a solution to improve experiences in medical settings.
 ==== Concept ====
-The concept of the //Healing Cocoon// is to transform clinical environments into calming and immersive spaces.
+The concept of the Healing Cocoon is to transform clinical environments into calming and immersive spaces.
 By combining light, sound and scent, it helps reduce stress and improve children well-being.
-The features of our //Healing Cocoon//:
+The features of our Healing Cocoon:
   * Calming audio and scent stimulation
   * Immersive 180° visual environment
@@ Line 19: / Line 20: @@
 === Structure ===
-  * Initial structural drafts and materials details -- Figure {{ref>fig:External_drawing}} shows the rigid metal structure made of aluminium arches (this material was chosen because it is less expensive than brass and easy to work with.). In red, we drew the brass panels that will be attached to the metal structure (the exterior surface of the panels will be brushed to make the outside of the cocoon less metallic and more welcoming).
+  - **Initial structural drafts and materials details** -- Figure {{ref>fig:External_drawing}} shows the rigid metal structure made of aluminium arches (this material was chosen because it is less expensive than brass and easy to work with.). In red, we drew the brass panels that will be attached to the metal structure (the exterior surface of the panels will be brushed to make the outside of the cocoon less metallic and more welcoming).
 <WRAP centeralign>
 <figure fig:External_drawing>
@@ Line 34: / Line 35: @@
 </WRAP>
-  - Material selection -- Figure {{ref>fig:Cross-section}} shows the different layers of our cocoon's structure. The air gap is due to the presence of the arched metallic structure in certain area of the cocoon, as shown in Figure {{ref>fig:External_drawing}}.
+  - **Material selection** -- Figure {{ref>fig:Cross-section}} shows the different layers of our cocoon's structure. The air gap is due to the presence of the arched metallic structure in certain area of the cocoon, as shown in Figure {{ref>fig:External_drawing}}.
 We have compiled a list of Portuguese suppliers who could meet our needs: (i) F.Marques da Silva S.A for the brass panels [(Brass2022)] and the aluminum structure [(Alu2022)]; and (ii)  artnovion for the acoustic panels [(ArtnovionFoam)].
+We are still thinking about the antimicrobial textil we want to use, but Monteiro Fabrics with its MEDIFLEX collection offers interesting possibilities [(Monteiro2026)]
 <WRAP centeralign>
@@ Line 44: / Line 46: @@
 </WRAP>
-  - Detailed drawings -- Figure {{ref>fig:detailed_drawings}} shows the evolution of the design of our idea. First of all, we decided that the cocoon will not be fully closed in order to avoid feelings of claustrophobia, but also so that parents could maintain contact with their child if needed. To allow for true sensory immersion, we wanted to incorporate a chair that could vary its positions (sitting, lying down) and rotate to face the visuals. We also wanted the inside of the cocoon to be accessible for children with reduced mobility, such as those in wheelchairs.
+  - **Detailed drawings** -- Figure {{ref>fig:detailed_drawings}} shows the evolution of the design of our idea. First of all, we decided that the cocoon will not be fully closed in order to avoid feelings of claustrophobia, but also so that parents could maintain contact with their child if needed. To allow for true sensory immersion, we wanted to incorporate a chair that could vary its positions (sitting, lying down) and rotate to face the visuals. We also wanted the inside of the cocoon to be accessible for children with reduced mobility, such as those in wheelchairs.
 We are now thinking about adding small wheels to the chair so it can be easily moved when a child in a wheelchair wants to get into the cocoon. These small wheels can be locked once the chair is inside the cocoon.
 <WRAP centeralign>
 <figure fig:detailed_drawings>
-{{ :report:design_cocoon_wheelchair_dimensions.png?direct&400 |}}
+{{ :report:design_cocoon_wheelchair_dimensions.png?direct |}}
-<caption>versions of the detailed drawings</caption>
+<caption>Improved detailed drawings</caption>
+</figure>
+</WRAP>
+  - **3D Model on SolidWorks** -- Figure {{ref>fig:SolidWorks}} shows the 3D Model of the Healing Cocoon made with SolidWorks. The logo will be visible on the back of the cocoon. Furthermore, we removed the cocoon's platform because the multisensory experience will be sufficiently stimulating with sight, sound, and smell. This new design makes moving the chair easier and improves wheelchair access.
+<WRAP centeralign>
+<figure fig:SolidWorks>
+{{ :report:solidworks_pictures_together_for_wiki.png?direct&400 |}}
+<caption>Cocoon structure in SolidWorks</caption>
 </figure>
 </WRAP>
@@ Line 110: / Line 121: @@
 <table bill>
 <caption>Bill of Materials</caption>
-^ Name ^ Type ^ Supplier ^ Notes ^ Price (€) ^ Quantity ^ Total (€) ^
+^ Name ^ Type ^ Supplier ^ Notes ^  Price (€) ^ Quantity ^  Total (€) ^
-| ESP32 DevKit V1, ESP32-WROOM-32 | Processor | Farnell | Dual core 240 MHz, integrated Wi-Fi + Bluetooth. Replaces separate Wi-Fi module. |  8.75 | 1 |  8.75 |
+| ESP32 DevKit V1, ESP32-WROOM-32 | Processor | Farnell | Dual core 240 MHz, integrated Wi-Fi + Bluetooth. Replaces separate Wi-Fi module. |  8.75 |  1  |  8.75 |
-| Light Sensor, BH1750 (GY-302) | Sensor | Botnoll | I2C digital lux sensor, 0–65535 lux, 3.3 V–5 V. Better than LDR — no conversion needed. |  1.87 | 1 |  1.87 |
+| Light Sensor, BH1750 (GY-302) | Sensor | Botnroll | I2C digital lux sensor, 0–65535 lux, 3.3 V–5 V. Better than LDR — no conversion needed. |  1.87 |  1  |  1.87 |
-| CO<sub>2</sub> Sensor, MQ-135 | Sensor | Aquario | Detects CO<sub>2</sub>, NH<sub>3</sub>, alcohol, benzene, smoke. 10–1000 ppm. Analog + digital output. Compatible 5 V ESP32. Needs 20s warm-up.  |  6.09 | 1 |  6.09 |
+| CO<sub>2</sub> Sensor, MQ-135 | Sensor | Aquario | Detects CO<sub>2</sub>, NH<sub>3</sub>, alcohol, benzene, smoke. 10–1000 ppm. Analog + digital output. Compatible 5 V ESP32.  |  6.09 |  1  |  6.09 |
-| Air Humidity and Temp Sensor, DHT22 (AM2302) | Sensor | Botnoll | Humidity 0–100 % RH (±2 %) + temperature -40 °C–80 °C (±0.5 °C). Single-wire digital output. 3.3 V–5 V. |  6.96 | 1 |  6.96 |
+| Air Humidity and Temp Sensor, DHT22 (AM2302) | Sensor | Botnroll | Humidity 0–100 % RH (±2 %) + temperature -40 °C–80 °C (±0.5 °C). Single-wire digital output. 3.3 V–5 V. |  6.96 |  1  |  6.96 |
-| Scent Sprayer, Ultrasonic atomiser 5 V | Actuator | electronperdido.es | 108–110 kHz, 5 V USB. Switched via relay. Use with essential oil diluted in water. |  7.00 | 1 |  7.00 |
+| Scent Sprayer, Ultrasonic atomiser 5 V | Actuator | Botnroll | 108–110 kHz, 5 V USB. Switched via relay. Use with essential oil diluted in water. |  7.00 |  1  |  7.00 |
-| Speaker + Amplifier, MAX98357A | Actuator | Aquario | I2S Class-D amp (2.7 V–5.5 V), directly compatible with ESP32. No external DAC needed. |  11.38 | 1 |  11.38 |
+| Speaker + Amplifier, MAX98357A | Actuator | Aquario | I2S Class-D amp (2.7 V–5.5 V), directly compatible with ESP32. No external DAC needed. |  14.90 |  1  |  14.90 |
-| Relay Module, 5 V single-channel relay | Control | Ptrobotics | Controls power to the ultrasonic atomiser from ESP32 GPIO pin.  |  4.60 | 1 |  4.60 |
+| Relay Module, 5 V single-channel relay | Control | Ptrobotics | Controls power to the ultrasonic atomiser from ESP32 GPIO pin.  |  4.60 |  1  |  4.60 |
-| Power Supply, 5 V 2 A USB adapter | Power | Amazon / AliExpress / Any local shop | Powers ESP32 + peripherals. USB power bank also works for portability. |  7.26 | 1 |  7.26 |
+| Power Supply, 5 V 2 A USB adapter | Power | Any local shop | Powers ESP32 + peripherals. USB power bank also works for portability. |  7.26 |  1  |  7.26 |
-| Total Cost ||||||  53.91 |
+| Projector | Actuator | Aquario |  |  174.20 |  1  |  174.20 |
+| Total Cost ||||||  229.75 |
 </table>
 **Detailed Schematics**
-Detailed schematic diagram illustrating the precise electronic connections for the "Healing Cocoon" project. This diagram serves as the electrical blueprint, detailing how the central ESP32-WROOM-32 microcontroller is meticulously wired to interface with the various sensors (temperature, light, and air quality) and actuators (speaker and scent sprayer) essential for the system's function. By following these specific pin connections and component values, the physical interaction described in the system architecture can be realized.
+Figure {{ref>fig:detailed_schematics}} presents the detailed schematics diagram illustrating the precise electronic connections for the "Healing Cocoon" project. This diagram serves as the electrical blueprint, detailing how the central ESP32-WROOM-32 microcontroller is meticulously wired to interface with the various sensors (temperature, light, and air quality) and actuators (speaker and scent sprayer) essential for the system's function. By following these specific pin connections and component values, the physical interaction described in the system architecture can be realized.
-Figure {{ref>fig:detailed_schematics}} presents the detailed schematics diagram.
 <WRAP centeralign>
 <figure fig:detailed_schematics>
@@ Line 136: / Line 147: @@
 **Power Budget**
-Power consumption breakdown for the system's components. This table outlines the nominal and maximum values for current (intensity), voltage, and power, providing a clear overview of the electrical requirements and the total system load.
+Power consumption breakdown for the system's components. Table {{ref>power_consumption}} outlines the nominal and maximum values for current (intensity), voltage, and power, providing a clear overview of the electrical requirements and the total system load.
 <table power_consumption>
-<caption>Power Consumption Specifications</caption>
+^ Component ^  Intensity [A] ^  Intensity (max) [A] ^  Voltage [V] ^  Voltage (max) [V] ^  Power [W] ^  Power (max) [W] ^
-^ Component ^ Intensity [A] ^ Intensity (max) [A] ^ Voltage [V] ^ Voltage(max) [V] ^ Power [W] ^ Power (max) [W] ^
+| ESP32 DevKit V1 (WROOM-32) |  0.0800 |  0.500 |  3.30 |  5.00 |  0.264 |  2.50 |
-| ESP32 DevKit V1 (WROOM-32) | 0,08 | 0,5 | 3,3 | 5 | 0,264 | 2,5 |
+| BH1750 (GY-302) |  0.000140 |  0.00100 |  3.30 |  5.50 |  0.000462 |  0.00550 |
-| BH1750 (GY-302) | 0,00014 | 0,001 | 3,3 | 5,5 | 0,000462 | 0,0055 |
+| MQ-135 |  0.150 |  0.160 |  5.00 |  5.10 |  0.750 |  0.816 |
-| MQ-135 | 0,15 | 0,16 | 5 | 5,1 | 0,75 | 0,816 |
+| DHT22 (AM2302) |  0.00150 |  0.00250 |  3.30 |  5.50 |  0.00495 |  0.0138 |
-| DHT22 (AM2302) | 0,0015 | 0,0025 | 3,3 | 5,5 | 0,00495 | 0,01375 |
+| Atomizador Ultrasónico 5 V |  0.300 |  0.500 |  5.00 |  5.50 |  1.50 |  2.75 |
-| Atomizador Ultrasónico 5 V | 0,3 | 0,5 | 5 | 5,5 | 1,5 | 2,75 |
+| MAX98357A |  0.300 |  1.50 |  2.50 |  5.50 |  0.750 |  8.25 |
-| MAX98357A | 0,3 | 1,5 | 2,5 | 5,5 | 0,75 | 8,25 |
+| Módulo Relé 5 V (1 Canal) |  0.0700 |  0.0900 |  5.00 |  5.50 |  0.350 |  0.495 |
-| Módulo Relé 5 V (1 Canal) | 0,07 | 0,09 | 5 | 5,5 | 0,35 | 0,495 |
+| TOTAL |  0.902 |  2.75 | | |  3.62 |  14.8 |
-| TOTAL | 0,90164 | 2,7535 | 27,4 | 37,6 | 3,619412 | 14,83025 |
 </table>
@@ Line 187: / Line 198: @@
 == Technologies & Tools ==
 The prototype was built using simple and accessible technologies:
-  * HTML for the structure
+  * HyperText Markup Language (HTML) for the structure
-  * CSS for the design and layout
+  * Cascading Style Sheets (CSS) for the design and layout
   * JavaScript for basic interactivity
@@ Line 204: / Line 215: @@
 The staff uses a dashboard to manage the system and set up sessions, while the child interacts with a much simpler interface designed to be intuitive and calming.
-== Screens & Explanation ==
+== User Interface ==
+<color #ed1c24>First introduce here the structure of the user interface (navigation map). Do not expect the reader to find out as he reads. Do not refer to the screens as interface 1, 2, n -- use always the name of its functionality : authentication, logout, child, etc.</color>
 == Login page ==
-<color #ed1c24>Figure {{ref>fig:login}} ...</color>
+Figure {{ref>fig:login}} presents the login for our application.
 <WRAP centeralign>
 <figure fig:login>
 {{ :report:login-page.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Login interface of Healing Cocoon</caption>
 </figure>
 </WRAP>
@@ Line 227: / Line 241: @@
 == Dashboard ==
-<color #ed1c24>Figure {{ref>fig:dashboard1}} ...</color>
+Figure {{ref>fig:dashboard1}} refers the dashboard interface 1.
 <WRAP centeralign>
 <figure fig:dashboard1>
 {{ :report:dashboard-1.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Dashboard overview interface 1</caption>
 </figure>
 </WRAP>
-<color #ed1c24>Figure {{ref>fig:dashboard2}} ...</color>
+Figure {{ref>fig:dashboard2}} refers the dashboard interface 2.
 <WRAP centeralign>
 <figure fig:dashboard2>
 {{ :report:dashboard-2.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Dashboard overview interface 2</caption>
 </figure>
 </WRAP>
@@ Line 256: / Line 270: @@
 == New Session page ==
-<color #ed1c24>Figure {{ref>fig:newsession1}} ...</color>
+Figure {{ref>fig:newsession1}} presents the new session configuration 1.
 <WRAP centeralign>
 <figure fig:newsession1>
 {{ :report:newsession-1.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>New session configuration page</caption>
 </figure>
 </WRAP>
-<color #ed1c24>Figure {{ref>fig:newsession2}} ...</color>
+Figure {{ref>fig:newsession2}} presents the new session configuration 2.
 <WRAP centeralign>
 <figure fig:newsession2>
 {{ :report:newsession-2.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>New session configuration page 2</caption>
 </figure>
 </WRAP>
@@ Line 286: / Line 300: @@
 == Active Session page ==
-<color #ed1c24>Figure {{ref>fig:activesession1}} ...</color>
+Figure {{ref>fig:activesession1}} presents active session interface 1.
 <WRAP centeralign>
 <figure fig:activesession1>
 {{ :report:activesession-1.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Active session monitoring interface 1</caption>
 </figure>
 </WRAP>
-<color #ed1c24>Figure {{ref>fig:activesession2}} ...</color>
+Figure {{ref>fig:activesession2}} presents the new session configuration 2.
 <WRAP centeralign>
 <figure fig:activesession2>
 {{ :report:activesession-2.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Active session monitoring interface2 </caption>
 </figure>
 </WRAP>
@@ Line 317: / Line 331: @@
 == Child View ==
-<color #ed1c24>Figure {{ref>fig:childview1}} ...</color>
+Figure {{ref>fig:childview1}} refers to child interaction interface 1.
 <WRAP centeralign>
 <figure fig:childview1>
 {{ :report:childview-1.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Child interaction interface 1</caption>
 </figure>
 </WRAP>
-<color #ed1c24>Figure {{ref>fig:childview2}} ...</color>
+Figure {{ref>fig:childview2}} presents the new session configuration 2.
 <WRAP centeralign>
 <figure fig:childview2>
 {{ :report:childview-2.png?1000 |}}
-<caption><color #ed1c24>Add caption</color></caption>
+<caption>Child interaction interface 2</caption>
 </figure>
 </WRAP>
@@ Line 340: / Line 354: @@
 == Accessibility page ==
+Figure {{ref>fig:accessibility1}} presents the accesibility settings interface 1.
+<WRAP centeralign>
+<figure fig:accessibility1>
 {{ :report:accessibility-1.png?1000 |}}
+<caption>Accessibility settings interface 1</caption>
+</figure>
+</WRAP>
+Figure {{ref>fig:accessibility2}} presents the accesibility settings interface 2.
+<WRAP centeralign>
+<figure fig:accessibility2>
 {{ :report:accessibility-2.png?1000 |}}
+<caption>Accessibility settings interface 2</caption>
+</figure>
+</WRAP>
 This page allows staff to configure accessibility options.
@@ Line 353: / Line 382: @@
 == Settings page ==
+Figure {{ref>fig:settings1}} refers to settings interface 1.
+<WRAP centeralign>
+<figure fig:settings1>
 {{ :report:settings-1.png?1000 |}}
+<caption>System settings interface 1</caption>
+</figure>
+</WRAP>
+Figure {{ref>fig:settings2}} refers to settings interface 2.
+<WRAP centeralign>
+<figure fig:settings2>
 {{ :report:settings-2.png?1000 |}}
+<caption>System settings interface 2</caption>
+</figure>
+</WRAP>
+Figure {{ref>fig:settings3}} refers to settings interface 3.
+<WRAP centeralign>
+<figure fig:settings3>
 {{ :report:settings-3.png?1000 |}}
+<caption>System settings interface 3</caption>
+</figure>
+</WRAP>
 The settings page is used to manage general system preferences.