Flexible test system and method for inertial combination measurement device

Abstract

The invention discloses a flexible test system and a flexible test method for an inertial combination measurement device, which are characterized in that an inertial measurement unit product and test equipment are integrally controlled, and the system can simultaneously control the test equipment to work cooperatively while acquiring inertial measurement unit data at a high speed, so that an inertial measurement unit can adapt to different test equipment to perform automatic test; the system adopts an architecture in which a test process, a test logic and an acquisition control protocol are separated, a bottom layer code does not need to be greatly modified when a bottom layer communication protocol is changed, a new test process and a new test case are quickly generated through visual configuration, and dynamic editing of complex test logic is supported; according to the system, a data and event bus is used for bearing loosely coupled data and event interaction, it is guaranteed that no data coincidence exists between all assemblies in the test process execution process, and the test process is controllable. The system framework is loosely coupled, the updating iteration period is shortened, the iteration difficulty is reduced, the automation degree is improved, the test compatibility is good, and the expansibility is good.

Description

Technical Field

[0001] The invention relates to a flexible testing system and method for an inertial combined measurement device, belonging to the technical field of automatic testing systems. Background Art

[0002] Inertial combination measurement unit (abbreviated as: IMU, also known as: IMU product) is a key product for precision navigation. IMU products have the characteristics of "small batch and multiple varieties" testing tasks. At present, IMU testing and equipment control are mainly operated manually, with problems such as low production efficiency, low degree of automation, and dedicated test system, which cannot meet the requirements of precision equipment testing. Therefore, the intelligent and universal IMU testing is imperative.

[0003] The traditional inertial group test system is mainly aimed at inertial group product types and test projects. According to the type customization requirements, the communication protocol instructions, test logic, and test process are built into the test system. The programming code is in programming languages ​​such as VB, and the test requirements are realized at the logic code level. It is special and dedicated. When there is a need to adjust the test project or a new product model needs to be tested, software technicians need to change and debug from the bottom of the code. The cycle is long and the test system is not flexible. It cannot adapt to the rapid iteration of products and the speed of production, and the time and labor costs are greatly increased. At the same time, with the multiple changes in product communication protocols, equipment models, and test tasks, the test system built by the traditional inertial group test method has problems such as high coupling of the underlying software framework, long and difficult update and iteration cycles, low degree of automation, poor test compatibility, and poor scalability. Therefore, it is urgent to provide a new technical solution to effectively solve the above problems. Summary of the invention

[0004] The present invention aims to provide a flexible testing system for an inertial combination measurement device. When the underlying communication protocol of the inertial combination measurement device test changes, the system can generate a new test process through visual configuration, integrate test equipment and its common control method, so that the inertial combination measurement device can be adapted to different test equipment for automated testing. The system framework is loosely coupled, shortens the update iteration cycle, reduces the iteration difficulty, improves the degree of automation, and has good test compatibility.

[0005] In order to achieve the above-mentioned purpose, the technical scheme adopted by the present invention is: a flexible testing system for an inertial combination measurement device, the system includes a test platform and an inertial combination measurement device, the test platform includes a host computer, a gateway, an inertial combination universal acquisition box, a test device and a back-end server, the host computer is installed with a process automation component, the process automation component generates a test process through visual configuration, and the test process is scheduled by the inertial combination test engine to complete the automated test of the inertial combination measurement device; the host computer is respectively connected to the gateway and the inertial combination universal acquisition box; the gateway is connected to the test device to control the command reception and transmission and data feedback of the test device; the inertial combination universal acquisition box is connected to the inertial combination measurement device to control the command reception and transmission and data collection of the inertial combination measurement device; the back-end server is connected to the host computer to store the database of the test platform.

[0006] The flexible testing system provided by the present invention can control the testing equipment to work together to meet the needs of inertial group testing while collecting inertial group data at high speed; the system generates a test process through visual configuration to address the problems of diverse product models and different underlying communication protocols involved in inertial group product testing, and is not restricted by the underlying communication protocol.

[0007] According to the embodiments of the present invention, the present invention can be further optimized. The following is the technical solution formed after optimization:

[0008] In one of the preferred embodiments, the process automation component also includes basic configuration, underlying communication protocol and driver, acquisition control logic, data and event bus;

[0009] The basic configuration adds, deletes and modifies the header of the data acquisition interface according to the data categories to be displayed in the test, sets the controls of the data acquisition interface, binds the data source, and creates a mapping relationship between the data source and the data bus variables; wherein the data source is the basic data of the test equipment and the inertial combination measurement device, and the data bus variables are stored in the data and event bus module for scheduling data interaction during the execution of the test process; the data acquisition interface is the configuration interface of the basic configuration implemented by the visualization configuration, and the controls include buttons, drop-down boxes, input boxes, radio buttons, check boxes and tables;

[0010] The underlying communication protocol and the driver configure the instructions through the visual configuration, generate instructions that meet the requirements of the underlying communication protocol, and create a mapping relationship between the parameters of the instructions and the data bus variables; the instructions include a sending frame and a return frame, the sending frame is the instruction frame sent by the host computer, and the return frame is the response instruction frame returned by the inertial combination measurement device;

[0011] The acquisition control logic includes simple logic and complex logic, which are used to control the sending frame and receive the return frame; the acquisition control logic is configured through the visual configuration, generates function blocks and / or actions, creates a mapping relationship between the parameters of the function blocks and / or actions and the data bus variables, and creates an event strategy corresponding to the function blocks and / or actions; wherein the event strategy is stored in the data and event bus module, and is used to schedule the strategy triggering during the execution of the test process, the function block is formed after the instruction is processed by the simple logic, and the action is formed after the instruction is processed by the complex logic;

[0012] The test process includes a common process and a monitoring process, which is configured and generated through the visual configuration, and a mapping relationship between the parameters of the test process and the data bus variables is created, and an event strategy corresponding to the test process is created. The configuration nodes of the common process include actions and function blocks, and the monitoring process is used to monitor the data of the inertial combination measurement device under test and the status of the test equipment in real time.

[0013] By adopting an architecture that separates the test process, test logic and acquisition control protocol, the flexible testing system provided by the present invention is not limited by the model of the inertial group product and the underlying communication protocol. It can quickly generate new test processes and test cases through visual configuration, support dynamic editing of complex test logic, and realize visual arrangement of test logic and test process. The data and event bus includes the inertial group's general data structure, which is used to carry loosely coupled data and event interactions, avoiding the complexity of the data structure caused by the deep coupling of the acquisition control layer and the process control layer, and at the same time ensuring that there is no data overlap between the components during the execution of the test process, and the test process is controllable.

[0014] In one of the preferred embodiments, the configuration node of the test process also includes a custom node, and the custom node is used to call a newly written underlying program.

[0015] During the test configuration process, when new or more complex test logic appears in the test requirements, it cannot match the standardized configuration of the packaged components, and the newly written underlying code can be called through the custom node. The flexible test system provided by the present invention can provide new underlying code to be written and then packaged and included in the flexible test system for selection, so as to expand the configuration selection library, so that the scalability of the system is good.

[0016] In one of the preferred embodiments, the test process also includes a sub-process, a troubleshooting process, and an exception handling process; the sub-process is a test process for repetitive operations in the test, the troubleshooting process is a test process for verifying and / or troubleshooting, and the exception handling process is a test process executed when an exception error is reported in the test.

[0017] During the test configuration process, there are repetitive test steps in the test task that need to be performed. In order to simplify the test process configuration, it can be configured as a sub-process; based on the data and event bus, standardized data monitoring and abnormal event processing of the inertial group and test equipment are realized during the test process, thereby improving the safety and reliability of the inertial group test.

[0018] In one of the preferred embodiments, the test process also includes a debugging process, which is used for debugging mode testing to monitor changes in test data, and the test data includes parameters of the instructions, parameters of the function blocks and / or the actions, parameters of the test process, and basic data of the test equipment and the inertial combination measurement device.

[0019] The parameters of the instruction, the parameters of the function block and / or the action, the parameters of the test process, and the basic data of the test equipment and the inertial combination measurement device can be obtained according to the technical specification or the test process specification; through the debugging mode test, problems arising during the test process can be checked.

[0020] In one preferred embodiment, the test process further includes a binding process, and the binding process is used for manual mode testing to reduce the reciprocating operation in the manual mode testing. When the test requires manual intervention, it can be completed through the manual test mode.

[0021] Based on the same concept, the present invention also provides a flexible testing method for an inertial combination measurement device, the method is based on the above-mentioned flexible testing system for an inertial combination measurement device, and comprises:

[0022] Step 1, log in to the process automation test software, and select the model of the inertial combination measurement device and the test equipment to be tested in the drop-down list; the process automation test software can automatically record the content selected last time, if there is no change, go to step 2, if you need to create a new test process, go to step 3;

[0023] Step 2: In the automated test interface, select the test process. The automated test software can automatically record the last selected content. If there is no change, go to step 4.

[0024] Step 3: If a new test process needs to be created, the basic configuration, underlying communication protocol and driver, and acquisition control logic configuration related to the test process are completed through the visual configuration according to the test requirements, and then step 4 is entered;

[0025] Step 4: Click the Start Test button on the interface. The process automation test software automatically loads the instructions, function blocks and / or actions, and test processes configured through the visual configuration according to the selected information, calls the selected test process, and enters the test execution phase.

[0026] Step 5, scheduling the test process through the inertial combination test engine to execute the actions in the test process from top to bottom according to the event strategy of the test process, executing the complex logic in the action and / or the simple logic in the function block after the action is triggered, generating the sending frame and sending it to the inertial combination measurement device, the inertial combination measurement device returns the return frame, the acquisition control logic module controls the issuance of the next sending frame by processing the data in the return frame or according to the data in the return frame, and the test data fed back by the inertial combination measurement device is displayed on the data acquisition interface from bottom to top;

[0027] Step 6: During the test, the monitoring process is nested in the common process and executed in parallel to monitor the data of the inertial combination measurement device and the status of the test equipment, including but not limited to voltage, current, output pulse, temperature, and angle.

[0028] In one of the preferred embodiments, before executing step 4, the method further includes: setting a file path, where the file path is a path for storing test data and test logs; and / or, editing parameters of the test process according to test requirements.

[0029] In one of the preferred embodiments, the test process also includes an exception handling process, and the exception handling process is a test process executed when an exception error is reported during the test. The method also includes: Step 7, during the test process, when an exception occurs, calling the configured exception handling process.

[0030] In one of the preferred embodiments, the method further includes: Step 8, during the test process, all operations and key states are recorded by the test log.

[0031] Compared with the prior art, the beneficial effects of the present invention are as follows: the flexible test system for inertial combination measurement device provided by the present invention can control the test equipment to work together to meet the needs of inertial combination measurement device testing while collecting inertial combination data at high speed by integrating and controlling inertial combination products and test equipment; by adopting an architecture in which the test process, test logic and acquisition control protocol are separated, the system is not limited by the model of the inertial combination product and the underlying communication protocol, and can quickly generate new test processes and test cases through visual configuration, support dynamic editing of complex test logic, and realize visual arrangement of test logic and test process; the data and event bus is used to carry loosely coupled data and event interactions, avoid the complex data structure caused by the deep coupling of the acquisition control layer and the process control layer, and ensure that there is no data overlap between the components during the execution of the test process, and the test process is controllable. The system does not need to significantly modify the underlying code when the underlying communication protocol of the inertial combination test changes, generates a new test process through visual configuration, integrates the test equipment and its common control method, so that the inertial combination can adapt to different test equipment for automated testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 It is a schematic diagram of a flexible testing system for an inertial combination measurement device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0033] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that the embodiments and features in the embodiments of the present invention can be combined with each other without conflict.

[0034] Example 1

[0035] This embodiment provides a flexible test system for an inertial combination measurement device, such as Figure 1 As shown, the system includes a process automation test platform and an inertial combination measurement device. The process automation test platform includes a host computer, a device acquisition control gateway, an inertial combination universal acquisition box, a test device and a back-end server. The host computer is installed with a process automation component. The process automation component generates a test process through visual configuration, and the test process is scheduled by the inertial combination test engine to complete the automated test of the inertial combination measurement device. The host computer is connected to the device acquisition control gateway and the inertial combination universal acquisition box respectively. The device acquisition control gateway is connected to the test device to control the command transmission and reception and data feedback of the test device. The inertial combination universal acquisition box is connected to the inertial combination measurement device to control the command transmission and reception and data collection of the inertial combination measurement device. The back-end server is connected to the host computer to store the database of the test platform. As shown Figure 1As shown, the host computer is connected to the device acquisition control gateway and the inertial group universal acquisition box through a LAN interface. There are many types of communication protocols for different models of inertial group products and test equipment, including 1553B, synchronous\asynchronous RS422, synchronous\asynchronous RS485, RS232, TCP / IP, etc.

[0036] The process automation components also include basic configuration, underlying communication protocol and driver, acquisition control logic, data and event bus. The implementation of each component is based on the interface configuration of the visual configuration, and is implemented in a graphical way of dragging and dropping:

[0037] Basic configuration: According to the data categories displayed on the upper computer interface as required by product testing, use the basic configuration to add, delete and modify the table headers of the interface UI, and customize the buttons and drop-down box options of the data collection and display interface (bind data source);

[0038] Bottom-layer communication protocol and driver: Classify according to protocol type, classify protocol instructions into periodic instructions and non-periodic instructions according to protocol requirements, split instructions into send frames and return frames, and configure the send frames and return frames of instructions through a visual interface. The configuration content includes frame header, command code, data content, frame tail, checksum, and form a complete instruction that meets the protocol requirements;

[0039] Acquisition control logic: Acquisition control logic needs to be implemented based on the underlying communication protocol and driver call instructions. It controls the host computer to send instruction frames (send frames), receives instruction frames returned by the product (return frames), directly processes the data in the return frames or sends the next control instruction based on the data. Acquisition control logic is divided into simple logic and complex logic:

[0040] 1) Simple logic includes but is not limited to directly accumulating the values ​​of the data content in the return frame (the sum of 100 return frames is one frame), performing addition, subtraction, multiplication and division operations on the individual data content in a single return frame, etc. After the simple logic processing is completed, a function block is formed;

[0041] 2) For complex logic, it is necessary to further organize the logic of the functional blocks formed by simple logic, including but not limited to judging the data eligibility of the data frames output by the functional blocks (whether the data meets the product technical index requirements after accumulation or addition, subtraction, multiplication and division operations), combining the data frames output by multiple functional blocks in time sequence (parallel, serial), etc. After the complex logic is processed, an action is formed.

[0042] Note: Function blocks do not need to participate in the action composition and can be directly selected as configuration nodes of the test process.

[0043] Test process: According to the product test task requirements and test steps, the process can be divided into ordinary process, sub-process and monitoring process. Sub-process refers to some repetitive test steps that need to be operated in multiple test tasks. In order to simplify the process configuration work, it can be configured as a sub-process; the ordinary process determines whether it contains sub-processes depending on the difficulty of operating the test steps; the monitoring process is used for test monitoring and is an indispensable test process. The ordinary process is to select actions, function blocks and sub-processes, and configure the strategy when the process is running, including but not limited to test time, single-step process judgment, single-step process jump, test conditions, loop testing, etc. to form an automatic or manual test process. The monitoring process is configured according to the product data and test equipment (for example: power supply, turntable, incubator) status that the product needs to monitor in real time, and needs to be nested in the ordinary process and run in parallel.

[0044] Inertial group test engine: After completing the test process through the configuration method, the inertial group test engine schedules the process from top to bottom to execute the actions in the process according to the operation strategy in the process. After the action is triggered, the complex logic in the action or the simple logic in the function block is executed. Finally, the instruction frame is sent to the inertial group product through the instruction. After the inertial group product returns the data, it is displayed from bottom to top on the data acquisition interface.

[0045] Data and event bus: Data interaction and event strategy triggering during the test process are stored and read through the data and event bus, ensuring that there is no data overlap between components and the test process is controllable.

[0046] Example 2

[0047] This embodiment 2 provides a flexible testing method for an inertial combination measurement device, including:

[0048] Protocol configuration of the test equipment: classify the equipment protocol according to periodic / non-periodic classification, use the visual configuration interface to configure the instructions, and form callable actions; the test equipment includes but is not limited to a turntable, an incubator, a programmable power supply, a collimated light tube, a constant current source, and a three-color lamp; the three-color lamp is a warning lamp, and its status is marked with different colors in the test process.

[0049] Protocol configuration of inertial group products: use instruction configuration, function block configuration, and action configuration to assemble the periodic and non-periodic instructions in the product communication protocol according to the acquisition control logic to form callable actions.

[0050] Configuration of test process: According to the requirements of product test items and process documents, in the test process configuration interface, actions, event strategies, test process execution forms (such as branches, loops), monitoring, etc. are used to call product and equipment actions to complete the configuration of the test process and form a test process that can be carried out.

[0051] Testing of custom group products: Process personnel select different test items and choose the project data storage path (first level, the project data storage path also has a second level, which is automatically created after the test process is executed). The test process will have an indicator to remind you to enter the test starting conditions, that is, the parameters that need to be edited before running. Click Confirm to confirm the process, path, and conditions twice, and click "Start Test" to start the product one-click automatic test;

[0052] Process monitoring: During the test, the current test action will be highlighted to remind the progress; the configured monitoring-related event strategy is used to monitor the product and equipment status test; the three-color light displays different colors according to different test states, and normal operation, standby, and alarm correspond to green, yellow, and red respectively; the monitoring data includes but is not limited to the product's voltage, current, output pulse, temperature, etc., the equipment's operating status, output data (angle, temperature, voltage and current, etc.), etc.;

[0053] Result preservation: After the test is completed, the data is automatically stored according to the directory hierarchy, and the test log (including process log and equipment status log) is also stored for review after the test.

[0054] Example 3

[0055] This embodiment 3 provides a flexible testing method for an inertial combination measurement device, which uses a process automation testing platform and a host computer to configure the test process of the inertial combination measurement device (inertial group product) using a flexible testing method to achieve the integrated functions of product testing, equipment control and status warning. The host computer installs a process automation host computer component, and the process automation host computer component is implemented based on C++ and python mixed programming.

[0056] Create the basic information of the inertial group product in the visual interface of the host computer, including product name, communication protocol type, interface, etc., and configure the process required for product testing according to the product testing task requirements and technical indicators.

[0057] According to the page requirements presented in the visual interface, enter the product model, protocol type, IP address, port, serial port, baud rate and other options, and click the "Save" button to successfully add the product information.

[0058] S1. Basic configuration module (collection interface configuration):

[0059] Create a new default collection interface, edit the interface header according to the product data collection requirements, add a new header, enter the header name, and select the data source, and the header list will display the newly added header name. The header name can be modified and deleted. After adding the header, create and edit it through the "Property Initialization Header" interface to take effect. The data source is the basic data of the test equipment and inertial group products. Select the data source to associate the basic data of the test equipment and inertial group products with the test process. The basic data is configured according to the process documents or technical indicators;

[0060] Create, edit, and modify the manual test operation buttons and options on the default interface. You can set buttons, drop-down boxes, input boxes, radio buttons, check boxes, tables, and other contents, establish a mapping relationship with the data bus, and map the state or specific value of the input / output parameters to the data bus variables. The various states set during the test will be assigned to the corresponding data bus variables. Complete the acquisition interface configuration.

[0061] S2. Bottom layer communication protocol and driver module (command configuration):

[0062] According to the communication protocol, the technician configures the sending instruction frame (sending frame) and the response instruction frame (returning frame), and can query, copy, delete, modify, etc. Click the menu "Instruction Setting" to open the "Instruction Setting" interface.

[0063] S2.1 New instructions

[0064] The steps of adding new instructions include: adding basic information of instructions, editing advanced properties, adding frames, data modeling and mapping, and saving. The data modeling is a unified modeling defined by data for the parameters in the product communication protocol, which can be globally called in the process automation host computer component; the mapping is a one-to-one connection relationship between parameters and variables in the data bus;

[0065] Add basic information of the instruction: Enter the instruction name, abbreviation, and description according to the requirements of the page, select the framing method: byte stream / string, and select the device: product / temperature box / turntable / programmable power supply / light tube.

[0066] Edit advanced properties: On the command details page, click the page link "Edit advanced properties" to pop up the advanced edit box and select the communication type. The communication types include RS422 / 232, 1553B, etc.

[0067] S2.2 Add command frame

[0068] According to the content of the communication protocol, add a sending frame or a returning frame. In this embodiment 3, add a sending frame as an example. There are two ways to add frames: single adding and multiple adding, and the corresponding visualization configuration operations are "add frame" and "table editing".

[0069] Add frame: Click "Add frame" in the command area to pop up the Add frame dialog box. Enter the frame name as required by the page, select the frame type, data type, frame length, and default value / formula according to the test requirements, and return to the command page. The corresponding command area will display the added frame data.

[0070] Table Edit: In the command area, click "Table Edit" to pop up the table edit box, where you can perform the following operations:

[0071] Add a new frame: In the table editing box, click "Add a new frame" in the lower left corner, and a piece of data will be added to the list area. Fill in the frame name, frame type, data type, default value / formula, input value type, etc. in the table;

[0072] Copy: Click the "Copy" icon in the operation column to copy a piece of identical frame data to be displayed at the bottom of the list.

[0073] Delete: Click the "Delete" icon in the operation column to delete unnecessary frame data.

[0074] Define as template: Define as template operation will pop up the template pop-up window, enter the template name, and then you can set the instruction as a template.

[0075] Save: In the table editing interface, after adding the instruction frame, return to the instruction details page, and the corresponding instruction area will display the added frame data. After the instruction frame is saved successfully, the instruction is added successfully. If you need to adjust the order of the frames, just select the frame and drag it to the specified position.

[0076] S2.3 Send frame / response frame mapping

[0077] That is, map the instruction parameters with the variables in the data bus. In this embodiment 3, take adding a send frame mapping as an example. After adding the frame data, in the instruction area, click "Send frame mapping", and on the mapping page, click "Add a new mapping", and a mapping data will be inserted into the page list. You can select the parameters in the instruction to map with the variables in the data modeling. (Note: Only instructions with a frame type of "input value" can add mapping) For example: the input value 'sequence code' in the instruction is associated with the 'count sequence variable' created in the data modeling. For instructions that do not require mapping, this step can be ignored. When all the instruction information is edited, save it to successfully add the instruction information.

[0078] S3. Acquisition control logic (function block and action configuration)

[0079] S3.1 Function Block Configuration

[0080] The process personnel configure the function block according to the business requirements and test process. The nodes of the function block include general nodes, function blocks, instructions, and custom nodes. General nodes are encapsulated function block nodes that can be directly called. In this embodiment 3, general nodes include data judgment, stopwatch start, stopwatch judgment, stopwatch reset, countdown start, countdown reset, countdown stop, set file path / file directory path, loop, combination, subscription, conditional branch, parallel branch, and execution node. The instruction is the instruction configured in S2. Click the menu "Function Block Settings" to open the "Function Block Settings" interface.

[0081] S3.1.1 Add a new function block: On the function block setting page, click the "Add a new function block" button to pop up the function block basic information editing box. According to the page requirements, enter the function block name, abbreviation, and description, select equipment: product / incubator / turntable / power supply / light tube, and enter the detailed information page of the new function block.

[0082] S3.1.2 Add function block node: Add a node on the function block details page. The function block details page displays all configured common nodes, function blocks, instructions, and custom nodes. Select the required function block node and click the name to add it. The center interface of the function block details page displays the content of the added function block node. Operations on function block nodes include replacement, deletion, copying, and moving node order. Select a function block node, and the configuration interface on the right displays the configuration information of the node, including data / event information.

[0083] S3.1.3 Setting function block node data information (data modeling mapping)

[0084] Select the function block node and click "Data Modeling Mapping" in the data interface to pop up the data modeling mapping box. On the mapping page, add a new mapping and select the input / output parameters of the function block node to map with the variables in the data modeling. After adding, the mapping is completed. For function block nodes that do not need to be mapped, you can ignore this step.

[0085] S3.1.4 Set function block node event information (event strategy)

[0086] To add an event, you can refer to the "Event Strategy Explanation", which is the instruction manual for the event strategy selected during the configuration process, including the type of event strategy selected, how to use it, etc. The configuration steps of the event strategy include: selecting the function block node, switching to the event interface, and popping up the event strategy edit box. First, select the event type, including start execution and end execution; second, select the specific information of the event execution, including execution time; finally, select the execution conditions, including direct execution, meet conditions, meet at the same time, and meet any conditions. Select the corresponding event strategy according to the actual test product task requirements.

[0087] S3.1.5 Input / output parameter mapping

[0088] After adding the function block node, add input / output parameter mapping. In this embodiment 3, taking input parameter mapping as an example, click "Mapping" at 'Input Parameter Mapping' and a new parameter box will pop up. Click the "Add Input Parameter" button and a function block node selection box with input parameters will pop up. The selection box interface displays all nodes with parameters for the current function block. Select the function block node that needs to set the parameters. The parameter name is displayed on the right. Check the parameter to successfully add a parameter. If the parameter needs to be edited before running, check the checkbox, otherwise uncheck it. After the settings are completed, return to the function block detailed interface, and the corresponding input / output parameter mapping area will display the mapped parameter information.

[0089] S3.2 Action Configuration

[0090] Click the menu "Action Settings" to open the "Action Settings" interface. Click "Add Action" to pop up the action basic information editing box. According to the page requirements, enter the action name, abbreviation, and description, and select the equipment: product / incubator / turntable / power supply / light tube. There is no need to select equipment for general instructions. Click the "OK" button to enter the detailed information page of the new action. First click the "Save" button to save the basic information of the new action. Continue to configure the action node, and its configuration method is the same as that of the function block node.

[0091] S3.2.1 Adding action nodes

[0092] On the action details page, click the "+" button in the center interface to pop up the action node selection box. This selection page displays all configured general nodes, function blocks, instructions, and custom nodes. Select the required action node and click the name to add it. The action details center interface displays the added action node content. The operations of the action node include: edit, copy, delete, and move the node sequence. Select the action node, and the configuration interface on the right displays the configuration information of the action node, including data / event information.

[0093] S3.2.2 Set action node data information (data modeling mapping)

[0094] If the selected action node has entry / exit parameters, the specific parameters will be displayed in the 'Data' area of ​​the configuration interface on the right. When you place the mouse on the parameter name, a floating window will pop up to display the specific information of the parameter.

[0095] Data modeling mapping: In the "Data" area, click "Data modeling mapping" next to the input parameter / output parameter to pop up the data modeling mapping box. On the mapping page, click "Add a mapping" and a mapping data will be inserted into the page list. You can select the input / output parameters of the action node to map with the variables in the data modeling. After adding, click the "Save" button to complete the mapping. (Note: For actions that do not require mapping, you can ignore this step.)

[0096] S3.2.3 Set action node event information (event strategy)

[0097] To add an event, you can refer to the "Event Strategy Explanation", which is the instruction manual for the event strategy selected during the configuration process, including the type of event strategy selected, how to use it, etc. The configuration steps of the event strategy include: select the action node, click "Event" in the configuration information on the right interface, switch to the event interface, click the "Add Event" button, and the event strategy editing box pops up. First, select the event type, including start execution and end execution; then select the specific information of the event execution, including the execution duration; finally, select the execution conditions, including: direct execution, meet conditions, meet at the same time, and meet any conditions. Select the corresponding event strategy according to actual business needs. After configuration, click the "Save" button in the upper right corner of the interface, and it will prompt that the save is successful. Click 'Back' to return to the action setting page, where you can view the newly added action information.

[0098] S3.2.4 Other operations

[0099] Actions can be queried, edited, copied, deleted, and other functional operations.

[0100] S3.2.5 Custom node settings

[0101] Process personnel set custom nodes according to business needs, and setting custom nodes requires writing code.

[0102] Click the menu "Custom Node Settings" to open the "Custom Node Settings" interface, click "Add Custom Function", and the custom node editing box will pop up. According to the requirements of the page, enter the name, abbreviation, description, and select the equipment: product / incubator / turntable / power supply / light tube. Enter the function-related information, including: file type, file path, function name, function description, add function parameters, etc. The function-related information is filled in according to the written function code. After filling in the content, click the "Save" button in the upper right corner of the page to successfully add a custom node. In actual applications, when more complex test logic appears and cannot match the configuration standardization of the packaged modules, the newly written underlying code can be called through the custom node. The method can provide writing and then packaging to be included in the method for selection, expanding the configuration selection library.

[0103] S4. Test process configuration

[0104] Process personnel configure test processes according to business needs. Test process types include general processes, troubleshooting processes, monitoring processes, sub-processes, binding processes, exception handling, and debugging processes. Test process nodes include general nodes, actions, sub-processes, and custom nodes.

[0105] Click the "Process Settings" menu to open the "Process Settings" interface. This interface displays all configured process information in two display formats: cards and lists. Click the icon in the upper right corner of the page to switch.

[0106] S4.1 Introduction to process types

[0107] The general process is the business process in the test. The troubleshooting process is used to verify and eliminate the process of a specific fault. The monitoring process is used to monitor the changes in the values ​​of parameters (this parameter includes instruction parameters, entry / exit parameters of function blocks / actions, test process parameters, and data bus variables) during automated testing, such as current and voltage value monitoring. That is, in the general process, add a power monitoring process. When executing this process, the current or voltage value set in the monitoring process will be monitored in real time; the monitoring process is an indispensable test process. The sub-process is a part of the process that can be shared in the business process. Binding process: Some buttons can be bound to a process separately. After the binding is completed, click the button to directly execute the process. When setting the binding process, only the process of type "binding process" can be selected. The buttons include buttons, drop-down boxes, input boxes, radio buttons, check boxes, and tables in the basic configuration interface. The use scenario of the binding process is mainly for manual mode testing in the acquisition interface. The binding process can reduce some reciprocating operations in the manual mode test, such as "click to start-click to stop-click to save data-click to clear data" and similar reciprocating operations. The exception handling process is used to continue to execute according to the set exception handling process when an exception error occurs during the test. That is, add an exception handling process to the normal process. If an exception occurs when executing the normal process, continue to execute according to the added exception handling process. The debugging process is the process required when the automated test runs in debugging mode. Selecting a specified "debugging process" can create a "data modeling snapshot" as required to facilitate monitoring of data changes. The data includes multiple data such as the parameters of the visual configuration, the gyro meter data pulse of the inertial group product, the product temperature, the gyro light intensity change, the meter temperature, etc.

[0108] S4.2 Create a new process

[0109] In the "Process Settings" interface, click "Add Process" and an edit box for basic process information will pop up. According to the page requirements, enter the process name, abbreviation, and description, select the process type, select the product, select the incubator, select the turntable, select the power supply, select the light tube, and select the alarm light. You do not need to select a product for a general process. The general process is a standardized process that is highly reusable during product testing and is not restricted by product type. Click the "OK" button to enter the detailed information page of the newly added process. First click the "Save" button in the upper right corner to save the basic information of the newly added process and continue to configure the process node. The configuration method of the process node is the same as that of the function block node. In general, the test needs to view the test results. Therefore, when creating a test process, the default first action is the "Set result save path" action.

[0110] S4.2.1 Add process nodes

[0111] On the process details page, click the "+" button on the center interface to pop up the node selection box. The selection page displays all configured common nodes, actions, function blocks, instructions, and custom nodes. Select the required node and click the name to add it. The center interface displays the added node content. Node operations include: replace, delete, copy, and move node order. Select the node, and the configuration interface on the right displays the configuration information of the node, including data / event information.

[0112] S4.2.2 Set process node data information (data modeling mapping)

[0113] If the selected node has inlet / outlet parameters, the specific parameters will be displayed in the 'Data' area of ​​the right configuration interface. When you place the mouse on the parameter name, a floating window will pop up to display the specific information of the parameter. Check the box behind the parameter name to indicate that the parameter needs to be edited before running. Uncheck it to indicate that it does not need to be edited before running.

[0114] Data modeling mapping: In the "Data" area, click "Data modeling mapping" next to the input parameter / output parameter to pop up the data modeling mapping box. On the data modeling mapping page, click "Add a mapping" to insert a mapping data in the page list. You can select the input / output parameters to map with the variables in the data modeling. After adding, click the "Save" button to complete the mapping. For processes that do not require mapping, you can ignore this step.

[0115] S4.2.3 Set process node event information (event strategy)

[0116] To add an event, you can refer to the "Event Strategy Explanation", which is the instruction manual for the event strategy selected during the configuration process, including the type of event strategy selected, how to use it, etc. The configuration steps of the event strategy include: select the node, click "Event" in the configuration information on the right interface, switch to the event interface, click the "Add Event" button, and the event strategy edit box pops up. First, select the event type, including: start execution, end execution; then select the specific information of the event execution, including the execution duration; finally, select the execution conditions, including: direct execution, meet conditions, meet at the same time, and meet any conditions. Select the corresponding event strategy according to actual business needs. After the configuration is completed, click the "Save" button in the upper right corner of the interface, and it will prompt that the save is successful. Click 'Return' to return to the process settings page, and you can view the newly added process information.

[0117] S4.3 Add monitoring process

[0118] When monitoring parameters, such as voltage or current, are required in the test process, a monitoring process can be added to the process. In the process adding page, click on the blank area of ​​the center page. The right interface displays the configurable content. Click "Add Monitoring Process" and the monitoring process selection box pops up. The monitoring process selection box displays all test processes of the type "Monitoring Process". Select the monitoring process to be added and click it to successfully add the monitoring process. The added monitoring process is displayed in the 'Monitoring Process' area on the right side of the center page. When the monitoring process is not needed, click the 'Delete' icon next to the monitoring process name to delete it.

[0119] S4.4 Add exception handling process

[0120] On the process adding page, click on the blank area of ​​the center page. The right interface displays the configurable content. Click "Add Exception Handling Process" to pop up the exception handling process selection box. The exception handling process selection box displays all test processes of type "Exception Handling". Select the exception handling process to be added and click it to successfully add the exception handling process. The added exception handling process is displayed in the 'Exception Handling Process' area on the right side of the center page. When the process is no longer needed, click the 'Delete' icon next to the process name to delete it.

[0121] S4.5 Data Monitoring

[0122] When a data monitoring node is added to the process, such as adding a general node "data judgment", the data monitoring area will display the data monitoring node information. Data monitoring is added based on the product's technical indicators or test requirements. Data monitoring and parameter monitoring in the monitoring process are both used for product data and parameter monitoring, but the data in data monitoring may be temporary data generated in the test process, not parameters in advance modeling. Data judgment: The product will generate temporary data or process data during testing. Data judgment is used to determine whether the test process is carried out according to the original configuration or how the test process should be carried out when there are different judgment results, or to collect data qualification judgments for complex logic in the control logic, and whether the data after calculation meets the product technical indicator requirements.

[0123] S4.6 Other operations

[0124] You can query, edit, copy, delete, and other operations on the process.

[0125] S5. Product Testing

[0126] S5.1 Hardware Connection

[0127] According to the composition of the process platform, prepare a PC and install the process automation host computer components;

[0128] S5.2 Automated Testing

[0129] Execute automated testing on the created test process, including: editing parameters before testing, starting testing, stopping testing, and viewing test results. The parameters that need to be edited before testing are based on the technical specifications or test process specifications of the group product.

[0130] Click "Automation" on the left menu to enter the automation interface. By default, this page only displays the normal process and troubleshooting process. Check "Show other processes" in the upper right corner to display other processes. The automation interface displays the content of the process version currently downloaded by the local machine. Click the process to be tested to enter the process test interface. Click the node icon to display all node information of the process. The nodes that need to be edited before running have a green edit icon in the upper right corner, which means that before starting the test, the node needs to be set with parameters. After the parameters of all nodes are set, click the "Save" button at the top of the interface, and then click the "Start Test" button to start the automated test. If you need to terminate the test, click the "Stop Test" button to stop the test.

[0131] Before testing, the parameters of the node "Set file path / file directory path" can be reset. For the parameters of other nodes, the tester can only re-edit the parameters before starting the test if "Edit before running" is selected. If it is not selected, the parameters cannot be modified.

[0132] For tests completed in online mode, the test data will be uploaded to the data management platform in real time. If the test is completed in offline mode, the test result file must be manually uploaded to the data management platform through the data upload client.

[0133] S5.3 Debug Mode

[0134] The test modes include automatic mode, manual mode and debug mode. The debug mode is used to observe the changes in node parameters and troubleshoot problems. The debug process is used for automated testing. When running in debug mode, select the specified "debug process" to create a "data modeling snapshot" as required to facilitate monitoring of data changes. The data includes multiple data such as the parameters of the visual configuration, the gyro meter data pulse of the inertial group product, the product temperature, the gyro light intensity change, and the meter temperature. In the automation interface, select the test process that needs to be debugged, enter the automation test interface, check the "debug mode" in the upper right corner of the interface, enter the debug mode state, and click the window adjustment icon to maximize or minimize the debug mode window. Before starting the debugging test, you need to click the "Save" button to save the process, and then click the "Start Debugging" button in the "Debug" area. It will prompt whether to start the test. Click "OK" to start the test. Click "Cancel Debugging" to stop the test. During debugging, you can check "Show Path" to view the node path; you can also view the current running node, breakpoints, view data bus values, and add debugging monitoring.

[0135] Example 4

[0136] This embodiment 4 provides a flexible testing method for an inertial combination measurement device, and the method specifically includes:

[0137] Log in to the process automation test software, select the current product and equipment model in the product and equipment drop-down list, and the process automation test software can automatically record the last selected content. If there is no change, there is no need to re-select;

[0138] In the automated test interface, select the test process for this time. The process automated test software can automatically record the content selected last time. If there is no change, there is no need to reselect.

[0139] Click the Start Test button on the interface. The process automation test software will automatically load the product and device drivers based on the selected information, that is, the underlying instructions, acquisition control logic, and test process of the products and devices that have been configured in advance, call the selected test process, and enter the test execution phase.

[0140] During the test, if an exception occurs, the configured exception handling process is adopted to perform emergency stop, power off and other operations to ensure product safety;

[0141] All operations and key states are recorded by the log system.

[0142] The contents explained in the above embodiments should be understood as these embodiments are only used to more clearly illustrate the present invention, and are not used to limit the scope of the present invention. After reading the present invention, various equivalent forms of modifications to the embodiments made by those skilled in the art fall within the scope defined by the claims attached to the present invention.

Claims

1. A flexible test system for an inertial combination measurement device, characterized in that: The system includes a test platform and an inertial combination measurement device. The test platform includes a host computer, a gateway, an inertial combination universal acquisition box, a test device and a back-end server. The host computer is installed with a process automation component. The process automation component generates a test process through visual configuration, and the test process is scheduled by an inertial combination test engine to complete the automated test of the inertial combination measurement device; the host computer is connected to the gateway and the inertial combination universal acquisition box respectively; the gateway is connected to the test device to control the command reception and transmission and data feedback of the test device; the inertial combination universal acquisition box is connected to the inertial combination measurement device to control the command reception and transmission and data collection of the inertial combination measurement device; the back-end server is connected to the host computer to store the database of the test platform.

2. The flexible test system for an inertial combination measurement unit according to claim 1, characterized in that: The process automation components also include basic configuration, underlying communication protocols and drivers, acquisition control logic, data and event buses; The basic configuration adds, deletes and modifies the header of the data acquisition interface according to the data categories to be displayed in the test, sets the controls of the data acquisition interface, binds the data source, and creates a mapping relationship between the data source and the data bus variables; wherein the data source is the basic data of the test equipment and the inertial combination measurement device, and the data bus variables are stored in the data and event bus module for scheduling data interaction during the execution of the test process; the data acquisition interface is the configuration interface of the basic configuration implemented by the visualization configuration, and the controls include buttons, drop-down boxes, input boxes, radio buttons, check boxes and tables; The underlying communication protocol and the driver configure the instructions through the visual configuration, generate instructions that meet the requirements of the underlying communication protocol, and create a mapping relationship between the parameters of the instructions and the data bus variables; the instructions include a sending frame and a return frame, the sending frame is the instruction frame sent by the host computer, and the return frame is the response instruction frame returned by the inertial combination measurement device; The acquisition control logic includes simple logic and complex logic, which are used to control the sending frame and receive the return frame; the acquisition control logic is configured through the visual configuration, generates function blocks and / or actions, creates a mapping relationship between the parameters of the function blocks and / or actions and the data bus variables, and creates an event strategy corresponding to the function blocks and / or actions; wherein the event strategy is stored in the data and event bus module, and is used to schedule the strategy triggering during the execution of the test process, the function block is formed after the instruction is processed by the simple logic, and the action is formed after the instruction is processed by the complex logic; The test process includes a common process and a monitoring process, which is configured and generated through the visual configuration, and a mapping relationship between the parameters of the test process and the data bus variables is created, and an event strategy corresponding to the test process is created. The configuration nodes of the common process include actions and function blocks, and the monitoring process is used to monitor the data of the inertial combination measurement device under test and the status of the test equipment in real time.

3. The flexible test system for an inertial combination measurement unit according to claim 2, characterized in that: The configuration nodes of the test process also include custom nodes, and the custom nodes are used to call the newly written underlying program.

4. The flexible test system for an inertial combination measurement unit according to claim 2, characterized in that: The test process also includes sub-processes, troubleshooting processes, and exception handling processes; the sub-processes are test processes for repetitive operations in the test, the troubleshooting process is a test process for verification and / or troubleshooting, and the exception handling process is a test process executed when an exception error is reported in the test.

5. The flexible test system for an inertial combination measurement unit according to claim 2, characterized in that: The test process also includes a debugging process, which is used for debugging mode testing to supervise changes in test data, and the test data includes parameters of the instructions, parameters of the function blocks and / or the actions, parameters of the test process, and basic data of the test equipment and the inertial combination measurement device.

6. The flexible test system for an inertial combination measurement unit according to claim 2, characterized in that: The test process also includes a binding process, and the binding process is used for manual mode testing to reduce the reciprocating operation in the manual mode testing.

7. A flexible testing method for an inertial combination measurement device, characterized in that: The method is based on the flexible testing system for an inertial combined measurement device according to claim 2, comprising: Step 1, log in to the process automation test software, and select the model of the inertial combination measurement device and the test equipment to be tested in the drop-down list; the process automation test software can automatically record the content selected last time, if there is no change, go to step 2, if you need to create a new test process, go to step 3; Step 2: In the automated test interface, select the test process. The automated test software can automatically record the last selected content. If there is no change, go to step 4. Step 3: If a new test process needs to be created, the basic configuration, underlying communication protocol and driver, and acquisition control logic configuration related to the test process are completed through the visual configuration according to the test requirements, and then step 4 is entered; Step 4: Click the Start Test button on the interface. The process automation test software automatically loads the instructions, function blocks and / or actions, and test processes configured through the visual configuration according to the selected information, calls the selected test process, and enters the test execution phase. Step 5, scheduling the test process through the inertial combination test engine to execute the actions in the test process from top to bottom according to the event strategy of the test process, executing the complex logic in the action and / or the simple logic in the function block after the action is triggered, generating the sending frame and sending it to the inertial combination measurement device, the inertial combination measurement device returns the return frame, the acquisition control logic module controls the issuance of the next sending frame by processing the data in the return frame or according to the data in the return frame, and the test data fed back by the inertial combination measurement device is displayed on the data acquisition interface from bottom to top; Step 6: During the test, the monitoring process is nested in the common process and executed in parallel to monitor the data of the inertial combination measurement device and the status of the test equipment, including but not limited to voltage, current, output pulse, temperature, and angle.

8. The flexible testing method for an inertial combination measurement device according to claim 7, characterized in that: Before executing step 4, the method further includes: Set the file path, which is the path for storing test data and test logs; And / or, edit the parameters of the test process according to the test requirements.

9. The flexible testing method for an inertial combination measurement device according to claim 8, characterized in that: The test process also includes an exception handling process, which is a test process executed when an exception error is reported during the test. The method also includes: Step 7: During the test, when an exception occurs, the configured exception handling process is called.

10. The flexible testing method for an inertial combination measurement device according to claim 9, characterized in that: The method further comprises: Step 8: During the test, all operations and key states are recorded by the test log.

Images