JPH1021159A - Node device and network system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily compile a sequence program (user program) without being conscious of the existence of another node and an actual address in a network system. SOLUTION: The node 10 is constituted of a PLC(programmable logic controller) part 10A and NET(communication controller) part 10B. In the PLC part 10A, a drive number is permitted to correspond to the actual address consisting of a network address and a node address so as to be adopted as a mount parameter and to be stored in a mount parameter storing part 16. When CPU 11 and an OS(operating system) part 12 receive the user program for designating the respective nodes of a transfer source and a transfer destination by the drive number from a user program storing part 14, the actual addresses of the respective nodes of the transfer source and the transfer destination are obtained from the mount parameter storing part 16 based on the designated drive number.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a node device constituting a node for constructing a network, and a network system for connecting a plurality of networks and exchanging data between the plurality of node devices constituting each network. It is about.

[0002]

2. Description of the Related Art FIG. 12 is a configuration diagram showing a general configuration of a network system. The network system shown in FIG.
0, and the relay station 100 is installed between the networks 200 and 300. The relay station 100 is connected to the network 200 via a line 204, and is connected to the network 300 via a line 303.

One network 200 is connected to a node 20
1, 202, and 203, and each node 201
To 203 are connected on a line 204. The other network 300 is constructed by node nodes 301 and 302, and connects the nodes 301 and 302 on a line 303. Each relay station 100, nodes 201 to 20
Reference numerals 3, 301 and 302 constitute a programmable logic controller (hereinafter, referred to as a PLC), and have a memory for storing data therein.

[0004] In network 200, "A" is set as the network address. In this network 200, nodes 201, 202, 20
3, "A1",
“A2” and “A3” are set. Network 3
In “00”, “B” is set as the network address. In the network 300, “B1” and “B2” are set as node addresses in the nodes 301 and 302, respectively.

[0005] The above network system exchanges data between the memory of its own node and the memory of another node using a real address consisting of a network address and a node address.

Here, the relationship between a network address and a node address in the above network system will be described. FIG. 13 is a diagram for explaining real addresses used for data exchange in the network system of FIG.

The nodes 201, 202, 203, 301,
302, different real addresses [A, A1],
[A, A2] and [A, A3] are set, and these different real addresses are used to identify the access point from other nodes.

For example, the own node is the node 201,
If the other node is the node 301, the node 20
1 (own node) in the real address [A, A
1], the data exchange is performed in a state where the communication address of the node 301 (other node) includes the real address [B, B1].

Next, a conventional node will be described in detail.
FIG. 14 is a block diagram showing a typical internal configuration of the PLC configuring the nodes 201 to 203, 301, and 302. FIG. 14 shows an example of the node 201 as the typical internal configuration. .

The node 201 includes a PLC unit 400 for executing a processing procedure as a PLC and a communication control device (hereinafter referred to as NET) unit 500 for performing communication control.
Is composed. The PLC section 400 is connected to the line 204 via the NET section 500, and the PLC section 400 and the NET section 500 are connected by a bus 600.

The PLC section 400 includes a CPU 401, an operating system (hereinafter referred to as OS) section 402,
OS memory unit 403, user program storage unit 40
4 and a user data storage unit 405.

The CPU 401 is constituted by a microprocessor or the like, and executes a processing procedure as a PLC according to the control contents of the OS unit 402. This CPU 401 is connected to the bus 40
6, an OS unit 402, an OS memory unit 403, a user program storage unit 404, a user data storage unit 405
Are connected to the bus 406 for each of these units.
, The processing procedure as a PLC is executed. The bus 406 is an internal bus of the PLC unit 400 and is connected to the bus 600 for exchanging data between the PLC unit 400 and the NET unit 500.

The OS section 402 stores a processing procedure for the PLC section 400 to operate as a PLC in a readable manner by the CPU 401, and the OS memory section 403 is used as a work area during execution of the CPU 401. The user program storage unit 404 stores a user program set by the user so that the CPU 401 can read the user program. The user program is executed under the control of the CPU 401 in accordance with the processing procedure of the OS unit 402, such as a control program shown in FIGS. 16, 18, and 20, which will be described later. The user data storage unit 405 stores various data such as initial data related to the processing procedure of the CPU 401, data during execution, and processing results.

The NET section 500 includes a CPU 501, an OS section 502, a bus I / F 503, a network address setting section 504, a node address setting section 505, and a communication interface.
/ F506. The NET unit 500 is connected to a bus 600 via a bus I / F 503.
Data communication with the PLC unit 400 is executed via the / F 503. The NET unit 500 is connected to the line 204 via a communication I / F 506, and executes communication control such as data exchange between the own node and another node via the communication I / F 506. In the example of FIG. 12, the nodes 202 and 203 in the same network 200 and the nodes 301 and 302 in the other network 300 correspond to the other nodes.

The CPU 501 is constituted by a microprocessor or the like, and executes a communication procedure according to the control contents of the OS unit 502. This CPU 501 is connected to an OS via a bus 507.
A unit 502, a network address setting unit 504, and a node address setting 505 are connected to each other, and access these units via the bus 507 to execute a communication procedure. A bus 507 is an internal bus of the NET unit 500, and is connected to the bus I / F 503 and the communication I / F 506.

The OS section 502 stores a program for the NET section 500 to operate as a NET so that the program can be read by the CPU 501. The network address setting unit 504 sets and stores a network address, and the node address setting unit 505 sets and stores a node address.

Here, the above-mentioned user data storage unit 40
5 will be described in detail. FIG. 15 shows a user data storage unit 40.
FIG. 5 is a block diagram showing an internal configuration of the fifth embodiment.

As shown in FIG. 15, the user data storage unit 405 stores a device X 405A and a device Y 405B.
The device X405A and the device Y
405B is used to store user data in the own node 201. In the following description, the device X 405A and the device Y 405B belong to the user data storage unit 405 in the own node 201 and are called local devices with respect to other nodes. On the other hand, devices X and Y belonging to a user data storage unit in a network of the own node or a node of another network, that is, another node are referred to as remote devices.

Next, the operation will be described. First, 2
Data transfer between two local devices will be described. FIG. 16 is a diagram showing an example of a user program incorporating a transfer command between two local devices.
FIG. 7 is a view for explaining a processing image of the user program shown in FIG.

In the user program shown in FIG. 16, "MOV" is used as a transfer command used for transfer within the own node, and thereafter, three fields for setting the contents of the command are provided. The first field has “X0” indicating the address 0 of the source device X, the second field has “Y0” indicating the address 0 of the destination device Y, and the third field has five points to be transferred ( "5" indicating 5 addresses)
Are set respectively.

According to this user program, when an execution instruction is established, data transfer between local devices is executed in the user data storage unit 405. That is, as shown in FIG. 17, five points of user data are read from the address 0 of the device X405A which is a local device, and the user data of the five points are read from addresses 0 to 4 of the device Y405B which is a local device. It is transferred to the address.

Next, data transfer from the local device to the remote device will be described. FIG. 18 is a diagram showing an example of a user program incorporating a transfer command from a local device to a remote device.
FIG. 19 is a diagram for explaining a processing image of the user program shown in FIG. 18. In FIG. 19, the node 202 includes a user data storage unit 2405 similarly to the node 201, and the user data storage unit 2405 is provided with a device X 2405A and a device Y 2405B.

In the user program shown in FIG. 18, "SEND" is used as a transfer instruction used for transfer to another node.
Is used, followed by five fields for setting the instruction content. The first field is “0” indicating that the transfer destination is the own network, the second field is “A2” indicating the node address of the transfer destination, and the third field is address 0 of the transfer source device X. "X0" indicating the destination device Y in the fourth field.
“Y0” indicating an address is set in the fifth field, and “5” indicating five points (for five addresses) to be transferred is set in the fifth field.

According to this user program, when an execution instruction is established, data transfer from the local device to the remote device is executed in the user data storage unit 405. That is, as shown in FIG.
Five points of user data are read from the address 0 of the device X405A, which is a local device, and the user data of the five points are transferred via the bus 204 to addresses 0 to 4 of the device Y2405B, which is a remote device. .

Next, data transfer from the remote device to the local device will be described. FIG. 20 is a diagram showing an example of a user program incorporating a transfer command from a remote device to a local device.
FIG. 21 is a diagram illustrating a processing image of the user program shown in FIG. 20. In FIG. 21, the node 301 includes a user data storage unit 3405 similarly to the node 201, and a device X 3405A and a device Y 3405B are provided in the user data storage unit 3405.

In the user program shown in FIG. 20, "RECV" is used as a transfer command used for transfer from another node, that is, reception, and thereafter, five fields for setting the contents of the command are provided. In the first field, “B” indicates the network address of the source of the other network, “B1” indicates the node address of the source in the second field, and “B1” indicates the node address of the source in the third field. "X0" indicating the address 0, and "Y" indicating the address 0 of the transfer destination device Y in the fourth field.
"0" is set in the fifth field, and "5" indicating five points (for five addresses) to be transferred is set.

According to this user program, when the execution instruction is established, data transfer from the remote device to the local device is executed in the user data storage unit 3405. That is, as shown in FIG.
Five points of user data are read from the address 0 of the device X3405A, which is a remote device, and the user data of the five points is stored in the line 303, the relay station 100, and the line 204.
Is transferred to addresses 0 to 4 of the device Y405B, which is a local device, via the.

As described above, the user program storage unit 40
4 shows “MO” according to the transfer contents by the user.
A user program using instructions such as "V", "SEND", and "RECV" is stored. CPU 401 and OS unit 4
02 means that, when an instruction is received from the user program storage unit 404 via the bus 406, if the instruction is “SEND” as a transfer instruction, the NET unit 500 requests transmission to another node. , The transfer instruction "REC
If "V", the NET unit 500 is requested to receive data from another node.

That is, the CPU 401 and the OS unit 402 create a communication message in the OS memory unit 403 for the communication request (transmission request, reception request), and send this message via the bus 600 to the NET unit. Send to 500.

Next, the above-mentioned communication request will be described in detail. FIG. 22 is a flowchart illustrating a communication request procedure according to a conventional sequence program. The operation according to the flowchart in FIG. 22 is executed under the control of the CPU 401 in accordance with the processing procedure of the OS unit 402.

First, in step S110, it is determined whether or not an instruction has been received from the user program stored in the user program storage unit 405. Then, when a determination result indicating that no instruction has been received is obtained, the process proceeds to step S102, and another processing procedure as a PLC is executed. Thereafter, the process returns to step S101, and waits for an instruction to be received again.

If it is determined in step S101 that an instruction has been received, the process proceeds to step S103 to determine whether the received instruction is "MOV" of the transfer instruction. Determine. When the transfer command “MOV” is confirmed in this determination, the process proceeds to step S104, and the local device transfer process is performed. Thereafter, the process returns to step S101, and waits for an instruction to be received again.

If the transfer command "MOV" cannot be confirmed in the determination in step S103, it is determined in next step S105 whether or not the transfer command is "SEND". If the transfer command "SEND" is confirmed in this determination, the process proceeds to step S106, and a transmission message addressed to the transmission target node is created in order to perform the remote device transfer process. This transmission message is stored in the OS memory unit 4.
03 is stored. Thereafter, the processing shifts to step S109.

In this case, in step S109, a transmission message addressed to the node to be transmitted is read from the OS memory unit 403, and the transmission message is transmitted to the NET via the bus 600.
Processing to be transmitted to the unit 600 is executed. Thus, the transmission request from the PLC unit 400 to the NET unit 500 for performing the remote device transfer processing is completed. NET
The unit 500 can access a remote device of another node to be transmitted according to the transmission request received from the PLC unit 400.

If the transfer command "SEND" cannot be confirmed in the determination in step S105, it is determined in next step S107 whether or not the transfer command is "RECV". If the transfer command “RECV” is confirmed in this determination, the process proceeds to step S108, and a reception message addressed to the receiving node is created in order to perform the remote device transfer process. This received message is stored in the OS memory unit 403. After that, the process proceeds to step S109
Move to

In this case, in step S109, a received message addressed to the node to be received is read from the OS memory unit 403, and the received message is
Processing to be transmitted to the unit 600 is executed. Thus, the reception request from the PLC unit 400 to the NET unit 500 for performing the remote device transfer processing is completed. NET
The unit 500 can access a remote device of another node to be received according to the reception request received from the PLC unit 400.

Thus, in step S109,
When the transmission request or the reception request to the NET unit 500 is completed, the process returns to step S101, and waits for an instruction again.

If the transfer command "RECV" cannot be confirmed in the determination in step S107, the accepted commands are the transfer commands "MOV", "SEND", "R".
Since it does not correspond to any of the “ECV”, the process shifts to step S110 to execute an error process. afterwards,
The process returns to step S101, and waits again for an instruction.

As an approximation technique, see, for example,
Japanese Patent Application Laid-Open No. 348667/1991 discloses a technique for automatically creating route information between nodes performing communication using a network address, a node address, and the like.

[0040]

Since the conventional network system is configured as described above, the NET unit 5
00 accesses the remote device of another node to be communicated according to the communication request received from the PLC unit 400, the presence of another node of the own network or another node of the other network, and the real address including the network address and the node address. It was necessary to build a sequence program always aware of this.

It is a first object of the present invention to provide a node device capable of easily building a sequence program without being aware of the existence and real addresses of other nodes in a network system.

A second object of the present invention is to provide a network system which can easily exchange data by simply setting up a sequence program without being aware of the existence or real addresses of other nodes.

[0043]

Means for Solving the Problems The above-mentioned problems are solved,
In order to achieve the first object, a node device according to the present invention associates a drive number with each real address in advance, and uses each drive number to select a target node device for data exchange from a plurality of node devices. Specify and convert the specified drive number to the corresponding real address.

Accordingly, since the real address is obtained by specifying the drive number, the sequence program can be easily constructed without the user being aware of the existence of other nodes and the real address.

In the node device according to the next invention, a drive number is made to correspond to each real address in advance, and a data exchange source node device and a data exchange destination node device are selected from a plurality of node devices using each drive number. Specify the device and
According to the correspondence between the designated drive number of the data exchange source and the drive number of the data exchange destination, data transmission from the own node device to one of the other node devices or self data transmission from one of the other node devices. It is determined whether data is received to the node device, and when data is exchanged in accordance with the determined data transmission or data reception, the data is converted into a real address corresponding to each designated drive number.

Therefore, the actual addresses of the data exchange source and the data exchange destination are obtained simply by designating the node device of the data exchange source and the node device of the data exchange destination by the drive number. The designation of the node device and the node device to which data is exchanged is simplified, so that the user can easily compose a sequence program without being aware of the existence or real address of another node.

Further, in order to achieve the second object, the network system according to the present invention associates a drive number with each real address in advance and exchanges data from a plurality of node devices using each drive number. And performs data exchange using a node device that converts the specified drive number into a corresponding real address.

Therefore, when data is exchanged between the node devices, the real address is obtained by designating the drive number, so that in each node device, the user side does not need to be aware of the existence or real address of another node. Data can be easily exchanged by simply setting up a sequence program.

In the network system according to the next invention, a drive number is associated with each real address in advance, and a data exchange source node device and a data exchange destination node device are selected from a plurality of node devices using each drive number. Device, and according to the correspondence between the specified drive number of the data exchange source and the drive number of the data exchange destination, data transmission from the own node device to any one of the other node devices, or data transmission from the other node device A node that determines whether data is received from one of the devices to its own node device and, when performing data exchange according to the determined data transmission or data reception, converts the data to a real address corresponding to each specified drive number. Data exchange is performed using the device.

Therefore, when data is exchanged between the node devices, the actual addresses of the data exchange source and the data exchange destination can be changed simply by specifying the node device of the data exchange source and the node device of the data exchange destination by the drive number. Since the information is acquired, the designation of the data exchange source node device and the data exchange destination node device in each node device is simplified, so that the user does not need to be aware of the existence or real address of another node. Data can be easily exchanged by simply setting up a sequence program.

[0051]

Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. FIG. 1 is a configuration diagram showing a configuration of a network system according to the present invention. The network system shown in FIG. 1 is constructed by a network 1 and a network 2, and a relay station 100 is provided between the networks 1 and 2 in the same manner as in the conventional example described above.
(Not shown). The relay station 100 is connected to the network 1 by a line 204, and is connected to the network 2 by a line 303.

One network 1 is composed of nodes 10 and 2
0, 30 and each node 10, 20, 30
Are connected on the line 204. The other network 2 is constructed by node nodes 40 and 50, and connects each node 40 and 50 on a line 303. Each node 10, 20, 30, 40, 50 constitutes a PLC having a network function.

Network addresses “A” and “B” are set in networks 1 and 2 similarly to networks 200 and 300, respectively. Node 10,
Node addresses “A1”, “A2”, “A3”, “B1”, and “B2” are set in 20, 30, 40, and 50, respectively.

The nodes 10 to 50 are connected to the PLC units 10A, 20A, 30A, 40A, 5
0A and NET section 10B, 20B, 30B, 40B, 50
B.

The PLC sections 10A to 50A store user program storage sections 14, 24, 34, 44, and 5 for storing user programs (sequential programs), respectively.
4 and a user data storage unit 1 for storing user data
5, 25, 35, 45, and 55.

Although the specific differences between the PLC units 10A to 50A and the conventional example will be described later, the relationship between the user program and the user data is, for example, as shown in FIG. There are differences. Also,
The NET units 10B to 50B have the N
Since the configuration is the same as that of the ET section 500, the description is omitted.

Next, the nodes will be described in detail. FIG. 2 is a block diagram showing a typical internal configuration of a PLC for constructing a network system according to the present invention. FIG. 1 shows an example of a node 10 as the typical internal configuration.

The node 10 is connected to a PLC unit 10A that executes a processing procedure as a PLC and a NET unit 10 that performs communication control.
And B to form a PLC. The PLC unit 10A is connected to the line 204 via the NET unit 10B,
The unit 10A and the NET unit 10B are connected by a bus 19.

The PLC section 10A includes a CPU 11, an OS section 1
2, OS memory unit 13, user program storage unit 1
4, a user data storage unit 15, and a mount parameter storage unit 16.

The CPU 11 is constituted by a microprocessor or the like, and executes a processing procedure as a PLC according to the control contents of the OS unit 12. The CPU 11 is connected to an OS unit 12, an OS memory unit 13, a user program storage unit 14, a user data storage unit 15, and a mount parameter storage unit 16 via a bus 17, and these units are connected to the respective units via the bus 17. In this case, the processing procedure as a PLC is executed. Bus 17 is PLC section 10A
Of the PLC unit 10A and the NET unit 10
It is connected to a bus 19 for performing data communication between B.

The OS section 12 stores a processing procedure for the PLC section 10B to operate as a PLC so that it can be read by the CPU 11, and the OS memory section 13 stores the processing procedure.
11 is used as a work area during execution.
The user program storage unit 14 stores a user program set by the user so that the user program can be read by the CPU 11. The user program is executed by a user program such as a control program shown in FIGS.
It is executed under the control of 1.

The user data storage section 15 stores various data such as initial data, data being executed, and processing results related to the processing procedure of the CPU 11. The mount parameter storage unit 16 stores a network address to be mounted (hereinafter, referred to as a mount network address).
The drive No. is assigned to the combination of the ID and the node address (mount node address). It stores the mount parameter corresponding to the (number).

The NET unit 10B is provided with the NE described in the conventional example.
It has the same configuration as the T unit 500, and has a CPU 502,
It comprises the same units as the OS unit 502, the bus I / F 503, the network address setting unit 504, the node address setting unit 505, and the communication I / F 506. This NET unit 10B, like the NET unit 500,
In addition to executing data communication with the PLC unit 10A via the bus 19, communication control such as data exchange between the own node and another node is performed via the line 204.

Next, the mount parameter storage section 16 will be described in detail. FIG. 3 shows the mount parameter storage unit 16.
3 is a diagram showing a memory configuration of FIG. The mount parameter storage unit 16 stores each drive No. as shown in FIG. 0 ...
In this case, a different combination of a mount network address and a mount node address, which is a network environment, that is, a real address is stored so as to be mounted as a drive. By referring to the mount parameter storage unit 16, the drive No. Can be converted to a real address.

The mount parameter storage 16 stores
To access the user data storage of another node,
The drive No. is as if the user data storage unit 15 of the node 10 itself. The mount parameters are set in the form of real addresses so that they can be accessed with. Therefore, the drive of the user data storage unit of the other node functions as a virtual drive in the own node 10.

For example, the drive No. 0 (0 :), the user data storage unit 15 of the own node 10 is stored in the drive number. 0, a combination of the mount network address and the mount node address [0
(Example of special code in mount network address) or A (representing own network 1), FF (Example of special code in mount node address) or A
1 (representing the own node 10)].

Drive No. In the column of 1 (1 :), the user data storage of the other node 20 in the own network 1 is stored in the drive No. For mounting as 1, a combination [0 or A, A2 (representing another node 20)] of the mount network address and the mount node address is set in association with each other. Drive No. In the column of 2 (2 :), the user data storage of the other node 30 in the own network 1 is stored in the drive No. 2, the combination of the mount network address and the mount node address [0 or A, A3 (representing other node 30)]
Are set in association with each other.

Drive No. 3 (3 :), the user data storage of the other node 40 in the other network 2 is stored in the drive No. 3 column. 3, the combination of the mount network address and the mount node address [B (representing other network 2), B1 (other node 4
0)]]. Drive N
o. 4 (4 :), the user data storage of the other node 50 in the other network 2 is stored in the drive No. 4 column. 4, the combination [B, B2 (representing the other node 50)] of the mount network address and the mount node address is set in association with each other.

The above drive No. 1 to No. Drive 4 corresponds to a virtual drive. The mount parameters stored in the mount parameter storage unit 16 are data created and prepared by the user in advance,
The number of drives may be six or more or four or less depending on conditions such as the number of networks and the number of nodes.

Next, the virtual drive will be described in detail.
4 and 5 are diagrams for explaining the concept of a virtual drive for another node of the own network, and FIGS. 6 and 7 are diagrams for explaining the concept of a virtual drive for another node of the other network.

The user data storage unit 15 of the own node 10 (A1) stores the drive No. as shown in FIG. 0
(0 :) and this drive N
o. Conversion to a real address is performed by designating 0, and the user data storage unit 15 can be accessed. The user data storage unit 25 of the other node 20 (A2) in the own network 1 stores the drive No. as shown in FIG. 1
(1 :) and this drive N
o. The conversion to the real address is performed just by specifying 1,
Other node 2 without any difference from access in own node 10
0 user data storage unit 25 can be accessed. As shown in FIG. 5, the user data storage unit 35 of the other node 30 (A3) in the own network 1
o. 2 (2 :). The conversion to the real address is performed only by designating 2, and the user data storage unit 35 of the other node 30 can be accessed without any difference from the access in the own node 10.

The other node 40 in the other network 2
As shown in FIG. 6, the user data storage unit 45 of (B1) stores the drive No. 3 (3 :), and this drive No. 3 is mounted. The conversion to the real address is performed only by specifying “3”, and the user data storage unit 45 of the other node 40 can be accessed without any difference from the access in the own node 10. The user data storage unit 55 of the other node 50 (B2) in the other network 2 stores the drive No. as shown in FIG. 4 (4 :). The conversion to the real address is performed only by specifying “4”, and the user data storage unit 55 of the other node 50 can be accessed without any difference from the access in the own node 10.

As described above, the access to the user data storage unit 15 in the own node 10 can be performed in the own network 1 or in the other network 2 without any difference.

Next, the operation will be described. First, 2
Data transfer between two local devices will be described. FIG. 8 is a diagram showing an example of a user program in which a transfer command between two local devices is incorporated.

In the user program according to the present embodiment, as shown in FIG. 8, "MOV" is used as a transfer command used for transfer in the own node 10, and thereafter, three fields for setting the contents of the command are provided. Is provided. The first field contains the drive number of the transfer source. And “X” indicating the address 0 of the transfer source device X.
0 "in the second field.
And "Y" indicating the address 0 of the transfer destination device Y.
"0" and "5" indicating five points (for five addresses) to be transferred are set in the third field, respectively.

According to this user program, data transfer between local devices is executed in the user data storage unit 15 when an execution instruction is established. That is, the drive No. In the own node 10 of the own network 1 mounted as "0", five points of user data are read from the address 0 of the device X (local device).
(Local device) are transferred to addresses 0 to 4 (see FIG. 1).

Next, data transfer from the local device to the remote device will be described. FIG. 9 is a diagram illustrating an example of a user program in which a transfer command from a local device to a remote device is incorporated.

In the user program according to the present embodiment, as shown in FIG. 9, the transfer command used for transfer to another node is replaced by "MO" instead of the conventional "SEND".
"V" is used, and thereafter, three fields for setting the contents of the instruction are provided in the same manner as in the transfer to the own node described above. The first field contains the source drive N
o. "0" indicating the address of the source device X, "X0" indicating the address of the source device X, and the second field
o. And “Y0” indicating the address 0 of the transfer destination device Y. In the third field, five points (5
"5" is set.

According to this user program, when the execution instruction is established, the user data storage unit 15
Data transfer from the local device to the remote device is performed. That is, the drive No. The user data of five points is read from the address 0 of the device X (local device) of the own node 10 of the own network 1 mounted as 0, and the user data of the five points is read from the bus 2.
04 via the drive No. It is transferred to addresses 0 to 4 of the device Y of the other node 20 (remote device) of the own network 1 mounted as 1 (see FIG. 4).

Next, data transfer from a remote device to a local device will be described. FIG. 10 is a diagram illustrating an example of a user program in which a transfer command from a remote device to a local device is incorporated.

In the user program according to the present embodiment, as shown in FIG. 10, "MOV" is used instead of the conventional "RECV" as a transfer command used for transfer from another node, that is, reception. Are provided with three fields for setting the contents of the command in the same manner as in the transfer to the own node described above. The first field contains the drive number of the transfer source. "4" indicating the transfer destination device X, "X0" indicating the address 0 of the transfer source device X, and the drive number of the transfer destination in the second field. "0" indicating the transfer destination device Y
“Y0” indicating an address and “5” indicating five points (for five addresses) to be transferred are set in the third field, respectively.

According to this user program, when the execution instruction is established, the remote device in the user data storage unit 55 of the node 50 (B2) which is the transfer source transfers the data in the user data storage unit 15 of the own node 10 (A1). Data transfer to the local device is performed. That is, five points of user data are read from the address 0 of the device X (remote device) of the other node 50 of the other network 2, and the user data of the five points is transferred to the line 303 and the relay station 1.
00 (not shown), own network 1 via line 204
0 of device Y (local device) of own node 10
The address is transferred to addresses 4 to 4 (see FIG. 7).

As described above, conventionally, user programs using different notations “MOV”, “SEND”, and “RECV” for transfer instructions have been used, but in the present embodiment,
The instruction notation of “MOV”, “SEND”, and “RECV” is all unified to “MOV”, and the subsequent fields are 3
Only one. That is, the CPU 11 and the OS
Even if the command is a transfer command related to transmission / reception to / from another node, the unit 12
The instruction can be accepted even in the notation “MOV” similar to the transfer instruction in the above.

Therefore, the conventional transfer instruction "SEND"
If the transfer instruction is “MOV”, the NET unit 10
B, a transmission request with another node is made. If the transfer instruction is “MOV” corresponding to the conventional transfer instruction “RECV”, the NET unit 10B makes a reception request with another node. Will do.

As described above, the CPU 11 and the OS unit 12
Means that a message for communication is created in the OS memory unit 13 for the communication request (transmission request, reception request) and transmitted to the NET unit 10B via the bus 19.

Next, the above-mentioned communication request will be described in detail. FIG. 11 is a flowchart illustrating a communication request procedure according to the sequence program according to the present embodiment.
The operation according to the flowchart of FIG.
Is executed under the control of the CPU 11 according to the processing procedure described above, and only the transfer command “MOV” is accepted as a command.

First, in step S1, it is determined whether or not an instruction has been received from a user program stored in the user program storage unit 15. Then, when a determination result that no instruction is received is obtained,
The process shifts to step S2 to execute another processing procedure as a PLC. Thereafter, the process returns to step S1, and waits for reception of an instruction again.

If it is determined in step S1 that a command has been received, the process proceeds to step S3, in which the first and second steps following the received transfer command "MOV" are performed. 2 field indicates the source drive No. And the transfer destination drive No. And analyze.
In this analysis, the source and destination are both drive N
o. It is determined whether it is 0 (0 :) or not. If both are drive No. When a determination result of 0 is obtained, the process proceeds to step S4, and if the instruction is an execution instruction shown in FIG. 8, for example, a local device transfer process as shown in FIG. I do. Thereafter, the process returns to step S1, and waits for reception of an instruction again.

Further, in the determination of step S3, drive N
o. 0 (transfer source) and drive No. If the transfer instruction between transfer destinations 0 and 0 (transfer destination) cannot be confirmed, the process proceeds to the subsequent step S5, where each drive No. of the transfer source and transfer destination is set.
Is a mount parameter registered in the mount parameter storage unit 16. If it is confirmed that the user is not registered, the process proceeds to step S
Then, the process goes to 6 to execute error processing. Thereafter, the process returns to step S1, and waits for reception of an instruction again.

If the registration is confirmed in the determination in step S5, the process proceeds to step S7. In this step S7, the transfer source drive No. 0 to the transfer destination drive No. It is determined whether or not the transfer instruction is other than 0 (No. 1, No. 2, No. 3, or No. 4). Based on the determination, the transfer source drive No. 0 to destination drive N
o. If it is confirmed that the transfer instruction is other than 0, the process proceeds to step S8.

In step S8, a transmission message addressed to the transmission target node is created to perform the remote device transfer processing. For example, the transfer source drive No. 0, the transfer destination is the drive No. If 1, the user program is created as shown in FIG. 9, and in this case, for example, the transfer as shown in FIG. 19 is performed.

For this purpose, from the address 0 of the device X (local device) of the own node 10 of the own network 1 to 5
The user data corresponding to the points is read out, and the user data corresponding to the five points is transferred to the other nodes 20 (remote devices) of the own network 1 via the bus 204.
A transmission message to be transferred to the address is created. This transmission message is stored in the OS memory unit 13. Thereafter, the process proceeds to step S10.

In this case, in the next step S10, O
A transmission message addressed to the transmission target node is read out from the S memory unit 13 and the transmission message is transmitted to the NET via the bus 19.
Processing for transmitting to the unit 10B is executed. Thus, the transmission request from the PLC unit 10A to the NET unit 10B for performing the remote device transfer processing is completed. NET
The unit 10B can access a remote device of another node to be transmitted according to the transmission request received from the PLC unit 10A.

Also, in the determination of step S7, the source drive No. 0 to the destination drive No. If it is confirmed that the instruction is a transfer instruction to 0, the process proceeds to step S9.

In step S9, a reception message addressed to the node to be received is created in order to perform the remote device transfer processing. Transfer source drive No. 4, the transfer destination is the drive No. If it is 0, a user program is created as shown in FIG. 10, and in this case,
For example, transfer as shown in FIG. 21 of the related art is performed.

For this purpose, 5 from the address 0 of the device X (remote device) of the other node 50 of the other network 2
The user data for the points is read, and the user data for the five points is transferred to the line 303, the relay station 100 (not shown), the line 2
For example, a reception message to be transferred to addresses 0 to 4 of the device Y (local device) of the own node 10 of the own network 1 via the network 04 is created. This received message is stored in the OS memory unit 13. Thereafter, the process proceeds to step S1
Move to 0.

In this case, in the next step S10, O
A reception message addressed to the node to be received is read out from the memory unit 13 for S, and the reception message is
Processing for transmitting to the unit 10B is executed. Thus, the reception request from the PLC unit 10A to the NET unit 10B for performing the remote device transfer processing is completed. NET
The unit 10B can access a remote device of another node to be received according to the reception request received from the PLC unit 10A.

As described above, in step S10, N
When the transmission request or the reception request to the ET unit 10B is completed, the process returns to step S1, and waits for reception of an instruction again.

As described above, according to the present embodiment, when data is exchanged between the own node 10 and any one of the other nodes 20, 30, 40, and 50, the mount parameter storage unit 16 Drive No. according to the mount parameter. By specifying the transfer source node and the transfer destination node in the user program, the real addresses of the transfer source and the transfer destination can be obtained. In this case, the transfer command was unified to "MOV".
In a network system, designation of a transfer source node and a transfer destination node is simplified.

As a result, a user program (sequence program) can be easily constructed on the user side without being aware of the existence or real address of another node, thereby facilitating data exchange.

[0101]

As described above, according to the node device of the present invention, the real address is obtained by designating the drive number, so that the user is not conscious of the existence of the other node or the real address. This makes it possible to obtain a node device capable of easily setting a sequence program.

According to the node device of the next invention, the real addresses of the data exchange source and the data exchange destination are obtained simply by specifying the node device of the data exchange source and the node device of the data exchange destination by the drive number. Thus, the designation of the node device of the data exchange source and the node device of the data exchange destination is simplified, whereby the sequence program can be easily assembled on the user side without being aware of the existence of other nodes and the real addresses. There is an effect that a node device capable of performing the operation can be obtained.

According to the network system of the next invention, when data is exchanged between the node devices, the real address is obtained by designating the drive number. An effect is obtained that a network system capable of easily performing data exchange can be obtained by easily forming a sequence program without being aware of the existence and the real address.

According to the network system of the present invention, when data is exchanged between the node devices, the data exchange source node device and the data exchange destination node device are simply designated by the drive numbers. Since each real address of the data exchange destination is obtained, designation of the data exchange source node device and the data exchange destination node device in each node device is simplified.
By simply assembling a sequence program without the user being aware of the existence and real addresses of other nodes, a network system capable of easily exchanging data can be obtained.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a network system according to the present invention.

FIG. 2 is a block diagram showing a typical internal configuration of a PLC for constructing a network system according to the present invention.

FIG. 3 is an explanatory diagram showing a memory configuration of a mount parameter storage unit according to the embodiment.

FIG. 4 is an explanatory diagram showing a concept of a virtual drive for another node of the own network according to the present embodiment.

FIG. 5 is an explanatory diagram showing a concept of a virtual drive for another node of the own network according to the present embodiment.

FIG. 6 is an explanatory diagram showing the concept of a virtual drive for another node in another network according to the present embodiment.

FIG. 7 is an explanatory diagram showing the concept of a virtual drive for another node in another network according to the present embodiment.

FIG. 8 is an explanatory diagram showing an example of a user program incorporating a transfer instruction between two local devices according to the present embodiment.

FIG. 9 is an explanatory diagram showing an example of a user program incorporating a transfer command from a local device to a remote device according to the present embodiment.

FIG. 10 is an explanatory diagram showing an example of a user program incorporating a transfer command from a remote device to a local device according to the present embodiment.

FIG. 11 is a flowchart illustrating a communication request procedure according to a sequence program according to the present embodiment.

FIG. 12 is a block diagram showing a general configuration of a network system.

FIG. 13 is an explanatory diagram showing real addresses used for data exchange of the network system shown in FIG.

FIG. 14 is a block diagram showing a typical internal configuration of a PLC according to a conventional example.

FIG. 15 is a block diagram showing an internal configuration of a user data storage unit according to a conventional example.

FIG. 16 is an explanatory diagram showing an example of a user program incorporating a transfer command between two local devices according to a conventional example.

17 is an explanatory diagram showing a processing image of the user program shown in FIG.

FIG. 18 is an explanatory diagram showing an example of a user program incorporating a transfer command from a local device to a remote device according to a conventional example.

FIG. 19 is an explanatory diagram showing a processing image of the user program shown in FIG. 18;

FIG. 20 is an explanatory diagram showing an example of a user program incorporating a transfer command from a remote device to a local device according to a conventional example.

FIG. 21 is an explanatory diagram showing a processing image of the user program shown in FIG. 20;

FIG. 22 is a flowchart showing a communication request procedure according to a conventional sequence program.

[Explanation of symbols]

10, 20, 30, 40, 50 nodes, 10A, 2
0A, 30A, 40A, 50A PLC part, 11C
PU, 12 OS section, 13 OS memory section, 1
4, 24, 34, 44, 54 user program storage, 15 user data storage, 16 mount parameter storage

Claims (4)

[Claims] 1. A node device applied to a network system for connecting a plurality of networks and exchanging data according to a real address specifying each node device among a plurality of node devices constructing each of the networks. Storage means for storing a drive number corresponding to each of the real addresses; and designating means for designating a target node device for data exchange from among the plurality of node devices using each drive number stored in the storage means. And conversion means for converting the drive number specified by the specification means into a real address corresponding to the specified drive number among the real addresses stored in the storage means. Node device. 2. A method for connecting a plurality of networks to each other and constructing each of the networks between a self-node device and a plurality of other node devices according to a real address for specifying the self-node device and each of the other node devices. In a node device applied to a network system for performing data exchange, storage means for storing a drive number corresponding to each of the real addresses in advance, and the plurality of nodes using each drive number stored in the storage means Designation means for designating a data exchange source node device and a data exchange destination node device from among the devices; and a correspondence between the data exchange source drive number and the data exchange destination drive number designated by the designation means. Data transmission from the own node device to any one of the other node devices, or Determining means for determining whether data is received from any one of the apparatuses to the own node apparatus; and performing data exchange according to the data transmission or data reception determined by the determining means. Conversion means for converting the address into a real address corresponding to each drive number designated by the designation means. 3. A network system for connecting a plurality of networks and exchanging data between a plurality of node devices constructing each of the networks in accordance with a real address for specifying each node device, wherein each of the node devices comprises: Storage means for storing a drive number corresponding to each of the real addresses; and designating means for designating a target node device for data exchange from among the plurality of node devices using each drive number stored in the storage means. And conversion means for converting the drive number specified by the specification means into a real address corresponding to the specified drive number among the real addresses stored in the storage means. Network system. 4. A connection between a plurality of networks, and between the own node device and each of the plurality of other node devices constructing each of the networks, according to a real address for specifying each of the own node device and each of the other node devices. In a network system for exchanging data, the node device includes a storage unit configured to store a drive number corresponding to each of the real addresses in advance, and the plurality of node devices using each drive number stored in the storage unit. A designation unit that designates a data exchange source node device and a data exchange destination node device from among the following, according to the correspondence between the data exchange source drive number and the data exchange destination drive number designated by the designation unit, Whether data transmission from the own node device to any one of the other node devices or the other node device Determining means for receiving data from any one of the nodes to the own node device; and performing data exchange according to the data transmission or data reception determined by the determining means, the real address stored in the storage means. A conversion means for converting the data into a real address corresponding to each drive number designated by the designation means.