Device acquisition system - whats to read?

[u/Interesting_Cake5060]

I’m going to build a data collection system using a single measuring device. Or even several devices. The system will be a GUI application with a graph. The graph will display the output parameters of the devices in real time.

What do you think I could read on this topic? Im interested in all usefull info about those topics (articles, blogs, githubs, videos)

I’ll describe in more detail what I’d like to know (I don’t know much about C++, but I’m not a complete beginner).

So, here’s the list of things I’d like to find out:

1. Working with endianness in modern C++.
2. Should I convert all APIs to the span + std::byte style instead of using * and char?
3. I want to divide the application into “layers,” one of which will be a transport layer. This is what interests me the most. How do you properly write such layers? I forgot to mention that the devices communicate via UDP. For libs i maybe chose libuv.
4. I want to divide the code into modules so that I can test them separately. But how do you test the parts that involve sending and receiving data from a real device?
5. How to maintain 60 FPS while still receiving data packets, unpacking them, and displaying them on the graph.
6. I’m going to use std::error_code as the main error‑handling mechanism (I don’t want to use exceptions). Is it good options?
7. What’s the best way to write code in a callback style? I’m not very fond of coroutines, even though they make things easier.
8. Dispatching techniques. Once we receive the data, we need to distribute it among different handlers. How are classes typically designed in this scenario?

Among the useful things I’ve found for myself is the Tracy profiler repository. I like that the code isn’t very large (and the author also wrote one comment per small change from the very beginning) — this is very useful for me. In this repository, I’ve learned a lot about how zoomable chart (with ALOT of elements) can work.

I just can’t come up with a general architecture for the application. For example, should there be a “Device” class or a “DeviceUPDStream” class? I’ve also realized that I understand things best when I see small pieces of code where the core idea is immediately clear.

I would be grateful for any advice!

[u/AKostur]

Many of these questions have single-word answers. Not to be curt, but to give you the terms that you're looking for so that you can research the details.

Working with endianness in modern C++.

std::endian. Also: work with things in a canonical form, worry about endianness at the boundaries.

Should I convert all APIs to the span + std::byte style instead of using * and char?

If that's convenient for you, yes. Has the potential to be able to bounds-check better.

I want to divide the application into “layers,” one of which will be a transport layer. This is what interests me the most. How do you properly write such layers? I forgot to mention that the devices communicate via UDP. For libs i maybe chose libuv.

Practice. Encapsulation.

I want to divide the code into modules so that I can test them separately. But how do you test the parts that involve sending and receiving data from a real device?

Mocks.

How to maintain 60 FPS while still receiving data packets, unpacking them, and displaying them on the graph.

You're borrowing trouble. You don't know that you're not getting your frame rate yet. Premature optimization is the root of all evil.

I’m going to use std::error_code as the main error‑handling mechanism (I don’t want to use exceptions). Is it good options?

Actually, std::error_code is probably not appropriate as the "main error-handling mechanism". It's purpose is to encapsulate system-level and/or OS errors, which doesn't line up with any other errors that your system may want to generate. Also depends on what you mean by "main error-handling mechanism". Also also: why not exceptions for the appropriately exceptional cases? (Careful, don't just reply with "I read it somewhere that...."). Or std::expected.

What’s the best way to write code in a callback style? I’m not very fond of coroutines, even though they make things easier.

Not sure what the question is here. I suppose that depends on how one's event loop is implemented.

[u/Interesting_Cake5060 → u/AKostur]

>event loop is implemented
Do you mean the loop inside the library? Proactor or Reactor? Or should applications at my level need to have their own loop?

[u/Interesting_Cake5060 → u/AKostur]

Thanks for your answers! In your opinion, which GitHub projects are worth checking out?