Master-Slave Control Architecture for Time-Synchronous Microscopy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing control systems for microscopy and similar systems face challenges in performing time-sensitive operations due to network connection limitations, where synchronous processes are hindered by the need to manage numerous communication services and software stacks, and time-sensitive networking (TSN) is not universally supported by all components.
Innovation Solution
A control system comprising a master unit and slave units with both software processing and programmable logic parts, using separate communication lines for high-level network protocols and low-level protocols respectively, allowing for time-synchronous processing without network delays, where job data is transformed and executed autonomously by slave units based on current job status information from the programmable logic part.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If network connections are used to control operable components, then communication services and data management are enabled, but time-sensitive synchronous processes cannot be performed due to network delays and software stack overhead
Solution Approach 1:
The control system is segmented into a master control unit and slave control units, each with dedicated hardware resources. Time-critical communication is handled through direct hardware connections (I2C, SPI, UART) between master and slave units, while non-time-critical communication uses the network connection. This segmentation allows simultaneous handling of both communication types without interference, resolving the contradiction between network management capability and time-sensitive synchronization.
2Loss of time
If time-sensitive networking (TSN) is implemented to improve real-time communication, then synchronous processing capability is enhanced, but all components must support this specific networking protocol which reduces compatibility
Solution Approach 1:
The master control unit acts as an intermediary that translates between different communication protocols. It receives high-level commands from the network, processes them, and generates time-critical control signals for slave units using dedicated hardware protocols (I2C, SPI, UART). This intermediary approach enables time-sensitive control without requiring slave units to support complex networking protocols, maintaining component compatibility while achieving real-time performance.
3Adaptability or versatility
If all control processing is handled by software on network-connected devices, then flexibility and programmability are improved, but time-critical response speed deteriorates due to software stack overhead
Solution Approach 1:
Each slave control unit is segmented into a microcontroller for time-critical hardware control and an FPGA for parallel processing of time-sensitive operations. The microcontroller handles protocol-specific communication (I2C, SPI, UART) with deterministic timing, while the FPGA processes data in parallel pipelines for high-speed image processing and analysis. This architectural segmentation allows both software flexibility and hardware speed to coexist.
Solution Approach 2:
Time-critical control functions are substituted from software-based network communication to hardware-based direct connections. Dedicated hardware communication interfaces (I2C, SPI, UART) replace software network stacks for time-sensitive control signals, providing deterministic microsecond-level response times. Non-time-critical functions remain software-based, maintaining programming flexibility where applicable.
Data Source
Figure 1
Figure 2
AI summary
The invention relates to control system (100) for operating a system (200) comprising an operable component (220, 230) for performing a task, the control system (100) comprising a master unit (110) and a slave unit (120, 130) assigned to the component (220, 230), the master unit (110) and the slave unit (120, 130) each comprising a software processing part (111, 121, 131) and a programmable logic part (112, 122, 132), the master unit (110), by means of its software processing part (111), being arranged to receive job data, for operating the system (200), from an external processing unit (300), transform the job data into component job data, for operating the component (220, 230) of the system (200), and send the component job data to the slave unit (120, 130) assigned to the component (220, 230), the slave unit (120, 130), by means of its software processing part (122, 132), being arranged to receive the component job data from the master unit (110), the master unit (110) being arranged to execute the job corresponding to the job data and, by means of its programmable logic part (112), being arranged to send information about a current job status to the slave unit (120, 130), and the slave unit (120, 130), by means of its programmable logic part (122, 132), being arranged to receive the information about the current job status from the master unit (110), and send information about the current job status to the software processing part (121, 131) of the slave unit (120, 130), the slave unit (120, 130), by means of its software processing part (122, 132), being arranged to execute the job corresponding to the component job data using the current job status, such a system (200) and a respective method.