IO-Link Device Dual Microcontroller Protocol Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing IO-Link devices require significant software development costs and time for porting the protocol stack when switching between different microcontroller platforms, limiting their reconfigurability and increasing development time.
Innovation Solution
An IO-Link device with a transceiving module implemented in a single chip, featuring a second microcontroller coupled to a physical layer transceiver, which executes the device-side protocol stack and manages communication with a first microcontroller, decoupling protocol management from sensor/actuator types and allowing for easier reconfiguration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the protocol stack is implemented in the microcontroller of the IO-Link device, then the device can execute the IO-Link communication protocol for data transmission, but significant software development costs and time are required for porting when switching between different microcontroller platforms
Solution Approach 1:
The device is segmented into two microcontrollers: a first microcontroller dedicated to sensor/actuator control and a second microcontroller dedicated to executing the IO-Link protocol stack. This separation allows the protocol stack to be isolated in a single microcontroller, eliminating the need to recompile and adapt it across different platforms, thus reducing software development time and costs while maintaining adaptability.
Solution Approach 2:
The second microcontroller acts as an intermediary between the physical layer transceiver and the first microcontroller. It handles all protocol stack operations and communicates with the first microcontroller through a standardized interface, shielding the sensor/actuator control logic from protocol-specific complexities and platform dependencies.
2Device complexity
If a single microcontroller handles both sensor control and protocol stack execution, then device structure is simpler, but the computational load on the sensor/actuator control microcontroller increases
Solution Approach 1:
The device functionality is segmented between two microcontrollers: the first microcontroller focuses exclusively on sensor/actuator control with minimal computational requirements, while the second microcontroller handles the computationally intensive protocol stack execution. This division reduces the computational load on the sensor control microcontroller, lowering its energy consumption despite increased overall device complexity.
3Productivity
If the protocol stack is tightly coupled with the microcontroller platform, then implementation is more efficient, but switching between different microcontroller platforms requires significant software porting
Solution Approach 1:
The second microcontroller is designed to universally execute the IO-Link protocol stack independently of the first microcontroller's platform. By isolating the protocol stack in a dedicated microcontroller that communicates through a standardized interface, the system achieves platform compatibility without sacrificing implementation efficiency, as the protocol stack can be optimized once and reused across different device configurations.
Data Source
Figure 1~2
Figure 3~4
AI summary
An IO-link device (20) configured as slave for transmitting/receiving signal data with a master module (19), the IO-link device comprising : a sensor or actuator (11) configured to produce output measurement signals; a first microcontroller (21) operatively coupled to the sensor or actuator and configured to receive the measurement signals and generate data based on the measurement signals, and a transceiving module (22) which comprises a physical layer transceiver (24) configured to receive/transmit signal data from/to the master module (19), and a second microcontroller (23) operatively coupled and in bi-directional communication with the transceiver, wherein the transceiver (24) is configured to receive signal data associated with a request from the master module (19) and transmit signal data associated with the request to the second microcontroller (23) and the second microcontroller (23) is configured to receive the signal data from the transceiver and to execute a device IO-Link protocol stack, the second microcontroller being operatively coupled and in bi-directional communication with the first microcontroller (21) for the transmission of signal data associated with the request to the first microcontroller and to receive data based on measurement signals from the first controller.