System and method for managing plug-in of tested equipment in test of motor control equipment

Abstract

The invention belongs to the technical field of motor control equipment testing, and particularly relates to a system and a method for managing plug-ins of tested equipment in motor control equipment testing. The system for managing the plug-ins of the tested equipment in the test of the motor control equipment comprises a plug-in packaging module for managing plug-in information of the equipment, a plug-in configuration database, a plug-in software library, a plug-in file, a plug-in executable part, a plug-in parameter exchange file, a plug-in matching module, a plug-in installation module and a plug-in calling module, the plug-in data operation module and the plug-in authorization file can be switched to different tested devices for testing at any time without modifying codes or redeveloping special testing software, so that testing tasks with various different tested devices can be managed uniformly and efficiently, and the testing efficiency is improved. The response speed of equipment testing is improved, and the working efficiency of testing and research and development personnel is improved. And the capability of controlling the specified equipment is realized in a mode of independently installing the plug-in.

Description

Technical Field

[0001] The invention relates to the technical field of motor control equipment testing, and in particular to a plug-in management system and method for a tested device in a motor control equipment test. Background Art

[0002] With the widespread application of motors in various industries, the research and development of equipment for controlling motors, such as (inverters), has become more and more diversified, and the complexity of the equipment has become increasingly greater, resulting in an increasing demand for testing of motor control equipment (such as inverters). Therefore, how to speed up the testing of equipment, improve testing efficiency, and thus shorten its development cycle as much as possible has become a huge challenge for various companies.

[0003] In the professional field of motor control equipment testing, if you need to test a control device such as a frequency converter, based on the various parameters of the device and its own control logic, such as starting the frequency converter, setting the frequency, stopping the frequency converter, modifying the frequency converter parameters, etc., you usually need to write a set of special software. In the software, according to the different test conditions and working conditions, give the device corresponding test conditions, and then observe the functional performance and problems of the device under different working conditions.

[0004] However, with the increase in equipment research and development, different research and development plans, different equipment parameters, and different control logic. If different equipment needs to be tested, a set of dedicated testing software needs to be developed for each device. This leads to a long cycle, time-consuming and labor-intensive, low efficiency, and prone to errors. Summary of the invention

[0005] The object of the present invention is to provide a plug-in management system and method for a device under test in a motor control device test, so as to solve the problems raised in the above-mentioned background technology.

[0006] To achieve the above object, the present invention provides the following technical solution: a plug-in management system for a device under test in a motor control device test, comprising: The plug-in management system for the device under test communicates with the dedicated test management system during the motor control device test. The plug-in management system for the device under test during the motor control device test includes a plug-in packaging module for managing device plug-in information, a plug-in configuration database, a plug-in software library, a plug-in file, a plug-in executable part, a plug-in parameter exchange file, a plug-in matching module, a plug-in installation module, a plug-in calling module, a plug-in data calculation module, and a plug-in authorization file; The signal output end of the plug-in packaging module is connected to the plug-in configuration database and the plug-in file, the output end of the plug-in configuration database is connected to the plug-in software library, the output end of the plug-in software library is connected to the plug-in file, the input end of the plug-in configuration database is connected to the plug-in matching module, the output end of the plug-in file is connected to the plug-in executable part, the plug-in parameter exchange file, the plug-in data operation module, and the plug-in authorization file, the output end of the plug-in software library is connected to the plug-in installation module and the plug-in calling module, and the output end of the dedicated test management system is connected to the plug-in calling module and the plug-in data operation module.

[0007] Preferably, the plug-in packaging module is responsible for encrypting the dynamic library file and plug-in parameter exchange file compiled from the software code, the dynamic library file is the executable part of the plug-in, and the dynamic library file and the plug-in parameter exchange file are packaged together with the plug-in authorization file into a plug-in file for distribution and installation later.

[0008] Preferably, the plug-in configuration database is used to maintain configuration information of each device plug-in, and the configuration information includes at least plug-in name, plug-in description, unique serial number, device information, publisher information, version number, release date, authorized use time, device compatibility list, parameter function group, plug-in download address, and the device information also includes the serial number of the hardware device, the name of the hardware device manufacturer, and the rated operating voltage, current, and power information of the hardware device.

[0009] Preferably, the plug-in software library is used to store plug-in files and provide upload and download services for plug-in files in the form of local or remote FTP file services. The plug-in file is a file in a special format that includes a plug-in executable part and a plug-in parameter exchange file, with a plug-in authorization file attached, and the plug-in authorization file includes an authorization serial code, an activation date, and an expiration date.

[0010] Preferably, the executable part of the plug-in has an interface and function for software control of the device compatible with the plug-in, and is called by the dedicated test management system in the form of an application program interface.

[0011] Preferably, the plug-in parameter exchange file is used to set a series of parameters of the device compatible with this plug-in, such as the hardware address of the corresponding parameter and the parameter value that can be written to this hardware address and its format. The series of parameters can be classified and organized according to parameter function groups, and the parameter function groups are registered and maintained in the plug-in configuration database.

[0012] Preferably, the plug-in matching module uses the matching rules set by the user to query the plug-in configuration database. If a suitable plug-in is matched, the download address of this plug-in in the plug-in software library is queried and downloaded to a temporary directory. The download address is a local file directory or a remote file server address, depending on the deployment method of the plug-in software library.

[0013] Preferably, the plug-in installation module is used to decrypt the plug-in file in the temporary directory and extract the corresponding plug-in executable part, plug-in parameter exchange file and plug-in authorization file, and check the local operating environment to determine whether the authorization requirements are met.

[0014] Preferably, the plug-in calling module is used to perform function calls and parameter settings on the installed plug-in, and to provide call routing services for the dedicated test management system in the form of an application program interface. The plug-in data calculation module is used to calculate and process the test data after the dedicated test management system calls its interface after the test is completed to obtain the test results.

[0015] A method for managing a plug-in system of a device under test in a motor control device test, the method comprising the following specific steps: Step 0: There is a new device under test that needs to be tested; Step 1: Develop the executable part of the plug-in according to the requirements of the device under test and write the plug-in parameter exchange file; Step 2: After encrypting the plug-in executable part and the plug-in parameter exchange file, package them together with the authorization information to generate a plug-in file; Step 3: Maintain the plug-in configuration database, write the plug-in name, plug-in description, unique serial number, device information, publisher information, version number, release date, use authorization time, device compatibility list, parameter function group, plug-in download address, and upload the plug-in file to the plug-in software library; Step 4: The test operator sets the matching search rules for the device under test, and the plug-in matching module reads the rules and searches for plug-in information that meets the matching characteristics from the plug-in configuration database; Step 5: If the required plug-in information is found, jump to step 6, otherwise return to step 4; Step 6: Query the download path of the plug-in registered in the plug-in software library from the plug-in configuration database; Step 7: Download the plugin file to a temporary directory, decrypt and extract the plugin executable part and plugin parameter exchange file, as well as authorization information; Step 8: Check whether the authorization is correct. If it is correct, go to step 9, otherwise go to step 10; Step 9: Select this plug-in parameter to configure the device, select this plug-in interface to connect the device and control the device, and start the test; Step 10: The system prompts that authorization failed and jumps to step 12; Step 11: After the test is completed, call the data operation interface of this plug-in to analyze the test data and obtain the test result data; Step 12: The process ends.

[0016] Compared with the prior art, the present invention has the following beneficial effects: By registering and updating the plug-in library of the device under test, the control logic and device parameters of the device under test can be updated in time. Without modifying the code or re-developing dedicated test software, you can switch to different devices under test for testing at any time. In this way, for test tasks with multiple different devices under test, unified and efficient management can be carried out, which improves the response speed of equipment testing and the work efficiency of test and R&D personnel.

[0017] The ability to control a specific device is achieved by installing a plug-in independently. Device plug-ins must be authorized before they can be used. The device uses the dedicated algorithm of its matching plug-in to calculate the test results. The plug-in file can be automatically downloaded through a remote file service without manual operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a system logic block diagram of the present invention; Figure 2 The figure is a flow chart of the method of the present invention.

[0019] In the figure: 13. Plug-in packaging module; 14. Plug-in configuration database; 15. Plug-in software library; 16. Plug-in file; 17. Plug-in executable part; 18. Plug-in parameter exchange file; 19. Plug-in matching module; 20. Plug-in installation module; 21. Plug-in calling module; 22. Plug-in data operation module; 23. Plug-in authorization file; 24. Dedicated test management system. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0021] In the description of the present invention, it is necessary to understand that the terms "upper", "lower", "front", "back", "left", "right", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship are based on the orientation or position relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0022] Embodiment 1: See also Figure 1-2 The present invention provides a technical solution: a plug-in management system for a device under test in a motor control device test, comprising: The plug-in management system for the device under test in the motor control device test communicates with the dedicated test management system 24, and the plug-in management system for the device under test in the motor control device test includes a plug-in packaging module 13 for managing device plug-in information, a plug-in configuration database 14, a plug-in software library 15, a plug-in file 16, a plug-in executable part 17, a plug-in parameter exchange file 18, a plug-in matching module 19, a plug-in installation module 20, a plug-in calling module 21, a plug-in data calculation module 22 and a plug-in authorization file 23; The signal output end of the plug-in packaging module 13 is connected to the plug-in configuration database 14 and the plug-in file 16, the output end of the plug-in configuration database 14 is connected to the plug-in software library 15, the output end of the plug-in software library 15 is connected to the plug-in file 16, the input end of the plug-in configuration database 14 is connected to the plug-in matching module 19, the output end of the plug-in file 16 is connected to the plug-in executable part 17, the plug-in parameter exchange file 18, the plug-in data operation module 22, and the plug-in authorization file 23, the output end of the plug-in software library 15 is connected to the plug-in installation module 20 and the plug-in calling module 21, and the output end of the dedicated test management system 24 is connected to the plug-in calling module 21 and the plug-in data operation module 22.

[0023] The plug-in packaging module 13 is responsible for encrypting the dynamic library file and plug-in parameter exchange file 18 compiled from the software code. The dynamic library file is the plug-in executable part 17. The dynamic library file and the plug-in parameter exchange file 18 are packaged together with the plug-in authorization file 23 into a plug-in file 16 for distribution and installation later.

[0024] The plug-in configuration database 14 is used to maintain the configuration information of each device plug-in, which configuration information at least includes the plug-in name, plug-in description, unique serial number, device information, publisher information, version number, release date, authorized use time, device compatibility list, parameter function group, and plug-in download address. The device information also includes the serial number of the hardware device, the name of the hardware device manufacturer, and the rated operating voltage, current, and power information of the hardware device.

[0025] The plug-in software library 15 is used to store plug-in files 16 and provide upload and download services for plug-in files 16 in the form of local or remote FTP file services. The plug-in file 16 is a file in a special format that includes a plug-in executable part 17 and a plug-in parameter exchange file 18, which is accompanied by a plug-in authorization file 23. The plug-in authorization file 23 includes an authorization serial code, an activation date, and an expiration date.

[0026] The plug-in executable part 17 has an interface and function for software control of the device compatible with the plug-in, and is called by the dedicated test management system 24 in the form of an application program interface.

[0027] The plug-in parameter exchange file 18 is used to set a series of parameters for the device compatible with this plug-in, such as the hardware address of the corresponding parameter and the parameter value that can be written to this hardware address and its format. The series of parameters can be classified and organized according to parameter function groups, and the parameter function groups are registered and maintained in the plug-in configuration database 14.

[0028] The plug-in matching module 19 uses the matching rules set by the user to query the plug-in configuration database 14. If a suitable plug-in is matched, the download address of this plug-in in the plug-in software library is queried and downloaded to a temporary directory. The download address is a local file directory or a remote file server address, depending on the deployment method of the plug-in software library.

[0029] The plug-in installation module 20 is used to decrypt the plug-in file in the temporary directory and extract the corresponding plug-in executable part 17, plug-in parameter exchange file 18 and plug-in authorization file 23, and check the local operating environment to determine whether the authorization requirements are met.

[0030] The plug-in calling module 21 is used to call functions and set parameters of the installed plug-in, and provide call routing services for the dedicated test management system 24 in the form of an application program interface. The plug-in data calculation module 22 is used to calculate and process the test data after the dedicated test management system 24 calls its interface after the test is completed to obtain the test results.

[0031] A method for managing a plug-in system of a device under test in a motor control device test, the method comprising the following specific steps: Step 0: There is a new device under test that needs to be tested; Step 1: Develop the executable part of the plug-in according to the requirements of the device under test and write the plug-in parameter exchange file; Step 2: After encrypting the plug-in executable part and the plug-in parameter exchange file, package them together with the authorization information to generate a plug-in file; Step 3: Maintain the plug-in configuration database, write the plug-in name, plug-in description, unique serial number, device information, publisher information, version number, release date, use authorization time, device compatibility list, parameter function group, plug-in download address, and upload the plug-in file to the plug-in software library; Step 4: The test operator sets the matching search rules for the device under test, and the plug-in matching module reads the rules and searches for plug-in information that meets the matching characteristics from the plug-in configuration database; Step 5: If the required plug-in information is found, jump to step 6, otherwise return to step 4; Step 6: Query the download path of the plug-in registered in the plug-in software library from the plug-in configuration database; Step 7: Download the plugin file to a temporary directory, decrypt and extract the plugin executable part and plugin parameter exchange file, as well as authorization information; Step 8: Check whether the authorization is correct. If it is correct, go to step 9, otherwise go to step 10; Step 9: Select this plug-in parameter to configure the device, select this plug-in interface to connect the device and control the device, and start the test; Step 10: The system prompts that authorization failed and jumps to step 12; Step 11: After the test is completed, call the data operation interface of this plug-in to analyze the test data and obtain the test result data; Step 12: The process ends.

[0032] The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention. For those skilled in the art, it is obvious that the present invention is not limited to the details of the above exemplary embodiments, and the present invention can be implemented in other specific forms without departing from the spirit or basic features of the present invention; therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-restrictive. The scope of the present invention is limited by the attached claims rather than the above description. Therefore, it is intended to include all changes within the meaning and scope of the equivalent elements of the claims in the present invention, and any figure marks in the claims should not be regarded as limiting the claims involved.

[0033] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A plug-in management system for a device under test in a motor control device test, characterized in that: include: The plug-in management system for the device under test in the motor control device test communicates with the dedicated test management system (24), and the plug-in management system for the device under test in the motor control device test includes a plug-in packaging module (13) for managing device plug-in information, a plug-in configuration database (14), a plug-in software library (15), a plug-in file (16), a plug-in executable part (17), a plug-in parameter exchange file (18), a plug-in matching module (19), a plug-in installation module (20), a plug-in calling module (21), a plug-in data operation module (22) and a plug-in authorization file (23); The signal output end of the plug-in packaging module (13) is connected to the plug-in configuration database (14) and the plug-in file (16); the output end of the plug-in configuration database (14) is connected to the plug-in software library (15); the output end of the plug-in software library (15) is connected to the plug-in file (16); the input end of the plug-in configuration database (14) is connected to the plug-in matching module (19); the output end of the plug-in file (16) is connected to the plug-in executable part (17), the plug-in parameter exchange file (18), the plug-in data operation module (22), and the plug-in authorization file (23); the output end of the plug-in software library (15) is connected to the plug-in installation module (20) and the plug-in calling module (21); and the output end of the dedicated test management system (24) is connected to the plug-in calling module (21) and the plug-in data operation module (22).

2. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in packaging module (13) is responsible for encrypting the dynamic library file and the plug-in parameter exchange file (18) compiled from the software code, the dynamic library file being the plug-in executable part (17), and the dynamic library file and the plug-in parameter exchange file (18) are packaged together with the plug-in authorization file (23) into a plug-in file (16) for distribution and installation at a later stage.

3. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in configuration database (14) is used to maintain the configuration information of each device plug-in, and the configuration information at least includes the plug-in name, plug-in description, unique serial number, device information, publisher information, version number, release date, use authorization time, device compatibility list, parameter function group, plug-in download address, and the device information also includes the serial number of the hardware device, the name of the hardware device manufacturer, and the rated working voltage, current, and power information of the hardware device.

4. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in software library (15) is used to store the plug-in file (16) and provide upload service and download service of the plug-in file (16) in the form of local or remote FTP file service. The plug-in file (16) is a file in a special format including a plug-in executable part (17) and a plug-in parameter exchange file (18), and is accompanied by a plug-in authorization file (23). The plug-in authorization file (23) includes an authorization serial code, an activation date, and an expiration date.

5. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in executable part (17) has an interface and function for performing software control on the device compatible with the plug-in, and is called by the dedicated test management system (24) in the form of an application program interface.

6. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in parameter exchange file (18) is used to set a series of parameters of the device compatible with the plug-in, such as the hardware address of the corresponding parameter and the parameter value that can be written to the hardware address and its format. The series of parameters can be classified and organized according to parameter function groups, and the parameter function groups are registered and maintained in the plug-in configuration database (14).

7. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in matching module (19) uses the matching rules set by the user to query the plug-in configuration database (14). If a suitable plug-in is matched, the download address of the plug-in in the plug-in software library is queried and downloaded to a temporary directory. The download address is a local file directory or a remote file server address, depending on the deployment method of the plug-in software library.

8. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in installation module (20) is used to decrypt the plug-in file in the temporary directory and extract the corresponding plug-in executable part (17), the plug-in parameter exchange file (18) and the plug-in authorization file (23), and check the local operating environment to determine whether the authorization requirements are met.

9. The plug-in management system for a device under test in a motor control device test according to claim 1, characterized in that: The plug-in calling module (21) is used to call functions and set parameters of the installed plug-in, and provide a calling routing service for the dedicated test management system (24) in the form of an application program interface. The plug-in data operation module (22) is used to perform operation processing on the test data after the dedicated test management system (24) calls its interface after the test is completed to obtain the test result.

10. A method for managing a plug-in system of a device under test in a motor control device test according to any one of claims 1 to 9, characterized in that: The specific steps of this method are as follows: Step 0: There is a new device under test that needs to be tested; Step 1: Develop the executable part of the plug-in according to the requirements of the device under test and write the plug-in parameter exchange file; Step 2: After encrypting the plug-in executable part and the plug-in parameter exchange file, package them together with the authorization information to generate a plug-in file; Step 3: Maintain the plug-in configuration database, write the plug-in name, plug-in description, unique serial number, device information, publisher information, version number, release date, use authorization time, device compatibility list, parameter function group, plug-in download address, and upload the plug-in file to the plug-in software library; Step 4: The test operator sets the matching search rules for the device under test, and the plug-in matching module reads the rules and searches for plug-in information that meets the matching characteristics from the plug-in configuration database; Step 5: If the required plug-in information is found, jump to step 6, otherwise return to step 4; Step 6: Query the download path of the plug-in registered in the plug-in software library from the plug-in configuration database; Step 7: Download the plugin file to a temporary directory, decrypt and extract the plugin executable part and plugin parameter exchange file, as well as authorization information; Step 8: Check whether the authorization is correct. If it is correct, go to step 9, otherwise go to step 10; Step 9: Select this plug-in parameter to configure the device, select this plug-in interface to connect the device and control the device, and start the test; Step 10: The system prompts that authorization failed and jumps to step 12; Step 11: After the test is completed, call the data operation interface of this plug-in to analyze the test data and obtain the test result data; Step 12: The process ends.

Images