Differences
This shows you the differences between two versions of the page.
|
iothings:proiecte:2023:configurableindoorairqualitymonitoringsystem [2024/01/15 00:59] andrei.enescu0512 [4.1 MCU code] |
iothings:proiecte:2023:configurableindoorairqualitymonitoringsystem [2024/06/30 00:59] (current) andrei.enescu0512 [Configurable Indoor Air Quality Monitoring System] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Configurable Indoor Air Quality Monitoring System====== | ======Configurable Indoor Air Quality Monitoring System====== | ||
| * Author: Andrei-George-Lucian ENESCU | * Author: Andrei-George-Lucian ENESCU | ||
| - | * Email: <andrei.enescu0512@stud.acs.upb.ro> | + | * Email: <enescu.andrei23@gmail.com> |
| - | * Master: AAC | + | * Master : AAC |
| - | * Academic year: 2023-2024 | + | * Academic year : 2023-2024 |
| - | * Source code: FIXME | + | * Source files : {{:iothings:proiecte:2023:enescu_andrei_iot_design_files.rar|download_design_files}} |
| - | * Video: FIXME | + | * Project presentation : {{:iothings:proiecte:2023:enescu_andrei_iot_project_presentation.pdf|download_project_presentation}} |
| + | * Video : [[https://drive.google.com/file/d/12pxGG4WmBNYgOO-bVUk5fnq6-0USTvlY/view?usp=sharing|view_demo_video]] | ||
| =====1. Introduction===== | =====1. Introduction===== | ||
| - | The aim of this project is to create the infrastructure for an configurable indoor air quality monitoring system. The principle behind this idea is to have multiple devices that can be placed anywhere in an enclosed area. Depending on the user’s needs, the devices can be reconfigured accordingly to meet any demand, without reprogramming them. | + | The aim of this project is to create the infrastructure for a configurable indoor air quality monitoring system. The principle behind this idea is to have multiple devices that can be placed anywhere in an enclosed area. Depending on the user’s needs, the devices can be reconfigured accordingly to meet any demand, without reprogramming them. |
| Each device is separated into 2 boards, the first one which has multiple sensors for monitoring the environment, and the second one which’s purpose is to acquire the data read by the previous board and send it to a server. | Each device is separated into 2 boards, the first one which has multiple sensors for monitoring the environment, and the second one which’s purpose is to acquire the data read by the previous board and send it to a server. | ||
| The communication between the two boards will be done via a serial protocol. Being small and maneuverable, the device can be easily placed in | The communication between the two boards will be done via a serial protocol. Being small and maneuverable, the device can be easily placed in | ||
| - | different parts of the room, and thus, it must be powered up by a battery. | + | different parts of the room, and thus, it must be powered up by a battery. The data acquired will be monitored using a custom web page. |
| + | |||
| + | Project structure: | ||
| + | |||
| + | |||
| + | {{:iothings:proiecte:2023:project_structure.jpeg?400|}} | ||
| Line 461: | Line 467: | ||
| } | } | ||
| </code> | </code> | ||
| - | |||
| - | <code C> | ||
| - | </code> | ||
| - | |||
| - | |||
| - | |||
| - | |||
| Line 725: | Line 724: | ||
| The components of the MQTT protocol are the following: | The components of the MQTT protocol are the following: | ||
| * **MQTT client** -> multiple clients can connect to network; in our case there are 2 clients, the website and the master board | * **MQTT client** -> multiple clients can connect to network; in our case there are 2 clients, the website and the master board | ||
| - | * **MQTT broker** -> it handles the communication between the MQTT clients; only 1 broker can exist, and the protocol cannot function without it; the broker is hosted locally on laptop | + | * **MQTT broker** -> it handles the communication between the MQTT clients; the protocol cannot function without it; the broker is hosted locally on laptop |
| + | |||
| + | MQTT architecture: | ||
| + | |||
| + | {{:iothings:proiecte:2023:MQTT_structure.jpeg?600|}} | ||
| The MQTT is a lightweight protocol designed for IOT devices, since the clients do not need to connect or keep tracking other clients, they only need to exchange data with the broker, using topics. A client can publish ( post data ) or subscribe ( receive data ) on a topic. | The MQTT is a lightweight protocol designed for IOT devices, since the clients do not need to connect or keep tracking other clients, they only need to exchange data with the broker, using topics. A client can publish ( post data ) or subscribe ( receive data ) on a topic. | ||
| Line 743: | Line 746: | ||
| =====5. Conclusion===== | =====5. Conclusion===== | ||
| - | In conclusion, this project’s aim was to create the infrastructure for an configurable indoor air quality monitoring system, which was successfully obtained. The advantages of using this infrastructure are that any device can be added with ease to the Dashboard, and the MQTT can support a large number ( even reach up to 1000 clients ), and the configuration of a device can be changed, requiring a minimum amount of effort. | + | In conclusion, this project’s aim was to create the infrastructure for a configurable indoor air quality monitoring system, which was successfully obtained. The advantages of using this infrastructure are that any device can be added with ease to the Dashboard, and the MQTT can support a large number ( even reach up to 1000 clients ), and the configuration of a device can be changed, requiring a minimum amount of effort. |
| =====Resources===== | =====Resources===== | ||
