JP2012174148A - Data processing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable local memories, used between any apparatuses connected to any network, to be related to each other.SOLUTION: In profile data 4A, a network type of a connection destination and a predetermined parameter are described for each apparatus. In memory assignment rule data 6, a memory assignment rule, using the parameter described in the profile data 4, is described for each network type. An apparatus configuration management section 8 extracts a parameter described in the profile data 4 of an apparatus connected to a network type that is a target of a memory assignment, and displays the extracted parameter together with a corresponding apparatus so that setting information for identifying a local memory of the apparatus is input for each parameter. A memory assignment analysis section 9 analyzes the memory assignment rule, using the setting information for the parameter, to identify a group of local memories to be related to each other.

Description

The present invention relates to a technique for sharing data among a plurality of devices.
The present invention relates to a technology for sharing data among, for example, a plurality of FA (Factory Automation) devices.

In a control system configured using FA devices, in order to exchange data between devices, communication is performed by connecting via a network or bus communication (hereinafter, included in “network”).
Various networks are used depending on the purpose of communication. Depending on the network, a shared memory may be used as a communication mechanism.
In such a network, a memory shared by each device is virtually prepared on the network, a value of a specific memory area of each device is periodically written, and the value is stored in a specific memory area of another device. By periodically writing, memory values are shared between devices.
For example, in a CC-Link IE field network (see Non-Patent Document 1) whose specifications are defined by the CC-Link Association, data communication is performed between a master station and a slave station using a distributed shared memory as shown in FIG. Is going.
By using the shared memory, the devices B to D that are slave stations can acquire a part of the output data of the device A that is a master station, and the device A outputs all the outputs of the devices B to D. Data can be acquired.
When developing a control system, programs and debugging are performed by directly using the memory address name of the device.
Therefore, in a system using a shared memory, it is necessary to grasp which local memory of which device is allocated to the local memory of the device.
For example, in the system shown in FIG. 2, when the output 1 is used in the program of the device A, it is necessary to program that the value of the memory is written to the input b of the device B.
Further, when monitoring the device A by debugging, it is necessary to grasp that the input 1 is the output c of the device C.
The memory allocation relationship is uniquely determined by the network method, the network configuration for constructing the control system, the memory configuration of the devices connected to the network, and setting information such as parameters for each device.
Since it is necessary to grasp various rules and device characteristics in order to analyze the allocation relationship, the device configuration development support system has provided a function for supporting the user by displaying the allocation relationship of the shared memory.
For example, in Non-Patent Document 2, display of the memory sharing relationship between devices is performed by an allocation image diagram display function.

In recent years, in order to develop a control system combining various networks and devices, a device configuration development support system corresponding to various networks and devices has been demanded.
Past device configuration development support systems have been developed by creating the memory configuration of the corresponding device directly in the device configuration development support system.
However, with this method, it is necessary to recreate a device configuration development support system each time a new device is developed.
Therefore, in recent years, device configuration development support systems corresponding to various devices have been developed by acquiring device information from profile data.
For example, in Patent Document 1, a device that can be connected to a network is identified by reading profile data in which specification information of the network and the device is written.
According to Patent Document 1, the device configuration development support system can perform memory mapping for an arbitrary device by reading information on the memory configuration of the device from the profile data.

JP 2006-302297 A

“Outline of“ CC-Link IE Field Network ””, CC-Link Association, Internet <URL: http: // www. cc-link. org / jp / material / documents / ie_field — 100210. pdf> “Q compatible MELSECNET / H network system reference manual (internet between PCs)”, Mitsubishi Electric Corporation, Internet <URL: http: // wwwf2. mitsubishielectric. co. jp / melfansweb / members / document / manual / school_text / sh080711 / sh080711b. pdf>

The shared memory allocation method may differ depending on the network.
For example, as shown in FIG. 2, in the network that assigns only the number of points used, and in the network that assigns the same number of inputs and outputs to each device as shown in FIG. Results are different.
Some networks can customize the allocation method by setting parameters.
Conventional device configuration development support systems have provided a function for analyzing assignments according to the corresponding network assignment method.
However, since it is provided for each individual network type, it cannot handle different networks.
In particular, when using a device that performs bus communication whose rules are uniquely defined by a vendor, it is necessary to use a device configuration development support system specialized for the network.

  The main object of the present invention is to solve the above-described problems, and it is a main object of the present invention to enable the association of local memories used between arbitrary devices connected to an arbitrary network.

The data processing apparatus according to the present invention
A data processing device for associating a local memory of a device among a plurality of devices connected to a network,
For each device type, a profile database that stores profile data describing a network type and a predetermined parameter as a connection destination of the device of the device type,
For each network type, a rule database that stores rule data in which memory association rules using parameters described in profile data of a device type having the network type as a connection destination are described;
Enter the target network type that is the target of local memory association, and select the profile data of multiple selected device types that are selected as the target of local memory association from the device types that have the target network type as the connection destination. The parameters described are extracted, the extracted parameters are displayed in association with the corresponding selected device type, and setting information for specifying the local memory of the device of the corresponding selected device type is displayed for each displayed extracted parameter. An input device configuration management unit;
Applying the setting information input by the device configuration management unit to the extraction parameter, analyzing the memory association rule of the target network type, specifying a set of related local memories, and specifying the specified set of local memories And a rule analysis unit to be related.

  According to the present invention, since the memory association rule using the parameters described in the profile data is provided for each network type, the parameters described in the profile data and the parameters are set regardless of the network type. The local memory can be related using the setting information for.

The system block diagram of the apparatus structure development assistance system by Embodiment 1 and 2. FIG. The figure which shows an example of the memory allocation in the network which communicates using a shared memory. The figure which shows an example of the memory allocation in the network which allocates the same score with respect to the input of each apparatus, and an output. FIG. 5 shows an example of profile data according to the first embodiment. FIG. 4 is a diagram showing an example of memory allocation rule data according to the first embodiment. FIG. 3 is a diagram illustrating an example of a device configuration managed by a device configuration management unit according to the first embodiment. The flowchart figure which shows the flow of operation | movement of the apparatus structure development assistance system by Embodiment 1. FIG. The figure which shows the example of the memory allocation relationship analyzed in the apparatus structure development assistance system in Embodiment 1. FIG. FIG. 10 is a diagram illustrating an example of a device configuration managed by a device configuration management unit according to the second embodiment. The figure which shows the example of the memory allocation in the system in which the apparatus which has a role of the gateway in Embodiment 2 performs the memory allocation between several networks. FIG. 6 shows an example of profile data according to the second embodiment. The system block diagram of the apparatus structure development assistance system by Embodiment 3 and 4. FIG. The figure which shows the hardware structural example of the apparatus structure development assistance system by Embodiment 1-4.

Embodiment 1 FIG.
In the present embodiment, a device configuration development support system capable of analyzing the allocation relationship of shared memory used between arbitrary devices connected to an arbitrary network will be described.

FIG. 1 is a system configuration diagram of a device configuration development support system 1 according to the first embodiment.
The device configuration development support system 1 is an example of a data processing device.

In FIG. 1, an input unit 2 is used by a device configuration developer to specify a device configuration.
The display unit 3 displays the device configuration designated by the device configuration developer.
Profile data 4 is data in which device specification information such as a network type used by a device, parameters, and a local memory map is described for each device in a common format.
The profile database 5 can store a plurality of profile data 4.
The memory allocation rule data 6 is data describing the memory allocation rule of the shared memory for each network.
More specifically, the memory allocation rule data 6 uses information written in the profile data of devices connectable to the network as variables, so that the shared memory can be stored in a common format independent of the type of network. Memory allocation rules are described.
The memory allocation rule database 7 stores a plurality of memory allocation rule data 6.
The memory allocation rule database 7 is an example of a rule database.
The device configuration management unit 8 manages the configuration of the system designed by the device configuration developer and displays and manages the setting information for each device by acquiring information that needs to be set for each device from the profile data. .
The memory allocation analysis unit 9 analyzes the memory allocation of the shared memory based on the memory allocation rule data 6.
The memory allocation analysis unit 9 is an example of a rule analysis unit.
The control unit 9 manages the execution of the input unit 2, display unit 3, profile database 5, memory allocation rule database 7, device configuration management unit 8, and memory allocation analysis unit 9 and data reference.

[Profile data 4]
FIG. 4 shows an example of the profile data 4.
The profile data 4a of the device A describes a master device, communication on the network P, a memory map to be allocated to the shared memory, and a parameter map.
Similarly, the profile data 4b of the device B describes a slave device, communication on the network P, a memory map assigned to the shared memory, and a parameter map.
Device A and device B in the profile data represent device types, not individual devices.
The device type is, for example, the model name or model number of the device, and the profile data 4a of the device A represents the specification of the model name / model number of the device A. Similarly, the profile data 4b of the device B represents the specification of the model name / model number of the device B.

[Memory allocation rule data 6]
FIG. 5 shows an example of the memory allocation rule data 6.
In FIG. 5, a condition for specifying the slave device is shown in the “device designation” column, an identifier of the local memory of the slave device is shown in the “device memory” column, and “master memory” The column shows a condition for specifying the local memory of the master device.
The memory allocation rule is described by using a reserved word indicating a specific meaning and information written in profile data of each device as variables.
The reserved word used in the memory allocation rule data of FIG. 5 indicates that “PARAM” refers to the parameter value written in the profile data of the slave device to which the network is connected, and “PARAM_MASTER”. Indicates that the parameter value written in the profile data of the master device to which the network is connected is referred to.
In this way, the conditions (conditions for specifying the slave device) shown in the “device specification” column are defined by the parameters written in the profile data of the slave device, and the “master memory” The conditions shown in the column (conditions for specifying the local memory of the master device) are defined by parameters written in the profile data of the master device.
“NEXT” indicates that the memory is allocated to the next address of the memory allocated in the previous row.
For example, the description on the first line in FIG. 5 indicates that the local memory of the master device specified by the parameter “Device_input_lead” of the master device is different from the local memory “Local-in-1” of the device whose parameter “StationNum” is 1. Indicates allocation.
Reserved words need to be shared by all networks, but it is not necessary to share memory addresses and parameter description methods for all networks.
However, since it is necessary to refer to the information described in the profile data of each device type from the character string described in the memory allocation rule data 6, the description format of the information used in the memory allocation rule data 6 is the network type. The profile data of the device type that is shared for each network and connected to the network needs to be described using a common description format.
The memory allocation rule may be indicated by the allocation relationship between the local memory and the shared memory of each device, but since the allocation relationship between the local memories of each device is finally derived, only the allocation rule between the devices can be shown. The allocation rule to the shared memory is not essential.
FIG. 5 shows the memory allocation relationship in a table format, but the allocation rules may be shown in a program format such as a script.
Further, when creating the network specifications, the allocation specifications to the shared memory are described in a format that can be analyzed by the memory allocation analysis unit 9, and the data of the specifications can be directly used as the memory allocation rule data 6. Good.

[Device configuration management unit 8]
FIG. 6 shows an example of the device configuration set using the device configuration management unit 8.
In this example, one device A and two devices B (devices B-1 and B-2) are connected by a network P.
Further, the device configuration management unit 8 provides means for setting parameters of each device based on information written in the profile data 4.
More specifically, the device configuration management unit 8 inputs a target network type to be associated with the local memory from the device configuration developer via the input unit 2 and searches the profile database 5 for the target. A device type having the network type as a connection destination (a device type in which the target network type is described in the network type field of the profile data) is extracted, and a list of the extracted device types is displayed using the display unit 3.
Next, the device configuration developer selects a device to be associated with the local memory from the displayed device type list.
The selected device is called a selected device. The device type of the selected device corresponds to the selected device type.
The device configuration developer may select all models in the list as selected devices, or may select only specific models as selected devices.
Next, the device configuration management unit 8 extracts parameters described in the profile data of the selected device.
Then, the device configuration management unit 8 displays a screen for setting the extracted parameters extracted for the selected device using the display unit 3.
In addition, the device configuration management unit 8 inputs setting information for specifying the local memory of the corresponding selected device for each extraction parameter.

In the case of FIG. 6, when the device configuration management unit 8 inputs the network P as the target network type from the device configuration developer, the device type having the network P as the connection destination (for example, device A, device B, device C). And a list of the extracted device types is displayed using the display unit 3.
Here, it is assumed that the device configuration developer has selected one device A and two devices B as the configurations of the devices connected to the network P (device A, device B-1, and device B-2 in FIG. 6). Corresponding).
In this case, the device configuration management unit 8 extracts the parameters (Device1_input_lead etc.) described in the profile data 4a of the device A and the parameters (SationNum) described in the profile data 4b of the device B, and extracts each parameter. Are displayed together with the corresponding selected device (device A, device B-1, device B-2).
Then, in the example of FIG. 6, the device configuration management unit 8 inputs setting information Local-out-1 from the device configuration developer, for example, to the parameter Device1_input_lead of the master device, and also sets the parameter StationNum of the slave device. On the other hand, as setting information, the identifier of the device B-1 and “1” (StationNum = 1) are input, and the identifier of the device B-2 and “2” (StationNum = 2) are input.

In FIG. 6, as an example of a setting screen generated by the device configuration management unit 8, an example of a screen for setting the device configuration in a visually understandable format is shown, but a setting screen in another format such as a table is displayed. Also good.
In addition to the setting screen shown in FIG. 6, the device configuration management unit 8 lists the local memory of the device A shown in the input / output map of the profile data 4a and the local memory of the device B shown in the input / output map of the profile data 4b. You may make it display the list of.

[Memory allocation analysis unit 9]
FIG. 7 shows a flowchart describing the flow of operation of the memory allocation analysis unit 9.
An example in which memory allocation is executed using the flowchart of FIG. 7 with respect to the examples of FIGS. 4, 5, and 6 will be described below.

First, the memory allocation analysis unit 9 acquires from the information of the device configuration management unit 8 in FIG. 6 that the network type for performing the allocation determination is the network P (STEP 1 in FIG. 7).
In order to acquire the memory allocation rule for the network P acquired in STEP 1 of FIG. 7, the memory allocation analysis unit 9 acquires the memory allocation rule data 6 of the network P shown in FIG. 5 from the memory allocation rule database 7 ( (Step 2 in FIG. 7).
Next, the memory allocation analysis unit 9 acquires all the model names (device A, device B) of the devices connected to the network P by the device configuration management unit 8 in FIG. 6 (STEP 3 in FIG. 7).
In order to acquire the device information acquired in STEP 3 of FIG. 7, the memory allocation analysis unit 9 acquires the profile data 4 of the devices A and B shown in FIG. 4 from the profile database 5 (FIG. 7). (Step 4).
In this example, the device information used in the device configuration management unit 8 is associated with the profile data 4 using the model name. However, the association may be performed using other information (eg, model number). I do not care.
Next, the memory allocation analysis unit 9 sequentially performs memory allocation using the information written in the memory allocation rule data 6 acquired in STEP 2 in FIG. 7 (STEP 5 to STEP 7 in FIG. 7).
In the memory allocation rule data 6 shown in FIG. 5, first, PARAM (StationNum = 1) is written in the device specification of the memory allocation rule data, so the memory allocation analysis unit 9 sets StationNum to 1 as a parameter. The device configuration management unit 8 checks the devices that are being used.
Then, since Station Num of device B-1 is 1, memory allocation to device B-1 is started.
Since the memory information of the master to be allocated to Local-in-1 of the device B-1 is written as PARAM_MASTER (Device1_input_lead) in the first line of the memory allocation rule data 6, the memory allocation analysis unit 9 uses the master parameter Device1_input_lead. The device configuration management unit 8 examines the value set in, and acquires Local-out-1.
As a result, it is understood that the Local-out-1 of the device A is allocated to the Local-in-1 of the device B-1.
Further, since the memory information of the master allocated to Local-in-2 of the device B-1 is NEXT, the profile data 4 of the device A is checked, and the memory in the next row of Local-out-1 is checked.
Thereby, it is understood that the Local-out-2 of the device A is allocated to the Local-in-2 of the device B-1.
In this way, all memory allocation is performed according to the memory allocation rule data 6.
In the profile data 4b of the device B in FIG. 4, only three addresses, Local-in-1, Local-in-2, and Local-out-1, are described, so that the memory is allocated. Is only for these three addresses.
In the relationship with the device B, the memory allocation rules for Local-in-3 and Local-out-2 shown in FIG. 5 are not used, but the local-in is included in the profile data of another device (for example, device C). -3, Local-out-2 is described, memory allocation rules for these addresses are also used, and memory allocation is also performed for these addresses.

Here, an example has been described in which the assignment can be customized by the parameters set in the device as shown in FIG. 4, but other types of information such as the arrangement order of the devices can be customized as parameters. Also good.
In this case, for example, “device arrangement order” is described in the profile data 4 of each device as a parameter in the same manner as in FIG. 4, and an allocation rule using “device arrangement order” is described in the memory allocation rule data 6. The “device arrangement order” may be set by the configuration management unit 8, or if it is general information such as “device arrangement order”, the “device arrangement order” is acquired. A reserved word is defined, memory allocation rule data 6 is described using the reserved word, and the “device arrangement order” is not described in the profile data 4 of each device. May be set.

FIG. 8 shows the result of analyzing the memory allocation by the memory allocation analysis unit 9 for the examples of FIGS. 4, 5, and 6.
As a result of the analysis, it is understood that the frequency setting of the device B-1 may be set to Local-out-1 of the device A, and in order to acquire the device B completion flag of the device B-2, It can be seen that the Local-in-2 of device A can be viewed.

  As described above, according to the present embodiment, the memory allocation rules are described in a common format that does not depend on the network type, and the setting data in the device configuration development support system regardless of the network type. Since it is possible to analyze the memory allocation relationship using, it becomes possible to support programming and monitoring of a control system using a shared memory in various networks.

The common format is, for example, that the following (1) to (4) are shared.
(1) Format showing devices to be associated In FIG. 5, the master is fixed, and the format shows devices to be associated in the two left columns.
(2) Format showing memory association FIG. 5 shows that memories written on the same line are allocated.
(3) Format indicating parameters as variables [PARAM] in FIG. In addition, it is easy to describe by unifying the format for specifying parameters of special devices (master, etc.).
(4) Format for ease of description “NEXT” in FIG. 5 corresponds.

In this embodiment,
A device configuration development support system including the following means has been described.
(A) An input unit for the device configuration developer to specify the device configuration;
(B) a display unit for displaying the device configuration designated by the device configuration developer;
(C) a profile database capable of storing a plurality of profile data in which device specification information such as a network type used by a device and a local memory map is described for each device type in a common format;
(D) Uses information written in the profile data of devices connectable to the network as variables, and stores a plurality of memory allocation rule data describing memory allocation rules in a common format that does not depend on the type of network. Possible memory allocation rule database;
(E) Managing the configuration of the system designed by the device configuration developer, obtaining a list of information that the device configuration developer needs to set for each device from the profile data, and setting means for the device configuration developer A device configuration management unit that manages setting information for each device by providing
(F) It is possible to interpret a common format describing a memory allocation rule, and profile data and memory allocation rule data corresponding to the device and network managed by the device configuration management unit and set by the device configuration management unit A memory allocation analysis unit that analyzes the memory allocation of the shared memory using the set information.

In the above description, the device configuration management unit 8 has described an example in which parameters are extracted from profile data of a selected device (in the above example, device A and device B) selected by the device configuration developer. Instead of this, the parameters may be extracted from the memory allocation rule of the target network type (network P in the above example).
In this case, parameters need not be described in the profile data.
That is, the parameter map information shown in FIG. 4 is not necessary.
When the device configuration management unit 8 inputs the network P as the target network type from the device configuration developer, the device configuration management unit 8 extracts and extracts the device types (for example, the device A, the device B, and the device C) that are connected to the network P. A list of device types is displayed using the display unit 3.
In parallel, a master parameter (Device1_input_lead etc.) and a slave parameter (StationNum = 1 etc.) are extracted from the memory allocation rule of the network P.
Here, it is assumed that the device configuration developer has selected one device A and two devices B as the configurations of the devices connected to the network P (device A, device B-1, and device B-2 in FIG. 6). Corresponding).
In this case, the device configuration management unit 8 displays the master parameter extracted from the memory allocation rule of the network P for the device A and displays the slave parameter for the devices B-1 and B-2.
In the example of FIG. 6, for example, the device configuration management unit 8 inputs the setting information Local-out-1 for the parameter Device1_input_lead of the master device from the device configuration developer, and also enters the parameter StationNum of the slave device. On the other hand, as setting information, the identifier of the device B-1 and “1” (StationNum = 1) are input, and the identifier of the device B-2 and “2” (StationNum = 2) are input.
The operation of the memory allocation analysis unit 9 is as shown in FIG.

Embodiment 2. FIG.
FIG. 9 is an example of a device configuration created by the device configuration management unit 8 of the device configuration development support system 1 according to the second embodiment.
In this example, the device E is assigned to the network Q and the network R and serves as a gateway that relays the network Q and the network R.
The device E has a termination local memory (Local1 to 4) that terminates the network Q and a termination local memory (Local_a to d) that terminates the network R, and links the termination local memories as shown in FIG. Memory allocation is performed on
That is, the memory “Local5” of the device C is allocated to the memory “Local_a” of the device F via the memories “Local1” and “Local_a” of the device E.
The profile data 4 of the device E acting as a gateway is described as shown in FIG.
That is, it has a memory map used on the network Q side and a memory map used on the network R side, and has allocation relationship information between the memories for both networks.
As the description format of the memory map, a format commonly defined in each network is used.
That is, the address on the network Q side is described using a description format defined by the network Q, and the address on the network R side is described using a description format defined by the network R.
The example of FIG. 10 shows an example in the case where the correspondence between the address on the network Q side and the address on the network R side is fixed, but in the case of a device whose allocation can be changed by parameters, the memory allocation rule data 6 and Similarly, an assignment rule using the parameter name as a variable may be described in the profile data 4 of the device E.

The memory allocation analysis unit 9 first analyzes the memory allocation of the network Q and the network R using the method shown in the first embodiment.
Further, by analyzing the correspondence relationship between the networks using the correspondence relationship between the memories for both networks described in the profile data of the device E, the memory allocation relationship as shown in FIG. 10 can be shown. it can.

  As described above, according to the present embodiment, it is possible to analyze a memory allocation relationship for a system in which a plurality of types of networks are connected via a device serving as a gateway and a value is shared between devices across the plurality of networks. It becomes.

In this embodiment,
The device configuration development support system in which the following characteristics are added to (c) and (f) described in the first embodiment has been described.
(G) A profile database that can also store profile data that can be connected to a plurality of networks and that can manage the allocation relationship between the memories allocated to the shared memory of each network;
(H) Memory that can analyze memory allocation for a plurality of networks managed by the device configuration management unit, and can analyze memory allocation among a plurality of networks using the profile data information shown in (g) Allocation analysis unit.

Embodiment 3 FIG.
FIG. 12 is a system configuration diagram of the device configuration development support system 1 according to the third embodiment.
The device configuration development support system 1 includes a communication unit 11 that can execute communication with the control system in addition to the system configuration in the first embodiment.
In STEP 6 of FIG. 7 of the analysis processing by the memory allocation analysis unit 9, when the current value of the information described in the profile data 4 is required, the device configuration management unit 8 uses the communication unit 11 as a development target. It communicates with any device (for example, master device) in a certain control system, and acquires the current parameter value (for example, Local-out-1 which is the value of Device1_input_lead).
The memory allocation analysis unit 9 analyzes the memory allocation using the value.
For example, in order to check the value of the parameter set in the control system, the device configuration management unit 8 inquires the value of the Device1_input_lead to the development target control system via the communication unit 11 and It is envisaged to get a response.

  As described above, according to the present embodiment, by using the information of the control system main body, it is possible to analyze the memory allocation using the setting information that is actually operating.

In this embodiment,
In addition to (a), (b), (c), (d), and (f) described in the first embodiment, the device configuration development support system including the following means has been described.
(G) a communication unit capable of acquiring information set in the control system by communicating with the control system;
(H) Manage the configuration of the system designed by the device configuration developer, and when the setting information of each device is requested from the memory allocation analysis unit, acquire the information set in the control system using the communication unit Device configuration management unit that is passed to the memory allocation analysis unit.

Embodiment 4 FIG.
In the present embodiment, in STEP 1 and STEP 3 in FIG. 7 of the analysis processing by the memory allocation analysis unit 9, the device configuration is obtained when acquiring the network type and the device model name for performing the allocation analysis from the device configuration management unit 8. The management unit 8 uses the communication unit 11 to communicate with any device (for example, a master device) in the control system to be developed, and the current network type, model name information of the device connected to the network, To get.
The memory allocation analysis unit 9 analyzes the memory allocation using the information.
The configuration of the device configuration development support system 1 according to the present embodiment is the same as that shown in FIG.

  As described above, according to the present embodiment, by using the information of the control system main body, even in an environment where the device configuration management unit 8 does not have the configuration information of the control system, it is possible to Allocation analysis can be performed.

In this embodiment,
In addition to (a), (b), (c), (d), and (f) described in the first embodiment, the device configuration development support system including the following means has been described.
(G) a communication unit capable of acquiring the configuration of the control system and information set in the control system by communicating with the control system;
(H) Manages the configuration of the system designed by the device configuration developer. When the device configuration is requested by the memory allocation analysis unit, the configuration of the control system is acquired using the communication unit, and the setting information of each device is obtained. A device configuration management unit that acquires information set in the control system using the communication unit and passes it to the memory allocation analysis unit when requested.

Finally, a hardware configuration example of the device configuration development support system 1 shown in the first to fourth embodiments will be described.
FIG. 13 is a diagram illustrating an example of hardware resources of the device configuration development support system 1 described in the first to fourth embodiments.
The configuration in FIG. 13 is merely an example of the hardware configuration of the device configuration development support system 1, and the hardware configuration of the device configuration development support system 1 is not limited to the configuration illustrated in FIG. It may be a configuration.

In FIG. 13, the device configuration development support system 1 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, a processing unit, a microprocessor, a microcomputer, and a processor) that executes a program.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an SSD (Solid State Drive), an optical disk device, or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
The “profile database 5” and “memory allocation rule database 7” described in the first to fourth embodiments are realized by the RAM 914, the magnetic disk device 920, and the like.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

The communication board 915 is connected to a network.
For example, the communication board 915 is connected to the Internet, a WAN (wide area network), a SAN (storage area network), etc. in addition to a LAN (local area network).

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the device configuration development support system 1 is activated, the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.

  The program group 923 stores programs that execute the functions described as “˜unit” and “˜means” in the description of the first to fourth embodiments. The program is read and executed by the CPU 911.

In the file group 924, in the description of the first to fourth embodiments, “acquisition of”, “extraction of”, “analysis of”, “reference of”, “setting of”, “selection of” ”,“ Input of ~ ”,“ Output of ~ ”, etc. Information, data, signal values, variable values, and parameters indicating the results of the processing are listed as“ ~ file ”and“ ~ database ”items. It is remembered.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory.
Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit.
The read information, data, signal value, variable value, and parameter are used for CPU operations such as extraction, search, reference, comparison, calculation, calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
Further, the arrows in the flowcharts described in the first to fourth embodiments mainly indicate input / output of data and signals.
Data and signal values are recorded on a recording medium such as a memory of the RAM 914, a flexible disk of the FDD 904, a compact disk of the CDD 905, a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk, and a DVD.
Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

Further, in the description of the first to fourth embodiments, what is described as “to part” and “to means” may be “to circuit”, “to device”, and “to device”. It may be “˜step”, “˜procedure”, “˜processing”.
That is, the process of the device configuration development support system 1 can be regarded as a data processing method by the steps, procedures, and processes shown in the flowcharts described in the first to fourth embodiments.
In addition, what is described as “˜unit” and “˜means” may be realized by firmware stored in the ROM 913.
Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware.
Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD.
The program is read by the CPU 911 and executed by the CPU 911.
That is, the program causes the computer to function as “to part” and “to means” in the first to fourth embodiments. Alternatively, the procedures and methods of “to part” and “to means” in the first to fourth embodiments are executed by a computer.

As described above, the device configuration development support system 1 shown in the first to fourth embodiments includes a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a communication board, and a display device as an output device. A computer including a communication board and the like.
As described above, the functions indicated as “˜unit” and “˜means” are realized by using these processing devices, storage devices, input devices, and output devices.

  1 device configuration development support system, 2 input unit, 3 display unit, 4 profile data, 5 profile database, 6 memory allocation rule data, 7 memory allocation rule database, 8 device configuration management unit, 9 memory allocation analysis unit, 10 control unit 11 Communication unit.

Claims (9)

A data processing device for associating a local memory of a device among a plurality of devices connected to a network,
For each device type, a profile database that stores profile data describing a network type and a predetermined parameter as a connection destination of the device of the device type,
For each network type, a rule database that stores rule data in which memory association rules using parameters described in profile data of a device type having the network type as a connection destination are described;
Enter the target network type that is the target of local memory association, and select the profile data of multiple selected device types that are selected as the target of local memory association from the device types that have the target network type as the connection destination. The parameters described are extracted, the extracted parameters are displayed in association with the corresponding selected device type, and setting information for specifying the local memory of the device of the corresponding selected device type is displayed for each displayed extracted parameter. An input device configuration management unit;
Applying the setting information input by the device configuration management unit to the extraction parameter, analyzing the memory association rule of the target network type, specifying a set of related local memories, and specifying the specified set of local memories A data processing apparatus comprising a rule analysis unit for relating. The rule database is
Stores rule data written in a common format independent of the network type,
The rule analysis unit
The data processing apparatus according to claim 1, wherein the data processing apparatus is configured to analyze a common format of rule data. The profile database is
For each device type, it stores profile data describing a list of local memory provided in the device of the device type,
The device configuration management unit
3. The data processing apparatus according to claim 1, wherein a list of local memories described in corresponding profile data is extracted for each selected device type, and the extracted list of local memories is displayed. The data processing device includes:
A data processing device for associating a local memory between a master device and a slave device for a network to which a master device and a slave device are connected,
The profile database is
As profile data for each device type,
Stores the profile data of the master device type and the profile data of the slave device type,
In the master device type profile data, master parameters are described.
In the slave device type profile data, slave parameters different from the master parameters are described.
The rule database is
Master device local memory specifying conditions for specifying the master device's local memory and slave device specifying conditions for specifying the slave device are included.
The local memory identifier is related to the slave device identification condition, the master device local memory identification condition is related to the local memory identifier,
Storing rule data describing a memory association rule in which a master device local memory specifying condition is defined by a master parameter and a slave device specifying condition is defined by a slave parameter;
The device configuration management unit
Master parameters described in the profile data of the master device type selected as the target of the local memory and slaves described in the profile data of the slave device type selected as the target of the local memory Extract the parameters for
Display the extracted master parameters and slave parameters,
As the setting information,
For the displayed master parameter, enter the local memory identifier of the master device of the master device type,
For the displayed slave parameter, input the slave device identifier of the slave device type,
The rule analysis unit
In the memory association rule of the target network type, the master device local memory identifier input by the device configuration management unit is applied to the master device local memory specifying condition master parameter, and the slave device specifying condition slave parameter The identifier of the slave device input by the device configuration management unit is applied to the memory association rule of the target network type, and the set of the local memory of the master device and the local memory of the slave device to be related is specified. The data processing apparatus according to any one of claims 1 to 3. The profile database is
Connect to two or more networks, relay the two or more networks, and for each network, for each relay device type corresponding to a relay device having a terminal local memory that terminates the network, Stores profile data that defines the relationship between end local memories,
The rule analysis unit
For each network relayed by the relay device, the termination local memory and the local memory of other devices in the network are related,
5. The data processing apparatus according to claim 1, wherein the terminal local memories of each network are related to each other in accordance with the definition of the profile data of the relay device type. The data processing device further includes:
It has a communication unit that can communicate with the device,
The device configuration management unit
The data processing apparatus according to claim 1, wherein the setting information is input from any device in the target network via the communication unit. The data processing device further includes:
It has a communication unit that can communicate with the device,
The device configuration management unit
The data processing apparatus according to claim 1, wherein information indicating a device configuration in the target network is input from any device in the target network via the communication unit. A data processing device for associating a local memory of a device among a plurality of devices connected to a network,
For each device type, a profile database that stores profile data that describes the network type that is the connection destination of the device of the device type,
A rule database that stores rule data in which memory association rules using parameters are described for each network type;
Enter the target network type to be related to the local memory, and display a plurality of selected device types selected as the target of local memory from the device types with the target network type as the connection destination A device configuration management unit that displays parameters used in the memory association rule of the target network type and inputs setting information for specifying the local memory of the device of the selected device type for each displayed parameter;
Applying the setting information input by the device configuration management unit for each parameter, analyzing the memory association rule of the target network type, identifying a set of related local memories, and relating the specified set of local memories And a rule analysis unit for attaching the data processing device. The data processing device includes:
A data processing device for associating a local memory between a master device and a slave device for a network to which a master device and a slave device are connected,
The profile database is
As profile data for each device type,
Stores the profile data of the master device type and the profile data of the slave device type,
The rule database is
Master device local memory specifying conditions for specifying the master device's local memory and slave device specifying conditions for specifying the slave device are included.
The local memory identifier is related to the slave device identification condition, the master device local memory identification condition is related to the local memory identifier,
The master device local memory specifying condition is defined by the master parameter for the master device, and the slave device specifying condition is defined by the slave parameter for the slave device.
The device configuration management unit
The master device type selected as the local memory correlation target and the slave device type selected as the local memory correlation target are displayed and used for the memory correlation rule of the target network type. Display master parameters and slave parameters,
As the setting information,
For the displayed master parameter, enter the local memory identifier of the master device of the master device type,
For the displayed slave parameter, input the slave device identifier of the slave device type,
The rule analysis unit
In the memory association rule of the target network type, the master device local memory identifier input by the device configuration management unit is applied to the master device local memory specifying condition master parameter, and the slave device specifying condition slave parameter The identifier of the slave device input by the device configuration management unit is applied to the memory association rule of the target network type, and the set of the local memory of the master device and the local memory of the slave device to be related is specified. The data processing apparatus according to claim 8.

Images