WO2018109949A1

WO2018109949A1 - Simulation device, simulation method and simulation program

Info

Publication number: WO2018109949A1
Application number: PCT/JP2016/087684
Authority: WO
Inventors: 洋平安友
Original assignee: 三菱電機株式会社
Priority date: 2016-12-16
Filing date: 2016-12-16
Publication date: 2018-06-21
Also published as: JPWO2018109949A1

Abstract

According to the present invention, a token receiving unit (112) receives a token communicated in a token passing system. A simulation unit (120) determines whether a receiver of a token received by the token receiving unit (112) is a communication device included in the token passing system, and simulates, with a virtual communication device, an operation of the communication device, when the receiver of the token is not the communication device.

Description

Simulation device, simulation method, and simulation program

The present invention relates to a token passing system.

In the Factory Automation system (hereinafter referred to as FA system), a plurality of Programmable Logic Controllers (hereinafter referred to as PLC) are connected to the network. Devices such as robots and sensors are connected to each PLC. Each PLC controls these devices. In the FA system, a token passing system may be used as a communication system. In a token passing system, a data transmission right called a token circulates between a plurality of nodes connected to a network. The node holding the token can transmit data. By using the token passing system in the FA system, each PLC can transmit data at a constant cycle.

There is a technique described in Patent Document 1 as a technique for testing the FA system. In the technique disclosed in Patent Document 1, a virtual PLC and a virtual communication unit that transmits and receives data are provided on a virtual environment. And in the technique of patent document 1, it tests by delaying the communication timing of a virtual communication unit according to the delay time designated by the user.

JP-A-11-73210

In the technique of Patent Document 1, a token token passing system is not physically configured, but a virtual token passing system is constructed. And in the technique of patent document 1, it tests by delaying the communication timing of a virtual communication unit by the delay time designated by the user. However, the delay time specified by the user does not always match the delay time generated in the actual PLC. If the delay time specified by the user does not match the delay time generated in the actual PLC, the delay occurring in the FA system production environment cannot be accurately reproduced in the test.
On the other hand, it is difficult to prepare all the PLCs used in the production environment at the time of the test, and it is desired to perform the test with a configuration of PLCs smaller than that in the production environment. Since the delay that occurs in the FA system is proportional to the number of PLCs, if the number of PLCs is small during the test, the period at which each PLC transmits data (the period at which each PLC acquires a token) is shorter than in the production environment. . For this reason, the time until the data of the control command is transmitted to the devices connected to each PLC will be different between the test and the production environment. In the test, the device was successfully controlled. A situation of failure can occur.

In view of such circumstances, the main object of the present invention is to obtain a configuration capable of performing a test with high accuracy in a token passing system configured with fewer communication devices than a production environment.

The simulation apparatus according to the present invention is
A simulation device included in the token passing system,
A token receiver for receiving a token communicated by the token passing system;
It is determined whether or not the destination of the token received by the token receiving unit is a communication device included in the token passing system. When the destination of the token is not the communication device, the communication is performed as a virtual communication device. A simulation unit that simulates the operation of the device.

In the present invention, the simulation device included in the token passing system simulates the operation of the communication device as a virtual communication device. Therefore, according to the present invention, the operation of a communication device that is not included in the token passing system can be reflected in the test during the test, and the token passing system is configured with fewer communication devices than the production environment. The test can be performed with high accuracy.

1 is a diagram illustrating a system configuration example of a token topology token passing system according to Embodiment 1. FIG. 1 is a diagram illustrating a system configuration example of a line topology token passing system according to Embodiment 1. FIG. 1 is a diagram showing a system configuration example of a ring topology token passing system according to Embodiment 1. FIG. FIG. 3 is a diagram illustrating a hardware configuration example of a master device according to the first embodiment. FIG. 3 is a diagram illustrating a functional configuration example of a master device according to the first embodiment. FIG. 3 is a diagram illustrating a hardware configuration example of a slave device according to the first embodiment. FIG. 3 is a diagram illustrating a functional configuration example of a slave device according to the first embodiment. 1 is a diagram illustrating a system configuration example of a token passing system including a virtual slave device according to Embodiment 1. FIG. 6 is a flowchart showing a procedure A according to the first embodiment. 5 is a flowchart showing a procedure B according to the first embodiment. FIG. 4 is a diagram showing a system configuration example of a star topology token passing system according to a second embodiment. FIG. 4 is a diagram illustrating a hardware configuration example of a simulation apparatus according to a second embodiment. FIG. 4 is a diagram illustrating a functional configuration example of a simulation apparatus according to a second embodiment. FIG. 6 is a diagram illustrating a functional configuration example of a master device according to a second embodiment. 10 is a flowchart showing a procedure B according to the second embodiment. The figure which shows the example of the apparatus management table before the update which concerns on Embodiment 1. FIG. The figure which shows the example of the apparatus management table after the update which concerns on Embodiment 1. FIG.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description of the embodiments and drawings, the same reference numerals denote the same or corresponding parts.

Embodiment 1 FIG.
*** Explanation of configuration ***
FIG. 1 shows a system configuration example of the token passing system according to the first embodiment. Although the network topology of the token passing system in FIG. 1 is a star type, the network topology of the token passing system according to the first embodiment is not limited to the star type.
FIG. 2 shows a system configuration example of a token-passing system having a line topology. FIG. 3 shows an example of the system configuration of a ring topology token passing system.
1 and 2 can be combined to construct a token passing system having a network topology in which a line type and a star type are mixed.
In the following, the token passing system having the network topology of FIG. 1 will be mainly described.

In FIG. 1, a master device 100, a slave device 200, and a slave device 300 are PLCs.
Each of the slave device 200 and the slave device 300 corresponds to a communication device.
In the present embodiment, master device 100 corresponds to a simulation device. Operations performed by the master device 100 correspond to a simulation method and a simulation program.
The master device 100 manages the slave device 200 and the slave device 300. More specifically, the master device 100 manages the transmission destination of the token packet and the data length of the data. In addition, the master device 100 sets management information for notifying the transmission destination and data length of the token packet in the slave device 200 and the slave device 300. The token packet is a packet for delivering a token. Hereinafter, sending a token packet is also called sending a token. In addition, receiving a token packet is also referred to as receiving a token.
The slave device 200 and the slave device 300 are connected to a robot, a sensor, and the like, respectively. The slave device 200 and the slave device 300 perform token transmission and data transmission based on the management information set by the master device 100, respectively.
The master device 100, the slave device 200, and the slave device 300 are each connected to the switching hub 400.
The switching hub 400 relays communication among the master device 100, the slave device 200, and the slave device 300.

FIG. 4 shows a hardware configuration example of the master device 100.
As illustrated in FIG. 4, the master device 100 includes a processor 151, a storage device 152, a communication interface 153, and a device control interface 154.
The master device 100 is a computer.
The processor 151 transmits data. Further, the processor 151 determines whether or not to hold a token. The processor 151 performs a calculation for operating a device management table described later. Further, the processor 151 executes a program for realizing the functions shown in FIG.
The storage device 152 stores a device management table. In addition, the storage device 152 stores a program that implements the functions shown in FIG. Further, the storage device 152 stores data received from the slave device 200 and the slave device 300. The storage device 152 stores data to be transmitted to the slave device 200 and the slave device 300.
The communication interface 153 is an interface for communicating with the slave device 200 and the slave device 300 via the switching hub 400.
The device control interface 154 is an interface for controlling devices such as robots and sensors.
Although only one communication interface 153 is shown in FIG. 4, the master device 100 may include a plurality of communication interfaces 153. Similarly, in FIG. 4, only one device control interface 154 is shown, but the master device 100 may include a plurality of device control interfaces 154.

FIG. 6 shows a hardware configuration example of the slave device 200.
As illustrated in FIG. 6, the slave device 200 includes a processor 251, a storage device 252, a communication interface 253, and a device control interface 254.
The slave device 200 is a computer.
The processor 251 transmits data. Further, the processor 251 determines whether or not to hold a token. Furthermore, the processor 251 executes a program that implements the functions shown in FIG.
The storage device 252 stores a program that implements the functions shown in FIG. The storage device 252 stores data received from the master device 100 and the slave device 300. The storage device 252 stores data to be transmitted to the master device 100 and the slave device 300.
The communication interface 253 is an interface for communicating with the master device 100 and the slave device 300 via the switching hub 400.
The device control interface 254 is an interface for controlling devices such as robots and sensors.
Although only one communication interface 253 is shown in FIG. 6, the slave device 200 may include a plurality of communication interfaces 253. Similarly, in FIG. 6, only one device control interface 254 is shown, but the slave device 200 may include a plurality of device control interfaces 254.
The hardware configuration of the slave device 300 is also as shown in FIG.

FIG. 5 shows a functional configuration example of the master device 100.
The master device 100 includes an initial setting unit 111, a token reception unit 112, a data transmission unit 113, a token transmission unit 114, a data reception unit 115, and a simulation unit 120.
The initial setting unit 111, the token reception unit 112, the data transmission unit 113, the token transmission unit 114, and the data reception unit 115 are functional blocks that realize the function of the master device 100 as a PLC.
The simulation unit 120 is a functional block for the master device 100 to simulate the operation of the slave device.
The simulation unit 120 includes a device management table operation unit 121, a token destination setting unit 122, a virtual device token reception unit 123, a virtual device data transmission unit 124, and a virtual device token transmission unit 125.
The initial setting unit 111, the token receiving unit 112, the data transmitting unit 113, the token transmitting unit 114, the data receiving unit 115, and the simulation unit 120 are realized by a program. When the processor 151 executes these programs, the functions of the initial setting unit 111, the token reception unit 112, the data transmission unit 113, the token transmission unit 114, the data reception unit 115, and the simulation unit 120 are realized.
5 schematically illustrates a state in which the processor 151 is executing a program that realizes the functions of the initial setting unit 111, the token reception unit 112, the data transmission unit 113, the token transmission unit 114, the data reception unit 115, and the simulation unit 120. It represents.
The device management table storage unit 116 stores a device management table. The device management table is, for example, a table shown in FIG. In the device management table, a MAC (Media Access Control) address, a token destination MAC address, and a transmission data length are described for each communication device. Details of the device management table will be described later. The device management table storage unit 116 is realized by the storage device 152.

Next, details of the initial setting unit 111, the token reception unit 112, the data transmission unit 113, the token transmission unit 114, the data reception unit 115, and the device management table storage unit 116 will be described.

The initial setting unit 111 sets information such as the token destination MAC address of the device management table in the slave device 200 and the slave device 300.

The token receiving unit 112 receives a token packet. Then, the token reception unit 112 compares the token destination MAC address described in the received token packet with the MAC address of the master device 100. If the token destination MAC address matches the MAC address of the master device 100, the token receiving unit 112 holds the token. The token receiving unit 112 instructs the data transmitting unit 113 to transmit data.
On the other hand, when the token destination MAC address does not match the MAC address of the master device 100, the token reception unit 112 transfers the token packet to the simulation unit 120.
Note that the token receiving unit 112 receiving a token packet is also referred to as the token receiving unit 112 receiving a token.
The operation of the token reception unit 112 corresponds to token reception processing.

The data transmission unit 113 transmits data to the slave device 200 and the slave device 300 when receiving an instruction from the token reception unit 112. The data transmitted by the data transmission unit 113 includes control information for controlling the slave device 200 and the robot, sensor, and the like connected to the slave device 300.

After the data transmission by the data transmission unit 113 is completed, the token transmission unit 114 refers to the device management table and broadcasts a token packet in which the token destination MAC address of the master device 100 is described. Note that the token transmission unit 114 transmitting a token packet is also referred to as the token transmission unit 114 transmitting a token.

The data receiving unit 115 receives the data transmitted from the slave device 200 and the data transmitted from the slave device 300.

As described above, the device management table storage unit 116 stores a device management table.
In the device management table, as shown in FIG. 16, the MAC address, token destination MAC address, and transmission data length are described for each communication device. FIG. 16 shows a device management table when the token circuit is master device 100 → slave device 200 → slave device 300 → master device 100. The token circuit is a token passing path.
The MAC address column describes the MAC address assigned to each communication device.
In the column of the token destination MAC address, the MAC address assigned to the destination communication device of the token packet is described. For example, “BB: BB: BB: BB: BB: BB” is described in the token destination MAC address column of the master device 100. That is, the master device 100 transmits a token packet with the slave device 200 as a destination.
In the column of transmission data length, the data length of data transmitted by each communication device is described. For example, “10 bytes” is described in the transmission data length column of the master device 100. That is, the master device 100 transmits 10-byte data to the slave device 200 and the slave device 300.

Next, details of the simulation unit 120 will be described.

The simulation unit 120 changes the setting of the selected communication device so that a token destined for the virtual communication device is transmitted from the selected communication device selected from the plurality of communication devices included in the token passing system. The virtual communication device is a virtual slave device that is simulated by the master device. Hereinafter, the virtual communication device is referred to as a slave device 500. The slave device 500 is virtually added to the token passing system at the position shown in FIG.
Here, in the token passing system of FIG. 1, it is assumed that the token circulation circuit is master device 100 → slave device 200 → slave device 300 → master device 100.
For example, the simulation unit 120 selects the slave device 200 as the selected communication device, and changes the setting of the slave device 200 so that a token is transmitted from the slave device 200 to the slave device 500.
In addition, the simulation unit 120 determines whether the destination of the token packet transferred from the token reception unit 112 is any of a plurality of communication devices included in the token passing system. That is, the simulation unit 120 determines whether the token destination is the slave device 200 or the slave device 300. The simulation unit 120 operates the slave device 200 or the slave device 300 as a virtual communication device when the token destination is neither the slave device 200 nor the slave device 300, that is, when the token destination is the slave device 500. Simulate.
The operation of the simulation unit 120 corresponds to simulation processing.

In the simulation unit 120, the device management table operation unit 121 changes the device management table.
As described above, when the token is transmitted from the slave device 200 to the slave device 500 as the destination, the device management table operation unit 121 updates the device management table of FIG. 16 as illustrated in FIG.
In the device management table of FIG. 17, a real identifier column is added.
In addition, a record of the slave device 500 that is a virtual communication device is added.
In FIG. 17, the part surrounded by the broken line is an additional part from FIG.
In the real identifier column, “True” is described for a communication device included in the token passing system. On the other hand, if the communication device (virtual communication device) is not included in the token passing system, “False” is described.
In the example of FIG. 17, “True” is described for the master device 100, the slave device 200, and the slave device 300, but “False” is described for the slave device 500.

The token destination setting unit 122 sets a token destination MAC address described in the device management table for all communication devices included in the token passing system.
That is, the token destination setting unit 122 sets the token destination MAC address “CC: CC: CC: CC: CC” for the slave device 200 if the device management table is in the state shown in FIG. Further, the token destination setting unit 122 sets the token destination MAC address “AA: AA: AA: AA: AA” for the slave device 300.
When the device management table is updated to the state shown in FIG. 17 by the device management table operation unit 121, the token destination setting unit 122 sends the token destination MAC address “DD: DD: DD: DD: DD” to the slave device 200. Set. That is, the token destination setting unit 122 changes the setting of the slave device 200 so that the slave device 200 transmits a token destined for the slave device 500.

When the token packet received by the token receiving unit 112 is transferred from the token receiving unit 112, the virtual device token receiving unit 123 collates the token destination MAC address described in the token packet with the MAC address of the device management table. . When the token destination MAC address matches the MAC address of the slave device 500, the virtual device token reception unit 123 holds the token as the slave device 500.
Then, the virtual device token receiving unit 123 instructs the virtual device data transmitting unit 124 to transmit data as the slave device 500. That is, the virtual device token reception unit 123 instructs the virtual device data transmission unit 124 to behave as the slave device 500 that is a virtual communication device.
On the other hand, when the token destination MAC address does not match the MAC address of the slave device 500, the token reception unit 211 discards the token packet.

When there is an instruction from the virtual device token receiving unit 123, the virtual device data transmission unit 124 generates data having a data length that matches the data length of the slave device 500 in the device management table, and broadcasts the generated data.

After the data transmission by the virtual device data transmission unit 124 is completed, the virtual device token transmission unit 125 refers to the device management table and broadcasts a token packet in which the token destination MAC address of the slave device 500 is described.
Note that the virtual device token transmission unit 125 transmitting the token packet is also referred to as the virtual device token transmission unit 125 transmitting the token.

The token reception unit 112 receives a token packet, the data transmission unit 113 transmits data, the token transmission unit 114 transmits a token, the data reception unit 115 receives data, the virtual device data transmission unit 124 transmits data, The token transmission by the virtual device token transmission unit 125 is performed by the communication interface 153 of FIG.

FIG. 7 shows a functional configuration example of the slave device 200.

The token receiving unit 211 receives a token packet. Then, the token receiving unit 211 compares the token destination MAC address described in the received token packet with the MAC address of the slave device 200.
If the token destination MAC address matches the MAC address of the slave device 200, the token receiving unit 211 holds the token. The token reception unit 211 instructs the data transmission unit 212 to transmit data.
On the other hand, when the token destination MAC address does not match the MAC address of the slave device 200, the token receiving unit 211 discards the token packet. Note that the token receiving unit 211 receiving a token packet is also referred to as the token receiving unit 211 receiving a token.

The data transmission unit 212 transmits data to the master device 100, the slave device 300, and the slave device 500 when instructed by the token reception unit 211.

The token transmission unit 213 broadcasts a token packet in which the token destination MAC address is described after the data transmission by the data transmission unit 212 is completed.
Note that the token transmission unit 213 transmits a token packet, and the token transmission unit 213 also transmits a token.

The data receiving unit 214 receives data transmitted from the master device 100 and the slave device 300.

Note that the token reception unit 211 receives a token packet, the data transmission unit 212 transmits data, the token transmission unit 213 transmits a token, and the data reception unit 214 receives data. The communication interface 253 in FIG.
The functional configuration of the slave device 300 is also as shown in FIG.

*** Explanation of operation ***
Next, an operation example of the master device 100 will be described. Hereinafter, an example in which the master device 100 behaves as the slave device 500 in FIG. 8 by simulating the operation of the slave device 200 or the slave device 300 will be described.
The operation of the master device 100 is divided into procedure A and procedure B. In procedure A, the device management table is updated and the communication device is set based on the updated device management table. In the procedure B, the token is received, the original operation of the master device 100 and the operation of the slave device 500 are performed.
FIG. 9 is a flowchart showing the procedure A, and FIG. 10 is a flowchart showing the procedure B.

First, the procedure A will be described with reference to FIG.

In step S1, the device management table operation unit 121 updates the device management table.
More specifically, the operator of the master device 100 inputs information surrounded by a broken line in FIG. Then, the device management table operation unit 121 updates the device management table as shown in FIG. 17 based on the information input from the operator. That is, the device management table operation unit 121 adds a record of the slave device 500 that is a virtual slave device, adds a real identifier column, and changes the token destination MAC address of the slave device 200.

Next, in step S2, the token destination setting unit 122 sets the token destination MAC address of the device management table to the corresponding slave device.
In the example of FIG. 17, the token destination setting unit 122 sets a new token destination MAC address “DD: DD: DD: DD: DD” in the slave device 200.
Here, the token destination setting unit 122 sets a new token destination MAC address only to the slave device 200 whose token destination MAC address is changed, but the token destination setting unit 122 The token destination MAC address “AA: AA: AA: AA: AA” may be set also in the slave device 300 whose MAC address is not changed.

Next, the procedure B will be described with reference to FIG.

When the token receiving unit 112 receives the token packet, in step S3, the token receiving unit 112 determines whether or not the token destination is the master device 100.
Specifically, the token receiving unit 112 compares the token destination MAC address included in the token packet with the MAC address of the master device 100 in the device management table.

When the token destination MAC address matches the MAC address of the master device 100, that is, when the token destination MAC address is “AA: AA: AA: AA: AA: AA”, the token reception unit 112 in step S4 , Hold the token. The token reception unit 112 instructs the data transmission unit 113 to transmit data.

Next, in step S5, the data transmission unit 113 broadcasts the data of the master device 100.

When the data transmission by the data transmission unit 113 is completed, the token transmission unit 114 transmits the token packet to the token destination of the master device 100 in step S6.
More specifically, the token transmission unit 114 broadcasts a token packet in which “BB: BB: BB: BB: BB: BB”, which is the token destination MAC address of the master device 100 in the device management table, is described.

If the token destination MAC address does not match the MAC address of the master device 100 in step S3, the token receiving unit 112 transfers the token packet to the simulation unit 120. In step S7, the virtual device token receiving unit 123 determines whether or not the communication device that is the destination of the token actually exists.
More specifically, the virtual device token receiving unit 123 searches the device management table for a MAC address that matches the token destination MAC address. Then, the virtual device token receiving unit 123 determines whether the real identifier described in the MAC address record that matches the token destination MAC address is “True” or “False”.
When the MAC address that matches the token destination MAC address is “BB: BB: BB: BB: BB: BB” or “CC: CC: CC: CC: CC: CC”, the real identifier is “True”. .
In this case, the virtual device token receiving unit 123 discards the received token packet in step S8.

On the other hand, when the real identifier described in the MAC address record that matches the token destination MAC address is “False”, the virtual device token receiving unit 123 holds the token as the slave device 500 in step S9. That is, when the MAC address that matches the token destination MAC address is “DD: DD: DD: DD: DD: DD”, the virtual device token receiving unit 123 holds the token as the slave device 500.
Further, the virtual device token receiving unit 123 instructs the virtual device data transmitting unit 124 to transmit data.

Next, in step S10, the virtual device data transmission unit 124 broadcasts data of the slave device 500.

When the data transmission by the virtual device data transmission unit 124 is completed, the virtual device token transmission unit 125 transmits the token packet to the token destination of the slave device 500 in step S11.
More specifically, the virtual device token transmission unit 125 broadcasts a token packet in which “CC: CC: CC: CC: CC: CC”, which is the token destination MAC address of the slave device 500 in the device management table, is described. .

*** Explanation of the effect of the embodiment ***
As described above, in the present embodiment, the master device 100 behaves as the slave device 500 that does not exist during the test.
Therefore, according to the present embodiment, the slave device 500 and the devices connected to the slave device 500 are not prepared without preparing the slave device 500 and the devices (robots, sensors, etc.) connected to the slave device 500. The operation can be reflected in the test. That is, according to the present embodiment, the test can be performed under the same conditions as in the production environment.

Embodiment 2. FIG.
In the first embodiment, the master device 100 behaves as a slave device 500 that is a virtual slave device. In the present embodiment, an example in which devices other than the master device 100, the slave device 200, and the slave device 300 behave as the slave device 500 will be described.
Hereinafter, differences from the first embodiment will be mainly described.
Matters not described below are the same as those in the first embodiment.

*** Explanation of configuration ***
FIG. 11 shows a system configuration example of the token passing system according to the second embodiment. The network topology of the token passing system in FIG. 11 is a star type, but the network topology is not limited to the star type. As in the first embodiment, the network topology of the token passing system may be any of a ring type, a line type, and a combination of a line type and a star type.

In the configuration of FIG. 11, a simulation apparatus 600 is added as compared to the configuration shown in FIG.
The slave device 200 and the slave device 300 are the same as those described in the first embodiment.
The simulation apparatus 600 performs the operation of the simulation unit 120 described in the first embodiment. That is, the simulation apparatus 600 simulates the operation of a slave device as a virtual communication device. Hereinafter, the simulation device 600 behaves as the slave device 500 by simulating the operation of the slave device 200 or the slave device 300.
On the other hand, the master device 100 does not perform the operation of the simulation unit 120 described in the first embodiment in the present embodiment. That is, the master device 100 functions as a communication device in the present embodiment.
The switching hub 400 relays communication among the master device 100, the slave device 200, the slave device 300, and the simulation apparatus 600.

FIG. 12 shows a hardware configuration example of the simulation apparatus 600.
As illustrated in FIG. 12, the simulation apparatus 600 includes a processor 651, a storage device 652, and a communication interface 653.
The simulation apparatus 600 is a computer.
The processor 651 transmits data. Further, the processor 651 determines whether or not to hold a token. The processor 651 performs a calculation for operating a device management table described later. Further, the processor 651 executes a program for realizing the functions shown in FIG.
The storage device 652 stores a device management table. In addition, the storage device 652 stores a program that implements the functions illustrated in FIG. The storage device 652 stores data to be transmitted to the master device 100, the slave device 200, and the slave device 300.
The communication interface 653 is an interface for communicating with the slave device 200 and the slave device 300 via the switching hub 400.
Although only one communication interface 653 is shown in FIG. 12, the master device 100 may include a plurality of communication interfaces 653.

FIG. 13 shows a functional configuration example of the simulation apparatus 600.
The simulation device 600 includes a token reception unit 112 and a simulation unit 120.
The token receiving unit 112 and the simulation unit 120 are the same as those shown in the first embodiment. The simulation unit 120 is a functional block for the simulation apparatus 600 to simulate a slave device.
The token receiving unit 112 and the simulation unit 120 are realized by a program. The functions of the token receiving unit 112 and the simulation unit 120 are realized by the processor 651 executing the program.
FIG. 13 schematically illustrates a state in which the processor 651 is executing a program that realizes the functions of the token reception unit 112 and the simulation unit 120.
The simulation unit 120 includes a device management table operation unit 121, a token destination setting unit 122, a virtual device token reception unit 123, a virtual device data transmission unit 124, and a virtual device token transmission unit 125.
The device management table operation unit 121, token destination setting unit 122, virtual device token reception unit 123, virtual device data transmission unit 124, and virtual device token transmission unit 125 in FIG. 13 are the same as those described in the first embodiment. Therefore, these descriptions are omitted.
The device management table storage unit 615 stores a device management table. Since the device management table is the same as that described in the first embodiment, description of the device management table is omitted. The device management table storage unit 615 is realized by the storage device 652.

FIG. 14 shows a functional configuration example of the master device 100.
In the present embodiment, the master device 100 includes only an initial setting unit 111, a token reception unit 112, a data transmission unit 113, a token transmission unit 114, a data reception unit 115, and a device management table storage unit 116. That is, master device 100 according to the present embodiment does not include simulation unit 120.
Since the initial setting unit 111, token reception unit 112, data transmission unit 113, token transmission unit 114, data reception unit 115, and device management table storage unit 116 in FIG. 14 are the same as those described in the first embodiment, These descriptions are omitted.

Note that the hardware configuration of the master device 100 of the second embodiment is as shown in FIG. The hardware configurations of the slave device 200 and the slave device 300 of the second embodiment are as shown in FIG. The functional configurations of the slave device 200 and the slave device 300 of the second embodiment are as shown in FIG.

*** Explanation of operation ***
Next, an operation example of the simulation apparatus 600 will be described.
The operation of the simulation apparatus 600 is divided into a procedure A and a procedure B. In procedure A, the device management table is updated and the communication device is set based on the updated device management table. In the procedure B, the token is received, the original operation of the master device 100 and the operation of the slave device 500 are performed.
The simulation unit 120 of the simulation apparatus 600 performs the procedure A according to FIG. Since the details of FIG. 9 have been described in the first embodiment, the details of FIG. 9 are not described. If the token destination MAC address of the master device 100 has been updated, the token destination setting unit 122 sets the updated token destination MAC address in the master device 100 in step S2.

Next, the procedure B will be described with reference to FIG.

When the token receiving unit 112 receives the token packet, the token receiving unit 112 transfers the token packet to the virtual device token receiving unit 123.
In step S12, the virtual device token receiving unit 123 determines whether or not the token destination node actually exists.
More specifically, the virtual device token receiving unit 123 searches the device management table for a MAC address that matches the token destination MAC address. Then, the virtual device token receiving unit 123 determines whether the real identifier described in the MAC address record that matches the token destination MAC address is “True” or “False”.
The MAC address that matches the token destination MAC address is “AA: AA: AA: AA: AA: AA”, “BB: BB: BB: BB: BB: BB” or “CC: CC: CC: CC: CC: CC” ", The real identifier is" True ".
In this case, the virtual device token receiving unit 123 discards the received token packet in step S13.

On the other hand, when the real identifier described in the MAC address record that matches the token destination MAC address is “False”, the virtual device token receiving unit 123 holds the token as the slave device 500 in step S14. That is, when the MAC address that matches the token destination MAC address is “DD: DD: DD: DD: DD: DD”, the virtual device token receiving unit 123 holds the token as the slave device 500.
Further, the virtual device token receiving unit 123 instructs the virtual device data transmitting unit 124 to transmit data.

Next, in step S15, the virtual device data transmitting unit 124 broadcasts data of the slave device 500.

When the data transmission by the virtual device data transmission unit 124 is completed, the virtual device token transmission unit 125 transmits a token packet to the token destination of the slave device 500 in step S16.
More specifically, the virtual device token transmission unit 125 broadcasts a token packet in which “CC: CC: CC: CC: CC: CC”, which is the token destination MAC address of the slave device 500 in the device management table, is described. .

*** Explanation of the effect of the embodiment ***
As described above, in the present embodiment, the simulation device 600 simulates the operation of the slave device 500 that does not exist during the test.
Therefore, according to the present embodiment, the slave device 500 and the devices connected to the slave device 500 are not prepared without preparing the slave device 500 and the devices (robots, sensors, etc.) connected to the slave device 500. The operation can be reflected in the test. That is, according to the present embodiment, the test can be performed under the same conditions as in the production environment.
Also, by simulating the slave device 500 by the simulation device 600 instead of the master device 100, the load on the master device 100 can be reduced.

Although the embodiments of the present invention have been described above, these two embodiments may be combined and implemented.
Alternatively, one of these two embodiments may be partially implemented.
Alternatively, these two embodiments may be partially combined.
In addition, this invention is not limited to these embodiment, A various change is possible as needed.

*** Explanation of hardware configuration ***
Finally, a supplementary explanation of the hardware configuration of the master device 100 and the simulation apparatus 600 will be given.
The processor 151 and the processor 651 are integrated circuits (ICs) that perform processing.
The processor 151 and the processor 651 are a CPU (Central Processing Unit) and a DSP (Digital Signal Processor), respectively.
The storage device 152 and the storage device 652 are a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, a HDD (Hard Disk Drive), and the like.
The communication interface 153 and the communication interface 653 each include a receiver that receives data and a transmitter that transmits data.
Each of the communication interface 153 and the communication interface 653 is, for example, a communication chip or a NIC (Network Interface Card).

The storage device 152 also stores an OS (Operating System).
At least a part of the OS is executed by the processor 151.
In the first embodiment, the processor 151 executes the functions of the initial setting unit 111, the token reception unit 112, the data transmission unit 113, the token transmission unit 114, the data reception unit 115, and the simulation unit 120 while executing at least a part of the OS. Execute the program to be realized.
When the processor 151 executes the OS, task management, memory management, file management, communication control, and the like are performed.
In addition, information, data, signal values, and variable values indicating the processing results of the initial setting unit 111, token receiving unit 112, data transmitting unit 113, token transmitting unit 114, data receiving unit 115, and simulation unit 120 are stored in the storage device 152. And stored in at least one of a register and a cache memory in the processor 151.
The programs for realizing the functions of the initial setting unit 111, the token receiving unit 112, the data transmitting unit 113, the token transmitting unit 114, the data receiving unit 115, and the simulation unit 120 are a magnetic disk, a flexible disk, an optical disk, a compact disk, a Blu-ray disc. It may be stored in a portable storage medium such as a (registered trademark) disk or DVD.

The storage device 652 also stores an OS.
Then, at least a part of the OS is executed by the processor 651.
The processor 651 executes a program that realizes the functions of the token receiving unit 112 and the simulation unit 120 while executing at least a part of the OS.
When the processor 651 executes the OS, task management, memory management, file management, communication control, and the like are performed.
Further, information, data, signal values, and variable values indicating the processing results of the token receiving unit 112 and the simulation unit 120 are stored in at least one of the storage device 652, the register in the processor 651, and the cache memory.
In addition, programs that realize the functions of the token receiving unit 112 and the simulation unit 120 may be stored in a portable storage medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, and a DVD.

In addition, the “setting” of the initial setting unit 111, the token receiving unit 112, the data transmitting unit 113, the token transmitting unit 114, the data receiving unit 115, and the simulating unit 120 is referred to as “circuit” or “process” or “procedure” or “processing”. May be read as "."
The master device 100 and the simulation apparatus 600 may be implemented by an electronic circuit such as a logic IC (Integrated Circuit), a GA (Gate Array), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array).
The processor and the electronic circuit are also collectively referred to as a processing circuit.

100 master device, 111 initial setting unit, 112 token reception unit, 113 data transmission unit, 114 token transmission unit, 115 data reception unit, 116 device management table storage unit, 120 simulation unit, 121 device management table operation unit, 122 token destination Setting unit, 123 Virtual device token receiving unit, 124 Virtual device data transmitting unit, 125 Virtual device token transmitting unit, 151 Processor, 152 Storage device, 153 Communication interface, 154 Device control interface, 200 Slave device, 211 Token receiving unit, 212 Data transmission unit, 213 token transmission unit, 214 data reception unit, 251 processor, 252 storage device, 253 communication interface, 254 device control interface, 300 slave device 400 switching hub 500 slave device 600 simulator, 615 device management table storage unit, 651 a processor, 652 a storage device, 653 communication interface.

Claims

A simulation device included in the token passing system,
A token receiver for receiving a token communicated by the token passing system;
It is determined whether or not the destination of the token received by the token receiving unit is a communication device included in the token passing system. When the destination of the token is not the communication device, the communication is performed as a virtual communication device. A simulation apparatus having a simulation unit that simulates the operation of the device.
The simulation unit
The simulation apparatus according to claim 1, wherein the setting of the communication device is changed so that a token destined for the virtual communication device is transmitted from the communication device.
The token passing system includes a slave device as the communication device,
The simulation device according to claim 1, wherein the simulation device is a master device that manages the slave device.
The token passing system includes a master device and a slave device as a plurality of communication devices,
The simulation device according to claim 1, wherein the simulation device is a device different from the master device and the slave device.
The token receiver
Receiving the token in a test against the token passing system;
The simulation unit
In the test for the token passing system, it is determined whether the destination of the token received by the token receiving unit is the communication device, and when the destination of the token is not the communication device, the virtual communication device The simulation apparatus according to claim 1, which simulates the operation of the communication device.
A computer included in the token passing system receives a token communicated in the token passing system;
When the computer determines whether the received token destination is a communication device included in the token passing system, and the token destination is not the communication device, the communication device is used as a virtual communication device. A simulation method for simulating the operation of a computer.
To the computer included in the token passing system,
A token reception process for receiving a token communicated by the token passing system;
It is determined whether the destination of the token received by the token reception process is a communication device included in the token passing system. When the destination of the token is not the communication device, the communication is performed as a virtual communication device. A simulation program that executes a simulation process that simulates the operation of a device.