Programmable Controller Automatic Device Driver Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In constructing and managing automatic machines, conventional programmable controllers require manual user intervention to link device drivers, increasing costs and complexity, especially with larger systems that have multiple software modules for different device functions.
Innovation Solution
A programmable controller that connects to devices via a network, requesting and storing device identifiers and mode information to automatically acquire and link suitable software modules from a database server, eliminating the need for manual operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual user intervention is used to link device drivers, then accuracy of device configuration is improved, but work cost and complexity increase with larger systems
Solution Approach 1:
The system enables automatic self-service through plug-and-play functionality where the controller automatically detects connected devices, retrieves their identifiers via network communication, and links appropriate device drivers without requiring manual user intervention. This automation resolves the contradiction by eliminating manual configuration work while maintaining accurate device linking through systematic automatic identification and matching processes
Solution Approach 2:
Device drivers and software modules are pre-stored in the controller's storage unit along with device identifier information. When a device is connected, the controller performs preliminary matching by comparing the device's identifier against stored identifiers to automatically determine the correct driver linkage, thereby achieving accurate configuration without manual intervention
2Ease of operation
If plug-and-play function is implemented, then ease of operation is improved, but automatic driver linking cannot be achieved under specific situations
Solution Approach 1:
The system enhances automatic driver linking by introducing mode information as an additional dimension beyond basic device identifiers. Mode information specifies which function to utilize and how the device operates, enabling the controller to automatically select appropriate software modules from multiple candidates. This dimensional expansion resolves the contradiction by providing sufficient information for complete automation while maintaining plug-and-play ease of operation
Solution Approach 2:
The controller requests and receives mode information from connected devices via network communication, creating a feedback loop that provides the necessary data for automatic software module selection. This feedback mechanism enables the controller to make informed automatic decisions about driver linkage, achieving both ease of operation and complete automation
3Adaptability or versatility
If multiple software modules are provided for different device functions, then adaptability is improved, but determination of suitable module increases complexity
Solution Approach 1:
Mode information is stored locally in the storage unit alongside device identifier information, creating localized quality data that specifies which software module is suitable for each device function. This local quality information enables the controller to automatically determine the appropriate module for each specific device connection, achieving both high adaptability for multiple device functions and simplified selection without increasing overall system complexity
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A programmable controller (10) of an embodiment is a programmable controller (10) connected to a device (21 to 23) to be a controlled object via a network (30), and includes a control unit (70) that requests the device (21 to 23) to notify an identifier of the device (21 to 23) and mode information via the network (30), the mode information defining a utilized function and an operation method of the device (21 to 23); and a storage unit (71) that stores the identifier and the mode information notified by the device (21 to 23) via the network (30) in response to the request.