CAN integrated test environment tool
By using a heterogeneous computing architecture of Raspberry Pi and communication MCU, the problems of large repetitive workload and human error in ECU CAN integration testing are solved, achieving efficient automation and accurate test results, and supporting multi-vehicle adaptation and cloud-based collaborative management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-30
- Publication Date
- 2026-03-27
AI Technical Summary
Existing CAN integration testing methods for ECUs are characterized by repetitive workload, time-consuming and labor-intensive processes, and susceptibility to human error, making it difficult to achieve efficient automation and standardization.
It adopts a heterogeneous computing architecture, using a combination of Raspberry Pi and communication MCU, and realizes data interaction through SPI bus and CAN bus. Raspberry Pi is responsible for test logic scheduling and data analysis, while communication MCU is responsible for underlying CAN communication and GPIO interrupt response, so as to realize automated testing.
It improves testing efficiency, reduces human intervention, ensures the accuracy and consistency of test results, and supports dynamic adaptation and cloud-based collaborative management of multiple vehicle models.
Smart Images

Figure CN224052574U_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The utility model relates to ECU test technical field especially relates to a CAN integration test environment frock. BACKGROUND
[0002] In motor vehicles, multiple electronic control units (ECU) are usually equipped, which realize efficient cooperation by accessing a controller area network (CAN). Component suppliers develop ECUs according to technical specifications, including ECU communication requirement specifications, network management requirement specifications, and diagnostic requirement specifications, etc. During the development process, component suppliers need to conduct comprehensive and strict network tests on ECUs according to the specifications. These tests not only cover the communication capabilities of ECUs in the CAN network, but also include their fault detection and diagnosis capabilities under different working conditions, to ensure that they can meet the high standard requirements of vehicle manufacturers.
[0003] With the parallel development of multiple vehicle models, test engineers face an increasingly growing workload. Although the CAN integration test methods of different vehicle models have high similarity, test engineers still need to repeatedly perform a large number of test tasks according to the specific requirements of each vehicle model. This repetitive work not only consumes a lot of time and effort, but also may introduce human errors due to manual operation, thereby affecting the accuracy of test results. Therefore, during the development stage of component suppliers, how to improve test efficiency and reduce human intervention through automated test tools and standardized processes has become a key link to ensure the quality of ECU development. SUMMARY
[0004] The utility model aims at overcoming the above problems existing in prior art, and provides a CAN integration test environment frock.
[0005] To achieve the above technical purposes and effects, the utility model realizes the following technical scheme:
[0006] A CAN integration test environment frock, comprising:
[0007] A database for storing test logs and test configuration information;
[0008] A Raspberry Pi connected with the database through a data line to upload test logs to the database or load test configuration information from the database;
[0009] A communication MCU connected with the Raspberry Pi through an SPI bus for bidirectional communication;
[0010] The CAN transceiver is connected with the communication MCU and the ECU through the CAN bus to realize bidirectional conversion between digital signals and differential signals.
[0011] The one input and output interface of the Raspberry Pi is connected with one input and output interface of the communication MCU, so that the communication MCU sends an interrupt signal to the Raspberry Pi.
[0012] The other input and output interface of the Raspberry Pi is connected with the MCU reset interface of the communication MCU, so that the Raspberry Pi sends an MCU reset instruction to the communication MCU.
[0013] The CAN driver is installed in the communication MCU, and the CAN transceiver is connected with the CAN driver.
[0014] The utility model discloses a beneficial effect is: using communication MCU carries out real -time control and raspberry Pi carries out the heterogeneous computing framework of high -order processing, division of labor is clear, and communication MCU is responsible for bottom CAN communication, GPIO interrupt response, and raspberry Pi is responsible for test logic scheduling, data analysis, report generation, and through SPI bus realizes bidirectional efficient data interaction between communication MCU and raspberry Pi, and the real -time and computing ability are given priority to, solve the problem of performance deficiency of traditional single MCU scheme. BRIEF DESCRIPTION OF DRAWINGS
[0015] The accompanying drawings, which are included to provide a further understanding of the utility model and are incorporated in and constitute a part of this application, illustrate embodiments of the utility model and serve to explain the utility model, and do not constitute improper limitation on the utility model. In the drawings:
[0016] Figure 1 It is the framework drawing of the CAN integrated test environment tool in the utility model;
[0017] Figure 2 It is part of the circuit of the raspberry Pi in the utility model Figure One ;
[0018] Figure 3 It is part of the circuit of the raspberry Pi in the utility model Figure Two ;
[0019] Figure 4 It is part of the circuit of the raspberry Pi in the utility model Figure Three ;
[0020] Figure 5 It is part of the circuit of the raspberry Pi in the utility model Figure Four ;
[0021] Figure 6 It is part of the circuit of the communication MCU in the utility model Figure One ;
[0022] Figure 7 is part of the communication MCU in the utility model Figure Two ;
[0023] Figure 8 is part of the communication MCU in the utility model Figure Three ;
[0024] Figure 9 is part of the communication MCU in the utility model Figure Four . DETAILED DESCRIPTION
[0025] The utility model will be described in detail below with reference to the drawings and in combination with embodiments.
[0026] As Figures 1 to 9 shown, a CAN integrated test environment tool includes a database for storing test logs and test configuration information, a Raspberry Pi, a communication MCU, and a CAN transceiver.
[0027] The Raspberry Pi is connected to the database through a data line to upload test logs to the database or load test configuration information from the database.
[0028] The communication MCU is connected to the Raspberry Pi through an SPI bus for bidirectional communication, and bidirectional high-efficiency data interaction between the communication MCU and the Raspberry Pi is realized through the SPI bus, taking into account real-time performance and computing power.
[0029] One input / output interface of the Raspberry Pi is connected to one input / output interface of the communication MCU for the communication MCU to send an interrupt signal to the Raspberry Pi.
[0030] Another input / output interface of the Raspberry Pi is connected to an MCU reset interface of the communication MCU for the Raspberry Pi to send an MCU reset instruction to the communication MCU.
[0031] The CAN transceiver is connected to the communication MCU and the ECU through a CAN bus to realize bidirectional conversion between digital signals and differential signals.
[0032] The communication MCU is installed with a CAN driver, and the CAN transceiver is connected to the CAN driver.
[0033] In this embodiment, the model of the Raspberry Pi is Compute Module 4, the model of the communication MCU is FS32K142HAT0MLHT, and the model of the CAN transceiver is TJA1044.
[0034] The CAN integrated test environment tool is based on the dual-core architecture of the communication MCU and the Raspberry Pi, combined with multiple communication interfaces (CAN, SPI), to realize automatic testing. The following is the detailed working process:
[0035] S1, test initialization and configuration,
[0036] CAN communication parameter setting: set baud rate, communication ID, etc.
[0037] Test parameter loading: Raspberry Pi reads test case library from server or locally.
[0038] S2, communication automation test case execution,
[0039] The Raspberry Pi sends data to the communication MCU through the SPI bus, and the communication MCU sends preset messages such as periodic signals and function requests to the ECU through the CAN bus.
[0040] Monitor ECU response, such as message period, signal value range, record timeout or error frame.
[0041] S3, data analysis and report generation,
[0042] The communication MCU uploads the original test data to the Raspberry Pi through the SPI bus, and the Raspberry Pi runs the analysis algorithm.
[0043] Compare ECU response with expected value, such as ISO 15765-2 timing requirements.
[0044] Automatically generate test reports, mark failed items, such as CAN ID 0x101 response timeout.
[0045] The test report is in HTML or PDF format.
[0046] The CAN integrated test environment tool has the following advantages:
[0047] (1) Dynamic adaptation to multiple vehicle models: Raspberry Pi loads automated test scripts and sends preset data to ECU through MCU.
[0048] (2) Edge computing optimization: MCU pre-processes real-time data such as filtering, and Raspberry Pi focuses on high-level analysis to reduce communication load.
[0049] (3) Cloud collaborative test management: test configuration, data, and reports are synchronized through the cloud, supporting multi-team collaboration and historical data comparison.
[0050] The above shows and describes the basic principles, main features and advantages of the present application. Those skilled in the art should understand that the present application is not limited by the above examples, and the above examples and descriptions in the specification are only to illustrate the principles of the present application. Without departing from the spirit and scope of the present application, various changes and improvements can be made to the present application, and these changes and improvements all fall within the scope of the claimed present application.
Claims
1. A CAN integration test environment fixture, characterized by, The application relates to a test system for vehicle electronic control unit (ECU), which comprises: a database for storing test logs and test configuration information; a Raspberry Pi connected with the database through a data line to upload test logs to the database or load test configuration information from the database; a communication MCU connected with the Raspberry Pi through an SPI bus for bidirectional communication; a CAN transceiver connected with the communication MCU and the ECU through a CAN bus to realize bidirectional conversion between digital signals and differential signals.
2. The CAN integration test environment fixture of claim 1, wherein: One input / output interface of the Raspberry Pi is connected with one input / output interface of the communication MCU, so that the communication MCU sends an interrupt signal to the Raspberry Pi.
3. The CAN integration test environment fixture of claim 1, wherein: Another input / output interface of the Raspberry Pi is connected with an MCU reset interface of the communication MCU, so that the Raspberry Pi sends an MCU reset instruction to the communication MCU.
4. The CAN integration test environment fixture of claim 1, wherein: A CAN driver is installed in the communication MCU, and the CAN transceiver is connected with the CAN driver.