Method for matching upper computer and diagnosis questionnaire according to configuration file self-adaption

Abstract

The invention relates to an upper computer and diagnosis questionnaire matching method self-adaptive according to a configuration file, and belongs to the technical field of vehicle-mounted test diagnosis, and the method comprises the following steps: importing the configuration file: selecting the configuration file according to different diagnosis questionnaires, obtaining the corresponding configuration file, and importing and initializing the configuration file; reading the data, and processing and translating a bus value; writing in the data; the components are controlled; and carrying out reading detection on the DTC.

Description

Technical Field

[0001] This invention belongs to the field of vehicle-mounted testing and diagnostic technology, and relates to a method for matching a host computer with a diagnostic questionnaire based on a configuration file. Background Technology

[0002] Currently, most host computers for embedded system communication vehicle-mounted testing (UDS) are relatively independent and not tied to the project. Occasionally, some host computers can be based on the diagnostic questionnaire of the corresponding project and bind the functions, buttons, and bus data according to the parameters given in the diagnostic questionnaire. However, the host computers generated by this method are highly coupled with the project diagnostic questionnaire. Moreover, after the development of such host computers is completed, the button function logic is fixed and can only be based on the diagnostic questionnaire at the development stage. Therefore, when subsequent changes are involved in the diagnostic questionnaire and functions, it is also necessary to reconstruct the translation of functions, buttons, and bus data, which greatly increases the difficulty of subsequent maintenance. Summary of the Invention

[0003] In view of this, the purpose of this invention is to provide a method for matching a host computer and a diagnostic questionnaire that is self-adaptive according to a configuration file. By modularizing the input of the project diagnostic questionnaire, the host computer and the diagnostic questionnaire are decoupled, thereby achieving low-code or even no-code diagnostic questionnaire adaptation during the development process, which greatly improves the flexibility of host computer development and maintenance.

[0004] To achieve the above objectives, the present invention provides the following technical solution: A method for matching a host computer with a diagnostic questionnaire based on a configuration file, comprising the following steps: Import configuration files: Select the appropriate configuration file based on the different diagnostic questionnaires, obtain the corresponding configuration file, and import and initialize it; Read the data, process and translate the bus values; Write the data; Control the components; Perform read detection on DTC.

[0005] Furthermore, the importing of the configuration file specifically includes the following steps: S11: Select the configuration file according to different diagnostic questionnaires, and obtain the CANFD / CAN bus configuration, security algorithm configuration, DTC configuration, and DID configuration in the corresponding configuration file directory; S12: Import the basic configuration data, and then configure the UDS basic service based on the existing device connections and basic data; S13: Render read / write control function cases and their corresponding slot functions according to the configuration file.

[0006] Furthermore, the CANFD / CAN bus configuration is used to configure the physical address, functional address, response address, bus type for project communication, and its matching baud rate and hardware channel that match the diagnostic questionnaire; after completing the connection of the bus data acquisition device, the device configuration, channel configuration, and address configuration of the bus data acquisition device are automatically completed according to the CANFD / CAN configuration file, realizing the association between the program and the hardware; the CANFD / CAN bus configuration import process includes: Start importing the CANFD / CAN bus configuration file, obtain the associated bus data acquisition device, and attempt to initialize the device and channel. If initialization fails, end the initialization process and report the reason for the initialization failure. If initialization is successful, match the baud rate and bus type between the device and the corresponding project.

[0007] Furthermore, the DID configuration is used to match the data reading function, data writing function, and actuator control function of the project requirements; the data reading function reads various temperature sensors, actuator feedback opening and voltage, and blower gear bus values ​​planned in the diagnostic questionnaire through the bus, and converts the bus values ​​into physical values ​​with corresponding physical meanings and reports them; the data writing function translates the VIN code, fingerprint information, and configuration information physical values ​​and writes them to the slave device; the actuator control can perform various control operations on various types of downstream actuators specified in the diagnostic questionnaire; the DID configuration import process includes: Import the DID data read service configuration, data write service configuration, and strong control configuration respectively; after the import is completed, perform basic rationality checks on the imported parameters. If there are any unreasonable configuration parameters, end the initialization and report the reason for the initialization failure.

[0008] Furthermore, the process of reading data, processing and translating bus values ​​specifically includes the following steps: S21: Obtain the effective length of the bus feedback message data; S22: For the returned data, the different sub-signals are divided by length using the configuration data; S23: Index configuration file data, determine the data type of the current sub-data: If the current data is of character type, the entire data segment will be converted to ASCII. If the current data is a numeric type, the segmented bytes are converted into the physical value of the sub-data using a conversion formula. Then, it is determined whether the current sub-data data type has a mapping: if no mapping exists, it is determined whether the current real value is within the maximum and minimum range. If it exceeds the range, the data is padded with units and feedback is provided. If it does not exceed the range, an over-range warning is provided while padding with units. If a mapping exists, the mapping type is determined. If it is a direct mapping, it is determined whether the mapping has a valid value. If a valid value exists, feedback is provided based on the mapping matched with the real value. If no valid mapping exists, the real value is reported and an empty mapping warning is reported. If it is a bitwise mapping, the real value is extracted bit by bit and the corresponding values ​​are mapped one by one and feedback is provided.

[0009] Furthermore, the process of writing data specifically includes the following steps: S31: Obtain the DID configuration corresponding to the configuration file; S32: Determine the sub-data type of the data to be written based on the configuration file: if it is a character type, create a text window and a corresponding label box; if it is a numeric type, determine whether the sub-data is a mapping type: if the data is a mapping type, read the mapping parameters corresponding to the configuration file, render the corresponding mapping selection box, and create the corresponding label box; if the data is not a mapping type, create a label box and a numeric input box, and limit the maximum and minimum values ​​of the numeric input box using the parameters in the configuration file. This completes the rendering of the data writing box. S33: After the user completes and confirms the input, the system identifies each sub-data item in the data rendering box and determines the data type: if it is a character type, the text is converted into a HEX value in ASCII code form, and the number of bytes after conversion is limited by the byte length in the DID configuration; if it is a numeric type, the system determines whether the sub-data type is a mapping type: if it is a mapping type, the mapping text is reverse-converted; if it is not a mapping text, the real physical value is converted into a bus value. S34: After the input data is bused, the preprocessing operation of writing the data to the bus is performed. S35: After each preprocessing operation is successful, the translated value is uploaded to the bus and monitored. If there is a positive response, the data is fed back. If there is no response or an error response, the error type is fed back. The data writing is now complete.

[0010] Furthermore, the control of the component specifically includes the following steps: S41: Retrieve the DID configuration corresponding to the configuration file; S42: Determine the sub-data type of the written data based on the configuration file: If it is a numeric type, determine whether the sub-data is a mapping type. If the data is a mapping type, read the mapping parameters corresponding to the configuration file, render the corresponding mapping selection box, and create the corresponding representation box. If the data is not a mapping, create an identifier box and limit the maximum and minimum values ​​of the selection box opening through the parameters in the configuration file. This completes the rendering of the component control box opening. S43: After the user completes and confirms the input, the system identifies each sub-data item in the data rendering box and determines the data type: if it is a character type, the text is converted into a HEX value in ASCII code form, and the number of bytes after conversion is limited in combination with the byte length in the DID configuration; if it is a numeric type, the system determines whether the sub-data type is a mapping type: if it is a mapping type, the mapping text is reverse-converted; if it is not a mapping text, the real physical value is converted into a bus value. S44: After the input data is bused, perform the preprocessing operation to write the data to the bus; S45: After each preprocessing operation is successful, the configuration file is used to determine whether the control component needs a control mask; if a control mask exists, the corresponding mask is filled in according to the control sub-item, and the translated value is uploaded to the bus and monitored; if it is a positive response, the control value is fed back, and if it is a negative response, the error type is fed back, thus completing the strong control.

[0011] Furthermore, the reading and detection of DTC specifically includes the following steps: S51: Select the DTC type to be read, construct a request message based on the corresponding service ID, upload it to the bus and wait for a response; S52: If there is no response or a negative response, feedback will be provided based on the error type; If the response is positive, the response data is obtained, the DTC configuration is retrieved, and the DTC codes are matched one by one. If the corresponding DTC fault code exists in the DTC configuration, the corresponding DTC is matched and the corresponding DTC fault meaning is reported. If the DTC code does not exist in the DTC configuration, a warning is issued that the DTC configuration file is missing and the original DTC code is reported.

[0012] The beneficial effects of this invention are as follows: This invention enables low-code or even no-code generation of data for matching the host computer with diagnostic questionnaires, reducing development time required for different projects and improving the flexibility and scalability of existing projects. It also reduces the maintenance costs of updating the host computer for diagnostic questionnaires.

[0013] 1. By using modular functional code, the program framework is fixed and associated with the project configuration file through an interface, reducing the coupling between the program and the project.

[0014] 2. Alignment of project configuration files and diagnostic questionnaires has been achieved. Data writing, data reading, and actuator control are configured in the form of Excel files, reducing the amount of code required for project development, maintenance, and changes.

[0015] 3. By dynamically generating code, the function keys for different projects are automatically generated, rendered, and function functions are assembled, reducing code redundancy.

[0016] Other advantages, objectives, and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination, or may be learned from practice of the invention. The objectives and other advantages of the invention can be realized and obtained through the following description. Attached Figure Description

[0017] To make the objectives, technical solutions, and advantages of the present invention clearer, the preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, wherein: Figure 1 Import flowchart for configuration file; Figure 2 A flowchart for data reading and translation; Figure 3 Write the data into the flowchart; Figure 4 Component control flowchart; Figure 5 This is a flowchart of the DTC reading and detection process. Detailed Implementation

[0018] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0019] The accompanying drawings are for illustrative purposes only and are schematic diagrams, not actual pictures. They should not be construed as limiting the invention. To better illustrate the embodiments of the invention, some parts in the drawings may be omitted, enlarged, or reduced, and do not represent the actual product dimensions. It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.

[0020] Example 1: This invention provides a method for matching a host computer with a diagnostic questionnaire based on a configuration file, thus supplementing existing UDS diagnostic host computers. It meets user needs and reduces development and maintenance costs.

[0021] like Figure 1 As shown, the first step is to import the configuration file. After starting the program, the user can select a configuration file based on different diagnostic questionnaires. The program will then retrieve the CANFD / CAN bus configuration, security algorithm configuration, DTC configuration, and DID configuration from the corresponding configuration file directory.

[0022] The CANFD / CAN bus configuration is used to configure the physical address, functional address, and response address that match the diagnostic questionnaire, as well as the bus type, matching baud rate, and hardware channel for project communication. After the connection of the bus data acquisition device is completed, the program will automatically complete the device configuration, channel configuration, and address configuration of the bus data acquisition device according to the CANFD / CAN configuration file, realizing the association between the program and the hardware. The CANFD / CAN bus configuration process is as follows: The program will begin importing the bus configuration file. It will automatically obtain the associated bus data acquisition device and attempt to initialize the device and channel. If the initialization fails, the initialization will end and the reason for the failure will be reported. If successful, the program will further match the device with the corresponding project in terms of baud rate, bus type, etc.

[0023] The security algorithm configuration is used to unlock the non-level 0 security sections of the diagnostic questionnaire as a prerequisite for data writing and component control. Different projects typically have different algorithms and keys, and the keys are not shared. The security algorithm configuration process is as follows: When you start importing the algorithm configuration module, it will match the corresponding algorithm according to the different algorithms required by different projects.

[0024] DTC configuration is used to match and translate different fault codes in diagnostic questionnaires for different vehicle models. It is a prerequisite for DTC detection and reading. The DTC configuration process is as follows: When you start importing the DTC configuration module, the DTC directory generated according to the project specifications will be imported. Depending on the project, you can add, delete, or modify the DTC by adding, removing, or changing configuration files.

[0025] DID configuration is used to match the data reading, data writing, and actuator control functions required by the project. The data reading function reads bus values ​​from various temperature sensors, actuator feedback opening and voltage, blower speed, etc., as specified in the diagnostic questionnaire, converts these bus values ​​into corresponding physical values, and reports them. The data writing function translates physical values ​​such as VIN codes, fingerprint information, and configuration information and writes them to the slave device. The actuator control function performs various control operations on the various downstream actuators specified in the diagnostic questionnaire. Furthermore, all of the above DID configuration functions can be adjusted by modifying the configuration file to change the number of bytes, boundary values, offsets, and enumeration descriptions of the configured objects. The DID configuration process is as follows: The program begins importing DID configurations, including data read service configuration, data write service configuration, and strong control configuration. After importing, basic validity checks are performed on the imported parameters. If parameters are out of bounds or the data is invalid, the program will proceed to the end of initialization and report the reason for the initialization failure.

[0026] After the basic configuration data is imported, the program will configure the UDS layer response time, flow control frame timeout, maximum block size for consecutive frames, etc., based on the existing device connections and basic data. After the configuration is complete, the program will automatically generate buttons for data reading, data writing, and actuator control for various actuators based on the existing DID configuration, thus completing the import of the entire configuration file.

[0027] like Figure 2 The diagram illustrates the steps involved in reading and translating data. During data reading and other operations, the transmission and reception of UDS data involves processing and translating the bus values.

[0028] First, for the returned data, the program will segment different sub-signals by length using the configuration data. After segmentation, the program will index the configuration data and determine the data type of the current sub-data. If the current data is a character type, the entire data segment will be converted to ASCII.

[0029] If the data type is numeric, the segmented bytes are converted into the physical value of the sub-data using a conversion formula. After conversion, it is determined whether a mapping exists for the current sub-data data type. If no mapping exists, it is checked whether the current actual value is within the maximum or minimum range. If it exceeds the range, the data is padded with units and feedback is provided. If it does not exceed the range, units are padded and an out-of-range warning is issued. If a mapping exists, the mapping type is determined. If it is a direct mapping, it is checked whether a valid value exists. If a valid value exists, the mapping that matches the actual value is provided and feedback is given. If no valid mapping exists, the actual value is reported and an empty mapping warning is issued. If it is a bitwise mapping, the actual value is extracted bit by bit, and the corresponding values ​​are mapped one by one and feedback is provided.

[0030] like Figure 3 As shown, when writing data, the system first retrieves the DID configuration file for the data. Based on the configuration file, it determines the sub-data type of the data to be written. If the sub-data type is character, a text window and a corresponding identifier box are created. If it is numeric, it checks whether the sub-data is a mapped type. If the data is a mapped type, it reads the mapping parameters from the configuration file, renders the corresponding mapped selection box, and creates the corresponding identifier box. If it is not a mapped type, it creates an identifier box and a numeric input box, and limits the maximum and minimum values ​​of the numeric input box using parameters in the configuration file to prevent parameters from exceeding limits. This completes the rendering of the data writing box.

[0031] After the user completes and confirms the input, the program will identify each sub-data item in the data rendering box and determine the data type. If it is a character type, the text will be converted into a HEX value in ASCII format, and the number of bytes after conversion will be limited by the byte length in the DID configuration. If it is a numeric type, the program will further determine whether the sub-data type is a mapped type. If it is a mapped type, the mapped text will be reverse-converted; if it is not mapped text, the actual physical value will be converted into a bus value.

[0032] After the input data is bused, the program will read the configuration file to obtain the data for the preprocessing operation of writing to the bus. After each preprocessing operation is successful, the translated value will be uploaded to the bus and monitored. If there is a positive response, the program will respond with data; if there is no response or an error response, the program will report the error type. This completes the data writing process.

[0033] like Figure 4 As shown, during component control, the DID configuration file for the data is first retrieved. Based on the configuration file, the sub-data type of the written data is determined. If it is a numeric type, it is checked whether the sub-data is a mapping type. If the data is a mapping type, the corresponding mapping parameters in the configuration file are read, the corresponding mapping selection box is rendered, and a corresponding representation box is created. If it is not a mapping type, an identifier box is created, and the maximum and minimum values ​​of the selection box openings are limited by the parameters in the configuration file to prevent parameter out-of-bounds errors. This completes the rendering of the component control box openings. After the user completes and confirms the input, the program will identify each sub-data item in the data rendering box and determine the data type. If it is a character type, the text will be converted into a HEX value in ASCII format, and the number of bytes after conversion will be limited by the byte length in the DID configuration. If it is a numeric type, the program will further determine whether the sub-data type is a mapped type. If it is a mapped type, the mapped text will be reverse-converted; if it is not mapped text, the actual physical value will be converted into a bus value.

[0034] After the input data is bus-based, the program reads the configuration file to obtain the data for preprocessing operations on the bus. After each preprocessing operation is successful, the program uses the configuration file to determine whether a control mask is needed for the controlled component. If a control mask exists, the program fills in the corresponding mask according to the control sub-items, uploads the translated value to the bus, and listens for updates. If the response is positive, the program provides feedback on the control value; if the response is negative, the program provides feedback on the error type. This completes the forced control process.

[0035] like Figure 5 As shown, reading a DTC requires distinguishing between DTC types. After selecting the DTC type to read, a request message is constructed based on the corresponding service ID and uploaded to the bus to await a response. If there is no response or a negative response, feedback is provided according to the error type. If there is a positive response, the response data is retrieved, the DTC configuration is searched, and the DTC codes are matched one by one. If the corresponding DTC fault code exists in the DTC configuration, the corresponding DTC is matched and the corresponding DTC fault meaning is reported. If the DTC code does not exist in the DTC configuration, a warning is issued that the DTC configuration file is corrupt and the original DTC code is reported.

[0036] Example 2: An electronic device, comprising a memory and a processor; The memory is used to store computer programs; The processor is configured to implement the method described in Embodiment 1 when executing the computer program.

[0037] Example 3: A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in Embodiment 1.

[0038] Example 4: A computer program product includes a computer program that, when executed by a processor, implements the method described in Example 1.

[0039] In the above embodiments, the reference to "this embodiment" in the specification indicates that a specific feature, structure, or characteristic described in connection with the embodiment is included in at least some embodiments, but not necessarily all embodiments. Multiple appearances of "this embodiment" do not necessarily refer to the same embodiment.

[0040] In the above embodiments, although the invention has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory structures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed. The embodiments of the invention are intended to cover all such substitutions, modifications, and variations falling within the broad scope of the appended claims.

[0041] As will be understood by those skilled in the art, the computer-readable storage medium described in this embodiment allows for the implementation of all or part of the steps in the above method embodiments by computer program-related hardware. The aforementioned computer program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0042] The electronic terminal provided in this embodiment includes a processor, a memory, a transceiver, and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication between them. The memory is used to store computer programs, the communication interface is used to perform communication, and the processor and the transceiver are used to run the computer programs, so that the electronic terminal performs the steps of the above method.

[0043] In this embodiment, the memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0044] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0045] This invention can be used in a wide range of general-purpose or special-purpose computing system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices, etc.

[0046] This invention can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0047] Finally, 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 present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for matching a host computer with a diagnostic questionnaire based on a configuration file, characterized in that: Includes the following steps: Import configuration files: Select the appropriate configuration file based on the different diagnostic questionnaires, obtain the corresponding configuration file, and import and initialize it; Read the data, process and translate the bus values; Write the data; Control the components; Perform read detection on DTC.

2. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 1, characterized in that: The import configuration file specifically includes the following steps: S11: Select the configuration file according to different diagnostic questionnaires, and obtain the CANFD / CAN bus configuration, security algorithm configuration, DTC configuration, and DID configuration in the corresponding configuration file directory; S12: Import the basic configuration data, and then configure the UDS basic service based on the existing device connections and basic data; S13: Render read / write control function cases and their corresponding slot functions according to the configuration file.

3. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 2, characterized in that: The CANFD / CAN bus configuration is used to configure the physical address, functional address, response address, bus type for project communication and its matching baud rate, and hardware channel that match the diagnostic questionnaire. After the connection of the bus data acquisition device is completed, the device configuration, channel configuration, and address configuration of the bus data acquisition device are automatically completed according to the CANFD / CAN configuration file, realizing the association between the program and the hardware. The CANFD / CAN bus configuration import process includes: Start importing the CANFD / CAN bus configuration file, obtain the associated bus data acquisition device, and attempt to initialize the device and channel. If initialization fails, end the initialization process and report the reason for the initialization failure. If initialization is successful, match the baud rate and bus type between the device and the corresponding project.

4. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 2, characterized in that: The DID configuration is used to match the data reading function, data writing function, and actuator control function of the project requirements. The data reading function reads various temperature sensors, actuator feedback opening degree and voltage, and blower gear bus values ​​from the diagnostic questionnaire plan through the bus, and converts the bus values ​​into physical values ​​with corresponding physical meanings and reports them. The data writing function translates the VIN code, fingerprint information, and configuration information physical values ​​and writes them to the slave device. The actuator control can perform various control operations on the various types of attached actuators specified in the diagnostic questionnaire; The DID configuration import process includes: Import the DID data read service configuration, data write service configuration, and strong control configuration respectively; After the import is complete, perform basic validation of the imported parameters. If there are any issues with the configuration parameters, end the initialization process and report the reason for the initialization failure.

5. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 1, characterized in that: The process of reading data, processing and translating bus values ​​specifically includes the following steps: S21: Obtain the effective length of the bus feedback message data; S22: For the returned data, the different sub-signals are divided by length using the configuration data; S23: Index configuration file data, determine the data type of the current sub-data: If the current data is of character type, the entire data segment will be converted to ASCII. If the current data is a numeric type, the segmented bytes are converted into the physical value of the sub-data using a conversion formula. Then, it is determined whether the current sub-data data type has a mapping: if no mapping exists, it is determined whether the current real value is within the maximum and minimum range. If it exceeds the range, the data is padded with units and feedback is provided. If it does not exceed the range, an over-range warning is provided while padding with units. If a mapping exists, the mapping type is determined. If it is a direct mapping, it is determined whether the mapping has a valid value. If a valid value exists, feedback is provided based on the mapping matched with the real value. If no valid mapping exists, the real value is reported and an empty mapping warning is reported. If it is a bitwise mapping, the real value is extracted bit by bit and the corresponding values ​​are mapped one by one and feedback is provided.

6. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 1, characterized in that: The process of writing data specifically includes the following steps: S31: Obtain the DID configuration corresponding to the configuration file; S32: Determine the sub-data type of the data to be written based on the configuration file: if it is a character type, create a text window and a corresponding label box; if it is a numeric type, determine whether the sub-data is a mapping type: if the data is a mapping type, read the mapping parameters corresponding to the configuration file, render the corresponding mapping selection box, and create the corresponding label box; if the data is not a mapping type, create a label box and a numeric input box, and limit the maximum and minimum values ​​of the numeric input box using the parameters in the configuration file. This completes the rendering of the data writing box. S33: After the user completes and confirms the input, the system identifies each sub-data item in the data rendering box and determines the data type: if it is a character type, the text is converted into a HEX value in ASCII code form, and the number of bytes after conversion is limited by the byte length in the DID configuration; if it is a numeric type, the system determines whether the sub-data type is a mapping type: if it is a mapping type, the mapping text is reverse-converted; if it is not a mapping text, the real physical value is converted into a bus value. S34: After the input data is bused, the preprocessing operation of writing the data to the bus is performed. S35: After each preprocessing operation is successful, the translated value is uploaded to the bus and monitored. If there is a positive response, the data is fed back. If there is no response or an error response, the error type is fed back. The data writing is now complete.

7. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 1, characterized in that: The control of the components specifically includes the following steps: S41: Retrieve the DID configuration corresponding to the configuration file; S42: Determine the sub-data type of the written data based on the configuration file: If it is a numeric type, determine whether the sub-data is a mapping type. If the data is a mapping type, read the mapping parameters corresponding to the configuration file, render the corresponding mapping selection box, and create the corresponding representation box. If the data is not a mapping, create an identifier box and limit the maximum and minimum values ​​of the selection box opening through the parameters in the configuration file. This completes the rendering of the component control box opening. S43: After the user completes and confirms the input, the system identifies each sub-data item in the data rendering box and determines the data type: if it is a character type, the text is converted into a HEX value in ASCII code form, and the number of bytes after conversion is limited in combination with the byte length in the DID configuration; if it is a numeric type, the system determines whether the sub-data type is a mapping type: if it is a mapping type, the mapping text is reverse-converted; if it is not a mapping text, the real physical value is converted into a bus value. S44: After the input data is bused, perform the preprocessing operation to write the data to the bus; S45: After each preprocessing operation is successful, the configuration file is used to determine whether the control component needs a control mask; if a control mask exists, the corresponding mask is filled according to the control sub-item, and the translated value is uploaded to the bus and monitored; if it is a positive response, the control value is fed back, and if it is a negative response, the error type is fed back, thus completing the strong control.

8. The method for matching a host computer with a diagnostic questionnaire based on a configuration file according to claim 1, characterized in that: The process of reading and detecting DTC specifically includes the following steps: S51: Select the DTC type to be read, construct a request message based on the corresponding service ID, upload it to the bus and wait for a response; S52: If there is no response or a negative response, feedback will be provided based on the error type; If the response is positive, the response data is obtained, the DTC configuration is retrieved, and the DTC codes are matched one by one. If the corresponding DTC fault code exists in the DTC configuration, the corresponding DTC is matched and the corresponding DTC fault meaning is reported. If the DTC code does not exist in the DTC configuration, a warning is issued that the DTC configuration file is missing and the original DTC code is reported.

Images