Debugging tool interaction control method, device and equipment of wireless intelligent equipment

Abstract

The embodiment of the invention provides a debugging tool interaction control method, device and equipment for wireless intelligent equipment, and belongs to the field of wireless equipment testing. Comprising the steps that a tool main interface is displayed, the tool main interface comprises a mode selection control, a debugging starting control and a testing starting control, and the mode selection control is used for selecting to enter a function debugging mode or a product testing mode; in a function debugging mode, in response to a trigger instruction for the debugging start control, displaying a code scanning network access prompt interface for waiting for an identification code of an external scanning target wireless intelligent device, establishing a connection with the target wireless intelligent device according to the identification code, obtaining device information, and storing the device information in a database; and in response to the obtained equipment information, displaying a debugging main interface which comprises a first equipment information area and a function debugging area, the first equipment information area being used for displaying the equipment information, and the function debugging area being used for triggering function debugging. The invention aims to improve the testing efficiency of the wireless intelligent equipment.

Description

Technical Field

[0001] The present application relates to the field of wireless device testing technology, and in particular to a method, apparatus, and device for interactive control of debugging tools for wireless smart devices. Background Art

[0002] In the existing technology, when wireless smart devices are being developed and debugged or tested on product lines, workers need to use a gateway to complete the network access of the wireless smart devices. This makes the performance of the product during the test dependent on the network performance of the gateway. Alternatively, wireless smart devices can be added and tested by entering complex command lines in a Linux system environment. However, this also has the problems of complex Linux system environment operations, long time consumption, and low testing efficiency, which affects the efficiency of both R&D and production.

[0003] In summary, the technical problems existing in the relevant technologies need to be improved. Summary of the Invention

[0004] The main purpose of the embodiments of the present application is to provide a method, apparatus and device for interactive control of debugging tools for wireless smart devices, aiming to improve the testing efficiency of wireless smart devices.

[0005] To achieve the above objectives, an embodiment of the present application provides a method for interactively controlling a debugging tool of a wireless smart device, the method comprising: Display the tool main interface, which includes a mode selection control, a debug start control, and a test start control. The mode selection control is used to select the debug tool to enter a function debug mode or a product test mode; In the function debugging mode, in response to a trigger instruction of the debugging startup control, a code scanning network access prompt interface is displayed, wherein the code scanning network access prompt interface is used to wait for an external code scanning device to scan the identification code of the target wireless smart device, establish a connection with the target wireless smart device according to the identification code, obtain corresponding device information, and store the device information in a database; In response to acquiring the device information, a debugging main interface is displayed, the debugging main interface including a first device information area and a function debugging area, the first device information area is used to display the device information, and the function debugging area is used to trigger function debugging of the target wireless smart device.

[0006] In some embodiments, the function debugging area includes a switch light debugging control, and triggering the function debugging of the target wireless smart device includes: In response to a trigger instruction for the light switch debugging control, a light control interface is displayed, wherein the light control interface includes a light switch control control, and the light switch control control is used to control the on and off state of a preset light unit on the target wireless smart device.

[0007] In some embodiments, the function debugging area further includes a light brightness debugging control, and triggering the function debugging of the target wireless smart device further includes: In response to a trigger instruction for the light brightness debugging control, the light control interface is displayed. The light control interface also includes a brightness control control and a brightness information area. The brightness control control is used to control the light brightness of the preset light unit, and the brightness information area is used to display corresponding brightness information according to the light brightness.

[0008] In some embodiments, the function debugging area includes a network exit control control, and triggering the function debugging of the target wireless smart device includes: In response to the trigger instruction of the network exit control component, the device information of the target wireless smart device is deleted from the database, the connection with the target wireless smart device is disconnected, and the tool main interface is displayed.

[0009] In some embodiments, the method further comprises: In the product test mode, in response to a trigger instruction of the test start control, the scan code to access the network prompt interface is displayed, and a connection with the target wireless smart device is waited for through the scan code to access the network prompt interface, the device information is obtained, and the device information is stored in the database; In response to obtaining the device information, a test main interface is displayed, wherein the test main interface includes a second device information area and a test progress area, wherein the second device information area is used to display the device information, and the test progress area is used to display the progress of the functional test of the target wireless smart device, wherein the functional test includes a light on / off function test, a light brightness adjustment function test, and a network logoff function test that are automatically performed in sequence.

[0010] In some embodiments, the method further comprises: In response to all functions being tested in the product test mode being passed, deleting the device information of the target wireless smart device from the database, disconnecting from the target wireless smart device, and displaying a test pass prompt interface; In response to a failure in the test of any function in the product test mode, the process of the function test is stopped and a test failure prompt interface is displayed.

[0011] In some embodiments, the debugging main interface and the testing main interface both include a reset control, and the method further includes: In response to the trigger instruction of the reset control, the Bluetooth adapter state of the target wireless smart device is reset.

[0012] In some embodiments, the tool main interface further includes a log control, and the method further includes: In response to a trigger instruction for the log control, a log area is displayed on the tool main interface, and the log area is used to display function debugging information, function test information and / or error information.

[0013] To achieve the above-mentioned purpose, another aspect of the present application provides a debugging tool interactive control device for a wireless smart device, the device comprising: A first processing module is configured to display a tool main interface, wherein the tool main interface includes a mode selection control, a debug start control, and a test start control, wherein the mode selection control is configured to select a function debug mode or a product test mode for the debug tool; a second processing module configured to, in the function debugging mode, display a code scanning network access prompt interface in response to a trigger instruction for the debugging startup control, wherein the code scanning network access prompt interface is configured to wait for an external code scanning device to scan an identification code of a target wireless smart device, establish a connection with the target wireless smart device according to the identification code, obtain corresponding device information, and store the device information in a database; The third processing module is used to display a debugging main interface in response to obtaining the device information, where the debugging main interface includes a first device information area and a function debugging area, where the first device information area is used to display the device information, and the function debugging area is used to trigger function debugging of the target wireless smart device.

[0014] To achieve the above-mentioned purpose, another aspect of an embodiment of the present application provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the above-mentioned method when executing the computer program.

[0015] The embodiments of the present application include at least the following beneficial effects: the present application provides a method, apparatus and device for interactive control of a debugging tool for a wireless smart device, wherein the scheme displays a tool main interface and uses a mode selection control on the tool main interface to select the debugging tool to enter a functional debugging mode or a product testing mode; in the functional debugging mode, in response to a trigger instruction of a debugging start control on the interface, a code scanning network prompt interface is displayed, through which an external code scanning device is waited for to scan the identification code of a target wireless smart device, based on which the debugging tool establishes a connection with the target wireless smart device, obtains corresponding device information, and stores the device information in a database; in response to obtaining the device information, a debugging main interface is displayed, the debugging main interface includes a first device information area and a function debugging area, the device information is displayed in the first device information area, and the function debugging of the target wireless smart device is performed in the function debugging area. Compared with debugging that requires relying on a gateway or Linux system environment, the present application realizes a simplified and intuitive visualization of the debugging process through a debugging tool with a visual interface, which not only enables staff to more intuitively understand the relevant information of the debugging process, but also helps to reduce the learning cost and operation cost required for debugging operations, improve testing efficiency, and improve the efficiency of R&D and production ends. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 This is a flowchart of a debugging tool interactive control method for a wireless smart device provided in an embodiment of the present application; Figure 2 This is a schematic diagram of the main interface of the tool in the embodiment of the present application; Figure 3 This is a schematic diagram of the QR code scanning prompt interface for network access in an embodiment of the present application; Figure 4 This is a schematic diagram of the main debugging interface of the embodiment of the present application; Figure 5 is a schematic diagram of a lighting control interface according to an embodiment of the present application; Figure 6 This is a schematic diagram of the main test interface of the embodiment of the present application; Figure 7 This is a schematic diagram of the test pass prompt interface of the embodiment of the present application; Figure 8 This is a schematic diagram of a prompt interface for a test failure in an embodiment of the present application; Figure 9 This is a structural diagram of an interactive control device for a debugging tool of a wireless smart device provided in an embodiment of the present application; Figure 10 This is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present application. They are merely examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the appended claims.

[0018] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing the embodiments of this application only and are not intended to limit this application.

[0019] In the existing technology, when wireless smart devices are being developed and debugged or tested on product lines, workers need to use a gateway to complete the network access of the wireless smart devices. This makes the performance of the product during the test dependent on the network performance of the gateway. Alternatively, wireless smart devices can be added and tested by entering complex command lines in a Linux system environment. However, this also has the problems of complex Linux system environment operations, long time consumption, and low testing efficiency, which affects the efficiency of both R&D and production.

[0020] In view of this, the embodiments of the present application provide a method, apparatus and device for interactive control of a debugging tool of a wireless smart device. Figure 1 This is an optional flowchart of a debugging tool interactive control method for a wireless smart device provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S100 to S300.

[0021] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0022] Step S100, displaying the tool main interface 100, which includes a mode selection control 110, a debug start control 120, and a test start control 130. The mode selection control 110 is used to select the debug tool to enter a function debug mode or a product test mode; The debugging tool described in the embodiment of the present application is a software tool that can be applied to devices such as PC terminals, mobile terminals or embedded devices. It requires the device to have a display unit for outputting visual content, such as a display screen configured for a PC terminal, so as to perform visual output through the display unit and obtain user input operations through input units such as a mouse or touch screen to achieve the interactive control required by the method of this embodiment.

[0023] Specifically, the tool main interface 100 is the default interface displayed after the debugging tool is started. Figure 2 The tool main interface 100 includes at least a mode selection control 110, a debug start control 120, and a test start control 130. The debugging tool of this embodiment can be used to perform functional debugging or product testing on wireless smart devices. Functional debugging is used when R&D staff are debugging a product while it is still in the R&D stage, while product testing is used when a product is developed and is being tested on the production line after it is completed.

[0024] Corresponding to the two application scenarios of function debugging and product testing, the debugging tool is provided with corresponding function debugging mode and product testing mode. The debugging tool can be selected to enter either mode by triggering the mode selection control 110. The mode selection control 110 can be set to a style such as a drop-down menu or a check option. Figure 2 The mode selection control 110 can be preset to select one of the modes, for example, the product test mode can be preset to select the product test mode.

[0025] On the other hand, the debug start control 120 is used to start the functional debugging process, and the test start control 130 is used to start the product testing process. Both controls can be set as buttons or checkboxes, and can be directly triggered by clicking or other operations. It should be noted that if the current debugging tool enters a mode that does not correspond to the corresponding one, for example, the test start control 130 in the functional debugging mode can be hidden or grayed out, and the control cannot be triggered. This is a fool-proof design to prevent staff from operating it incorrectly.

[0026] Step S200: In the function debugging mode, in response to a trigger instruction of the debug start control 120, a code scanning network prompt interface 200 is displayed. The code scanning network prompt interface 200 is used to wait for an external code scanning device to scan the identification code of the target wireless smart device, establish a connection with the target wireless smart device according to the identification code, obtain corresponding device information, and store the device information in a database; After the debugging tool enters the function debugging mode, in response to the trigger instruction of the debugging start control 120, the function debugging process is executed. At this time, it is necessary to verify the network access function of the target wireless smart device first. On the interface of the debugging tool, refer to Figure 3, a QR code scanning and network access prompt interface 200 is displayed. Text or legends can be displayed on this interface to guide the staff on what to do at this time. At this time, outside the debugging tool, the staff needs to use a barcode scanning gun or other barcode scanning device to scan the identification code on the target wireless smart device, so that the debugging tool can identify the target wireless smart device according to the identification code and establish a communication connection with it.

[0027] After the communication connection is successfully established, it means that the network access function of the target wireless smart device is normal. Furthermore, the corresponding device information is obtained to help staff visually identify the target wireless smart device and store the device information in the database, ensuring that the data archiving function is also operating normally during the function debugging process.

[0028] In step S300, in response to obtaining device information, the debugging main interface 300 is displayed. The debugging main interface 300 includes a first device information area 310 and a function debugging area 320. The first device information area 310 is used to display device information, and the function debugging area 320 is used to trigger function debugging of the target wireless smart device.

[0029] After confirming that the target wireless smart device has a normal network access function, the debugging main interface 300 is displayed. Figure 4 The debugging main interface 300 includes a first device information area 310 and a function debugging area 320. The first device information area 310 is used to display the acquired device information of the target wireless smart device, such as the device model and ID, etc. The function debugging area 320 is used to display multiple trigger controls for function debugging to meet the staff's debugging needs for various functions.

[0030] It should be noted that the various interfaces described in the embodiments of the present application, such as the tool main interface 100 and the debugging main interface 300, are all different states of the debugging tool during use. For example, some controls set in the tool main interface 100 are not hidden in the debugging main interface 300. There may be the same areas or controls between two different interfaces. The embodiments of the present application only limit the controls or areas that are more critical for the corresponding interface in order to realize its corresponding functions, and do not fully list all the same or different controls between different interfaces. Therefore, in addition to the above description, the tool main interface 100 and the debugging main interface 300 may also include other controls, such as those that can be referred to. Figure 2 and Figure 4 The comparison is not limited in this embodiment.

[0031] In steps S100 to S300 shown in the embodiment of the present application, by displaying the tool main interface 100, using the mode selection control 110 of the tool main interface 100 to select the debugging tool to enter the functional debugging mode or product testing mode; in the functional debugging mode, in response to the trigger instruction of the debugging start control 120 on the interface, the code scanning network prompt interface 200 is displayed, and the code scanning network prompt interface 200 waits for the external code scanning device to scan the identification code of the target wireless smart device through the code scanning network prompt interface 200. Based on the identification code, the debugging tool establishes a connection with the target wireless smart device, obtains the corresponding device information, and stores the device information in the database; in response to the acquisition of the device information, the debugging main interface 300 is displayed. The debugging main interface 300 includes a first device information area 310 and a functional debugging area 320. The device information is displayed through the first device information area 310, and the functional debugging of the target wireless smart device is performed through the functional debugging area 320. Compared with debugging that requires relying on a gateway or Linux system environment, this application simplifies and intuitively visualizes the debugging process through a debugging tool with a visual interface. This not only enables staff to understand the relevant information of the debugging process more intuitively, but also helps to reduce the learning and operating costs required for debugging operations, improve testing efficiency, and also improve the efficiency of R&D and production.

[0032] In some embodiments, the function debugging area 320 includes a light on / off debugging control 321 , and triggering the function debugging of the target wireless smart device includes: In response to the trigger instruction of the light switch debugging control 321, the light control interface 400 is displayed. The light control interface 400 includes the light switch control control 410. The light switch control control 410 is used to control the on and off state of the preset light unit on the target wireless smart device.

[0033] Optionally, the function debugging area 320 includes a light switch debugging control 321, which is used to trigger the preset light unit on the debugging target wireless smart device to turn on and off normally. It can be set to a button or other style. When the light switch debugging control 321 is triggered, the light control interface 400 is displayed. This interface can be referred to Figure 5 The interface includes a light switch control 410, which is used to control the on / off state of a preset light unit on the target wireless smart device.

[0034] Specifically, the preset lighting unit is an LED lamp or other lighting device. Taking an LED lamp as an example, it can include multiple LED lamps. The switch light control control 410 is configured to control the on / off state of each LED lamp individually, and / or to control the on / off state of each LED lamp uniformly. When the on / off state is the off state, triggering the switch light control control 410 can control the on / off state to switch to the on state, and when the on / off state is the on state, triggering the switch light control control 410 can control the on / off state to switch to the off state. For different current on / off states, the switch light control control 410 can be set as buttons of different styles, for example, with different prompt text on the buttons for distinction, or can be set as styles such as check boxes, etc., which are not limited in this embodiment.

[0035] Through the light switch debugging control 321, the staff can conveniently debug the light switch function, improve the testing efficiency, and also improve the efficiency of the R&D end.

[0036] In some embodiments, the function debugging area 320 further includes a light brightness debugging control 322 , and triggering the function debugging of the target wireless smart device further includes: In response to the trigger instruction of the light brightness debugging control 322, the light control interface 400 is displayed. The light control interface 400 also includes a brightness control control 420 and a brightness information area 430. The brightness control control 420 is used to control the light brightness of the preset light unit, and the brightness information area 430 is used to display corresponding brightness information according to the light brightness.

[0037] Optionally, the function debugging area 320 may further include a light brightness debugging control 322, which is used to trigger the debugging of whether the light brightness of the preset light unit can be changed according to the control, and can be set to a button or other style. When the light brightness debugging control 322 is triggered, the light control interface 400 is displayed, and the light control interface 400 can be as follows: Figure 5 Generally, a light switch control control 410, a brightness control control 420 and a brightness information area 430 are integrated.

[0038] Specifically, the brightness control control 420 is used to control the change of the light brightness of the preset light unit. It can be set to a style such as a slider or a numeric input box to display the minimum brightness to the maximum brightness supported by the preset light unit in the form of a percentage; on the other hand, the brightness information area 430 is used to display the brightness-related information of the current preset light unit, such as intuitively displaying the brightness value of the current preset light unit in lumens, and can also combine it with a percentage number to display the relationship between the brightness of the current preset light unit and the maximum brightness.

[0039] Through the light brightness debugging control 322, the staff can conveniently debug the light brightness adjustment function, thereby improving the test efficiency and the efficiency of the R&D end.

[0040] In some embodiments, the function debugging area 320 includes a network exit control control 323, and triggering the function debugging of the target wireless smart device includes: In response to the trigger instruction of the network exit control component 323, the device information of the target wireless smart device is deleted from the database, the connection with the target wireless smart device is disconnected, and the tool main interface 100 is displayed.

[0041] Optionally, the function debugging area 320 may also include a network exit control control 323, which is used to debug whether the network exit function of the target wireless smart device is normal. The control can be set to a button or other style. When the network exit control control 323 is triggered, the connection between the debugging tool and the target wireless smart device is disconnected, and its related device information is removed, specifically deleted from the database, thereby completing the network exit of the target wireless smart device.

[0042] In addition, if the network exit is normal, the debugging tool and the target wireless smart device will be disconnected, so the debugging of the network exit function can be arranged to be the last debugging.

[0043] Through the off-line control control 323, the staff can conveniently debug the off-line function, improve the testing efficiency, and also improve the efficiency of the R&D end.

[0044] In some embodiments, the method further comprises: In the product test mode, in response to the trigger instruction of the test start control 130, the code scanning network prompt interface 200 is displayed, and the code scanning network prompt interface 200 waits for the connection with the target wireless smart device to be established, obtains the device information, and stores the device information in the database; In response to obtaining the device information, the test main interface 500 is displayed. The test main interface 500 includes a second device information area 510 and a test progress area 520. The second device information area 510 is used to display device information, and the test progress area 520 is used to display the progress of the functional test of the target wireless smart device. The functional test includes an automatic and sequential light on / off function test, a light brightness adjustment function test, and a network exit function test.

[0045] Unlike functional debugging mode, product testing mode is used for completed products, after they have been designed and manufactured on the production line, before they are put into use. Therefore, the automation of the product testing process is crucial to production efficiency, and the functional test items in product testing mode must cover as many functions as can be debugged during functional debugging as possible.

[0046] Based on this, the product test mode of the debugging tool in this embodiment can automatically and sequentially test the light on / off function, light brightness adjustment function, and network logoff function described in the above embodiment. Regarding the network access function, it is understood that the network access test must wait for an external code scanning device to scan the product's identification code. Therefore, it is necessary to display the same code scanning network access prompt interface 200 as in the function debugging mode, and wait through this interface. This scanning step can be performed manually by a production line worker or automatically by an automated production line. After establishing a connection with the target wireless smart device, the device information is similarly obtained and stored in the database.

[0047] Further, after passing the network function test and obtaining the device information, refer to Figure 6 , displaying the test main interface 500, which includes at least a second device information area 510 and a test progress area 520. Optionally, the test main interface 500 may also include a function debugging area. The second device information area 510 is used to display the acquired device information of the target wireless smart device, such as the device model and ID. The second device information area 510 differs from the first device information area 310 only in that it operates in two different modes. The test progress area 520 is used to display the progress of the functional test of the target wireless smart device, for example, using text, percentage, or progress bar style controls to indicate the currently running test item and its execution progress.

[0048] In other embodiments, the debugging tool can also be used to perform product testing on multiple products at the same time. After passing the network access function test, product testing on multiple products can be performed synchronously. The device information and function test progress corresponding to each product are displayed in the second device information area 510 and the test progress area 520 in a list or other style.

[0049] Through the test main interface 500, the debugging tool can clearly and concisely inform the staff of the current test progress, thereby helping the staff to understand the product testing status of the target wireless smart device and ensure the effectiveness of the product testing. In addition, after the network access is passed, the debugging tool can automatically test multiple functions, which also improves the efficiency of the production end.

[0050] In some embodiments, in response to a trigger instruction on the function debugging area of ​​the test main interface 500 , the arrangement order of each debugging control in the function debugging area is refreshed and displayed, and the order of test items of the automatic functional test is changed according to the changed arrangement order.

[0051] Optionally, the function debugging area of ​​the test main interface 500 can support users to adjust the arrangement order of various debugging controls by dragging, long pressing, or right-clicking the mouse. By integrating an interpreter in the backend, the debugging tool can determine the order of test items in the automated functional testing process based on the arrangement order of the debugging controls on the interface, thereby enabling the editing of test scripts. It can be understood that, except for the network access function and the network exit function, which need to be set at the start and end positions respectively, the order of other test items can be customized. If the debugging tool can support debugging of more functions in other embodiments, the same is true. This allows users to customize and edit product test scripts through an intuitive visual interface, improving the convenience of product testing.

[0052] If the debugging tool is used to test multiple products simultaneously, each product can display its corresponding functional debugging area, allowing users to edit the order of test items for multiple different products being tested simultaneously, further expanding the convenience of using the debugging tool for product testing.

[0053] In addition, the order of test items customized by the user can also be summarized and counted. Specifically, when the debugging tool tests the product, it also determines the device type of the product based on the device information, and stores the order of the test items it executes in the database according to the device type for recording. The order of test items for different device types is counted separately. The order of test items executed may actually be the order of test items that the user has edited to meet the user's needs. Therefore, for the order of test items recorded in the database, the most frequent order or the order of some items that will be fixed and executed continuously are counted, and defined as the adaptation test order for the corresponding device type. When a new product of the corresponding device type is connected to the debugging tool for product testing, the debugging control of the functional debugging area is displayed according to the adjusted adaptation test order, and automated functional testing is performed according to the adaptation test order, further improving the user experience of the debugging tool.

[0054] In some embodiments, the method further comprises: In response to all functions being tested in the product test mode being passed, the device information of the target wireless smart device is deleted from the database, the connection with the target wireless smart device is disconnected, and a test pass prompt interface 600 is displayed; In response to any function failing the test in the product test mode, the function test process is stopped and a test failure prompt interface 700 is displayed.

[0055] When all the test items of functions are passed in the product test mode, since the last function tested is the network disconnection function, the network disconnection of the target wireless smart device is completed at this time, its device information is deleted from the database, and the connection is disconnected. Figure 7, a test pass prompt interface 600 is displayed, which can prompt the staff in the form of text or pictures that the target wireless smart device has passed the product test and can continue to test the next product.

[0056] When in product test mode, if any of the functions including network access, light on / off, light brightness adjustment and network exit fails, the function test process will be stopped immediately and the following will be displayed: Figure 8 The test failed prompt interface 700 shown in the figure can have the same overall style as the test passed prompt interface 600. The only difference is the style of the text or picture used for prompts in the interface. For example, the text in the test failed prompt interface 700 can be set to red to serve as a striking prompt.

[0057] Through the test pass prompt interface 600 and the test fail prompt interface 700, the staff can intuitively understand the test results of the target wireless smart device according to the interface, arrange subsequent product testing processes, and improve the efficiency of the production end.

[0058] In some embodiments, both the debugging main interface 300 and the testing main interface 500 include a reset control 140 , and the method further includes: In response to the triggering instruction of the reset control 140 , the Bluetooth adapter status of the target wireless smart device is reset.

[0059] Optionally, to address abnormalities during some functional debugging or functional testing, such as unstable connections, a reset control 140 is provided on both the debugging main interface 300 and the testing main interface 500. The reset control 140 can be configured as a button, for example. By triggering the reset control 140, the state of the Bluetooth adapter on the target wireless smart device can be reset. This allows personnel to use the reset control 140 displayed by the debugging tool to help resolve abnormalities during functional debugging or functional testing, thereby improving the reliability of the debugging tool.

[0060] In some embodiments, the tool main interface 100 further includes a log control 150, and the method further includes: In response to a trigger instruction for the log control 150 , a log area is displayed on the tool main interface 100 , and the log area is used to display function debugging information, function test information and / or error information.

[0061] Optionally, a log control 150 is further provided on the tool main interface 100. The log control 150 can be set to a style such as a button or a check option. In response to a trigger instruction of the log control 150, a log area is displayed on the tool main interface 100. Figure 8The log area is used to display the function debugging information and / or function test information generated by the debugging tool when performing function debugging and / or function testing before the current moment. If errors or other problems occur, the error information is also included, which is helpful for staff to check the information in the log area to understand the previous equipment debugging or testing status.

[0062] On the other hand, the log control 150 can also be set in the debugging main interface 300 and the testing main interface 500, and the log area can also be displayed by triggering the log control 150 during the function debugging or function testing process. At this time, the log area is equivalent to displaying the log information generated by the current function debugging or function testing process, which can help the staff confirm the progress of the function debugging or function testing.

[0063] In addition, the information recorded in the log area can be set to be cleared when the debugging tool is closed, thereby protecting the privacy of device information.

[0064] In other embodiments, other controls may be provided in the tool main interface 100, the debugging main interface 300 and / or the test main interface 500, for example Figure 2 The obtain network information control 160 and the stop control control 170 shown are used to support the staff to understand the connected network information and stop the function debugging process or function testing process, so as to improve the diversity of the debugging tool functions.

[0065] The following describes the embodiments of the present invention in detail with reference to specific application examples: In an embodiment of the present application, a method for interactively controlling a debugging tool of a wireless smart device is provided. Figure 2 The tool main interface 100 shown includes a mode selection control 110 , a debug start control 120 , and a test start control 130 . The user can select to enter a function debug mode or a product test mode by triggering the mode selection control 110 .

[0066] When the user chooses to enter the function debugging mode, the user triggers the debugging start control 120, and the following is displayed: Figure 3 The code scanning network prompt interface 200 shown in the figure prompts that the code scanning network prompt interface 200 is waiting for the external code scanning device to scan the identification code of the target wireless smart device, connect to the network based on the identification code, establish a connection with the target wireless smart device, obtain its device information, and store the device information in the database. After obtaining the device information and completing the network, the following is displayed: Figure 4The debugging main interface 300 shown includes a first device information area 310 and a function debugging area 320 . The first device information area 310 can display device information of the target wireless smart device being debugged.

[0067] Function debugging area 320 includes switch light debugging control 321, light brightness debugging control 322 and network exit control control 323. When the user triggers switch light debugging control 321 or light brightness debugging control 322, the following is displayed: Figure 5 The light control interface 400 shown includes a light on / off control control 410, a brightness control control 420, and a brightness information area 430. When a user triggers the light on / off control control 410, he can control the on / off state of a preset light unit on the target wireless smart device. When the user triggers the brightness control control 420, he can adjust the brightness of the preset light unit. The brightness information area 430 displays the brightness information of the current preset light unit.

[0068] When the user triggers the network exit control control 323 , the device information of the target wireless smart device is deleted from the database, and its connection is disconnected, thereby realizing network exit and returning to the display tool main interface 100 .

[0069] On the other hand, when the user chooses to enter the product test mode, the user can also trigger the test start control 130 to display the scan code network prompt interface 200 to complete the network operation. Figure 6 The test main interface 500 is shown. In addition to the same network access operation, the test main interface 500 includes a second device information area 510 and a test progress area 520. The second device information area 510 is also used to display the device information of the target wireless smart device. After the test main interface 500 is displayed, the debugging tool automatically performs the light switch function test, light brightness adjustment function test and network exit function test in sequence, and displays the function test progress in the test progress area 520. If any function fails to pass the test during the function test, the function test process is stopped and the following is displayed: Figure 8 The test fails prompt interface 700 shown in FIG. 7 is displayed. If all functions are tested successfully, the device will be disconnected from the network, the device information will be deleted from the database, and the connection will be disconnected. Figure 7 A test pass prompt interface 600 is shown.

[0070] In addition, the debugging main interface 300 and the testing main interface 500 also include a reset control 140. When the user triggers the reset control 140, the process of functional debugging or functional testing can be reset. If the process is in the process of automated functional testing, the process of functional testing is stopped, the connection with the target wireless smart device is disconnected, and the state of the target wireless smart device is reset.

[0071] The tool main interface 100 further includes a log control 150 . When a user triggers the log control 150 , a log area can be displayed in the tool main interface 100 , through which function debugging information, function test information and / or error information can be viewed.

[0072] See also Figure 9 The present application also provides a debugging tool interactive control device for a wireless smart device, which can implement the above-mentioned debugging tool interactive control method for a wireless smart device. The device includes: The first processing module is used to display the tool main interface 100, which includes a mode selection control 110, a debugging start control 120, and a test start control 130. The mode selection control 110 is used to select the debugging tool to enter the function debugging mode or the product testing mode; The second processing module is configured to, in the function debugging mode, respond to a trigger instruction of the debugging startup control 120 to display a code scanning network access prompt interface 200, wherein the code scanning network access prompt interface 200 is configured to wait for an external code scanning device to scan the identification code of the target wireless smart device, establish a connection with the target wireless smart device according to the identification code, obtain corresponding device information, and store the device information in a database; The third processing module is used to display the debugging main interface 300 in response to obtaining the device information. The debugging main interface 300 includes a first device information area 310 and a function debugging area 320. The first device information area 310 is used to display device information, and the function debugging area 320 is used to trigger function debugging of the target wireless smart device.

[0073] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0074] The present application also provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-mentioned method for interactive control of a debugging tool for a wireless smart device. The electronic device can be any smart terminal, including a tablet computer and an in-vehicle computer.

[0075] It can be understood that the contents of the above method embodiments are applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0076] See also Figure 10 , Figure 10 The hardware structure of an electronic device according to another embodiment is shown. The electronic device includes: The processor 901 can be implemented as a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application; The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the debugging tool interactive control method for a wireless smart device in the embodiments of this application. Input / output interface 903, used to implement information input and output; Communication interface 904, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.); Bus 905 , which transmits information between various components of the device (e.g., processor 901 , memory 902 , input / output interface 903 , and communication interface 904 ); The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0077] The embodiments described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0078] Those skilled in the art will appreciate that all or some of the steps in the methods, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.

[0079] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0080] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0081] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the above-mentioned units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0082] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0083] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0084] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes multiple instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: various media that can store programs, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0085] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present invention should be within the scope of the present invention.

Claims

1. A debugging tool interactive control method for a wireless smart device, characterized in that: The method comprises: Display the tool main interface, which includes a mode selection control, a debug start control, and a test start control. The mode selection control is used to select the debug tool to enter a function debug mode or a product test mode; In the function debugging mode, in response to a trigger instruction of the debugging startup control, a code scanning network access prompt interface is displayed, wherein the code scanning network access prompt interface is used to wait for an external code scanning device to scan the identification code of the target wireless smart device, establish a connection with the target wireless smart device according to the identification code, obtain corresponding device information, and store the device information in a database; In response to acquiring the device information, a debugging main interface is displayed, the debugging main interface including a first device information area and a function debugging area, the first device information area is used to display the device information, and the function debugging area is used to trigger function debugging of the target wireless smart device.

2. The method according to claim 1, characterized in that The function debugging area includes a switch light debugging control, and triggering the function debugging of the target wireless smart device includes: In response to a trigger instruction for the light switch debugging control, a light control interface is displayed, wherein the light control interface includes a light switch control control, and the light switch control control is used to control the on and off state of a preset light unit on the target wireless smart device.

3. The method according to claim 2, characterized in that The function debugging area further includes a light brightness debugging control, and the triggering of the function debugging of the target wireless smart device further includes: In response to a trigger instruction for the light brightness debugging control, the light control interface is displayed. The light control interface also includes a brightness control control and a brightness information area. The brightness control control is used to control the light brightness of the preset light unit, and the brightness information area is used to display corresponding brightness information according to the light brightness.

4. The method according to claim 1, wherein The function debugging area includes a network exit control control, and triggering the function debugging of the target wireless smart device includes: In response to the trigger instruction of the network exit control component, the device information of the target wireless smart device is deleted from the database, the connection with the target wireless smart device is disconnected, and the tool main interface is displayed.

5. The method according to claim 1, wherein The method further comprises: In the product test mode, in response to a trigger instruction of the test start control, the scan code to access the network prompt interface is displayed, and a connection with the target wireless smart device is waited for through the scan code to access the network prompt interface, the device information is obtained, and the device information is stored in the database; In response to obtaining the device information, a test main interface is displayed, wherein the test main interface includes a second device information area and a test progress area, wherein the second device information area is used to display the device information, and the test progress area is used to display the progress of the functional test of the target wireless smart device, wherein the functional test includes a light on / off function test, a light brightness adjustment function test, and a network logoff function test that are automatically performed in sequence.

6. The method according to claim 5, characterized in that The method further comprises: In response to all functions being tested in the product test mode being passed, deleting the device information of the target wireless smart device from the database, disconnecting from the target wireless smart device, and displaying a test pass prompt interface; In response to a failure in the test of any function in the product test mode, the process of the function test is stopped and a test failure prompt interface is displayed.

7. The method according to claim 5, characterized in that The debugging main interface and the testing main interface both include a reset control, and the method further includes: In response to the trigger instruction of the reset control, the Bluetooth adapter state of the target wireless smart device is reset.

8. The method according to claim 1, characterized in that The tool main interface also includes a log control, and the method further includes: In response to a trigger instruction for the log control, a log area is displayed on the tool main interface, and the log area is used to display function debugging information, function test information and / or error information.

9. A debugging tool interactive control device for a wireless intelligent device, characterized in that: The device comprises: A first processing module is configured to display a tool main interface, wherein the tool main interface includes a mode selection control, a debug start control, and a test start control, wherein the mode selection control is configured to select a function debug mode or a product test mode for the debug tool; a second processing module configured to, in the function debugging mode, display a code scanning network access prompt interface in response to a trigger instruction for the debugging startup control, wherein the code scanning network access prompt interface is configured to wait for an external code scanning device to scan an identification code of a target wireless smart device, establish a connection with the target wireless smart device according to the identification code, obtain corresponding device information, and store the device information in a database; The third processing module is used to display a debugging main interface in response to obtaining the device information, where the debugging main interface includes a first device information area and a function debugging area, where the first device information area is used to display the device information, and the function debugging area is used to trigger function debugging of the target wireless smart device.

10. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 8 when executing the computer program.

Images