A method and system for reading controller data based on DoIP

Abstract

The present invention relates to a method and system for reading controller data based on DoIP, the method comprising the following steps: a host computer sends a directory request 0X38 service to a controller; the controller sends a directory request response 0X78 to the host computer; the host computer sends a directory information request 0X36 service to the controller; the controller sends a directory information request response 0X76 to the host computer; the host computer sends a transmission termination request 0X37 service to the controller; the controller sends a transmission termination request response 0X77 to the host computer to complete the directory transmission; the host computer sends a file request 0X38 service to the controller; the controller sends a file request response 0X78 to the host computer; the host computer sends a file data request 0X36 service to the controller; the controller sends a file data request response 0X76 to the host computer; the host computer sends a transmission termination request 0X37 to the controller; the controller sends a transmission termination request response 0X77 to the host computer, and the file transmission is completed. The present invention facilitates engineers to analyze the controller situation and improves the efficiency of problem solving.

Description

Technical Field

[0001] The present invention relates to the technical field of autonomous driving vehicles, and in particular to a technology for reading controller data based on DoIP. Background Art

[0002] Nowadays, automobile controllers are no longer single MCUs, but hybrid operating systems with MPUs and MCUs. When the controller is working, a large amount of data is exchanged between the MCU and MPU, and logs are stored inside the controller. During the controller development phase, when testers find abnormalities in the software functions inside the controller, they cannot directly read the relevant log data from the controller to analyze the problem. They need to give the controller to developers for data reading. When developers read data files, they need to enter multiple shell commands to read the relevant data. The problem is that it takes a long time to obtain log files, the process is cumbersome, and the problem analysis efficiency is low, which in turn affects the product development progress. Summary of the invention

[0003] The purpose of the present invention is to provide a method and system for reading controller data based on DoIP, and to solve the following technical problems:

[0004] When testers discover that the software functions inside the controller are abnormal, they cannot directly read the relevant log data of the controller. When developers are asked to read the data, they also have to enter instructions to read the relevant data. It takes a long time to obtain data and the process is cumbersome, resulting in low efficiency in analyzing problems, which in turn affects the progress of product development.

[0005] In order to solve the above technical problems, the technical solution adopted by the present invention is: a method for reading controller data based on DoIP, comprising the following steps:

[0006] S01: The host computer sends a directory request 0X38 service to the controller;

[0007] S02: The host computer receives a directory request response 0X78 sent by the controller;

[0008] S03: The host computer sends a directory information request 0X36 service to the controller;

[0009] S04: The host computer receives the directory information response 0X76 initiated by the controller;

[0010] S05: The host computer sends a transmission termination request 0X37 service to the controller;

[0011] S06: The host computer receives the transmission termination response 0X77 sent by the controller, and completes the directory transmission;

[0012] S07: The host computer sends a file request OX38 service to the controller;

[0013] S08: The host computer receives the file request response 0X78 sent by the controller;

[0014] S09: The host computer sends a file data request 0X36 service to the controller;

[0015] S10: The host computer receives the file data request response 0X76 sent by the controller;

[0016] S11: looping through S09 to S10 until all requested file transfers are completed;

[0017] S12: The host computer sends a transmission termination request 0X37 service to the controller;

[0018] S13: The host computer receives the transmission termination request response 0X77 sent by the controller, and the file transfer is completed.

[0019] Preferably,

[0020] In S08, the response sent by the controller also includes a file request denial response, which includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted.

[0021] Preferably,

[0022] In S10, the response sent by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming failure, and error block sequence counter.

[0023] Preferably,

[0024] In S13, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0025] The present invention also provides a method for reading controller data based on DoIP, comprising the following steps:

[0026] A01: The controller receives the directory request sent by the host computer;

[0027] A02: The controller sends a directory request response 0X78 to the host computer;

[0028] A03: The controller receives a directory information request sent by the host computer;

[0029] A04: The controller sends a directory information request response 0X76 to the host computer;

[0030] A05: the controller receives a transmission termination request sent by the host computer;

[0031] A06: The controller sends a transmission termination response 0X77 to the host computer to complete the directory transmission;

[0032] A07: The controller receives a file request sent by the host computer;

[0033] A08: The controller sends a file request response 0X78 to the host computer;

[0034] A09: The controller receives a file data request sent by the host computer;

[0035] A10: The controller sends a file data request response 0X76 to the host computer;

[0036] A11: looping through A09 to A10 until all the requested files are transferred.

[0037] A12: The controller receives a transmission termination request sent by the host computer;

[0038] A13: The controller sends a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

[0039] Preferably,

[0040] In A08, the response sent by the controller also includes a negative response to the file request, and the negative response to the file request includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted.

[0041] Preferably,

[0042] In A10, the response sent by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming fault, and error block sequence counter.

[0043] Preferably,

[0044] In A13, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0045] The present invention also provides a method for reading controller data based on DoIP, comprising the following steps:

[0046] B01: The host computer sends a directory request 0X38 service to the controller;

[0047] B02: The controller sends a directory request response 0X78 to the host computer;

[0048] B03: The host computer sends a directory information request 0X36 service to the controller;

[0049] B04: The controller sends a directory information request response 0X76 to the host computer;

[0050] B05: The host computer sends a transmission termination request 0X37 service to the controller;

[0051] B06: The controller sends a transmission termination request response 0X77 to the host computer to complete the directory transmission;

[0052] B07: The host computer sends a file request 0X38 service to the controller;

[0053] B08: The controller sends a file request response 0X78 to the host computer;

[0054] B09: The host computer sends a file data request 0X36 service to the controller;

[0055] B10: The controller sends a file data request response 0X76 to the host computer;

[0056] B11: cyclically executing B09 to B10 until all the requested file transfers are completed;

[0057] B12: The host computer sends a transmission termination request 0X37 to the controller;

[0058] B13: The controller sends a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

[0059] Preferably,

[0060] In B08, the response sent by the controller also includes a negative response to the file request, and the negative response to the file request includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted.

[0061] Preferably,

[0062] In B10, the response initiated by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming failure, and error block sequence counter.

[0063] Preferably,

[0064] In B13, the response sent by the controller also includes a negative response to the transmission termination request, and the negative response to the transmission termination request includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0065] The present invention also provides a system for reading controller data based on DoIP, comprising a host computer and a controller, wherein the host computer and the controller communicate with each other via Ethernet, and the system further comprises:

[0066] The first sending module is used for the host computer to send a directory request 0X38 service to the controller;

[0067] The second sending module is used for the controller to send a directory request response 0X78 to the host computer;

[0068] The third sending module is used for the host computer to send a directory information request 0X36 service to the controller;

[0069] The fourth sending module is used for the controller to send a directory information request response 0X76 to the host computer;

[0070] A fifth sending module, used for the host computer to send a transmission termination request 0X37 service to the controller;

[0071] A sixth sending module, used for the controller to send a transmission termination request response 0X77 to the host computer;

[0072] A seventh sending module, used for the host computer to send a file request 0X38 service to the controller;

[0073] An eighth sending module, used for the controller to send a file request response 0X78 to the host computer;

[0074] A ninth sending module, used for the host computer to send a file data request 0X36 service to the controller;

[0075] A tenth sending module, used for the controller to send a file data request response 0X76 to the host computer;

[0076] A loop module, used for looping the ninth sending module to the tenth sending module until all the requested file transmissions are completed;

[0077] An eleventh sending module, used for the host computer to send a transmission termination request 0X37 to the controller;

[0078] The twelfth sending module is used for the controller to send a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

[0079] Preferably,

[0080] In the eighth sending module, the response sent by the controller also includes a file request negative response, and the file request negative response includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download are not accepted.

[0081] Preferably,

[0082] In the tenth sending module, the response initiated by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming failure, and error block sequence counter.

[0083] Preferably,

[0084] In the twelfth sending module, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0085] By adopting the above technical scheme, the beneficial technical effects that can be achieved by the present invention are as follows: the present invention reads the black box data of the automobile controller through the UDS protocol, which is convenient for developers and testers to analyze the working conditions of the controller and improves the efficiency of engineers in analyzing and solving problems. The present invention is universal and applicable to all controllers based on vehicle Ethernet. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] Figure 1 Connect the view to the device;

[0087] Figure 2 This is the software block diagram of the host computer;

[0088] Figure 3 Request a directory flow chart;

[0089] Figure 4 Request file flow chart. DETAILED DESCRIPTION

[0090] The present invention will be further described below in conjunction with the accompanying drawings.

[0091] like Figure 1 and Figure 2As shown, the present invention provides a method for reading controller data based on DoIP, the host computer communicates with the controller through Ethernet, and a 12V power supply is used to power the controller to ensure the normal operation of the controller.

[0092] The host computer is installed with software for reading the internal data of the controller. The software saves the read data in TXT format in the set target path.

[0093] like Figure 2 As shown in the figure, it is the front-end interface of the software. The software includes a basic information setting module, a button area module, and a print area module. The basic information setting module can obtain the IP address of the computer where the software is located, supports the selection of different controller objects, and can set the internal path, file name, and save target path of the data file to be read in the controller; the button area module has query, read, exit, and clear information buttons. The trigger query button can read the file directory information under the specified path of the controller, and the trigger read button can read the data information under different file names under the specified directory into a new TXT document and save it in the specified path. The exit button is used to close the upper computer software, and the clear information button is used to clear the information recorded in the print area; the print area module is used to display the controller's internal directory information, the read data information, the log information fed back by the controller, etc.

[0094] Specifically, the basic information setting module supports the selection of different lower-level computer objects, such as driving controller, parking controller, and gateway; it can automatically obtain the IP address of the computer where the upper-level computer software is located, so that engineers can quickly confirm whether the upper-level computer and the lower-level computer belong to the same network segment; the paths where general data files exist are " / misc / adr", " / misc / adr / run_dog", and " / misc / adr / event_log". Fill in the read data file path name in the data file path text box, and use the read button to obtain all data file names under the path; the file name text box is used to fill in the name of the data file you want to read, such as " / xcu8.0_app_ca.bin.zip.sign"; the log path text box is used to set the path for saving data files, and the path format uses an absolute path, such as "F:DoIP\dist\test.txt". The query button in the button area is used to trigger the process, send the directory query instruction, and read the file directory information under the specified path of the controller; the read button triggers the process, sends the read file name, data file save path, and obtains the file size and other information, reads the data information under different file names in the specified directory into a new TXT document and saves it in the specified path; the exit button is used to close the upper computer software; the clear information button realizes the function of clearing the record information in the print area. The print area is used to display the controller's internal directory information, the read data information, the log information fed back by the controller, etc.

[0095] like Figure 3 and Figure 4 As shown, the present invention provides a method for reading controller data based on DoIP, comprising the following steps:

[0096] S01: The host computer sends a directory request 0X38 service to the controller;

[0097] S02: The host computer receives the directory request response 0X78 sent by the controller;

[0098] S03: The host computer sends a directory information request 0X36 service to the controller;

[0099] S04: The host computer receives the directory information response 0X76 initiated by the controller;

[0100] S05: The host computer sends a transmission termination request 0X37 service to the controller;

[0101] S06: The host computer receives the transmission termination response 0X77 sent by the controller and completes the directory transmission;

[0102] S07: The host computer sends a file request OX38 service to the controller;

[0103] S08: The host computer receives the file request response 0X78 sent by the controller;

[0104] S09: The host computer sends a file data request 0X36 service to the controller;

[0105] S10: The host computer receives the file data request response 0X76 sent by the controller;

[0106] S11: looping through S09 to S10 until all requested file transfers are completed;

[0107] S12: The host computer sends a transmission termination request 0X37 service to the controller;

[0108] S13: The host computer receives the transmission termination request response 0X77 sent by the controller, and the file transfer is completed.

[0109] Specifically,

[0110] In S08, the response sent by the controller also includes a negative response to the file request, which includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted.

[0111] Specifically,

[0112] In S10, the response sent by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming fault, and error block sequence counter.

[0113] Specifically,

[0114] In S13, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0115] The present invention also provides a method for reading controller data based on DoIP, comprising the following steps:

[0116] A01: The controller receives the directory request sent by the host computer;

[0117] A02: The controller sends a directory request response 0X78 to the host computer;

[0118] A03: The controller receives the directory information request sent by the host computer;

[0119] A04: The controller sends a directory information request response 0X76 to the host computer;

[0120] A05: The controller receives a transmission termination request sent by the host computer;

[0121] A06: The controller sends a transmission termination response 0X77 to the host computer to complete the directory transmission;

[0122] A07: The controller receives the file request sent by the host computer;

[0123] A08: The controller sends a file request response 0X78 to the host computer;

[0124] A09: The controller receives the file data request sent by the host computer;

[0125] A10: The controller sends a file data request response 0X76 to the host computer;

[0126] A11: loops through A09 to A10 until all requested file transfers are completed;

[0127] A12: The controller receives the transmission termination request sent by the host computer;

[0128] A13: The controller sends a transfer termination request response 0X77 to the host computer, and the file transfer is completed.

[0129] Specifically,

[0130] In A08, the response sent by the controller also includes a negative response to the file request, which includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted.

[0131] Specifically,

[0132] In A10, the response sent by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming fault, and error block sequence counter.

[0133] Specifically,

[0134] In A13, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0135] The present invention also provides a method for reading controller data based on DoIP, comprising the following steps:

[0136] B01: The host computer sends a directory request 0X38 service to the controller;

[0137] B02: The controller sends a directory request response 0X78 to the host computer;

[0138] B03: The host computer sends a directory information request 0X36 service to the controller;

[0139] B04: The controller sends a directory information request response 0X76 to the host computer;

[0140] B05: The host computer sends a transmission termination request 0X37 service to the controller;

[0141] B06: The controller sends a transmission termination request response 0X77 to the host computer to complete the directory transmission;

[0142] B07: The host computer sends a file request 0X38 service to the controller;

[0143] B08: The controller sends a file request response 0X78 to the host computer;

[0144] B09: The host computer sends a file data request 0X36 service to the controller;

[0145] B10: The controller sends a file data request response 0X76 to the host computer;

[0146] B11: loop through B09 to B10 until all requested file transfers are completed;

[0147] B12: The host computer sends a transmission termination request 0X37 to the controller;

[0148] B13: The controller sends a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

[0149] Specifically,

[0150] In B08, the response sent by the controller also includes a negative response to the file request, which includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted.

[0151] Specifically,

[0152] In B10, the response initiated by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming fault, and error block sequence counter.

[0153] Specifically,

[0154] In B13, the response sent by the controller also includes a negative response to the transmission termination request, and the negative response to the transmission termination request includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

[0155] The present invention also provides a system for reading controller data based on DoIP, including a host computer and a controller, the host computer and the controller communicate with each other via Ethernet, and the system also includes:

[0156] The first sending module is used for the host computer to send a directory request 0X38 service to the controller;

[0157] The second sending module is used for the controller to send a directory request response 0X78 to the host computer;

[0158] The third sending module is used for the host computer to send a directory information request 0X36 service to the controller;

[0159] The fourth sending module is used for the controller to send a directory information request response 0X76 to the host computer;

[0160] The fifth sending module is used for the host computer to send a transmission termination request 0X37 service to the controller;

[0161] The sixth sending module is used for the controller to send a transmission termination request response 0X77 to the host computer;

[0162] The seventh sending module is used for the host computer to send a file request 0X38 service to the controller;

[0163] An eighth sending module is used for the controller to send a file request response 0X78 to the host computer;

[0164] The ninth sending module is used for the host computer to send file data request 0X36 service to the controller;

[0165] The tenth sending module is used for the controller to send a file data request response 0X76 to the host computer;

[0166] A loop module, used for looping the ninth sending module to the tenth sending module until all the requested file transfers are completed;

[0167] The eleventh sending module is used for the host computer to send a transmission termination request 0X37 to the controller;

[0168] The twelfth sending module is used for the controller to send a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

[0169] Specifically,

[0170] In the eighth sending module, the response sent by the controller also includes a negative response to the file request, and the negative response to the file request includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download are not accepted.

[0171] Specifically,

[0172] In the tenth sending module, the response initiated by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming fault, and error block sequence counter.

[0173] Specifically,

[0174] In the twelfth sending module, the response sent by the controller also includes a negative response to the transmission termination request, and the negative response to the transmission termination request includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

Claims

1. A method for reading controller data based on DoIP, characterized in that: The following steps are involved: S01: The host computer sends a directory request 0X38 service to the controller; S02: The host computer receives a directory request response 0X78 sent by the controller; S03: The host computer sends a directory information request 0X36 service to the controller; S04: The host computer receives the directory information response 0X76 initiated by the controller; S05: The host computer sends a transmission termination request 0X37 service to the controller; S06: The host computer receives the transmission termination response 0X77 sent by the controller, and completes the directory transmission; S07: The host computer sends a file request OX38 service to the controller; S08: The host computer receives the file request response 0X78 and the file request negative response sent by the controller, and the file request negative response includes: incorrect message length or invalid format, incorrect condition, request timeout limit, security access denied, and upload and download are not accepted; S09: The host computer sends a file data request 0X36 service to the controller; S10: The host computer receives the file data request response 0X76 sent by the controller; S11: looping through S09 to S10 until all requested file transfers are completed; S12: The host computer sends a transmission termination request 0X37 service to the controller; S13: The host computer receives the transmission termination request response 0X77 sent by the controller, and the file transfer is completed.

2. The method for reading controller data based on DoIP according to claim 1, characterized in that: In S10, the response sent by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming failure, and error block sequence counter.

3. The method for reading controller data based on DoIP according to claim 1, characterized in that: In S13, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

4. A method for reading controller data based on DoIP, characterized in that: The following steps are involved: A01: The controller receives the directory request sent by the host computer; A02: The controller sends a directory request response 0X78 to the host computer; A03: The controller receives a directory information request sent by the host computer; A04: The controller sends a directory information request response 0X76 to the host computer; A05: the controller receives a transmission termination request sent by the host computer; A06: The controller sends a transmission termination response 0X77 to the host computer to complete the directory transmission; A07: The controller receives a file request sent by the host computer; A08: The controller sends a file request response 0X78 and a file request negative response to the host computer; The negative response to the file request includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted; A09: The controller receives a file data request sent by the host computer; A10: The controller sends a file data request response 0X76 to the host computer; A11: looping through A09 to A10 until all the requested files are transferred. A12: The controller receives a transmission termination request sent by the host computer; A13: The controller sends a transfer termination request response 0X77 to the host computer, and the file transfer is completed.

5. The method for reading controller data based on DoIP according to claim 4, characterized in that: In A10, the response sent by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming fault, and error block sequence counter.

6. The method for reading controller data based on DoIP according to claim 4, characterized in that: In A13, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

7. A method for reading controller data based on DoIP, characterized in that: The following steps are involved: B01: The host computer sends a directory request 0X38 service to the controller; B02: The controller sends a directory request response 0X78 to the host computer; B03: The host computer sends a directory information request 0X36 service to the controller; B04: The controller sends a directory information request response 0X76 to the host computer; B05: The host computer sends a transmission termination request 0X37 service to the controller; B06: The controller sends a transmission termination request response 0X77 to the host computer to complete the directory transmission; B07: The host computer sends a file request 0X38 service to the controller; B08: The controller sends a file request response 0X78 and a file request negative response to the host computer; The negative response to the file request includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download not accepted; B09: The host computer sends a file data request 0X36 service to the controller; B10: The controller sends a file data request response 0X76 to the host computer; B11: cyclically executing B09 to B10 until all the requested file transfers are completed; B12: The host computer sends a transmission termination request 0X37 to the controller; B13: The controller sends a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

8. The method for reading controller data based on DoIP according to claim 7, characterized in that: In B10, the response initiated by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming failure, and error block sequence counter.

9. The method for reading controller data based on DoIP according to claim 7, characterized in that: In B13, the response sent by the controller also includes a negative response to the transmission termination request, and the negative response to the transmission termination request includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

10. A system for reading controller data based on DoIP, characterized in that: The system comprises a host computer and a controller, wherein the host computer and the controller communicate with each other via Ethernet. The system further comprises: The first sending module is used for the host computer to send a directory request 0X38 service to the controller; The second sending module is used for the controller to send a directory request response 0X78 to the host computer; The third sending module is used for the host computer to send a directory information request 0X36 service to the controller; The fourth sending module is used for the controller to send a directory information request response 0X76 to the host computer; A fifth sending module, used for the host computer to send a transmission termination request 0X37 service to the controller; A sixth sending module, used for the controller to send a transmission termination request response 0X77 to the host computer; A seventh sending module, used for the host computer to send a file request 0X38 service to the controller; An eighth sending module is used for the controller to send a file request response 0X78 and a file request negative response to the host computer; the file request negative response includes: incorrect message length or invalid format, incorrect conditions, request timeout limit, security access denied, and upload and download are not accepted; A ninth sending module, used for the host computer to send a file data request 0X36 service to the controller; A tenth sending module, used for the controller to send a file data request response 0X76 to the host computer; A loop module, used for looping the ninth sending module to the tenth sending module until all the requested file transmissions are completed; An eleventh sending module, used for the host computer to send a transmission termination request 0X37 to the controller; The twelfth sending module is used for the controller to send a transmission termination request response 0X77 to the host computer, and the file transfer is completed.

11. The system for reading controller data based on DoIP according to claim 10, characterized in that: In the tenth sending module, the response initiated by the controller also includes a file data request negative response, and the file data request negative response includes: incorrect message length or invalid format, request sequence error, request exceeds limit, general programming failure, and error block sequence counter.

12. The system for reading controller data based on DoIP according to claim 10, characterized in that: In the twelfth sending module, the response sent by the controller also includes a transmission termination request negative response, and the transmission termination request negative response includes: incorrect message length, request sequence error, request exceeds limit, and general programming failure.

Images