JP4784754B2 - Control system setting device - Google Patents

Description

  The present invention relates to a control system setting device for setting a control system including a programmable controller (PLC) and other control devices and a network.

  The network of the control system is composed of a plurality of layers, and many types of networks are used. Depending on the network type, the network type (master & slave type, peer-to-peer type, etc.), the number of connected devices, communication protocol, communication command system, etc. are different, and the appropriate network type is selected according to the application. .

  When building a control system and starting operation, it is necessary to select the type of network used for the control system, select an appropriate device constituting the control system, and set appropriate parameters for each device. Also, similar work may be required when changing or maintaining the control system.

  When setting the devices constituting the control system, a computer installed with a setting program (setting program), particularly a small or portable computer such as a personal computer is used.

  In the FA (Factor Automation) field, in recent years, it is common to perform setting and information acquisition from a tool on a PC to a control device to construct and maintain a system. In addition, with the advancement and diversification of control devices, the types of tools on the PC are increasing, and the number of files associated with the tools is constantly increasing.

  As the number of tools and related files increase, the effort and man-hours for control device designers and maintainers to manage these files increase, and incorrect configuration file transfer and storage errors due to management errors frequently occur. It is like that.

In order to solve such a problem, an integrated project management tool disclosed in Patent Document 1 has been conventionally provided. In the invention disclosed in Patent Document 1, when a FA system is constructed using a large number of PLCs and networks, a large number of programmings and settings are required. It solves the problem of confusing or forgetting file names. Specifically, using an off-the-shelf drawing software, etc., the hardware configuration is stored separately as a drawing, and an integrated project that makes it easy to visually and intuitively start the programming software and setting software used in the system Based on the premise of a management tool, it is possible to centrally manage the addresses to the created file and its related home page with a single file, and to transfer all information to a third party.
JP2003-2848548

  In the invention disclosed in Patent Document 1, the control device system is actually configured for the purpose of providing one of the setting file utilization methods, such as transferring all information to a third party. There has been no improvement in operability at the time of programming or debugging to create a setting file for each device.

  An object of the present invention is to provide a control system setting device that can uniquely specify a setting file related to a control device or a network on a control device system and can be used immediately.

A control system setting device according to the present invention is (1) a control system setting device used for setting a control system by connecting to a control system including a plurality of devices connected by a network. Configuration management application for creating a configuration diagram, storage means for storing a setting file consisting of parameters and / or programs set in the device , a dedicated tool for creating / updating the setting file, and storage in the storage means associating a storage location information for specifying a storage location in the storage means of the held the set files, and tools name of the special tools, and unique ID assigned to the device corresponding to the configuration file, the And a work memory for holding related files. When the configuration management application selects a figure representing a device on the network configuration diagram for which a configuration file has been created, the configuration management application accesses the work memory and displays the configuration file before the configuration file for the selected device. The storage location information, tool name, and ID are acquired, the acquired storage location information, file name, and ID are passed to the dedicated tool specified by the tool name, and the processing for starting the dedicated tool is executed. It has the function to do. Further, the dedicated tool that stores the setting file in the storage unit has a function of setting storage location information of the stored setting file in the work memory, and the storage unit includes a graphic indicating the same device. A plurality of different setting files associated with the plurality of setting files can be stored, a master flag is set for each related file on the work memory corresponding to the plurality of setting files, and any one master of the related files is set. The storage location information passed to the dedicated tool by the configuration management application when the flag is set to ON and the graphic is selected is assumed to be stored in a related file whose master flag is ON.

The graphic corresponds to the virtual icon I in the embodiment. The storage means corresponds to the storage 5 of the embodiment. The work memory corresponds to the data storage unit 15 constituting the database of the embodiment. In the present invention, the related file for the device is specified. However, the related file for the network is stored in the work memory as in the embodiment, and the network stored in the storage is stored in accordance with the storage location information of the related file. The setting file may be read out or a dedicated tool for the network may be activated.

In the present invention, a common work memory (storage) is arranged, the storage location information of the setting file for the tool associated with the device is shared by a unique ID provided by the work memory , and the user specifies the storage location information. Launch related tools and files without any problems. A work memory is prepared on the computer, and the ID for identifying the device in the work memory and the storage location information of the related setting file on the storage for storing the setting file of the device are held on the work memory and configured. By associating with the graphic representing the device of the management application, the user can simply start the related file from the graphic on the configuration management application and load the configuration file according to the storage location information of the configuration file stored in the work memory. The dedicated tool can be started according to the tool name . Furthermore, although the storage location information is stored in the work memory of the main memory, the contents of the actual setting file are stored in the storage, so the capacity of the work memory does not have to be so large.

The storage means can store a plurality of different setting files associated with a figure indicating the same device, and a master flag is set in each related file on the work memory corresponding to the plurality of setting files. The storage location information that the configuration management application passes to the dedicated tool when the master flag of any one of the related files is set to ON and a graphic is selected is the one stored in the related file with the master flag ON. As a result, for example, a plurality of files having different versions can be stored as setting files for the same device, which is suitable for setting work and debugging. Since the setting file to be activated is specified as one file whose master flag is ON, the dedicated tool activation process can be performed without any problem.

(2) The plurality of setting files for the same device are the setting file of the update source and the setting file after the update, and are set so that the master flag of the related file of the setting file after the update is turned on. It is good to do so.

(3) Furthermore, it is preferable to provide means for switching ON / OFF of master flags of a plurality of related files for the same device.
(4) The work memory may be set on a main memory of a computer constituting the control system setting device.
(5) The dedicated tool that stores the setting file in the storage unit may have a function of setting storage location information of the stored setting file in the work memory. In the embodiment, when the dedicated tool stores the setting file in the storage, the storage location information is passed to the database and the database adds to the related file. However, the dedicated tool may write the data to the database itself. .

(6) Configuration management application, if the graphic representing the equipment diagram network configuration is deleted, deletes the relevant file stored in the work memory based on an ID corresponding to the deleted graphic, work A function for deleting the setting file stored in the storage according to the storage location information stored in the memory may be provided. The actual deletion may be performed directly by the configuration management application, or may be performed by the work memory based on a request from the configuration management application as in the embodiment. In this way, when a configuration management application graphic is deleted, the setting file associated therewith can be easily deleted.

(7) When a graphic representing a device on the network configuration diagram is copied, the configuration management application stores the storage according to the storage location information of the related file in the work memory associated with the ID corresponding to the copied graphic. It is preferable to have a function of copying the setting file stored in the storage location information of the copied new setting file to the work memory as a new related file. The setting file associated with the duplicate is also duplicated, and the physical control device can be easily duplicated.

  In the present invention, a setting file related to a control device or network on the control device system can be uniquely specified and can be used immediately.

  As shown in FIG. 1, the control system setting device 10 and the control device 1 are connected to a network 2, and data is transmitted / received via the network 2. The control device 1 includes a PLC, a robot controller, a CNC (Computerized Numeric Controller), and the like. Although not shown, the control system is connected to the control device 1 with sensors, various I / Os and other devices directly or via a network.

  The control system setting device 10 creates a network configuration diagram of the FA network, sets parameters for the devices and devices constituting the network, and downloads programs. The control system setting device 10 is a personal computer in which an application program and setting data for performing the above processing are installed. In this embodiment, the control system setting device 10 is connected to each device / equipment via a network, but may be directly connected to each device / equipment using a serial interface such as RS-232C. .

  The software configuration of the control system setting device 10 includes an application layer and a middleware layer. The middleware layer includes communication middleware 14 that communicates with other control devices 1 and the like connected to the network 2, and a data storage unit (database middleware) 15 that accesses the storage 5 and reads / writes data. The application layer includes a configuration management application 11 for managing the configuration of the control device system, a communication interface 12 for performing communication between the configuration management application 11 and the communication middleware 14, and the configuration management application 11 and data storage. And a database interface 13 for performing communication with the unit 15.

  Each of the interfaces 12 and 13 issues an operation request to lower layer software (middleware) in accordance with a request of the application, and attaches the result.

  The data storage unit 15 operates on the RAM and has a function as a work memory when each application operates. The database includes a database interface 13 which is an access interface unit and a data storage unit 15 (hereinafter, the database indicates both the database interface 13 and the data storage unit 15). The data storage unit 15 operates under the application and stores data such as the model, communication settings, network number, node number, and unit number of the control device and network.

  The storage 5 is a storage device for storing data (application files and database files) stored in the data storage unit 15 and is configured by an internal hard disk of an personal computer, an external removable disk, or the like.

  FIG. 2 shows a hardware configuration of the control system setting device 10. The control system setting device 10 includes a CPU 10a, a RAM / HDD 10b, a ROM / HDD 10c, and a communication control unit 10d as internal devices. These internal devices are connected to the bus 10e, and send and receive necessary data via the bus 10e. The CPU 10a is a processor that executes an installed application program. The RAM / HDD 10b is a temporary storage unit, and is used as a work area (IP address work table or the like), for example, when the CPU 10a performs operations. The ROM / HDD 10c constitutes a storage device, and the application program (software execution module) is stored in the storage device. The main memory in which the database is set corresponds to the RAM / HDD 10b. The database is stored in the HDD when the apparatus is not in operation, and is expanded and used in the RAM when the apparatus is in operation. The communication control unit 10d is used to control communication via a network such as the Internet. This is the same as the hardware configuration of a general PC.

  Hereinafter, functions of each processing unit will be described while explaining procedures for executing various actual processes. First, the start-side process for creating a database entry will be described with reference to FIGS. In FIG. 3, a symbol W is a display screen displayed on the display device of the control system setting device 10, and shows a state where a network configuration diagram is created by executing the configuration management application 11. The following processes (1) to (7) correspond to the same numbers in FIG.

  The data storage unit 15 has a project for group management of data information. This project is created, for example, for each network configuration diagram, and devices and networks that configure the network configuration diagram are linked in the lower level. Projects, devices, and networks are created as folders, respectively, and their properties (attributes) are held in XML as files (see FIGS. 5 and 6). As shown in FIG. 4, the data storage unit 15 stores each folder as a tree structure on the memory, and writes it in a file when the project is stored.

  (1) The user Y starts the configuration management application 11 for managing the configuration of the control device system. This activation process is realized by a process (such as clicking an icon) similar to the activation of application software in a normal personal computer.

  (2) The started configuration management application 11 connects to the data storage unit 15 via the database interface 13 (FIG. 7A: S1). The configuration management application 11 designates a project name that identifies the project to be processed input by the user. That is, the configuration management application 11 passes the project name to the database storage unit 15 (FIG. 7A: S2). The user inputs a project name by operating an input device such as a keyboard or a pointing device of a personal computer in which the configuration management application 11 is installed.

  When the data storage unit 15 acquires the project name from the configuration management application 11 (FIG. 7B: S3), the data storage unit 15 determines whether there is a project with the acquired project name in the data storage unit 15 (FIG. 7). (B): S4). If the designated project exists, the data storage unit 15 opens the project (FIG. 7B: S6), and creates a new project if it does not exist (FIG. 7B: S5). .

  (3) The user uses the configuration management application 11 to create on the display screen of the display device of the personal computer a network configuration diagram composed of the control device configuring the control system and the virtual icon I of the network. As a function of the configuration management application 11 for creating this network configuration diagram, for example, the invention disclosed in Japanese Patent Laid-Open No. 2003-288458 can be used. That is, the configuration diagram created on the display screen is not simply configured with image data, but the parts indicating each device and each network constitute a virtual icon I. When the virtual icon I is selected (clicked or the like), processing for setting and storing the device and network and reading the set data can be executed. Specific processing is as follows.

  (4) The user selects the virtual icon I on the configuration management application 11 and selects a menu for setting a control device and a network or starting a tool for collecting information (hereinafter, a dedicated tool). The selection of the virtual icon I is performed, for example, by operating an input device (pointing device or the like) of a personal computer in which the configuration management application 11 is installed, and setting the pointer displayed on the display screen on the target virtual icon I. This is done by clicking on the pointing device. Then, by performing such a click, the configuration management application 11 displays a menu list. Further, the configuration management application 11 recognizes that the virtual icon I has been selected, thereby acquiring a device (including a network) designated by the user (FIG. 7C: S7). FIG. 3 shows a state in which the virtual icon I having the device name “device 1” is selected and the dedicated tool is activated.

  (5) The configuration management application 11 requests the database interface 13 to create an entry for the control device or network related to the selected virtual icon (device connection request) (FIG. 7 (c): S8). The entry includes the type, communication setting, network number, node number, and unit number. The database interface 13 creates the above entry in the data storage unit 15.

  (6) If the acquired device is a new device, the database interface 13 attaches a unique ID (“ID1” in FIG. 3) to the entry created in the process (5) and stores it in the data storage unit 15.

  (7) The database interface 13 returns the ID (device ID) assigned to the device that has requested connection to the configuration management application 11. The configuration management application 11 stores the device ID returned from the held device interface 13 in the device management table in association with the device name of the corresponding device. Actually, the configuration management application 11 registers the device name in the device management table when the virtual icon is arranged and the device name is set in the creation of the network configuration diagram (process (3)), and later. A device ID may be added, or when the device ID is acquired, the device ID and the associated device name may be combined and stored in the device management table. In FIG. 3, the device name “device 1” set by the configuration management application and the device ID “ID1” generated by the database interface 13 are associated with each other and stored in the device management table. This data management table is stored in a work memory provided in the RAM / HDD 10c, for example.

  The functions on the database side for executing the processes (5) to (7) are as shown in the flowchart of FIG. When the device interface 13 acquires the device name to be connected from the configuration management application 11 (FIG. 7 (d): S9), it is determined whether or not a corresponding device exists in the data storage unit 15 (FIG. 7 (d). ): S10). If no device exists in the data storage unit 15, the database creates a new device in the project of the data storage unit 15, generates a unique device ID, and stores the generated device ID in the new device. It returns to the configuration management application 11 (FIG. 7 (d): S11). On the other hand, if a device already exists in the data storage unit 15, the device ID of the device is acquired, and the acquired device ID is returned to the configuration management application 11 (FIG. 7 (d): S12).

  In the device database schema described in XML stored in the data storage unit 15 shown in FIG. 6, “CX-Integrator” (tool name) is registered as the application that created the device, and as the device ID (key) “214430303031” is registered, and “C1” is registered as the device name (name). Thus, by setting a unique device ID, the device can be uniquely specified in the network configuration diagram, and by setting the device name, the user can easily understand. As shown in FIG. 5, for each project, a uniquely set project key (215030303031) and project name (new project 1) are stored, and the project key is uniquely specified by the project key. The project name makes it easier for the user to recognize.

  Next, processing on the activated side when the dedicated tool is activated will be described based on FIGS. 8 to 10. The following processes (1) to (3) correspond to the same numbers in FIG.

  (1) When the user selects the activation menu M for the virtual icon I displayed on the work window W of the configuration management application 11, the configuration management application 11 uses the project name and device ID for the virtual icon I for exclusive use. Pass to the tool and start the dedicated tool.

  (2) The activated dedicated tool is connected to the data storage unit 15 via the database interface 13 using the project name and device ID received from the configuration management application 11.

  (3) The database interface 13 determines whether or not the project name and device ID passed together with the connection request are in the data storage unit 15, and returns the determination result to the dedicated tool.

  The functions of the dedicated tool and the database for executing the processes (1) to (3) on the invoked side are as shown in the flowcharts of FIGS. In any figure, (a) is a function of a dedicated tool, and (b) is a function of a database.

  The activated dedicated tool receives the project name and device ID from the configuration management application 11 (FIG. 9A: S15). Then, the dedicated tool first passes the received project name to the database interface 13 and makes a project connection request (FIG. 9A: S16). Then, the dedicated tool waits for a response from the database interface 13 and determines whether or not the response is an error (FIG. 9A: S17). In the case of an error, a startup error process is executed (FIG. 9A: S18). This activation error processing includes, for example, displaying an error message on the work window W1 of the dedicated tool. On the other hand, if no error is returned from the database interface 13, the process proceeds to the next process. Here, the flowchart of FIG. 10A is executed.

  Upon receiving the project connection request shown in FIG. 9A, the database interface 13 executes the flowchart shown in FIG. That is, the database interface 13 acquires the project name from the dedicated tool (FIG. 9B: S20), and determines whether or not a project having the acquired project name exists in the data storage unit 15 (FIG. 9). (A): S21). If there is no corresponding project in the database 15, the database interface 13 notifies the dedicated tool of an error (FIG. 9B: S23). On the other hand, when there is a project corresponding to the database 15, the database interface 13 opens the project (FIG. 9B: S22).

  When the branch determination in process step S17 is No, the dedicated tool passes the device ID to the database interface 13 and makes a device connection request (FIG. 10A: S24). The dedicated tool waits for a response from the database interface 13 and determines whether the response is an error (FIG. 10A: S25). In the case of an error, startup error processing is executed (FIG. 10 (a): S26). This activation error processing includes, for example, displaying an error message on the work window W1 of the dedicated tool. On the other hand, if no error is returned from the database interface 13, the process proceeds to the next process.

  The database interface 13 that has received the device connection request shown in FIG. 10A executes the flowchart shown in FIG. That is, the database interface 13 acquires the device ID from the dedicated tool (FIG. 10B: S27), and whether a device having the acquired device ID exists in the data storage unit 15 (project opened in S22). It is determined whether or not (FIG. 10A: S28). If the corresponding device ID does not exist in the database 15, the database interface 13 notifies the dedicated tool of an error (FIG. 10B: S30). On the other hand, when the device ID corresponding to the data storage unit 15 exists, the database interface 13 returns a connection success to the dedicated tool (FIG. 10B: S29).

  Next, the save process on the invoked side will be described with reference to FIGS. The following processes (1) to (4) correspond to the same numbers in FIG.

  (1) The user selects save of the setting file on the dedicated tool and saves the file. The file to be saved includes a device management table. A dialog D for inquiring the file name and storage position to the user is displayed. The user uses this dialog D to input a file name and a storage location.

  (2) The dedicated tool passes the file name (including the storage location) input via the dialog D to the database interface 13 and the device ID to be stored.

  (3) The database interface 13 has a file name (including the storage location: c: in the example) under the control device or network ID ("ID1" in the figure) indicated by the device ID passed to the data storage unit 15. \ Temp \ file1.cxp). At this time, a master flag (a flag for setting a default activation file) is set (MASTER = ON) as in the storage location.

  (4) The dedicated tool stores the project name (save location) in a file (eg, c: \ Project \ Project1.cop) and the user ends the dedicated tool.

  The functions of the dedicated tool and the database for executing the processes (1) to (4) on the invoked side are as shown in the flowchart of FIG. In the figure, (a) is the function of the dedicated tool, and (b) is the function of the database.

  The dedicated tool passes the file storage location information designated by the user to the database interface 13 together with the device ID (S31). The dedicated tool waits for a response from the database interface 13 and determines whether the response is an error (S32). In the case of an error, a storage error process is executed (S33). This save error processing includes, for example, displaying an error message on the work window W1 of the dedicated tool. On the other hand, if no error is returned from the database interface 13, the storage process is terminated (S34).

  The database interface 13 acquires the file storage location and device ID from the dedicated tool (S35), and determines whether the acquired device ID exists in the data storage unit 15 (S36). If the corresponding device ID does not exist in the database 15, the database interface 13 notifies the dedicated tool of an error (S38). On the other hand, when the corresponding device ID exists in the data storage unit 15, the database interface 13 adds file storage information to the device ID (S37).

  Next, the save / end process on the start side will be described with reference to FIGS. The following processes (1) to (9) correspond to the same numbers in FIG.

  (1) The user ends the configuration management application 11. As shown in the figure, this termination process is executed by the normal termination process of the software, such as clicking the “Exit” field in the startup menu consisting of a pull-down list or clicking the “x” in the upper right of the work window W. The The configuration management application 11 that has recognized the termination process executed by the user makes a termination request to the database interface 13.

  (2) Upon receiving the termination request, the database interface 13 asks the user for the storage location. That is, a dialog D for inputting a storage location is displayed.

  (3) Using this dialog D, the user inputs a file name and a storage location ("c: \ temp \ project.cxp" in FIG. 13).

  (4) The database interface 13 adds the storage location input in the process (3) to the storage location information (FIG. 5) of the project data in the data storage unit 15.

  (5) The database interface 13 writes the data in the data storage unit 15 as a folder and an XML file on the storage 5.

  (6) The database interface 13 compresses the folder and file into one file.

  (7) The database interface 13 stores the database compressed file with the same name as the project in the storage location added in the process (4).

  (8) The database interface 13 creates an XML file that holds a summary of the database compressed file (FIG. 14), and stores it in the same location as the compressed file with the same name as the project. The summary consists of information that allows the contents of the compressed file to be understood without being decompressed, and includes at least the project name and the project key.

  (9) The database interface 13 deletes the uncompressed folder and XML file stored in the storage 5.

  Next, the restart process will be described with reference to FIGS. The following processes (1) to (5) correspond to the same numbers in FIG.

  (1) The user again selects the previous control device or network virtual icon I in the configuration management application 11 (in the figure, selects “device 1: ID1”), and an associated file (hereinafter referred to as a related file). Select the menu for starting up (click “Start dedicated tool” in the figure).

  (2) The configuration management application 11 passes the associated device ID (ID1) to the database interface 13 and makes a search request for the file name (including the storage location) of the related file.

  (3) The database interface 13 accesses the data storage unit 15, searches for the file name, and manages the configuration of the detected file name (including the storage location ("c: \ temp \ file.cxp" in the figure)) of the related file detected. Return to application 11.

  (4) The configuration management application 11 passes the project name, device ID, and related file name (including the storage location) to the dedicated tool, and activates the dedicated tool.

  (5) The dedicated tool is activated with the relevant file name. That is, the dedicated tool recognizes the storage location from the acquired related file name, accesses the storage 5 based on the recognized storage location information, and reads information about the device ID.

  The configuration management application and the processing function of the dedicated tool execute the flowchart shown in FIG. That is, the configuration management application 11 passes the project name to the database interface (S40), and then passes the device ID to the database interface (S42). The configuration management application 11 determines the presence / absence of an error every time each process is executed (S41, S43). If there is an error, the configuration management application 11 executes a startup error process (S42, S44). After passing each data to the data interface, the configuration management application 11 acquires file position information for the device specified by each data from the database interface (S46). If the acquisition fails (S47 is Yes), the configuration management application 11 executes a startup error process (S48). If the acquisition is successful, the configuration management application 11 passes the project name, device name, and file location information to the dedicated tool (S49). .

  The dedicated tool receives the project name, device ID, and file location information (storage location) from the configuration management application 11 (S151), accesses the storage based on the received information, and reads the file stored in the file storage location (S152). ). The dedicated tool determines whether there is an error such as the corresponding file is missing or damaged (S153), and if there is an error, executes a startup error process (S154). The dedicated tool opens the normally read file and displays it on the screen (S155).

  Next, the startup file switching process will be described with reference to FIGS. The following processes (1) to (9) correspond to the same numbers in FIG. As described above in the restart process (FIGS. 15 and 16), the virtual icon I of the control device or the network can be selected to activate the related file. When the related file (version 1) of the virtual icon is read and corrected, and the corrected related file (version 2) is saved, there is a case where it is desired to save the related file (version 1) before correction. Therefore, in the present embodiment, it is allowed to save a plurality of types of related files for the same virtual icon I. When a plurality of types of related files are stored in this way, it is necessary to specify one related file to be activated when the virtual icon I is selected and the restart process is executed. Specifically, a master flag is set for each file name, and when there are a plurality of related files related to the same virtual icon, the master flag of one of the related files is turned ON, and the other related files Set the file master flag to OFF. When the virtual icon is selected and the restart process is executed, the configuration management application 11 starts the related file whose master flag is ON. The startup file switching process manages such a master flag and controls switching of related files (startup files) to be started. Specifically, it is as follows.

  (1) The user again selects the control device or network virtual icon I in the configuration management application 11 (in the figure, selects “device 1: ID1”), and selects a menu for acquiring or switching related files.

  (2) The configuration management application 11 passes the device ID of the selected virtual icon I to the database interface 13 according to the contents of the menu selected in the process (1), and the file name (including the storage location) of the related file. Issue a request to get all.

  (3) The database interface 13 acquires a list of file names (including storage locations) of related files from the data storage unit 15 and returns it to the configuration management application 11.

  (4) The configuration management application 11 shows a related file list to the user. In this example, a “file list dialog” separate from the work window W of the component application 11 is output and displayed.

  (5) The user selects a file to be activated from the related file list. This selection is performed, for example, when the user operates a pointing device of a personal computer on which the configuration management application 11 is mounted and clicks one of the files listed in the file list dialog. In FIG. 17, “c: ¥ temp ¥ file2.cxp” is selected.

  (6) The configuration management application 11 issues a master file switching request to the database interface 13 together with the file name (including the storage location) of the file selected by the process (5).

  (7) The database interface 13 turns on the master flag of the file name passed to the storage location stored in the data storage unit 15, and turns off the master flag of the file name that was originally turned on. As a result, the file with the master flag ON is activated for subsequent activation. In FIG. 17, the master flag “c: ¥ temp ¥ file2.cxp” is turned ON, and the master flag “c: ¥ temp \ file.cxp” is turned OFF.

  (8) The configuration management application 11 passes the device ID of the selected virtual icon and the selected related file name to the dedicated tool, and activates the dedicated tool.

  (9) The dedicated tool activates the acquired related file name.

  The functions of the configuration management application and the database for executing the processes (1) to (9) are as shown in the flowcharts of FIGS. In each figure, (a) is the function of the dedicated tool, and (b) is the function of the database.

  The configuration management application 11 acquires the device name of the virtual icon I selected by the user (FIG. 18 (a): S51). Next, the configuration management application 11 acquires a device ID corresponding to the device name with reference to the device management table, and passes an information list acquisition request together with the acquired device ID to the database interface 13 (FIG. 18A: S52). .

  Upon receiving the information list acquisition request together with the device ID from the configuration management application (FIG. 18B: S53), the database interface 13 determines whether the device ID exists in the data storage unit 15 (FIG. 18 ( b): S54). When the accepted device ID exists in the data storage unit 15, the database interface 13 returns the information list of the file added to the device ID to the configuration management application 11 (FIG. 18B: S55). If the received device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the configuration management application 11 (FIG. 18B: S56).

  When the information list is returned from the database interface 13, the configuration management application 11 displays the list and acquires file position information designated by the user (FIG. 19A: S61). Turn on the master flag. The configuration management application 11 passes the device ID and the acquired file position information to the database interface 13 and issues a master file switching request (FIG. 19A: S62).

  When the database interface 13 acquires the master file switching request together with the device ID (FIG. 19 (b): S63), it determines whether or not the device ID is in the database storage unit 15 (FIG. 19 (b): S64). . If the device ID exists in the database storage unit 15, the database interface 13 turns off the master flag in the file position information of the file whose master flag is currently ON for the device ID (FIG. 19B: S65). ), The master flag in the received file position information is set to ON (FIG. 19B: S67). If the received device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the configuration management application 11 (FIG. 19B: S66).

  Next, device deletion processing will be described with reference to FIGS. The following processes (1) to (5) correspond to the same numbers in FIG.

  (1) The user selects and deletes the virtual icon I of the control device or network that has been created by the configuration management application 11. In this deletion process, after the user operates a personal computer input device (pointing device) on which the configuration management application 11 is mounted and clicks the pointer over the corresponding virtual icon to select a virtual icon, This is done by pressing the derate key.

  (2) The configuration management application 11 that has recognized the deletion process executed by the user makes a deletion request to the database interface 13. That is, the configuration management application 11 passes a device ID corresponding to the selected virtual icon to the database interface 13 and issues a file deletion request to the database interface 13.

  (3) The database interface 13 deletes the file according to the file location storage information of the device ID stored in the data storage unit 15.

  (4) The database interface 13 deletes the device with the received device ID from the data storage unit 15.

  (5) The configuration management application 11 deletes the device name and device ID from the device management table and removes the association between the device name and the device.

  The functions of the configuration management application and the database for executing the processes (1) to (5) are as shown in the flowchart of FIG. In the figure, (a) is the function of the configuration management application, and (b) is the function of the database.

  The configuration management application 11 acquires the device name of the virtual icon selected by the user (S71). Next, the configuration management application 11 acquires a device ID corresponding to the device name with reference to the device management table, and passes a file location information deletion request together with the acquired device ID to the database interface 13 (S72).

  When the database interface 13 receives the deletion request together with the device ID from the configuration management application (S73), the database interface 13 determines whether the device ID exists in the data storage unit 15 (S74). If the accepted device ID exists in the data storage unit 15, the database interface 13 deletes the file position information added to the device ID (S75). If the accepted device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the configuration management application 11 (S76).

  Next, device copy processing will be described with reference to FIGS. The following processes (1) to (6) correspond to the same numbers in FIG.

  (1) The user selects and copies a control device or network virtual icon I created in the configuration management application 11. The copy process is performed, for example, by performing a process similar to the selection of the virtual icon in the above-described deletion process, selecting the copy source virtual icon I, and then inputting a predetermined command. The user names the copied device. In FIG. 22, the device name “device 2” is assigned to the copied device.

  (2) The configuration management application 11 passes the device ID of the selected copy source device (“ID1” in FIG. 22) and the name of the copy destination device named by the user (“device 2” in FIG. 22) to the database interface 13. Issue a device copy request.

  (3) The database interface 13 copies the file according to the file location storage information on the acquired device ID stored in the data storage unit 15. In the example of FIG. 22, the database interface 13 acquires “c: ¥ temp ¥ file2.cxp” as the file location storage information whose device ID is ID1, and copies the corresponding file stored in the storage 5 based on the acquired information. . As a result, “c: ¥ temp ¥ copy of file2.cxp” is created.

  (4) The database interface 13 creates an entry for a new device in the data storage unit 15 with the copy destination device name (device 2). The database interface 13 assigns a new device ID (“ID2” in FIG. 22). The file location storage information on the new device is updated with the storage location information (“c: ¥ temp ¥ copy of file2.cxp” in FIG. 22) of the file copied in the process (3).

  (5) The database interface 13 returns a new device ID (“ID2” in FIG. 22) to the configuration management application 11.

  (6) The configuration management application 11 updates the device management table. That is, the configuration management application 11 adds “device name and device ID” related to the virtual icon generated by copying to the device management table.

  The functions of the configuration management application 11 and the database for executing the processes (1) to (6) are as shown in the flowchart of FIG. In the figure, (a) is the function of the configuration management application, and (b) is the function of the database.

  The user copies the virtual icon (S81). That is, the configuration management application 11 creates a copy of the virtual icon selected by the user and displays it at a predetermined position in the work window. The configuration management application 11 acquires the device name associated with the virtual icon before copying specified by the user and the device name set for the virtual icon after copying (S82). The configuration management application 11 refers to the device management table, acquires the device ID corresponding to the device name of the virtual icon before copying, and passes the device copy information together with the acquired device ID to the database interface 13 (S83).

  When the database interface 13 receives the replication information together with the device ID from the configuration management application 11 (S84), the database interface 13 determines whether the device ID exists in the data storage unit 15 (S85). If the accepted device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the configuration management application 11 (S86). When the accepted device ID exists in the data storage unit 15, the database interface 13 copies the device information added to the device ID (S87). The database interface 15 creates a copy of the file in stage 5 in the file position information on the stage 5 (S88), and updates the file position information with the copied file name (S89).

  Next, the double-click activation process will be described with reference to FIGS. This double-click activation process is for enabling the activated dedicated tool to be activated directly. That is, in each process described above, the configuration management application 11 activates a necessary dedicated tool according to the selected virtual icon. By this double-click activation process, the user performs a dedicated process for a device to be processed or the like. Realized the function to start the tool. The following processes (1) to (8) correspond to the same numbers in FIG.

  (1) The user double-clicks the saved file of the dedicated tool. In FIG. 24, for example, “c: \ temp \ file3.cxp” is double-clicked from among files listed by the explorer or the like.

  (2) The dedicated tool searches the storage 5 for a summary file with the saved project name. The project name includes path information.

  (3) The dedicated tool extracts the project name from the XML summary file.

  (4) The dedicated tool issues a connection request to the database interface 13 with the project name extracted from the summary file.

  (5) The database interface 13 receives the connection request, expands the database compressed file, and makes the data storage unit 15 available.

  (6) The dedicated tool passes the held device ID (for example, “ID1”) to the database interface 13 and connects to the device on the data storage unit 15.

  (7) The dedicated tool passes its file name to the database interface 13 and searches for a file registered on the database.

  (8) If there is a file, it is regarded as a file registered in the project and the activation is completed. If the file does not exist, the activation is failed and a message is displayed on the screen of the dedicated tool to notify the user that the file not managed by the database is being opened.

  The functions of the dedicated tool and the database for executing the processes (1) to (8) are as shown in the flowcharts of FIGS. In each figure, (a) is the function of the dedicated tool, and (b) is the function of the database.

  When the user double-clicks the dedicated tool file ("c: \ temp \ file3.cxp" in FIG. 24), the dedicated tool is activated (S91). The dedicated tool connects to the database with the project name held in the tool file (S92). That is, the dedicated tool executes the processes (2) and (3) described above to acquire the project name, and executes the process (4). When this process is executed, the database interface 13 expands the database compressed file in the data storage unit 15.

  Next, the dedicated tool accesses the device management table to acquire the device ID corresponding to the device name, passes the device ID to the database interface 13 and makes a device connection request (S93). This corresponds to the process (6) described above.

  On the other hand, when the device interface 13 receives a device connection request together with the device ID from the dedicated tool (S94), the device interface 13 determines whether the device ID exists in the data storage unit 15 (S95). If the received device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the dedicated tool (S86). If the received device ID exists in the data storage unit 15, the database interface 13 returns success to the dedicated tool (S97).

  The dedicated tool that has received a successful device connection from the database interface 13 by executing S97 makes a file search request to the database interface 13 with the device ID and file name (S101). As will be described later, since a response (success / error) to this search request is returned from the database interface 13, the dedicated tool determines whether or not the response is successful (S102). (Error message output, etc.) is performed (S103), and if successful, the startup process is completed (S104).

  When the database interface 13 receives a file connection request together with the device ID and file name from the dedicated tool (application) (S105), the database interface 13 determines whether the device ID exists in the data storage unit 15 (S106). If the received device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the dedicated tool (S107). If the accepted device ID exists in the data storage unit 15, it is determined whether or not the accepted file name exists below the detected device ID (S108). If the accepted file name does not exist below the device ID, the database interface 13 returns an error to the dedicated tool (S107). If the accepted file name exists in the device ID, the database interface 13 returns success to the dedicated tool (S109).

  Next, the import process will be described with reference to FIGS. The following processes (1) to (11) correspond to the same numbers in FIG.

  (1) The user selects a control device or network virtual icon I created in the configuration management application 11, and selects a menu for importing a related file. That is, the selection process is set so that, for example, when a virtual icon I is specified by right-clicking on the pointing device, a list of processes to be executed (copy, delete, import,...) Is displayed by a pull-down menu. This can be executed by selecting “Import” from the menu.

  (2) The configuration management application 11 shows a list of files to be imported (dialog D) to the user.

  (3) The user selects a file to be imported from the list of files displayed in the dialog D. In FIG. 27, “c: ¥ temp ¥ file5.cxp” is selected. If the file to be imported at this time is already recorded in the database, the import is stopped.

  (4) The configuration management application 11 acquires a device ID associated with the virtual icon I with reference to the device management table, passes the acquired device ID to the database interface 13, and issues a device connection request.

  (5) The configuration management application 11 passes the project name, device ID, and file name to be imported (for example, c: \ temp \ file5.cxp) to the dedicated tool, and starts the dedicated tool.

  (6) The dedicated tool activates the specified file.

  (7) The dedicated tool passes the project name and device ID to the database interface 13 and issues a database connection request.

  (8) The user selects saving of the setting file on the dedicated tool, and saves the file (eg, c: \ temp \ file6.cxp). The file includes a device management table.

  (9) The dedicated tool passes the file name (including the storage location) and ID to the database interface 13.

  (10) The database interface 13 creates a file name (including the storage location) under the control device or network ID indicated by the ID in the data storage unit. At this time, a master flag (a flag for setting a default startup file) is set as in the storage location. (MASTER = ON)

  (11) The user ends the dedicated tool.

  The functions of the dedicated tool and the database for executing the processes (1) to (11) are as shown in the flowcharts of FIGS. In each figure, (a) is the function of the configuration management application and dedicated tool, and (b) is the function of the database.

  When the user double-clicks the tool file ("c: \ temp \ file5.cxp" in FIG. 27), the dedicated tool is activated (S111). The dedicated tool connects to the database with the project name held in the tool file (S112).

  Next, the dedicated tool accesses the device management table to obtain a device ID corresponding to the device name, passes the device ID to the database interface 13 and makes a device connection request (S113).

  On the other hand, when the device interface 13 receives a device connection request together with the device ID (S114), the device interface 13 determines whether the device ID exists in the data storage unit 15 (S115). If the received device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the dedicated tool (S116). If the received device ID exists in the data storage unit 15, the database interface 13 returns success to the dedicated tool (S117).

  When the configuration management application 11 recognizes that the user has selected the import process (S120), the configuration management application 11 presents a list of files under an arbitrary folder to the user in a dialog (S121). The configuration management application waits for the user to select a file (S122, S123). When the file is selected, the configuration management application 11 closes the file list dialog (S124). At this time, the configuration management application 11 stores the file position information selected by the user.

  When the database interface 13 receives a file connection request together with the device ID and file name from the application (S125), the database interface 13 determines whether the device ID exists in the data storage unit 15 (S126). If the accepted device ID does not exist in the data storage unit 15, the database interface 13 returns an error to the application (S127). If the accepted device ID exists in the data storage unit 15, it is determined whether or not the accepted file name exists below the detected device ID (S128). If the accepted file name does not exist below the device ID, the database interface 13 returns an error to the application (S127). If the accepted file name exists in the device ID, the database interface 13 adds file storage location information to the device ID.

  The configuration management application 11 acquires the device ID from the device management table and connects to the database (S131). The configuration management application 11 waits for a response from the database interface 13 and determines whether the response is an error (S132). If there is an error, error processing is executed (S133). This error processing includes, for example, displaying an error message on the work window. On the other hand, if no error is returned from the database interface 13, the configuration management application 11 passes the project name, device ID, and remembered file position information to the dedicated tool (S134).

  The dedicated tool acquires the project name, device ID, and file location information from the configuration management application 11 (S135), and opens the file with the acquired file location information (S136). Then, the dedicated tool performs slur processing when there is no file with the file position information corresponding to the storage (S138). On the other hand, if the corresponding file exists in the storage, the file is opened (S139).

It is a figure which shows an example of the system schematic diagram in this invention. It is a figure which shows the hardware constitutions of a control system setting apparatus. It is a figure explaining the starting side process of database entry creation. It is a figure explaining the starting side process of database entry creation. It is a figure explaining the starting side process of database entry creation. It is a figure explaining the starting side process of database entry creation. It is a figure explaining the starting side process of database entry creation. It is a figure explaining the process of the to-be-activated side when a dedicated tool is started. It is a figure explaining the process of the to-be-activated side when a dedicated tool is started. It is a figure explaining the process of the to-be-activated side when a dedicated tool is started. It is a figure explaining the preserve | saved process by the side of a to-be-activated. It is a figure explaining the preserve | saved process by the side of a to-be-activated. It is a figure explaining the preservation | save / completion | finish process by the side of starting. It is a figure explaining the preservation | save / completion | finish process by the side of starting. It is a figure explaining a restart process. It is a figure explaining a restart process. It is a figure explaining a start file switching process. It is a figure explaining a start file switching process. It is a figure explaining a start file switching process. It is a figure explaining a device deletion process. It is a figure explaining a device deletion process. It is a figure explaining a device copy process. It is a figure explaining a device copy process. It is a figure explaining a double click starting process. It is a figure explaining a double click starting process. It is a figure explaining a double click starting process. It is a figure explaining an import process. It is a figure explaining an import process. It is a figure explaining an import process. It is a figure explaining an import process.

Explanation of symbols

5 Storage 10 Control System Setting Device 11 Configuration Management Application 12 Communication Interface 13 Database Interface 13
14 Communication middleware 15 Data storage

Claims (7)

A control system setting device used for setting a control system by connecting to a control system including a plurality of devices connected via a network,
A configuration management application for creating a network configuration diagram of the control system;
Storage means for storing and holding a setting file comprising parameters and / or programs set in the device ;
A dedicated tool for creating and updating the configuration file;
The storage location information for specifying the storage location in the storage means of the setting file stored and held in the storage means, the tool name of the dedicated tool, and the unique assigned to the device corresponding to the setting file A work memory holding a related file in which the ID is associated;
With
The configuration management application already created configuration file, the graphic representing the device drawing the network configuration is selected, pre-Symbol saving of the configuration file for the selected device to access the work memory acquired location information, tool name, the ID, the the tool name to dedicated tools identified, with pass and the storage location information and the file name and the ID acquired, the ability to perform the process for starting the special tool Have
In the storage means, it is possible to save a plurality of different setting files associated with a figure indicating the same device,
A master flag is set in each related file on the work memory corresponding to the plurality of setting files,
Any one of the related files has a master flag set to ON,
The control system setting device , wherein the storage location information that the configuration management application passes to the dedicated tool when the graphic is selected is stored in a related file whose master flag is ON .   The plurality of configuration files are an update source configuration file and an updated configuration file, and are set such that a master flag of an associated file of the updated configuration file is set to ON. Item 4. The control system setting device according to Item 1.   The control system setting device according to claim 1, further comprising means for switching ON / OFF of master flags of the plurality of related files. 4. The control system setting device according to claim 1, wherein the work memory is set on a main memory of a computer constituting the control system setting device. 5. The dedicated tool that stores the setting file in the storage unit has a function of setting storage location information of the stored setting file in the work memory. 6. Control system setting device. The configuration management application, when the graphic representing the device drawing the network configuration is deleted, deletes the relevant file stored in the work memory based on an ID corresponding to the deleted graphic, the work 6. The control system setting device according to claim 1, further comprising a function of deleting a setting file stored in the storage in accordance with storage location information stored in a memory . When the graphic representing the device on the network configuration diagram is duplicated, the configuration management application stores in the storage according to the storage location information of the related file in the work memory associated with the ID corresponding to the duplicated graphic. with replicating the configuration files, the one replicated storage location information of the new configuration file from claim 1, characterized in that a function of storing in the work memory as a new associated file 6 of 1 The control system setting device according to item.

Images