Development of a frame and choice of technology for automated control of the device?

Question

Automation

There is an apparatus consisting of many physical devices. The devices are connected to the on-board network with access to a PC. For each device, there is a software control module on the PC, implemented as a plug-in (child window in the MDI application). Device control is performed in manual mode: commands are sent to physical devices through plugin controls, device responses are also displayed on plugins.
The task is to make the control of the device automatic (automated). Since there are many similar projects (various devices), the task becomes more complicated. It is necessary to develop a framework (architecture) of the control program (we are talking only about the program on a PC), suitable for multiple reuse in different projects. Hence the requirements for flexibility, scalability, etc. It is obvious that the control program must be configured by scripts. It looks attractive to use Qt+Python, although not required.
Where can I get detailed advice (including paid advice) on the development of the framework of this program and on the choice of appropriate technologies?
Options for attracting a specialist for temporary or permanent work are also being considered. One of the main requirements is design experience and perfect mastery of relevant technologies.

Answer 1

There are many options. It depends on how the interaction physically takes place and whether the protocol (documentation) is open, whether there is an API / SDK and for which platform.

Answer 2

If you consider C# and .NET then there is "extensibility" and "modularity" out of the box. It is called the Managed Extensibility Framework (MEF).
For example, we use it for the equipment polling service, when a new device appears, a separate assembly is written that implements the interface
which is already processed in the service itself.
Adding a new module is done by dropping it into the program folder and restarting. And again - all this is available as part of .NET