A method for online monitoring of bus data of embedded products

Abstract

The application belongs to the technical field of bus data monitoring, and discloses a bus data online monitoring method for embedded products, which comprises the following steps: establishing a bus monitoring configuration file; sending monitoring data between the embedded device and all 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; obtaining parsed data by parsing and converting the monitoring data according to the bus monitoring configuration file; and obtaining a monitoring result by displaying and judging the consistency of the parsed data according to data monitoring requirements. According to the method, the data monitoring device can parse and convert the received communication data according to the bus monitoring configuration file, and can select the data to be displayed according to actual monitoring requirements, so that the displayed data can be viewed and judged for consistency.

Description

Technical Field

[0001] This invention relates to the field of bus data monitoring technology, and specifically to a method for online monitoring of bus data in embedded products. Background Technology

[0002] For embedded products with communication functions, it is often necessary to verify the correctness of their communication data transmission and reception during the product development phase. During the joint testing phase between the product and external physical devices, if a device in the communication data network fails to receive data or receives incorrect data, it is also necessary to troubleshoot the faulty device nodes in the data flow process segment by segment. In addition, it is also necessary to monitor and analyze the trend of the transmitted and received data over a period of time to determine whether the changes are in line with expectations. To cope with the above situations, online monitoring of bus data is essential.

[0003] In practical engineering, it is usually necessary to customize dedicated equipment and equip it with a communication daughter card of its actual communication bus type for data monitoring according to the specific needs of the embedded product. This method not only increases the R&D cost, but also the equipment cannot be directly used to monitor the bus data of other products, resulting in poor reusability.

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

[0005] To address the technical problems of high cost and poor reusability in existing embedded products' bus data monitoring, this invention discloses an online bus data monitoring method for embedded products, the method comprising the following steps:

[0006] S101. Based on the interface control file between the embedded device and the physical device, establish a bus monitoring configuration file in the data monitoring device;

[0007] S102. Establish a communication link between the embedded device and the data monitoring device, and send the monitoring data between the embedded device and all the physical devices to the data monitoring device in real time. The monitoring data includes the communication data between the embedded device and each of the physical devices.

[0008] S103. Parse and transform the monitoring data according to the bus monitoring configuration file to obtain parsed data;

[0009] S104. Based on the data monitoring requirements, display and perform consistency checks on the parsed data to obtain monitoring results.

[0010] Further, in step S101, based on 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:

[0011] S1011. Obtain the interface control file between the embedded device and all physical devices, and extract the communication elements of the interface control file, including bus type, device name, data communication direction and data name;

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

[0013] Further, in step S1012, establishing the conversion relationship of communication elements to obtain the bus monitoring configuration file between the embedded device and all the physical devices includes:

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

[0015] S10122. Based on the bus type, establish a second conversion relationship between each data name and data ID in the physical device;

[0016] S10123. Based on the first conversion relationship, the second conversion relationship, the bus type, and the data communication direction of all the physical devices, establish an association table 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, wherein the data ID of the ARI NC429 bus is a data identifier number, and the data ID of the AFDX bus is a data packet sequence number.

[0018] Further, in step S103, parsing and converting the monitoring data according to the bus monitoring configuration file to obtain parsed data includes:

[0019] S1031. Parse the monitoring data to extract the communication data between each physical device and the embedded device. The communication data includes bus type, device ID, data communication direction, and data ID.

[0020] S1032. Based on 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 also includes:

[0022] S1033. Based on the second conversion relationship in the bus monitoring configuration file, replace the data ID in the parsed data with the data name to obtain the final parsed data.

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

[0024] S1041. Based on the data monitoring requirements, select the communication element and input the monitoring time period on the display interface of the embedded device, and extract data from the parsed data and display it based on the communication element and the monitoring time period.

[0025] S1042. Perform a consistency check between the displayed data and the expected product receive / send data. If the consistency check result is consistent, output a normal communication signal; if the consistency check result is inconsistent, output a communication error signal.

[0026] Furthermore, step S104 also includes:

[0027] S1043. Plot the extracted data during the monitoring period into a curve and analyze whether the trend of the curve meets expectations.

[0028] Compared with the prior art, the beneficial effects achieved by at least one of the above-mentioned technical solutions adopted in the embodiments of this specification include at least the following: the online bus data monitoring method of the present invention can realize real-time monitoring, storage, and playback of bus data, providing support for the research and development of embedded products. This solution eliminates the need for dedicated data monitoring equipment for embedded products, effectively reducing research and development costs; it does not limit the communication bus type between embedded products and external interconnection devices, thus being applicable to embedded products with different architectures; it supports monitoring parameter configuration, exhibiting strong portability and reusability, and has a wide range of application scenarios in embedded product bus monitoring. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a schematic diagram illustrating the interconnection relationship between the embedded device, physical device, and data monitoring device disclosed in an embodiment of the present invention;

[0031] Figure 2 This is a flowchart of an online bus data monitoring method for embedded products disclosed in an embodiment of the present invention. Detailed Implementation

[0032] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0033] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. This application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, in the absence of conflict, the following embodiments and features of the embodiments can be combined with each other. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0034] This invention discloses an online monitoring method for bus data in embedded products, see [link to relevant documentation]. Figure 1 As shown, an embedded product (i.e., an embedded device) to be monitored interconnects with 1 to N physical devices. This product can send data to and receive data output from the physical devices. A data monitoring device connects to the embedded product to receive all its communication data. See also... Figure 2 As shown, the online bus data monitoring method disclosed in this embodiment of the invention includes the following steps:

[0035] S101. Based on the interface control file between the embedded device and the physical device, establish a bus monitoring configuration file in the data monitoring device;

[0036] S102. Establish a communication link between the embedded device and the data monitoring device, and send the monitoring data between the embedded device and all the physical devices to the data monitoring device in real time. The monitoring data includes the communication data between the embedded device and each of the physical devices.

[0037] S103. Parse and transform the monitoring data according to the bus monitoring configuration file to obtain parsed data;

[0038] S104. Based on the data monitoring requirements, display and perform consistency checks on the parsed data to obtain monitoring results.

[0039] The online bus data monitoring method of the present invention allows the data monitoring device to parse and convert the received communication data through a bus monitoring configuration file. Simultaneously, it can select the data to be displayed based on actual monitoring needs, facilitating viewing and consistency assessment of the displayed data.

[0040] Further, in step S101, based on 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:

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

[0042] There are various types of buses, such as ARI NC429 bus, AFDX bus, RS422 bus, RS485 bus, etc. This embodiment uses ARI NC429 bus and AFDX bus as examples to specifically explain the data ID. The data ID of the ARI NC429 bus is a data identifier, and the data ID of the AFDX bus is a data packet sequence number. Data communication includes both sending and receiving.

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

[0044] In practical 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 the 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] Further, in step S1012, establishing the conversion relationship of communication elements to obtain the bus monitoring configuration file between the embedded device and all the physical devices includes:

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

[0049] S10122. Based on the bus type, establish a second conversion relationship between each data name and data ID in the physical device;

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

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

[0052] Table 2: First Conversion Relationship between Device ID and Device Name

[0053] Equipment Name Device ID Physical equipment 1 001 Physical equipment 2 002 Physical device 3 ports 1 003 Physical device 3-port 2 004

[0054] In the second conversion relationship, the representation of data IDs differs depending on the bus type. Therefore, the second conversion relationship is shown in Tables 3 and 4 below. In the communication mode of the ARI NC429 bus type, the data ID in the communication data is distinguished by the data identifier number. In the communication mode of the AFDX bus type, the data ID in the communication data is distinguished by the data packet sequence number.

[0055] Table 3: 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: First conversion relationship between data ID and data name (taking physical device 3 as an example, corresponding to AFDX bus type)

[0058] Data packet sequence number Data Name 0 Data 6 1 Data 7

[0059] Furthermore, in its specific implementation, step S102 includes:

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

[0061] Embedded devices communicate with data monitoring devices 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] In Table 5, the data is grouped into a single data packet based on the physical device division in Table 1 and sent to the data monitoring device.

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

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

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

[0068] Further, in step S103, parsing and converting the monitoring data according to the bus monitoring configuration file to obtain parsed data includes:

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

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

[0071] S1032. Based on 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 practice, when it is only necessary to check whether the timestamp of the communication data is correct or whether there are any missing packets, only the device ID can be converted into the device name for easy viewing.

[0073] Furthermore, if it is necessary to examine the communication data in detail for errors or to understand the data change trend, it is also necessary to replace the data ID with the data name. Therefore, the above step S103 also includes:

[0074] S1033. Based on the second conversion relationship in the bus monitoring configuration file, replace the data ID in the parsed data with the data name to obtain the final parsed data.

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

[0076] Table 1: Display of Analyzed Data (Partial)

[0077]

[0078] It should be noted that: for ARI NC429 type data, if the received data packet contains multiple AR INC429 data entries, they should be stored sequentially according to their data identifier numbers, one data entry per line; for AFDX data, if the received data packet contains multiple AFDX data entries, they should be stored sequentially according to their packet sequence numbers, one data entry per line. Furthermore, the SDI field is only valid for ARINC429 information; the raw data should only contain 4 bytes of data.

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

[0080] S1041. Based on the data monitoring requirements, select the communication element and input the monitoring time period on the display interface of the embedded device, and extract data from the parsed data and display it based on the communication element and the monitoring time period.

[0081] Specifically, the parsed data can be displayed in various forms. For example, the display interface can preset two modes: brief or standard. After selection, the interface can automatically display the data in the desired mode.

[0082] When displayed in "brief mode", the data is refreshed in real time and includes bus type, device name, communication direction (receive / send), number of data bytes, and raw data.

[0083] Table 2 Examples of Brief Mode Display Content

[0084]

[0085] When a user switches to "Detailed Mode" on the data monitoring tool interface and selects a specific physical device, the detailed content of each data point in the raw data of that physical device will 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 9th to 10th bits of the raw data; "Data Segment Data" displays the hexadecimal representation of the 14th to 29th bits of data; D32 to D1 display the bit data (displaying each bit of the data one by one).

[0087] Table 3: Detailed Data Display of ARI NC429 (Taking Physical Device 1 as an Example)

[0088]

[0089] For example, the display format of AFDX data in detail mode is shown in Table 4 below:

[0090] Table 4: Detailed AFDX Information Display (Taking Physical Device 3 as an Example)

[0091]

[0092] Of course, you can also select the data items you are interested in according to your monitoring needs, filter the data and display the selected content. For example, if the monitoring personnel want to obtain all the received information of physical device 1 according to the actual monitoring needs, they can select both filter conditions a (device ID: 001) and b (communication direction: receiving). The display interface will only show the data that meets the specified filter conditions a and b.

[0093] S1042. Perform a consistency check between the displayed data and the expected product receive / send data. If the consistency check result is consistent, output a normal communication signal; if the consistency check result is inconsistent, output a communication error signal.

[0094] Specifically, 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 is the same.

[0095] Furthermore, step S104 also includes:

[0096] S1043. Plot the extracted data during the monitoring period into a curve and analyze whether the trend of the curve meets expectations.

[0097] Specifically, monitoring personnel can use data monitoring tools to replay historical data and plot data curves to analyze whether data trends meet expectations. This includes: monitoring personnel setting the query keyword to "Device 1 Data 2" in the historical data playback interface of the data monitoring equipment; the data monitoring equipment retrieving data that meets the conditions from the database based on the display items selected by the monitoring personnel; the data monitoring equipment displaying the timestamps, data values, and other information of all "Data 2" entries in the database on the data playback interface, and plotting a data curve with the timestamps as the horizontal axis and the data values ​​of "Data 2" as the vertical axis. By observing the trend of the data curve, the changes can be analyzed to see if they meet expectations.

[0098] The online bus data monitoring method of this invention enables real-time monitoring, storage, and playback of bus data, providing support for the research and development of embedded products. This solution eliminates the need for dedicated data monitoring equipment for embedded products, effectively reducing development costs; it does not limit the communication bus type between the embedded product and external interconnection devices, thus making it suitable for embedded products with different architectures; it supports configuration of monitoring parameters, exhibiting strong portability and reusability, and has wide application scenarios in embedded product bus monitoring.

[0099] Obviously, those skilled in the art will understand that the steps of the above embodiments can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the embodiments of the present invention are not limited to any particular hardware and software combination.

[0100] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, various modifications and variations can be made to the embodiments of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for online monitoring of bus data of an embedded product, characterized in that, The application relates to a bus monitoring method and device. According to the interface control file between an embedded device and physical devices, a bus monitoring configuration file is established in a data monitoring device, including: obtaining the interface control file between the embedded device and all the physical devices, extracting the communication elements of the interface control file, the communication elements including a bus type, a device name, a data communication direction and a data name; establishing a first conversion relationship between the device name of the physical device and a device ID; according to the bus type, establishing a second conversion relationship between each data name of the physical device and a data ID; according to the first conversion relationship, the second conversion relationship, the bus type and the data communication direction of all the physical devices, establishing a correlation relationship table to obtain the bus monitoring configuration file; A communication link between the embedded device and the data monitoring device is established, and monitoring data between the embedded device and all the physical devices is sent to the data monitoring device in real time, the monitoring data including the communication data between the embedded device and each physical device; According to the bus monitoring configuration file, the monitoring data is parsed and converted to obtain parsed data, and according to data monitoring requirements, the parsed data is displayed and consistency is judged to obtain a monitoring result, including: the monitoring data is parsed to obtain the communication data between each physical device and the embedded device, the communication data including a bus type, a device ID, a data communication direction and a data ID; according to the first conversion relationship in the bus monitoring configuration file, the device ID in the communication data is replaced by a device name to obtain the parsed data.

2. The method of claim 1, wherein, 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 serial number.

3. The method of claim 1, wherein the embedded product bus data online monitoring method is characterized by, The application further relates to According to the second conversion relationship in the bus monitoring configuration file, the data ID in the parsed data is replaced by a data name to obtain final parsed data.

4. The method of claim 1, wherein the embedded product bus data online monitoring method is characterized by, According to data monitoring requirements, the parsed data is displayed and consistency is judged to obtain a monitoring result, including: According to data monitoring requirements, a communication element and a monitoring time period are selected on a display interface of the embedded device, and data is extracted from the parsed data according to the communication element and the monitoring time period for display; The displayed data is compared with expected product receiving / sending data for consistency judgment, a communication normal signal is output when the consistency judgment result is consistent, and a communication abnormal signal is output when the consistency judgment result is inconsistent.

5. The method of claim 4, wherein, The application further relates to The extracted data in the monitoring time period is drawn into a curve, and whether the change trend of the curve meets an expectation is analyzed.

Images