Relay device, relay method, and relay program

Abstract

The challenge is to reduce the overall communication volume of the system. [Solution] The relay device includes a first communication unit that communicates with a first device connected to a first link, a second communication unit that communicates with a second device connected to a second link, a communication control unit that receives software from the first device that is to be transmitted to the second device and stores the received software in a storage unit, and an update control unit that updates the software of the second device by transmitting the software stored in the storage unit to the second device.

Description

Technical Field

[0001] The present invention relates to a relay device, a relay method, and a relay program.

Background Art

[0002] In a conventional system, a host and field devices are connected by a link, and an operator uses the host to acquire sensor values measured by the field devices. Also, the operator uses the host to update the software of the field devices. When there are multiple links, a relay device is used to connect each link.

[0003] FIG. 16 is a diagram for explaining a conventional system. As shown in FIG. 16, a conventional system 10 includes hosts 11a, 11b, a relay device 12, and field devices 13a-1, 13a-2, 13b, 13c-1, 13c-2. The hosts 11a, 11b, the relay device 12, and the field devices 13c-1, 13c-2 are connected to a first link L1. The relay device 12 and the field devices 13a-1, 13a-2, 13b are connected to a second link L2.

[0004] The hosts 11a, 11b are PCs (Personal Computers) used by an operator, and are used to acquire sensor values from the field devices 13a-1, 13a-2, 13b, 13c-1, 13c-2 and to update the software. The field devices 13a-1, 13a-2, 13b, 13c-1, 13c-2 are sensors or the like.

[0005] The field devices 13a-1, 13a-2 are the same field devices. The field devices 13c-1, 13c-2 are the same field devices. In the following description, the field devices 13a-1, 13a-2 are collectively referred to as the field device 13a as appropriate. The field devices 13c-1, 13c-2 are collectively referred to as the field device 13c as appropriate.

[0006] When hosts 11a, 11b and field device 13c connected to the first link L1 communicate with each other, the first link L1 is used. On the other hand, when hosts 11a, 11b and field device 13c connected to the first link L1 communicate with field devices 13a and 13b connected to the second link L2, communication is performed via the relay device 12.

[0007] Generally, since the first link L1 and the second link L2 have different communication protocols and communication speeds, the relay device 12 performs communication conversion between the first link L1 and the second link L2. The relay device 12 is an I / O device, etc.

[0008] For example, when host 11a updates the software of field device 13a, it sends the downloadable software 5 to field device 13a via relay device 12. Even for identical field devices, software updates are performed for each field device, so when host 11a updates field device 13a, it sends the software 5 to field devices 13a-1 and 13a-2, respectively. [Prior art documents] [Patent Documents]

[0009] [Patent Document 1] Japanese Patent Publication No. 2005-122591 [Overview of the project] [Problems that the invention aims to solve]

[0010] In the conventional technology described above, if there are multiple identical field devices, the software for download is sent to each field device. As a result, the communication bandwidth of the first link L1 and the second link L2 is occupied by the software transmission while the software is being transmitted.

[0011] As a result, for example, while host 11a is updating the software of field device 13a, communication between host 11a, 11b and field device 13c connected to the first link L1 will be restricted, requiring a reduction in the overall communication volume of the system.

[0012] One objective is to provide a relay device, relay method, and relay program that can reduce the overall communication volume of the system. [Means for solving the problem]

[0013] The relay device on one side includes a first communication unit that communicates with a first device connected to a first link, a second communication unit that communicates with a second device connected to a second link, a communication control unit that receives software from the first device that is to be transmitted to the second device and stores the received software in a storage unit, and an update control unit that updates the software of the second device by transmitting the software stored in the storage unit to the second device.

[0014] The relay method on one side involves a first communication unit that communicates with a first device connected to a first link, and a second communication unit that communicates with a second device connected to a second link. The computer receives software destined for the second device from the first device, stores the received software in a storage unit, and transmits the software stored in the storage unit to the second device, thereby updating the software of the second device.

[0015] The relay program on one side uses a first communication unit that communicates with a first device connected to a first link and a second communication unit that communicates with a second device connected to a second link to receive software from the first device that is destined to send to the second device, store the received software in a storage unit, and transmit the software stored in the storage unit to the second device, thereby causing the computer to execute a process to update the software of the second device. [Effects of the Invention]

[0016] According to one embodiment, the communication volume of the entire system can be reduced.

Brief Description of Drawings

[0017] [Figure 1] It is a functional block diagram showing the configuration of a conventional relay device. [Figure 2] It is a flowchart (1) showing the process of software download in the prior art. [Figure 3] It is a flowchart (2) showing the process of software download in the prior art. [Figure 4] It is a diagram showing the system of Embodiment 1. [Figure 5] It is a functional block diagram showing the functional configuration of the relay device according to Embodiment 1. [Figure 6] It is a diagram showing an example of the data structure of the device list. [Figure 7] It is a flowchart (1) showing the process of software download in Embodiment 1. [Figure 8] It is a flowchart (2) showing the process of software download in Embodiment 1. [Figure 9] It is a diagram showing the system of Embodiment 2. [Figure 10] It is a functional block diagram showing the functional configuration of the relay device according to Embodiment 2. [Figure 11] It is a flowchart (1) showing the process of software download in Embodiment 2. [Figure 12] It is a flowchart (2) showing the process of software download in Embodiment 2. [Figure 13] It is a functional block diagram showing the configuration of the relay device according to other embodiments. [Figure 14] It is a diagram showing an example of the data structure of the device list according to other embodiments. [Figure 15] It is a diagram for explaining an example of hardware configuration. [Figure 16] It is a diagram for explaining the prior art system. [Modes for carrying out the invention]

[0018] The following describes in detail, with reference to the drawings, embodiments of the relay device, relay method, and relay program disclosed herein. However, the present invention is not limited by these embodiments. Furthermore, the same elements are denoted by the same reference numerals, redundant descriptions are omitted as appropriate, and each embodiment can be combined as appropriate within a non-contradictory range.

[0019] (Embodiment 1) (Supplementary explanation of conventional technology) Before describing Embodiment 1, we will provide supplementary information on the prior art. First, we will describe an example of the configuration of the conventional relay device 12 shown in Figure 16. Figure 1 is a functional block diagram showing the configuration of the conventional relay device.

[0020] As shown in Figure 1, the relay device 12 includes a first communication unit 12a, a second communication unit 12b, and a conversion unit 12c.

[0021] The first communication unit 12a communicates with hosts 11a, 11b and field devices 13c connected to the first link L1, based on the communication speed and communication protocol of PROFIBUS-DP or the like. When the first communication unit 12a receives data destined for field devices 13a, 13b on the second link L2, it outputs the received data to the conversion unit 12c.

[0022] The second communication unit 12b communicates with field devices 13a and 13b connected to the second link L2 using a communication speed and communication protocol based on PROFIBUS-PA or the like. When the second communication unit 12b receives data destined for hosts 11a and 11b or field device 13c on the first link L2, it outputs the received data to the conversion unit 12c.

[0023] The conversion unit 12c converts the communication between the first link L1 and the first link L2. For example, when the conversion unit 12c receives data from the first communication unit 12a, it converts the data's communication speed and communication protocol to the communication speed and communication protocol of the second link L2 and outputs it to the second communication unit 12b. On the other hand, when the conversion unit 12c receives data from the second communication unit 12b, it converts the data's communication speed and communication protocol to the communication speed and communication protocol of the first link L1 and outputs it to the first communication unit 12a.

[0024] Next, we will describe the software download process for system 10 as explained in Figure 16. Here, we will describe the case where host 11a transmits software to field device 13a. For example, in the conventional software download process, the process is carried out in the order of step 1, step 2, and step 3.

[0025] The first step is described below. Host 11a sends a command to field device 13a instructing it to start the download. In the following description, the command instructing the start of the download will be referred to as the "download start command". Upon receiving the command, field device 13a prepares to download. Once host 11a has finished preparing field device 13a for the download, it proceeds to the second step.

[0026] The second step will now be explained. Host 11a sends the download software to the field device 13a. Because the download software is large and cannot be sent all at once, Host 11a divides it into multiple communication frames and sends them to the field device 13a. Once Host 11a has finished sending the download software, it moves on to the third step.

[0027] The third step will now be explained. Host 11a sends a command to field device 13a instructing it to switch software. In the following explanation, the command instructing the software to switch software will be referred to as the "software switching command". Upon receiving the command, field device 13a updates its software to the new software received in step 2 and starts up. From this point onward, field device 13a operates with the new software.

[0028] Figures 2 and 3 are flowcharts illustrating the process of downloading software using conventional technology. The examples shown in Figures 2 and 3 describe the case where host 11a sends downloadable software to field device 13a. The "Download Read Status Read Command" shown in Figures 2 and 3 is a command that queries the field device for the download read status. The "Sensor Value Read Command" is a command that queries the field device for the sensor value. The "Download Complete Status Read Command" is a command that queries the field device for the download complete status. Furthermore, Download (New Software #1) to Download (New Software #n) show how the divided downloadable data is sent to the field device.

[0029] First, let's explain Figure 2. Host 11a sends a Download Start command to field device 13a-1 via relay device 12. When field device 13a-1 receives the Download Start command, it sends an acknowledgment to host 11a via relay device 12 and prepares for the download (step S10).

[0030] Host 11a repeatedly sends a Download Read status command to field device 13a-1 via relay device 12 until field device 13a-1 is ready for download. When field device 13a-1 is ready for download, it sends an acknowledgment of readiness to host 11a via relay device 12 (step S11).

[0031] The host 11a and field devices 13a-1 and 13a-2 transmit and receive various types of data via the relay device 12, but in the explanation from step S12 onward, the phrase "via the relay device 12" will be omitted. As described above, the relay device 12 converts the communication between the first link L1 and the first link L2.

[0032] When host 11a receives a "ready" message from field device 13a-1, it divides the download software into segments and sends them to field device 13a-1. Each time field device 13a-1 receives a segment of the software, it sends an acknowledgment to host 11a. Host 11a and field device 13a-1 repeat this process until all of the download software has been sent. Once field device 13a-1 has received all of the download software, it enters a "Download complete" state (step S12).

[0033] Once host 11a has finished sending all the software for download, it sends a Download complete status Read command to field device 13a-1. Upon receiving the Download complete status Read command, field device 13a-1 sends a Download complete message to host 11a (step S13).

[0034] Host 11a sends a software switch command to field device 13a-1. Upon receiving the software switch command, field device 13a-1 updates its software to the new software and restarts (step S14).

[0035] While the host 11a is performing the process in step S12, it periodically executes a process to acquire sensor values ​​from field devices 13a-1 and 13a-2. For example, the host 11a sends a sensor value Read command to field device 13a-1, and field device 13a-1 sends the sensor value to the host 11a (step S12a). The host 11a sends a sensor value Read command to field device 13a-2, and field device 13a-2 sends the sensor value to the host 11a (step S12b).

[0036] Next, we will move on to the explanation of Figure 3. Host 11a sends a Download Start command to field device 13a-2. Upon receiving the Download Start command, field device 13a-2 sends an acknowledgment to host 11a and prepares for the download (step S15).

[0037] Host 11a repeatedly sends a Download Read status command to field device 13a-1 until field device 13a-2 is ready for download. When field device 13a-2 is ready for download, it sends an acknowledgment to host 11a indicating that it is ready (step S16).

[0038] When host 11a receives a "ready" message from field device 13a-2, it divides the download software into segments and sends them to field device 13a-2. Each time field device 13a-2 receives a segment of the software, it sends an acknowledgment to host 11a. Host 11a and field device 13a-2 repeat this process until all of the download software has been sent. Once field device 13a-2 has received all of the download software, it enters a "Download complete" state (step S17).

[0039] Once host 11a has finished sending all the software for download, it sends a Download complete status Read command to field device 13a-2. When field device 13a-2 receives the Download complete status Read command, it sends a Download complete message to host 11a (step S18).

[0040] Host 11a sends a software switch command to field device 13a-2. Upon receiving the software switch command, field device 13a-2 updates its software to the new software and restarts (step S19).

[0041] While the host 11a is performing the process in step S17, it periodically executes a process to acquire sensor values ​​from field devices 13a-1 and 13a-2. For example, the host 11a sends a sensor value Read command to field device 13a-1, and field device 13a-1 sends the sensor value to the host 11a (step S17a). The host 11a sends a sensor value Read command to field device 13a-2, and field device 13a-2 sends the sensor value to the host 11a (step S17b).

[0042] As described above, in the conventional system 10, the communication bandwidth of the first link L1 and the second link L2 is occupied by software transmission while the process in step S12 in Figure 2 and the process in step S17 in Figure 3 are being performed.

[0043] Furthermore, even if there are multiple identical field devices, software downloads are performed for each field device, occupying the communication bandwidth of the first link L1 for each device performing the software download. This limits the amount of communication with hosts and field devices on the first link L1, thus affecting the control loop on the first link L1.

[0044] Furthermore, software downloads are time-consuming and performed for each field device, increasing the load on the host. Therefore, software downloads are often performed with the entire system's control loop, including not only the first link L2 but also the first link L1, shut down, resulting in extended downtime.

[0045] (Description of the system in Embodiment 1) Next, an example of the system of Embodiment 1 will be described. Figure 4 is a diagram showing the system of Embodiment 1. As shown in Figure 4, the system 50 of Embodiment 1 includes hosts 51a, 51b, a relay device 100, and field devices 53a-1, 53a-2, 53b, 53c-1, and 53c-2. The hosts 51a, 51b, the relay device 100, and the field devices 53c-1 and 53c-2 are connected to the first link L1. The relay device 100 and the field devices 53a-1, 53a-2, and 53b are connected to the second link L2. Here, "link" refers to a circuit or transmission path that is in a state where signals and data can be sent and received.

[0046] Hosts 51a and 51b are PCs used by workers, and they acquire sensor values ​​from field devices 53a-1, 53a-2, 53b, 53c-1, and 53c-2, and update software. Field devices 53a-1, 53a-2, 53b, 53c-1, and 53c-2 are sensor devices and operating devices installed in plants using petroleum, petrochemicals, chemicals, gases, etc. Sensor devices include pressure sensors, temperature sensors, flow sensors, pH sensors, speed sensors, and acceleration sensors. Operating devices include valves, pumps, and fans, which are driven by motors and actuators.

[0047] Note that field devices 53a-1 and 53a-2 are the same field device. Field devices 53c-1 and 53c-2 are the same field device. In the following explanation, field devices 53a-1 and 53a-2 will be collectively referred to as field device 53a as appropriate. Field devices 53c-1 and 53c-2 will be collectively referred to as field device 53c as appropriate.

[0048] For example, when we say that each field device is identical, it means that each field device has the same hardware and software configuration and the same performance and functionality.

[0049] Field device 53a is designated as a "device type A" field device. Field device 53b is designated as a "device type B" field device. Field device 53c is designated as a "device type C" field device.

[0050] When hosts 51a, 51b and field device 53c connected to the first link L1 communicate with each other, the first link L1 is used. On the other hand, when hosts 51a, 51b and field device 53c connected to the first link L1 communicate with field devices 53a and 53b connected to the second link L2, communication is performed via the relay device 100.

[0051] In the following explanation, the hosts 51a and 51b and field device 53c connected to the first link L1 will be referred to as "each device connected to the first link L1" as appropriate. The field devices 53a and 53b connected to the second link L2 will be referred to as "each device connected to the second link L2" as appropriate.

[0052] In Embodiment 1, each device using the first link L1 communicates with each other using a communication speed and communication protocol based on PROFIBUS-DP, etc. Each device connected to the second link L2 communicates with each other using a communication speed and communication protocol based on PROFIBUS-PA, etc.

[0053] The relay device 100 is a device that performs communication conversion between the first link L1 and the second link L2. The relay device 100 is an I / O device, etc.

[0054] Here, we will describe the process in system 50 in which a host connected to the first link L1 updates the software of the same field device connected to the second link L2 via the relay device 100. As an example, we will describe the case in which host 51a updates the software of field device 53a.

[0055] Host 51a transmits "device type A software" to relay device 100, and relay device 100 stores the device type A software in its memory unit. Relay device 100 updates the software of field device 53a-1 by transmitting the device type A software to field device 53a-1 while exchanging commands with field device 53a-1. Subsequently, relay device 100 updates the software of field device 53a-2 by transmitting the device type A software to field device 53a-2 while exchanging commands with field device 53a-2.

[0056] This prevents the first link's bandwidth from being occupied while the field device 13a is receiving the software for download, thereby reducing the overall system traffic.

[0057] (Functional configuration of the relay device in Embodiment 1) Next, an example of the configuration of the relay device 100 shown in Figure 4 will be described. Figure 5 is a functional block diagram showing the functional configuration of the relay device according to Embodiment 1. As shown in Figure 5, the relay device 100 has a first communication unit 110, a second communication unit 120, a conversion unit 130, a storage unit 140, a communication control unit 150, and an update control unit 160.

[0058] The first communication unit 110 communicates with each device connected to the first link L1 using a communication speed and communication protocol based on PROFIBUS-DP or the like. When the first communication unit 110 receives data destined for each device on the second link L2, it outputs the received data to the conversion unit 130. For example, the devices on the second link L2 are field devices 53a and 53b.

[0059] The second communication unit 120 communicates with each device connected to the second link L2 using a communication speed and communication protocol based on PROFIBUS-PA or the like. When the second communication unit 120 receives data destined for each device on the first link L2, it outputs the received data to the conversion unit 130. For example, each device on the first link L2 is a field device with a 53c signal.

[0060] The conversion unit 130 converts the communication between the first link L1 and the first link L2. For example, when the conversion unit 130 receives data from the first communication unit 110, it converts the data's communication speed and communication protocol to the communication speed and communication protocol of the second link L2 and outputs it to the second communication unit 120. On the other hand, when the conversion unit 130 receives data from the second communication unit 120, it converts the data's communication speed and communication protocol to the communication speed and communication protocol of the first link L1 and outputs it to the first communication unit 110.

[0061] The storage unit 140 contains a device list 141 and software data 142. The storage unit 140 is a memory, etc.

[0062] The device list 141 contains information about each device connected to the second link L2. Figure 6 shows an example of the data structure of the device list. As shown in Figure 6, the device list 141 has an address and a revision.

[0063] The address is the IP (Internet Protocol) address of the field device. The device type is the device type of the field device. Field devices of the same device type are considered the same field device. The revision indicates the version of the software configured on the field device in question.

[0064] In Embodiment 1, the address of field device 53a-1 is set to "10". The address of field device 53a-2 is set to "20". The address of field device 53b is set to "30".

[0065] Software data 142 is data for software to be downloaded, transmitted from host 51a. For example, software data 142 is data for software of device type A. Software data 142 may also include data regarding the device type and software revision.

[0066] Furthermore, the relay device 100 can store any number of device lists 141 and software data 142, as long as the size of the storage unit 140 allows. For example, the relay device 100 can store software data for device type A, software data for device type B, and software data for other device types in the storage unit 140 as software data 142.

[0067] The communication control unit 150 has the function of communicating with the host 51a connected to the first link L1, and communicates using communication protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol) or HTTP (HyperText Transfer Protocol).

[0068] For example, when host 51a transmits software for device type A to relay device 100, communication control unit 150 receives the software for device type A via first communication unit 110 and stores it in storage unit 140 as software data 142. Once communication control unit 150 has finished receiving the software for device type A, it instructs update control unit 160 to download the device on second link L2 (field device 53a).

[0069] When the update control unit 160 receives a download processing instruction from the communication control unit 150, it identifies the field devices to be downloaded based on the device type in the software data 142 and the device list 141. For example, if the device type in the software data 142 is "device type A", the update processing unit 160 identifies field devices 53a-1 and 53a-2 as targets for software download.

[0070] An example of the processing performed by the update control unit 160 after identifying field devices 53a-1 and 53a-2 as targets for software download will be described below. The update control unit 160 performs the processing of steps 1, 2, and 3 for field device 53a-1, and then performs the processing of steps 1, 2, and 3, which will be described later, for field device 53a-2.

[0071] The first step performed by the update control unit 160 is described below. The update control unit 160 sends a command to the field device 53a-1 to instruct it to start downloading. In the following description, the command instructing the start of downloading will be referred to as the "download start command". When the field device 53a-1 receives the download start command, it prepares for downloading. Once the field device 53a-1 has finished preparing for downloading, the update control unit 160 proceeds to the second step.

[0072] The second step performed by the update control unit 160 will now be described. The update control unit 160 transmits the download software to the field device 53a-1. Since the download software is large and cannot be transmitted all at once, the update control unit 160 divides it into multiple communication frames and transmits them to the field device 53a-1. Once the transmission of the download software is complete, the update control unit 160 proceeds to the third step.

[0073] The third step performed by the update control unit 160 will now be described. The update control unit 160 sends a command to the field device 53a-1 instructing it to switch software. In the following description, the command instructing the software to switch software will be referred to as the "software switching command". When the field device 53a-1 receives the software switching command, it updates its own software to the new software received in the second step and starts up. From this point onward, the field device 53a-1 operates with the new software. The update processing unit 160 updates the revision corresponding to the field device 53a-1 (address 10) in the device list 141 to the updated revision.

[0074] The first, second, and third steps of processing performed by the update control unit 160 on field device 53a-1 have been described above. The first, second, and third steps of processing performed by the update control unit 160 on field device 53a-2 after these steps are the same as the above processing except that the target changes from field device 53a-1 to field device 53a-2, so the explanation is omitted.

[0075] (Processing procedure for software download in Embodiment 1) Next, the software download processing procedure for Embodiment 1 will be described. Figures 7 and 8 are flowcharts of the software download processing for Embodiment 1. In the example shown in Figures 7 and 8, the processing procedure when host 51a sends "device type A software" for download to relay device 100 will be described. Note that the "Download Read Status Read Command" shown in Figures 7 and 8 is a command to inquire about the download readiness status of the field device. The "Sensor Value Read Command" is a command to inquire about the sensor value of the field device. The "Download Complete Status Read Command" is a command to inquire about the download completion status of the field device. Furthermore, Download (New Software #1) to Download (New Software #n) show how the divided download data is sent to the field device.

[0076] First, let's explain Figure 7. Host 51a transmits the software for device type A to relay device 100, and relay device 100 stores the software for device type A in the storage unit 140 (step S101).

[0077] The relay device 100 transmits a Download Start command to the field device 53a-1. Upon receiving the Download Start command, the field device 53a-1 transmits an acknowledgment to the relay device 100 and prepares for the download (step S102).

[0078] The relay device 100 repeatedly sends a Download Read status command to the field device 53a-1 until the field device 53a-1 is ready to download. When the field device 53a-1 is ready to download, it sends an acknowledgment to the relay device 100 indicating that it is ready (step S103).

[0079] When relay device 100 receives a ready signal from field device 53a-1, it divides and transmits the download software (new software #1 to #n) to field device 53a-1. Each time field device 53a-1 receives a divided piece of software, it sends an acknowledgment to relay device 100. Relay device 100 and field device 53a-1 repeat this process until all download software has been transmitted. When field device 53a-1 has finished receiving all download software, it enters a Download complete state (step S104).

[0080] Once the relay device 100 has finished transmitting all the software for download, it sends a Download complete status Read command to the field device 53a-1. When the field device 53a-1 receives the Download complete status Read command, it sends a Download complete message to the relay device 100 (step S105).

[0081] The relay device 100 transmits a software switching command to the field device 53a-1. Upon receiving the software switching command, the field device 53a-1 updates its software to the new software and restarts (step S106).

[0082] While the process in step S104 is being performed, the host 51a periodically performs the process of acquiring sensor values ​​from field devices 53a-1 and 53a-2 via the relay device 100. For example, the host 51a sends a sensor value Read command to field device 53a-1, and field device 53a-1 sends the sensor value to the host 51a (step S104a). The host 51a sends a sensor value Read command to field device 53a-2, and field device 53a-2 sends the sensor value to the host 51a (step S104b).

[0083] Next, we will move on to the explanation of Figure 8. The relay device 100 transmits a Download Start command to the field device 53a-2. When the field device 53a-2 receives the Download Start command, it transmits an acknowledgment to the relay device 100 and prepares for the download (step S107).

[0084] The relay device 100 repeatedly sends a Download Read status command to the field device 53a-2 until the field device 53a-2 is ready to download. When the field device 53a-2 is ready to download, it sends an acknowledgment to the relay device 100 indicating that it is ready (step S108).

[0085] When relay device 100 receives a "ready" message from field device 53a-2, it divides and transmits the download software (new software #1 to #n) to field device 53a-2. Each time field device 53a-2 receives a divided piece of software, it sends an acknowledgment to relay device 100. Relay device 100 and field device 53a-2 repeat this process until all download software has been transmitted. Once field device 53a-2 has received all download software, it enters a "Download complete" state (step S109).

[0086] Once the relay device 100 has finished transmitting all the software for download, it sends a Download complete status Read command to the field device 53a-2. When the field device 53a-2 receives the Download complete status Read command, it sends a Download complete message to the relay device 100 (step S110).

[0087] The relay device 100 transmits a software switching instruction command to the field device 53a-2. Upon receiving the software switching instruction command, the field device 53a-2 updates its software to the new software and restarts (step S111).

[0088] While the process in step S109 is being performed, the host 51a periodically performs the process of acquiring sensor values ​​from field devices 53a-1 and 53a-2 via the relay device 100. For example, the host 51a sends a sensor value Read command to field device 53a-1, and field device 53a-1 sends the sensor value to the host 51a (step S109a). The host 51a sends a sensor value Read command to field device 53a-2, and field device 53a-2 sends the sensor value to the host 51a (step S109b).

[0089] (Effects of Embodiment 1) Next, the effects of the relay device 100 according to Embodiment 1 will be described. The relay device 100 receives software from the host on the first link L2, with the destination being a device connected to the second link L2, and stores the received software in the storage unit 140. The relay device 100 updates the device connected to the second link L2 by transmitting the software stored in the storage unit 140 to the device connected to the second link L2. This prevents the communication bandwidth of the first link L1 from being occupied while the device (field device) connected to the second link L2 is receiving the download software, thereby reducing the overall communication volume of the system.

[0090] By preventing the first link L1's communication bandwidth from being occupied while a device (field device) connected to the second link L2 is receiving downloadable software, the time the first link L1's control loop is stopped can be reduced.

[0091] This reduces the load on hosts 51 and 52 of the first link L1, which transmits the software, thereby shortening the overall system downtime.

[0092] (Embodiment 2) (Description of the system in Embodiment 2) Next, an example of the system of Embodiment 2 will be described. Figure 9 is a diagram showing the system of Embodiment 2. As shown in Figure 9, the system 60 of Embodiment 2 includes hosts 61a, 61b, a relay device 200, and field devices 63a-1, 63a-2, 63b, 63c-1, and 63c-2. The hosts 61a, 61b, the relay device 200, and the field devices 63c-1 and 63c-2 are connected to the first link L1. The relay device 200 and the field devices 63a-1, 63a-2, and 63b are connected to the second link L2.

[0093] Hosts 61a and 61b are PCs used by workers, and they acquire sensor values ​​from field devices 63a-1, 63a-2, 63b, 63c-1, and 63c-2, and update software. Field devices 63a-1, 63a-2, 63b, 63c-1, and 63c-2 are sensors, etc.

[0094] Note that field devices 63a-1 and 63a-2 are the same field device. Field devices 63c-1 and 63c-2 are the same field device. In the following explanation, field devices 63a-1 and 63a-2 will be collectively referred to as field device 63a as appropriate. Field devices 63c-1 and 63c-2 will be collectively referred to as field device 63c as appropriate.

[0095] Field device 63a is designated as a "device type A" field device. Field device 63b is designated as a "device type B" field device. Field device 63c is designated as a "device type C" field device.

[0096] When hosts 61a, 61b and field device 63c connected to the first link L1 communicate with each other, the first link L1 is used. On the other hand, when hosts 61a, 61b and field device 63c connected to the first link L1 communicate with field devices 63a and 63b connected to the second link L2, communication is performed via the relay device 200.

[0097] In the following explanation, the hosts 61a and 61b and field device 63c connected to the first link L1 will be referred to as "each device connected to the first link L1" as appropriate. The field devices 63a and 63b connected to the second link L2 will be referred to as "each device connected to the second link L2" as appropriate.

[0098] Similar to Embodiment 1, in Embodiment 2, each device utilizing the first link L1 communicates with each other using a communication speed and communication protocol based on PROFIBUS-DP, etc. Each device connected to the second link L2 communicates with each other using a communication speed and communication protocol based on PROFIBUS-PA, etc.

[0099] The relay device 200 is a device that performs communication conversion between the first link L1 and the second link L2. The relay device 200 is an I / O device, etc.

[0100] Here, we will describe the process in system 60 in which a host connected to the first link L1 updates the software of the same field device connected to the second link L2 via the relay device 200. As an example, we will describe the case in which host 61a updates the software of field device 63a.

[0101] The host 61a transmits the "device type A software" to the field device 53a-1 via the relay device 200, and the host 61a updates the software of the field device 53a-1 while exchanging commands with the field device 53a-1. While relaying the "device type A software," the relay device 200 processes the "device type A software" and stores it in its memory unit.

[0102] After the update of field device 53a-1 is completed, the relay device 100 updates the software of field device 53a-2 by exchanging commands with field device 53a-2 and transmitting the software for device type A stored in its memory unit to field device 53a-2.

[0103] In Embodiment 2, the procedure of sending the "device type A software" only from the host 61a to the relay device 200 is eliminated, making it possible to shorten the overall system time required for software download compared to Embodiment 1. Furthermore, since the relay device 200 transmits the software stored in its memory unit to the remaining field devices to perform software updates, it prevents the first link's communication bandwidth from being occupied and reduces the overall system communication volume.

[0104] (Functional configuration of the relay device in Embodiment 2) Next, an example of the configuration of the relay device 200 shown in Figure 9 will be described. Figure 10 is a functional block diagram showing the functional configuration of the relay device according to Embodiment 2. As shown in Figure 10, the relay device 200 has a first communication unit 210, a second communication unit 220, a conversion unit 230, a storage unit 240, a communication control unit 250, and an update control unit 260.

[0105] The first communication unit 210 communicates with each device connected to the first link L1 based on the communication speed and communication protocol based on PROFIBUS-DP, etc. When the first communication unit 210 receives data destined for any of the devices on the second link L2, it outputs the received data to the conversion unit 130.

[0106] The second communication unit 220 communicates with each device connected to the second link L2 according to the communication speed and communication protocol based on PROFIBUS-PA, etc. When the second communication unit 220 receives data destined for any of the devices on the first link L2, it outputs the received data to the conversion unit 230.

[0107] The conversion unit 230 converts the communication between the first link L1 and the first link L2. For example, when the conversion unit 230 receives data from the first communication unit 210, it converts the data's communication speed and communication protocol to the communication speed and communication protocol of the second link L2 and outputs it to the second communication unit 220. On the other hand, when the conversion unit 230 receives data from the second communication unit 120, it converts the data's communication speed and communication protocol to the communication speed and communication protocol of the first link L1 and outputs it to the first communication unit 210.

[0108] The storage unit 240 contains a device list 241 and software data 242. The storage unit 240 is a memory, etc.

[0109] The device list 241 contains information about each device connected to the second link L2. Further description of the device list 241 is the same as the description of the device list 141 described in Figure 6. In Embodiment 2, the address of field device 63a-1 is set to "10". The address of field device 63a-2 is set to "20". The address of field device 63b is set to "30".

[0110] Software data 242 is the data for the downloadable software transmitted from host 61a. Further description of software data 242 is the same as the description of software data 142 described in Figure 5.

[0111] The communication control unit 250 has the function of communicating with the host 61a connected to the first link L1, and communicates using communication protocols such as TCP / IP or HTTP.

[0112] For example, when host 61a transmits software for device type A to field device 63a-1 via relay device 200, communication control unit 250 receives the software for device type A via first communication unit 210 and stores it in storage unit 240 as software data 242.

[0113] When the communication control unit 250 has finished receiving the software for device type A, it instructs the update control unit 260 to download the device on the second link L2 (field device 53a-2). The communication control unit 250 also monitors the data exchange between the host 61a and the field device 63a-1, and when it determines that the download for field device 63a-1 is complete, it notifies the update control unit 260 that the download for field device 63a-1 is complete.

[0114] When the update control unit 260 receives a download processing instruction from the communication control unit 250, it identifies the field device to be downloaded based on the device type in the software data 242 and the device list 241. For example, if the device type in the software data 242 is "device type A" and the download for field device 63a-1 has been completed, the update processing unit 260 identifies field device 63a-2 as the target for software download.

[0115] Next, the software download process for system 60 will be described. Here, we will describe the case where host 61a transmits software to field device 63a-1, and then relay device 200 transmits software to field device 63a-2. For example, in the software download process of Embodiment 2, the process is carried out in the order of the first, second, third, fourth, fifth, and sixth steps, which will be described later.

[0116] The first step of system 60 is described below. Host 61a sends a Download Start command to field device 63a-1. Upon receiving the command, field device 63a-1 prepares for the Download. Once host 61a has finished preparing field device 63a-1 for the Download, it proceeds to the second step.

[0117] The second step of system 60 will now be described. Host 61a transmits downloadable software to field device 63a-1. Because the downloadable software is large and cannot be transmitted all at once, host 61a divides it into multiple communication frames and transmits them to field device 63a-1. The communication control unit 250 of the relay device 200 stores the downloadable software transmitted from host 61a to field device 63a-1 in the storage unit 240. Once host 61a has finished transmitting the downloadable software, it proceeds to the third step.

[0118] The third step of system 60 will now be described. Host 61a sends a software switching command to field device 63a-1. Upon receiving the command, field device 63a-1 updates its software to the new software received in the second step and starts up. From this point onward, field device 63a operates with the new software. The communication control unit 250 also updates the revision corresponding to field device 63a-1 (address 10) in the device list 241 to the updated revision.

[0119] The fourth step of system 60 is described below. The update control unit 260 of the relay device 200 sends a Download start command to field device 63a-2. Upon receiving the command, field device 53a-2 prepares for the Download. When field device 63a-1 has finished preparing for the Download, the update control unit 260 proceeds to the fifth step.

[0120] The fifth step of system 60 will now be described. The update control unit 260 transmits the download software to the field device 63a-2. Since the download software is large and cannot be transmitted all at once, the update control unit 260 divides it into multiple communication frames and transmits them to the field device 63a-2. Once the transmission of the download software is complete, the update control unit 260 proceeds to the sixth step.

[0121] The sixth step of system 60 is described below. The update control unit 260 sends a software switching command to field device 63a-2. Upon receiving the command, field device 63a-2 updates its software to the new software received in step 5 and starts up. From this point onward, field device 63a-2 operates with the new software. The update processing unit 260 updates the revision corresponding to field device 63a-2 (address 20) in the device list 241 to the updated revision.

[0122] (Processing procedure for software download in Embodiment 2) Next, the software download processing procedure of Embodiment 2 will be described. Figures 11 and 12 are flowcharts of the software download processing of Embodiment 1. In the example shown in Figures 11 and 12, the case in which host 61a transmits software to field device 63a-1, and then relay device 200 transmits software to field device 63a-2 will be described. The explanation of each command shown in Figures 11 and 12 is the same as the explanation of each command in Figures 7 and 8.

[0123] First, let's explain Figure 11. Host 61a sends a Download Start command to field device 63a-1 via relay device 200. When field device 63a-1 receives the Download Start command, it sends an acknowledgment to host 11a via relay device 200 and prepares for the download (step S201).

[0124] Host 61a repeatedly sends a "Download Ready" message to field device 63a-1 via relay device 200 until field device 63a-1 is ready to download. Once field device 63a-1 is ready to download, it sends an acknowledgment of readiness to host 61a via relay device 200 (step S202).

[0125] When host 61a receives a "ready" message from field device 63a-1, it divides the download software into segments and sends them to field device 63a-1. Each time field device 63a-1 receives a segment of the software, it sends an acknowledgment to host 61a. Host 61a and field device 63a-1 repeat this process until all download software has been sent. Once field device 63a-1 has received all download software, it enters a "Download Complete" state. The relay device 200 stores the download software sent from host 61a to field device 63a-1 in its storage unit 240 (step S203).

[0126] Once host 61a has finished sending all the software for download, it sends a Download complete status Read to field device 63a-1. When field device 63a-1 receives the Download complete status Read command, it sends a Download complete message to host 61a (step S204).

[0127] The host 61a sends a software switching command to the field device 63a-1. Upon receiving the software switching command, the field device 63a-1 updates its software to the new software and restarts (step S205).

[0128] While the host 61a is performing the processing in step S203, it periodically executes a process to acquire sensor values ​​from field devices 63a-1 and 63a-2. For example, the host 61a sends a sensor value Read command to field device 63a-1, and field device 63a-1 sends the sensor value to the host 61a (step S203a). The host 61a sends a sensor value Read command to field device 63a-2, and field device 63a-2 sends the sensor value to the host 61a (step S203b).

[0129] Next, we will move on to the explanation of Figure 12. The relay device 100 sends a Download Start command to the field device 63a-2. When the field device 63a-2 receives the Download Start command, it sends an acknowledgment to the relay device 200 and prepares for the download (step S206).

[0130] The relay device 200 repeatedly sends a Download Read status command to the field device 63a-2 until the field device 63a-2 is ready to download. When the field device 63a-2 is ready to download, it sends an acknowledgment to the relay device 200 indicating that it is ready (step S207).

[0131] When relay device 200 receives a "ready" message from field device 63a-2, it transmits the download software (new software #1 to #n) in segments to field device 63a-2. Each time field device 63a-2 receives a segmented piece of software, it sends an acknowledgment to relay device 200. Relay device 200 and field device 63a-2 repeat this process until all download software has been transmitted. When field device 63a-2 has received all download software, it enters a "Download complete" state (step S208).

[0132] Once the relay device 200 has finished transmitting all the software for download, it sends a Download complete status Read command to the field device 63a-2. When the field device 53a-2 receives the Download complete status Read command, it sends a Download complete message to the relay device 100 (step S209).

[0133] The relay device 200 transmits a software switching command to the field device 63a-2. Upon receiving the software switching command, the field device 63a-2 updates its software to the new software and restarts (step S210).

[0134] While the process in step S208 is being performed, the host 61a periodically performs the process of acquiring sensor values ​​from field devices 63a-1 and 63a-2 via the relay device 200. For example, the host 61a sends a Sensor Value Read command to field device 63a-1, and field device 63a-1 sends the sensor value to the host 61a (step S208a). The host 61a sends Sensor Value Read to field device 63a-2, and field device 63a-2 sends the sensor value to the host 61a (step S208b).

[0135] (Effects of Embodiment 2) Next, the effects of the relay device 200 according to Embodiment 2 will be described. For example, in the process in which a host 61a connected to the first link L1 transmits the "software for device type A" to a field device 63a-1 connected to the second link L2 for updating, the relay device 200 stores the "software for device type A" in the storage unit 240. The relay device 200 then transmits the "software for device type A" stored in the storage unit 240 to the field device 63a-2 connected to the second link L2 to perform the update.

[0136] In Embodiment 2, the procedure of sending the "device type A software" only from the host 61a to the relay device 200 is eliminated, making it possible to shorten the overall system time required for software download compared to Embodiment 1. Furthermore, since the relay device 200 transmits the software stored in its memory unit to the remaining field devices to perform software updates, it prevents the first link L1's communication bandwidth from being occupied, thereby reducing the overall system communication volume.

[0137] Although Embodiments 1 and 2 have been described above, the processing of the system according to the present invention is not limited to the processing described in Embodiments 1 and 2. Other embodiments will be described below.

[0138] (Regarding other embodiments) For example, a separate interface could be provided on the relay device to store "software for specific device types" for download from devices on the third link L3 or storage devices such as USB (Universal Serial Bus) memory, and then update field devices connected to the second link.

[0139] Figure 13 is a functional block diagram showing the configuration of a relay device according to another embodiment. As shown in Figure 13, the relay device 300 has a first communication unit 310, a second communication unit 320, a conversion unit 330, a storage unit 340, a communication control unit 350, an update control unit 360, and an interface 370.

[0140] When describing the relay device 300, the devices connected to the first link L1 of the system according to the other embodiment will be referred to as the hosts 51a, 51b and field device 53c shown in Figure 4. The devices connected to the second link L2 will be referred to as the field devices 53a, 53b shown in Figure 4.

[0141] The description of the first communication unit 310, the conversion unit 330, and the second communication unit 320 is the same as the description of the first communication units 110, 210, the conversion units 130, 230, and the second communication units 120, 220.

[0142] The storage unit 340 contains a device list 341 and software data 342. The storage unit 340 is a memory, etc.

[0143] The equipment list 341 contains information about each device connected to the second link L2. The equipment list 341 may be the equipment list 141 described in Figure 6, or it may be an equipment list like the one shown in Figure 14.

[0144] Figure 14 shows an example of the data structure of a device list according to another embodiment. As shown in Figure 14, the device list 341 has a download target, address, and revision. The download target indicates whether or not it is a software download target. It is set to "on" if it is a download target and to "off" if it is not. The on / off status of the download target in the device list 341 may be set by a device connected to the third link L3 accessing the relay device 300, or it may be set directly by a user operating the input section of the relay device 300.

[0145] The descriptions of addresses and revisions in equipment list 341 are the same as those for addresses and revisions in equipment list 141.

[0146] The software data 342 may be downloadable software data transmitted from the host 51a, or downloadable software data input via interface 370 from a device on the third link L3 or a storage device such as a USB memory.

[0147] The communication control unit 350 has the function of communicating with the host 51a connected to the first link L1, and communicates using communication protocols such as TCP / IP or HTTP. The communication control unit 350 may also communicate with the device on the third link L3 to receive data regarding the on / off setting of the download targets in the device list 341 and whether the software transmission has been completed. When the communication control unit 350 receives confirmation from the device on the third link L3 that the software transmission has been completed, it instructs the update control unit 360 to perform the download process on the device on the second link L2 (for example, the field device 53a).

[0148] Further details regarding the communication control unit 350 are the same as those for the communication control units 150 and 250.

[0149] When the update control unit 360 receives a download processing instruction from the communication control unit 350, it identifies the field devices to be downloaded based on the device type in the software data 342 and the device list 341. For example, as shown in Figure 14, if the download targets for addresses "10" and "20" are set to "on", the update control unit 360 identifies field devices 53a-1 and 53a-2 as targets for software download.

[0150] Further details regarding the update control unit 360 are the same as those for the update control units 160 and 260.

[0151] Interface 370 connects to a device (such as a host) on the third link L3 or to a storage device such as a USB memory stick, and stores "software for a specific device type" for download in the storage unit 340.

[0152] As described above, a separate interface 370 is provided on the relay device 300 to store "software for specific device types" for download from devices on the third link L3 or storage devices such as USB memory, and update field devices connected to the second link. This makes it possible to download software without increasing the load on the host or the first link L1.

[0153] Furthermore, when applied to a system with multiple relay devices, interface 370 may be connected to other relay devices. For example, by connecting relay devices with a third link L3, it is possible to share the software for download devices stored in the storage unit 340, enabling efficient software downloads for the entire system.

[0154] The relay device 300 sets information in the device list 342 indicating whether or not a device is subject to software download. This allows for software downloads to be performed only on specific field devices, or to unify the revision of all devices on the second link L2, and to perform configurations.

[0155] (Hardware) Next, an example of the hardware configuration of the relay device 100 (200, 300) will be described. Figure 15 is a diagram illustrating the example hardware configuration. As shown in Figure 15, the relay device 100 has a communication device 6a, an HDD (Hard Disk Drive) 6b, memory 6c, and a processor 6d. Furthermore, each of the parts shown in Figure 15 is interconnected by a bus or the like.

[0156] The communication device 6a is a network interface card or the like, and communicates with other servers. The HDD 6b stores programs and databases that operate the functions shown in Figure 5, etc.

[0157] The processor 6d operates the processes that perform the functions described in Figure 5 by reading programs that perform the same processing as the processing units shown in Figure 5, etc., from the HDD 5b, etc., and loading them into memory 6c. For example, this process performs the same functions as the processing units of the relay device 100. Specifically, the processor 6d executes processes that perform the same processing as the first communication unit 110, the second communication unit 120, the conversion unit 130, the communication control unit 150, the update control unit 160, etc.

[0158] Thus, the relay device 100 operates as a relay device that executes the relay method by reading and executing a program. Furthermore, the relay device 100 can also achieve the same functionality as the embodiment described above by reading the program from the recording medium using a media reader and executing the read program. Note that the program referred to in this other embodiment is not limited to being executed by the relay device 100. For example, the present invention can be similarly applied when another computer or server executes the program, or when they collaborate to execute the program.

[0159] This program can be distributed via networks such as the Internet. Furthermore, this program can be recorded on computer-readable storage media such as hard disks, flexible disks (FDs), CD-ROMs, MO (Magneto-Optical disks), and DVDs (Digital Versatile Discs), and executed by reading the program from these media using a computer.

[0160] (others) Some examples of the combinations of technical features that will be disclosed are listed below.

[0161] (1) A first communication unit that communicates with the first device connected to the first link, A second communication unit that communicates with a second device connected to the second link, A communication control unit receives software from the first device that is a destination to the second device, and stores the received software in a storage unit, The update control unit transmits the software stored in the storage unit to the second device to update the software of the second device. A relay device having the following features.

[0162] (2) Multiple second devices belonging to the same equipment type are connected to the second link. The communication control unit further performs the process of storing the software in the storage unit during the process in which the software is transmitted from the first device to any one of the plurality of second devices and updated. The relay device according to (1), wherein the update control unit further performs the process of updating the software by transmitting the software stored in the storage unit to an unupdated second device among the plurality of second devices.

[0163] (3) Multiple second devices are connected to the second link, The storage unit further stores a list of devices that associates the second device with the device type of the second device. The relay device according to (1), wherein the update control unit further performs a process to identify a second device to which the software will be transmitted from the plurality of second devices, based on the device type set in the software and the device list.

[0164] (4) The relay device according to (3), wherein the device list indicates a second device to which the software is to be transmitted, and the update control unit further performs a process to identify the second device to which the software is to be transmitted from the plurality of second devices based on the device list.

[0165] (5) The relay device according to (1), further comprising an interface unit for acquiring software for updating the second device from a third device connected to a third link different from the first and second links, and storing the acquired software in the storage unit.

[0166] (6) The relay device according to (5), wherein the interface unit further performs the process of acquiring software for updating the second device from an external storage device and storing the acquired software in the storage unit.

[0167] (7) The relay device described in (1), wherein the second device is a sensor device or operating device installed in the plant.

[0168] (8) The relay device according to (1), wherein the update control unit updates the software of the second device by dividing the software and transmitting it to the second device.

[0169] (9) Computers Using a first communication unit that communicates with a first device connected to a first link, and a second communication unit that communicates with a second device connected to a second link, the system receives software from the first device with the second device as the destination, and stores the received software in a storage unit. The software stored in the storage unit is transmitted to the second device to update the software of the second device. A relay method for executing processing.

[0170] (10) To the computer, Using a first communication unit that communicates with a first device connected to a first link, and a second communication unit that communicates with a second device connected to a second link, the system receives software from the first device with the second device as the destination, and stores the received software in a storage unit. The software stored in the storage unit is transmitted to the second device to update the software of the second device. A relay program that executes a process. [Explanation of Symbols]

[0171] 100, 200, 300 relay devices 110,210,310 First Communications Department 120,220,320 Second Communications Department 130,230,330 Conversion Unit 140,240,340 storage section 141,241,341 Equipment List 142,242,342 Software Data 150,250,350 Communication Control Unit 160,260,360 Update Control Unit 370 Interfaces

Claims

1. A first communication unit that communicates with a first device connected to a first link, A second communication unit that communicates with a second device connected to the second link, A communication control unit receives software from the first device that is a destination to the second device, and stores the received software in a storage unit, The update control unit updates the software of the second device by transmitting the software stored in the storage unit to the second device. A relay device having the following features.

2. Multiple second devices belonging to the same equipment type are connected to the aforementioned second link. The communication control unit further performs the process of storing the software in the storage unit during the process in which the software is transmitted from the first device to any one of the plurality of second devices and updated. The relay device according to claim 1, wherein the update control unit further performs a process of updating the software by transmitting the software stored in the storage unit to an unupdated second device among the plurality of second devices.

3. Multiple second devices are connected to the aforementioned second link. The storage unit further stores a list of devices that associates the second device with the device type of the second device. The relay device according to claim 1, wherein the update control unit further performs a process to identify a second device to which the software will be transmitted from the plurality of second devices, based on the device type set in the software and the device list.

4. The relay device according to claim 3, wherein the device list indicates a second device to which the software is to be transmitted, and the update control unit further performs a process to identify the second device to which the software is to be transmitted from the plurality of second devices based on the device list.

5. The relay device according to claim 1, further comprising an interface unit for acquiring software for updating the second device from a third device connected to a third link different from the first and second links, and storing the acquired software in the storage unit.

6. The relay device according to claim 5, wherein the interface unit further performs a process of acquiring software for updating the second device from an external storage device and storing the acquired software in the storage unit.

7. The relay device according to claim 1, wherein the second device is a sensor device or operating device installed in a plant.

8. The relay device according to claim 1, wherein the update control unit updates the software of the second device by dividing the software and transmitting it to the second device.

9. Computers Using a first communication unit that communicates with a first device connected to a first link, and a second communication unit that communicates with a second device connected to a second link, the system receives software from the first device with the second device as the destination, and stores the received software in a storage unit. The software stored in the storage unit is transmitted to the second device to update the software of the second device. A relay method for executing processing.

10. On the computer, Using a first communication unit that communicates with a first device connected to a first link, and a second communication unit that communicates with a second device connected to a second link, the system receives software from the first device with the second device as the destination, and stores the received software in a storage unit. The software stored in the storage unit is transmitted to the second device to update the software of the second device. A relay program that executes a process.

Images