A control method for a multi-ECU control system based on industrial Modbus 485

By enabling Modbus RTU handshake and slave address allocation, broadcast address operation, and real-time monitoring, the problems of difficult address allocation and low communication efficiency in complex industrial control systems of the traditional Modbus protocol are solved, achieving flexible expansion and efficient communication.

CN119689960BActive Publication Date: 2026-11-17SHENZHEN SILICON MOUNTAIN TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411918570.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-12-23
Publication Date
2026-11-17
Estimated Expiration
2044-12-23

AI Technical Summary

Technical Problem

The traditional Modbus protocol suffers from difficulties in address allocation and low communication efficiency when dynamically expanding and operating multiple devices, especially in large-scale, complex industrial control systems.

Method used

By performing Modbus RTU handshake and slave address allocation during system initialization, and employing a random delay mechanism and CRC check, we ensure that each ECU obtains a unique address; we use broadcast addresses for multi-ECU operation, combined with selective control of data byte flag bits; and we monitor and handle anomalies in real time to ensure the robustness of the communication process.

Benefits of technology

It enables flexible expansion and efficient communication in complex scenarios, avoids address conflicts, improves the real-time performance and communication efficiency of the system, supports dynamic changes in the number of slave devices, and simplifies data management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119689960B_ABST
    Figure CN119689960B_ABST
Patent Text Reader

Abstract

This invention discloses an industrial Modebus 485 and multi-ECU control system, belonging to the field of industrial automation technology. The system includes: system initialization and communication interface settings; Modbus RTU handshake and slave address allocation; single-ECU hydraulic parameter read / write control; multi-ECU hydraulic merging and synchronization operation; communication status feedback and anomaly handling; and real-time monitoring and system adjustment. This industrial Modebus 485 and multi-ECU control system retains the core structure of the standard Modbus protocol while adding more functions to adapt to complex scenarios. Through handshake mechanisms and multi-ECU operation support, it is suitable for dynamically expandable and real-time control industrial scenarios. Through delay mechanisms, error handling, and hardware loopback detection, the robustness of the communication process is improved. The introduced improved mechanisms reduce learning costs and facilitate future functional expansion.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of industrial automation technology, specifically to an industrial Modebus 485 and multiple ECU control system. Background Technology

[0002] With the development of intelligent manufacturing, industrial automation systems are placing higher demands on efficient, stable, and flexible communication protocols. Among numerous industrial communication protocols, the Modbus protocol is widely used in industrial control systems, especially in process industries and discrete manufacturing, due to its simplicity, openness, and strong compatibility. The Modbus RTU protocol, as its most common implementation, has become the communication standard for many industrial equipment and control systems due to its real-time performance, stability, and ease of integration.

[0003] The basic structure of the Modbus protocol includes elements such as address identifiers, function codes, data, and CRC checksums, ensuring the reliability and accuracy of data transmission between devices. Based on this, the system can perform functions such as device status monitoring, data reading, and parameter setting. For large-scale, distributed industrial control systems, the Modbus protocol provides a simple and effective solution that can meet the needs of device interconnection and information exchange.

[0004] However, with the increasing complexity of industrial equipment, the variability of production environments, and the growing demand for control, the traditional Modbus protocol has shown its shortcomings in some complex application scenarios, especially in the following aspects: Dynamic expansion and address allocation difficulties: The Modbus protocol uses static device addresses, with each device having a fixed address. When a new device needs to be added to the system, the address configuration may need to be manually adjusted, which poses significant challenges to dynamic device management and system expansion. In some dynamically changing scenarios, the Modbus protocol does not support a flexible address reallocation mechanism, resulting in poor scalability and flexibility when facing frequently changing slave numbers and states.

[0005] Inconvenient operation of multiple devices: Although the Modbus protocol supports broadcasting, when multiple devices need to perform operations simultaneously, each device usually replies to the host computer, generating a large number of invalid responses, which leads to a decrease in communication efficiency. Especially in large-scale systems, the processing of responses and data traffic increase greatly, affecting the real-time performance of the system. Summary of the Invention

[0006] To address the shortcomings of existing technologies, this invention provides an industrial Modebus 485 and multiple ECU control system to solve the problems mentioned in the background section.

[0007] To achieve the above objectives, the present invention provides the following technical solution: In a first aspect, embodiments of the present invention provide an industrial Modebus 485 and multiple ECU control system, including: S1. Perform system initialization and communication interface settings; When the system starts up, the host computer performs Modbus RTU protocol communication initialization, including setting communication parameters such as baud rate, data bits, and stop bits; the host computer checks whether there is a device response and verifies whether the communication link is normal through CRC check code; the host computer sends a broadcast data frame to notify all ECUs to prepare to enter the next handshake process. S2. Perform Modbus RTU handshake and slave address allocation; After system initialization and communication interface settings are completed, the host computer enters the handshake phase, during which a unique slave address is assigned to each ECU via the Modbus RTU protocol. S3. Perform single ECU oil pressure parameter reading and writing control; After the handshake and address allocation are successful, each ECU performs independent oil pressure parameter read and write operations according to its slave address; S4. Perform multi-ECU hydraulic pressure merging and synchronization operation; Based on the single ECU hydraulic pressure parameter reading and writing control, it is extended to the synchronous operation of multiple ECUs to achieve overall coordinated control of hydraulic pressure; S5. Perform communication status feedback and anomaly handling; After the multi-ECU hydraulic pressure merging and synchronization operation, ensure that the status feedback of each ECU is correctly received and handle any abnormalities in a timely manner. S6. Perform real-time monitoring and system adjustments; The host computer continuously monitors the status information of all ECUs; if the oil pressure parameter of a certain ECU exceeds the normal range or the equipment malfunctions, the system automatically issues an adjustment command to ensure that the oil pressure parameter is restored to the predetermined range.

[0008] To further optimize this technical solution, in step S1, when the host computer verifies that the communication link has not been successfully established, the host computer issues a fault alarm and stops the system startup; During initialization, the hardware status of each ECU is checked to confirm whether any device is faulty, disconnected, or unresponsive.

[0009] To further optimize this technical solution, in step S2, the host computer sends a broadcast frame to inform all ECUs that they have entered the handshake mode; After receiving the broadcast frame, the ECU responds sequentially according to a preset random delay time to avoid conflicts caused by multiple devices responding simultaneously. Each ECU includes device information in its response and confirms whether it has successfully received the broadcast data.

[0010] To further optimize this technical solution, in step S2, after the host computer receives the response from each ECU, it uses a CRC check code to check whether the response of each ECU is valid and assigns a unique slave address to each ECU. The ECU that has successfully been assigned an address replies with a confirmation signal; otherwise, the handshake is retried until all ECUs have been successfully assigned addresses. The host computer precisely controls each ECU and prepares to enter the parameter control stage.

[0011] To further optimize this technical solution, in step S3, the host computer accurately reads or writes the oil pressure parameters of each ECU through the Modbus RTU protocol. Each ECU's oil pressure control parameters have a unique address to ensure that the parameters of different ECUs do not interfere with each other.

[0012] To further optimize this technical solution, in step S3, when the host computer reads the oil pressure parameter of a certain ECU, it sends a command with the target ECU address, function code 0x03 to read the parameter and the parameter address; after receiving the command, the ECU returns the corresponding oil pressure value and confirmation signal. When the host computer modifies the oil pressure parameter of an ECU, it will send function code 0x06 to write the parameter and specify the new parameter value. After receiving the write command, the ECU will adjust according to the new oil pressure value and send a response frame to the host computer. If the operation fails, the ECU returns an error code, indicating an exception.

[0013] To further optimize this technical solution, in step S4, the multi-ECU oil pressure merging and synchronous operation includes: The host computer sends operation commands to all ECUs at once via the broadcast address of the Modbus RTU protocol; Commands sent via broadcast address are responded to by all ECUs, which then execute the corresponding operations.

[0014] To further optimize this technical solution, in step S4, the host computer also selectively operates certain ECUs, rather than all ECUs, by setting specific flag bits; The host computer sends a data byte, in which the high-order flag bit indicates the ECU that needs to be operated; The host computer specifies ECU3, ECU4, and ECU6 through flag bits, meaning that the ECUs marked as the third, fourth, and sixth will adjust the oil pressure simultaneously, while the other ECUs will not respond.

[0015] To further optimize this technical solution, in step S5, after the multi-ECU oil pressure merging and synchronous operation, the system monitors the execution status of each ECU to ensure that the operation command has been executed as expected. The host computer will send feedback requests to each ECU according to the Modbus RTU protocol and obtain the execution results.

[0016] To further optimize this technical solution, in step S6, the ECU status information includes oil pressure data, equipment operating status, and fault alarms; the host computer periodically sends a query command with function code 0x03 to obtain the latest status data of each ECU and performs analysis.

[0017] In a second aspect, embodiments of the present invention provide a computer device, including a memory and a processor, wherein the memory stores a computer program, wherein: when the computer program instructions are executed by the processor, they implement the steps of an industrial modebus485 and multiple ECU control system as described in the first aspect of the present invention.

[0018] Thirdly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, wherein: when the computer program instructions are executed by a processor, they implement the steps of an industrial modebus485 and multiple ECU control system as described in the first aspect of the present invention.

[0019] Compared with the prior art, the present invention provides an industrial Modebus 485 and multiple ECU control system, which has the following advantages: This industrial Modebus485 and multi-ECU control system retains the core structure of the standard Modbus protocol while adding more functions to adapt to complex scenarios. Through handshake mechanism and multi-ECU operation support, it is suitable for industrial scenarios with dynamic expansion and real-time control. Through delay mechanism, error handling and hardware loopback detection, the robustness of the communication process is improved. While following the existing Modbus basic specifications, the introduction of improved mechanisms reduces the learning cost and facilitates future functional expansion.

[0020] Specifically, it includes the following advantages: Continuous random delay handshake mechanism: Through the random delay mechanism, the order of handshakes when multiple ECUs handshake at the same time is guaranteed, avoiding address allocation conflicts caused by synchronous transmission. It can dynamically allocate slave addresses, making the system suitable for scenarios that require frequent changes in the number or status of slaves.

[0021] Single ECU parameter read / write control: The design clearly defines the independence and consistency of parameters across different ECUs, and simplifies data management through a unified parameter address specification. It employs a clear command structure (read and write parameters), conforms to the style of the standard Modbus RTU protocol, and is easy to integrate and extend.

[0022] Multi-ECU operation: Commands can be sent to all devices at once via broadcast addresses, suitable for scenarios requiring network-wide synchronization, such as global resets or parameter standardization. The high-order flag of the data byte supports simultaneous operation of multiple specific devices, rather than a single device or network-wide broadcast, improving operational flexibility. Unselected ECUs will not reply to the host computer, reducing the amount of response data on the bus and optimizing communication efficiency. Attached Figure Description

[0023] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This invention presents a host computer and ECU topology diagram for an industrial Modebus 485 and multiple ECU control system. Figure 2 This is a flowchart illustrating an industrial Modebus 485 and multiple ECU control system proposed in this invention. Figure 3 This is a flowchart of an ECU delay handshake process for an industrial modebus485 and a multi-ECU control system proposed in this invention. Figure 4 This invention presents a single ECU control flowchart for an industrial modebus485 and multi-ECU control system. Figure 5 This invention presents a multi-ECU control flowchart for an industrial modebus 485 and multi-ECU control system. Detailed Implementation

[0025] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0026] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0027] Secondly, the term "an embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single embodiment or an embodiment selectively excluded from other embodiments. Example 1:

[0028] Reference Figures 1-5 This is the first embodiment of the present invention, which provides an industrial Modebus 485 and multiple ECU control system, characterized in that it includes: S1. Perform system initialization and communication interface settings.

[0029] During system startup, the host computer (default PC) first performs Modbus RTU protocol communication initialization, including setting communication parameters such as baud rate, data bits, and stop bits. During initialization, the host computer verifies the response of each device and checks the integrity and correctness of the communication data using a CRC checksum. If any communication error is detected during initialization, the host computer issues an alarm signal and stops system startup. This step also includes checking the hardware status of each ECU device to ensure no device is offline or malfunctioning. After completing the communication interface initialization, the host computer broadcasts a frame to notify all ECUs to enter a ready state, preparing to begin the handshake process. During communication, each data frame will include a CRC checksum to ensure that the data is not tampered with or lost during transmission.

[0030] S2. Perform Modbus RTU handshake and slave address allocation.

[0031] The host computer initiates the handshake process by sending a broadcast frame, and all ECUs respond one by one according to a random delay mechanism. Each ECU carries its device information in its response and uses a CRC check to ensure the correctness of data transmission. In this stage, the CRC checksum is used to detect the validity of each ECU's response. If the host computer receives incomplete or erroneous response data, it will re-initiate the handshake until all ECUs successfully respond and receive a unique slave address. After successful address allocation, the host computer sends an acknowledgment signal to ensure that each ECU receives its assigned address. At the end of this step, the communication connection between the host computer and each ECU is established, each device has an independent address, and is ready for the next step.

[0032] S3. Perform single ECU oil pressure parameter reading and writing control.

[0033] After each ECU is successfully assigned an address, the host computer can use the Modbus RTU protocol to read or write the hydraulic pressure parameters of each ECU. During data transmission, all command frames contain the target ECU's address, command type (e.g., function code 0x03 for read, 0x06 for write), parameter address, data value, and CRC checksum. The CRC checksum ensures that no errors occur during data transmission. If the read command sent by the host computer is executed correctly, the ECU will return the read hydraulic pressure parameters and a CRC checksum for the host computer to verify the data's validity. If the write command sent by the host computer is executed correctly, the ECU will adjust according to the new hydraulic pressure value and return an acknowledgment frame and a CRC checksum. If a communication error is detected, the ECU will send an error code, prompting the host computer to re-initiate the command. CRC checksum ensures that each data exchange is correct and complete.

[0034] S4. Perform multi-ECU oil pressure merging and synchronization operation.

[0035] During the multi-ECU operation phase, the host computer sends synchronization operation commands to all ECUs via the Modbus RTU protocol broadcast address (0x00). In this process, the host computer can also selectively operate certain ECUs using specific flag bits. For example, by setting flag bits in the data byte (such as 0xAC, indicating simultaneous control of ECU3, ECU4, and ECU6), synchronized operation of multiple ECUs can be achieved. Upon receiving the operation command, each ECU adjusts the oil pressure according to the instruction and sends an acknowledgment frame to the host computer via the Modbus protocol. All data frames must contain a CRC checksum to ensure that no errors occurred during communication. If an ECU malfunctions and cannot execute the command correctly, it returns an error code along with CRC checksum information via an error frame, prompting the host computer to resend the command or handle the error.

[0036] S5. Perform communication status feedback and exception handling.

[0037] After multi-ECU synchronous operation, the host computer needs to obtain operation feedback from each ECU to confirm whether all operations have been successfully completed. Each ECU returns a status feedback frame after completing its operation, including the execution result (e.g., success, failure) and a CRC checksum. Upon receiving these feedback frames, the host computer first performs a CRC check to verify the data's completeness and correctness. If the CRC check passes, the host computer proceeds to the next step based on the feedback. If an error occurs in the feedback (e.g., operation failure or equipment malfunction), the host computer takes appropriate exception handling measures (e.g., retrying the operation, alarm prompts, etc.) based on the returned error code. This step ensures the system can quickly respond to various abnormal situations, avoiding system failures or operational instability.

[0038] S6. Perform real-time monitoring and system adjustments.

[0039] After the system begins long-term operation, the host computer needs to periodically send query commands (e.g., function code 0x03) to each ECU to obtain real-time oil pressure parameters and equipment status. Each query command's return data includes a CRC checksum to ensure that data is not lost or tampered with during transmission. The host computer monitors the operating status of each ECU based on this real-time data and makes necessary adjustments to the system. If the oil pressure parameters of a certain ECU exceed the preset range, or if a device malfunctions, the host computer can issue an adjustment command to adjust the system status in real time, ensuring the stability and reliability of the entire oil pressure confluence system. Furthermore, CRC verification ensures the accuracy of real-time monitoring data, thereby ensuring that every adjustment and operation of the system is effectively executed. Example 2:

[0040] This embodiment also provides a computer device applicable to an industrial modebus 485 and multiple ECU control system, including a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to realize the industrial modebus 485 and multiple ECU control system as proposed in the above embodiment.

[0041] This embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements an industrial modebus 485 and multiple ECU control system as described in the above embodiments.

[0042] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0043] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0044] More specific examples (a non-exhaustive list) of computer-readable media include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0045] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0046] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A control method of a plurality of ECU control systems based on industrial modbus 485, characterized by, include: S1. Perform system initialization and communication interface settings; When the system starts up, the host computer performs Modbus RTU protocol communication initialization, including setting communication parameters such as baud rate, data bits, and stop bits; the host computer checks whether there is an ECU response and verifies whether the communication link is normal through CRC check code; the host computer sends a broadcast data frame to notify all ECUs to prepare to enter the next handshake process. S2. Perform Modbus RTU handshake and slave address allocation; After system initialization and communication interface settings are completed, the host computer enters the handshake phase, during which a unique slave address is assigned to each ECU via the ModbusRTU protocol. S3. Perform single ECU oil pressure parameter reading and writing control; After the handshake and address allocation are successful, each ECU performs independent oil pressure parameter read and write operations according to its slave address; S4. Perform multi-ECU hydraulic pressure merging and synchronization operation; Based on the single ECU hydraulic pressure parameter reading and writing control, it is extended to the synchronous operation of multiple ECUs to achieve overall coordinated control of hydraulic pressure; S5. Perform communication status feedback and anomaly handling; After the multi-ECU hydraulic pressure merging and synchronization operation, ensure that the status feedback of each ECU is correctly received and handle any abnormalities in a timely manner. S6. Perform real-time monitoring and system adjustments; The host computer continuously monitors the status information of all ECUs; if the oil pressure parameter of a certain ECU is found to be outside the normal range or the ECU is found to be faulty, the system will automatically issue an adjustment command to ensure that the oil pressure parameter is restored to the predetermined range.

2. The control method of a plurality of ECU control system based on industrial modbus 485 according to claim 1, characterized in that, In step S1, when the host computer verifies that the communication link has not been successfully established, the host computer issues a fault alarm and stops the system startup. During initialization, the hardware status of each ECU is checked to confirm whether any ECU is faulty, disconnected, or unresponsive.

3. The control method of a plurality of ECU control system based on industrial modbus 485 according to claim 1, characterized in that, In step S2, the host computer informs all ECUs to enter handshake mode by sending a broadcast data frame; After receiving the broadcast data frame, the ECU responds sequentially according to a preset random delay time to avoid conflicts caused by multiple ECUs responding simultaneously. Each ECU sends its ECU information along with a confirmation that it has successfully received the broadcast data frame.

4. The control method of a plurality of ECU control system based on industrial modbus 485 according to claim 3, characterized in that, In step S2, after the host computer receives the responses from each ECU, it uses a CRC check code to check whether the response of each ECU is valid and assigns a unique slave address to each ECU. The ECU that has successfully been assigned an address replies with a confirmation signal; otherwise, the handshake is retried until all ECUs have been successfully assigned addresses. The host computer precisely controls each ECU and prepares to enter the parameter control stage.

5. The control method of a plurality of ECU control system based on industrial modbus 485 according to claim 1, characterized in that, In step S3, the host computer accurately reads or writes the oil pressure parameters of each ECU through the Modbus RTU protocol. Each ECU's oil pressure parameters have a unique address to ensure that the parameters of different ECUs do not interfere with each other.

6. The control method for a multi-ECU control system based on industrial Modbus 485 according to claim 1, characterized in that, In step S3, when the host computer reads the oil pressure parameters of a certain ECU, it sends a command with the target ECU address, function code 0x03 to read parameters and parameter address; after receiving the command, the ECU returns the corresponding oil pressure parameters and confirmation signal. When the host computer modifies the oil pressure parameter of an ECU, it will send function code 0x06 to write the parameter and specify the new parameter value. After receiving the write command, the ECU will adjust according to the new oil pressure parameter and send a response frame to the host computer. If the operation fails, the ECU returns an error code, indicating an exception.

7. The control method for a multi-ECU control system based on industrial Modbus 485 according to claim 1, characterized in that, In step S4, the multi-ECU oil pressure merging and synchronization operation includes: The host computer sends operation commands to all ECUs at once via the broadcast address of the Modbus RTU protocol; Commands sent via broadcast address are responded to by all ECUs, which then execute the corresponding operations.

8. The control method for a multi-ECU control system based on industrial Modbus 485 according to claim 1, characterized in that, In step S4, the host computer also selectively operates certain ECUs, rather than all ECUs, by setting specific flag bits; The host computer sends a data byte, in which the high-order flag bit indicates the ECU that needs to be operated; The host computer specifies ECU3, ECU4, and ECU6 through flag bits, meaning that the ECUs marked as the third, fourth, and sixth will adjust the oil pressure simultaneously, while the other ECUs will not respond.

9. The control method for a multi-ECU control system based on industrial Modbus 485 according to claim 1, characterized in that, In step S5, after the multi-ECU hydraulic pressure merging and synchronization operation, the system monitors the execution status of each ECU to ensure that the operation command has been executed as expected. The host computer will send feedback requests to each ECU according to the Modbus RTU protocol and obtain the execution results.

10. The control method for a multi-ECU control system based on industrial Modbus 485 according to claim 1, characterized in that, In step S6, the ECU status information includes oil pressure parameters and ECU operating status; the host computer periodically sends a query command with function code 0x03 to obtain the latest status data of each ECU and performs analysis.

Citation Information

Patent Citations

  • Communication method and communication system based on Modbus RTU protocol

    CN110851392A

  • One-master multi-slave-station communication method and system based on MODBUS_RTU protocol

    CN113746712A