Solution Overview

This solution is a further enhancement and optimization of the CAN/CAN FD/CAN XL/LIN/FlexRay bus network and diagnostic testing solution provided by Polelink. Although the structure and interface of this testing system are designed modularly, allowing for functional module customization based on testing requirements, challenges remain in the reusability of test scripts during specific testing implementations, especially when vehicle platforms and controllers change.

In this context, this solution conducts an in-depth analysis of the challenges associated with test script reuse during single controller or vehicle network and diagnostic testing processes. It proposes methods such as communication database abstraction, gateway routing table adaptation, and dynamic test parameter management to improve the reusability and automation of test scripts across different vehicle models, ensuring efficient testing for new vehicle launches.

Background

During the network and diagnostic testing of automotive electronic controllers (ECUs), differences in vehicle models and controllers make it difficult to reuse test scripts, primarily reflected in the following areas:

• Database File Differences: The database files for each controller are different, necessitating manual changes to specific test parameters during test execution for a particular vehicle model.

• Gateway Routing Table Differences: Different vehicle models and controllers may use varying gateway routing tables, requiring adjustments to test parameters based on these different tables.

• Diversity of Test Parameters: Each vehicle model or controller has distinct input and output parameters (e.g., signal rate, message ID), which must be refined and customized during development, increasing complexity.

• Communication Protocol Differences: The communication protocols used by various vehicle models may differ, such as CAN, CANFD, LIN, FlexRay, and Ethernet. These protocols vary in data transmission methods, rates, and frame structures, causing test scripts designed for one protocol to be incompatible with another. For example, the differences in data transmission methods and frame formats between CAN and FlexRay necessitate completely different signal monitoring and data capture logic scripts.

• Diagnostic Service Differences: Different vehicle models and controllers involve various diagnostic requests, data formats, and DTC parsing methods, complicating the reuse of test scripts developed for specific diagnostic services on other vehicle models or controllers.

Due to the repetitive workload and poor reusability caused by these differences in test script development, the automotive industry faces significant challenges. When part-level test scripts developed by the testing department are released to suppliers, the differences in parameters among controllers make adaptation difficult, leading to either the suppliers needing to redevelop scripts or the testing personnel from the vehicle manufacturer categorizing and debugging adaptations. Both solutions severely impact controller delivery times and vehicle launch schedules.

Software Integration Solution

To address these issues, Polelink proposes a comprehensive automated processing solution covering database file conversion, test parameter generation, test project reorganization, test execution driving, and test report handling. The core of the solution is illustrated in Figures 1 and 2.

Figure 1: Composition of the Network Communication Testing Integration Solution

Figure 2: Composition of the Diagnostic Testing Integration Solution

Key functional modules include:

• Signal Matrix Generation Database File: Automatically converts communication signal matrices into database files (DBC, LDF, Fibex, etc.) for subsequent test parameter generation.
• Database Parsing and Preprocessing: Automatically parses database files to resolve differences arising from different formats (e.g., DBC and ARXML), reducing complexity and manual intervention.
• Test Parameter Generation: Generates necessary test parameter files based on database files, routing tables, and common parameter tables, ensuring parameter reusability across different vehicle models.
• Test Project Reorganization and Compilation: Automatically reorganizes and compiles CANoe test projects based on generated test parameters, reducing manual configuration time.
• Automated CANoe Driving: Uses automated scripts to invoke CANoe for test execution, eliminating tedious manual operations and enhancing testing efficiency.
• Testing Information GUI Input: Provides a simple GUI for testers to input controller information, test project directories, etc., simplifying the testing process.
• Test Report Generation and Handling: Automatically generates detailed test reports after execution and standardizes processing for subsequent project analysis and management.

Example of Solution Execution Steps (Using Diagnostic Survey Form as Input):

• Script Development: Parameters related to diagnostics are unified in Parameters.cin for ease of reuse across platforms or input changes.

  
  

Figure 3: Example of Parameters.cin

• Test Case Development: Uses variables from Parameters.cin.

• Import Diagnostic Survey Form: Utilize the PAVELINK.SOA-Converter tool to convert the diagnostic survey form to ODX, automatically parse it, and generate test-specific Parameters.cin.

Figure 4: Configuration Interface for Automatic Parameter Generation

Figure 5: Operation Interface for Parsing ODX/PDX and Generating Parameters

• Replace Files in the Project: Use the generated Parameters.cin to replace files in the project.
• Initiate Testing: Automatically drive CANoe for subsequent testing processes.
• Monitor Testing Process: After testing, automatically read the XML report generated by CANoe and parse and process it according to the configured Excel template to generate the final test report.

Advantages of the Solution

• Increased Reusability: This solution lowers script differences among various vehicle models and controllers through unified signal and database processing, enhancing script reusability.
• Reduced Manual Steps: A unified configuration interface only requires setting input paths and necessary parameters, allowing one-click execution without manual intervention.
• Enhanced Compatibility: Regardless of whether using DBC, ARXML, CDD, or ODX, this solution ensures script compatibility through unified preprocessing and parsing modules.

This solution will effectively elevate the automation level of automotive electronic network and diagnostic testing, addressing the challenges of test script reuse across multiple vehicle models and controllers.

Polelink focuses on the automotive electronic testing field, offering comprehensive automotive electronic testing solutions and continuously upgrading automation testing systems to enhance testing efficiency. For inquiries about testing systems or services, please feel free to consult us!