WO2015136965A1 - 制御機器、制御システム、制御機器の制御方法、および、制御システムの制御方法 - Google Patents
制御機器、制御システム、制御機器の制御方法、および、制御システムの制御方法 Download PDFInfo
- Publication number
- WO2015136965A1 WO2015136965A1 PCT/JP2015/050879 JP2015050879W WO2015136965A1 WO 2015136965 A1 WO2015136965 A1 WO 2015136965A1 JP 2015050879 W JP2015050879 W JP 2015050879W WO 2015136965 A1 WO2015136965 A1 WO 2015136965A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- recording medium
- data
- type
- firmware
- control
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
Definitions
- the present invention relates to writing data to a control device.
- control devices such as PLCs (programmable logic controllers) that control the system are used.
- the said control apparatus controls the said system by performing a calculation based on a control program.
- various techniques have been proposed for downloading data such as a control program in such a control device.
- Patent Document 1 discloses a technique related to parameter setting for each unit of a control device. More specifically, when downloading parameters from the information processing device to the control device, the information processing device compares the version of the model information definition file used for parameter setting with the version of the unit in the control device. The information processing apparatus executes download to the control device when both versions match or the unit version is newer, and downloads to the control device when the unit version is older. An error is displayed after the download is prohibited.
- Patent Document 2 discloses a program creation support apparatus that causes a control device to download a control program and additional information of the control program. More specifically, when downloading a control program and additional information to the control device, the program creation support device stores the additional information in the memory capacity if the control device cannot store the additional information in terms of memory capacity. Then, the control device is made to download the control program and the additional information.
- a control system is required to download programs and data to a control device quickly and easily. This is also affected by the fact that downloading in the control device is performed at the time of mass production of the control device and when the control device fails.
- the download is performed quickly from the viewpoint of improving productivity in mass production. Further, in order to avoid downloading erroneous data or the like at the time of mass production, it is preferable that the download is performed simply.
- the download is performed quickly in order to shorten the production stop time due to the failure of the control device.
- the download is performed simply so that even an unskilled worker at the manufacturing site can download the data without fail.
- the present invention has been conceived in view of such circumstances, and an object thereof is to enable a program and data to be written in a control device quickly and easily.
- control equipment includes a reading device for reading data of a portable recording medium, a storage device for storing data used for control, and a processor for writing data recorded on the portable recording medium to the storage device.
- a reading device for reading data of a portable recording medium
- a storage device for storing data used for control
- a processor for writing data recorded on the portable recording medium to the storage device.
- combination information that is information for specifying a combination of data types is further recorded.
- the processor stores the portable recording medium.
- the data recorded in is stored in the storage device. If the combination information recorded on the portable recording medium does not include the combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium, the processor Data recorded on the medium is not written to the storage device.
- the data stored in the storage device is one type or a plurality of types of firmware of the control device.
- the data recorded on the portable recording medium is one type or a plurality of types of setting data used for control by firmware.
- the combination information is information that identifies a combination of the type of firmware and the type of setting data used for control by the firmware.
- the data recorded on the portable recording medium is one type or a plurality of types of firmware of the control device.
- the data stored in the storage device is one type or a plurality of types of setting data used for control by firmware.
- the combination information is information that identifies a combination of the type of firmware and the type of setting data used for control by the firmware.
- the control device when the combination information recorded on the portable recording medium does not include a combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium, A notification unit that performs a notification operation is further provided.
- a control system including a control device and a support device for recording data written in the control device on a portable recording medium.
- the support device includes a recording device for recording information on a portable recording medium, and a controller for controlling the operation of the recording device.
- the controller is configured to cause the recording device to record data and combination information, which is information specifying the type of data combined with the type of data, on a portable recording medium.
- the control device includes a reading device for reading data of the portable recording medium, a storage device for storing data used for control of the control device, and a processor for writing the data recorded on the portable recording medium to the storage device Including.
- the processor stores the portable recording medium. Write the data recorded in the storage device. If the combination information recorded on the portable recording medium does not include the combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium, the processor Data recorded on the medium is not written to the storage device.
- the data stored in the storage device is one or more types of firmware for controlling the operation of the control device.
- the data recorded on the portable recording medium is one type or a plurality of types of setting data used for control by firmware.
- the combination information is information that identifies a combination of the type of firmware and the type of setting data used for control by the firmware.
- the data stored in the storage device is one type or a plurality of types of setting data used for control by firmware.
- the combination information is information that identifies a combination of the type of firmware and the type of setting data used for control by the firmware.
- control device when the combination information recorded on the portable recording medium does not include a combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium, A notification unit that performs a notification operation is further included.
- a control device control method executed by a processor of a control device including a reading device for reading data of a portable recording medium and a storage device for storing data used for control.
- a portable recording medium data and combination information that is information for specifying a combination of data types are recorded.
- the control method determines whether the combination information recorded on the portable recording medium includes a combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium.
- the combination information recorded on the portable recording medium includes a combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium. Writing the recorded data to the storage device.
- the method further includes a step of executing notification without writing the data recorded on the portable recording medium to the storage device.
- a control method for a control system including a control device and a support device for recording data written in the control device on a portable recording medium.
- the support device includes a recording device for recording information on a portable recording medium.
- the control method includes a step in which the support device causes the recording device to record data and combination information that is information specifying a data type to be combined with the data type on a portable recording medium.
- the control device includes a reading device for reading data on the portable recording medium and a storage device for storing data used for control of the control device.
- the control device determines whether the combination information recorded on the portable recording medium includes a combination of the type of data stored in the storage device and the type of data recorded on the portable recording medium.
- control device is configured such that the combination information recorded on the portable recording medium includes the type of data stored in the storage device and the type of data recorded on the portable recording medium.
- control method includes a combination of the type of data stored in the storage device and the type of data recorded in the portable recording medium as the combination information recorded in the portable recording medium by the control device. If not, it further comprises a step of executing notification without writing the data recorded on the portable recording medium to the storage device.
- the control device can determine whether or not the data recorded on the recording medium can be written according to the combination information recorded on the recording medium. Therefore, when writing data in the control device, it is not necessary for an operator who attends the writing to have knowledge for determining whether data can be written to the control device.
- FIG. 1 is a diagram schematically illustrating an example of a configuration of a manufacturing site where each of the control systems according to the four embodiments is used.
- FIG. 1 when consumer goods 5 flow on conveyor 4 along the direction indicated by arrow A ⁇ b> 1 at the manufacturing site, each consumer goods 5 is processed in each of manufacturing apparatuses 2 ⁇ / b> A, 2 ⁇ / b> C, 2 ⁇ / b> E. Applied.
- Consumer goods 5 means, for example, products manufactured at a factory.
- goods for general consumers such as food, medicines, clothes, household goods, home appliances, automobiles, or smartphones can be cited.
- Other examples of the consumer goods 5 include parts used for general consumer products such as semiconductors, liquid crystal panels, automobile parts, and wood.
- Manufacturing devices 2A, 2C, and 2E mean devices for manufacturing consumer goods.
- manufacturing apparatus 2A, 2C, 2E a semiconductor manufacturing apparatus, a machine tool, a packaging machine, and a press machine are mentioned, for example.
- the manufacturing apparatuses 2A, 2C, and 2E are equipped with FA control equipment (hereinafter simply referred to as “control equipment”) for controlling each manufacturing apparatus. More specifically, the control devices 3A and 3B are mounted on the manufacturing apparatus 2A. Control devices 3C and 3D are mounted on the manufacturing apparatus 2C. Control devices 3E and 3F are mounted on the manufacturing apparatus 2E.
- An example of the control devices 3A to 3F is a PLC. Further, the control devices 3A to 3F may include a display device, a sensor, a servo motor, a robot, and the like in a broad sense.
- Control system configuration The configuration of the control system according to each embodiment will be described.
- the PLC that controls a control target such as a machine or facility will be described as a typical example of the control device (the control devices 3A to 3F shown in FIG. 1).
- the control device according to the present invention is not limited to the PLC, and can be applied to various control devices.
- FIG. 2 is a diagram schematically showing the system configuration of the control system 1.
- control system 1 includes a PLC 100 and a support device 300.
- the support device 300 performs various parameter settings, programming, monitoring, debugging, and the like for a program that can be executed in the PLC 100.
- the PLC 100 and the support device 300 are typically configured to be communicable according to the USB (Universal Serial Bus) standard.
- the support apparatus 300 records a program and data written in the PLC 100 in a portable recording medium (hereinafter simply referred to as “recording medium”) 500 that can be read by the PLC 100.
- recording medium 500 is a recording medium that can be attached to and detached from the PLC 100 and the support apparatus 300.
- the PLC 100 includes a CPU (Central Processing Unit) unit 104 that executes control operations and one or more IO (Input / Output) units 106. These units are configured to exchange data with each other via the PLC system bus 108. These units are supplied with power of an appropriate voltage by the power supply unit 102.
- CPU Central Processing Unit
- IO Input / Output
- the PLC 100 exchanges data with various field devices via the IO unit 106 (connected via the PLC system bus 108) and / or via the field bus 110.
- These field devices include an actuator for performing some processing on the control target, a sensor for acquiring various information from the control target, and the like.
- FIG. 2 shows a servomotor driver 30 that drives the detection switch 10, the relay 20, and the motor 32 as an example of such a field device.
- the PLC 100 is connected to the remote IO terminal 200 via the field bus 110.
- the remote IO terminal 200 basically performs processing related to general input / output processing in the same manner as the IO unit 106. More specifically, the remote IO terminal 200 includes a communication coupler 202 for performing processing related to data transmission via the field bus 110 and one or more IO units 204. These units are configured to exchange data with each other via the remote IO terminal bus 208.
- FIG. 3 is a diagram illustrating an example of a functional configuration of a PLC that is an example of a control device.
- system firmware 104A and add-on firmware 104B are installed in the PLC 100.
- the system firmware 104A is software that provides the basic functions of the PLC 100.
- the system firmware 104A includes software for realizing basic functions (program execution, communication, sensing, etc.) of the control device, such as “Basic middleware” and “Basic application”.
- the system firmware 104A includes an OS (Operating System).
- the system firmware 104A includes software for controlling hardware resources installed in the control device such as a display device and a memory of the control device, such as “Bootloader”, “FPGA”, and “Device driver”.
- the add-on firmware 104B is software that adds application functions to the control device.
- the applied function is a function specific to the manufacturing apparatus in which the control device is mounted. An example is a temperature control function or a special communication function.
- the application function is a function that is different from the basic function of the control device in order to increase the competitiveness of the manufacturer of the control device, and is a function that is desired to increase the value of the control device. That is, the application function may be different for each control device and for each manufacturing apparatus on which the control device is mounted.
- the PLC 100 further includes user configuration data 104C.
- the user configuration data 104C is an example of setting data, and is data (data group) for customizing the PLC 100 by changing settings or programming.
- the user configuration data 104C used in the PLC 100 includes data for customizing the system firmware 104A and data for customizing the add-on firmware 104B.
- FIG. 4 is a diagram illustrating an example of a hardware configuration of the PLC 100.
- the PLC 100 includes a processor 122, a main memory 124, a nonvolatile memory 126, an LED (Light Emitting Diode) 128, an input device 132, a connector 134, and an SD (Secure Data) memory.
- Card interface 136 is a diagram illustrating an example of a hardware configuration of the PLC 100.
- the PLC 100 includes a processor 122, a main memory 124, a nonvolatile memory 126, an LED (Light Emitting Diode) 128, an input device 132, a connector 134, and an SD (Secure Data) memory.
- SD Secure Data
- the processor 122 controls the operation of the PLC 100 by executing a program stored in the nonvolatile memory 126 or the like.
- the main memory 124 can be used as a work area for the processor 122.
- the nonvolatile memory 126 stores various data such as programs.
- the LED 128 is an example of a notification unit, and the lighting operation is controlled by the processor 122.
- the input device 132 accepts input of information from the outside and is configured by buttons, for example.
- the connector 134 is provided for connection to an external device such as a USB (Universal Serial Bus) memory.
- the SD memory card interface 136 reads information recorded on an SD memory card which is an example of the recording medium 500.
- FIG. 5 is a diagram illustrating an example of a hardware configuration of the support apparatus 300. As shown in FIG. 5, the support apparatus 300 is typically composed of a general-purpose computer.
- the support apparatus 300 includes a CPU 302 that executes various programs including an OS, a ROM (Read Only Memory) 304 that stores BIOS and various data, and data necessary for the CPU 302 to execute the programs.
- the CPU 302 and the RAM 306 constitute an example of a controller.
- the support program 330 is stored in the hard disk 308.
- the support program 330 includes an application program for adjusting the program executed by the support apparatus 300 in the PLC 100.
- the support apparatus 300 further includes a keyboard 310 and a mouse 312 that accept operations from the user, and a monitor 314 for presenting information to the user.
- the support device 300 also includes an SD memory card interface 316 for reading data recorded on the recording medium 500 and recording data on the recording medium 500.
- the support apparatus 300 includes a communication interface (IF) 318 for communicating with the PLC 100 (CPU unit 104) and the like.
- Programs such as the support program 330 executed by the support device 300 can be stored in an optical recording medium and distributed.
- the program stored in the optical recording medium can be read by a drive device (not shown) dedicated to the optical recording medium and stored in the hard disk 308 or the like.
- the program may be written from a host computer or the like via a network.
- the hard disk 308 is an example of a storage device.
- the SD memory card interface 316 is an example of a recording device.
- the program executed in the control device such as the PLC 100 includes the firmware of the control device.
- firmware is roughly classified into two types: system firmware and add-on firmware.
- the PLC 100 may write these programs via the recording medium 500.
- the support apparatus 300 records the above-described two types of firmware on the recording medium 500 for the PLC 500. More specifically, the support apparatus 300 records the two types of firmware on the recording medium 500 in a predetermined combination.
- the control system of the first embodiment will be described.
- FIG. 6 is a diagram schematically illustrating an example of a functional configuration of the support apparatus 300 according to the first embodiment of the control system. As illustrated in FIG. 6, the support apparatus 300 stores a project file 350, a firmware database 360, and a combination table 370.
- the project file 350 is an example of a data group for operating the control device, and includes a user program (system firmware and add-on firmware described later) and data representing the system configuration (user configuration data). More specifically, the project file 350 includes information specifying system firmware and add-on firmware executed in the PLC 100, and user configuration data that is data for setting in these firmware.
- the project file 350 is stored in the HDD 308, for example.
- the firmware database 360 is a database that stores firmware data of the control device and its license.
- the firmware database 360 identifies firmware according to the type specified in the project file 350.
- the type of firmware includes a large classification (system firmware, add-on firmware,%) Related to firmware and a classification based on version (Ver1.0, Ver1.1,).
- the firmware database 360 is realized by, for example, the HDD 308 that stores firmware and the CPU 302 that executes a search for the stored firmware.
- the combination table 370 stores information on combinations of data stored in the firmware database 360.
- the combination table 370 includes information for identifying the type of add-on firmware that normally operates on each type of system firmware for each type of system firmware.
- the combination table 370 is stored in the HDD 308, for example.
- the combination table 370 includes information for identifying the type of user configuration data that can be used for setting each type of system firmware for each type of system firmware.
- the combination table 370 includes information for identifying the type of user configuration data that can be used for setting each type of add-on firmware for each type of add-on firmware.
- FIG. 7 is a diagram illustrating an example of information included in the combination table 370 according to the first embodiment.
- the combination table 370 includes information for specifying the type of add-on firmware that can be used (normally operates) on the version of each system firmware.
- the type specified here identifies the title and version of the add-on firmware. That is, in the combination table 370, even if the title is common, add-on firmware having different versions are identified as different types of add-on firmware.
- the system firmware version and the add-on firmware version can be specified by, for example, the file name of each firmware program.
- information “Add-on_A V1.0” is associated with the system firmware of the version “V1.0”. This means that on the system firmware of version “V1.0”, the program of version “V1.0” of the add-on firmware of the type “Add-on_A” operates normally.
- information “Add-on_A V1.0” and information “Add-on_B V1.0” are associated with the system firmware of version “V1.1”.
- the program of version “V1.0” of the add-on firmware type “Add-on_A” and the version “V1” of the add-on firmware type “Add-on_B” .0 means that the program operates normally.
- a table as shown in FIG. 7 is stored in the HDD 308, for example.
- the information specifying the combination as described above can be stored in any known format (for example, a function) other than the table format.
- the support apparatus 300 stores in the recording medium 500 the combination system firmware and add-on firmware specified in the combination table. More specifically, in the support apparatus 300, software for creating a project file (for example, an application for creating a project file) is installed. In the application, system firmware is first set. Next, the application accepts designation of add-on firmware. However, the application accepts designation only for add-on firmware that can operate normally on the designated system firmware. In other words, after setting the system firmware, the application accepts only the specification of add-on firmware that can operate normally on the set system firmware in the above table, and when any other add-on firmware is specified Perform error notification and the like.
- software for creating a project file for example, an application for creating a project file
- the application stores the system firmware and add-on firmware specified in the project file in the recording medium 500. Therefore, the combination of system firmware and add-on firmware stored in the recording medium 500 in the present embodiment is a combination that can operate normally.
- FIG. 8 is a flowchart of an example of processing executed in the support device 300.
- This process is a process for the support apparatus 300 to record the firmware in the firmware database 360 on the recording medium 500.
- the processing is realized by the CPU 302 executing a given program (for example, the above-described application for creating a project file).
- step S10 CPU 302 accepts selection of the type of system firmware and the type of add-on firmware.
- step S12 the CPU 302 determines whether or not the combination of the system firmware and add-on firmware that has been designated in step S10 can be combined based on the combination table 370.
- control proceeds to step S16 (YES in step S12), and the CPU 302 determines that combinations are not possible (for example, combinations not defined in combination table 370). Then, control proceeds to step S14 (NO in step S12).
- step S14 the CPU 302 informs that the selected combination is not permitted, and returns the control to step S10.
- the notification is realized, for example, by displaying a message indicating that the combination is not permitted on the monitor 314.
- step S16 the CPU 302 determines whether an instruction to write to the recording medium 500 has been input.
- CPU 302 waits for an instruction in step S16 until it is determined that the instruction has been input (NO in step S16).
- the CPU 302 advances the control to step S18 (YES in step S16).
- step S18 the CPU 302 records the designated system firmware and add-on firmware in the recording medium 500, and ends the process.
- the support apparatus 300 records the above combination table together with the configuration data on the recording medium 500.
- the configuration of the control system will be described.
- the combination table 370 illustrated in FIG. 6 includes information for specifying a combination for user configuration data. More specifically, the combination table 370 includes information for specifying a combination of user configuration data and system firmware, and information for specifying a combination of user configuration data and add-on firmware.
- FIG. 9 is a diagram schematically showing an example of information for specifying a combination of system firmware and user configuration data.
- the system firmware version is associated with the type (version) of user configuration data that can be used for each system firmware.
- version “V1.0” of system firmware includes user configuration data of version “User configuration data (System) for V1.0” and user of version “User configuration data (System) for V1.1”.
- Configuration data is associated.
- the system firmware version can be specified by, for example, the file name of each firmware program.
- the version of the user configuration data can be specified by the file name of the data, for example.
- FIG. 10 is a diagram schematically showing an example of information for specifying a combination of add-on firmware and user configuration data.
- the version of add-on firmware and the type (version) of user configuration data that can be used for each system firmware are associated.
- FIG. 10 shows the relationship for one type “add-on A” of the multiple types of add-on firmware.
- the add-on firmware of the add-on A version “V1.0” is associated with the user configuration data of the version “User configuration data (Add-on_A) for V1.0”.
- the version of the add-on firmware can be specified by, for example, the file name of each firmware program.
- FIG. 11 is a flowchart of a process for recording user configuration data on the recording medium 500, which is executed by the support apparatus 300 according to the second embodiment.
- step S20 CPU 302 accepts selection of user configuration data.
- step S22 the CPU 302 determines whether an instruction to write to the recording medium 500 has been received. If it is determined that the instruction has not been received yet, the instruction is awaited in step S22 (NO in step S22). If it is determined that the instruction has been received, the control proceeds to step S24 (YES in step S22).
- step S24 the CPU 302 generates a combination table corresponding to the user configuration data selected in step S20 on the recording medium 500.
- “Corresponding combination table” means a portion of the combination table 370 including the selected user configuration data. More specifically, for example, as shown in FIG. 9, the user configuration data of the version “User configuration data (System) for V1.0” is the version “V1.0”, “V1.1” and “V1”. .2 ”associated with system firmware. For this reason, when the user configuration data of the version “User configuration data (System) for V1.0” is selected, the version “V1.0” “V1.1” is selected from the combination table 370 in step S24. And the part corresponding to the system firmware of “V1.2” is extracted, so that the “corresponding combination table” is generated.
- the user configuration data of version “User configuration data (Add-on_A) for V1.0” is the add-on firmware of versions “V1.0” and “V1.1” of add-on A Associated with. For this reason, when user configuration data of version “User configuration data (System) for V1.0” is selected, version “V1.0”, “V1.1” and “V1. By extracting the portion including the system firmware of “2”, the “corresponding combination table” is generated.
- step S 26 the CPU 302 stores the selected user configuration data and the combination table generated in step S 24 in the recording medium 500. Record and finish the process.
- the CPU 302 records the selected user configuration data and the combination table corresponding to the user configuration data on the recording medium 500.
- the combination table recorded on the recording medium 500 only needs to include at least a portion corresponding to the selected user configuration data. That is, for example, the entire combination table 370 may be recorded on the recording medium 500 in step S26.
- FIG. 12 is a flowchart of data writing processing to the PLC using the recording medium 500 on which data is recorded by the processing as shown in FIG.
- the processing in FIG. 12 is executed by the processor 122 of the PLC.
- the processor 122 executes the process of FIG. 12 with the recording medium 500 mounted on the SD memory card interface 136.
- step S ⁇ b> 30 the processor 122 records a combination of user configuration data stored in the recording medium 500 and system firmware or add-on firmware installed in the PLC 100 in the recording medium 500. It is determined whether it is appropriate based on the contents defined in the combination table (steps S24 and S26). More specifically, the processor 122, when the system firmware or add-on firmware installed in the PLC 100 is associated with the user configuration data recorded in the recording medium 500 in the combination table, the combination is Judge that it is appropriate. In addition, the processor determines that the combination is not appropriate when it is not associated. When the processor 122 determines that the combination is appropriate, the processor 122 advances the control to step S32 (YES in step S30). If the processor 122 determines that the combination is not appropriate, the processor 122 advances the control to step S34 (NO in step S30).
- step S32 the processor 122 writes the user configuration data recorded in the recording medium 500 to the nonvolatile memory 126, and ends the processing in FIG.
- step S34 the processor 122 informs that the data recorded in the recording medium 500 is invalid without performing the writing as performed in step S32, and ends the processing.
- the suitability of the combination is determined according to the combination table stored in the recording medium 500. That is, it is not necessary for the worker who attends the work of writing the user configuration data to have knowledge about the suitability of the combination of the user configuration data and the system firmware and / or add-on firmware. Thereby, the writing can be executed quickly and easily.
- the worker who attends the above operation operates, for example, a switch for turning on the power to the PLC 100, operates a switch for starting the processing of FIG. 12, and / or attaches the recording medium 500 to the PLC 100. To do.
- step S34 If the user configuration data in the recording medium 500 is not compatible with the system firmware and / or add-on firmware installed in the PLC 100, notification is made in step S34. Thereby, in PLC100, it can avoid writing incorrect user configuration data. Further, in PLC 100, when a version change of system firmware and / or add-on firmware that is not intended by a manager at the manufacturing site is made, the change can be easily found.
- the support apparatus 300 records system firmware, add-on firmware, user configuration data, and a combination table on the recording medium 500.
- the PLC 100 writes data using the recording medium 500.
- FIG. 13 is a flowchart of a process for recording on the recording medium 500 in the support apparatus 300 according to the third embodiment.
- CPU 302 accepts selection of system firmware and add-on firmware.
- step S42 the CPU 302 determines whether or not the combination selected in step S40 is appropriate based on the contents defined in the combination table 370 (see FIG. 7). Then, if CPU 302 determines that it is appropriate, it proceeds to step S46 (YES in step S42). If CPU 302 determines that it is not appropriate, control proceeds to step S44 (NO in step S42).
- step S44 the CPU 302 notifies that the combination of the selected system firmware and add-on firmware is not appropriate, and returns the control to step S40.
- step S46 the CPU 302 accepts selection of user configuration data. And control is advanced to step S48.
- step S48 the CPU 302 determines that the user configuration data selected in step S46 is the system firmware or add-on firmware selected in step S40 based on the contents defined in the combination table 370 (see FIG. 9 or FIG. 10). It is judged whether it is a thing combined appropriately. Then, if CPU 302 determines that it is appropriate, it proceeds to step S52 (YES in step S48). If CPU 302 determines that it is not appropriate, control proceeds to step S50 (NO in step S48).
- step S50 the CPU 302 informs that the selected user configuration data is not properly combined with the already selected system firmware and / or add-on firmware, and controls to step S46. return.
- step S52 the CPU 302 determines whether an instruction to write to the recording medium 500 has been received. If it is determined that the instruction has not been received yet, the instruction is awaited in step S52 (NO in step S52). If it is determined that the instruction has been received, the control proceeds to step S54 (YES in step S52).
- step S54 the CPU 302 generates a combination table corresponding to the system firmware and add-on firmware selected in step S40 and the user configuration data selected in step S46.
- the generation of the combination table corresponds to 1) generation of a combination table corresponding to the selected system firmware, 2) generation of a combination table corresponding to the selected add-on firmware, and 3) corresponding to the selected user configuration data. Includes generation of combination tables.
- step S56 the CPU 302 records the system firmware and add-on firmware selected in step S40, the user configuration data selected in step S46, and the combination table generated in step S54 on the recording medium 500 for processing. End.
- FIG. 14 is a flowchart of data writing processing to the PLC 100 using the recording medium 500.
- the processor 122 executes the process of FIG. 14 with the recording medium 500 mounted on the SD memory card interface 136.
- step S60 processor 122 determines whether or not user configuration data is stored in PLC 100.
- the processor 122 determines whether or not a file having a file name including a predetermined character string for user configuration data is stored in the nonvolatile memory 126, for example.
- the processor 122 advances the control to step S64 (YES in step S60).
- the processor 122 advances the control to step S62 (NO in step S60).
- step S62 the processor 122 writes all the data stored in the recording medium 500 to the nonvolatile memory 126, and ends the process of FIG.
- step S64 the processor 122 determines the type of data stored in the recording medium 500. If processor 122 determines that only firmware (system firmware and add-on firmware) is stored, control proceeds to step S66. If the processor 122 determines that firmware (system firmware and add-on firmware) and user configuration data are stored, the processor 122 proceeds to step S72. If the processor 122 determines that only the user configuration data is stored, the processor 122 advances the control to step S74.
- step S66 the processor 122 determines the user configuration data stored in the PLC 100 and the firmware (system firmware and add-on firmware stored in the recording medium 500 based on the contents of the combination table stored in the recording medium 500. ) Is determined to be appropriate. More specifically, the processor 122 extracts a part including the system firmware in the recording medium 500 from the combination table in the recording medium 500, and the extracted part includes the user configuration data in the PLC 100. Determine whether or not. Further, the processor 122 extracts a part including the add-on firmware in the recording medium 500 from the combination table in the recording medium 500, and determines whether the extracted part includes the user configuration data in the PLC 100. To do. The determination “include” corresponds to the determination that the combination is appropriate. The determination “not included” corresponds to the determination that the combination is not appropriate.
- step S68 YES in step S66. If the processor 122 determines that the user configuration data in the PLC 100 is not appropriately combined with either the system firmware or the add-on firmware in the recording medium 500, the processor 122 advances the control to step S70 (NO in step S66).
- step S68 the processor 122 writes the firmware (system firmware and add-on firmware) stored in the recording medium 500 to the nonvolatile memory 126 while leaving the user configuration data in the PLC 100, and ends the processing of FIG. .
- step S70 the processor 122 informs that the recording medium 500 has illegal data without performing the writing in step S68, and ends the process.
- the notification is, for example, lighting or blinking of the LED 128.
- step S72 the processor 122 writes the firmware (system firmware and add-on firmware) and user configuration data in the recording medium 500 to the nonvolatile memory 126, and ends the process of FIG.
- step S74 the processor 122, based on the contents of the combination table stored in the recording medium 500, the firmware (system firmware and add-on firmware) installed in the PLC 100 and the user configuration recorded in the recording medium 500. Judge whether the combination with data is appropriate. More specifically, the processor 122 extracts a part including the user configuration data in the recording medium 500 from the combination table in the recording medium 500, and the extracted part is the system firmware or add-on in the PLC 100. Determine if the firmware is included. The determination “include” corresponds to the determination that the combination is appropriate. The determination “not included” corresponds to the determination that the combination is not appropriate.
- step S76 determines that the user configuration data in the recording medium 500 is appropriate as a combination with the system firmware or add-on firmware in the PLC 100. If the processor 122 determines that the user configuration data in the recording medium 500 is not properly combined with either the system firmware or the add-on firmware in the PLC 100, the processor 122 advances the control to step S78 (NO in step S74).
- step S76 the processor 122 writes the user configuration data in the recording medium 500 to the nonvolatile memory 126 while leaving the system firmware or add-on firmware installed in the PLC 100, and ends the processing of FIG.
- step S78 the processor 122 informs that the recording medium 500 has illegal data without performing the writing as in step S76, and ends the processing.
- the notification is, for example, lighting or blinking of the LED 128.
- the PLC 100 determines whether the data recorded in the recording medium 500 can be written according to the combination table stored in the recording medium 500.
- the PLC 100 when the PLC 100 writes user configuration data from the recording medium 500 as shown in steps S74 to S78, the user configuration data and the user configuration data are stored in accordance with the combination table stored in the recording medium 500.
- the suitability of the combination with the firmware already stored in the PLC 100 is determined. That is, it is not necessary for the worker who attends the writing work to have knowledge about the suitability of the combination of the user configuration data and the system firmware and / or add-on firmware. Thereby, the data writing to the PLC 100 can be executed quickly and easily.
- steps S66 to S70 when the PLC 100 writes firmware (system firmware and / or add-on firmware) from the recording medium 500, the firmware and the firmware are already in accordance with the combination table stored in the recording medium 500.
- the suitability of the combination with the user configuration data stored in the PLC 100 is determined. That is, it is not necessary for the worker who attends the writing operation to have knowledge about the suitability of the user configuration data already stored in the PLC 100 and the combination of the system firmware and add-on firmware to be written. Thereby, the data writing to the PLC 100 can be executed quickly and easily.
- the system firmware, add-on firmware, and / or user configuration data in the PLC 100 is about to be written by changing the version or the like without the administrator at the manufacturing site. If the firmware or user configuration data is not properly combined, it is notified that the combination is not appropriate (steps S70 and S78). Thereby, the change can be easily found.
- the writing process shown in FIG. 14 can also be applied to a process using a recording medium other than the recording medium 500 in which data is recorded according to the process of FIG.
- the support apparatus 300 records system firmware, add-on firmware, and user configuration data on the recording medium 500. These constitute the appropriate combinations defined by the combination table 370. Such a combination of system firmware, add-on firmware, and user configuration data is written in the new PLC 100 as it is, for example.
- FIG. 15 is a flowchart of a process for recording data on the recording medium 500, which is executed by the support apparatus 300 according to the fourth embodiment.
- step S56 of the process shown in FIG. 15 the CPU 302 records the system firmware and add-on firmware selected in step S40 and the user configuration data selected in step S46 on the recording medium 500.
- the PLC 100 writes all data (system firmware, add-on firmware, and user configuration data) recorded on the recording medium 500 by the support apparatus 300. These data are data in accordance with combinations defined as appropriate in the combination table 370. Therefore, the worker who is present at the writing work in the PLC 100 does not need to have special knowledge about the combination of these data. Therefore, the operation of writing data to the PLC 100 is quick and easy.
- control system 100 PLC, 122 processor, 124 main memory, 126 nonvolatile memory, 132 input device, 134 connector, 136,316 SD memory card interface, 300 support device, 308 hard disk, 310 keyboard, 312 mouse, 314 monitor 500 recording media.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
- Programmable Controllers (AREA)
Abstract
Description
図1は、4つの実施の形態の制御システムのそれぞれが利用される製造現場の構成の一例を概略的に示す図である。図1を参照して、製造現場において、消費財5が、コンベア4上を矢印A1が示す方向に沿って流れる際に、各消費財5は、製造装置2A,2C,2Eのそれぞれにおいて処理を施される。
各実施の形態に係る制御システムの構成について説明する。各実施の形態では、機械や設備などの制御対象を制御するPLCを制御機器(図1に示された制御機器3A~3F)の典型例として、説明を行う。但し、本発明に係る制御機器は、PLCに限られることなく、各種の制御機器へ適用可能である。
図3は、制御機器の一例であるPLCの機能的な構成の一例を示す図である。PLC100には、システムファームウェア104Aおよびアドオンファームウェア104Bがインストールされている。システムファームウェア104Aは、PLC100の基本機能を提供するソフトウェアである。図3に示されるように、システムファームウェア104Aは、「Basic middleware」および「Basic application」といった、制御機器の基本機能(プログラム実行、通信、センシング等)を実現するためのソフトウェアを含む。また、システムファームウェア104Aは、OS(Operating System)を含む。また、システムファームウェア104Aは、「Bootloader」「FPGA」および「Device driver」といった、制御機器の表示装置やメモリ等の、制御機器に搭載されたハードウェア資源を制御するソフトウェアを含む。
図4は、PLC100のハードウェア構成の一例を示す図である。図4に示されるように、PLC100は、プロセッサ122と、メインメモリ124と、不揮発性メモリ126と、LED(Light Emitting Diode)128と、入力装置132と、コネクタ134と、SD(Secure Data)メモリカード・インタフェース136とを含む。
図5は、支援装置300のハードウェア構成の一例を示す図である。図5に示されるように、支援装置300は、典型的には、汎用のコンピュータで構成される。
以上説明した制御システムでは、PLC100等の制御機器において実行されるプログラムは、当該制御機器のファームウェアを含む。制御機器に置いて、ファームウェアは、大きく分類して、システムファームウェアとアドオンファームウェアとの2つの種類に分類される。PLC100は、記録媒体500を介して、これらのプログラムを書き込む場合もある。制御システムの第1の実施の形態では、支援装置300は、PLC500のために、上記された2種類のファームウェアを記録媒体500に記録する。より具体的には、支援装置300は、上記2種類のファームウェアを、予め定められた組合せで記録媒体500に記録する。以下、第1の実施の形態の制御システムについて説明する。
図6は、制御システムの第1の実施の形態における支援装置300の機能構成の一例を模式的に示す図である。図6に示されるように、支援装置300には、プロジェクトファイル350と、ファームウェアデータベース360と、組合せテーブル370とが格納されている。
図7は、第1の実施の形態の組合せテーブル370に含まれる情報の一例を示す図である。図7に示されるように、組合せテーブル370は、システムファームウェアのバージョンごとに、当該バージョン上で使用可能な(正常に動作する)アドオンファームウェアの種類を指定する情報を含む。ここで指定される種類とは、アドオンファームウェアのタイトルおよびバージョンを識別する。つまり、組合せテーブル370では、タイトルが共通しても、バージョンが異なるアドオンファームウェア同士は、互いに異なる種類のアドオンファームウェアとして識別される。システムファームウェアのバージョンおよびアドオンファームウェアのバージョンは、たとえば、各ファームウェアのプログラムのファイル名によって特定され得る。
ン「V1.0」のシステムファームウェア上では、「Add-on_A」という種類のアドオンファームウェアのバージョン「V1.0」のプログラムが正常に動作することを意味する。
図8は、支援装置300において実行される処理の一例のフローチャートである。当該処理は、支援装置300が、記録媒体500に、ファームウェアデータベース360内のファームウェアを記録するための処理である。当該処理は、CPU302が、所与のプログラム(たとえば、上記したプロジェクトファイル作成用のアプリケーション)を実行することによって、実現される。
第2の実施の形態の制御システムでは、支援装置300は、記録媒体500に、コンフィグレーションデータとともに、上記した組合せテーブルを記録する。以下、制御システムの構成を説明する。
第2の実施の形態の制御システムでは、図6に示された組合せテーブル370は、ユーザコンフィグレーションデータについての組合せを特定する情報を含む。より具体的には、組合せテーブル370は、ユーザコンフィグレーションデータとシステムファームウェアとの組合せを特定する情報、および、ユーザコンフィグレーションデータとアドオンファームウェアとの組合せを特定する情報を含む。
図11は、第2の実施の形態の支援装置300において実行される、記録媒体500へのユーザコンフィグレーションデータの記録のための処理のフローチャートである。
図12は、図11に示されたような処理によってデータを記録された記録媒体500を利用したPLCへのデータの書込処理のフローチャートである。図12の処理は、PLCのプロセッサ122によって実行される。プロセッサ122は、SDメモリカード・インタフェース136に記録媒体500を装着された状態で、図12の処理を実行する。
第3の実施の形態の制御システムでは、支援装置300は、記録媒体500に、システムファームウェアと、アドオンファームウェアと、ユーザコンフィグレーションデータと、組合せテーブルとを記録する。PLC100は、当該記録媒体500を利用して、データの書き込みを実行する。以下、第3の実施の形態の制御システムの構成を説明する。
図13は、第3の実施の形態の支援装置300において記録媒体500に記録するための処理のフローチャートである。図11を参照して、ステップS40で、CPU302は、システムファームウェアおよびアドオンファームウェアの選択を受け付ける。
図14は、記録媒体500を利用する、PLC100へのデータの書込処理のフローチャートである。プロセッサ122は、SDメモリカード・インタフェース136に記録媒体500を装着された状態で、図14の処理を実行する。
第4の実施の形態の支援装置300は、記録媒体500に、システムファームウェア、アドオンファームウェア、および、ユーザコンフィグレーションデータを記録する。これらは、組合せテーブル370によって規定される適切な組合わせを構成する。このような組合せのシステムファームウェア、アドオンファームウェア、および、ユーザコンフィグレーションデータは、たとえば、新規のPLC100にそのまま書き込まれる。
Claims (12)
- 可搬型記録媒体のデータを読み込むための読取装置と、
制御に用いられるデータを記憶する記憶装置と、
前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込むためのプロセッサとを備え、
前記可搬型記録媒体には、さらに、データの種類の組合せを特定する情報である組合せ情報が記録されており、
前記プロセッサは、
前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含む場合には、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込み、
前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含まない場合には、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込まないように構成されている、制御機器。 - 前記記憶装置に記憶されたデータは、前記制御機器の一種類または複数種類のファームェアであり、
前記可搬型記録媒体に記録されたデータは、前記ファームウェアによる制御に用いられる一種類または複数種類の設定データであり、
前記組合せ情報は、前記ファームウェアの種類と当該ファームウェアによる制御に用いられる設定データの種類との組合せを特定する情報である、請求項1に記載の制御機器。 - 前記記憶装置に記憶されたデータは、前記ファームウェアによる制御に用いられる一種類または複数種類の設定データであり、
前記組合せ情報は、ファームウェアの種類と当該ファームウェアによる制御に用いられる設定データの種類との組合せを特定する情報である、請求項2に記載の制御機器。 - 前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含まない場合に、報知動作を実行する報知部をさらに備える、請求項1~請求項3のいずれか1項に記載の制御機器。
- 制御機器と、前記制御機器に書き込まれるデータを可搬型記録媒体に記録するための支援装置とを備える制御システムであって、
前記支援装置は、
可搬型記録媒体に情報を記録するための記録装置と、
前記記録装置の動作を制御するためのコントローラとを含み、
前記コントローラは、前記記録装置に、前記可搬型記録媒体へ、データと、当該データの種類と組み合わされるデータの種類を特定する情報である組合せ情報とを記録させるように構成されており、
前記制御機器は、
前記可搬型記録媒体のデータを読み込むための読取装置と、
前記制御機器の制御に用いられるデータを記憶する記憶装置と、
前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込むためのプロセッサとを含み、
前記プロセッサは、
前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含む場合には、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込み、
前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含まない場合には、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込まないように構成されている、制御システム。 - 前記記憶装置に記憶されたデータは、前記制御機器における動作を制御するための一種類または複数種類のファームウェアであり、
前記可搬型記録媒体に記録されたデータは、前記ファームウェアによる制御に用いられる一種類または複数種類の設定データであり、
前記組合せ情報は、ファームウェアの種類と当該ファームウェアによる制御に用いられる設定データの種類との組合せを特定する情報である、請求項5に記載の制御システム。 - 前記記憶装置に記憶されたデータは、ファームウェアによる制御に用いられる一種類または複数種類の設定データであり、
前記組合せ情報は、ファームウェアの種類と当該ファームウェアによる制御に用いられる設定データの種類との組合せを特定する情報である、請求項6に記載の制御システム。 - 前記制御機器は、前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含まない場合に、報知動作を実行する報知部をさらに含む、請求項5~請求項7のいずれか1項に記載の制御システム。
- 可搬型記録媒体のデータを読み込むための読取装置と、制御に用いられるデータを記憶する記憶装置とを備える制御機器のプロセッサによって実行される、当該制御機器の制御方法であって、
前記可搬型記録媒体には、データと、データの種類の組合せを特定する情報である組合せ情報とが記録されており、
前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含むか否かを判断するステップと、
前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含む場合に、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込むステップとを備える、制御機器の制御方法。 - 前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含まない場合に、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込むことなく報知を実行するステップをさらに備える、請求項9に記載の制御機器の制御方法。
- 制御機器と、前記制御機器に書き込まれるデータを可搬型記録媒体に記録するための支援装置とを備える制御システムの制御方法であって、
前記支援装置は、可搬型記録媒体に情報を記録するための記録装置を含み、
前記制御方法は、前記支援装置が、前記記録装置に、前記可搬型記録媒体へ、データと、当該データの種類と組み合わされるデータの種類を特定する情報である組合せ情報とを記録させるステップを備え、
前記制御機器は、前記可搬型記録媒体のデータを読み込むための読取装置と、前記制御機器の制御に用いられるデータを記憶する記憶装置とを含み、
前記制御方法は、前記制御機器が、前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含むか否かを判断するステップと、
前記制御方法は、前記制御機器が、前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含む場合に、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込むステップとを備える、制御システムの制御方法。 - 前記制御方法は、前記制御機器が、前記可搬型記録媒体に記録されている組合せ情報が、前記記憶装置が記憶するデータの種類と前記可搬型記録媒体に記録されているデータの種類との組合せを含まない場合に、前記可搬型記録媒体に記録されたデータを前記記憶装置に書き込むことなく報知を実行するステップをさらに備える、請求項11に記載の制御システムの制御方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15761341.5A EP3101537A4 (en) | 2014-03-14 | 2015-01-15 | Control device, control system, control method for control device, and control method for control system |
US15/123,204 US10296241B2 (en) | 2014-03-14 | 2015-01-15 | Control device, control system, control method for control device, and control method for control system |
CN201580011591.5A CN106062712A (zh) | 2014-03-14 | 2015-01-15 | 控制设备、控制系统、控制设备的控制方法及控制系统的控制方法 |
JP2016507376A JP6337956B2 (ja) | 2014-03-14 | 2015-01-15 | 制御機器、制御システム、制御機器の制御方法、および、制御システムの制御方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014-052680 | 2014-03-14 | ||
JP2014052680 | 2014-03-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015136965A1 true WO2015136965A1 (ja) | 2015-09-17 |
Family
ID=54071419
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/050879 WO2015136965A1 (ja) | 2014-03-14 | 2015-01-15 | 制御機器、制御システム、制御機器の制御方法、および、制御システムの制御方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10296241B2 (ja) |
EP (1) | EP3101537A4 (ja) |
JP (1) | JP6337956B2 (ja) |
CN (1) | CN106062712A (ja) |
WO (1) | WO2015136965A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019176274A1 (ja) | 2018-03-13 | 2019-09-19 | オムロン株式会社 | コントローラ、ライセンスの管理方法、およびライセンスの管理プログラム |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6661409B2 (ja) * | 2016-03-01 | 2020-03-11 | キヤノン株式会社 | 自動設置システム、情報処理装置、情報処理装置の制御方法、及びプログラム |
DE102016224784A1 (de) * | 2016-12-13 | 2018-06-14 | Robert Bosch Gmbh | Steuervorrichtung zur Steuerung mindestens eines Teils einer industriellen Anlage und Verfahren zur Programmierung und/oder Diagnose der Steuervorrichtung |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003223617A (ja) * | 2002-01-29 | 2003-08-08 | Sony Corp | 情報処理装置および方法、記録媒体、記憶媒体、並びにプログラム |
JP2012212415A (ja) * | 2011-03-18 | 2012-11-01 | Hitachi Kokusai Electric Inc | 無線基地局装置 |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6412082B1 (en) | 1997-12-17 | 2002-06-25 | Sony Corporation | Method and apparatus for selecting computer programs based on an error detection mechanism |
JP4029448B2 (ja) * | 1997-12-17 | 2008-01-09 | ソニー株式会社 | 情報処理装置および情報処理方法 |
JP2003345617A (ja) | 2002-05-23 | 2003-12-05 | Nec Corp | 情報処理装置、情報処理方法、icカード、及びプログラム |
JP4462443B2 (ja) | 2005-02-28 | 2010-05-12 | オムロン株式会社 | パラメータ設定装置 |
JP3925557B2 (ja) * | 2005-02-28 | 2007-06-06 | オムロン株式会社 | パラメータ設定装置 |
JP4390079B2 (ja) | 2005-09-27 | 2009-12-24 | オムロン株式会社 | 制御システム |
JP4952978B2 (ja) * | 2006-02-28 | 2012-06-13 | ブラザー工業株式会社 | インストーラを作成するためのプログラム,該プログラムを記憶する記憶媒体,情報処理装置 |
JP2010055279A (ja) | 2008-08-27 | 2010-03-11 | Fuji Xerox Co Ltd | 更新判定装置、画像処理装置、及びプログラム |
US8892699B2 (en) * | 2008-12-31 | 2014-11-18 | Schneider Electric USA, Inc. | Automatic firmware updates for intelligent electronic devices |
JP5428721B2 (ja) * | 2009-10-02 | 2014-02-26 | 富士通株式会社 | 管理システム,管理装置,管理方法および管理プログラム |
CN102043614A (zh) | 2009-10-12 | 2011-05-04 | 无锡华润矽科微电子有限公司 | 一种二次开发系统及二次开发方法 |
JP2012168879A (ja) * | 2011-02-16 | 2012-09-06 | Nec Access Technica Ltd | 情報処理装置 |
US8978024B2 (en) * | 2012-08-02 | 2015-03-10 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Federated system automatic update communication to enable selective update of critical firmware elements |
US9027014B2 (en) * | 2013-01-17 | 2015-05-05 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Updating firmware compatibility data |
US9116775B2 (en) * | 2013-05-15 | 2015-08-25 | Dell Products L.P. | Relationship-based dynamic firmware management system |
-
2015
- 2015-01-15 CN CN201580011591.5A patent/CN106062712A/zh active Pending
- 2015-01-15 WO PCT/JP2015/050879 patent/WO2015136965A1/ja active Application Filing
- 2015-01-15 US US15/123,204 patent/US10296241B2/en active Active
- 2015-01-15 JP JP2016507376A patent/JP6337956B2/ja active Active
- 2015-01-15 EP EP15761341.5A patent/EP3101537A4/en not_active Withdrawn
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003223617A (ja) * | 2002-01-29 | 2003-08-08 | Sony Corp | 情報処理装置および方法、記録媒体、記憶媒体、並びにプログラム |
JP2012212415A (ja) * | 2011-03-18 | 2012-11-01 | Hitachi Kokusai Electric Inc | 無線基地局装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3101537A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019176274A1 (ja) | 2018-03-13 | 2019-09-19 | オムロン株式会社 | コントローラ、ライセンスの管理方法、およびライセンスの管理プログラム |
Also Published As
Publication number | Publication date |
---|---|
US20170212699A1 (en) | 2017-07-27 |
JP6337956B2 (ja) | 2018-06-06 |
EP3101537A4 (en) | 2017-03-22 |
CN106062712A (zh) | 2016-10-26 |
EP3101537A1 (en) | 2016-12-07 |
US10296241B2 (en) | 2019-05-21 |
JPWO2015136965A1 (ja) | 2017-04-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4462449B2 (ja) | 制御システム設定装置 | |
US8914794B2 (en) | Multiple deployment of applications with multiple configurations in an industrial automation environment | |
JP5295464B1 (ja) | システム構築支援ツール及びシステム | |
WO2015136959A1 (ja) | 制御システム、方法、プログラムおよび情報処理装置 | |
JP2005327263A (ja) | 制御システム設定装置 | |
JP6337956B2 (ja) | 制御機器、制御システム、制御機器の制御方法、および、制御システムの制御方法 | |
JP2009217707A (ja) | Fa機器並びにファイルアクセスシステム | |
US11402819B2 (en) | Screen creation device and screen creation system | |
CN103477291A (zh) | 参数设定装置及参数设定系统 | |
JP6442131B2 (ja) | 制御システムおよび制御装置 | |
JP7063009B2 (ja) | 表示装置、画面生成方法、および画面生成プログラム | |
JP5444166B2 (ja) | 設備管理装置、画面表示方法、およびプログラム | |
EP2985662A1 (en) | Automatic creation of hardware configuration in a distributed control system | |
CN108351633B (zh) | 食品工业中的机器的操作模块 | |
EP3104236B1 (en) | Control device, control system, support apparatus, and control-device maintenance management method | |
JP6169306B2 (ja) | 制御システム及びプログラマブルロジックコントローラ | |
JP3580347B2 (ja) | データ管理方法、データ管理装置及びそれらの記録媒体 | |
EP2908194A1 (en) | Method and device for configuring hardware devices in an industrial automation system | |
JP6785916B1 (ja) | 設定実行装置、設定実行方法および設定実行プログラム | |
CN103503494A (zh) | 修改移动通信设备内容的系统和方法 | |
CN116343896B (zh) | 板卡老化测试的方法、系统、设备及存储介质 | |
WO2022190427A1 (ja) | 開発支援装置、開発支援方法、及び、開発支援プログラム | |
WO2021065033A1 (ja) | プログラム開発装置およびプログラム開発装置を実現するためのプログラム | |
KR20060061001A (ko) | 단일씨피유를 이용한 씨앤씨시스템 | |
JP2023027509A (ja) | サポート装置、サポートプログラムおよび制御システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15761341 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016507376 Country of ref document: JP Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 2015761341 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15123204 Country of ref document: US Ref document number: 2015761341 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |