Bus Error Identification via Segmented Codes and Requested Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing bus protocols inadequately manage errors in bus communication systems, as they often assign the same error code to different errors or fail to assign codes for all errors, leading to unclear or unidentifiable issues, which impairs error management in industrial automation processes.
Innovation Solution
A method that enhances error management by allowing bus subscribers to detect errors, generate and transmit error messages with additional error identification, and request further information to improve error identification precision, using existing bus protocols without requiring changes, enabling the identification of multiple errors and precise error analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the bus protocol assigns the same error code to different errors, then the bus protocol maintains simplicity and compatibility, but the error identification precision deteriorates
Solution Approach 1:
The error identification is segmented into two parts: a standardized bus error code for protocol compatibility and an additional error identification field for precise error differentiation. This segmentation allows the system to maintain protocol simplicity while achieving accurate error identification.
Solution Approach 2:
The patent adds another dimension to error identification by introducing an additional error identification field beyond the standard bus error code. This dimensional expansion enables precise error differentiation without modifying the existing bus protocol structure.
2Device complexity
If the bus protocol does not assign error codes to all errors, then the bus protocol remains simple and compatible, but the error management capability deteriorates
Solution Approach 1:
The bus subscriber performs preliminary action by storing detailed error identification information locally when an error occurs. This pre-stored information is then transmitted upon request, enabling comprehensive error management without requiring the bus protocol to define error codes for all possible errors in advance.
Solution Approach 2:
The patent introduces an intermediary mechanism where the bus subscriber acts as a mediator between the error occurrence and the error identification process. The subscriber stores and manages detailed error information locally, providing it to other subscribers upon request, thus enhancing error management without protocol modification.
3Measurement precision
If additional error identification information is transmitted, then the error identification precision improves, but the communication time and data transmission increase
Solution Approach 1:
The bus subscriber pre-stores detailed error identification information in memory when an error occurs. This preliminary storage eliminates the need for real-time error analysis during communication, allowing rapid transmission of precise error information only when requested, thus minimizing communication time overhead.
4Reliability
If the bus subscriber stores and transmits detailed error identification, then the error management capability improves, but the device complexity increases
Solution Approach 1:
The bus subscriber provides self-service by automatically storing, managing, and transmitting detailed error identification information when requested. This self-service capability enhances error management without requiring external error analysis systems, and the implementation uses standard bus communication functions to minimize additional complexity.
Data Source
AI summary
A method for error management in bus communication is disclosed. A first bus subscriber generates a first bus message and writes a bus error code into a bus data area of a first bus message. The second bus subscriber identifies the error by evaluating the bus error code. The first bus subscriber stores an error identification of the error, generates a first bus message and writes the bus error code into the bus data area of the first bus message. A second bus message with a request for transmission of the error identification is generated by the second bus subscriber. A third bus message is generated by the first bus subscriber and the stored error identification is written into the bus data area of the third bus message. The second bus subscriber identifies the errors by evaluating the bus error code and the error identification.