Bus data online monitoring method of embedded product

Abstract

The invention belongs to the technical field of bus data monitoring, and discloses an embedded product bus data online monitoring method, which comprises the following steps: establishing a bus monitoring configuration file; sending monitoring data between the embedded device and all the physical devices to a data monitoring device in real time, wherein the monitoring data comprises communication data between the embedded device and each physical device; and analyzing and converting the monitoring data according to the bus monitoring configuration file to obtain analyzed data, and performing display and consistency judgment on the analyzed data according to a data monitoring requirement to obtain a monitoring result. According to the method disclosed by the invention, the data monitoring equipment can analyze and convert the received communication data through the bus monitoring configuration file, and meanwhile, the data needing to be displayed can be selected according to actual monitoring requirements, so that the displayed data can be conveniently checked and the consistency of the displayed data can be conveniently judged.

Description

Technical Field

[0001] The invention relates to the technical field of bus data monitoring, and in particular to an online bus data monitoring method for an embedded product. Background Art

[0002] For embedded products with communication functions, it is often necessary to verify the correctness of their communication receiving and sending data during the product development stage. During the stage of joint testing between the product and external physical devices, when a device in the communication data network fails to receive data or receives incorrect data, it is also necessary to check the erroneous device nodes in the data flow process section by section. In addition, it is also necessary to monitor and analyze the changing trends of the sent and received data over a period of time to determine whether the changes are in line with expectations. In order to deal with the above situations, online monitoring of bus data is essential.

[0003] In actual projects, it is usually necessary to customize dedicated equipment for embedded products based on their specific needs and equip them with communication daughter cards of their actual communication bus type for data monitoring. This method not only increases the R&D cost, but the equipment cannot be directly used to monitor the bus data of other products, and has poor reusability.

[0004] Therefore, it is necessary to design a universal data online monitoring solution that can quickly adapt to embedded products of different communication bus types and monitor sufficiently detailed data content. Summary of the invention

[0005] In order to solve the technical problems of high cost and poor reusability of existing embedded product bus data monitoring, the present invention discloses an online bus data monitoring method for embedded products, the method comprising the following steps:

[0006] S101, establishing a bus monitoring configuration file in a data monitoring device according to an interface control file between an embedded device and a physical device;

[0007] S102, establishing a communication link between the embedded device and a data monitoring device, and sending monitoring data between the embedded device and all the physical devices to the data monitoring device in real time, wherein the monitoring data includes communication data between the embedded device and each of the physical devices;

[0008] S103, parsing and converting the monitoring data according to the bus monitoring configuration file to obtain parsed data;

[0009] S104: Display and make consistency judgment on the analyzed data according to data monitoring requirements to obtain monitoring results.

[0010] Furthermore, in step S101, a bus monitoring configuration file is established in the data monitoring device according to the interface control file between the embedded device and the physical device, including:

[0011] S1011, obtaining interface control files between the embedded device and all physical devices, and extracting communication elements of the interface control files, wherein the communication elements include bus type, device name, data communication direction, and data name;

[0012] S1012: Establish a conversion relationship between communication elements to obtain a bus monitoring configuration file between the embedded device and all the physical devices.

[0013] Furthermore, in step S1012, a conversion relationship of communication elements is established to obtain a bus monitoring configuration file of the embedded device and all the physical devices, including:

[0014] S10121. Establish a first conversion relationship between the device name and the device ID of the physical device;

[0015] S10122. Establish, according to the bus type, a second conversion relationship between each of the data names and the data ID in the physical device;

[0016] S10123. Establish an association table according to the first conversion relationship, the second conversion relationship, the bus type, and the data communication direction of all the physical devices to obtain the bus monitoring configuration file.

[0017] Furthermore, in step S1011, the bus type includes any one of ARI NC429 bus, AFDX bus, RS422 bus and RS485 bus, the data ID of the ARI NC429 bus is a data identification number, and the data ID of the AFDX bus is a data packet sequence number.

[0018] Further, in step S103, the monitoring data is parsed and converted according to the bus monitoring configuration file to obtain parsed data, including:

[0019] S1031, parsing the monitoring data, extracting the communication data between each of the physical devices and the embedded device, the communication data including bus type, device ID, data communication direction and data ID;

[0020] S1032. According to the first conversion relationship in the bus monitoring configuration file, replace the device ID in the communication data with the device name to obtain the parsed data.

[0021] Furthermore, step S103 further includes:

[0022] S1033. According to the second conversion relationship in the bus monitoring configuration file, the data ID in the parsed data is replaced with a data name to obtain final parsed data.

[0023] Furthermore, in step S104, the parsed data is displayed and consistency judged according to the data monitoring requirements to obtain monitoring results, including:

[0024] S1041, selecting a communication element and inputting a monitoring time period on a display interface of the embedded device according to a data monitoring requirement, and extracting data from the parsed data for display according to the communication element and the monitoring time period;

[0025] S1042, performing consistency judgment between the displayed data and the expected product receiving / sending data, and outputting a normal communication signal when the consistency judgment result is consistent, and outputting a communication abnormality signal when the consistency judgment result is inconsistent.

[0026] Furthermore, step S104 further includes:

[0027] S1043: Plot the data extracted in the monitoring time period into a curve, and analyze whether the change trend of the curve meets expectations.

[0028] Compared with the prior art, the beneficial effects that can be achieved by at least one of the above technical solutions adopted in the embodiments of this specification include at least: the bus data online monitoring method of the present invention can realize real-time monitoring, storage and playback of bus data, and provide support for the research and development of embedded products. This solution does not require the embedded product to be equipped with a dedicated data monitoring device, which can effectively reduce the research and development cost; it does not limit the type of communication bus between the embedded product and the external cross-linking device, so it is suitable for embedded products of different architectures; it supports monitoring parameter configuration, has strong portability and reusability, and has a wide range of application scenarios in embedded product bus monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0030] Figure 1 A schematic diagram of the cross-linking relationship among the embedded device, the physical device and the data monitoring device disclosed in the embodiment of the present invention;

[0031] Figure 2 The present invention is a flowchart of a method for online monitoring of bus data of an embedded product disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0032] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0033] The following describes the implementation methods of the present application through specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and the features of the embodiments can be combined with each other in the absence of conflict. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work belong to the scope of protection of the present application.

[0034] The present invention discloses a method for online monitoring of bus data of an embedded product. Figure 1 As shown in the figure, an embedded product (i.e., embedded device) to be monitored is interconnected with 1 to N physical devices. The product can send data to the physical devices and receive data output by the physical devices. The data monitoring device is connected to an embedded product to receive all the communication data. Figure 2 As shown, the bus data online monitoring method disclosed in the embodiment of the present invention includes the following steps:

[0035] S101, establishing a bus monitoring configuration file in a data monitoring device according to an interface control file between an embedded device and a physical device;

[0036] S102, establishing a communication link between the embedded device and a data monitoring device, and sending monitoring data between the embedded device and all the physical devices to the data monitoring device in real time, wherein the monitoring data includes communication data between the embedded device and each of the physical devices;

[0037] S103, parsing and converting the monitoring data according to the bus monitoring configuration file to obtain parsed data;

[0038] S104: Display and make consistency judgment on the analyzed data according to data monitoring requirements to obtain monitoring results.

[0039] In the bus data online monitoring method of the present invention, the data monitoring device can parse and convert the communication data it receives through the bus monitoring configuration file, and can select the data to be displayed according to the actual monitoring needs, so as to facilitate the viewing and consistency judgment of the displayed data.

[0040] Furthermore, in step S101, a bus monitoring configuration file is established in the data monitoring device according to the interface control file between the embedded device and the physical device, including:

[0041] S1011. Obtain interface control files between the embedded device and all physical devices, and extract communication elements of the interface control files, where the communication elements include bus type, device name, data communication direction, and data name.

[0042] Generally, there are many types of bus types, such as ARI NC429 bus, AFDX bus, RS422 bus, RS485 bus, etc. In this embodiment, ARI NC429 bus and AFDX bus are taken as examples to specifically explain the data ID. The data ID of the ARINC429 bus is the data identification number, and the data ID of the AFDX bus is the data packet sequence number. The data communication direction includes sending and receiving.

[0043] S1012: Establish a conversion relationship between communication elements to obtain a bus monitoring configuration file between the embedded device and all the physical devices.

[0044] In specific implementation, the communication elements are shown in Table 1 below. It should be noted that the cross-linking devices shown in Table 1 do not need to be divided according to actual physical devices. For example, in AFDX bus communication, each AFDX port can be regarded as a device.

[0045] Table 1: Communication elements

[0046]

[0047] Furthermore, in step S1012, a conversion relationship of communication elements is established to obtain a bus monitoring configuration file of the embedded device and all the physical devices, including:

[0048] S10121. Establish a first conversion relationship between the device name and the device ID of the physical device;

[0049] S10122. Establish, according to the bus type, a second conversion relationship between each of the data names and the data ID in the physical device;

[0050] S10123. Establish an association table according to the first conversion relationship, the second conversion relationship, the bus type, and the data communication direction of all the physical devices to obtain the bus monitoring configuration file.

[0051] In specific implementation, the first conversion relationship is shown in Table 2 below:

[0052] Table 2: The first conversion relationship between device ID and device name

[0053] Device Name Device ID Physical Device 1 001 Physical Device 2 002 Physical Device 3 Port 1 003 Physical Device 3 Port 2 004

[0054] In the second conversion relationship, when the bus type is different, the representation method of the data ID is also different. Therefore, the second conversion relationship is shown in Table 3 and Table 4. In the communication mode of the ARI NC429 bus type, the data ID in the communication data is distinguished by the data identification number, and in the communication mode of the AFDX bus type, the data ID in the communication data is distinguished by the data packet number.

[0055] Table 3: The first conversion relationship between data ID and data name (taking physical device 1 as an example, corresponding to ARI NC429 bus type)

[0056]

[0057] Table 4: The first conversion relationship between data ID and data name (taking physical device 3 as an example, corresponding to AFDX bus type)

[0058] Packet sequence number Data name 0 Data 6 1 Data 7

[0059] Furthermore, when step S102 is specifically implemented, it includes:

[0060] S1021. Design the communication protocol format between embedded devices and data monitoring equipment.

[0061] The embedded device and the data monitoring device communicate via Ethernet, and the communication protocol is shown in Table 5 below:

[0062] Table 5: Ethernet communication protocols between embedded devices and data monitoring equipment

[0063]

[0064] The data in Table 5 is packaged in such a way that, according to the physical device division in Table 1, the data of the same physical device is packaged into one data packet and sent to the data monitoring device;

[0065] S1022. Establish a physical communication link between the embedded device and the data monitoring device, where the physical communication link uses Ethernet.

[0066] S1023. Write software code for the embedded device communication module so that it sends all data received and sent through the ARI NC429 bus and the AFDX bus to the data monitoring device through the Ethernet port of the maintenance cable in accordance with the communication protocol defined in Table 5, such as every 50 ms.

[0067] S1024. The data monitoring device receives all monitoring data sent by the embedded device in real time.

[0068] Further, in step S103, the monitoring data is parsed and converted according to the bus monitoring configuration file to obtain parsed data, including:

[0069] S1031. Analyze the monitoring data to extract the communication data between each physical device and the embedded device, where the communication data includes bus type, device ID, data communication direction and data ID.

[0070] Specifically, the data monitoring device first unpacks the received data packet according to the communication protocol format in Table 5 to obtain the communication data between each physical device and the embedded device, and stores it in the local database.

[0071] S1032. According to the first conversion relationship in the bus monitoring configuration file, replace the device ID in the communication data with the device name to obtain the parsed data.

[0072] In specific implementation, when you only need to check whether the timestamp of the communication data is correct, whether there are any packet leaks, etc., you can only convert the device ID and convert it into a device name for easy viewing.

[0073] Furthermore, if it is necessary to check in detail whether the communication data is wrong or to understand the data change trend, it is also necessary to replace the data ID with the data name, so the above step S103 also includes:

[0074] S1033. According to the second conversion relationship in the bus monitoring configuration file, the data ID in the parsed data is replaced with a data name to obtain final parsed data.

[0075] Specifically, the display form of the parsed data obtained after the conversion is shown in Table 6:

[0076] Table 1: Display of parsed data (partial)

[0077]

[0078] It should be noted that: for ARI NC429 type data, if the received data packet contains multiple ARINC429 data, they should be stored in sequence according to the data identification number, with one line for each data; for AFDX data, if the received data packet contains multiple AFDX data, they should be stored in sequence according to the packet sequence number, with one line for each data. In addition, the SD I field is only valid for ARINC429 information; the original data only fills in 4 bytes of data.

[0079] Furthermore, in step S104, the parsed data is displayed and consistency judged according to the data monitoring requirements to obtain monitoring results, including:

[0080] S1041. Select a communication element and input a monitoring time period on the display interface of the embedded device according to data monitoring requirements, and extract data from the parsed data for display according to the communication element and the monitoring time period.

[0081] Specifically, the parsed data can be displayed in a variety of forms. For example, two modes, brief or modal, can be preset on the display interface. After selection, the data in the desired mode can be automatically displayed on the interface.

[0082] When in "Brief Mode", the display is refreshed in real time, and the displayed data includes bus type, device name, communication direction (receive / send), number of data bytes, and original data;

[0083] Table 2 Example of display content in brief mode

[0084]

[0085] When the user chooses to switch to "Detailed Mode" on the data monitoring tool interface and selects a specific physical device, the detailed content of each piece of data in the original data of the physical device can be displayed.

[0086] For example, for ARI NC429 data, the display format in detailed mode is shown in Table 3. According to the general ARINC429 data format, "SDI" displays the content of the 9th to 10th bits of the original data; "Data segment data" displays the hexadecimal representation of 14 to 29 bits of data; D32 to D1 display bit data (displaying each bit of data one by one).

[0087] Table 3: ARI NC429 data detailed mode display content (taking physical device 1 as an example)

[0088]

[0089] For another example, for AFDX data, the display format in the detailed mode is shown in Table 4 below:

[0090] Table 4: Detailed display content of AFDX information (taking physical device 3 as an example)

[0091]

[0092] Of course, you can also select the data items of interest according to the monitoring needs, filter the data and display the checked content. For example: according to the actual monitoring needs, the monitoring personnel want to obtain all the receiving information of physical device 1, then check the two filtering conditions a (device ID: 001) and b (communication direction: receiving) at the same time: only the data that meets the specified filtering conditions in a and b are displayed on the display interface.

[0093] S1042, performing consistency judgment between the displayed data and the expected product receiving / sending data, and outputting a normal communication signal when the consistency judgment result is consistent, and outputting a communication abnormality signal when the consistency judgment result is inconsistent.

[0094] Specifically, the monitoring personnel can compare the data displayed on the data monitoring tool interface with the data received / sent by the external physical device to determine whether the data are the same.

[0095] Furthermore, step S104 further includes:

[0096] S1043: Plot the data extracted in the monitoring time period into a curve, and analyze whether the change trend of the curve meets expectations.

[0097] Specifically, monitoring personnel can use data monitoring tools to replay historical data and draw data curves to analyze whether the data change trend meets expectations, including: monitoring personnel set the query keyword as "device 1 data 2" on the historical data playback interface of the data monitoring device; the data monitoring device reads data that meets the conditions from the database according to the display items selected by the monitoring personnel; the data monitoring device displays the timestamps, data values ​​and other information of all "data 2" in the database on the data playback interface, and draws a data curve with the timestamp as the horizontal axis and the value of data 2 as the vertical axis. By observing the change trend of the data curve, analyze whether its change meets expectations.

[0098] The bus data online monitoring method of the present invention can realize real-time monitoring, storage and playback of bus data, and provide support for the research and development of embedded products. This solution does not need to equip embedded products with dedicated data monitoring equipment, which can effectively reduce research and development costs; it does not limit the communication bus type between embedded products and external cross-linking devices, so it is suitable for embedded products with different architectures; it supports monitoring parameter configuration, has strong portability and reusability, and has a wide range of application scenarios in embedded product bus monitoring.

[0099] Obviously, those skilled in the art should understand that the steps of the above embodiments can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the embodiments of the present invention are not limited to any specific combination of hardware and software.

[0100] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the embodiments of the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A bus data online monitoring method for an embedded product, characterized in that: include: According to the interface control file between the embedded device and the physical device, a bus monitoring configuration file is established in the data monitoring device; Establishing a communication link between the embedded device and a data monitoring device, and sending monitoring data between the embedded device and all the physical devices to the data monitoring device in real time, wherein the monitoring data includes communication data between the embedded device and each of the physical devices; The monitoring data is parsed and converted according to the bus monitoring configuration file to obtain parsed data, and the parsed data is displayed and consistency judged according to data monitoring requirements to obtain monitoring results.

2. The method for online monitoring of bus data of an embedded product according to claim 1, characterized in that: According to the interface control file between the embedded device and the physical device, a bus monitoring configuration file is established in the data monitoring device, including: Obtaining interface control files between the embedded device and all physical devices, and extracting communication elements of the interface control files, wherein the communication elements include bus type, device name, data communication direction, and data name; A conversion relationship of communication elements is established to obtain bus monitoring configuration files of the embedded device and all the physical devices.

3. The method for online monitoring of bus data of an embedded product according to claim 2, characterized in that: Establishing a conversion relationship of communication elements to obtain bus monitoring configuration files of the embedded device and all the physical devices includes: Establishing a first conversion relationship between the device name and the device ID of the physical device; According to the bus type, establishing a second conversion relationship between each of the data names and the data ID in the physical device; According to the first conversion relationship, the second conversion relationship, the bus type and the data communication direction of all the physical devices, an association table is established to obtain the bus monitoring configuration file.

4. The method for online monitoring of bus data of an embedded product according to claim 3, characterized in that: The bus type includes any one of an ARINC429 bus, an AFDX bus, an RS422 bus and an RS485 bus. The data ID of the ARINC429 bus is a data identification number, and the data ID of the AFDX bus is a data packet sequence number.

5. The method for online monitoring of bus data of embedded products according to claim 3, characterized in that: Parsing and converting the monitoring data according to the bus monitoring configuration file to obtain parsed data includes: Parsing the monitoring data to extract the communication data between each of the physical devices and the embedded device, the communication data including bus type, device ID, data communication direction and data ID; According to the first conversion relationship in the bus monitoring configuration file, the device ID in the communication data is replaced with the device name to obtain the parsed data.

6. The method for online monitoring of bus data of an embedded product according to claim 5, characterized in that: Also includes: According to the second conversion relationship in the bus monitoring configuration file, the data ID in the parsed data is replaced with the data name to obtain the final parsed data.

7. The method for online monitoring of bus data of an embedded product according to claim 2, characterized in that: The analyzed data is displayed and consistency judged according to the data monitoring requirements to obtain monitoring results, including: According to data monitoring requirements, selecting a communication element and inputting a monitoring time period on a display interface of the embedded device, and extracting data from the parsed data for display according to the communication element and the monitoring time period; The displayed data is judged for consistency with the expected product receiving / sending data. When the consistency judgment result is consistent, a communication normal signal is output; when the consistency judgment result is inconsistent, a communication abnormal signal is output.

8. The method for online monitoring of bus data of an embedded product according to claim 7, characterized in that: Also includes: The data extracted during the monitoring period are plotted into a curve, and the changing trend of the curve is analyzed to see whether it meets expectations.

Images