Progress - Mnguyen4000/CSSE4011-Vulcan-Yellow GitHub Wiki
List the current progress made in the project (must be kept up to date, as the project progresses).
Time synchronisation data fusion algorithm prototype (Date: 28/04/2024)
Thingy52 Bluetooth Packets Signals (Date: 28/04/2024)
The code for the data structuring for the ibeacon bluetooth packets, it first sends the type of information and from which device (ranging between 1 and 2). Then it follows up with the sensor's data.
The data of the first packet of the ibeacon protocol is "VOC1"
The data of the second packet of the ibeacon protocol is "0001"
Therefore, the thingy52 is transmitting the data correctly.
Base Node Receiving Code (Date: 28/04/2024)
After adding a printk statement, we can see that the nrf52840dk board does receive and decipher the thingy52 bluetooth code fine.
Mobile nodes receive other mobile node information and relaying it (Date: 01/05/2024)
The format was swapped from iBeacon to EddyStone to allow for more information to be conveyed through a single packet.
- In this case, the information being conveyed is THINGY2, V, 2, 0002.
- Meaning that the device that the info is coming from is the THINGY52 (device 2)
- The 'V' corresponds to the type of data being in the packet, in this case is the TVOC.
- The '2' corresponds to the device which the information belongs to (in this case would be THINGY52 (device 2).
- And the last 4 characters would be the data, in this case, 0002 ppm for the TVOC.
This is an example where the THINGY52 (device 2) is relaying the info for THINGY52 (device 1)
- In this case, the information being conveyed is THINGY2, V, 1, 0234.
- Meaning that the device that the info is coming from is the THINGY52 (device 2)
- The 'V' corresponds to the type of data being in the packet, in this case is the TVOC.
- The '1' corresponds to the device which the information belongs to (in this case would be THINGY52 (device 1).
- And the last 4 characters would be the data, in this case, 0234 ppm for the TVOC.
Base Node JSON decoding and time synchronisation completed (Date: 06/05/2024)
Able to receive sensor data from NRF, process and synchronise clocks for each sensor.
Database working (Date: 07/05/2024)
Can upload json data to local database via flask.
Dashboard viewer complete (Date: 10/05/2024)
Sensor dashboard viewer with live updates complete
JSON Formatting outputting correctly and all sensors are transmitting (Date: 16/05/2024)
All the sensors transmit onto the base node correctly with calibration offset to get more accurate readings from the THINGY52 and the SEN54 is transmitting correctly.