Differences

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

--- report:intro [2026/03/26 17:34] – [1.5.3 Technical and Hardware Requirements] team5
+++ report:intro [2026/04/28 15:30] (current) – [1.8 Summary] team5
@@ Line 17: / Line 17: @@
 </table>
-=== 1.2 Motivation ===
+==== 1.2 Motivation ====
 The selection of digital art as the project’s primary theme resulted from an evaluation of various sectors, including healthcare and general well-being. While these initial areas were considered, digital art was ultimately identified as the optimal intersection for the group's diverse expertise. This theme provided a unique synergy between the creative methodologies of the design-oriented members and the technical competencies of the computer science enthusiasts. By leveraging the convergence of artistic expression and digital innovation, the project transitioned from a theoretical concept to the development of an interactive installation designed to foster meaningful public engagement.
 ==== 1.3 Problem ====
-Although modern public transit systems—particularly metropolitan rail networks—are characterized by high physical density, they frequently function as spaces of significant social isolation. This phenomenon of collective detachment is driven by two primary factors:
+Although modern public transit systems (particularly metropolitan rail networks) are characterized by high physical density, they frequently function as spaces of significant social isolation. This phenomenon of collective detachment is driven by two primary factors:
 **Passive Digital Consumption:** Passengers often utilize mobile devices as a primary strategy to mitigate the environmental stressors of crowded transit. This reliance on personal screens facilitates a transition from a shared public journey into a repetitive, solitary experience, a process often described as "digital escapism".
@@ Line 42: / Line 42: @@
 To ensure compliance with European industrial standards and safety protocols, the project must adhere to the following regulatory framework:
-**Regulatory and Standard Requirements**
+== 1.5.1 Regulatory and Standard Requirements ==
-The system shall be designed and documented in accordance with the following EU Directives:
+The system shall be designed and documented in accordance with the following European Union (EU) Directives:
 *  **Electromagnetic Compatibility Directive (2014/30/EU):** Ensuring the system does not interfere with metro signaling or communication.
@@ Line 65: / Line 65: @@
 *  **Interpersonal Connectivity:** The system must utilize shared sensory feedback to actively mitigate digital isolation and promote social interaction among passengers.
-*  **Asynchronous Narrative (Digital Storytelling):** The installation shall include a QR-based platform near exit points to facilitate the recording and playback of voice memos, creating a temporal link between passengers.
+*  **Asynchronous Narrative (Digital Storytelling):** The installation shall include a Quick Response (QR)-based platform near exit points to facilitate the recording and playback of voice memos, creating a temporal link between passengers.
 *  **Environmental Sustainability:** Material selection and power consumption must prioritize ecological impact and long-term durability in high-traffic environments.
@@ Line 75: / Line 75: @@
 *  **Sensor Integration:** The system shall utilize tactile inputs (pressure, heart rate) integrated directly into the metro’s physical infrastructure.
-*  **Real-time Feedback:** Visual (LED) and auditory (sound) outputs must respond with sub-perceptual latency to user interaction.
+*  **Real-time Feedback:** Visual (Light-Emitting Diode (LED)) and auditory (sound) outputs must respond with sub-perceptual latency to user interaction.
 *  **Structural Integration:** Existing metro handrails shall be replaced or modified with translucent housings containing embedded sensor-LED arrays.
 *  **Visual Logic:** The system must support multi-user light propagation, where individual touchpoints generate unique color pulses that travel vertically and blend on the ceiling to represent collective interaction.
+Hier is de volledig gecorrigeerde tekst voor hoofdstuk 1.6. De opmaak en de inhoud zijn exact hetzelfde gebleven, alleen de afkortingen zijn nu bij hun eerste vermelding netjes voluit geschreven (en vetgedrukt zodat je het makkelijk terugziet).
+Je kunt dit direct kopiëren en in je verslag plakken:
 ==== 1.6 Tests ====
-The goal of this project is to create a working prototype of a Distributed Smart Lighting System for public transportation. This system enhances the passenger experience by providing interactive visual feedback through addressable LEDs, triggered by touch-sensitive poles equipped with Velostat sensors. By utilizing a CAN Bus network, the system ensures high-reliability communication across the metro car, even in environments with high electromagnetic interference.
+The goal of this project is to create a working prototype of a Distributed Smart Lighting System for public transportation. This system enhances the passenger experience by providing interactive visual feedback through addressable LEDs, triggered by touch-sensitive poles equipped with Velostat sensors. By utilizing a Controller Area Network (CAN) Bus network, the system ensures high-reliability communication across the metro car, even in environments with high electromagnetic interference (EMI).
 The primary objective of this project is to deliver a functional and robust prototype. To guarantee its performance and safety in a railway-simulated environment, several tests must be conducted. Each test is outlined below, including the specific Evaluation Methodology used to verify the results.
-**Functionality Tests:**
+Functionality Tests:
-*  (FT-01)Velostat Touch Detection: Connect the sensor node to a PC and monitor the ADC output via the Serial Plotter. Apply varying hand pressures to ensure the signal changes linearly and triggers the intended software threshold.
+(FT-01) Velostat Touch Detection: Connect the sensor node to a PC and monitor the Analog-to-Digital Converter (ADC) output via the Serial Plotter. Apply varying hand pressures to ensure the signal changes linearly and triggers the intended software threshold.
-*  (FT-02)CAN Bus Communication: Implement a packet-counter script where the Pole Node sends 1,000 sequential messages. The Ceiling Node will log received IDs to calculate the Packet Delivery Ratio (PDR), with a target of $>99.9\%$.
-*  (FT-03)LED Visual Response: Trigger the sensor and visually inspect the LED strip for color accuracy ($RGB$ values), ensuring no "dead pixels" or flickering occur during the animation cycle.
-*  (FT-04)Sensitivity Calibration: Manually rotate the onboard potentiometer while applying a constant light touch. The test is successful if the trigger threshold can be adjusted to ignore vibrations while still detecting a deliberate touch.
-*  (FT-05)Power Management: Use a high-voltage laboratory power supply set to $72\text{V}$ and $110\text{V}$ DC. Use a multimeter to verify that the Buck Converter output remains at a stable $5.0\text{V } (\pm 0.1\text{V})$ under full LED load.
-**Performance Tests:**
+(FT-02) CAN Bus Communication: Implement a packet-counter script where the Pole Node sends 1000 sequential messages. The Ceiling Node will log received IDs to calculate the Packet Delivery Ratio (PDR), with a target of > 99.9 %.
-*  (PT-01)System Response Time: Record the interaction using a high-speed camera ($240\text{ FPS}$). Count the frames between the initial hand-to-sensor contact and the first LED illumination to calculate total latency (Target: $<100\text{ms}$).
+(FT-03) LED Visual Response: Trigger the sensor and visually inspect the LED strip for color accuracy (Red, Green, Blue (RGB) values), ensuring no "dead pixels" or flickering occur during the animation cycle.
-*  (PT-02)EMI Noise Resistance: Operate a brushed DC motor (simulating metro traction noise) within $10\text{ cm}$ of the CAN wiring and Velostat sensor. Monitor the system for "ghost triggers" or communication resets.
-*  (PT-03)Thermal PerformanceMethodology: Activate the LEDs at $80\%$ brightness for $4\text{ hours}$ in a non-ventilated environment. Use an infrared thermometer to measure the enclosure surface temperature every $30\text{ minutes}$ (Target: $<50\text{°C}$).
-*  (PT-04)Voltage DropMethodology: With the strip at full white brightness, measure the voltage at the $VCC$ pin of the very last LED using a multimeter. Ensure it remains above $4.7\text{V}$ to prevent color distortion.
-*  (PT-05)Long-term Durability: Use an automated mechanical actuator (or repeated manual cycles) to trigger the sensor 1,000 times. Inspect the Velostat "sandwich" for delamination or loss of electrical sensitivity.
-**Software & Simulation Tests:**
+(FT-04) Sensitivity Calibration: Manually rotate the onboard potentiometer while applying a constant light touch. The test is successful if the trigger threshold can be adjusted to ignore vibrations while still detecting a deliberate touch.
-*  (ST-01)Components Integration Simulation: Import $3D$ models of the PCBs and converters into a CAD environment (e.g., Fusion 360). Check for mechanical interferences and ensure a minimum $5\text{ mm}$ clearance between high-voltage and low-voltage traces.
+(FT-05) Power Management: Use a high-voltage laboratory power supply set to 72 V and 110 V Direct Current (DC). Use a multimeter to verify that the Buck Converter output remains at a stable 5.0 V (± 0.1 V) under full LED load.
-*  (ST-02)CAN Bus Logic Simulation: Use a network simulator or a dual-MCU breadboard setup to force "data collisions" by sending messages from two nodes simultaneously. Verify that hardware arbitration correctly prioritizes the higher-priority ID.
-*  (ST-03)Animation Algorithm: Run the LED code in a simulator (e.g., Wokwi) for $24\text{ hours}$ to check for memory leaks or buffer overflows that could lead to software hanging.
-*  (ST-04)Fault Detection: Physically disconnect the $CANH$ wire during operation. The software must detect a "Heartbeat Timeout" within $500\text{ ms}$ and switch the LEDs to a static "Safety White" mode.
-**Safety Tests:**
+Performance Tests:
-*  (SF-01)Electrical Safety: Perform a continuity test between the aluminum enclosure and the system $GND$ using a multimeter. Resistance must be $<0.1\text{ }\Omega$ to ensure proper earthing.
+(PT-01) System Response Time: Record the interaction using a high-speed camera (240 Frames Per Second (FPS)). Count the frames between the initial hand-to-sensor contact and the first LED illumination to calculate total latency (Target: < 100 ms).
-*  (SF-02)Mechanical Safety: Conduct a tactile sweep test. Run a gloved hand over all surfaces and seams of the enclosure to ensure no sharp edges or protruding screws are present.
-*  (SF-03)Fire Safety: Review the manufacturer datasheets for all cables and $3D$ filaments used. Verify they carry a $V-0$ (UL94) flammability rating or $LSHF$ (Low Smoke Halogen Free) certification.
-*  (SF-04)Vandalism Resistance: Attempt to peel the sensor off the pole using fingers. Apply a $5\text{ kg}$ impact to the sensor area and verify that the electrical housing remains intact and functional.
-*  (SF-05)Ingress Protection (IP): Lightly spray the enclosure with a fine mist of water (simulating cleaning fluids). Open the box after $5\text{ minutes}$ to inspect for any moisture ingress near the electronic components.
-**User Acceptance Testing (UAT):**
+(PT-02) EMI Noise Resistance: Operate a brushed DC motor (simulating metro traction noise) within 10 cm of the CAN wiring and Velostat sensor. Monitor the system for "ghost triggers" or communication resets.
-*  (UAT-01)Trigger Intuitiveness: Observe 5 non-technical users. Ask them to "activate the interaction" without explaining where the sensor is. More than $>80\%$ of users need to identify the pole sensor as the interaction point within 5 seconds.
+(PT-03) Thermal Performance Methodology: Activate the LEDs at 80 % brightness for 4 h in a non-ventilated environment. Use an infrared thermometer to measure the enclosure surface temperature every 30 min (Target: < 50 °C).
-*  (UAT-02)Visual Comfort (Glare Test): Users sit in a "metro seat" 1 meter away from the LEDs. Cycle through all colors at max brightness. Users report no eye strain or "dazzle" effect (blinding light).
-*  (UAT-03)Feedback Clarity: Ask users what the light animations signify (e.g., "What does the pulsing blue mean to you?"). Users correctly associate the animation with "System Active" or "Input Received".
+(PT-04) Voltage Drop Methodology: With the strip at full white brightness, measure the voltage at the Voltage at the Common Collector (VCC) pin of the very last LED using a multimeter. Ensure it remains above 4.7 V to prevent color distortion.
-*  (UAT-04)Ergonomics (Touch Height/Force): Test with users of different heights and hand strengths. All users can comfortably trigger the system regardless of their physical stature.
+(PT-05) Long-term Durability: Use an automated mechanical actuator (or repeated manual cycles) to trigger the sensor 1000 times. Inspect the Velostat "sandwich" for delamination or loss of electrical sensitivity.
+Software & Simulation Tests:
+(ST-01) Components Integration Simulation: Import 3D models of the Printed Circuit Boards (PCBs) and converters into a Computer-Aided Design (CAD) environment (e.g., Fusion 360). Check for mechanical interferences and ensure a minimum 5 mm clearance between high-voltage and low-voltage traces.
+(ST-02) CAN Bus Logic Simulation: Use a network simulator or a dual-MCU breadboard setup to force "data collisions" by sending messages from two nodes simultaneously. Verify that hardware arbitration correctly prioritizes the higher-priority ID.
+(ST-03) Animation Algorithm: Run the LED code in a simulator (e.g., Wokwi) for 24 h to check for memory leaks or buffer overflows that could lead to software hanging.
+(ST-04) Fault Detection: Physically disconnect the CAN High (CANH) wire during operation. The software must detect a "Heartbeat Timeout" within 500 ms and switch the LEDs to a static "Safety White" mode.
+Safety Tests:
+(SF-01) Electrical Safety: Perform a continuity test between the aluminum enclosure and the system Ground (GND) using a multimeter. Resistance must be < 0.1 Ω to ensure proper earthing.
+(SF-02) Mechanical Safety: Conduct a tactile sweep test. Run a gloved hand over all surfaces and seams of the enclosure to ensure no sharp edges or protruding screws are present.
+(SF-03) Fire Safety: Review the manufacturer datasheets for all cables and 3D filaments used. Verify they carry a V-0 (UL94) flammability rating or Low Smoke Halogen Free (LSHF) certification.
+(SF-04) Vandalism Resistance: Attempt to peel the sensor off the pole using fingers. Apply a 5 kg impact to the sensor area and verify that the electrical housing remains intact and functional.
+(SF-05) Ingress Protection (IP): Lightly spray the enclosure with a fine mist of water (simulating cleaning fluids). Open the box after 5 min to inspect for any moisture ingress near the electronic components.
+User Acceptance Testing (UAT):
+(UAT-01) Trigger Intuitiveness: Observe 5 non-technical users. Ask them to "activate the interaction" without explaining where the sensor is. More than > 80 % of users need to identify the pole sensor as the interaction point within 5 s.
+(UAT-02) Visual Comfort (Glare Test): Users sit in a "metro seat" 1 m away from the LEDs. Cycle through all colors at max brightness. Users report no eye strain or "dazzle" effect (blinding light).
+(UAT-03) Feedback Clarity: Ask users what the light animations signify (e.g., "What does the pulsing blue mean to you?"). Users correctly associate the animation with "System Active" or "Input Received".
+(UAT-04) Ergonomics (Touch Height/Force): Test with users of different heights and hand strengths. All users can comfortably trigger the system regardless of their physical stature.
 The testing framework defined in this chapter ensures the transition of the System from a concept to a robust prototype. By addressing EMI, thermal management, and passenger safety, these protocols guarantee that the CAN Bus architecture and Velostat sensing are reliable, scalable, and ready for real-world deployment in public transportation.
-==== Report Structure ====
+==== 1.7 Report Structure ====
 Below we can find in Table {{ref>tab_report_structure}} the main structure of the report and a short description of every chapter.
@@ Line 143: / Line 166: @@
 </WRAP>
 </table>
+==== 1.8 Summary ====
+Chapter 1 has shown us what CONNECT is about. It is a way to deal with people feeling alone when they are using the Porto Metro. We found out that the places where people wait are not really places where people connect with each other. So we made a list of what we need to do to make CONNECT work. We want to make sure that people can really talk to each other when they are using the Porto Metro.
+We are going to use technology, like digital art and special sensors to make this happen. We will make sure that it is safe and that people will like using it.
+Now that we knonw what we want to do with CONNECT we need to look at what we need to look at what other people are doing. The next chapter is going to tell us about how other people connect with each other in cities. We will look at what they did and what we can learn from them to make CONNECT really special and useful in the Porto Metro and other urban places.