JP6002021B2 - Slave device - Google Patents

Description

  Embodiments described herein relate generally to a slave device that is connected to a field network and communicates with a master device.

  Currently, field networks are indispensable for building process automation systems and factory automation systems. In constructing a field network, a system for configuring a network environment by software called a so-called configurator is widely used. In order to connect the inverter device as a slave device to a network constructed using the configurator, a configuration file for causing the configurator to recognize the inverter device is required.

  In the configuration file, various information including the device name, capacity, software version, and corresponding network service contents are described. Then, the configurator executes configuration for identifying the inverter device based on these pieces of information. In addition, there are many configurators in which information on parameters that can be set in the inverter device is included in the configuration file of the inverter device and a function for setting parameters based on the parameter information is supported.

  However, the definition of the configuration file, such as extension, description method, and description contents, differs depending on the type of field network. For example, an EtherNet / IP (registered trademark) has an EDS file, and Profibus (registered trademark) has a configuration file called a GSD file. No.

  A method of integrating multiple field networks called FDT / DTM has also been proposed, but only the greatest common divisor function can be used for the purpose of integrating multiple field networks. Many. In addition, when compared with a method using a configurator dedicated to each field network, it is different from a method used for general system construction.

JP 2009-181247 A

  From the above circumstances, in order to provide a user with an appropriate configuration file for each inverter device, it is necessary to prepare a wide variety of configuration files. Preparing a plurality of configuration files having the same meaning for one product group is a very complicated task for the manufacturer to provide. In many cases, in order to avoid complications, the amount of information described in the configuration file is reduced and unified, but a configuration file having a necessary and sufficient amount of information is often not provided.

  On the other hand, when viewed from the user, it is necessary to select an appropriate configuration file from a large number of options having the same meaning. In addition, the configuration file is often obtained through a website of the inverter device dealer or manufacturer, and it is necessary to access the website of the acquisition site each time. There is an annoying problem.

  Therefore, a slave device that allows a user to easily obtain a configuration file is provided.

According to the slave device of the embodiment, the memory, generates information required to generate a configuration file used in the configuration of each communication node to identify to define any device or is stored . Then, when a configuration file transmission request trigger is given, the file generation / transmission means generates a configuration file based on the generation information and transmits the file to an external terminal.
Further, according to the slave device of the embodiment, the configuration file is stored in the memory. Then, when a configuration file transmission request trigger is given, the file transmission means transmits the file to the external terminal.

The figure which is a 1st embodiment and shows the state by which the personal computer and the inverter apparatus were connected via the communication cable Diagram showing the overall network system configuration Sequence diagram showing the processing performed between the personal computer and the inverter device Figure showing an example of the generated configuration file (1) Figure showing an example of the generated configuration file (2) FIG. 1 equivalent view showing the second embodiment The figure which shows the process performed in the terminal (1) shown in FIG. FIG. 1 equivalent diagram showing the third embodiment The figure which shows the process performed in the terminal (2) shown in FIG. The figure which is 4th Embodiment and shows the process performed in the terminal (3) shown in FIG. The figure which is 5th Embodiment and shows the process performed in terminal (4), (5) shown in FIG. The figure which is 6th Embodiment and shows the state by which the USB memory was connected to the inverter apparatus Sequence diagram showing processing performed by the inverter device FIG. 13 equivalent diagram showing the seventh embodiment FIG. 1 equivalent diagram showing the eighth embodiment

(First embodiment)
Hereinafter, a first embodiment will be described with reference to FIGS. 1 to 5. FIG. 2 shows the configuration of the entire network system. A master device (communication node) controller 1 and a personal computer (personal computer) 2 are connected via an upper communication bus 3 based on a protocol such as EtherNet / IP, for example, which is an upper layer network (control network) 4. Is configured. The personal computer 2 (external terminal) is connected in order to perform initial setting of the network and to monitor the actual communication status.

  The controller 1 is connected to a slave device (communication node) such as an inverter device 5, a machine tool 6, a remote I / O 7, and a gateway 8 via a lower communication bus 9 based on a protocol such as Profibus. Constitutes a lower layer network (narrowly defined field network) 10. For example, a relay 11, a switch 12, an I / O device 13 and the like are connected to the gateway 8 via a lowest communication bus 14 using a protocol such as AS-i, and these are connected to the lowest layer network ( Field end network) 15.

  The configurator is software installed in the personal computer 2 and reads a configuration file related to each slave device. Then, configuration is performed in order to perform initial setting so that the controller 1 and each slave device can communicate with each other via the lower layer network 10. In this embodiment, the configuration file is provided from the slave device side as will be described later. Further, when the configuration is performed, the controller 1 and the personal computer 2 are connected via serial communication such as USB, the Internet, or the like.

  FIG. 1 shows a state in which a personal computer (PC) 2 and an inverter device 5 are connected via a communication cable 16 such as RS485. Moreover, about the inside of the inverter apparatus 5, only the functional part which concerns on the summary of this embodiment is shown with the block. The inverter device 5 includes a CPU 21 (file generation / transmission means), a nonvolatile memory 22 such as an EEPROM or a flash memory, and a communication IC 23. The CPU 21 writes and reads data to and from the nonvolatile memory 22 and controls the communication IC 23 to perform serial communication with the personal computer 2.

  The communication IC 23 is connected to the communication cable 16 via a connector 24 provided on the main body of the inverter device 5. When the data transmitted by the personal computer 2 is received, the data is converted into parallel data and output to the CPU 21. The data written by the CPU 21 is serially converted and transmitted to the personal computer 2. The nonvolatile memory 22 includes a control program (not shown) and the like, inverter specific information 25 that is information (generation information) for generating a configuration file, and parameter information 26 (setting information) used for controlling the inverter device 5. Is remembered. Here, the inverter specific information 25 is information such as the type and capacity of the inverter device 5 and the version of software, for example.

  In the case of a general inverter device, a plurality of items constituting the inverter specific information 25 and the parameter information 26 are distributed and arranged in the source code of the control program and other data areas. The information 25 and 26 in this embodiment are arranged in advance in a predetermined storage area in order to facilitate generation of a configuration file. That is, the storage area corresponds to the generation information storage area. The storage area 27 is an area for storing a configuration file generated based on the information 25 and 26 described above.

  Next, the operation of this embodiment will be described. FIG. 3 is a sequence diagram showing processing performed between the personal computer 2 and the inverter device 5. The CPU 21 of the inverter device 5 performs initial setting or the like when the power is turned on and started (B1). When a user operates the personal computer 2 and a configuration file generation / transmission instruction (transmission request command, transmission request trigger) is transmitted from the personal computer 2 (A1), the CPU 21 receives the inverter-specific information from the nonvolatile memory 22. 25 and parameter information 26 are read out and a configuration file is generated (B2). The generated file is written and stored in the storage area 27 of the nonvolatile memory 22.

  Then, the generated configuration file is transmitted to the personal computer 2 side (B3). The personal computer 2 stores the received configuration file in a storage device such as a hard disk. Thereafter, the user activates the configurator on the personal computer 2 and performs configuration using the acquired file. Note that the terminals (1) to (5) shown in FIG. 3 correspond to processing executed in an interrupted manner when a corresponding event occurs, and these will be described in the second and subsequent embodiments. To do.

FIG. 4 shows an example of the generated configuration file. FIG. 4A is an example of the inverter specific information 25.
ProdCode = 31000; EtherNet
Is the model code of the inverter device. FIG. 4B is an example of the parameter information 25.
2000,3200000,10000
Respectively correspond to the lower limit value, upper limit value, and initial value of the parameter RPI Range.
FIG. 5 is also an example of the parameter information 26, which is I / O scan (periodic communication) information corresponding to the inverter device. For example,
Assem20 =
Corresponds to the assembly number 20.

  As described above, according to the present embodiment, the inverter-specific information 25 necessary for generating the configuration file used for the configuration defining each communication node is stored in the nonvolatile memory 22 of the inverter device 5. To do. Then, when a configuration file generation / transmission instruction is given from the personal computer 2, the CPU 21 generates a configuration file based on the inverter specific information 25 and transmits the file to the personal computer 2. Therefore, the user can easily obtain the configuration file corresponding to the inverter device 5 from the inverter device 5 only by operating the personal computer 2.

(Second Embodiment)
6 and 7 show the second embodiment. The same parts as those in the first embodiment are denoted by the same reference numerals, description thereof is omitted, and different parts will be described below. The inverter device 31 (slave device) of the second embodiment includes a volatile memory 32 such as a RAM, in addition to the nonvolatile memory 22. The nonvolatile memory 22 stores inverter specific information 25 and parameter information 26 together with a control program and the like, and a storage area for the generated configuration file is provided in the volatile memory 32.

  Next, the operation of the second embodiment will be described. FIG. 7 shows processing executed by the CPU 21 of the inverter device 31 at the terminal (1) shown in FIG. The CPU 21 reads the inverter specific information 25 and the parameter information 26 from the nonvolatile memory 22 according to the control program (C1). Then, the read information is written in the storage area of the volatile memory 32 in the configuration file format defined on the code (control program) (C2).

  As in the first embodiment, when a configuration file generation / transmission instruction is transmitted from the personal computer 2 in step A1 shown in FIG. 3, the CPU 21 writes the inverter written in the storage area in the volatile memory 32. When the unique information 25 and the parameter information 26 are read, the file is written into the configuration file storage area in the memory 32 (B2). The subsequent processing is the same as in the first embodiment.

  As described above, according to the second embodiment, the CPU 21 of the inverter device 31 reads the inverter specific information 25 and the parameter information 26 from the nonvolatile memory 22, and stores the information in the configuration file storage area in the volatile memory 32. Write and generate a file. Therefore, the capacity required for the nonvolatile memory 22 can be reduced.

(Third embodiment)
8 and 9 show the third embodiment, and only the parts different from the first embodiment will be described. The inverter device 5A shown in FIG. 8 includes a human interface (hereinafter referred to as HMI) 28 in the main body. The HMI 28 (input means) is composed of input operation keys, a 7-segment display that can display numbers, alphabets, and the like, and is used when the user performs input settings for the parameter information 26, for example.

  Next, the operation of the third embodiment will be described. FIG. 9 shows processing executed by the CPU 21 of the inverter device 5 at the terminal (2) shown in FIG. It is assumed that the user operates the HMI 28 to change, for example, the control characteristics of the inverter device 5 that requires changing the parameter information 26, for example. At this time, a parameter changing function (program module) is activated to change the parameter of the corresponding area (D1). Then, the CPU 21 updates the parameter information 26 with the above function being called as a trigger.

  As described above, according to the third embodiment, when the control characteristic of the inverter device 5 that requires the user to change the parameter information 26 stored in the nonvolatile memory 22 is updated by the user, the CPU 21 The parameter information 26 provided with a separate storage area 22 is updated. Therefore, the parameter information 26 included when the configuration file is generated can always be kept up-to-date.

(Fourth embodiment)
FIG. 10 shows the fourth embodiment, and the differences from the third embodiment will be described. FIG. 10 shows processing executed by the CPU 21 of the inverter device 5 at the terminal (3) shown in FIG. In the fourth embodiment, as one of the inverter specific information 25, one that specifies the type (protocol) of the field network to which the inverter device 5 is connected (corresponding to the designation information) is stored in the nonvolatile memory 22. . That is, a code corresponding to EtherNet / IP or Profibus is specified as a parameter.

  The CPU 21 refers to the area after execution of step B1 and determines that the configuration file to be created corresponds to the field network of the designated protocol (F1). Thereafter, steps B2 and B3 are executed as in the first embodiment.

  As described above, according to the fourth embodiment, when the CPU 21 acquires the designation information of the field network stored in the nonvolatile memory 22, the configuration file is set according to the type of the field network designated by the designation information. Is generated. Accordingly, a configuration file corresponding to the type of field network to which the inverter device 5 is actually connected can be generated.

(Fifth embodiment)
FIG. 11 shows a fifth embodiment, and the differences from the fourth embodiment will be described. 11A shows a process executed by the personal computer 2 at the terminal (4) shown in FIG. 3, and FIG. 11B shows a process executed by the CPU 21 of the inverter device 5 at the terminal (5) shown in FIG. The user activates the software of the personal computer 2 and operates, for example, a GUI (Graphic User Interface) to select the type (protocol) of the field network to which the inverter device 5 is connected (corresponding to the designation information, G1).

  Then, the personal computer 2 designates generation of a configuration file corresponding to the selected protocol (G2). That is, information specifying the field network is included in the command transmitted in step G2. Thereafter, step A1 is executed as in the first embodiment. Then, referring to the designation information in the received command, the CPU 21 of the inverter device 5 determines that the configuration file to be created is associated with the field network of the designated protocol (H1). Thereafter, steps B2 and B3 are executed as in the first embodiment.

  As described above, according to the fifth embodiment, when the CPU 21 acquires the designation information that designates the type of the field network set by the user, the configuration is made according to the type of the field network designated by the designation information. Generate a file. Accordingly, a configuration file corresponding to the type of field network to which the inverter device 5 is actually connected can be generated.

(Sixth embodiment)
12 and 13 show a sixth embodiment. The inverter device 41 of the sixth embodiment includes an HMI 28 and a communication IC 43 corresponding to a CPU 42 (file generation / transmission means) and a USB (Universal Serial Bus). Further, the main body is provided with a USB port 45, and a USB memory 46 (external terminal) as an external storage device is connected to the USB port 45.

  Next, the operation of the sixth embodiment will be described. 13 corresponding to FIG. 3 is only the processing on the inverter device 41 side. Step B4 is inserted between the terminals (2) and (3). In step B4, when an input (transmission request command input, transmission request trigger) for instructing generation / transmission of the configuration file is performed by the user operating the HMI 28, the CPU 42 performs steps B2 ′ and B3 ′. Execute, generate and send configuration file.

  Note that the configuration file generated in step B2 'is transmitted to the USB memory 46 in step B3' without being written in the nonvolatile memory 22. Then, the USB memory 46 writes and stores the transmitted configuration file in itself.

  As described above, according to the sixth embodiment, the inverter device 41 is provided with the HMI 28 for the user to perform an input operation, and the CPU 42 receives the input for instructing the generation / transmission of the configuration file via the HMI 28. Generate and send a file. Therefore, the configuration file can be generated by the inverter device 41 alone, and the generated file can be transmitted to the USB memory 46 and stored. Since it is not necessary to provide a configuration file storage area in the nonvolatile memory 22, the capacity can be reduced.

(Seventh embodiment)
FIG. 14 shows a seventh embodiment, and only the parts different from the sixth embodiment will be described. In FIG. 14 corresponding to FIG. 13, step B5 is arranged instead of step B4. In step B5, when the CPU 42 (external terminal detecting means) detects that the USB memory 46 is connected to the USB port 45 (transmission request trigger), steps B2 ′ and B3 ′ are executed. Therefore, in the seventh embodiment, the HMI 28 is not necessarily required to generate the configuration file.

  As described above, according to the seventh embodiment, when the CPU 42 detects that the USB memory 46 is connected to the USB port 45 and can perform USB communication, the CPU 42 generates and transmits the file. . Therefore, the configuration file can be generated and transmitted without the user performing an input operation via the HMI 28 as in the sixth embodiment.

(Eighth embodiment)
FIG. 15 shows an eighth embodiment, and different parts from the first embodiment will be described. In the eighth embodiment, only the configuration file storage area 27 is provided in the nonvolatile memory 22B of the inverter device 5B, and the storage area 27 is in a stage before the inverter device 5B is shipped. A configuration file generated in advance is stored. And CPU21B (file transmission means) will read a configuration file from the storage area 27, and will transmit to the personal computer 2 side, if the transmission request command from the personal computer 2 is received similarly to 1st Embodiment. That is, only step B3 in FIG. 3 is executed.

  As described above, according to the eighth embodiment, the configuration generated in advance in the non-volatile memory 22B of the inverter device 5B is stored, and when the transmission request trigger is given, the CPU 21B stores the configuration file in the personal computer. 2 to send. Therefore, the capacity of the nonvolatile memory 22B can be reduced as compared with the nonvolatile memory 22 of the first embodiment.

Although several embodiments of the present invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.
For example, in the first embodiment, communication between the personal computer 2 and the inverter device 5 may be performed by wireless communication such as Bluetooth (registered trademark) or wireless LAN.
A power source for operating the CPU 21, the nonvolatile memory 22, and the communication IC 23 may be supplied from the personal computer 2 to the inverter device 5 side using a power supply line arranged in the RS485 communication cable.

The memory is not limited to the one built in the inverter device 5 but may be an external storage device such as a smartphone, a tablet, or an SD card connected to the inverter device 5. The USB memory in the sixth embodiment may also be an external storage device such as an SD card.
The present invention is not limited to the inverter device, and can be applied to any other slave device that is connected to the field network and communicates with the master device, such as a machine tool 6, a remote I / O 7, and a gateway 8.

  In the drawings, 1 is a controller (master device), 2 is a personal computer (external terminal), 5 is an inverter device (slave device), 10 is a lower layer network (field network), 21 is a CPU (file generation / transmission means), 22 is nonvolatile memory, 25 is inverter specific information (generation information), 26 is parameter information (setting information), 28 is HMI (input means), 31 is an inverter device (slave device), 32 is volatile memory, 41 is An inverter device (slave device), 42 is a CPU (file generation / transmission means, external terminal detection means), and 46 is a USB memory (external terminal).

Claims (8)

A slave device connected to the field network and communicating with the master device,
A memory for generating information required to generate a configuration file used in the configuration to identify defines each communication node any device or in order to perform the communication is stored,
A communication means for communicating with an external terminal;
A slave comprising: a file generation / transmission unit that generates a configuration file based on the generation information when a configuration file transmission request trigger is given, and transmits the configuration file to the external terminal. machine.   The slave device according to claim 1, wherein the file generation / transmission unit uses, as the transmission request trigger, reception of a configuration file transmission request command transmitted from the external terminal. An external terminal detecting means for detecting that the external terminal is in a communicable state via the communication means;
The slave device according to claim 1, wherein the file generation / transmission unit uses the transmission request trigger when the external terminal is in a communicable state. Provided with input means for the user to perform input operations,
2. The slave device according to claim 1, wherein the file generation / transmission means uses the transmission request command input through the input means as the transmission request trigger. An external terminal detection means for detecting that the external terminal is in a communicable state via the communication means;
Input means for the user to perform an input operation,
The generation information includes a selection parameter for determining which to select as the transmission request trigger,
The file generation / transmission means receives the transmission request command based on the selection parameter, the external terminal is in a communicable state, and the transmission request command is input via the input means. The slave device according to claim 2, wherein any one of the transmission request triggers is used. The memory also stores setting information related to the control of the device body,
6. The file generation / transmission unit handles the setting information as a part of the generation information, and updates the generation information using the update of the setting information as a trigger. The slave device according to any one of the items.   The file generation / transmission means is configured to be able to acquire designation information designating a field network type, and generates the configuration file according to the field network type designated by the designation information. The slave device according to any one of claims 1 to 6. A slave device connected to the field network and communicating with the master device,
A memory storing a configuration file used for a configuration that defines and identifies what device each communication node performs to perform the communication;
A communication means for communicating with an external terminal;
A slave device comprising file transmission means for transmitting a configuration file transmission request trigger to the external terminal when a configuration file transmission request trigger is given.

Images