Safety-Critical Modbus Communication Protocol Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication protocols, such as Modbus RTU, are not sufficient for ensuring the reliability and integrity of safety-critical communications in safety devices, failing to meet industry standards for preventing errors and malfunctions in safety-critical scenarios.
Innovation Solution
An enhanced communication strategy using the Modbus protocol with additional security measures, including message sequence numbering, CRC validation, and session key management, ensures that safety-critical communications satisfy industry standards for reliability and integrity, even when using existing Modbus RTU infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If Modbus RTU protocol is used for communication, then ease of operation and device compatibility are improved, but reliability and integrity of safety-critical communications deteriorate
Solution Approach 1:
The communication protocol is segmented into distinct modes: non-critical exchange mode using standard Modbus RTU for routine operations, and safety-critical exchange mode with enhanced validation for safety operations. This segmentation allows each mode to be optimized independently, maintaining ease of operation for routine tasks while ensuring reliability for critical functions.
Solution Approach 2:
An intermediary validation layer is introduced between the Modbus RTU protocol and the safety device. This intermediary implements additional checks including message sequence numbering, CRC validation, and authorization verification, acting as a mediator that preserves compatibility with Modbus RTU while ensuring safety-critical communication reliability.
2Device complexity
If standard Modbus RTU protocol is used, then device complexity is reduced, but ability to prevent errors and malfunctions in safety-critical scenarios deteriorates
Solution Approach 1:
Preliminary validation actions are performed before executing safety-critical communications. The system pre-establishes authorization, validates message sequences, and checks CRC values in advance, preventing errors and malfunctions before they can affect safety device operation.
Solution Approach 2:
The protocol implements feedback mechanisms including message sequence numbering to detect out-of-order messages, CRC validation to detect transmission errors, and authorization checks to prevent unauthorized modifications. These feedback loops continuously verify communication integrity and prevent harmful errors.
3Reliability
If additional security measures are implemented in communication protocol, then reliability and integrity of safety-critical communications are improved, but device complexity increases
Solution Approach 1:
Enhanced security measures are applied locally only to safety-critical communications rather than all communications. The system distinguishes between non-critical and safety-critical message types, applying complex validation only where needed, thereby improving reliability for critical functions while minimizing overall device complexity.
Data Source
Figure 1~2
Figure 3
Figure 4~6
AI summary
An exemplary method of communicating with a safety device includes obtaining a key from the safety device that is useable for only a single communication session with the safety device. A plurality of messages are sent to the safety device during the single communication session. Each of the plurality of messages includes the obtained key, an identifier of the source of the message, an identifier of the safety device, a sequence number indicating how many of the plurality of messages preceded the message during the communication session, a command for the safety device, and at least one cyclic redundancy code (CRC) based on content of the message. A next one of the plurality of messages is sent only after confirming that the safety device has accepted a most recently sent one of the plurality of messages.