CN101957878B - Method and device for constructing and managing prototype device library - Google Patents

Abstract

The invention discloses a method for constructing and managing a prototype device library, which comprises the following steps of: creating the prototype device library, and configuring parameters of the prototype device library, including creating simulation equipment, wherein the prototype device library comprises a plurality of pieces of simulation equipment, the parameters of the simulation equipment is configured and the configured simulation equipment is added into the prototype device library; after the configuration, saving the prototype device library; and receiving a simulation control command, and controlling the prototype device library to execute a corresponding simulation action according to the simulation control command. The invention also discloses a device for constructing and managing the prototype device library, which comprises a configuration module, a saving module and a control module. The method and the device for constructing and managing the prototype device library have the advantages of flexibly configuring the attributes of the prototype device library according to different hardware required by different projects, and meeting the requirements of different projects.

Description

Method and device for constructing and managing prototype device library

technical field

The invention relates to the field of computer application technology and semiconductors, in particular to a method and device for constructing and managing a prototype device library.

Background technique

With the continuous improvement of the integration level of integrated circuit chips and the continuous improvement of chip functions, people's requirements for technology are getting higher and higher. In the research, development and testing of semiconductor manufacturing equipment, including hardware and software research and development. Most of the development software is equipment control software. When testing these software, they need to be verified in the simulation environment first. However, simply developing a software test platform for a certain project is not only time-consuming but also poor in reusability. In order to improve The efficiency of software testing and the accurate positioning of system problems urgently require a general software testing platform system. It is necessary to provide simulation programs for all the hardware used in each project, so that the developed software can run on this basis for testing.

Simulation plays an important role in the research, development and testing of semiconductor manufacturing equipment. On the one hand, due to the complexity of the production process control itself, new requirements are constantly put forward for theoretical research, and theoretical research needs to increase the utilization rate of equipment. With the help of simulation tools; on the other hand, in the face of various system control software packages, a ready-made simulation platform is needed to fully reflect the effect of the algorithm in actual production and operation, and to obtain instructive algorithm improvement strategies, online parameter adjustment methods, etc. . The use of the simulation platform can accurately test the equipment control system software, reduce the failure of control system software execution and integrated circuit manufacturing process, solve the process stability and process reliability of integrated circuit process equipment, reduce equipment maintenance time, and maximize Improve the utilization rate of equipment.

The existing construction and management method and device of the prototype device library, from a functional point of view, the prototype device library creation management method and system mainly include the following functional modules:

(1) Device configuration module

Configure the communication protocol submodule: save the (communication protocol) attribute of the device selected by the user;

Configure the device parameter sub-module: save the device parameters configured by the user and put them in a container;

Configuration control command sub-module: put the command configured by the user in the position corresponding to the device parameter in the container.

(2) Device behavior module

Set the response time sub-module: save the (response time) parameters set by the user;

Set the reply information sub-module: put the reply information configured by the user in the position corresponding to the device command in the container;

Connection test sub-module: it can call the protocol layer function to send test information to the control computer to judge whether the command of the device is set correctly;

Set the device coupling relationship sub-module: use the container to save the relationship between the parameters inside the device;

Set parameter change behavior sub-module: use container to store parameter change behavior.

(3) Device editing module

Device renaming submodule: modify the identifier or name of the device object;

Modify the equipment parameter sub-module: modify the parameters of the equipment object.

(4) Equipment operation module

The equipment operation module is mainly responsible for invoking the protocol layer interface to communicate with the control terminal during the simulation operation.

The above-mentioned construction and management device for the prototype device library cannot configure the prototype device library according to the requirements of different manufacturing equipment, cannot meet the requirements of different hardware for different projects, and has poor configuration flexibility.

Contents of the invention

The purpose of the present invention is to at least solve one of the above-mentioned technical defects. In particular, a method and device for constructing and managing a prototype device library are proposed, which are suitable for simulation systems of different manufacturing equipment oriented to equipment control software testing, and can be used according to different According to different hardware usage methods in the project, the attributes of the prototype device library can be flexibly configured.

In order to achieve the above object, the present invention proposes a construction and management method of a prototype device library on the one hand, including the following steps:

Create a prototype device library, and configure the parameters of the prototype device library, including:

creating a simulation device, wherein the prototype device library includes a plurality of simulation devices,

Configuring parameters of the simulated device, wherein the parameters of the simulated device include: attributes of the simulated device, commands of the simulated device, actions of the simulated device, and communication ports of the simulated device, and

Add the configured simulation device to the prototype device library;

After the configuration is completed, save the prototype device library; and

receiving a simulation control command, and controlling the prototype device library to perform corresponding simulation actions according to the simulation control command.

The construction and management method of the prototype device library according to the embodiment of the present invention can be configured as related equipment that needs to be simulated according to the simulation requirements. After configuration, the prototype device library can be applied to the simulation devices of different manufacturing equipment for equipment control software testing, and the properties of the prototype device library can be flexibly configured according to the different methods of using the hardware in different projects to meet different project requirements.

On the other hand, the present invention also proposes a device for constructing and managing a prototype device library, including:

The configuration module is used to create a prototype device library, and configure the parameters of the prototype device library, including:

The configuration module creates a simulation device, wherein the prototype device library includes a plurality of the simulation devices,

The configuration module configures the parameters of the simulated device, wherein the parameters of the simulated device include: attributes of the simulated device, commands of the simulated device, actions of the simulated device and communication ports of the simulated device, Adding the configured simulation device to the prototype device library with the configuration module;

Save the module, used to save the configured prototype device library; and

The control module is configured to receive a simulation control command, and control the prototype device library to perform corresponding simulation actions according to the simulation control command. The device for constructing and managing a prototype device library according to an embodiment of the present invention can be configured as a related device that needs to be simulated according to a simulation requirement. After configuration, the prototype device library can be applied to the simulation devices of different manufacturing equipment for equipment control software testing, and the properties of the prototype device library can be flexibly configured according to the different methods of using the hardware in different projects to meet different project requirements.

Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Description of drawings

The above and/or additional aspects and advantages of the present invention will become apparent and easy to understand from the following description of the embodiments in conjunction with the accompanying drawings, wherein:

Fig. 1 is the flow chart of the construction and the management method of the prototype device library according to the embodiment of the present invention;

Fig. 2 is the implementation flowchart of the construction and management method of the prototype device library in Fig. 1;

Fig. 3 is the configuration according to the embodiment of the present invention and maintains the flowchart of prototype device storehouse;

4 is a structural diagram of a simulation device class according to an embodiment of the present invention;

5 is a schematic diagram of an interface for hierarchical management of simulation equipment according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an interface for creating a simulated device name and a simulated device type in FIG. 3;

FIG. 7 is a schematic diagram of an interface of a simulated device name and a simulated device type that are edited and configured according to an embodiment of the present invention;

8 is a schematic diagram of an interface for creating and editing properties of a simulated device according to an embodiment of the present invention;

9 is a schematic diagram of an interface for configuring simulation device parameters according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of an interface for configuring a simulation device command according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of an interface for configuring an action name of a simulation device according to an embodiment of the present invention;

12 is a schematic diagram of an interface for configuring action content of a simulation device according to an embodiment of the present invention;

Fig. 13 is a schematic diagram of the interface for configuring the action conditions of the simulation device in Fig. 12;

Fig. 14 is a schematic diagram of the interface of configuring the delay waiting of the simulated device in Fig. 12;

Fig. 15 is a schematic diagram of the interface of configuring the changing rule of the simulation device in Fig. 12;

Fig. 16 is a schematic diagram of the interface of three kinds of changing laws in Fig. 15;

Fig. 17 is a schematic diagram of the interface of configuration return information in Fig. 12;

18 is a schematic diagram of an interface for configuring coupling conditions of a simulation device according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of an Ethernet interface for configuring a simulation device according to an embodiment of the present invention;

20 is a schematic diagram of an interface for configuring a serial port protocol port of a simulation device according to an embodiment of the present invention;

21 is a flow chart of controlling prototype device library simulation according to an embodiment of the present invention;

22 is a schematic diagram of the running interface of the simulation device in the prototype device library according to an embodiment of the present invention; and

Fig. 23 is a schematic diagram of an apparatus for constructing and managing a prototype device library according to an embodiment of the present invention.

Detailed ways

Embodiments of the present invention are described in detail below, examples of which are shown in the drawings, wherein the same or similar reference numerals designate the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the figures are exemplary only for explaining the present invention and should not be construed as limiting the present invention.

In order to better understand the present invention, the construction and management method of the prototype device library according to the embodiment of the present invention will be described below with reference to the accompanying drawings. In the following description, the simulation system oriented to semiconductor manufacturing equipment functions is taken as an example, that is, the prototype device library provided by the embodiment of the present invention is suitable for the simulation system of semiconductor manufacturing equipment functions. It should be understood that the present invention is not limited thereto.

As shown in Figures 1 and 2, the construction and management method of the prototype device library of the embodiment of the present invention includes the following steps:

S101: Create a prototype device library, and configure parameters of the prototype device library;

As shown in Fig. 3, the prototype device library is firstly created. Since the prototype device library includes multiple simulation devices, the process of creating the prototype device library includes creating multiple simulation devices in the prototype device library.

In order to better understand the process of creating a simulated device in the present invention, the class structure of the simulated device will be described below in conjunction with FIG. 4 . As shown in Figure 4, the simulated device class mainly includes attribute class, command class and action class list. Each class includes its own properties and methods. FIG. 5 further shows a schematic diagram of an interface for hierarchical management of simulated devices. In order to facilitate the classification and search of a large number of simulated devices, a tree structure is used to manage the simulated device files. The simulated device information tree is composed of simulated device (Device) node and action (action), command (Command) and attribute (Property) three leaf nodes. A simulated device can contain any number of action (action), command (Command) and property (Property) leaf nodes, and the action (action), command (Command) and property (Property) nodes must belong to a certain simulated device node.

The process of creating a simulated device is described below with reference to FIG. 6 and FIG. 7 .

First create the name of the simulated device, as shown in Figure 6, fill in the created device name in the text box corresponding to DeviceName. Fill in the device type to which the device belongs in the text box corresponding to DeviceType, and finally click Add to enter the list on the right. In the list on the right, you can edit and delete the added options, as shown in Figure 7. Thus, by creating a simulation device, the creation of a prototype device library is completed.

After creating the prototype device library, configure the parameters of the above prototype device library. That is, configure the parameters of the simulation device in the prototype device library.

Wherein, the parameters of the simulated device include: properties of the simulated device, commands of the simulated device, actions of the simulated device and communication ports of the simulated device.

(1) Configure the properties of the simulated device

Wherein, the attributes of the simulated device include attribute names and attribute types. Among them, the attribute type, such as int, string, etc.

As shown in FIG. 8 , first, select the simulated device whose properties need to be configured according to the created device list. After selecting the simulated device, add the simulated device property. The new emulated device property is added to the list of emulated device properties. As shown in FIG. 9 , in an embodiment of the present invention, the attributes of the simulated device may include attribute maximum values, attribute minimum values, and attribute default initial values in addition to attribute names and attribute types. Fill in the property name of the device in the text box corresponding to PropertyName, and select the property type from the drop-down menu corresponding to PropertyType. For example: Boolean type, numeric type, etc. Then fill in the maximum value, minimum value and default initial value of the attribute in the text box below according to the corresponding text prompt. When the default initial value of the attribute does not exist, the value can be empty. Finally, click Add to add to the list on the right. In the list on the right, the added options can be edited and deleted. Specifically, after the creation is complete, any item in the properties of the simulated device can be edited, and the added property of the simulated device can be deleted in the device property list.

After the configuration is complete, click Save to return to the emulation device configuration management interface. If you need to edit and delete later, you can repeat the above actions.

In one embodiment of the present invention, the properties of the simulated device are saved in XML file format, so as to be convenient for users to read.

(2) Commands to configure emulated devices

First, select the simulated device that needs to configure the command. After selecting the simulated device, configure the commands for the simulated device. Wherein, the command of the simulated device includes: command name, command transmission direction and command content. Wherein, the command transfer direction includes: the simulated device sends commands to other devices, the simulated device receives commands from other devices, and the simulated device sends commands to itself and returns information.

After configuring the command delivery direction, further configure the command content. Since each command corresponds to a protocol format, the command content includes protocol name, protocol address range, protocol address, command description, command attribute number and command device attribute.

Among them, for the protocol name, because the protocol follows the command, and a command corresponds to a protocol format, the protocol name can select various protocols created when configuring the protocol.

For the protocol address range, when the protocol is serial port and TCP/IP protocol, since the protocol layer self-encapsulates the protocol format for the two types of protocols, there may be multiple string-type protocol fields, and you need to specify which string the field of the command belongs to field.

The protocol address specifies the physical address or port number to send the command, and the command description is the text explanation of the command. The number of attributes of the command indicates the number of attributes of the simulated device included in the command. The device attribute of the command is to specify the device attributes included in the command. For example, the command includes 3 device attributes, and the 3 device attributes are specified respectively.

Add the command of the created simulated device to the simulated device command list, and then edit any item in the command, and delete the command of the simulated device in the device command list. Then save the command to emulate the device.

In an embodiment of the present invention, the command of the simulated device is saved in an XML file format, so that it is convenient for the user to read.

As shown in Figure 10, you first need to select the device to be configured from the DeviceName drop-down menu. The first step is to fill in the set command name in the text box corresponding to CommandName, select the sending direction of the command in the drop-down menu corresponding to CommandDirection, and then fill in a brief description of the command in CommandNote. In the second step, select the protocol name to be used by the command in the ProtocolName drop-down option. The third step is to confirm the device attributes corresponding to the parameters in the command. Fill in the number of parameters of the command in the text box corresponding to ParameterNumber, and click OK after filling in the confirmation, and then a column of the number of numbers filled in will be automatically generated in the table below, each column represents a parameter, and then in There will be a drop-down menu option under each parameter. The options are all the attribute names configured before. After selecting the corresponding attribute name, click Add to add to the list on the right. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click OK to return to the device configuration management interface. If you need to edit and delete later, you can repeat the above actions.

(3) Configure the action of the simulated device

First, configure the action name of the simulated device, and then add the action name to the action list. According to the created action list, select the action of the simulated device to be configured.

Select the simulated device command coupled with the simulated device action from the above configured simulated device commands. The simulation device can only execute the corresponding simulation action after receiving the relevant simulation device command. Wherein, the simulated device command includes sending to itself to trigger the coupling behavior in the simulated device.

After configuring the command of the simulated device, further configure the number of steps of the simulated device action and the action type of each step. Among them, the simulated device action can be subdivided into many steps, and each step can correspond to a device action type. Each simulated device action can be divided into each step to execute.

Among them, the simulation device action types are divided into 5 categories, including: command behavior, action conditions, delay waiting, change rules, and return information.

(1) Behavior of the configuration command: the action type of the simulation device is to assign values to the attributes of the simulation device carried by the specified simulation command when configuring the simulation device command.

(2) Configure action conditions: The action type of the simulated device is to execute the next step when judging that the device attributes meet the requirements. The judging conditions can be combined, and the behavior after judging is divided into then and else. For example: when the flow rate of the device MFC is greater than 1000, go to step 2, otherwise go to step 3. The configuration content includes: equipment attributes, conditional judgments (<, >, ==, <=, =>), attribute values and logical relationships.

Among them, the device attribute can be selected according to the created device attribute list. Attribute values need to be specified by the user. The logical relationship can be AND, OR, XOR. Many conditional judgments can be combined into one conditional judgment. A new action condition is added to the action condition list.

(3) Configuration delay waiting: The action type of the simulated device is to execute actions and wait for the corresponding time. The content of the configuration includes: waiting time, that is, how long the execution needs to wait, and the unit is ms; the next step to be executed, that is, the step to be executed next.

(4) Configuration change rule: the action type of the simulated device specifies the change rule of the simulated device attribute. The content of the configuration includes: device attributes, change rules, user-defined sturdy rule interfaces, and the next steps to be executed.

Among them, the device attribute is selected according to the created device attribute list.

The change rule can be specified in advance, and the user can select it according to the simulation requirements. The change rule includes four options: PID, PI, PD and custom.

User-defined change rule interface, through which the user can define the change rule of attributes.

The next step to execute is to select the next step to execute.

(5) Configuration return information: the simulated device action type specifies the returned information from the simulated device to the control terminal. The content of the configuration includes: command name, protocol name, attributes of the set command and the steps to be executed next.

Among them, the command name can be selected according to the return type in the created simulation device command list.

The protocol name has the same meaning as the configuration command, which can be selected according to the created protocol list.

Set the attributes of the command, mainly to set the attributes of the simulated device to which the returned information belongs).

The next step to execute is to select the next step to execute.

After the above configuration, the new simulated device action will be added to the device action list. Users can edit any step in adding device actions, and can delete the added content in the device action name list, action condition list, and device action list. Then save the action of the simulated device

In one embodiment of the present invention, the actions of the simulated device are saved in an XML file format, which is convenient for users to read.

As shown in Figure 11, you first need to select the emulation device to be configured from the DeviceName drop-down menu. The setting and editing device action interface is divided into 2 pages. Among them, one is the ActionManager page for creating the action name, and the other is the ActionEdit page for setting the action content. You need to create the action name on the ActionManager page first, and then set the content for each new action on the ActionEdit page.

First, on the ActionManager page, fill in the action name in the text box corresponding to ActionName, and then click Add to enter the list on the right. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click the ActionEdit option to enter the interface for setting action content, as shown in Figure 12. If you need to edit and delete later, you can repeat the above actions.

On the ActionEdit interface, in the first step, select the previously created action name from the drop-down menu corresponding to ActionName. In the second step, select the previously created command name in the drop-down menu corresponding to CommandName. Step 3: In the text box corresponding to The Number of Steps, fill in the number of action types to be executed after the action receives the specified command. Step 4: Configure the types of actions to be executed in sequence. .In the corresponding drop-down menu, select the Step corresponding to the quantity filled in the third step to configure. For example: fill in 3 in the third step, indicating that 3 types of actions are to be performed, and Step1 to Step3 appear in the drop-down menu corresponding to SepNo. For example, if Step1 is selected, you can configure the action type for this step below. The fifth step is to configure the action type. There are 5 options, namely Command Behavior, Action Condition, WaitTime, Variational Rule and Return Info.

(1) The command line is Command Behavior

Clicking Command Behavior is to execute the parameter passed in the command to correspond to the corresponding device attribute previously configured, that is, the function in the command of Step3 setting and editing the communication protocol used by the device.

(2) Action Condition Condition

After clicking Condition, an interface will pop up for users to customize, as shown in Figure 13: First, add a judgment condition, select the previously configured device property in the drop-down menu corresponding to Property, and select the relationship with the following value in the drop-down menu corresponding to Relationship (Including greater than, less than, equal to, greater than or equal to, less than or equal to 5 types), and then fill in the value related to the attribute in the text box corresponding to Value. For example, when the pressure is greater than 0.5, select pressure in Property, select greater than in Relationship, and fill in 0.5 in Value. Then click the Add button to add the conditional judgment to the list on the right. Because the judgment conditions can exist at the same time, there are three options: AND, OR, and XOR. For example, when the pressure is greater than 0.5 or the temperature is less than 30, click OR after the first condition is set and Add, and set the second condition at this time, click Add to complete adding a complete condition.

Then after adding a judgment condition, you need to set the execution action after the judgment. In the Then Step box, select the execution action type after judging the condition from the drop-down menu corresponding to NextStep. In the Else Step box, the drop-down menu corresponding to NextStep Another execution action type after the judgment condition is selected in (both are allowed to be empty). For example, under the condition that the pressure is greater than or equal to 0.6, if the waiting action is satisfied, in the Then Step box, select 3-WaitTime; otherwise, to execute the return command action, in the Else Step box, select 5-Return Info. Then click the Add button to add to the list on the right, corresponding to the judgment conditions defined above. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click OK to return to the device action configuration interface. If you need to edit and delete later, you can repeat the above actions.

(3) Delay waiting for WaitTime

After clicking WaitTime, you will enter the waiting time configuration interface, as shown in Figure 14, select the waiting delay time in the drop-down menu corresponding to Delay, and the time is given by the designer with reference to the actual device. After the configuration is complete, click OK to return to the device action configuration interface.

(4) Variational Rule

After clicking VariationalRule, the variation rule configuration interface is entered, as shown in Figure 15. Select the name of the parameter that needs to be changed in the Property drop-down option, and select the variation rule of the parameter (such as PID, PI, user-defined) in the drop-down menu corresponding to VariationalRule. Among them, Fig. 16(a) is a schematic diagram of an interface whose changing rule is user-defined, Fig. 16(b) is a schematic diagram of an interface whose changing rule is PID, and Fig. 16(c) is a schematic diagram of an interface whose changing rule is PI. After the configuration is complete, click OK to return to the device action configuration interface.

(5) Return Information Return Info

After clicking Return Info, enter the reply information configuration interface, as shown in Figure 17, select the previously configured device command in the drop-down menu corresponding to CommandName, select the previously configured protocol name in the drop-down menu corresponding to ProtocolName, and then click below Select the parameter value to be returned from the table. After the configuration is complete, click OK to return to the device action configuration interface.

In the same way, after configuring all the Steps in the drop-down menu, click the Add button to add to the list on the right. In the list on the right, you can edit and delete the added options. After the configuration is complete, click OK to return to the device action configuration interface. If you need to edit and delete later, you can repeat the above actions.

After completing the configuration of the above action steps, further configure and edit the coupling conditions in the simulated device. As shown in Figure 18, click the CouplingCondition option on the upper toolbar, select the Edit option, and click to enter the setting and editing device action interface. First, add the judgment condition, select the previously configured device property in the drop-down menu corresponding to Property, and select the device property corresponding to Relationship. Select the relationship with the following value from the drop-down menu (including five types of greater than, less than, equal to, greater than or equal to, and less than or equal to), and then fill in the value related to the attribute in the text box corresponding to Value. For example: when the pressure is greater than 0.5, select pressure in Property, select greater than in Relationship, and fill in 0.5 in Value. Then click the Add button to add the conditional judgment to the list on the right. Because the judgment conditions can exist at the same time, there are three options: AND, OR, and XOR. For example, when the pressure is greater than 0.5 or the temperature is less than 30, click OR after the first condition is set and Add, and set the second condition at this time, click Add to complete adding a complete condition.

Then after adding a judgment condition, you need to set the execution command after the judgment, and select the previously configured Send Self command in the drop-down menu corresponding to SendSelfCommand. Then click the Add button to add to the list on the right, corresponding to the judgment conditions defined above. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click OK to return to the device action configuration interface. If you need to edit and delete later, you can repeat the above actions.

After the action configuration of the simulated device is completed, further configure the communication port of the simulated device. Specifically, according to the command of the simulated device, the physical port corresponding to the command of the simulated device is configured.

As shown in Figure 19, after clicking Run, a window will pop up, and all command names during configuration will be listed in the drop-down menu of CommandName, and the physical port information corresponding to the command can be filled in the following block diagram. As shown in Figure 20, since the rec command of the device uses the TCP/IP protocol, it is necessary to fill in the physical port information of TCP/IP, while the c1 command uses the serial port protocol, so only the port needs to be filled in. After setting a command, you need to click "OK" once, and click Save when all the command configurations are completed.

After the above configuration of the simulation device is completed, the configured simulation device is added to the prototype device library, thereby completing the configuration of the prototype device library.

S102: Save the prototype device library.

After the prototype device library is configured in step 102, the above prototype device library is saved.

In an embodiment of the present invention, the prototype device library can be saved in XML format.

S103: Receive a simulation control command, and control the prototype device library to perform corresponding simulation actions according to the simulation control command.

Figure 21 shows a flow chart for controlling the execution of a simulation by a library of prototype devices. As shown in Fig. 21, firstly, the simulation control command from the outside is received, and the corresponding simulation device in the prototype device library is selected according to the received simulation control command. Then check for conflicting working ports within the emulated device.

If the working port of the simulated device has no conflict, the simulation control command is sent to the corresponding simulated device through the communication management interface; otherwise, the simulation is terminated.

Specifically, when the working port of the simulated device has no conflict, the simulated device starts to run, reads the parameters of the simulated device into the hash table, and initializes the working port of the simulated device. After initialization, bind the received simulation control command with the corresponding working port. According to the trigger event of the control command, the corresponding coupling action processing is performed, and the coupling action is executed by analyzing the data until all the control commands are completed, then the simulation ends.

When the configuration of the communication port in Figure 20 is correct, click Save, and a window will pop up to prompt the user that the device has been started, and the running interface is shown in Figure 22. After starting, you can receive and send commands and perform related actions. At the same time, all parameter information configured by the device will be listed in the table on the right, and the status of these parameters can be refreshed in time. Similarly, if you need to stop or exit the device, just click the relevant menu on the right button.

The simulation equipment operation simulation of the prototype device library mainly completes the dynamic simulation function of the equipment. The simulated device receives the data and performs corresponding actions to change the parameter value of the device, and the system interface dynamically displays the parameter value of the device in the form of a table.

The construction and management method of the prototype device library according to the embodiment of the present invention can be configured as related equipment that needs to be simulated according to the simulation requirements. After configuration, the prototype device library can be applied to the simulation devices of different manufacturing equipment for equipment control software testing, and the properties of the prototype device library can be flexibly configured according to the different methods of using the hardware in different projects to meet different project requirements.

The embodiment of the present invention also proposes a device for constructing and managing a prototype device library. As shown in FIG. 23 , the device 100 includes a configuration module 110 , a storage module 120 and a control module 130 .

The configuration module 110 first creates a prototype device library, and configures parameters of the prototype device library. Wherein, the prototype device library includes a plurality of simulation devices, so the configuration module 110 first needs to create simulation devices.

The apparatus 100 for constructing and managing a prototype device library in the embodiment of the present invention further includes a user interface module 140 . The user interface module 140 can input the parameters of the execution process of the configuration module 110, the storage module 120 and the control module 130, and display the execution results in the form of an interface.

As shown in FIG. 6 and FIG. 7 , the configuration module 110 first creates the name of the simulated device. As shown in FIG. 6 , fill in the created device name in the text box corresponding to DeviceName. Fill in the device type to which the device belongs in the text box corresponding to DeviceType, and finally click Add to enter the list on the right. In the list on the right, you can edit and delete the added options, as shown in Figure 7. Thus, the configuration module 110 completes the creation of the prototype device library by creating the simulation device.

After the prototype device library is created, the configuration module 110 configures the parameters of the prototype device library. That is, configure the parameters of the simulation device in the prototype device library. Wherein, the parameters of the simulated device include: properties of the simulated device, commands of the simulated device, actions of the simulated device and communication ports of the simulated device.

(1) Configure the properties of the simulated device

Wherein, the attributes of the simulated device include attribute names and attribute types. Among them, the attribute type, such as int, string, etc. As shown in FIG. 8 , first, select the simulated device whose properties need to be configured according to the created device list. After selecting the simulated device, add the simulated device property. The new emulated device property is added to the list of emulated device properties. As shown in FIG. 9 , in an embodiment of the present invention, the attributes of the simulated device may include attribute maximum values, attribute minimum values, and attribute default initial values in addition to attribute names and attribute types. Fill in the property name of the device in the text box corresponding to PropertyName, and select the property type from the drop-down menu corresponding to PropertyType. For example: Boolean type, numeric type, etc. Then fill in the maximum value, minimum value and default initial value of the attribute in the text box below according to the corresponding text prompt. When the default initial value of the attribute does not exist, the value can be empty. Finally, click Add to add to the list on the right. In the list on the right, the added options can be edited and deleted. Specifically, after the creation is complete, any item in the properties of the simulated device can be edited, and the added property of the simulated device can be deleted in the device property list.

After the configuration module 110 is configured, click Save to return to the simulation device configuration management interface. If you need to edit and delete later, you can repeat the above actions.

In one embodiment of the present invention, the properties of the simulated device are saved in XML file format, so as to be convenient for users to read.

(2) Commands to configure emulated devices

First, the configuration module 110 selects a simulated device that needs configuration commands. After selecting the simulated device, configure the commands for the simulated device. Wherein, the command of the simulated device includes: command name, command transmission direction and command content. Wherein, the command transfer direction includes: the simulated device sends commands to other devices, the simulated device receives commands from other devices, and the simulated device sends commands to itself and returns information.

After configuring the command delivery direction, further configure the command content. Since each command corresponds to a protocol format, the command content includes protocol name, protocol address range, protocol address, command description, command attribute number and command device attribute. Among them, for the protocol name, because the protocol follows the command, and a command corresponds to a protocol format, the protocol name can select various protocols created when configuring the protocol. For the protocol address range, when the protocol is serial port and TCP/IP protocol, since the protocol layer self-encapsulates the protocol format for the two types of protocols, there may be multiple string-type protocol fields, and you need to specify which string the field of the command belongs to field.

The protocol address specifies the physical address or port number to send the command, and the command description is the text explanation of the command. The number of attributes of the command indicates the number of attributes of the simulated device included in the command. The device attribute of the command is to specify the device attributes included in the command. For example, the command includes 3 device attributes, and the 3 device attributes are specified respectively.

The configuration module 110 adds the command of the created simulated device to the simulated device command list, and then any item in the command can be edited, and the command of the simulated device can be deleted from the device command list. Then save the command to emulate the device.

In an embodiment of the present invention, the command of the simulated device is saved in an XML file format, so that it is convenient for the user to read.

As shown in Figure 10, you first need to select the device to be configured from the DeviceName drop-down menu. The first step is to fill in the set command name in the text box corresponding to CommandName, select the sending direction of the command in the drop-down menu corresponding to CommandDirection, and then fill in a brief description of the command in CommandNote. In the second step, select the protocol name to be used by the command in the ProtocolName drop-down option. The third step is to confirm the device attributes corresponding to the parameters in the command. Fill in the number of parameters of the command in the text box corresponding to ParameterNumber, and click OK after filling in the confirmation, and then a column of the number of numbers filled in will be automatically generated in the table below, each column represents a parameter, and then in There will be a drop-down menu option under each parameter. The options are all the attribute names configured before. After selecting the corresponding attribute name, click Add to add to the list on the right. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click OK to return to the device configuration management interface. If you need to edit and delete later, you can repeat the above actions.

(3) Configure the action of the simulated device

First, the configuration module 110 configures the action name of the simulated device, and then adds the action name to the action list. According to the created action list, select the action of the simulated device to be configured.

From the above configured simulated device commands, the configuration module 110 selects simulated device commands coupled with simulated device actions. The simulation device can only execute the corresponding simulation action after receiving the relevant simulation device command. Wherein, the simulated device command includes sending to itself to trigger the coupling behavior in the simulated device.

After configuring the commands of the simulated device, the configuration module 110 further configures the number of steps of the simulated device's action and the action type of each step. Among them, the simulated device action can be subdivided into many steps, and each step can correspond to a device action type. Each simulated device action can be divided into each step to execute.

Among them, the simulation device action types are divided into 5 categories, including: command behavior, action conditions, delay waiting, change rules, and return information.

(1) Behavior of the configuration command: the action type of the simulation device is to assign values to the attributes of the simulation device carried by the specified simulation command when configuring the simulation device command.

(2) Configure action conditions: The action type of the simulated device is to execute the next step when judging that the device attributes meet the requirements. The judging conditions can be combined, and the behavior after judging is divided into then and else. For example: when the flow rate of the device MFC is greater than 1000, go to step 2, otherwise go to step 3. The configuration content includes: equipment attributes, conditional judgments (<, >, ==, <=, =>), attribute values and logical relationships.

Among them, the device attribute can be selected according to the created device attribute list. Attribute values need to be specified by the user. The logical relationship can be AND, OR, XOR. Many conditional judgments can be combined into one conditional judgment. A new action condition is added to the action condition list.

(3) Configuration delay waiting: The action type of the simulated device is to execute actions and wait for the corresponding time. The content of the configuration includes: waiting time, that is, how long the execution needs to wait, and the unit is ms; the next step to be executed, that is, the step to be executed next.

(4) Configuration change rule: the action type of the simulated device specifies the change rule of the simulated device attribute. The content of the configuration includes: device attributes, change rules, user-defined sturdy rule interfaces, and the next steps to be executed.

Among them, the device attribute is selected according to the created device attribute list.

The change rule can be specified in advance, and the user can select it according to the simulation requirements. The change rule includes four options: PID, PI, PD and custom.

User-defined change rule interface, through which the user can define the change rule of attributes.

The next step to execute is to select the next step to execute.

(5) Configuration return information: the simulated device action type specifies the returned information from the simulated device to the control terminal. The content of the configuration includes: command name, protocol name, attributes of the set command and the steps to be executed next.

Among them, the command name can be selected according to the return type in the created simulation device command list.

The protocol name has the same meaning as the configuration command, which can be selected according to the created protocol list.

Set the attributes of the command, mainly to set the attributes of the simulated device to which the returned information belongs).

The next step to execute is to select the next step to execute.

After the above configuration, the configuration module 110 adds the new simulated device action to the device action list. Users can edit any step in adding device actions, and can delete the added content in the device action name list, action condition list, and device action list. Then save the action of the simulated device

In one embodiment of the present invention, the actions of the simulated device are saved in an XML file format, which is convenient for users to read.

As shown in Figure 11, you first need to select the emulation device to be configured from the DeviceName drop-down menu. The setting and editing device action interface is divided into 2 pages. Among them, one is the ActionManager page for creating the action name, and the other is the ActionEdit page for setting the action content. You need to create the action name on the ActionManager page first, and then set the content for each new action on the ActionEdit page.

First, on the ActionManager page, fill in the action name in the text box corresponding to ActionName, and then click Add to enter the list on the right. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click the ActionEdit option to enter the interface for setting action content, as shown in Figure 12. If you need to edit and delete later, you can repeat the above actions.

On the ActionEdit interface, in the first step, select the previously created action name from the drop-down menu corresponding to ActionName. In the second step, select the previously created command name in the drop-down menu corresponding to CommandName. Step 3: In the text box corresponding to The Number of Steps, fill in the number of action types to be executed after the action receives the specified command. Step 4: Configure the types of actions to be executed in sequence. .In the corresponding drop-down menu, select the Step corresponding to the quantity filled in the third step to configure. For example: fill in 3 in the third step, indicating that 3 types of actions are to be performed, and Step1 to Step3 appear in the drop-down menu corresponding to SepNo. For example, if Step1 is selected, you can configure the action type for this step below. The fifth step is to configure the action type. There are 5 options, namely Command Behavior, Action Condition, WaitTime, Variational Rule and Return Info.

(1) The command line is Command Behavior

Clicking Command Behavior is to execute the parameter passed in the command to correspond to the corresponding device attribute previously configured, that is, the function in the command of Step3 setting and editing the communication protocol used by the device.

(2) Action Condition Condition

After clicking Condition, an interface will pop up for users to customize, as shown in Figure 13: First, add a judgment condition, select the previously configured device property in the drop-down menu corresponding to Property, and select the relationship with the following value in the drop-down menu corresponding to Relationship (Including greater than, less than, equal to, greater than or equal to, less than or equal to 5 types), and then fill in the value related to the attribute in the text box corresponding to Value. For example, when the pressure is greater than 0.5, select pressure in Property, select greater than in Relationship, and fill in 0.5 in Value. Then click the Add button to add the conditional judgment to the list on the right. Because the judgment conditions can exist at the same time, there are three options: AND, OR, and XOR. For example, when the pressure is greater than 0.5 or the temperature is less than 30, click OR after the first condition is set and Add, and set the second condition at this time, click Add to complete adding a complete condition.

Then after adding a judgment condition, you need to set the execution action after the judgment. In the Then Step box, select the execution action type after judging the condition from the drop-down menu corresponding to NextStep. In the Else Step box, the drop-down menu corresponding to NextStep Another execution action type after the judgment condition is selected in (both are allowed to be empty). For example, under the condition that the pressure is greater than or equal to 0.6, if the waiting action is satisfied, in the Then Step box, select 3-WaitTime; otherwise, to execute the return command action, in the Else Step box, select 5-Return Info. Then click the Add button to add to the list on the right, corresponding to the judgment conditions defined above. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click OK to return to the device action configuration interface. If you need to edit and delete later, you can repeat the above actions.

(3) Delay waiting for WaitTime

After clicking WaitTime, you will enter the waiting time configuration interface, as shown in Figure 14, select the waiting delay time in the drop-down menu corresponding to Delay, where the time is given by the designer with reference to the actual device. After the configuration is complete, click OK to return to the device action configuration interface.

(4) Variational Rule

After clicking VariationalRule, the variation rule configuration interface is entered, as shown in Figure 15. Select the name of the parameter that needs to be changed in the Property drop-down option, and select the variation rule of the parameter (such as PID, PI, user-defined) in the drop-down menu corresponding to VariationalRule. Among them, Fig. 16(a) is a schematic diagram of an interface whose changing rule is user-defined, Fig. 16(b) is a schematic diagram of an interface whose changing rule is PID, and Fig. 16(c) is a schematic diagram of an interface whose changing rule is PI. After the configuration is complete, click OK to return to the device action configuration interface.

(5) Return Information Return Info

After clicking Return Info, enter the reply information configuration interface, as shown in Figure 17, select the previously configured device command in the drop-down menu corresponding to CommandName, select the previously configured protocol name in the drop-down menu corresponding to ProtocolName, and then click below Select the parameter value to be returned from the table. After the configuration is complete, click OK to return to the device action configuration interface.

In the same way, after configuring all the Steps in the drop-down menu, click the Add button to add to the list on the right. In the list on the right, you can edit and delete the added options. After the configuration is complete, click OK to return to the device action configuration interface. If you need to edit and delete later, you can repeat the above actions.

After completing the configuration of the above action steps, the configuration module 110 further configures and edits the coupling conditions in the simulated device. As shown in Figure 18, click the CouplingCondition option on the upper toolbar, select the Edit option, and click to enter the setting and editing device action interface. First, add the judgment condition, select the previously configured device property in the drop-down menu corresponding to Property, and select the device property corresponding to Relationship. Select the relationship with the following value from the drop-down menu (including five types of greater than, less than, equal to, greater than or equal to, and less than or equal to), and then fill in the value related to the attribute in the text box corresponding to Value. For example: when the pressure is greater than 0.5, select pressure in Property, select greater than in Relationship, and fill in 0.5 in Value. Then click the Add button to add the conditional judgment to the list on the right. Because the judgment conditions can exist at the same time, there are three options: AND, OR, and XOR. For example, when the pressure is greater than 0.5 or the temperature is less than 30, click OR after the first condition is set and Add, and set the second condition at this time, click Add to complete adding a complete condition.

Then after adding a judgment condition, you need to set the execution command after the judgment, and select the previously configured Send Self command in the drop-down menu corresponding to SendSelfCommand. Then click the Add button to add to the list on the right, corresponding to the judgment conditions defined above. In the list on the right, the added options can be edited and deleted. After the configuration is complete, click OK to return to the device action configuration interface. If you need to edit and delete later, you can repeat the above actions.

After the action configuration of the simulated device is completed, further configure the communication port of the simulated device. Specifically, according to the command of the simulated device, the physical port corresponding to the command of the simulated device is configured.

As shown in Figure 19, after clicking Run, a window will pop up, and all command names during configuration will be listed in the drop-down menu of CommandName, and the physical port information corresponding to the command can be filled in the following block diagram. As shown in Figure 20, since the rec command of the device uses the TCP/IP protocol, it is necessary to fill in the physical port information of TCP/IP, while the c1 command uses the serial port protocol, so only the port needs to be filled in. After setting a command, you need to click "OK" once, and click Save when all the command configurations are completed.

After the above configuration of the simulation device is completed, the configuration module 100 adds the configured simulation device to the prototype device library, thereby completing the configuration of the prototype device library.

After the configuration module 110 completes the configuration of the prototype device library, the saving module 120 saves the above prototype device library.

In one embodiment of the present invention, the saving module 120 saves the prototype device library in XML format.

The control module 130 receives the simulation control command, and controls the prototype device library to perform corresponding simulation actions according to the simulation control command.

As shown in FIG. 21 , first, the control module 130 receives an external simulation control command, and selects a corresponding simulation device in the prototype device library according to the received simulation control command. Then check for conflicting working ports within the emulated device.

If there is no conflict between the working ports of the simulation device, the control module 130 sends the simulation control command to the corresponding simulation device through the communication management interface; otherwise, the simulation ends.

Specifically, when there is no conflict between the working port of the simulated device, the control module 130 controls the simulated device to start running, reads the parameters of the simulated device into the hash table, and initializes the working port of the simulated device. After initialization, bind the received simulation control command with the corresponding working port. According to the trigger event of the control command, the corresponding coupling action processing is performed, and the coupling action is executed by analyzing the data until all the control commands are completed, then the simulation ends.

When the configuration of the communication port in Figure 20 is correct, click Save, and a window will pop up to prompt the user that the device has been started, and the running interface is shown in Figure 22. After starting, you can receive and send commands and perform related actions. At the same time, all parameter information configured by the device will be listed in the table on the right, and the status of these parameters can be refreshed in time. Similarly, if you need to stop or exit the device, just click the relevant menu on the right button.

The simulation equipment operation simulation of the prototype device library mainly completes the dynamic simulation function of the equipment. The simulated device receives the data and performs corresponding actions to change the parameter value of the device, and the system interface dynamically displays the parameter value of the device in the form of a table.

The device for constructing and managing a prototype device library according to an embodiment of the present invention can be configured as a related device that needs to be simulated according to a simulation requirement. After configuration, the prototype device library can be applied to the simulation devices of different manufacturing equipment for equipment control software testing, and the properties of the prototype device library can be flexibly configured according to the different methods of using the hardware in different projects to meet different project requirements.

Although the embodiments of the present invention have been shown and described, those skilled in the art can understand that various changes, modifications and substitutions can be made to these embodiments without departing from the principle and spirit of the present invention. and modifications, the scope of the invention is defined by the appended claims and their equivalents.

Claims (7)

1. the structure in an antetype device storehouse and management method is characterized in that, comprise the steps:

Create the antetype device storehouse, and dispose the parameter in said antetype device storehouse, wherein,

Said establishment antetype device storehouse comprises: create emulator, wherein, said antetype device storehouse comprises a plurality of emulators;

The parameter in the said antetype device of said configuration storehouse comprises: the parameter that disposes said emulator; Wherein, The parameter of said emulator comprises: the action of the attribute of said emulator, the order of said emulator, said emulator and the PORT COM of said emulator, wherein

The order of said configuration emulator also comprises: the command name, order direction of transfer and the command context that dispose said emulator; Preserve the order of said emulator, the order of said emulator is corresponding one by one with agreement, and said command context comprises: protocol name; The protocol address scope; Protocol address is used to the physical address or the port numbers of specifying said order to send; Command specification is used to explain said order; The command property number, the attribute number of the said emulator that comprises in the said order; The device attribute of order is used for the attribute of the said emulator of said order is specified,

The action of said configuration emulator also comprises: the denomination of dive that disposes said emulator;

The order of the said emulator of said configuration; Comprise: from the order of said emulator, choose the order that the action with said emulator is coupled; After the order of the said emulator of configuration, also comprise: the number of steps that disposes the action of said emulator; According to said number of steps, dispose the device motion type of each step;

Preserve the action of said emulator;

The PORT COM of said configuration emulator also comprises: according to the order of said emulator, and the order corresponding physical port of configuration and said emulator;

The emulator that configuration is accomplished adds in the antetype device storehouse;

Configuration is preserved said antetype device storehouse after accomplishing; And

The order of reception Simulation Control, and control said antetype device storehouse according to said Simulation Control order and carry out corresponding simulated actions, control antetype device storehouse is carried out corresponding simulated actions and is also comprised:

According to receiving the Simulation Control order, choose corresponding emulator in the said antetype device storehouse;

Whether the working port of checking said emulator conflicts;

If the working port of said emulator does not have conflict, then will read the parameter of said emulator, and said Simulation Control order will be sent to corresponding emulator through the telecommunication management interface, otherwise finish emulation;

Control said emulator according to the corresponding simulated actions of said Simulation Control command execution.

2. structure as claimed in claim 1 and management method is characterized in that, the attribute of configuration emulator also comprises:

Dispose Property Name, attribute type, attribute maximal value, attribute minimum value and the attribute acquiescence initial value of said emulator; With

Preserve the attribute of said emulator.

3. structure as claimed in claim 1 and management method is characterized in that, said device motion type comprises: order behavior, operation condition, delay wait, Changing Pattern and return message.

4. the structure in an antetype device storehouse and management devices is characterized in that, comprising:

Configuration module is used to create the antetype device storehouse, and disposes the parameter in said antetype device storehouse, wherein,

Said configuration module is created the antetype device storehouse and comprised: create emulator, wherein, said antetype device storehouse comprises a plurality of said emulators;

The parameter in the said antetype device of said configuration module configures storehouse comprises: the parameter that disposes said emulator; The parameter of wherein said emulator comprises: the action of the attribute of said emulator, the order of said emulator, said emulator and the PORT COM of said emulator; Wherein

The order of said configuration module configures emulator also comprises: the command name, order direction of transfer and the command context that dispose said emulator; Preserve the order of said emulator; The order of wherein said emulator is corresponding one by one with agreement, and said command context comprises: protocol name; The protocol address scope; Protocol address is used to the physical address or the port numbers of specifying said order to send; Command specification is used to explain said order; The command property number, the attribute number of the said emulator that comprises in the said order; The device attribute of order is used for the attribute of the said emulator of said order is specified;

The action of said configuration module configures emulator also comprises: the denomination of dive of the said emulator of said configuration module configures;

The order of the said emulator of said configuration module configures; Comprise: from the order of said emulator, choose the order that the action with said emulator is coupled; Said configuration module also comprises: the number of steps of the action of the said emulator of said configuration module configures after the order of the said emulator of configuration; According to said number of steps, the device motion type of said each step of configuration module configures; Said configuration module is preserved the action of said emulator;

The PORT COM of said configuration module configures emulator also comprises: according to the order of said emulator, and the order corresponding physical port of said configuration module configures and said emulator,

The emulator that said configuration module is accomplished configuration adds in the antetype device storehouse;

Preserve module, be used to preserve the antetype device storehouse after the configuration; And

Control module; Be used to receive the Simulation Control order; And control said antetype device storehouse according to said Simulation Control order and carry out corresponding simulated actions; Said control module control antetype device storehouse is carried out corresponding simulated actions and is also comprised: according to receiving the Simulation Control order, choose corresponding emulator in the said antetype device storehouse; Whether the working port of checking said emulator conflicts; If the working port of said emulator does not have conflict, then will read the parameter of said emulator, and said Simulation Control order will be sent to corresponding emulator through the telecommunication management interface, otherwise finish emulation; Control said emulator according to the corresponding simulated actions of said Simulation Control command execution.

5. structure as claimed in claim 4 and management devices is characterized in that, the attribute of said configuration module configures emulator also comprises:

The Property Name of the said emulator of said configuration module configures, attribute type, attribute maximal value, attribute minimum value and attribute acquiescence initial value; With

Said configuration module is preserved the attribute of said emulator.

6. structure as claimed in claim 4 and management devices is characterized in that, said device motion type comprises:

Order behavior, operation condition, delay wait, Changing Pattern and return message.

7. structure as claimed in claim 4 and management devices; It is characterized in that; The structure and the management devices in said antetype device storehouse also comprise subscriber interface module; Said subscriber interface module, the parameter of be used to import said configuration module, preserving module and control module implementation, and with interface form demonstration execution result.

Images