A method for analyzing data frame reporting of excavator Tbox equipment

Abstract

The present invention relates to the technical field of excavator data information transmission, and specifically, to an excavator Tbox device data frame reporting and parsing algorithm, comprising the following steps: S1: the Tbox device accesses a vehicle networking gateway platform through a fixed external network mapping address, and sends the collected data information to the vehicle networking gateway platform; S2: the vehicle networking gateway platform determines whether the data format uploaded by the Tbox device meets the requirements through the data upload format, wherein data that does not meet the format requirements is rejected; in summary, the beneficial effects of the present invention are: the present invention simplifies the data stream upload process, improves the upload efficiency, and effectively reduces the failure rate, specifies the device data upload format during the upload, prevents malicious device data from being uploaded, and improves data authenticity, the byte stream parsing method improves the data parsing accuracy, reduces the network interaction process, and facilitates timely viewing of the vehicle operation status and timely troubleshooting.

Description

Technical Field

[0001] The present invention relates to the technical field of excavator data information transmission, and in particular to a method for reporting and parsing data frames of an excavator Tbox device. Background Art

[0002] When the engineering vehicle Tbox on-board equipment reports the vehicle's various performance parameters, after collecting the vehicle's various parameters, it uses hexadecimal byte data to establish a link based on the TCP / IP protocol, compiles it using a fixed data format, and uploads the vehicle's real-time data information to the Netty framework technology to build a network program. It uses byte data parsing methods to convert hexadecimal vehicle real-time data into decimal visual data for platform data display and calculation.

[0003] However, in the existing technology, a Web application needs to be developed on the device side and a specific server needs to be run. The transmission method of sending command information through the HTTP / IP interface is inefficient and is greatly affected by the network and server, resulting in a high failure rate. The data collected by the device cannot be sent directly to the Internet of Vehicles platform, but is compiled and sent through a specific application. There is a risk of data tampering, which reduces the real-time and accuracy of the data. Summary of the invention

[0004] The purpose of the present invention is to provide a method for reporting and parsing data frames of an excavator Tbox device in view of the above problems, so as to solve the problems of low efficiency and high failure rate when the TBOX device uploads real-time data to the Internet of Vehicles platform.

[0005] To achieve the above object, the present invention discloses a method for analyzing data frame reporting of an excavator Tbox device, which is characterized by comprising the following steps:

[0006] S1: The Tbox device accesses the Internet of Vehicles gateway platform through a fixed external network mapping address, and sends the collected data information to the Internet of Vehicles gateway platform;

[0007] S2: The Internet of Vehicles gateway platform determines whether the format of data uploaded by the Tbox device meets the requirements based on the data upload format. Data that does not meet the format requirements will be rejected;

[0008] S3: The IoV parses the terminal data information that meets the requirements into readable information and stores it on the IoV big data platform;

[0009] Among them, when the Internet of Vehicles gateway platform in S2 receives the byte data string uploaded by Tbox, it splits the string according to a fixed format. The splitting module includes mechanical environmental protection code, data collection time, data unit, vehicle code, positioning information and information type flag, which meets the data format requirements of the above modules and receives data.

[0010] Preferably, in S3, data information parsing includes the following steps:

[0011] 1) According to the parsing format, the real-time data information is divided into TBOX data information, data stream information, ECU data information, MCU data information, TCU data information, HMI data information, and other data information data packets;

[0012] 2) Different data packets are transmitted to the corresponding parsing methods respectively. According to the data format requirements, the hexadecimal information is converted into decimal information by queuing and intercepting fixed-length parsing. The data is then operated on the offset and precision according to the format requirements and stored in the data field respectively.

[0013] 3) After each data packet is parsed, the parsed data fields are sorted and written into Json data for unified packaging, and sent to the Internet of Vehicles big data platform Kafka (information storage middleware) for storage through a fixed address.

[0014] Preferably, the splitting requirement of the mechanical environmental protection code is: the terminal device combines the WMC, MDS, CI and MIS data information uploaded by the vehicle into a 17-bit code, and uploads it using the ASCII code character comparison relationship. The platform parses it according to the ASCII code character table to determine whether it meets the requirements.

[0015] Preferably, the splitting requirement of the data collection time is: the device compiles the current time when the data is collected into 6 bytes of hexadecimal data, and the platform parses each byte into decimal data and splices them into the specific time year-month-day, hour-minute-second, and compares it with the data reception time. If the collection time is later than the data reception time, it is deemed to not meet the requirements.

[0016] Preferably, the splitting of the data unit meets the following requirements according to the encoding:

[0017] The code is 0x02, which is defined as real-time information reporting;

[0018] The code is 0x03, which is defined as re-issuance of information report.

[0019] Preferably, the splitting requirements of the vehicle code and positioning information are: converting the hexadecimal positioning information uploaded by the device into decimal data, multiplying by 0.000001° accuracy, and calculating the longitude and latitude information.

[0020] Preferably, the information type mark module data encoding needs to meet the following data range: encoding 0x81 is TBOX data information; encoding 0x82 is data stream information; encoding 0x85 is excavator ECU information; encoding 0x86 is excavator MCU / HMI information; encoding 0x87 is other excavator data information; encoding 0x9A is whole machine fault information.

[0021] Preferably, the parsing methods corresponding to different data packets include:

[0022] Numerical analysis method: Convert hexadecimal data into decimal data, and then calculate according to the accuracy and offset required by the platform protocol. The specific formula is:

[0023] Result = decimal data * precision + offset + unit, where the unit includes temperature and percentage;

[0024] Character parsing method: The encoding and version number data information is parsed using the ASCII code parsing method and displayed using the UTF-8 character set. The specific method is:

[0025] Result = ASCII code character comparison table * data information;

[0026] Type parsing method: After converting the hexadecimal data into decimal data, match the corresponding result set according to the value in it;

[0027] Binary high and low bit parsing method: Convert the hexadecimal data uploaded by the device into 8-bit binary data, extract every two or three bits of data, fill the high bit with 0 to 8 bits, and then convert it into decimal data. Calculate according to the accuracy and offset required by the platform protocol. The specific formula is:

[0028] Result = Binary data with high digits filled with 0 >>> Decimal data * precision + offset;

[0029] Vehicle fault analysis method: Fault information is transmitted using 4-byte data. First, the 4-byte data is converted into 8-bit binary data, and then the SPN code and FMI code in the fault are spliced ​​in the following format and converted into decimal data for display. The 4th byte is converted into a decimal fault number separately.

[0030] Preferably, the specific parsing method for the overseas positioning data being invalid data is: longitude = decimal longitude*0.000001, latitude = decimal latitude*0.000001.

[0031] In summary, the beneficial effects of the present invention are:

[0032] The present invention simplifies the data stream upload process, improves the upload efficiency, and effectively reduces the failure rate. The device data upload format is specified during the upload to prevent malicious device data from being uploaded and improve data authenticity. The byte stream parsing method improves data parsing accuracy and reduces the network interaction process, making it convenient to check the vehicle operation status in a timely manner and troubleshoot in a timely manner. DETAILED DESCRIPTION

[0033] The specific implementation of the present invention is further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0034] A method for analyzing data frames reported by a Tbox device of an excavator, comprising the following steps:

[0035] S1: The Tbox device accesses the Internet of Vehicles gateway platform through a fixed external network mapping address, and sends the collected data information to the Internet of Vehicles gateway platform. The access protocol adopts the TCP / IP protocol;

[0036] The device uploads the compiled hexadecimal byte data string to the Internet of Vehicles gateway platform via external network traffic to the external network mapping address provided in step 1.

[0037] S2: The Internet of Vehicles gateway platform determines whether the data format uploaded by the Tbox device meets the requirements based on the data upload format. Data that does not meet the format requirements will be rejected.

[0038] When the Internet of Vehicles gateway platform receives the byte data string uploaded by Tbox, it will split the string according to the fixed format, specifically into module data such as data collection time, data unit, vehicle code, positioning information, information type flag, etc. The conditions that need to be met are as follows:

[0039] 1. The data collection time is valid and cannot be later than the current data reception time.

[0040] 2. The data unit content must be within a specific range

[0041] 3. The vehicle code meets the requirements of vehicle networking coding to prevent garbled codes

[0042] 4. The positioning information must be valid domestic positioning information

[0043] 5. Information type mark information numbers must be within a specific range

[0044] 6. The length of the data string must be consistent with the data length required by the Internet of Vehicles

[0045] All the above conditions must be met, otherwise the Internet of Vehicles Gateway Platform will directly reject the message and stop parsing.

[0046] S3: The Internet of Vehicles parses the terminal data information that meets the requirements into readable information and stores it on the Internet of Vehicles big data platform.

[0047] In S3, data information parsing includes the following steps:

[0048] 1) According to the parsing format, the real-time data information is divided into TBOX data information, data stream information, ECU data information, MCU data information, TCU data information, HMI data information, and other data information data packets;

[0049] 2) Different data packets are transmitted to the corresponding parsing methods respectively. According to the data format requirements, the hexadecimal information is converted into decimal information by queuing and intercepting fixed-length parsing. The data is then operated on the offset and precision according to the format requirements and stored in the data field respectively.

[0050] 3) After each data packet is parsed, the parsed data fields are sorted and written into Json data for unified packaging, and sent to the Internet of Vehicles big data platform Kafka (information storage middleware) for storage through a fixed address.

[0051] The splitting of the mechanical environmental protection code meets the following requirements:

[0052] The terminal device combines the WMC, MDS, CI and MIS data information uploaded by the vehicle into a 17-bit code and uploads it using the ASCII code character comparison relationship. The platform parses it according to the ASCII code character table to meet the mechanical environmental protection code requirements.

[0053] The splitting of the data collection time meets the following requirements:

[0054] The device compiles the current time when data is collected into 6-byte hexadecimal data. The platform parses each byte into decimal data and splices them into the specific time of year-month-day, hour-minute-second, and compares it with the data reception time. If the collection time is later than the data reception time, it is considered not meeting the requirements.

[0055] The splitting of the data unit meets the following requirements according to the encoding:

[0056] The code is 0x02, which is defined as real-time information reporting;

[0057] The code is 0x03, which is defined as re-issuance of information report.

[0058] The separation of the vehicle code and positioning information meets the following requirements:

[0059] Convert the hexadecimal positioning information uploaded by the device into decimal data, multiply it by 0.000001° accuracy, and calculate the longitude and latitude information.

[0060] Among them, the specific analysis method for the overseas positioning data as invalid data is: longitude = decimal longitude*0.000001, latitude = decimal latitude*0.000001.

[0061] The data encoding of the information type mark module needs to meet the following data range:

[0062]

[0063] The corresponding parsing methods of different data packets include:

[0064] (1) Numerical parsing method: convert hexadecimal data into decimal data, and then calculate according to the accuracy and offset required by the platform protocol. The specific formula is:

[0065] Result = decimal data * precision + offset + unit, where the unit includes temperature and percentage.

[0066] (2) Character parsing method: the encoding and version number data information is parsed using the ASCII code parsing method and displayed using the UTF-8 character set. The specific method is as follows:

[0067] Result = ASCⅡ code character comparison table * data information.

[0068] (3) Type parsing method: After converting the hexadecimal data into decimal data, the corresponding result set is matched according to the value in it, for example:

[0069] Working gear information: 00: 1st gear; 01: 2nd gear; 02: 3rd gear; 03: 4th gear; 04: 5th gear; 05: 6th gear.

[0070] (4) Binary high and low bit parsing method: convert the hexadecimal data uploaded by the device into 8-bit binary data, extract every two or three bits of data, fill the high bit with 0 to 8 bits, and then convert it into decimal data. Calculate it according to the accuracy and offset required by the platform protocol. The specific formula is:

[0071] Result = binary data with high-order 0s added >>> decimal data * precision + offset.

[0072] (5) Vehicle fault analysis method: fault information is transmitted in 4-byte data. First, the 4-byte data is converted into 8-bit binary data. Then, the SPN code and FMI code in the fault are spliced ​​in the following format and converted into decimal data for display. The 4th byte is converted into the decimal fault number separately. The specific format is as follows:

[0073]

[0074] When FF or FE data items are passed in the original data, they are regarded as invalid data and are not parsed or calculated.

[0075] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and substitutions can be made without departing from the technical principles of the present invention. These improvements and substitutions should also be regarded as the scope of protection of the present invention.

Claims

1. A method for analyzing data frames reported by Tbox equipment of an excavator, characterized in that: The steps include: S1: The Tbox device accesses the Internet of Vehicles gateway platform through a fixed external network mapping address, and sends the collected data information to the Internet of Vehicles gateway platform; S2: The Internet of Vehicles gateway platform determines whether the format of data uploaded by the Tbox device meets the requirements based on the data upload format. Data that does not meet the format requirements will be rejected; S3: The IoV parses the terminal data information that meets the requirements into readable information and stores it on the IoV big data platform; Among them, when the Internet of Vehicles gateway platform in S2 receives the byte data string uploaded by Tbox, it splits the string according to a fixed format. The splitting module includes mechanical environmental protection code, data collection time, data unit, vehicle code, positioning information and information type flag. It meets the data format requirements of the above modules and receives data; In S3, data information parsing includes the following steps: 1) According to the parsing format, the real-time data information is divided into TBOX data information, data stream information, ECU data information, MCU data information, TCU data information, HMI data information, and other data information data packets; 2) Different data packets are transmitted to the corresponding parsing methods respectively. According to the data format requirements, the hexadecimal information is converted into decimal information by queuing and intercepting fixed-length parsing. The data is then operated on the offset and precision according to the format requirements and stored in the data field respectively. 3) After each data packet is parsed, the parsed data fields are sorted and written into Json data for unified packaging, and sent to the Internet of Vehicles big data platform Kafka (information storage middleware) for storage through a fixed address; The corresponding parsing methods of different data packets include: Numerical analysis method: Convert hexadecimal data into decimal data, and then calculate according to the accuracy and offset required by the platform protocol. The specific formula is: Result = decimal data * precision + offset + unit, where the unit includes temperature and percentage; Character parsing method: The encoding and version number data information is parsed using the ASCII code parsing method and displayed using the UTF-8 character set. The specific method is: Result = ASCII code character comparison table * data information; Type parsing method: After converting the hexadecimal data into decimal data, match the corresponding result set according to the value in it; Binary high and low bit parsing method: Convert the hexadecimal data uploaded by the device into 8-bit binary data, extract every two or three bits of data, fill the high bit with 0 to 8 bits and then convert it into decimal data, and calculate it according to the accuracy and offset required by the platform protocol. The specific formula is: Result = Binary data with high digits filled with 0 >>> Decimal data * precision + offset; Vehicle fault analysis method: Fault information is transmitted using 4-byte data. First, the 4-byte data is converted into 8-bit binary data, and then the SPN code and FMI code in the fault are spliced ​​in the following format and converted into decimal data for display. The 4th byte is converted into a decimal fault number separately.

2. A method for analyzing excavator Tbox device data frames as claimed in claim 1, characterized in that: The splitting requirements of the mechanical environmental protection code are as follows: the terminal device combines the WMC, MDS, CI and MIS data information uploaded by the vehicle into a 17-bit code, and uploads it using the ASCII code character comparison relationship. The platform parses it according to the ASCII code character table to determine whether it meets the requirements.

3. The excavator Tbox device data frame reporting and parsing method according to claim 1, characterized in that: The splitting requirement of the data collection time is as follows: the device compiles the current time during data collection into 6-byte hexadecimal data, and the platform parses each byte into decimal data and splices them into the specific time year-month-day, hour-minute-second, and compares it with the data reception time. If the collection time is later than the data reception time, it is deemed to not meet the requirements.

4. The excavator Tbox device data frame reporting and parsing method according to claim 1, characterized in that: The splitting of the data unit meets the following requirements according to the encoding: The code is 0x02, which is defined as real-time information reporting; The code is 0x03, which is defined as re-issuance of information report.

5. The excavator Tbox device data frame reporting and parsing method according to claim 1, characterized in that: The requirements for splitting the vehicle code and positioning information are: convert the hexadecimal positioning information uploaded by the device into decimal data, multiply it by 0.000001° accuracy, and calculate the longitude and latitude information.

6. A method for analyzing excavator Tbox device data frames as claimed in claim 1, characterized in that: The data encoding of the information type mark module needs to meet the following data range: encoding 0x81 is TBOX data information; encoding 0x82 is data stream information; encoding 0x85 is excavator ECU information; encoding 0x86 is excavator MCU / HMI information; encoding 0x87 is other excavator data information; encoding 0x9A is whole machine fault information.

7. A method for reporting and parsing data frames of an excavator Tbox device as claimed in claim 6, characterized in that: Overseas positioning data is invalid data and is not parsed into specific locations. The specific parsing method is: longitude = decimal longitude*0.000001, latitude = decimal latitude*0.000001.

Images