-
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
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
Change Language
Last update: 16-07-2024
Development Status & Update History
🔸 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
current project Total: > 8000 work.h
🆕 There's a new Discord Server for all other projects. To join click here.
I start working again on this project later this year in 2024. In the meantime looking for sponsors to pay for the required work necessary for the successful completion of this project.
If you like this open science project, consider contributing by raising an issue, here on GitHub, or sponsoring it with a small donation. If nothing else for a cup of coffee or a slice of pizza. Thank you.
Current scientific methods use traditional dataloggers (DAQ) to collect and measure experimental data. This means collected data many times is stored in a paper format, and most of the time in a conventional CSV Excel data file. This is prone to errors and even worse, forgery of experimental data. To this date, no dataloggers can automate experimental data acquisition in a scientific experiment, making it less transparent and less trustworthy.
The overall objective for this open project is to provide open hardware electronics for sensor data measurement acquisition capable of being used in a controlled environment, such as a scientific research laboratory and also outside, on-site. These smart DAQs have the capability to generate a Unique Fingerprint ID on all sensor data measurements collected for a more Trustworthy and authentic collection of experimental data. Dubbed S.D.A.D., these devices have the required specifications and capabilities to enable real-time validation of Experimental Data Origins. For a more detailed explanation of how this smart device is used please navigate to the document (paper) currently being written "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 Repositor".
in short, the open hardware electronics being prototyped and the open firmware code being programmed by this project allows
- a scientific researcher to publish in higher-ranked scientific journals;
- scientific researchers from outside academia and sci. research enterprise or business to publish in high-ranked scientific journals;
- businesses and institutions to use collected data in cases of legal dispute and court of law;
- Expected impact of this project on Scientific Research and Businesses
- How this project contributes to advance open technologies and open solutions
- Operational mode of the Openness of the Processes, and Foreseen Contribution to Open Scientific Research
- Workplan with the envisioned timeline and milestones ( deliverables / reports / participations etc.)
- Assembly Costs and Hardware Testing
- Measurable KPIs
-
Open Hardware Electronics [
]
- Smart DAQ Specifications
- Setup and Configure the Smart DAQ
- Data Measurements
- MS Excel Power Query Tutorials on YouTube by Leila Gharani
- Jupiter Notebooks tutorials on YouTube by Roshan
- How to code in Python on YouTube by Programming with Mosh
Available here, an intelligent system that takes a single document and classifies different writing styles within the document using stylometric analysis, that is worth have a run in python.
Research Laboratories currently currently using these open software and open hardware technologies:
- ⌛ Civil Engineering Department of Federal University of Santa Maria, Brazil;
- ⌛ Civil Engineering Department of Federal University of Santa Catarina, Brazil;
- ⌛ Civil Engineering Department of Beira Interior University, Portugal;
Want to join this open science project and start using these technologies?
Send an email to [email protected] or a WhatsApp message to +32 471 632 520.
Please include in your message the link to your LinkedIn profile. Thank you.
- Wireless sensor networks for temperature and humidity monitoring within concrete structures
- Temperature and moisture monitoring in concrete structures using embedded nanotechnology/microelectromechanical systems (MEMS) sensors
- How accurate is an Arduino Ohmmeter?
- Estimating Soil Moisture and Electrical Conductivity Using Wi-Fi
- A Review of Advances in Dielectric and Electrical Conductivity Measurement in Soils Using Time Domain Reflectometry
🟢 Hardware or firmware fully tested and working
A green circle means the hardware electronics or the firmware 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.
🟡 Hardware or firmware not tested. Working capability is unknown, it may work or not.
A yellow circle means the hardware electronics or the firmware 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.
🔴 Hardware or firmware fully tested but not working.
A red circle means the hardware electronics or the firmware 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.
⌛ Hardware Design/firmware programming not started.
The hourglass means the hardware electronics or the firmware 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 important for what you are seeing or reading.
🟢 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.