| Both sides previous revision Previous revision Next revision | Previous revision |
| report:dvp [2026/05/14 12:00] – [Packaging] team2 | report:dvp [2026/06/14 22:14] (current) – [Smart System] team2 |
|---|
| == Logo Design == | == Logo Design == |
| |
| The Bloem logo is designed to be simple and meaningful, combining three main ideas into one icon. A flower petal, a person meditating, and the letter "B". By merging the human shape with the petal, the logo clearly shows our goal: helping people "bloom" and feel better at work. We used soft, rounded edges instead of sharp corners to make the brand feel safe and welcoming. This cleanlook works perfectly on everything from small phone screens to the side of the physical capsule, keeping the brand looking professional and modern. | The Bloem logo, shown in Figure {{ref>fig:branding_3}}, is designed to be simple and meaningful, combining three main ideas into one icon. A flower petal, a person meditating, and the letter "B". By merging the human shape with the petal, the logo clearly shows our goal: helping people "bloom" and feel better at work. We used soft, rounded edges instead of sharp corners to make the brand feel safe and welcoming. This clean look works perfectly on everything from small phone screens to the side of the physical capsule, keeping the brand looking professional and modern. |
| |
| <WRAP centeralign> | <WRAP centeralign> |
| <figure fig:branding_3.jpg> | <figure fig:branding_3> |
| {{ :report:branding_3.jpg?900 |}} | {{ :report:branding_3.jpg?900 |}} |
| <caption>Final logo </caption> | <caption>Final logo</caption> |
| </figure> | </figure> |
| </WRAP> | </WRAP> |
| == Color Palette == | == Color Palette == |
| |
| The Bloem color palette is designed to communicate a balance between professional stability and organic tranquility. By utilizing a range of desaturated, nature-inspired tones, the brand establishes a visual language that feels both sophisticated and calming. The identity relies on a specific hierarchy of colors that ensures the brand remains versatile while consistently evoking a sense of peace. | Figure {{ref>fig:branding}} gives insights of the Bloem color palette. It is designed to communicate a balance between professional stability and organic tranquility. By utilizing a range of desaturated, nature-inspired tones, the brand establishes a visual language that feels both sophisticated and calming. The identity relies on a specific hierarchy of colors that ensures the brand remains versatile while consistently evoking a sense of peace. |
| |
| The lighter shades, Plaster and Mist, serve as the brand's primary background tones. They provide a clean, airy feel that represents openness and clarity, allowing the brand to exist comfortably within modern corporate aesthetics without appearing aggressive. These are complemented by the core botanical tones, Moss and Eucalyptus, which ground the identity in its natural roots. These greens are strategically chosen to symbolize growth and renewal, creating a "natural refuge" within the visual identity that invites the audience to slow down and breathe. | The lighter shades, Plaster and Mist, serve as the brand's primary background tones. They provide a clean, airy feel that represents openness and clarity, allowing the brand to exist comfortably within modern corporate aesthetics without appearing aggressive. These are complemented by the core botanical tones, Moss and Eucalyptus, which ground the identity in its natural roots. These greens are strategically chosen to symbolize growth and renewal, creating a "natural refuge" within the visual identity that invites the audience to slow down and breathe. |
| |
| <WRAP centeralign> | <WRAP centeralign> |
| <figure fig:branding.png> | <figure fig:branding> |
| {{ :report:branding.png?900 |}} | {{ :report:branding.png?900 |}} |
| <caption>Color palette </caption> | <caption>Color palette </caption> |
| </WRAP> | </WRAP> |
| |
| == 3D model with load and stress analysis == | The final design, shown in Figure {{ref>fig:bloem_capsule.png}}, features a single entrance with two door elements on the left and right side. These panels can be smoothly opened and closed, allowing easy access for the user. A ventilation concept is introduced in the user manual to improve the airflow. The interior incorporates cork elements as well as a cushioned seating area on the floor, enabling users to either sit or stand during different relaxation activities within the capsule. The middle layer consists of hemp-based panels, which are not visible from the inside or outside. These provide effective thermal insulation and sound reduction. The outer structure is made of plywood, which ensures stability and structural integrity. The final exterior finish consists of 3D-printed bloom-shaped panels, giving the capsule a high-quality appearance and making it suitable for office environments while enhancing user experience. |
| |
| The 3D modeling and structural stress analysis are scheduled for the next phase of the project's technical development. This stage will involve a digital simulation to verify how the interlocking wooden structure (Figure {{ref>fig:structural_drawings}}) supports the weight of the hemp and cork insulation layers. By postponing the deep stress testing until the final geometry and materials are fully defined, the analysis can provide more accurate data on the capsule’s durability and safety. This future step will ensure that the organic form is structurally sound and ready for professional manufacturing. | <WRAP centeralign> |
| | <figure fig:bloem_capsule.png> |
| | {{ :report:bloem_capsule.png?400 |}} |
| | <caption>Final design</caption> |
| | </figure> |
| | </WRAP> |
| | |
| | === 3D model with load and stress analysis === |
| | To validate the structural integrity of the Bloem pod, a static Finite Element Analysis (FEA) was performed using SOLIDWORKS Simulation. FEA is a numerical method that divides a structure into thousands of small elements and calculates how each element deforms and stresses under applied loads, allowing engineers to verify safety margins before physical construction begins. |
| | The analysis was carried out on the Bloem 3D model, which captures the egg-shaped shell panels, vertical wooden ribs, base ring, and interior seat platform. |
| | |
| | Material and Setup: |
| | |
| | The pod is constructed from birch plywood, modelled with the following properties: Elastic Modulus 11 GPa, Poisson's Ratio 0.3, Density 680 kg/m³, and Yield Strength 40 MPa. All surfaces were connected using Global Bonded contact, and the base ring was fully fixed to simulate the pod resting on a flat floor. Two loads were applied simultaneously: gravitational self-weight and a 1600 N occupant force on the seat. The 1600 N design load is derived from a 100 kg occupant with a 1.6× combined factor covering dynamic sitting impact and material variability, and exceeds the European furniture standard EN 1728 which specifies 1000 N. A curvature-based high-quality mesh with second-order tetrahedral elements was used to accurately capture the curved geometry. |
| | |
| | Test 1 Results — Distributed Load: |
| | |
| | <WRAP centeralign> |
| | <figure fig:strain_distribution> |
| | {{ :report:bloem7-static_1-strain-strain1.jpg?nolink&600 |Equivalent strain distribution}} |
| | <caption>Equivalent strain (ESTRN) distribution across the Bloem pod under design loading.</caption> |
| | </figure> |
| | </WRAP> |
| | The maximum equivalent strain was 3.75 × 10⁻⁵, concentrated at the seat support region and 267 times below the elastic limit of birch plywood. The upper dome shows nearly zero strain confirming it is not load-bearing. |
| | <WRAP centeralign> |
| | <figure fig:displacement_distribution> |
| | {{ :report:bloem7-static_1-displacement-displacement1.jpg?nolink&600 |Resultant displacement distribution}} |
| | <caption>Resultant displacement (URES) distribution under occupant loading.</caption> |
| | </figure> |
| | </WRAP> |
| | The maximum displacement was 0.0388 mm, less than half the thickness of a human hair and more than 100 times below the 5 mm threshold defined in EN 1728. |
| | <WRAP centeralign> |
| | <figure fig:stress_distribution> |
| | {{ :report:bloem7-static_1-stress-stress1.jpg?nolink&600 |Von Mises stress distribution}} |
| | <caption>Von Mises stress distribution under design loading.</caption> |
| | </figure> |
| | </WRAP> |
| | The maximum von Mises stress was 0.15 MPa at the base support region, representing only 0.375% of the material yield strength of 40 MPa, with no dangerous stress concentrations anywhere in the structure. |
| | <WRAP centeralign> |
| | <figure fig:factor_of_safety> |
| | {{ :report:bloem7-static_1-factor_of_safety-factor_of_safety1.jpg?nolink&600 |Factor of Safety distribution}} |
| | <caption>Factor of Safety distribution based on the von Mises stress criterion.</caption> |
| | </figure> |
| | </WRAP> |
| | The minimum Factor of Safety was 261, more than 130 times the standard furniture target of 2.0. No region of the pod falls below a FoS of 5. |
| | ^ Metric ^ Value ^ Limit ^ Verdict ^ |
| | | Strain | 3.75 × 10⁻⁵ | ~1 × 10⁻² | PASS — 267× margin | |
| | | Displacement | 0.0388 mm | 5 mm (EN 1728) | PASS — 129× margin | |
| | | Von Mises Stress | 0.15 MPa | 40 MPa | PASS — 267× margin | |
| | | Factor of Safety | 261 | 2.0 | PASS — 130× margin | |
| | |
| | Test 2 — Worst-Case Concentrated Load: |
| | |
| | A second simulation concentrated the full 1600 N onto a 200 × 200 mm patch at the center of the seat, representing the realistic contact area of a seated person. This produces a local pressure of 0.04 N/mm² and represents the most demanding loading condition for the seat structure. The patch was created using the SOLIDWORKS Split Line tool. |
| | The maximum von Mises stress under the concentrated load was 0.10 MPa, representing 0.25% of the material yield strength of 40 MPa. Stress dissipated rapidly through the surrounding rib structure with no dangerous concentrations elsewhere in the pod. The maximum displacement was 0.0367 mm, radiating outward from the contact zone while the base remained essentially stationary, confirming correct load transfer to the floor. The maximum equivalent strain was 3.649 × 10⁻⁵, tightly localised around the contact patch and fully within the elastic regime, meaning no permanent deformation occurs even under this demanding condition. The minimum Factor of Safety was 402, exceeding the standard furniture target of 2.0 by more than 200 times. |
| | ^ Metric ^ Value ^ Limit ^ Verdict ^ |
| | | Von Mises Stress | 0.10 MPa | 40 MPa | PASS — 400× margin | |
| | | Displacement | 0.0367 mm | 5 mm (EN 1728) | PASS — 136× margin | |
| | | Strain | 3.649 × 10⁻⁵ | ~1 × 10⁻² | PASS — 274× margin | |
| | | Factor of Safety | 402 | 2.0 | PASS — 201× margin | |
| |
| ==Color palette == | ==Color palette == |
| |
| The color identity of Bloem has been meticulously curated to foster a state of physiological and mental calm. The palette is composed of desaturated, nature-inspired tones that balance professional elegance with organic tranquility as shoun in the Figure {{ref>fig:branding.png}}. | The color identity of Bloem has been meticulously curated to foster a state of physiological and mental calm. The palette is composed of desaturated, nature-inspired tones that balance professional elegance with organic tranquility as shown in the Figure {{ref>fig:branding}}. |
| |
| The strategic application of the palette is divided into three functional areas: | The strategic application of the palette is divided into three functional areas: |
| - Exterior Surfaces: The shades Plaster (off-white) and Mist (pale blue) are used for the capsule's outer shell. These tones allow the large structure to remain visually light and blend seamlessly into modern office environments without becoming a distraction. | - Exterior Surfaces: The shades Plaster (off-white) and Mist (pale blue) are used for the capsule's outer shell. These tones allow the large structure to remain visually light and blend seamlessly into modern office environments without becoming a distraction. |
| |
| - Interior Environment: The interior utilizes Moss and Eucalyptus greens. These shades are scientifically associated with stress reduction and focus. By surrounding the user with these deeper botanical tones, the capsule creates a "cocoon" effect that psychologically distances the user from the bright, high-pressure office atmosphere. | - Interior Environment: The interior utilizes Moss and Eucalyptus greens as well as plaster. These shades are scientifically associated with stress reduction and focus. By surrounding the user with these deeper botanical tones, the capsule creates a "cocoon" effect that psychologically distances the user from the bright, high-pressure office atmosphere. |
| |
| - Contrast and Accents: The shade Soot (deep charcoal) is used for structural details, hardware, and typography. This tone provides the necessary professional weight and high-end finish, ensuring that Bloem is perceived as a sophisticated tool for corporate wellness. | - Contrast and Accents: The shade Soot (deep charcoal) is used for structural details, hardware, and typography. This tone provides the necessary professional weight and high-end finish, ensuring that Bloem is perceived as a sophisticated tool for corporate wellness. |
| |
| The synergy of this palette ensures that every touchpoint reinforces the brand's promise: providing a quiet, restorative space where users can truly "bloom." | The synergy of this palette ensures that every touchpoint reinforces the brand's promise: providing a quiet, restorative space where users can truly "bloom." |
| | |
| === Smart System === | === Smart System === |
| |
| - Tablet: Acts as the user interface. | - Tablet: Acts as the user interface. |
| |
| This section describes the schematic design of the system shown in {{ref>fig:schematic}}. The diagram illustrates the integration of the main components and their interactions. The ESP32 functions as the central controller and is responsible for controlling the lighting of the capsule. A light sensor is included to detect ambient light levels and determine when a session should begin. | This section describes the schematic design of the system shown in Figure {{ref>fig:schematic}}. The diagram illustrates the integration of the main components and their interactions. The ESP32 functions as the central controller and is responsible for controlling the lighting of the capsule. A light sensor is included to detect ambient light levels and determine when a session should begin. |
| The capsule uses a 12 V RGB LED strip with four connections: a 12 V supply line and three control lines for red, green, and blue. The color and brightness are controlled using pulse-width modulation (PWM). Each control signal is generated by a digital output pin on the ESP32 and passes through a resistor and a logic-level N-channel MOSFET. This setup allows the low-voltage ESP32 to safely control the higher voltage and current required by the LED strip. | The capsule uses a 12 V RGB LED strip with four connections: a 12 V supply line and three control lines for red, green, and blue. The color and brightness are controlled using pulse-width modulation (PWM). Each control signal is generated by a digital output pin on the ESP32 and passes through a resistor and a logic-level N-channel MOSFET. This setup allows the low-voltage ESP32 to safely control the higher voltage and current required by the LED strip. |
| Power is provided by a 12 V power supply. Since the ESP32 and sensor require a stable 3.3 V supply, a buck converter is used to step down the voltage accordingly. | Power is provided by a 12 V power supply. Since the ESP32 and sensor require a stable 3.3 V supply, a buck converter is used to step down the voltage accordingly. |
| **Use Cases and User Stories** | **Use Cases and User Stories** |
| |
| The Bloem system supports a set of focused interactions that define the user experience. | The Bloem system supports a set of focused interactions that define the user experience, which are explained in Table {{ref>tab:usecases}}. |
| <WRAP 80%> | <WRAP 80%> |
| <table tab:usecases> | <table tab:usecases> |
| </WRAP> | </WRAP> |
| |
| | Table {{ref>tab:userstories}} highlights the user stories. |
| <WRAP 80%> | <WRAP 80%> |
| <table tab:userstories> | <table tab:userstories> |
| **Selection of Development Platforms and Software Components** | **Selection of Development Platforms and Software Components** |
| |
| The Bloem system requires both a front-end application and an embedded control system. Different options were considered for the tablet application. | The Bloem system requires both a front-end application and an embedded control system. Different options were considered for the tablet application shown in Table {{ref>tab:platforms}}. |
| <WRAP 80%> | <WRAP 80%> |
| <table tab:platforms> | <table tab:platforms> |
| For Bloem, a **native Android application** is considered the most suitable option. It allows direct integration with the tablet hardware, ensures smooth performance, and provides better control over the user interface and device communication. | For Bloem, a **native Android application** is considered the most suitable option. It allows direct integration with the tablet hardware, ensures smooth performance, and provides better control over the user interface and device communication. |
| |
| The selected software components are summarized below. | The selected software components are summarized in Table {{ref>tab:softwarecomponents}}. |
| |
| <WRAP 80%> | <WRAP 80%> |
| The tablet application manages all user interactions, including session booking, environment configuration, and session control. Once the user selects a session and its parameters, the application sends commands to the embedded system. | The tablet application manages all user interactions, including session booking, environment configuration, and session control. Once the user selects a session and its parameters, the application sends commands to the embedded system. |
| |
| The ESP32 receives these commands and applies them to the physical lightning component. During the session, the system maintains the selected environment and ensures that the session duration is respected through a timer mechanism. | The ESP32 receives these commands and applies them to the physical lighting component. During the session, the system maintains the selected environment and ensures that the session duration is respected through a timer mechanism. |
| |
| This architecture ensures a clear separation between user interaction and hardware control, making the system easier to develop, test, and extend. | This architecture ensures a clear separation between user interaction and hardware control, making the system easier to develop, test, and extend. |
| === Packaging === | === Packaging === |
| |
| Given the significant scale of Bloem and its commitment to sustainable logistics, the packaging is designed as a high-end, industrial Flat-Pack System. Instead of shipping a voluminous, pre-assembled structure, the capsule is divided into modular components that optimize transport space and significantly reduce the carbon footprint of delivery. This system is specifically engineered for professional B2B handling, ensuring that all large-scale vertical ribs and delicate acoustic layers are protected during transit to corporate environments. The packaging utilizes heavy-duty, reinforced recycled kraft liners with a structural internal framework that mimics the protection of traditional wooden crates used for fine furniture, yet remains entirely plastic-free and recyclable. As shown in the overview in figure {{ref>fig:packing}}, each component is nested within custom-molded pulp inserts that secure the cork tiles and hemp blocks, while the exterior of the crate serves as both a technical manual and a brand statement. Using monochromatic, eco-friendly inks, the surface displays the assembly hierarchy and the structural logic of the project, providing immediate visual guidance for the professional installation team. Centered prominently on the main face of the packaging is the brand’s core promise: "Space to breathe, room to bloom." This serves as the final touchpoint of the delivery process, signaling that once the industrial protection is removed, what remains is a sanctuary designed for professional clarity and personal growth. | Given the significant scale of Bloem and its commitment to sustainable logistics, the packaging is designed as a high-end, industrial Flat-Pack System. Instead of shipping a voluminous, pre-assembled structure, the capsule is divided into modular components that optimize transport space and significantly reduce the carbon footprint of delivery. This system is specifically engineered for professional B2B handling, ensuring that all large-scale vertical ribs and delicate acoustic layers are protected during transit to corporate environments. The packaging utilizes heavy-duty, reinforced recycled kraft liners with a structural internal framework that mimics the protection of traditional wooden crates used for fine furniture, yet remains entirely plastic-free and recyclable. As shown in Figure {{ref>fig:packing}}, each component is nested within custom-molded pulp inserts that secure the cork tiles and hemp blocks, while the exterior of the crate serves as both a technical manual and a brand statement. Using monochromatic, eco-friendly inks, the surface displays the assembly hierarchy and the structural logic of the project, providing immediate visual guidance for the professional installation team. Centered prominently on the main face of the packaging is the brand’s core promise: "Space to breathe, room to bloom." This serves as the final touchpoint of the delivery process, signaling that once the industrial protection is removed, what remains is a sanctuary designed for professional clarity and personal growth. |
| |
| <WRAP centeralign> | <WRAP centeralign 90%> |
| <figure fig:packing> | <figure fig:packing> |
| {{ :report:skaermbillede_2026-05-14_115904.png?400 |}} | {{ :report:packaging_solution.png?800 |}} |
| <caption>Packaging Solution</caption> | <caption>Packaging Solution</caption> |
| </figure> | </figure> |
| |
| ==== Prototype ==== | ==== Prototype ==== |
| | === Structure === |
| | The prototype was developed based on the principles of the 3D model. It was designed as a puzzle-like construction that could be assembled without the use of nails. During the planning phase, the intention was to create a full-scale replica of the 3D model, including all insulation layers and the wooden exterior of the capsule. However, this proved to be too ambitious within the available time and resources. As a result, the decision was made to complete the prototype using paper instead of wood for the outer shell. Consequently, a significant amount of the originally ordered materials remained unused. The prototype was built at a scale of 1:6,25. This scale was chosen because it matched the dimensions of the wood that had been purchased for the project and fits the budget of the materials for the prototype. In figure {{ref>fig:Prototype1}} below, the wooden framework of the prototype can be seen, which was constructed first. It fits together like a puzzle. The capsule’s hardware is integrated into the base, where it controls the lighting and audio system through an app. |
| |
| Refer main changes in relation to the designed solution. | |
| |
| === Structure === | <WRAP centeralign> |
| Detail and explain any changes made in relation to the designed solution, including structural downscaling, different materials, parts, etc. | <figure fig:Prototype1> |
| | {{ :report:prototype.png?400 |}} |
| | <caption>Skeleton of the capsule</caption> |
| | </figure> |
| | </WRAP> |
| | |
| | As a next step, the outer shell of the capsule was added, as shown in Figure {{ref>fig:Prototype2}}. Initially, thin wooden panels were considered to replicate the intended final design. However, during the prototyping process it became evident that the wood was difficult to bend into the required curvature. Various bending techniques were tested, but the material either failed to maintain its shape or cracked under stress. As a result, cardboard was selected as an alternative material for the prototype. The cardboard panels were attached to the wooden framework using staples, allowing the curved geometry of the capsule to be represented accurately while reducing manufacturing complexity. Although this differs from the final design, where the wall panels are intended to be inserted into the base floor and structural ribs, the prototype successfully demonstrates the overall shape, construction principle, and assembly concept of the capsule. |
| | |
| | <WRAP centeralign> |
| | <figure fig:Prototype2> |
| | {{ :report:prototype2.jpeg?400 |}} |
| | <caption>Outer shell</caption> |
| | </figure> |
| | </WRAP> |
| |
| | As a final step, an insulation layer was planned to be integrated into the prototype in order to represent the acoustic concept of the final product. Since the intended materials, namely hemp insulation and cork panels, would have significantly exceeded the available prototype budget, bubble wrap was selected as a low-cost substitute. Although it does not provide the same acoustic performance, it allows the insulation layer and wall composition of the capsule to be demonstrated visually. At the time of writing this report, the bubble wrap had not yet been delivered and therefore could not be installed. The material will be added to the prototype as soon as it becomes available. Several elements of the final design were intentionally simplified or omitted from the prototype due to limitations in time, budget, and available resources. In particular, the sliding door and its guiding mechanism, as developed in the 3D model, were not implemented. Manufacturing a functional door system would have required additional materials, increased construction complexity, and exceeded the scope of the prototype phase. Similarly, the seating area and interior cushioning were not included. The available space inside the prototype was reserved for the installation and testing of the LED lighting system, which was considered a higher priority for demonstrating the intended user experience. Despite these simplifications, the prototype successfully validates the overall dimensions, structural concept, assembly process, and visual appearance of Bloem. It therefore serves as an effective proof of concept and provides a solid basis for future iterations incorporating all planned features of the final product. |
| === Hardware === | === Hardware === |
| Detail and explain any change made in relation to the designed solution. | Regarding the prototype’s hardware, the primary focus has been to integrate a reliable and functional LED-based light source. To enable user control of the lighting in Bloem, a client–server architecture was implemented. In this setup, the ESP32 operates as a client, communicating with a server defined within the application. The client receives commands from the server, which processes user input from the app and returns responses that change the color of the LED. Figure 30 shows the data flow. |
| In case there are changes regarding the hardware, present the detailed schematics of the prototype. | |
| |
| === Software === | <WRAP centeralign> |
| Detail and explain any changes made in relation to the designed solution, including different software components, tools, platforms, etc. | <figure fig:LEDflow> |
| | {{ :report:led_flow.drawio.png?500 |}} |
| | <caption>Flow diagram of controlling LED</caption> |
| | </figure> |
| | </WRAP> |
| |
| The code developed for the prototype (smart device and apps) is described here using code flowcharts. | This architecture ensures separation between the user interface and the hardware layer, allowing for scalable and flexible control. As a result, a fully functional prototype was developed, where the lighting inside the dome can be controlled by the user through the application. |
| |
| | In Figure {{ref>fig:hardware}} below, the prototype of the LED strip is shown. A main on/off button has also been included, allowing the system to be controlled with a single switch. When the system is turned on, a green LED indicates that it is active and functioning correctly. |
| | |
| | <WRAP centeralign> |
| | <figure fig:hardware> |
| | {{ :report:hardware2.jpg?200 |}} |
| | <caption>Electrical components</caption> |
| | </figure> |
| | </WRAP> |
| | |
| | The client receives commands from the server in a simple string-based message format, for example: message = "RGB:255,0,0\n". In this case, the LED will only emit red light, as the red value is set to 255 while the green and blue values are set to 0. The client code reads the incoming message by checking if it starts with the "RGB:" prefix. It then extracts the red, green, and blue values from the string and converts them into integers, which are used to control the LED output. The code developed in the Arduino IDE is included in the Deliverables section. |
| | |
| | === Software Implementation and Code Flowcharts === |
| | |
| | The Bloem application was developed as a native Android tablet app. The app is responsible for the main user interaction, including booking a session, browsing available environments, starting or ending a session, and controlling the capsule atmosphere. This solution was chosen instead of a website because it provides a more stable experience on the tablet and allows easier integration with local functions such as sound playback and hardware communication. |
| | |
| | The prototype software is divided into two main parts. The Android app manages the interface, session logic, timer, and audio playback through a Bluetooth speaker. The ESP32 is responsible for controlling the LED lighting system. Communication between the app and the ESP32 is done through Wi-Fi using TCP commands. |
| | |
| | <WRAP centeralign> |
| | <figure fig:session_booking> |
| | {{ :report:session_booking.png?600 |}} |
| | <caption>Flow of booking a session</caption> |
| | </figure> |
| | </WRAP> |
| | |
| | |
| | In the above Figure {{ref>fig:session_booking}} the flowchart shows the session booking process. The user opens the app, selects “Book a Session”, chooses the session duration and time slot, and confirms the booking if the selected slot is available. If the slot is unavailable, the app displays an error message and allows the user to choose again. |
| | |
| | <WRAP centeralign> |
| | <figure fig:session_controle> |
| | {{ :report:sessioncontrol.png?600 |}} |
| | <caption>Session control and environment flow</caption> |
| | </figure> |
| | </WRAP> |
| | |
| | In the above Figure {{ref>fig:session_controle}} the flowchart shows the session control and environment flow. When an active booking exists, the user can choose an environment preset, such as Calm, Ocean, Rain, or Energetic. The app then manages the session timer, plays the selected sound through the Bluetooth speaker, and sends lighting commands to the ESP32. |
| | |
| | <WRAP centeralign> |
| | <figure fig:LED_controle> |
| | {{ :report:ledcontrol.png?600 |}} |
| | <caption>TCP communication used for LED control</caption> |
| | </figure> |
| | </WRAP> |
| | |
| | In the above Figure {{ref>fig:LED_controle}} the flowchart shows the TCP communication used for LED control. When the user selects a color, the app converts it into RGB values, creates a command string, connects to the ESP32, sends the command, and waits for an acknowledgement response. If the response is valid, the app updates the interface as successful; otherwise, it displays an error. |
| | |
| | Overall, the flowcharts explain how the app separates the user experience from the hardware control. The tablet application handles interaction and audio, while the ESP32 manages the physical lighting system inside the capsule. |
| === Tests & Results === | === Tests & Results === |
| |
| == Hardware tests == | == Hardware tests == |
| |
| Perform the hardware tests specified in [[report:intro#tests|Tests]]. These results are usually presented in the form of tables with two columns: Functionality and Test Result (Pass/Fail). | The hardware tests specified in [[report:intro#tests|Tests]] are presented in the table. As shown in Table {{ref>tab:FunctionalTests}}, some of the functional tests for the hardware components were not implemented in the prototype and were therefore not tested. We have tested all the features that were implemented, and these passed. We prioritized implementing the lighting system in the prototype and only simulated the acoustic functions by adding layers to the structure. |
| | |
| | However, due to limited access to appropriate materials, we did not achieve a fully soundproof capsule. In addition, the prototype does not include a functional door, which also affects acoustic performance. |
| | |
| | <WRAP box 800px center> |
| | <table tab:FunctionalTests> |
| | <caption> Results of Functional Tests </caption> |
| | ^ Functionality ^ Test Result ^ |
| | | F1 – External speech is noticeably reduced inside the capsule | Not tested| |
| | | F2 – Sound from inside is not clearly understandable outside | Not tested| |
| | | F3 – LED responds to app control | Pass | |
| | | F4 – Response time is within 1–2 seconds | Pass | |
| | | F5 – No visible flickering during operation | Pass | |
| | | F6 – Light feels comfortable for users | Pass | |
| | | F7 – Sufficient air circulation is maintained | Not tested| |
| | | F8 – Users feel comfortable while using the space | Pass | |
| | </table> |
| | </WRAP> |
| |
| == Software tests == | == Software tests == |
| |
| Software tests comprise: | **Software Tests** |
| (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); | The Bloem mobile application was tested through functional, performance, and usability tests. These tests were used to verify that the application follows the defined use cases and user stories, communicates correctly with the ESP32, and provides a simple and intuitive user experience. |
| (iii) usability tests according to the [[https://www.usability.gov/how-to-and-tools/methods/system-usability-scale.html|System Usability Scale]]. | |
| | **Functional Tests** |
| | |
| | Functional tests were based on the main use cases and user stories defined for the Bloem application. Each function was tested manually on the Android prototype to check whether the expected app response and hardware behaviour occurred correctly. |
| | |
| | <WRAP 100%> |
| | |
| | <table tab:functionaltests> |
| | <caption>Functional Test Plan</caption> |
| | ^ Test ID ^ Related Use Case / User Story ^ Test Description ^ Expected Result ^ Status ^ |
| | | FT1 | Book a session | User selects session duration and available time slot | Booking is confirmed and session is saved | Passed | |
| | | FT2 | Book a session | User selects an unavailable time slot | App displays an unavailable message and asks the user to choose again | Passed | |
| | | FT3 | Start session | User starts a booked session | Session timer starts and environment options become available | Passed | |
| | | FT4 | Choose environment preset | User selects Calm, Ocean, Rain, or Energetic | Correct sound and lighting preset is selected | Passed | |
| | | FT5 | Set LED color | User selects a light color in the app | RGB command is sent to ESP32 and LED color changes | Passed | |
| | | FT6 | Control sound setting | User selects a sound option | Audio plays through the tablet and Bluetooth speaker | Passed | |
| | | FT7 | End session | User ends the session manually or timer expires | Audio stops and LED system is reset or turned off | Passed | |
| | | FT8 | Connection error | ESP32 is unavailable during LED command | App displays an error message and does not crash | Passed | |
| | </table> |
| | </WRAP> |
| | |
| | **Performance Tests** |
| | |
| | Performance tests focus on the communication between the Android app and the ESP32, as well as the responsiveness of important app operations. Each critical operation was repeated in order to calculate the average runtime and standard deviation. |
| | |
| | |
| | <WRAP 100%> |
| | |
| | <table tab:performancetests> |
| | <caption>Performance Test Plan</caption> |
| | ^ Test ID ^ Operation ^ Data Exchanged ^ Repetitions ^ Metric Measured ^ Average Result ($\mu$ ms) ^ Standard Deviation ($\sigma$ ms) ^ |
| | | PT1 | Send LED color command to ESP32 | 21 B (RGB command + ACK) | 10 | Runtime / latency | 76.90 | 15.10 | |
| | | PT2 | Start session command | 200 B (session object write) | 10 | Runtime / latency | 192.30 | 31.80 | |
| | | PT3 | End session command | 100 B (session status update) | 10 | Runtime / latency | 180.00 | 30.00 | |
| | | PT4 | Change environment preset | 320 B (preset config read + commands) | 10 | Runtime / latency | 350.00 | 70.00 | |
| | | PT5 | App screen navigation | Negligible (internal UI state) | 10 | Runtime / responsiveness | 30.00 | 5.00 | |
| | </table> |
| | </WRAP> |
| | |
| | |
| | |
| ==== Summary ==== | ==== Summary ==== |
| //Provide here the conclusions of this chapter and make the bridge to the next chapter.// | The prototype demonstrates a functional and well-integrated system combining both hardware and software components. The structural design reflects the intended capsule form, while the LED lighting system, controlled through a client–server architecture, operates as expected. The Android application provides an intuitive user interface, enabling session booking, environment selection, and real-time control of lighting and sound. |
| | |
| | Although some elements of the design were simplified or not implemented due to limitations in time, budget, and materials, the prototype still successfully validates the core concept and key functionalities of the system. Both hardware and software testing indicate that the implemented features perform consistently and meet the defined requirements. |
| | |
| | This leads to the final discussion of the project, where the achievements, limitations, and future development will be presented. |