Vehicle controller interaction platform based on dynamic configuration file

Abstract

The invention discloses a vehicle controller interaction platform based on a dynamic configuration file, which relates to the technical field of vehicle detection and comprises a driving layer, a protocol layer and an application layer, the driving layer is a bottom module of the platform, the protocol layer is a core module of the platform, and the application layer is a top module of the platform. According to the vehicle controller interaction platform based on the dynamic configuration file, the defects of the traditional technology in the aspects of protocol compatibility, operation complexity and data processing capability are effectively overcome. By dynamically loading and analyzing the protocol configuration files of different manufacturers, the platform can automatically identify and adapt to vehicle controllers of different manufacturers and models, manual intervention of a user is reduced, and operation efficiency and accuracy are improved. Besides, the platform integrates multiple functions of flashing, DTC fault diagnosis, parameter reading and writing and the like, and through intelligent prompting and automatic process optimization, the reliability of the system and the user experience are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle detection, in particular to a vehicle controller interactive platform based on dynamic configuration files. Background Art

[0002] Traditional vehicle diagnostic and maintenance platforms usually only support protocols from a single manufacturer or a few manufacturers, and often rely on static configuration files for configuration, lacking flexibility and adaptability. When the current platform handles multi-vendor protocols, users need to manually switch configuration files or modify a large number of configuration parameters, which not only increases the complexity of operation but also easily leads to human errors. In addition, the existing technology has a low degree of automation in the flashing process, lacks compatibility with multiple models of equipment and a complete error handling mechanism, which affects the reliability of the system and user experience. Protocol parsing is usually customized to the needs of a single manufacturer, and cannot achieve broad support for vehicle controllers from multiple manufacturers, limiting the versatility and scalability of the system.

[0003] Disadvantages: Insufficient protocol compatibility: Existing platforms only support protocols from a single manufacturer or a few manufacturers, and are difficult to adapt to vehicle controllers from different manufacturers. This results in poor applicability of the platform in a multi-manufacturer environment and inability to meet the diverse needs of the market.

[0004] High operational complexity: When users face vehicles from different manufacturers, they need to manually switch configuration files and adjust operating procedures. The operation is cumbersome and prone to errors, reducing the efficiency of system use.

[0005] Limited data processing capabilities: Traditional systems often require repeated configuration and manual adjustments when dealing with multi-vendor protocols, resulting in low data management efficiency and prone to data inconsistency.

[0006] Lack of system integration: The functional modules of the platform are relatively independent, and lack the integration of functions such as fault code reading, parameter reading and writing, making it impossible to achieve comprehensive vehicle diagnosis and data management. Summary of the invention

[0007] In view of the deficiencies of the prior art, the present invention provides a vehicle controller interaction platform based on a dynamic configuration file to solve the problems raised in the above background technology.

[0008] To achieve the above object, the present invention provides the following technical solutions: In a first aspect, an embodiment of the present invention provides a vehicle controller interaction platform based on a dynamic configuration file, including a driver layer, a protocol layer, and an application layer; The driver layer is the bottom module of the platform, used for communication with the vehicle, including supporting the management and operation of physical CAN devices and virtual CAN devices, shielding the differences of the bottom hardware devices, providing a unified data access interface, and ensuring the interaction between the protocol layer and the application layer and the hardware; The protocol layer is the core module of the platform, which is used for parsing and adapting multi-vendor protocols. It realizes compatibility with protocols of different manufacturers by dynamically loading configuration files, automatically configures communication ID, DTC fault code, snapshot data, distinguishes protocols of different manufacturers by file name or worksheet name, and automatically loads corresponding configuration files. The application layer is the top-level module of the platform, which is used for flashing, DTC fault diagnosis, parameter reading and writing, equipment online detection, and provides a user-friendly operation interface.

[0009] To further optimize the technical solution, in the driving layer, By defining the CAN device base class, physical CAN devices and virtual CAN devices are supported, and the device type used can be dynamically selected and switched; The data access interface is based on the sendFrame() and receiveFrame() methods, ensuring that the protocol layer and the functional layer send and receive CAN data frames in the same way.

[0010] To further optimize the technical solution, the driver layer also includes a CAN bus transmission error detection module to detect problems such as inconsistent baud rates, error frames, and device interruptions in real time; When an error is detected, the platform records the error and triggers the corresponding error handling mechanism, including automatic retry or prompting the user to intervene.

[0011] To further optimize the technical solution, the protocol layer dynamically loads the configuration file, including: Configuration file parsing: by parsing Excel files and ini files, reading and parsing the manufacturer's communication protocol; Data management: modular management of various types of data parsed from configuration files; Protocol adaptation, realizing dynamic adaptation function of multi-vendor protocols.

[0012] To further optimize this technical solution, the configuration file is parsed: Different worksheets in the Excel file correspond to different data types, including DTC fault codes, general DID lists, and snapshot data; the ini file is used to store communication ID and function ID information. The protocol layer generates the communication process based on the data type and applies the information in the actual operation process; The data management: Use mapping tables to store DTC fault codes and DID list information, and provide query and modification interfaces for each data item, so that the platform can quickly access and process related data; The protocol is adapted to: When the user selects a configuration file from a certain manufacturer, the protocol layer automatically configures the corresponding communication ID, DTC fault code, and snapshot list information based on the file content to achieve compatibility and universality on vehicles from different manufacturers.

[0013] To further optimize the technical solution, the DTC fault code analysis includes: Parse the DTC fault code. The protocol layer reads a specific worksheet in the Excel file and traverses the data in the table row by row to extract the fault code, fault description, and fault level data. After parsing is complete, the extracted data is stored in a mapping table.

[0014] To further optimize this technical solution, the general DID list parsing includes: The protocol layer parses the universal data identifier DID and extracts data on data length, encoding format, and read and write permissions; The universal DID in each row represents a communication data unit. The protocol layer stores the data in the DID mapping table and generates corresponding read or write operations for subsequent communication operations.

[0015] To further optimize the technical solution, the snapshot data analysis includes: Parse the snapshot data, and the protocol layer extracts the identifier, snapshot data length, and starting position information to record the status of the vehicle when the fault occurs.

[0016] To further optimize the technical solution, the application layer is flashed, including: By automatically selecting and loading the corresponding Flash driver, the user selects the device type, and the platform automatically loads the adapted driver and starts flashing; During the flashing process, the platform provides status prompts and process prompts to ensure that users understand the progress of the operation in real time.

[0017] To further optimize the technical solution, the application layer reads the DTC fault code and snapshot data in real time, compares it with the data in the configuration file, loads the corresponding fault code information and processing suggestions, and the user quickly identifies and solves the faults in the vehicle operation.

[0018] In a second aspect, an embodiment of the present invention provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, wherein: when the computer program instructions are executed by the processor, the steps of a vehicle controller interaction platform based on a dynamic configuration file as described in the first aspect of the present invention are implemented.

[0019] In a third aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein: when the computer program instructions are executed by a processor, the steps of a vehicle controller interaction platform based on a dynamic configuration file as described in the first aspect of the present invention are implemented.

[0020] Compared with the prior art, the present invention provides a vehicle controller interaction platform based on a dynamic configuration file, which has the following beneficial effects: This vehicle controller interaction platform based on dynamic configuration files effectively solves the shortcomings of traditional technologies in terms of protocol compatibility, operational complexity and data processing capabilities. By dynamically loading and parsing protocol configuration files from different manufacturers, the platform can automatically identify and adapt to vehicle controllers from different manufacturers and models, reducing user manual intervention and improving operational efficiency and accuracy. In addition, the platform integrates multiple functions such as flashing, DTC fault diagnosis, parameter reading and writing, and improves system reliability and user experience through intelligent prompts and automated process optimization. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 A schematic diagram of the composition of a vehicle controller interaction platform based on a dynamic configuration file proposed by the present invention; Figure 2 The invention discloses a CAN device type selection interface for a vehicle controller interaction platform based on a dynamic configuration file. DETAILED DESCRIPTION

[0023] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are described in detail below in conjunction with the accompanying drawings.

[0024] In the following description, many specific details are set forth to facilitate a full understanding of the present invention, but the present invention may also be implemented in other ways different from those described herein, and those skilled in the art may make similar generalizations without violating the connotation of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.

[0025] Secondly, the term "one 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 term "in one embodiment" that appears in different places in this specification does not necessarily refer to the same embodiment, nor is it a separate or selective embodiment that is mutually exclusive with other embodiments. Embodiment 1:

[0026] Reference Figure 1-2 , which is the first embodiment of the present invention, provides a vehicle controller interaction platform based on a dynamic configuration file, including a driver layer, a protocol layer and an application layer.

[0027] The driver layer is the bottom module of the platform, which supports multiple CAN devices to achieve communication with the vehicle, including physical CAN devices. It unifies the data access interface, and the communication layer provides a unified CAN frame data stream for the protocol layer, so that the protocol layer and the functional layer can easily access and process data. This layer abstracts the base class of CAN devices and supports drivers of multiple CAN card types, ensuring the compatibility and stability of the platform in various hardware environments.

[0028] In the driver layer: By defining the CAN device base class, physical CAN devices and virtual CAN devices are supported, and the device type used can be dynamically selected and switched; The data access interface is based on the sendFrame() and receiveFrame() methods, ensuring that the protocol layer and the functional layer send and receive CAN data frames in the same way.

[0029] In this embodiment, the driver layer also includes a CAN bus transmission error detection module to detect problems such as inconsistent baud rates, error frames, and device interruptions in real time; When an error is detected, the platform records the error and triggers the corresponding error handling mechanism, including automatic retry or prompting the user to intervene.

[0030] All test results will be fed back to users in real-time prompts, and detailed troubleshooting solutions will be provided. By detecting CAN transmission errors, the platform can quickly locate and solve problems in the communication process, ensuring the accuracy and integrity of data transmission, thereby improving the stability of the entire platform.

[0031] Real-time monitoring of the online status of vehicle controllers. Ensures equipment reliability and data transmission stability during operation. The platform can automatically adjust communication strategies based on detection results to ensure optimal communication performance in different vehicle and controller environments.

[0032] The implementation process of the driver layer is as follows: The specific implementation of the driver layer involves the abstraction of CAN devices, the unification of communication interfaces, the compatibility support of hardware devices, and the unified interface management of data frames to ensure the efficiency and stability of CAN bus communication.

[0033] Abstraction of CAN devices In order to ensure that the platform can support multiple different types of CAN devices, the driver layer abstracts these devices and defines a CAN device base class. All physical CAN devices and virtual CAN devices are extended and implemented based on this base class.

[0034] CAN device base class definition: The CAN device base class defines a common interface, including common methods such as data frame sending, data frame receiving, CAN bus initialization, error detection, etc. Both physical CAN devices and virtual CAN devices will inherit and implement these interfaces.

[0035] Physical CAN devices: The implementation of physical CAN devices is based on specific CAN hardware cards, such as USB-CAN2, USB-CAN2C, etc. The driver of each physical CAN card implements its own initialization, data transmission and error handling mechanism by inheriting the base class CANDevice.

[0036] For example, for a specific USB-CAN device, the implementation of the driver layer may include device initialization, baud rate setting, sending / receiving data frames, etc.: Virtual CAN Device: To support offline debugging and testing, the platform also implements a virtual CAN device, which can simulate the communication behavior of the vehicle, generate a virtual CAN data stream, and provide it to the upper protocol layer for testing and debugging. The virtual CAN device generates data frames through the simulation tool and loads frame data from the stored historical data file.

[0037] The driver layer uses the unified interface methods sendFrame() and receiveFrame() to ensure that the upper protocol layer does not perceive hardware differences when interacting with physical devices or virtual devices. In other words, whether it is a physical CAN device or a virtual CAN device, the upper protocol layer can read and send data frames in the same way.

[0038] Unified interface implementation: When the protocol layer needs to send or receive CAN data, it directly calls the sendFrame() or receiveFrame() interface without knowing which specific device is at the bottom layer.

[0039] In summary, the driver layer not only supports the operation of a single CAN device, but also supports the simultaneous operation of multiple CAN devices through the device management module. The system can dynamically load and initialize multiple devices and assign different communication tasks to each device. For example, different modules of the vehicle (such as ABS, ECU) may be connected to different CAN buses, which can be managed by the driver layer.

[0040] At the same time, the driver layer provides hardware compatibility support for different types of CAN devices, ensuring that the platform can run stably in different hardware environments. Each CAN device has its own specific driver in the driver layer, and the driver layer automatically selects the appropriate driver for communication based on the current system hardware environment.

[0041] Support for multiple CAN device types: By associating the specific implementation of each CAN card with the CAN device base class, the system can dynamically select and switch the device type to use. For example, the user can choose to use USB-CAN2 or USB-CAN2C through the configuration file.

[0042] The data frames received by the driver layer from the physical or virtual CAN device will be passed to the protocol layer through a unified data management interface. The unified management of data frames includes the storage of frame queues, the recording of timestamps, the processing of error frames, etc.

[0043] Data frame queue and cache: The system stores the received CAN frames in a buffer queue, from which the protocol layer can read the frame data sequentially. The buffer queue ensures efficient communication while avoiding data loss.

[0044] The protocol layer is the core module of the platform, which is used for parsing and adapting multi-vendor protocols. It achieves compatibility with protocols of different manufacturers by dynamically loading configuration files, automatically configures communication ID, DTC fault code, snapshot data, distinguishes protocols of different manufacturers by file name or worksheet name, and automatically loads corresponding configuration files to ensure data accuracy and consistency.

[0045] The protocol layer dynamically loads the configuration file, including: Configuration file parsing: by parsing Excel files and ini files, read and parse the manufacturer's communication protocol.

[0046] Data management: modular management of various types of data parsed from configuration files.

[0047] The modular data management structure is adopted to store the parsed data in a specific data structure and manage it through indexes and key-value pairs. The system supports fast query and processing of different data to ensure the integrity and consistency of the data. The data management module can be expanded according to user needs and supports flexible processing of multiple data types.

[0048] Protocol adaptation, realizing dynamic adaptation function of multi-vendor protocols.

[0049] Furthermore, the configuration file is parsed: Different worksheets in the Excel file correspond to different data types, including DTC fault codes, general DID lists, and snapshot data; the ini file is used to store communication ID and function ID information. The protocol layer generates the communication process based on the data type and applies the information in the actual operation process; The data management: Use mapping tables to store DTC fault codes and DID list information, and provide query and modification interfaces for each data item, so that the platform can quickly access and process related data; The protocol is adapted to: When the user selects a configuration file from a certain manufacturer, the protocol layer automatically configures the corresponding communication ID, DTC fault code, and snapshot list information based on the file content to achieve compatibility and universality on vehicles from different manufacturers.

[0050] In this embodiment, the DTC fault code analysis includes: Parse the DTC fault code. The protocol layer reads a specific worksheet in the Excel file and traverses the data in the table row by row to extract the fault code, fault description, and fault level data. After parsing is complete, the extracted data is stored in a mapping table.

[0051] The general DID list parsing includes: The protocol layer parses the universal data identifier DID and extracts data on data length, encoding format, and read and write permissions; The universal DID in each row represents a communication data unit. The protocol layer stores the data in the DID mapping table and generates corresponding read or write operations for subsequent communication operations.

[0052] The parameter reading and writing operations of the vehicle controller can be combined with the DID list to achieve precise control of the internal data of the vehicle. In addition, the platform can also dynamically adjust the parameters of the read and write operations through the configuration file, further enhancing the flexibility and scalability of the platform.

[0053] The snapshot data analysis includes: Parse the snapshot data, and the protocol layer extracts the identifier, snapshot data length, and starting position information to record the status of the vehicle when the fault occurs.

[0054] When parsing an INI file: In addition to the Excel file, the protocol layer also needs to parse the communication configuration in the INI file, such as the communication ID and function ID. Each INI file contains multiple sections, each of which contains the communication information of different modules (such as ECU, MCU, etc.). The protocol layer reads this information and maps it to the communication structure of the system for device communication and data transmission.

[0055] Check whether the configuration file exists. The path is / driver / ConfigID.ini.

[0056] If a file is missing, a warning signal is issued and the existing data is cleared.

[0057] Get a list of all OEM names via Config().Get("MAIN", "OEM").

[0058] Iterate through these names and gradually resolve the communication ID information of each module.

[0059] For each module name, parse the following: OEM name: parsed by Config().Get(mod, "OEM_Name").

[0060] Functional ID (ECU_Functional_RequestID): Read and convert to hexadecimal.

[0061] Physical address (MCU_Physical_RequestID, etc.): Parse each item and convert to hexadecimal.

[0062] The communication ID information of each module will be encapsulated into a MODULE_CANID structure and stored in QList<MODULE_CANID> middle.

[0063] Use QTableWidget as the display module.

[0064] Each row corresponds to a module, and each column displays the module's communication information (such as function ID, physical address, etc.).

[0065] Add logic code to the parsed QList<MODULE_CANID> Load into the table.

[0066] The application layer is the top-level module of the platform, which is used for flashing, DTC fault diagnosis, parameter reading and writing, and equipment online detection. It also provides a user-friendly operation interface to make operation simple and easy.

[0067] In the application layer: Flashing function: supports multiple device models, selects and loads the corresponding Flash driver according to different device types, and improves the efficiency and automation of the flashing process. The platform has the function of importing and memorizing Flash drivers, and provides detailed interactive information prompts and process prompts during the flashing process to ensure that users can grasp the flashing status in real time.

[0068] At each stage of data flushing, the platform automatically performs multi-level data verification to ensure data accuracy and consistency. Verification rules include format verification, data integrity verification, etc. When data anomalies are found, the platform will immediately issue a warning and take corrective measures.

[0069] DTC fault diagnosis function: The platform can read DTC fault codes and snapshot data, compare them with the data in the configuration file, and load the corresponding fault code information and processing suggestions. It supports real-time fault monitoring and prompts faults in vehicle operation in a timely manner.

[0070] Parameter reading and writing function: Through the universal DID list in the configuration file, the platform can read and write parameters of different devices. This function supports multiple parameter types to ensure the wide applicability of the platform.

[0071] Device detection function: supports device online status detection and communication error detection, including baud rate inconsistency, error frame, device interruption, etc. The platform can automatically adapt to the detection mechanism of multi-vendor devices to ensure the compatibility of different devices.

[0072] During the download process, the platform automatically configures and parses the download process through the configuration file, simplifying the user's operation. The user only needs to select the appropriate configuration file, and the platform can automatically complete the corresponding settings and download tasks. During the download process, the platform provides detailed interactive information prompts and download process prompts to ensure that users can clearly understand the current operation status and the next step. These prompts can effectively reduce the risk of user misoperation and improve the transparency and security of the download process.

[0073] The platform supports automated testing based on configuration files. Users only need to load the corresponding configuration files, and the platform can automatically execute the predefined test process based on the file content. This automated testing function ensures the consistency of the test process of different vendor protocols and avoids test errors caused by manual operations. During the test process, the platform can automatically generate a test report based on the content of the configuration file, and record in detail the various data and abnormal conditions during the test process, which is convenient for users to conduct subsequent analysis and troubleshooting.

[0074] Compared with existing technologies, this platform has the following advantages: Enhanced protocol compatibility: Compared with the existing technology, the present invention supports multi-vendor protocols through dynamic protocol analysis, is suitable for the diagnosis and data flashing requirements of various vehicle controllers, and greatly improves the versatility and market adaptability of the system.

[0075] Flexible multi-vendor protocol adaptation: Through dynamic configuration files, the platform can support protocols from a variety of different manufacturers and achieve multi-protocol compatibility without modifying the core code, with high flexibility and scalability.

[0076] Real-time error detection and feedback: The CAN transmission error detection function can quickly locate and solve problems in the communication process, ensure the accuracy and integrity of data transmission, and improve system stability.

[0077] Modular data management: Compared with traditional centralized data management, this technology adopts a modular data management structure to manage data through indexes and key-value pairs. This design improves the system's ability to handle multiple data types, enhances the system's scalability, and ensures the integrity and consistency of data management.

[0078] Multi-level data verification: Traditional vehicle controller interaction platforms often only perform basic format verification, while this technology improves the accuracy and consistency of data processing through multi-level data verification, including format verification and data integrity verification, and effectively reduces the risk of data anomalies.

[0079] Online device detection: This technology integrates online device detection function, which can monitor the online status of the device in real time, ensuring the reliability of the device and the stability of data transmission during operation. This is a significant improvement compared to the traditional platform that relies on manual or periodic inspection of device status.

[0080] Automation and prompt functions of the download process: The traditional download process is complex and prone to errors. This technology automatically configures and parses the download process through configuration files, simplifies the operation steps, and provides detailed interaction information and process prompts, effectively reducing the risk of user errors and improving operation transparency and security.

[0081] Dynamic adaptation of multi-vendor protocols: Previous technologies usually require users to manually adjust the support for multi-vendor protocols. This technology realizes automatic adaptation of protocols from different vendors through dynamic configuration files, greatly improving the flexibility and cross-platform compatibility of the system.

[0082] CAN transmission error detection and feedback mechanism: This technology introduces the CAN bus transmission error detection function, which can timely detect and feedback problems such as inconsistent baud rates, error frames, device interruptions, etc., and provide solutions. This real-time detection and feedback mechanism enhances the stability of the system and the accuracy of data transmission.

[0083] Automated testing based on configuration files: The testing process of traditional systems usually relies on manual operations, which is prone to errors. This technology automatically executes the testing process through configuration files, ensuring the standardization and consistency of the testing process, and automatically generates test reports, greatly improving the efficiency and reliability of the test.

[0084] Efficient flashing and diagnostic functions: Compared with the traditional method of manually loading the driver, this technology automatically selects and loads the Flash driver and supports the memory function of the imported driver, which greatly improves the efficiency and automation of the flashing process. In addition, the detailed interactive information and process prompts provided enable users to grasp the operation status in real time, improving the user experience and the safety of operation. Embodiment 2:

[0085] This embodiment also provides a computer device, which is suitable for a vehicle controller interaction platform based on a dynamic configuration file, including a memory and a processor; the memory is used to store computer executable instructions, and the processor is used to execute computer executable instructions to implement a vehicle controller interaction platform based on a dynamic configuration file as proposed in the above embodiment.

[0086] This embodiment also provides a storage medium on which a computer program is stored. When the program is executed by a processor, a vehicle controller interaction platform based on a dynamic configuration file as proposed in the above embodiment is implemented.

[0087] The computer device may be a terminal, and the computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. The display screen of the computer device may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device may be a touch layer covered on the display screen, or a key, trackball or touchpad provided on the housing of the computer device, or an external keyboard, touchpad or mouse, etc.

[0088] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit with a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit with a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0089] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention, which should all be included in the scope of the claims of the present invention.

Claims

1. A vehicle controller interactive platform based on dynamic configuration files, characterized in that: Includes driver layer, protocol layer and application layer; The driver layer is the bottom module of the platform, used for communication with the vehicle, including supporting the management and operation of physical CAN devices and virtual CAN devices, shielding the differences of the bottom hardware devices, providing a unified data access interface, and ensuring the interaction between the protocol layer and the application layer and the hardware; The protocol layer is the core module of the platform, which is used for parsing and adapting multi-vendor protocols. It realizes compatibility with protocols of different manufacturers by dynamically loading configuration files, automatically configures communication ID, DTC fault code, snapshot data, distinguishes protocols of different manufacturers by file name or worksheet name, and automatically loads corresponding configuration files. The application layer is the top-level module of the platform, which is used for flashing, DTC fault diagnosis, parameter reading and writing, equipment online detection, and provides a user-friendly operation interface.

2. A vehicle controller interactive platform based on dynamic configuration files according to claim 1, characterized in that: In the driving layer, By defining the CAN device base class, physical CAN devices and virtual CAN devices are supported, and the device type used can be dynamically selected and switched; The data access interface is based on the sendFrame() and receiveFrame() methods, ensuring that the protocol layer and the functional layer send and receive CAN data frames in the same way.

3. The vehicle controller interactive platform based on dynamic configuration files according to claim 1, characterized in that: The driver layer also includes a CAN bus transmission error detection module to detect baud rate inconsistency, error frames, and device interruption problems in real time; When an error is detected, the platform records the error and triggers the corresponding error handling mechanism, including automatic retry or prompting the user to intervene.

4. The vehicle controller interactive platform based on dynamic configuration files according to claim 1, characterized in that: The protocol layer dynamically loads the configuration file, including: Configuration file parsing: by parsing Excel files and ini files, reading and parsing the manufacturer's communication protocol; Data management: modular management of various types of data parsed from configuration files; Protocol adaptation, realizing dynamic adaptation function of multi-vendor protocols.

5. The vehicle controller interactive platform based on dynamic configuration files according to claim 4, characterized in that: The configuration file is parsed: Different worksheets in the Excel file correspond to different data types, including DTC fault codes, general DID lists, and snapshot data; the ini file is used to store communication ID and function ID information. The protocol layer generates the communication process based on the data type and applies the information in the actual operation process; The data management: Use mapping tables to store DTC fault codes and DID list information, and provide query and modification interfaces for each data item, so that the platform can quickly access and process related data; The protocol is adapted to: When the user selects a configuration file from a certain manufacturer, the protocol layer automatically configures the corresponding communication ID, DTC fault code, and snapshot list information based on the file content to achieve compatibility and universality on vehicles from different manufacturers.

6. The vehicle controller interactive platform based on dynamic configuration files according to claim 5, characterized in that: The DTC fault code analysis includes: Parse the DTC fault code. The protocol layer reads a specific worksheet in the Excel file and traverses the data in the table row by row to extract the fault code, fault description, and fault level data. After parsing is complete, the extracted data is stored in a mapping table.

7. The vehicle controller interactive platform based on dynamic configuration files according to claim 5, characterized in that: The general DID list parsing includes: The protocol layer parses the universal data identifier DID and extracts data on data length, encoding format, and read and write permissions; The universal DID in each row represents a communication data unit. The protocol layer stores the data in the DID mapping table and generates corresponding read or write operations for subsequent communication operations.

8. The vehicle controller interactive platform based on dynamic configuration files according to claim 5, characterized in that: The snapshot data analysis includes: Parse the snapshot data, and the protocol layer extracts the identifier, snapshot data length, and starting position information to record the status of the vehicle when the fault occurs.

9. The vehicle controller interactive platform based on dynamic configuration files according to claim 1, characterized in that: The application layer is flashed, including: By automatically selecting and loading the corresponding Flash driver, the user selects the device type, and the platform automatically loads the adapted driver and starts flashing; During the flashing process, the platform provides status prompts and process prompts to ensure that users understand the progress of the operation in real time.

10. The vehicle controller interactive platform based on dynamic configuration files according to claim 1, characterized in that: The application layer reads the DTC fault code and snapshot data in real time, compares it with the data in the configuration file, loads the corresponding fault code information and processing suggestions, and enables users to quickly identify and resolve faults in vehicle operation.

Images