Submodule Transfer Device for Peripheral Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In industrial automation systems, the existing methods for mapping input/output addresses of decentralized peripheral systems to main modules burden the application program with computational complexity, leading to delayed execution cycles and unnecessary copy tasks, which can result in outdated data.
Innovation Solution
A submodule with an embedded transfer device in the operating system uses a copy list with data range and direction indications to manage peripheral data exchange, shifting the copy cycle from the application program to the operating system, and includes a data interface for error detection and a priority list for time-critical data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the application program performs copy tasks for peripheral data mapping, then the data exchange between submodule and main module is achieved, but the application program execution time increases and data may become outdated
Solution Approach 1:
The copy task is extracted from the application program and transferred to the operating system. The operating system's transfer device performs the peripheral data copying based on a copy list, separating this function from the application program's responsibility and execution flow.
Solution Approach 2:
The copy list is created and stored in advance in the operating system, containing all necessary peripheral transfer data records with address range mappings. This preliminary preparation allows the transfer device to execute copies efficiently without requiring application program intervention during runtime.
2Ease of operation
If the application program performs peripheral data mapping, then address assignment between submodule and main module is achieved, but computational complexity increases
Solution Approach 1:
The computationally intensive copy task is extracted from the application program and assigned to the operating system's transfer device. The application program only needs to access the copy list structure, while the actual data copying is handled by the operating system.
Solution Approach 2:
The copy list serves as an intermediary data structure between the application program and the transfer device. It contains peripheral transfer data records that define address range mappings, allowing the application program to specify mapping requirements without directly performing the complex copying operations.
3Reliability
If copy tasks are performed in the application program cycle, then peripheral data is transferred to the main module, but the data may be outdated due to processing delays
Solution Approach 1:
The copy operation is extracted from the application program cycle and executed by the operating system's transfer device, which can operate independently and more frequently. This separation allows data to be copied without waiting for the application program cycle to complete.
Solution Approach 2:
The transfer device can perform copy tasks continuously or at more frequent intervals than the application program cycle allows. This continuous operation ensures that peripheral data is transferred to the main module more frequently, maintaining data currency without being constrained by the application program's execution timing.
Data Source
AI summary
A method for exchanging peripheral data and submodule, wherein a transfer means is embedded into an operating system of the submodule for the exchange of the peripheral data with a main module to accelerate a process of copying input/output data from a decentralized peripheral system to a superordinate level.