Differences

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

--- report:dvp [2026/04/12 18:55] – [Software] epsatisep
+++ report:dvp [2026/04/21 14:57] (current) – [Ideation] 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 36: / Line 37: @@
   - 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 49: / Line 51: @@
 <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>Detailed drawings</caption>
 </figure>
 </WRAP>
@@ Line 110: / Line 112: @@
 <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 | Botnoll | 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. Needs <color #ed1c24>20s</color> warm-up.  |  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 | 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 |
-| 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 | electronperdido.es | 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. |  11.38 |  1  |  11.38 |
-| 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 | Amazon / AliExpress / Any local shop | Powers ESP32 + peripherals. USB power bank also works for portability. |  7.26 |  1  |  7.26 |
 | Total Cost ||||||  53.91 |
 </table>
@@ Line 124: / Line 126: @@
 **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 137: @@
 **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 |  27.4 |  <color #ed1c24><del>37.6</del></color> |  3.62 |  14.8 |
-| TOTAL | 0,90164 | 2,7535 | 27,4 | 37,6 | 3,619412 | 14,83025 |
 </table>
@@ Line 187: / Line 188: @@
 == 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 205: @@
 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>caption</caption>
+<caption>Login interface of Healing Cocoon</caption>
 </figure>
 </WRAP>
@@ Line 227: / Line 231: @@
 == 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>caption</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>caption</caption>
+<caption>Dashboard overview interface 2</caption>
 </figure>
 </WRAP>
@@ Line 256: / Line 260: @@
 == 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>caption</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>caption</caption>
+<caption>New session configuration page 2</caption>
 </figure>
 </WRAP>
@@ Line 285: / Line 289: @@
 == Active Session page ==
+Figure {{ref>fig:activesession1}} presents active session interface 1.
+<WRAP centeralign>
+<figure fig:activesession1>
 {{ :report:activesession-1.png?1000 |}}
+<caption>Active session monitoring interface 1</caption>
+</figure>
+</WRAP>
+Figure {{ref>fig:activesession2}} presents the new session configuration 2.
+<WRAP centeralign>
+<figure fig:activesession2>
 {{ :report:activesession-2.png?1000 |}}
+<caption>Active session monitoring interface2 </caption>
+</figure>
+</WRAP>
 This page displays the currently active session.
@@ Line 302: / Line 321: @@
 == Child View ==
-F<color #ed1c24>igure {{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>caption</caption>
+<caption>Child interaction interface 1</caption>
-</figure
+</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>caption</caption>
+<caption>Child interaction interface 2</caption>
 </figure>
 </WRAP>
@@ Line 325: / Line 344: @@
 == 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.
+For example:
+  * Wheelchair access
+  * Removable seat
+  * Low stimulation mode
+This ensures that the system can be used by as many children as possible.
+== 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.
+It includes:
+  * Practice information
+  * Default session settings
+  * Notification options
+  * Basic data and privacy settings
+== Code flow ==
+The prototype uses a simple front-end logic.
+First, the staff logs into the system. Then, a new session is created and the selected data is stored using LocalStorage. The active session page reads this data and displays it.
+The child then interacts with the system through the child view.
+This approach makes it possible to simulate a working system without using a backend.
+== Future improvements ==
+This prototype is only a first version and can be further improved.
+Possible future improvements include:
+  * Integration with real hardware (such as projectors and scent systems)
+  * Adding a backend with a database and authentication
+  * Real-time communication between components
+  * More advanced personalization for children
 === Tests & Results ===