JP2010086206A - Setting device and field network system - Google Patents

Abstract

A technology for efficiently downloading firmware update data and improving the reliability of data transfer is provided.
In a temporary device connected in communication with a device that transmits firmware update data and a field device that receives firmware data transmitted from the device, the nonvolatile data received from the field device is received. The CPU 11 is configured to set the stored data to correspond to the firmware update data 7 and transmit the nonvolatile storage data for which the setting has been performed to the field device 2 in parallel with the transmission of the firmware update data 7 by the device 1. .
[Selection] Figure 1

Description

  The present invention relates to a setting device and a field network system.

  In recent years, field network systems in which field devices including sensors, actuators, and controllers such as flow meters and thermometers are connected via a network have been implemented.

  An example of the configuration of the field network system 100 will be described with reference to FIG. The field network system 100 includes a device 101 and field devices 102 to 104.

  The device 101 is an electronic device composed of a board or the like having a configuration function. The field devices 102 to 104 are field devices including sensors such as a flow meter and a thermometer. The device 101 and the field devices 102 to 104 are communication target devices of the FOUNDATION fieldbus H1 (registered trademark), and perform information communication via the H1 bus 104A for communication of the FOUNDATION fieldbus H1 (hereinafter referred to as H1).

  Next, an operation of updating firmware (software) in the field device 102 in the field network system 100 will be described.

  It is assumed that the field device 102 has a nonvolatile storage data takeover algorithm 106 for setting the nonvolatile storage data (tag information for identifying the field device or the like) to correspond to the firmware update data 105 in advance. In addition, it is assumed that the firmware update data 105 is previously created by the device 1 in a form corresponding to the nonvolatile storage data takeover algorithm 106.

  First, the firmware update data 105 is downloaded from the device 101 by the field device 102. Specifically, firmware update data 105 having the structure shown in FIG. 7 is downloaded. As shown in FIG. 7, the firmware update data 105 includes application execution data composed of data for executing fieldbus communication and control applications, and a nonvolatile storage data takeover algorithm.

  Then, the non-volatile storage data takeover algorithm 106 is used by the field device 102 to perform non-volatile storage data takeover processing (processing for setting the non-volatile storage data to correspond to the firmware update data 105). Then, the field device 102 is restarted. Thereby, the update of the firmware is completed.

In addition, for example, a technique is known that enables program layout to be changed without runaway of the program without turning off the power (see, for example, Patent Document 1).
JP-A-2005-182106

  However, in the field network system 100 described above, when the firmware update data 105 becomes new data and the nonvolatile storage data no longer corresponds to the firmware update data 105 (for example, the data format of the nonvolatile storage data and the storage location of the data are If the new firmware update data 105 no longer corresponds to the assumed data format or data storage location), the non-volatile storage data cannot be transferred normally. For example, when the nonvolatile storage data is information (tag information) for identifying a field device, the tag information is initialized when the takeover processing of the field device 102 is performed in a state where the nonvolatile storage data does not correspond to the firmware update data 105. Value (ROM value (fixed value) in firmware update data). Then, even if the field device is restarted, the field device may not be able to perform the intended operation (operation based on firmware update data).

  In this case, there is a method for performing takeover processing of non-volatile storage data by downloading an algorithm (a new non-volatile storage data takeover algorithm 107 shown in FIG. 6) for setting the non-volatile storage data to correspond to the new firmware update data 105. . However, in this case, the field device 102 has to update the nonvolatile storage data transfer algorithm 106 to a new nonvolatile storage data transfer algorithm 107 once. For this reason, for example, the firmware update data 105 including the new nonvolatile storage data takeover algorithm 107 (at this time, the application execution data is the data before the update) is downloaded, and then the updated new application execution data and the new nonvolatile storage are downloaded. It is necessary to download the firmware update data 105 including the data transfer algorithm 107. That is, it is necessary to download the firmware update data 105 twice. In this case, when there are a plurality of field devices, it is necessary to download the number of field devices × 2 and it is not efficient.

  There is also a method in which new firmware update data (new application execution data and data including a new nonvolatile storage data takeover algorithm) is downloaded at a time, and takeover processing is performed after the field device is restarted. However, if the field device performs the takeover process after restarting, it cannot be confirmed whether the takeover process is successful. For this reason, there has been a problem that the reliability of taking over the nonvolatile storage data is lacking.

  An object of the present invention is to provide a technique for efficiently downloading firmware update data and improving the reliability of data transfer.

In order to solve the above-described problem, the setting device according to the first aspect of the present invention provides:
In a transmission device that transmits firmware update data and a setting device that is communicatively connected to a field device that receives firmware update data transmitted from the transmission device.
The predetermined data received from the field device is set to correspond to the firmware update data, and the predetermined data for which the setting has been performed is performed in parallel with the transmission of the firmware update data by the transmission device. A control unit for transmitting to the field device is provided.

The invention according to claim 2 is the setting device according to claim 1,
A communication unit that communicates with the transmission device and the field device;
The predetermined data is:
It is data that needs to correspond to the firmware update data,
The controller is
After detecting transmission of the firmware update data by the transmission device via the communication unit, the predetermined data is received from the field device via the communication unit, and the firmware is received with respect to the predetermined data. Using algorithm data for setting corresponding to update data, setting corresponding to the firmware update data for the received predetermined data, and setting the predetermined data for which the setting has been performed by the transmitting device In parallel with the transmission of the firmware update data, the firmware update data is transmitted to the field device via the communication unit.

The field network system of the invention described in claim 3 is:
A setting device according to claim 1 or 2,
The transmitting device;
The field device,
The transmitter is
A transmitter side communication unit for communicating with the setting device and the field device;
A transmission device side control unit that transmits the firmware update data via the transmission device communication unit,
The field device is
A field device side communication unit that communicates with the setting device and the transmission device;
A field device-side control unit that receives the firmware update data and the predetermined data set to correspond to the firmware update data via the field device-side communication unit;
It is characterized by providing.

  According to the first to third aspects of the invention, the predetermined data set to correspond to the firmware update data is transmitted to the second device in parallel with the transmission of the update firmware. For this reason, firmware update data can be downloaded efficiently, and the takeover reliability of data (predetermined data) can be improved.

  Embodiments according to the present invention will be described below in detail with reference to the accompanying drawings. However, the scope of the invention is not limited to the illustrated examples.

  Embodiments according to the present invention will be described with reference to FIGS. A field network system 10 according to the present embodiment includes a device 1 as a transmission device, field devices 2 to 4, and a temporary device 5 as a setting device. The device 1, the field devices 2 to 4, and the temporary device 5 are H1 communication target devices, and perform information communication via the H1 bus 6 for H1 communication. The device 1 and the field devices 2 to 4 have the same configuration as the field devices 102 to 104 shown in FIG.

  The device 1 is an electronic device composed of a board having a configuration function. The device 1 transmits firmware update data 7 to the field devices 2 to 4 via the H1 bus 6. In the present embodiment, the field device 2 will be described as receiving firmware update data 7.

  The temporary device 5 is an electronic device composed of a board or the like having a function of performing takeover processing of nonvolatile storage data. The internal configuration of the temporary device 5 will be described with reference to FIG. As illustrated in FIG. 2, the temporary device 5 includes a CPU (Central Processing Unit) 11 as a control unit, a RAM 12, a storage unit 13, and a communication unit 14.

  The CPU 11 centrally controls each part of the temporary device 5. The CPU 11 develops a program designated from the system program and various application programs stored in the storage unit 13 in the RAM 12, and executes various processes in cooperation with the program expanded in the RAM 12.

The CPU 11 detects the transmission of firmware update data through the communication unit 14 in cooperation with a temporary device program to be described later, and takes over the nonvolatile storage data as predetermined data using the nonvolatile storage data takeover algorithm. Processing is performed, and the takeover-processed nonvolatile storage data is transmitted to the field device in parallel with the firmware update data.
The nonvolatile storage data takeover algorithm is a setting that associates nonvolatile storage data with firmware update data (for example, the data format of the nonvolatile storage data and the storage area of the data, the data format assumed by the firmware update data, and the data storage Algorithm data to be set).
The nonvolatile storage data is data that needs to be associated with the firmware update data (data that needs to be inherited in the same state as before the update even if the update firmware data is updated). For example, data stored in a nonvolatile storage area and field device-specific setting data (field device tag information, sensor setting values, etc.) correspond to the nonvolatile storage data.
The takeover process is a process for setting the nonvolatile storage data to correspond to the firmware update data.

  The RAM 12 is a volatile memory, and forms a work area for temporarily storing various programs to be executed and data related to these various programs.

  The storage unit 13 includes a flash memory, a ROM (Read Only Memory), and the like, and stores various programs and various data. The storage unit 13 stores a non-volatile storage data takeover algorithm for setting the temporary device program and the non-volatile storage data to correspond to the firmware update data.

  The communication unit 14 transmits / receives information to / from the device 1 and the field devices 2 to 4.

  Next, the internal configuration of the device 1 will be described with reference to FIG. The device 1 includes a CPU 21 as a transmission device side control unit and a communication unit 22 as a transmission device side communication unit.

  The CPU 21 transmits firmware update data via the communication unit 22. The communication unit 22 transmits / receives information to / from the temporary device 5 and the field devices 2 to 4.

Next, the internal configuration of the field device will be described with reference to FIG. The field devices 2 to 4 have the same configuration. Hereinafter, the field device 2 will be described as a representative.
The field device 2 includes a CPU 31 as a field device side control unit and a communication unit 32 as a field device side communication unit.

  The CPU 31 receives the firmware update data and the non-volatile storage data subjected to the takeover process via the communication unit 32. The communication unit 32 transmits / receives information to / from the device 1 and the temporary device 5.

Next, the firmware update data 7 will be described with reference to FIG. As shown in FIG. 4A, the firmware update data 7 includes application execution data, address information, and identification information.
The address information is information indicating the address of the field device to which the firmware update data 7 is transmitted. The identification information is information (firmware version information) for identifying the nonvolatile storage data takeover algorithm used in the takeover process.

  Next, with reference to FIG. 4B, a non-volatile stored data takeover algorithm stored in the storage unit 13 will be described. As shown in FIG. 4B, the storage unit 13 stores a plurality of nonvolatile storage data takeover algorithms. Each nonvolatile storage data takeover algorithm is stored in association with identification information (firmware version information).

Next, a case where the nonvolatile storage data takeover algorithm stored in the storage unit 13 is changed will be described. For example, it is assumed that an external device (not shown) has a desired nonvolatile storage data takeover algorithm to be changed. In this case, a desired nonvolatile storage data takeover algorithm is received from the external device via the communication unit 14, and the received nonvolatile storage data takeover algorithm is stored in the storage unit 13.
Further, for example, the nonvolatile storage data takeover algorithm may be changed by replacing a memory device (a device such as a flash memory) storing the nonvolatile storage data takeover algorithm by the user.

  Next, with reference to FIG. 5, a temporary device process executed by the temporary device 5 will be described. The temporary device processing is processing for performing non-volatile storage data transfer processing using a non-volatile storage data transfer algorithm and transmitting the non-volatile storage data subjected to the transfer processing to the field device 2 in parallel with the firmware update data.

  It is assumed that a plurality of nonvolatile storage data takeover algorithms are stored in the storage unit 13 in advance.

  For example, in the temporary device 5, reading from the storage unit 13 is triggered by automatically detecting that the firmware update data 7 is being transmitted from the device 1 to the field device 2 via the communication unit 14. Then, the temporary device process is executed in cooperation with the CPU 11 and the temporary device program appropriately loaded in the RAM 12.

  First, the address information of the field device 2 included in the firmware update data 7 is acquired via the communication unit 14 (step S11). And the identification information contained in firmware update data is acquired via the communication part 14 (step S12).

  After execution of step S12, a nonvolatile storage data takeover algorithm is selected based on the acquired identification information (step S13). Specifically, one non-volatile stored data takeover algorithm associated with the firmware version information that matches the identification information (firmware version information) is selected from the storage unit 13.

  After execution of step S13, the takeover process is executed by the selected nonvolatile storage data takeover algorithm (step S14). Specifically, nonvolatile storage data is read from the field device 2 (nonvolatile storage data is received via the communication unit 14), and a nonvolatile storage data takeover algorithm is used for the read nonvolatile storage data. Then, takeover processing corresponding to the firmware update data is executed.

  After execution of step S14, the non-volatile storage data subjected to the handover process is transmitted to the field device 2 in parallel with the firmware update data via the communication unit 14 (step S15). After execution of step S15, the temporary device process is terminated.

  As described above, according to the present embodiment, the nonvolatile storage data subjected to the takeover process is transmitted to the field device 2 in parallel with the transmission of the firmware update data. For this reason, the field device 2 needs to download the firmware update data only once, so that the firmware update data can be efficiently downloaded. Further, in parallel with the transmission of the firmware update data, the non-volatile data that has been handed over is transmitted to the field device 2, so that the field device 2 acquires the non-volatile data that has been handed over along with the firmware update data. Can do. For this reason, since the field device 2 can perform the takeover process for the nonvolatile storage data before the restart, the reliability of the takeover of the nonvolatile storage data can be improved.

  Further, since the temporary device 5 performs the takeover process using the nonvolatile storage data takeover algorithm, the field device 2 does not need to perform the takeover process using the nonvolatile storage data takeover algorithm.

  In addition, since the nonvolatile storage data in which the takeover setting is performed is transmitted to the field device 2 in parallel with the transmission of the firmware update data, the field device 2 can perform the download without taking time.

  In addition, the temporary device 5 uses an address for a temporary device (address for temporarily confirming the bus status) defined in the H1 specification, so that an existing H1 bus setting (preliminarily set) is used. The communication connection can be made to the H1 bus without affecting the H1 bus.

  Further, it is not necessary to install a special application in the device 1.

  Further, for example, when the nonvolatile storage data takeover algorithm is acquired from the external device via the communication unit 14, it is not necessary to perform communication according to the rules of H1, so it takes time to change the nonvolatile storage data takeover algorithm. do not do.

  The description in the above embodiment is an example of the field network system according to the present invention, and the present invention is not limited to this.

For example, in the above-described embodiment, the temporary device process is triggered by automatically detecting that the firmware update data 7 is transmitted from the device 1 to the field device 2 via the communication unit 14. However, the present invention is not limited to this. For example, the temporary device 5 receives a notification that the firmware update data 7 is to be transmitted from the device 1 to the field device 2 via the communication unit 14, and detects that the transmission of the firmware update data 7 is detected by the reception. It may be a trigger.

  In step S12 of the temporary device process, the identification information included in the firmware update data 7 is acquired. However, the present invention is not limited to this. For example, the field device 2 may have identification information, and the temporary device 5 may acquire the identification information from the field device 2. In this case, the temporary device 5 identifies the field device 2 based on the address information included in the firmware update data 7 and acquires identification information from the identified field device 2.

  Further, although the temporary device 5 performs the handover process using one nonvolatile storage data handover algorithm, the present invention is not limited to this. For example, in the temporary device 5, a plurality of nonvolatile storage data takeover algorithms may be operated in parallel. Thereby, the update firmware data can be simultaneously updated in the same type or different type field device. For example, even if the field devices 2 to 4 are temperature transmission devices (same type field devices), the field device 2 is a temperature transmission device, and the field devices 3 and 4 are pressure transmission devices (atypical field devices). Even if there is, update firmware data can be updated at the same time. For this reason, as the number of field devices increases, it is possible to realize time reduction by parallel operation of transmission of firmware update data and transmission of takeover-processed nonvolatile storage data.

  In the H1 specification, four addresses for the temporary device 5 are prepared in one local area network link. For this reason, four temporary devices 5 can be installed. In this case, by using the four temporary devices 5 to update the update firmware data, it is possible to improve the execution efficiency of the internal processing of the temporary device 5 and the usage efficiency of the field network system 10.

The device 1 or the temporary device 5 may be a terminal device such as a PC (Personal Computer).

  In addition, the detailed structure and detailed operation of the field network system 1 in the present embodiment can be changed as appropriate without departing from the spirit of the present invention.

It is a figure which shows the structure of the field network system of embodiment which concerns on this invention. It is a block diagram which shows the internal structure of a temporary device. (A) is a block diagram showing an internal configuration of a device. (B) is a block diagram showing an internal configuration of the field device. (A) is a figure explaining firmware update data. (B) is a figure explaining the non-volatile preservation data takeover algorithm memorize | stored in a memory | storage part. It is a flowchart which shows a temporary device process. It is a figure which shows the conventional field network system. It is a figure which shows firmware update data.

Explanation of symbols

1 Device 2 to 4 Field device 5 Temporary device 7 Firmware update data 10 Field network system 11 CPU
12 RAM
13 storage unit 14 communication unit

Claims (3)

In a transmission device that transmits firmware update data and a setting device that is communicatively connected to a field device that receives firmware update data transmitted from the transmission device.
The predetermined data received from the field device is set to correspond to the firmware update data, and the predetermined data for which the setting has been performed is performed in parallel with the transmission of the firmware update data by the transmission device. A setting device comprising a control unit that transmits to a field device. A communication unit that communicates with the transmission device and the field device;
The predetermined data is:
It is data that needs to correspond to the firmware update data,
The controller is
After detecting transmission of the firmware update data by the transmission device via the communication unit, the predetermined data is received from the field device via the communication unit, and the firmware is received with respect to the predetermined data. Using algorithm data for setting corresponding to update data, setting corresponding to the firmware update data for the received predetermined data, and setting the predetermined data for which the setting has been performed by the transmitting device The setting apparatus according to claim 1, wherein the setting device transmits the firmware update data to the field device via the communication unit in parallel with the transmission of the firmware update data. A setting device according to claim 1 or 2,
The transmitting device;
The field device,
The transmitter is
A transmitter side communication unit for communicating with the setting device and the field device;
A transmission device side control unit that transmits the firmware update data via the transmission device communication unit,
The field device is
A field device side communication unit that communicates with the setting device and the transmission device;
A field device-side control unit that receives the firmware update data and the predetermined data set to correspond to the firmware update data via the field device-side communication unit;
A field network system comprising:

Images