ideas
ideas copied to clipboard
No bullshit data acquisition library
Project description
I need a data acquisition library that has the following traits:
- it is a native library
- object oriented
- has concept of a device class. Examples of a device class are: an oscilloscope, a power meter, a spectrometer, a signal generator, a stepper motor driver and so on.
- each device driver is a shared library that can be built separately and linked to the pre-built core
Having a concept of a device class allows to hide impl details of each device under it and be able to swap the decices.
Relevant Technology
Complexity and required time
Complexity
- [x] Beginner - This project requires no or little prior knowledge of the technolog(y|ies) specified to contribute to the project
Required time (ETA)
- [x] Much work - The project will take more than a couple of weeks and serious planning is required
Categories
- [x] APIs/Backend
- [x] Developer Tooling
- [x] Extension/Plugin/Add-On
@KOLANICH Good Idea!! I can partecipate to this. I think C++ can be a good choice for this kind of project. Let me know when you think to start this!
I suspect that such a thing already exists, it is just me who is not aware of it. It is likely that libsigrok
is one of the closest libs to what. Have not tried it yet though since it is not enough modular, everything is within single tree and must be compiled together, and the build system they use is extremily shitty (autotools). I probably should raise the issues in its bug tracker.
So since I just need to wrap a single spectrometer by now + a single fake spectrometer to test the app, I'd just gonna to reinvent the wheel.
If I found some framework that worth attention, it probably should not be so hard to make my sources to use the framework, there is not so much design space to make the migration hard.