-
-
Notifications
You must be signed in to change notification settings - Fork 0
Proof of Concept
Navigation | AeonLabs Main Index >> Open Scientific Research >> Real-time validation of Experimental Data Origins: A Swarm of DAQ devices able to Deliver Unique Experimental Data using Blockchain-like Fingerprint ID to a Data Repository >> Wiki >> Proof of Concept
Change Language
Last update: 17-07-2024
Development Status & Update History
These Smart DAQ devices are of type "Internet of Everything" (IoE) Smart Devices and are able to connect with each other using swarm intelligence. The main purpose is to increase data integrity and trustworthiness among DAQ devices connected and on all experimental data collected during an experiment or research project.
Experimental data collected is stored in a block format, meaning, a single block stores an individual piece of experimental data written to it, the hash of the previous block, and its own hash.
This is the main principle of operation behind blockchain technologies, to make it really difficult to modify experimental data once it’s written to a block since hashes are interconnected among each other since the beginning of an experiment, experimental campaign, and even since the beginning of a research project. Every block written references the hash of its previous block. This way, for any modification to the data stored in a block, the hash it stores changes forcing the following blocks to also indicate a change (since they must have the hash of the previous block). To modify a block a rewrite is needed on all blocks.
In everyday science at a laboratory these Smart DAQ devices are able to connect among each other, in a swarm-like manner, and when doing so, increase experimental data trustworthiness and authenticity in an experiment part of a research project or experimental campaign. Setting up a Swarm network of smart DAQ devices not only increases the quality of research results, by tagging each individual piece of experimental data collected from each individual sensor, with a unique data fingerprint ID (hash) at the exact same moment of data collection, broadcast it to other nearby smart DAQ devices and finally do data upload to a repository where a new, additional data fingerprint is added to existing ones (generated locally). This way is maintained and guarantees data collection integrity locally, from the laboratory, until the moment is received and stored in a data repository in a cloud server.
The very first prototype for a Smart Data Acquisition Device (SDAD) back in 2021
Summary of advantages of these Smart Data Acquisition Devices (S.D.A.D.)
- Ability to collect sensor measurements in real-time / LIVE and generate a unique fingerprint identification (UFPID) from and for a sensor data record;
- Ability to store sensor measurement records on a dataset (Excel CSV file, SQLite Database) using blockchain technologies;
- Ability to connect with other SDADs on the same experiment using SWARM technology to increase experimental data authenticity and trustworthiness;
- Ability to exchange data with a data repository in real-time / LIVE, for instance www.dataverse.org, autonomously and without any human intervention with the purpose of increasing experimental data authenticity and trustworthiness;
- Ability to upload individual experimental data records to a data repository in real-time / LIVE;
- Ability to connect to other SDADs on other experiments and link experimental data in a Blockchain-like manner with the purpose of increasing experimental data authenticity and trustworthiness on a scientific project or research campaign. For instance, link experimental data measurements from two or more ongoing experiments on the same project;
A document is currently being written, vis-à-vis a "paper", in an open-environment format. See the Index below to access it. Is also available as a preprint draft document at Elsevier's SSRN platform, here: https://ssrn.com/abstract=4210504, and as a MS Word .docX document with embedded 360 videos of both hardware electronics and test specimens. To access it click here.
🟢 Fully tested and working
A green circle means the hardware electronics or the programming code was fully tested, each of its functionalities and capabilities. And it can be installed in a vehicle. Keep in mind this does not mean errors won't happen. As in everything related to electronics and software, there are revisions and updates. This open hardware is no different.
💯 Fully tested & working, no improvements necessary - already being sold online
🆓 Fully Open hardware \ source code
🤪 There's better than this. don't use it
🔐 Fully closed hardware \ source code
⚡️ fully tested and working, however, it is a dangerous solution to deploy
🟡 Not tested. Working capability is unknown, it may work or not.
A yellow circle means the hardware electronics or the programming code was not fully tested, each of its functionalities and capabilities. This does not mean it not working, it simply means testing is needed before giving a green circle of approval.
🔴 Fully tested but not working.
A red circle means the hardware electronics or the programming code was fully tested, and found some kind of critical error or fault. This means the electronics or firmware code cannot be used in a vehicle.
⌛ Not started.
The hourglass means the hardware electronics or the programming hasn't started. Most likely because is waiting for the necessary test components needed for reverse engineering and also engineering of the new open solution.
🆕 New updated contents
The new icon means the link next to it was recently updated with new contents
💬 Comments on the Discussion page
The comments icon means there are useful and even new comments on the discussions page of the repository important for what you are seeing or reading.
Join the beta program to test and debug to provide feedback, ideas, modifications, suggestions, and improvements. And in return, write your own article blog or post on social media about it. See participation conditions on the Wiki.
The Beta Participant Agreement is a legal document being executed between you and AeonLabs that outlines the conditions when participating in the Beta Program.
Bug reports and pull requests are welcome on any of AeonLabs repositories. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.
- Contributing
Please make sure tests pass before committing, and add new tests for new additions.
You can get in touch with me on my LinkedIn Profile:
You can also follow my GitHub Profile to stay updated about my latest projects:
The PCB design Files I provide here for anyone to use are free. If you like this Smart Device or use it, please consider buying me a cup of coffee, a slice of pizza or a book to help me study, eat and think new PCB design files.
Make a donation on PayPal and get a TAX refund*.
Liked any of my PCB KiCad Designs? Help and Support my open work to all by becoming a GitHub sponsor.
Before proceeding to download any of AeonLabs software solutions for open-source development and/or PCB hardware electronics development make sure you are choosing the right license for your project. See AeonLabs Solutions for Open Hardware & Source Development for more information.