Point inspection menu display method and device, electronic equipment and storage medium
By acquiring overview information and data description information of the target device, the inspection menu is dynamically generated, which solves the problem of incompatibility between the inspection tool and the outdoor unit version, improves the reliability of inspection and reduces maintenance costs.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- GD MIDEA HEATING & VENTILATING EQUIP CO LTD
- Filing Date
- 2026-01-27
- Publication Date
- 2026-05-12
AI Technical Summary
In existing technologies, the inspection tools cannot adapt to the problem of incompatibility between the outdoor unit and the inspection tool program version, resulting in decreased inspection reliability and frequent software update requirements.
By acquiring overview information of the target device, determining the data description information of the inspection menu data, parsing and rendering the inspection menu data, the dynamic generation of the inspection menu is realized, avoiding the need to pre-generate the inspection table.
It improves the reliability of inspection, reduces the risk of failure and maintenance costs, and avoids frequent updates of inspection tools due to software version incompatibility.
Smart Images
Figure CN122018972A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, electronic device and storage medium for displaying an inspection menu. Background Technology
[0002] During the maintenance and diagnosis of air conditioning equipment, specialized inspection tools are typically used to collect and parse the operating status data of the outdoor unit. In related technologies, these tools access a pre-maintained point table, initiate specific command codes to retrieve corresponding data segments, and then parse these data segments into an inspection menu based on the point descriptions in the point table. This method requires the outdoor unit's software version and the inspection tool's program version to be compatible. If the outdoor unit's software version and the inspection tool's program version differ, the inspection tool cannot adapt to the unknown point table, resulting in problems such as failure to obtain point values, missed point values, and numerical parsing errors, thus reducing the reliability of the inspection. Summary of the Invention
[0003] This invention aims to at least partially solve one of the technical problems in related technologies. To this end, the first objective of this invention is to propose a method for displaying inspection menus. Based on overview information, inspection menu data for various versions can be obtained from the target device. This data is then parsed to obtain the corresponding inspection menus, which are then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate inspection tables; instead, it generates different versions of inspection menus in real time based on the different versions of the inspection menu data. This eliminates the problem of software version mismatch with the target device, thereby improving the reliability of the inspection process.
[0004] A second objective of this invention is to provide a computer-readable storage medium.
[0005] The third objective of this invention is to provide an electronic device.
[0006] The fourth objective of this invention is to provide a display device for an inspection menu.
[0007] To achieve the above objectives, a method for displaying an inspection menu is proposed according to a first aspect embodiment of the present invention, comprising: acquiring overview information sent by a target device; determining data description information of inspection menu data based on the overview information; acquiring inspection menu data from the target device based on the data description information, wherein the inspection menu data structure of the target device includes overview information and inspection menu data, the overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device; parsing the inspection menu data to obtain the inspection menu, and rendering the inspection menu to display the inspection menu.
[0008] According to the method for displaying an inspection menu according to an embodiment of the present invention, overview information sent by a target device is obtained, and data description information of the inspection menu data is determined based on the overview information. Inspection menu data is then obtained from the target device based on the data description information, parsed to obtain the inspection menu, and rendered for display. The inspection menu data structure of the target device includes overview information and inspection menu data. The overview information describes and verifies the inspection menu data, while the inspection menu data describes the content of the inspection menu on the target device. Therefore, the defined inspection menu data structure provides a unified standard for the description language of the inspection menu. Based on the overview information, various versions of inspection menu data can be obtained from the target device, parsed to obtain the corresponding inspection menu, and displayed on the user interface. Thus, the inspection tool does not need to pre-generate an inspection table; instead, it generates different versions of the inspection menu in real time based on different versions of the inspection menu data, eliminating the problem of software version mismatch with the target device and improving the reliability of the inspection.
[0009] According to an embodiment of the present invention, the data description information includes version information, length information, and a check code of the inspection menu data. Obtaining the inspection menu data from the target device based on the data description information includes: if, based on the version information and the check code, it is determined that the inspection menu corresponding to the version information has not been generated, sequentially sending a first query instruction to the target device, wherein the first query instruction includes an offset of the inspection menu data and a preset reading length, and the offset in each sent first query instruction is the sum of the lengths of the received inspection menu data; sequentially receiving inspection menu data segments sent by the target device until the sum of the lengths of the received inspection menu data segments reaches the length information, to obtain at least one inspection menu data segment; and concatenating the at least one inspection menu data segment according to the receiving order to obtain the inspection menu data.
[0010] According to one embodiment of the present invention, determining the data description information of the check menu data based on the overview information includes: extracting version information, length information and check code from the overview information according to a preset data structure, wherein the preset data structure includes the data length of the version information, the data length of the length information and the data length of the check code.
[0011] According to one embodiment of the present invention, parsing inspection menu data includes: obtaining the length of the outermost list of the inspection menu data; based on the length of the outermost list, parsing each sub-item in the outermost list according to the type of each sub-item in the outermost list of the inspection menu data, wherein the inspection menu includes the outermost list and each sub-item in the outermost list.
[0012] According to one embodiment of the present invention, parsing each sub-item in the outermost list of the inspection menu data according to the type of each sub-item in the outermost list includes: when the type of the sub-item is a list, obtaining the length of the sub-list corresponding to the sub-item, and based on the length of the sub-list, parsing each sub-item in the sub-list according to the type of each sub-item in the sub-list; or when the type of the sub-item is a point, parsing the point attribute corresponding to the sub-item.
[0013] According to one embodiment of the present invention, rendering an inspection menu includes: rendering the outermost list according to a preset display format to display the outermost list; and rendering each sub-item in the outermost list according to the type of each sub-item in the outermost list to display each sub-item in the outermost list.
[0014] According to one embodiment of the present invention, rendering each sub-item in the outermost list of the inspection menu data according to the type of each sub-item includes: rendering the sub-list corresponding to the sub-item according to a preset display format when the type of the sub-item is a list and the sub-item is triggered; or sending a second query instruction to the target device when the type of the sub-item is a point, so that the target device finds the point value corresponding to the point according to the second query instruction, receives the point value sent by the target device, and renders the point name and point value of the point.
[0015] To achieve the above objectives, a computer-readable storage medium is provided according to a second aspect of the present invention, on which a computer program is stored, which, when processed by a processor, executes the method for displaying the inspection menu of any of the foregoing embodiments.
[0016] According to the computer-readable storage medium of the present invention, by executing the computer program of the above-described method for displaying inspection menus, inspection menu data of various versions can be obtained from the target device based on overview information, and the inspection menu data can be parsed to obtain the corresponding inspection menus. The inspection menus are then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate inspection tables, but generates different versions of inspection menus in real time based on the inspection menu data of different versions. There is no problem of software version mismatch with the target device, thereby improving the reliability of inspection.
[0017] To achieve the above objectives, an electronic device is provided according to a third aspect of the present invention, including a memory, a processor, and a display program for an inspection menu stored in the memory and executable on the processor. When the processor executes the display program for the inspection menu, it implements the method for displaying the inspection menu of any of the foregoing embodiments.
[0018] According to the electronic device of the present invention, the processor executes the computer program of the above-described method for displaying the inspection menu. Based on the overview information, the inspection menu data of various versions can be obtained from the target device, and the inspection menu data is parsed to obtain the corresponding inspection menu. The inspection menu is then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate the inspection table, but generates different versions of the inspection menu in real time based on the inspection menu data of different versions. There is no problem of software version mismatch with the target device, thereby improving the reliability of the inspection.
[0019] To achieve the above objectives, a display device for an inspection menu is provided according to a fourth aspect of the present invention, comprising: a first acquisition module for acquiring overview information sent by a target device; a determination module for determining data description information of the inspection menu data based on the overview information, wherein the inspection menu data structure of the target device includes overview information and inspection menu data, the overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device; a second acquisition module for acquiring the inspection menu data from the target device based on the data description information; a parsing module for parsing the inspection menu data to obtain the inspection menu; and a rendering module for rendering the inspection menu to display the inspection menu.
[0020] According to an embodiment of the present invention, the device for displaying an inspection menu acquires overview information sent by a target device through a first acquisition module, and determines data description information of the inspection menu data based on the overview information through a determination module. The inspection menu data structure of the target device includes overview information and inspection menu data. The overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device. The device also acquires the inspection menu data from the target device based on the data description information through a second acquisition module, parses the inspection menu data through a parsing module to obtain the inspection menu of the target device, and renders the inspection menu through a rendering module for display. Thus, the defined inspection menu data structure provides a unified standard for the description language of the inspection menu. Based on the overview information, various versions of inspection menu data can be acquired from the target device, parsed to obtain the corresponding inspection menu, and displayed on the user interface. Therefore, the inspection tool does not need to pre-generate an inspection table, but instead generates different versions of the inspection menu in real time based on different versions of the inspection menu data, eliminating the problem of software version mismatch with the target device and improving the reliability of the inspection.
[0021] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description
[0022] Figure 1 This is a flowchart illustrating a method for displaying an inspection menu according to an embodiment of the present invention; Figure 2 This is a schematic diagram of a preset display format according to an embodiment of the present invention; Figure 3 This is a flowchart illustrating a method for displaying an inspection menu according to a specific embodiment of the present invention; Figure 4 This is a system schematic diagram of an electronic device according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of a display device for an inspection menu according to an embodiment of the present invention. Detailed Implementation
[0023] Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.
[0024] In related technologies, inspection tools access a pre-maintained point table internally, initiate specific command codes to obtain corresponding data segments, and parse the data segments into inspection menus according to the point descriptions in the point table. This method requires the outdoor unit's software version and the inspection tool's program version to correspond. If the outdoor unit's software version and the inspection tool's program version are different, the inspection tool cannot adapt to the unknown point table, resulting in problems such as failure to obtain point values, missed point values, and numerical parsing errors, leading to a decrease in inspection reliability. Furthermore, when the outdoor unit's point table is updated, the inspection tool needs to develop parsing code and update its software version to adapt to the new point table. The increased frequency of software updates simultaneously increases the risk of program failure and maintenance costs.
[0025] The following description, with reference to the accompanying drawings, describes a method, apparatus, electronic device, and storage medium for displaying an inspection menu according to embodiments of the present invention.
[0026] Figure 1 This is a flowchart illustrating a method for displaying an inspection menu according to an embodiment of the present invention. Figure 1 As shown, the methods for displaying the inspection menu include: S101, Obtain overview information sent by the target device.
[0027] It should be noted that the target device can be one of the electrical devices such as household appliances (e.g., air conditioning equipment) or industrial equipment.
[0028] In an optional implementation, the method of this embodiment can be applied to a terminal device. Before obtaining the overview information sent by the target device, the terminal device can first send a third query instruction to the target device. After receiving the third query instruction, the target device returns the overview information to the terminal device so that the terminal device can obtain the overview information.
[0029] S102, determine the data description information of the inspection menu data based on the overview information. The inspection menu data structure of the target device includes overview information and inspection menu data. The overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device.
[0030] The target device's inspection menu data structure includes overview information and inspection menu data. The overview information describes and validates the inspection menu data, while the inspection menu data describes the content (e.g., locations and lists) of the target device's inspection menu. Because the overview information is used to describe and validate the inspection menu data, parsing the overview information yields the data description information for the inspection menu data.
[0031] For example, the check-in menu data may include multiple JSON data segments, which describe the content of the dynamic check-in menu in a tree structure. The data description information includes the version information, length information, and checksum corresponding to the JSON data. The version information of the check-in menu data is used to identify the version of the check-in table. Since the length and checksum of the JSON data corresponding to different check-in table versions are different, it is also necessary to determine the length information and checksum of the JSON data corresponding to the version information.
[0032] In some embodiments, determining the data description information of the inspection menu data based on the overview information includes: extracting version information, length information, and check code from the overview information according to a preset data structure, wherein the preset data structure includes the data length of the version information, the data length of the length information, and the data length of the check code.
[0033] Specifically, the overview information is generated based on a preset data structure, which includes the data length of the version information, the data length of the length information, and the data length of the checksum. The version information, length information, and checksum can be extracted from the overview information in sequence according to the data length of the version information, the data length of the length information, and the data length of the checksum.
[0034] Taking the data structure of the inspection menu as shown in Table 1 as an example: Table 1
[0035] The overview information includes 4 bytes of version information, 4 bytes of length information, and 16 bytes of checksum. Therefore, by extracting the first to fourth bytes of the overview information, the version information can be obtained; by extracting the fifth to eighth bytes, the length information can be obtained; and by extracting the ninth to twenty-fourth bytes, the checksum can be obtained.
[0036] Therefore, the definition of the inspection menu data structure provides a unified standard for the description language of the inspection menu. Using this data structure eliminates the need for manual parsing of the inspection table. Different inspection tables can be parsed from the inspection menu data, avoiding the need to develop corresponding parsing code due to changes in the inspection table.
[0037] It should be noted that the inspection menu is not limited to the structure shown in Table 1, and can also use file formats with built-in file end marks and verification.
[0038] S103: Obtain the inspection menu data from the target device based on the data description information.
[0039] Understandably, the data description information enables the terminal device to accurately retrieve the corresponding inspection menu data from the target device. Version information ensures that the version of the inspection menu on the terminal device is consistent with the software version on the target device; length information ensures that the terminal device obtains accurate inspection menu data, thereby avoiding errors in inspection menu parsing caused by missing or excessive inspection menu data; and the checksum ensures the integrity of data transmission, effectively identifying and avoiding data errors caused by transmission interference or device malfunction.
[0040] S104 parses the inspection menu data to obtain the inspection menu, and renders the inspection menu for display.
[0041] Specifically, the terminal device parses the inspection menu data to obtain the inspection menu corresponding to the current software version of the target device, and renders the inspection menu onto the terminal device's display screen to display it to the user. The user can operate on the display screen to query the point values corresponding to different points in the inspection menu, or write point values. After the user writes point values, the terminal device sends a write command to the target device to set the point values on the target device.
[0042] In the above embodiments, the defined data structure of the inspection menu provides a unified standard for the description language of the inspection menu. Based on the overview information, inspection menu data of various versions can be obtained from the target device, and the inspection menu data can be parsed to obtain the corresponding inspection menu, which is then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate the inspection table, but generates different versions of the inspection menu in real time based on the inspection menu data of different versions. There is no problem of software version mismatch with the target device, thereby improving the reliability of the inspection. Furthermore, it does not require frequent software updates to the inspection tool, thereby reducing the risk of failure and maintenance costs.
[0043] In some embodiments, the data description information includes version information, length information, and a checksum of the inspection menu data. Obtaining the inspection menu data from the target device based on the data description information includes: if, based on the version information and the checksum, it is determined that the inspection menu corresponding to the version information has not been generated, sequentially sending a first query instruction to the target device, wherein the first query instruction includes an offset of the inspection menu data and a preset reading length, and the offset in each sent first query instruction is the sum of the lengths of the received inspection menu data; sequentially receiving inspection menu data segments sent by the target device until the sum of the lengths of the received inspection menu data segments reaches the length information, to obtain at least one inspection menu data segment; and concatenating the at least one inspection menu data segment according to the receiving order to obtain the inspection menu data.
[0044] Specifically, based on the version information and the verification code, it can be determined whether the inspection menu corresponding to the version information has already been generated. If the inspection menu corresponding to the version information has already been generated, there is no need to obtain the inspection menu data again to regenerate the inspection menu; the already generated inspection menu can be directly called. For example, if there is historical version information that matches the current version information, and the verification code corresponding to that historical version information also matches the verification code, then it can be determined that the inspection menu corresponding to the current version information has been generated. If at least one of the version information and the verification code is different, then the inspection menu corresponding to the current version information has not been generated; therefore, it is necessary to obtain the inspection menu data to generate the inspection menu.
[0045] If the inspection menu corresponding to the version information has not been generated, the terminal device sends a first query command to the target device for the first time. Since this is the first time reading the inspection menu data, the offset is 0. Assuming the preset read length is 200 bytes, the target device reads the inspection menu data from byte 1 to byte 200 according to the first query command to generate the first inspection menu data segment and sends the first inspection menu data segment to the terminal device. The terminal device receives the first inspection menu data segment and determines whether the first inspection menu data segment has reached the length information. If the first inspection menu data segment has not reached the length information and the remaining length is greater than 200 bytes, the terminal device sends a first query command to the target device for the second time. The offset of the first query command is 200, and the preset read length is 200 bytes. The target device reads the inspection menu data from byte 201 to byte 400 according to the first query command to generate the second inspection menu data segment and sends it to the terminal device. The terminal device sends a second inspection menu data segment, which is received by the target device. The terminal device determines whether the sum of the lengths of the first and second inspection menu data segments reaches the required length. If it does, it stops sending the first query command. If the sum of the lengths of the first and second inspection menu data segments does not reach the required length, and the remaining length is less than 200 bytes (e.g., 100 bytes), the terminal device sends the first query command to the target device for the third time. The offset of the first query command is 400, and the preset read length is 100 bytes. The target device reads bytes 401 to 500 of the inspection menu data according to the first query command to generate a third inspection menu data segment, and sends this third inspection menu data segment to the terminal device. The terminal device receives the third inspection menu data segment. Because the sum of the lengths of the first to third inspection menu data segments reaches the required length, the terminal device stops sending the first query command. Then, the terminal device concatenates the multiple inspection menu data segments in the receiving order to obtain the inspection menu data.
[0046] Optionally, after obtaining the inspection menu data, it is also necessary to use a verification code to verify the inspection menu data to ensure that the inspection menu data obtained by the terminal device is complete.
[0047] In the above embodiments, since the length information of the inspection menu data is different, the inspection data is obtained in segments, and the total length of the returned inspection menu data segments is used to determine whether the length information has been reached, thereby ensuring that complete inspection menu data can be obtained.
[0048] In some embodiments, parsing the inspection menu data includes: obtaining the length of the outermost list of the inspection menu data; and based on the length of the outermost list, parsing each sub-item in the outermost list according to the type of each sub-item in the outermost list of the inspection menu data, wherein the inspection menu includes the outermost list and each sub-item in the outermost list.
[0049] In other words, firstly, the outermost list in the inspection menu data is parsed to obtain the length of the outermost list. Then, each sub-item in the outermost list is parsed sequentially according to its length. Each sub-item in the outermost list is parsed based on its type, where the type of the sub-item includes list and point.
[0050] Taking the type of a sub-item as an example, the corresponding point attributes of the sub-item are parsed. The point attributes include point ID (identity identifier), point name, list sorting, Chinese name, English name, readability / writeability, default value, invalid value, enumeration value, secondary confirmation, password required, and child nodes.
[0051] Taking a list as an example, the parsing method for the sublists corresponding to the subitems is similar to that for the outermost list. First, the length of the sublist corresponding to the subitem is obtained. Then, each subitem in the sublist is parsed sequentially according to its length. Each subitem in the sublist is parsed based on its type. If the subitem in the sublist is a list, it is parsed using the list parsing method; if the subitem in the sublist is a point, its point attributes are parsed.
[0052] In one optional implementation, the checkpoint menu data is parsed using a depth-first approach. That is, when the sub-items in the outermost list include both the list and the location, the list is parsed first, and then the location in the outermost list is parsed after the list is parsed.
[0053] In this embodiment, according to the above parsing method, all inspection menu data can be parsed to obtain the dynamic inspection menu transmitted by the target device. Therefore, the inspection menu on the terminal device matches the inspection table on the target device.
[0054] In some embodiments, rendering the inspection menu includes: rendering the outermost list according to a preset display format to display the outermost list; and rendering each sub-item in the outermost list according to the type of each sub-item in the outermost list to display each sub-item in the outermost list.
[0055] Specifically, the preset display format can be as follows: Figure 2 The aforementioned vertical table format will include the outermost list (i.e. Figure 2The list in the outermost list is rendered onto the screen. The sub-items in the outermost list can be either lists or points. If the sub-items in the outermost list are lists, then they can be rendered according to... Figure 2 The preset display format is shown. If the sub-item in the outermost list is a point, the point needs to be rendered on the screen as a single-line item. Therefore, each sub-item in the outermost list needs to be rendered according to its type in order to display each sub-item in the outermost list.
[0056] In some embodiments, rendering each sub-item in the outermost list of the inspection menu data according to the type of each sub-item in the outermost list includes: rendering the sub-list corresponding to the sub-item according to a preset display format when the type of the sub-item is a list and the sub-item is triggered; or sending a second query instruction to the target device when the type of the sub-item is a point, so that the target device finds the point value corresponding to the point according to the second query instruction, receives the point value sent by the target device, and renders the point name and point value of the point.
[0057] by Figure 2 For example, when the sub-item type is a point, the point name and point value need to be rendered onto the screen as an item in the list. The point value is obtained by the terminal device sending a second query command to the target device. Specifically, the terminal device sends a second query command to the target device, which may include a 2-byte point ID. The target device queries the corresponding point value based on the point ID and returns a 2-byte point ID and a 4-byte point value. After receiving the point value, the terminal device renders the point name and point value onto the display screen.
[0058] It should be noted that the point name can be rendered as the Chinese or English name of the point according to the current system language and displayed on the left side of the corresponding row in the list. The point value can be parsed into an integer or floating-point type according to the point type and displayed on the right side of the corresponding row in the list.
[0059] When the sub-item is a list, the user can access that list by clicking on it on the screen. Therefore, when a sub-item is triggered, the list is displayed. For example... Figure 2 As shown, the outermost list (i.e. Figure 2 The list (in the text) has three sub-items: sublist1, sublist2, and sublist3. When the user clicks on sublist1, they can enter sublist1, which is rendered on the screen as a vertical table. When sublist1.1 within sublist1 is triggered, sublist1.1 is also rendered on the screen as a vertical table.
[0060] It should be noted that when rendering a list, you can first render the list to the screen, and then render the sublist to the screen when the user clicks on it. Alternatively, you can render the entire list to the screen, thus eliminating the need to navigate to a sublist.
[0061] In the above embodiment, the list, location names and values are rendered on the screen according to the location menu data provided by the target device, and the inspection menu is finally displayed to the user, which solves the problem that the inspection tool in the related technology needs to have built-in code for parsing location names and values.
[0062] In an optional real-time mode, after the inspection menu is rendered to the display screen, if the target device supports writing point values, the user can edit the point values on the display screen. After receiving the point values written by the user, the terminal device sends a write command to the target device. The write command includes a 2-byte point ID and a 4-byte point value. Then the target device returns the write result or confirmation information. The terminal device can determine whether the point value was written successfully based on the write result. If the write is successful, the new point value is displayed on the display screen. If the write fails, an error message is issued.
[0063] It should be noted that the first to third query instructions and the write instruction can be set with different command codes according to the communication protocol between the terminal device and the target device, thereby defining the specifications for transmitting the inspection menu. The terminal device can read the inspection menu and corresponding point values from the target device according to this specification, without needing to care about the menu version of the target device.
[0064] The technical solution of this application is further described in detail below with reference to specific implementation methods: like Figure 3 As shown, the method for displaying the inspection menu includes the following steps: S201, the user opens the user interface on the display screen, and the display screen sends an initialization signal to the terminal device.
[0065] S202, the terminal device sends a third query command to the target device to query overview information.
[0066] S203, the target device returns overview information.
[0067] S204, the terminal device extracts version information, length information and checksum from the overview information.
[0068] S205, the terminal device sends a first query instruction to the target device. The first query instruction includes the offset of the inspection menu data and the preset reading length.
[0069] S206, the target device returns the first inspection menu data segment according to the first query instruction.
[0070] S207, the terminal device determines whether the first inspection menu data segment has reached the length information. If not, it continues to send the first query instruction and updates the offset in the first query instruction until the total length of the received inspection menu data segments reaches the length information.
[0071] S208, the terminal device splices multiple inspection menu data segments in the order of reception to obtain the inspection menu data.
[0072] S209, the terminal device parses the inspection menu data to obtain the inspection menu.
[0073] S210, the terminal device renders the outermost list onto the display screen.
[0074] S211, when a user clicks on a sublist on the display screen, the display screen sends a rendering request for the sublist to the terminal device.
[0075] S212, the terminal device renders the sublist onto the display screen.
[0076] S213, the display screen sends a rendering request for the point value corresponding to the point in the sublist to the terminal device.
[0077] S214, the terminal device sends a second query instruction to the target device, the second query instruction including the location ID.
[0078] S215, the target device queries the corresponding point value based on the point ID and returns the point ID and the corresponding point value to the terminal device.
[0079] S216, the terminal device parses the point value into an integer or floating-point type according to the point type.
[0080] S217, the terminal device renders the location name to the left of the corresponding row in the list on the display screen according to the current system language, and renders the location value to the right of the corresponding row in the list on the display screen.
[0081] S218, the user edits the point value on the display screen, and the display screen sends the new point value to the terminal device.
[0082] S219, the terminal device sends a write command to the target device. The write command includes the point ID and the new point value.
[0083] S220, the target device returns the write result or confirmation information.
[0084] S221, the terminal device displays the new point value on the display screen or issues an error message based on the writing result.
[0085] In summary, the inspection menu display method according to embodiments of the present invention provides a unified standard for the description language of the inspection menu by defining the inspection menu data structure. Based on the overview information, inspection menu data for various versions can be obtained from the target device, and the inspection menu data is parsed to obtain the corresponding inspection menu, which is then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate inspection tables; instead, it generates different versions of inspection menus in real time based on the inspection menu data for different versions, eliminating the problem of software version mismatch with the target device and thus improving the reliability of the inspection. Furthermore, it eliminates the need for frequent software updates to the inspection tool, thereby reducing the risk of failure and maintenance costs.
[0086] Corresponding to the above embodiments, embodiments of the present invention also provide a computer-readable storage medium storing a computer program thereon, which, when processed by a processor, executes the method for displaying the inspection menu of any of the foregoing embodiments.
[0087] According to the computer-readable storage medium of the present invention, by executing the computer program of the above-described method for displaying inspection menus, inspection menu data of various versions can be obtained from the target device based on overview information, and the inspection menu data can be parsed to obtain the corresponding inspection menus. The inspection menus are then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate inspection tables, but generates different versions of inspection menus in real time based on the inspection menu data of different versions. There is no problem of software version mismatch with the target device, thereby improving the reliability of inspection.
[0088] Corresponding to the above embodiments, embodiments of the present invention also provide an electronic device. For example... Figure 4 As shown, the electronic device 100 includes a memory 110, a processor 120, and a display program for the inspection menu stored in the memory 110 and executable on the processor 120. When the processor 120 executes the display program for the inspection menu, it implements the display method for the inspection menu of any of the aforementioned embodiments.
[0089] According to the electronic device of the present invention, the processor executes the computer program of the above-described method for displaying the inspection menu. Based on the overview information, the inspection menu data of various versions can be obtained from the target device, and the inspection menu data is parsed to obtain the corresponding inspection menu. The inspection menu is then displayed on the user interface. Therefore, the inspection tool does not need to pre-generate the inspection table, but generates different versions of the inspection menu in real time based on the inspection menu data of different versions. There is no problem of software version mismatch with the target device, thereby improving the reliability of the inspection.
[0090] Corresponding to the above embodiments, embodiments of the present invention also provide a device for displaying an inspection menu. For example... Figure 5As shown, the display device for the inspection menu includes: a first acquisition module 10, a determination module 20, a second acquisition module 30, a parsing module 40, and a rendering module 50.
[0091] The system comprises the following modules: a first acquisition module 10, which acquires overview information sent by the target device; a determination module 20, which determines the data description information of the inspection menu data based on the overview information, wherein the inspection menu data structure of the target device includes overview information and inspection menu data, the overview information being used to describe and verify the inspection menu data, and the inspection menu data being used to describe the content of the inspection menu of the target device; a second acquisition module 30, which acquires the inspection menu data from the target device based on the data description information; a parsing module 40, which parses the inspection menu data to obtain the inspection menu; and a rendering module 50, which renders the inspection menu for display.
[0092] In some embodiments, the data description information includes version information, length information, and a check code of the inspection menu data. The second acquisition module 30 is further configured to: when it is determined, based on the version information and the check code, that the inspection menu corresponding to the version information has not been generated, sequentially send a first query instruction to the target device. The first query instruction includes an offset of the inspection menu data and a preset reading length. The offset in each sent first query instruction is the sum of the lengths of the received inspection menu data. The module then sequentially receives inspection menu data segments sent by the target device until the sum of the lengths of the received inspection menu data segments reaches the length information, thereby obtaining at least one inspection menu data segment. Finally, the module concatenates the at least one inspection menu data segment according to the receiving order to obtain the inspection menu data.
[0093] In some embodiments, the determining module 20 is further configured to: extract version information, length information and checksum from the overview information according to a preset data structure, wherein the preset data structure includes the data length of the version information, the data length of the length information and the data length of the checksum.
[0094] In some embodiments, the parsing module 40 is further configured to: obtain the length of the outermost list of the inspection menu data; based on the length of the outermost list, parse each sub-item in the outermost list according to the type of each sub-item in the outermost list of the inspection menu data, wherein the inspection menu includes the outermost list and each sub-item in the outermost list.
[0095] In some embodiments, the parsing module 40 is further configured to: when the type of the sub-item is a list, obtain the length of the sublist corresponding to the sub-item, and based on the length of the sublist, parse each sub-item in the sublist according to the type of each sub-item in the sublist; or when the type of the sub-item is a point, parse the point attribute corresponding to the sub-item.
[0096] In some embodiments, the rendering module 50 is further configured to: render the outermost list according to a preset display format to display the outermost list; and render each sub-item in the outermost list according to the type of each sub-item in the outermost list to display each sub-item in the outermost list.
[0097] In some embodiments, the rendering module 50 is further configured to: render the sublist corresponding to the subitem according to a preset display format when the type of the subitem is a list and the subitem is triggered; or send a second query instruction to the target device when the type of the subitem is a point, so that the target device can find the point value corresponding to the point according to the second query instruction, receive the point value sent by the target device, and render the point name and point value of the point.
[0098] It should be noted that the specific implementation of the inspection menu display device in this embodiment corresponds one-to-one with the specific implementation of the inspection menu display method in the foregoing embodiments of this invention, and will not be repeated here.
[0099] According to an embodiment of the present invention, the device for displaying an inspection menu acquires overview information sent by a target device through a first acquisition module, and determines data description information of the inspection menu data based on the overview information through a determination module. The inspection menu data structure of the target device includes overview information and inspection menu data. The overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device. The device also acquires the inspection menu data from the target device based on the data description information through a second acquisition module, parses the inspection menu data through a parsing module to obtain the inspection menu, and renders the inspection menu through a rendering module for display. Thus, the defined inspection menu data structure provides a unified standard for the description language of the inspection menu. Based on the overview information, various versions of inspection menu data can be acquired from the target device, parsed to obtain the corresponding inspection menu, and displayed on the user interface. Therefore, the inspection tool does not need to pre-generate an inspection table, but instead generates different versions of the inspection menu in real time based on different versions of the inspection menu data, eliminating the problem of software version mismatch with the target device and improving the reliability of the inspection.
[0100] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.
[0101] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.
[0102] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0103] Furthermore, the terms "first," "second," etc., used in the embodiments of this invention are for descriptive purposes only and should not be construed as indicating or implying relative importance, or implicitly specifying the number of technical features indicated in this embodiment. Therefore, features defined with terms such as "first" and "second" in the embodiments of this invention can explicitly or implicitly indicate that the embodiment includes at least one of those features. In the description of this invention, the word "multiple" means at least two or more, such as two, three, four, etc., unless otherwise explicitly specified in the embodiments.
[0104] In this invention, unless otherwise explicitly specified or limited in the embodiments, the terms "installation," "connection," "joining," and "fixing" appearing in the embodiments should be interpreted broadly. For example, a connection can be a fixed connection, a detachable connection, or an integral part; it can also be a mechanical connection, an electrical connection, etc. Of course, it can also be a direct connection, or an indirect connection through an intermediate medium, or it can be the internal communication of two components, or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific implementation.
[0105] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.
Claims
1. A method for displaying an inspection menu, characterized in that, include: Obtain overview information sent by the target device; The data description information of the inspection menu data is determined based on the overview information. The inspection menu data structure of the target device includes the overview information and the inspection menu data. The overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device. The inspection menu data is obtained from the target device based on the data description information; The inspection menu data is parsed to obtain the inspection menu, and the inspection menu is rendered to display the inspection menu.
2. The method according to claim 1, characterized in that, The data description information includes version information, length information, and a checksum of the inspection menu data. Obtaining the inspection menu data from the target device based on the data description information includes: If it is determined from the version information and the verification code that the inspection menu corresponding to the version information has not been generated, a first query instruction is sent to the target device in sequence. The first query instruction includes the offset of the inspection menu data and a preset reading length. The offset in each first query instruction is the sum of the lengths of the received inspection menu data. The system sequentially receives inspection menu data segments sent by the target device until the total length of the received inspection menu data segments reaches the length information, so as to obtain at least one inspection menu data segment. The inspection menu data is obtained by concatenating the at least one inspection menu data segment in the order of receipt.
3. The method according to claim 2, characterized in that, Based on the overview information, the data description information for the inspection menu data is determined, including: According to a preset data structure, the version information, the length information, and the checksum are extracted from the overview information, wherein the preset data structure includes the data length of the version information, the data length of the length information, and the data length of the checksum.
4. The method according to any one of claims 1-3, characterized in that, The inspection menu data is parsed, including: Obtain the length of the outermost list of the inspection menu data; Based on the length of the outermost list, each sub-item in the outermost list of the inspection menu data is parsed sequentially according to its type. The inspection menu includes the outermost list and each sub-item in the outermost list.
5. The method according to claim 4, characterized in that, Based on the type of each sub-item in the outermost list of the inspection menu data, each sub-item in the outermost list is parsed, including: If the type of the sub-item is a list, obtain the length of the sublist corresponding to the sub-item, and based on the length of the sublist, parse each sub-item in the sublist according to its type; or If the type of the sub-item is a point, the point attribute corresponding to the sub-item is parsed.
6. The method according to claim 4, characterized in that, Rendering the inspection menu includes: The outermost list is rendered according to a preset display format in order to display the outermost list. Each item in the outermost list is rendered based on its type to display each item in the outermost list.
7. The method according to claim 6, characterized in that, Based on the type of each sub-item in the outermost list of the inspection menu data, each sub-item in the outermost list is rendered, including: When the type of the sub-item is a list and the sub-item is triggered, the sub-list corresponding to the sub-item is rendered according to the preset display format; or When the type of the sub-item is a point, a second query instruction is sent to the target device so that the target device can find the point value corresponding to the point according to the second query instruction, receive the point value sent by the target device, and render the point name and the point value of the point.
8. A computer-readable storage medium, characterized in that, It stores a computer program, which, when processed by a processor, executes the method for displaying the inspection menu as described in any one of claims 1-7.
9. An electronic device, characterized in that, The device includes a memory, a processor, and a display program for an inspection menu stored in the memory and executable on the processor. When the processor executes the display program for the inspection menu, it implements the method for displaying the inspection menu as described in any one of claims 1-7.
10. A display device for an inspection menu, characterized in that, include: The first acquisition module is used to acquire overview information sent by the target device; The determination module is used to determine the data description information of the inspection menu data based on the overview information. The inspection menu data structure of the target device includes overview information and inspection menu data. The overview information is used to describe and verify the inspection menu data, and the inspection menu data is used to describe the content of the inspection menu of the target device. The second acquisition module is used to acquire the inspection menu data from the target device according to the data description information; The parsing module is used to parse the inspection menu data to obtain the inspection menu; The rendering module is used to render the inspection menu for display.