A fault injection test fixture

By designing a fault injection test fixture, and utilizing a fault simulation module, a self-testing MCU, and a Raspberry Pi, we can achieve multi-channel and multi-type fault injection and real-time monitoring of ECUs. This solves the problem that traditional tools cannot monitor in real time, and improves the accuracy and reliability of the test.

CN224287073UActive Publication Date: 2026-05-26NANJING WEISIKE AUTOMOBILE TECH CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Utility models(China)
Current Assignee / Owner
NANJING WEISIKE AUTOMOBILE TECH CO LTD
Filing Date
2025-05-30
Publication Date
2026-05-26

AI Technical Summary

Technical Problem

Traditional fault injection tools lack real-time monitoring capabilities and cannot effectively verify the response behavior of ECUs under complex fault conditions.

Method used

A fault injection test fixture was designed, including a fault simulation module, a self-test MCU, a Raspberry Pi, and a power module. It achieves bidirectional communication through SPI bus and 485 bus. Combined with the self-test circuit and power module, it enables real-time monitoring of the fault simulation module and multi-channel, multi-type fault injection.

Benefits of technology

It enables real-time monitoring of multi-channel and multi-type fault injection in ECUs, improving the accuracy and reliability of testing, reducing manual intervention, and enhancing the automation and safety of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN224287073U_ABST
    Figure CN224287073U_ABST
Patent Text Reader

Abstract

This utility model relates to a fault injection test fixture, including a fault simulation module, a self-test MCU, a Raspberry Pi, and a power supply module. The fault simulation module is connected to an ECU; the self-test MCU is connected to the fault simulation module through a self-test circuit; the Raspberry Pi's SPI6 interface and the self-test MCU's SPI2 interface are bidirectionally connected via an SPI bus; the Raspberry Pi's UART4 interface is connected to an external 485 transceiver via a 485 bus; the 485 transceiver is connected to the serial communication interface of the fault simulation module and the UART2 interface of the self-test MCU via the 485 bus; the power supply module is electrically connected to the self-test MCU, the self-test circuit, the Raspberry Pi, and the fault simulation module. The beneficial effects are: by the collaborative work of the Raspberry Pi, the self-test MCU, the self-test circuit, and the fault simulation module, control and real-time monitoring of the fault simulation module can be achieved, meeting the needs of multi-channel, multi-type fault injection and improving the accuracy and reliability of the test.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This utility model relates to the field of ECU fault testing technology, and in particular to a fault injection testing fixture. Background Technology

[0002] Traditional fault injection tools lack real-time monitoring capabilities and cannot effectively verify the response behavior of ECUs under complex fault conditions. Therefore, developing a fault injection fixture with real-time monitoring capabilities is of great significance. Utility Model Content

[0003] The purpose of this invention is to overcome the above-mentioned problems in the existing technology and provide a fault injection test fixture.

[0004] To achieve the above-mentioned technical objectives and effects, this utility model is implemented through the following technical solution:

[0005] A fault injection test fixture, comprising:

[0006] A fault simulation module, which is connected to the ECU;

[0007] The self-testing MCU is connected to the fault simulation module via a self-testing circuit.

[0008] The Raspberry Pi has its SPI6 interface and the SPI2 interface of the self-test MCU connected bidirectionally via the SPI bus. The Raspberry Pi's UART4 interface is connected to an external 485 transceiver via the 485 bus. The 485 transceiver is connected to the serial communication interface of the fault simulation module and the UART2 interface of the self-test MCU via the 485 bus.

[0009] The power module is electrically connected to the self-test MCU, the self-test circuit, the Raspberry Pi, and the fault simulation module.

[0010] The Raspberry Pi's GPIO interface is connected to the hard reset interface of the self-test MCU via a data cable.

[0011] The Raspberry Pi's signal ground interface is electrically connected to the fault simulation block.

[0012] The self-test circuit includes a multiplexer and a constant current source. The multiplexer is connected to the fault simulation block, the GPIO interface of the self-test MCU, and the AD interface of the self-test MCU via cables. The constant current source is connected to the multiplexer via cables.

[0013] The power module includes a BUCK DC-DC 12V output circuit, a BUCK DC-DC 5V output circuit, a CM4 3.3V output circuit, and a 12V REF interface. The BUCK DC-DC 12V output circuit powers the self-test circuit, the BUCK DC-DC 5V output circuit powers the Raspberry Pi and the self-test MCU, the CM4 3.3V output circuit powers the Ethernet LED module through the Raspberry Pi, and the 12V REF interface is connected to the 12V Output interface of the fault simulation module.

[0014] The beneficial effects of this invention are: by working together with the Raspberry Pi, self-test MCU, self-test circuit, and fault simulation module, the fault simulation module can be controlled and monitored in real time to meet the needs of multi-channel and multi-type fault injection, and improve the accuracy and reliability of testing. Attached Figure Description

[0015] The accompanying drawings, which are included to provide a further understanding of the present invention and form part of this application, illustrate exemplary embodiments of the present invention and, together with the description thereof, serve to explain the present invention and do not constitute an undue limitation thereof. In the drawings:

[0016] Figure 1 This is a schematic diagram of the framework of some mechanisms of the fault injection test fixture in this utility model;

[0017] Figure 2 This is a portion of the Raspberry Pi circuitry in this utility model. Figure 1 ;

[0018] Figure 3 This is a portion of the Raspberry Pi circuitry in this utility model. Figure 2 ;

[0019] Figure 4 This is a portion of the Raspberry Pi circuitry in this utility model. Figure 3 ;

[0020] Figure 5 This is a portion of the Raspberry Pi circuitry in this utility model. Figure 4 ;

[0021] Figure 6 This is the circuit diagram of the self-testing MCU in this utility model;

[0022] Figure 7 This is a part of the self-test circuit in this utility model. Figure 1 ;

[0023] Figure 8 This is a part of the self-test circuit in this utility model. Figure 2 ;

[0024] Figure 9 This is a part of the self-test circuit in this utility model. Figure 3 ;

[0025] Figure 10 This is a part of the self-test circuit in this utility model. Figure 4 ;

[0026] Figure 11 This is a part of the self-test circuit in this utility model. Figure 5 ;

[0027] Figure 12 This is the circuit diagram of the fault simulation module in this utility model;

[0028] Figure 13 This is a schematic diagram of the circuit module framework in this utility model;

[0029] Figure 14 This is a partial circuit diagram of the circuit module in this utility model. Detailed Implementation

[0030] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0031] like Figures 1 to 5 As shown, a fault injection test fixture includes a fault simulation module, a self-test MCU, a Raspberry Pi, and a power module.

[0032] The fault simulation module is connected to the ECU. After receiving commands from the Raspberry Pi, the fault simulation module injects faults into the ECU through components such as relays and switches. These faults include various types such as short circuit to ground, short circuit to power supply, abnormal resistance, and communication abnormality. The fault simulation module also enables multi-channel fault injection.

[0033] The self-testing MCU is connected to the fault simulation module through a self-testing circuit. The self-testing MCU and the self-testing circuit work together to monitor the status of the fault simulation module in real time.

[0034] The self-test circuit includes a multiplexer and a constant current source. The multiplexer is connected to the fault simulation block, the GPIO interface of the self-test MCU, and the AD interface of the self-test MCU via cables. The constant current source is connected to the multiplexer via cables.

[0035] The Raspberry Pi's SPI6 interface and the SPI2 interface of the self-test MCU are bidirectionally connected via the SPI bus. The Raspberry Pi's UART4 interface is connected to an external 485 transceiver via the 485 bus. The 485 transceiver is connected to the serial communication interface of the fault simulation module and the UART2 interface of the self-test MCU via the 485 bus. The Raspberry Pi's GPIO interface is connected to the hard reset interface of the self-test MCU via a data line. The Raspberry Pi's signal ground interface is electrically connected to the fault simulation block.

[0036] In this embodiment: the Raspberry Pi is a Compute Module 4, the self-test MCU is a FS32K144HAT0MLLT, the multiplexers are DG4051EEY and DG408LE, the constant current source is implemented based on the VI conversion circuit, and the main components are voltage regulators of model MCP6002.

[0037] How Raspberry Pi works:

[0038] (1) After the Raspberry Pi system starts up, it first starts the self-test MCU and self-test circuit through the SPI bus.

[0039] (2) After the self-test MCU and self-test circuit are started, they collect parameters such as current and voltage, detect the status of the fault simulation module, and feed back the detection results to the Raspberry Pi.

[0040] (3) The Raspberry Pi determines whether the fault simulation module is in normal condition based on the self-test results: if it is normal, the fault simulation module enters working mode; if it is abnormal, the fault simulation module reports the fault.

[0041] (4) When the fault simulation module is normal, the Raspberry Pi communicates with the fault simulation module through the 485 bus and controls the fault simulation module to inject the specified fault type into the ECU, such as short circuit to ground, short circuit to power supply, abnormal resistance, communication abnormality, etc.

[0042] The power module is electrically connected to the self-test MCU, self-test circuit, Raspberry Pi, and fault simulation module. Specifically, the power module includes one BUCK DC-DC 12V output circuit, one BUCK DC-DC 5V output circuit, one CM4 3.3V output circuit, and a 12V REF interface. The BUCK DC-DC 12V output circuit powers the self-test circuit, the BUCK DC-DC 5V output circuit powers the Raspberry Pi and self-test MCU, the CM4 3.3V output circuit powers the Ethernet LED module through the Raspberry Pi, and the 12V REF interface is connected to the 12V Output interface of the fault simulation module.

[0043] Working principle of the power module:

[0044] (1) The power module uses DC 24V as input.

[0045] (2) The BUCK DC-DC 12V output circuit outputs 12V voltage to power devices such as SIT1021, DG4051EEY, DG408LE and CCR.

[0046] (3) The BUCK DC-DC 5V output circuit outputs a 5V voltage, which is converted by the SY6280 and divided into four mutually isolated 5V outputs, namely:

[0047] 1) +5V (current limited to 370mA), used as the input for the STG detection constant current source and the Normal detection constant current source;

[0048] 2) Logic 5V (current limit 200mA) is used as the input voltage divider signal for the constant current source, INA180Ax (current amplifier), and DG4051EEY (self-test MCU AD detection).

[0049] 3) Comm 5V (current limited to 200mA), used as the input for communication MCU and communication CAN;

[0050] 4) +5V (current limited to 200mA), used as the input for self-testing MCU and self-testing 485.

[0051] (4) The BUCK DC-DC 5V output circuit outputs a 5V voltage, which is processed by the bidirectional voltage level converter TXB0104 and used as the input of the Raspberry Pi system.

[0052] (5) Power the Ethernet LED (ETH) module through the Raspberry Pi system.

[0053] (6) The power supply module uses the 12V input of the fault simulation module as the reference voltage.

[0054] The advantages of this fault injection test fixture are:

[0055] 1. Multi-channel, multi-type fault injection: Supports multiple fault types such as short circuit to ground, short circuit to power supply, and abnormal resistance, and can be independently controlled by multiple channels to meet complex testing needs.

[0056] 2. High integration and automation: Using Raspberry Pi as the main controller, it integrates communication, control, self-testing and other functions, resulting in a high degree of system automation and reducing manual intervention.

[0057] 3. Real-time monitoring and self-test: The self-test MCU and self-test circuit work together to monitor the status of the fault simulation module in real time, and collect parameters such as current and voltage to ensure the accuracy and safety of fault injection.

[0058] 4. High power isolation and safety: The power module adopts a multi-channel isolated power supply design, which improves the system's anti-interference capability and safety, and protects the main control and the device under test.

[0059] 5. Modular design: The main control, self-test, fault simulation and power supply modules have clear division of labor, which facilitates maintenance and expansion.

[0060] The foregoing has shown and described the basic principles, main features, and advantages of this utility model. Those skilled in the art should understand that this utility model is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of this utility model. Various changes and modifications can be made to this utility model without departing from its spirit and scope, and all such changes and modifications fall within the scope of the claimed utility model.

Claims

1. A fault injection test fixture, characterized in that, include: A fault simulation module, which is connected to the ECU; The self-testing MCU is connected to the fault simulation module via a self-testing circuit. The Raspberry Pi has its SPI6 interface and the SPI2 interface of the self-test MCU connected bidirectionally via the SPI bus. The Raspberry Pi's UART4 interface is connected to an external 485 transceiver via the 485 bus. The 485 transceiver is connected to the serial communication interface of the fault simulation module and the UART2 interface of the self-test MCU via the 485 bus. The power module is electrically connected to the self-test MCU, the self-test circuit, the Raspberry Pi, and the fault simulation module.

2. The fault injection test fixture according to claim 1, characterized in that: The Raspberry Pi's GPIO interface is connected to the hard reset interface of the self-test MCU via a data cable.

3. The fault injection test fixture according to claim 1, characterized in that: The Raspberry Pi's signal ground interface is electrically connected to the fault simulation block.

4. The fault injection test fixture according to claim 1, characterized in that: The self-test circuit includes a multiplexer and a constant current source. The multiplexer is connected to the fault simulation block, the GPIO interface of the self-test MCU, and the AD interface of the self-test MCU via cables. The constant current source is connected to the multiplexer via cables.

5. The fault injection test fixture according to claim 1, characterized in that: The power module includes one BUCK DC-DC 12V output circuit, one BUCK DC-DC 5V output circuit, one CM4 3.3V output circuit, and a 12V REF interface. The BUCK DC-DC 12V output circuit powers the self-test circuit, the BUCK DC-DC 5V output circuit powers the Raspberry Pi and the self-test MCU, the CM4 3.3V output circuit powers the Ethernet LED module through the Raspberry Pi, and the 12V REF interface is connected to the 12V Output interface of the fault simulation module.