Fieldbus Access Interface for Coordinated Display Mode Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing device access software for fieldbus systems lacks the ability to seamlessly switch between different display modes in response to external conditions or user input, leading to inefficiencies in user interaction and adaptability.
Innovation Solution
A method and device access software that allows switching between display modes by changing parameters via an interface between the frame application and driver/application software components, enabling coordinated mode changes across a heterogeneous software environment, including touch and non-touch modes, and adapting to environmental conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If device access software integrates multiple driver- or application software components from different manufacturers, then the software can access diverse fieldbus system components, but coordinating display mode switching across these heterogeneous components becomes complex
Solution Approach 1:
The interface is designed with universal parameter structures that can accommodate multiple driver- or application software components from different manufacturers. The interface defines standardized parameter names and data types that work across heterogeneous components, allowing the frame application to switch display modes uniformly regardless of which specific drivers are integrated.
Solution Approach 2:
The invention uses parameter-based control to manage display mode switching. By defining display mode parameters with specific data types and value ranges in the interface, the system can dynamically change parameters to switch between display modes (e.g., touch mode vs. non-touch mode) without restructuring the software architecture or handling different components differently.
2Ease of operation
If the frame application switches display mode independently, then the frame application can adapt to different user conditions, but the driver- or application software components do not automatically adapt, leading to inconsistent user experience
Solution Approach 1:
The interface establishes a feedback mechanism where the frame application sends display mode parameter changes to the driver- or application software components, and the components can report their supported display modes and current state back to the frame application. This ensures all components remain synchronized and maintain a consistent user experience across the entire software system.
Solution Approach 2:
The invention merges the display mode control functionality into the existing interface between the frame application and driver- or application software components. By integrating display mode parameters into the already-established communication interface, the system achieves coordinated switching across all components without creating separate control mechanisms, ensuring consistency while maintaining ease of operation.
3Adaptability or versatility
If different driver- or application software components have different display mode capabilities, then each component can be optimized for its specific function, but achieving joint display mode switching across all components becomes difficult
Solution Approach 1:
The interface allows driver- or application software components to declare their supported display modes through parameters, enabling partial participation in display mode switching. Components that support certain display modes can be activated for those modes, while others remain inactive or use default modes. This allows joint switching to be achieved for the subset of components that support the target display mode, maintaining ease of operation while respecting individual component capabilities.
Data Source
AI summary
Described is a method for changing the display mode of a device access software with which components of a fieldbus system can be accessed. The device access software includes a frame application and at least one software component integrated into the frame application, wherein between the frame application and the at least one software component an interface is provided. The method includes switching the frame application from a first display mode into a second display mode different from the first display mode and changing at least one parameter in the software components via the relevant interface, wherein the change of the at least one parameter effects a switching of the display mode from the first display mode into the second display mode.