WO2015136966A1 - 制御機器、制御システム、支援装置、および、制御機器のメンテナンスの管理方法 - Google Patents
制御機器、制御システム、支援装置、および、制御機器のメンテナンスの管理方法 Download PDFInfo
- Publication number
- WO2015136966A1 WO2015136966A1 PCT/JP2015/050880 JP2015050880W WO2015136966A1 WO 2015136966 A1 WO2015136966 A1 WO 2015136966A1 JP 2015050880 W JP2015050880 W JP 2015050880W WO 2015136966 A1 WO2015136966 A1 WO 2015136966A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- control device
- firmware
- plc
- maintenance operation
- writing
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0286—Modifications to the monitored process, e.g. stopping operation or adapting control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25112—Using firmware stored in processor
Definitions
- the present invention relates to the maintenance operation of control equipment for controlling a factory automation (FA) system such as a production system.
- FA factory automation
- a control device such as a PLC (programmable logic controller) which controls the FA system installed in a production site of a production factory controls the system by executing operations based on a control program.
- a control device an already installed program can be updated by installing an appropriate program.
- functions may be added by installing an appropriate program.
- Patent Document 1 proposes a downloading method which enables downloading of only a part of a system program.
- Patent Document 2 discloses a technique for recording information on an abnormality generated in the control device in the control device.
- Patent Document 2 in the control device, if an abnormality occurs, information of the abnormality is recorded. However, if an abnormality did not occur, information representing the state of the control device was not recorded. Therefore, it has been difficult in the past to verify the contents of maintenance work performed without occurrence of abnormality in the control device as described above. From this, in order to verify the state of the control device, it is necessary to analyze the control device in detail.
- the worker at the site concerned performs maintenance of the control device such as downloading of a program without obtaining the approval of the supervisor at the site concerned. May do.
- the supervisor needs to verify the state of the control device by performing a detailed analysis of the control device as described above, which is cumbersome.
- production plants of one company may exist in many countries. From this, the production plant may be located in a country different from the country in which the substantial supervisor of the production plant resides. In such a case, in order to analyze the control device, the above-mentioned substantial supervisor needs to go to the country where the production plant is located, which is not convenient.
- the present invention has been made in view of such circumstances, and an object thereof is to make it possible to easily confirm the history of maintenance in a control device.
- a control device for controlling a production system.
- the control device comprises a storage device and a processor configured to write the firmware of the control device recorded on the portable recording medium into the storage device.
- the processor is configured to write the information identifying the writing of the firmware to the storage device.
- the information specifying the writing of the firmware includes information specifying the name of the firmware written in the storage device.
- the information specifying the writing of the firmware includes information specifying a portable recording medium.
- a control system includes a control device for controlling a production system and a support device capable of communicating with the control device.
- the control device includes a first storage device and a first interface for communicating with the support device.
- the support device includes a second storage device, a second interface for communicating with the control device, and a control device recorded in the first storage device in the second storage device via the second interface.
- a controller configured to write firmware.
- the controller is further configured to write the information identifying the writing of the firmware to the first storage device.
- the controller further writes, to the second storage device, information specifying the writing of the firmware.
- the assistance device further includes display means configured to display information identifying the writing of the firmware in the first storage device and information identifying the writing of the firmware in the second storage device.
- control device further includes a processor configured to write the firmware of the control device, which is recorded on a portable recording medium that is removable from the control device, into the first storage device.
- the processor is configured to write, to the first storage device, information identifying the writing of the firmware, recorded on the portable storage medium, to the first storage device.
- the display means is further configured to display information specifying writing of the firmware recorded in the portable recording medium to the first storage device.
- a support device in communication with a control device for controlling a production system.
- the support device includes a storage device, an interface for communicating with the control device, and a controller configured to write firmware of the control device recorded in the storage device to the control device via the interface.
- the controller is configured to write information specifying the writing of the firmware to the control device in the control device.
- the information specifying the writing of the firmware to the control device includes information specifying the control device.
- a method of managing maintenance of a control device which is executed by a computer of the control device for controlling a production system.
- the management method includes the steps of writing the firmware of the control device recorded in the portable recording medium into the storage device of the control device, and writing the information specifying the writing of the firmware in the storage device of the control device.
- the information specifying the writing of the firmware includes information specifying a portable recording medium.
- a method of managing the writing of firmware to a control device is provided, which is executed in a support device capable of communicating with a control device for controlling a production system.
- the management method includes the steps of writing the firmware of the control device into the control device and writing information specifying the writing of the firmware of the control device into the control device.
- the information specifying the writing of the firmware of the control device includes information specifying the control device.
- a control device for controlling a production system.
- the control device comprises a storage device and a processor configured to delete firmware of the control device from the storage device.
- the processor is configured to write to the storage device information identifying the deletion of the firmware.
- control device information specifying at least one of writing and deletion of firmware is recorded.
- at least one of the writing and deleting of the firmware is recorded in the control device. Therefore, by referring to the history, the history of maintenance of firmware in the control device can be easily confirmed.
- the substantial supervisor of the manufacturing site remotely refers to and confirms the history of maintenance of the firmware of the control device installed at the manufacturing site. can do.
- FIG. 1 schematically shows an example of a configuration of a control system according to an embodiment of the present invention. It is a figure showing roughly an example of the hardware constitutions of a support device. It is a figure which shows an example of the hardware constitutions of PLC. It is a figure for demonstrating the outline
- FIG. 1 schematically shows an example of a configuration of a control system according to an embodiment of the present invention. It is a figure showing roughly an example of the hardware constitutions of a support device. It is a figure which shows an example of the hardware constitutions of PLC. It is a figure for demonstrating the outline
- FIG. 6 is a view schematically showing an example of a history of maintenance operations recorded on a recording medium. It is a flow chart of an example of processing for maintenance operation of PLC by support device. It is a flow chart of other examples of processing for maintenance operation of PLC by support device. It is a flow chart of an example of processing of maintenance operation which PLC performs using a recording medium. It is a figure which shows an example of the display where the log
- FIG. 17 is a diagram showing an example of the display of the history of the maintenance operation when the recording medium of the ID “2B63-3AA4” is attached.
- FIG. 17 is a diagram showing an example of the display of the history of the maintenance operation when the recording medium of the ID “3C87-2EB5” is attached.
- FIG. 1 is a diagram schematically showing an example of the configuration of a control system according to an embodiment of the present invention.
- the control system includes a PLC 100 and a support device 300.
- the PLC 100 is an example of a control device that controls the FA system.
- the PLC 100 controls operations of, for example, a relay and a servomotor driver for driving a motor in the FA system.
- the support device 300 is an example of an information processing device capable of communicating with the PLC 100.
- the support device 300 is configured of, for example, a general-purpose computer. Setting, programming, monitoring, debugging, etc. of various parameters for programs that can be executed in the PLC 100 are performed.
- the support device 300 executes the maintenance operation of the PLC 100.
- the PLC 100 includes an arithmetic unit (processor 122 in FIG. 3) as described later, and the arithmetic unit executes control of the FA system by executing a program.
- the maintenance operation of the PLC 100 includes, for example, writing data to be used for control of the FA system to the PLC 100.
- An example of the maintenance operation is that the assisting device 300 writes data to the PLC 100, as indicated by an arrow R1 in FIG.
- the PLC 100 can execute the maintenance operation of the PLC 100 by writing the data recorded in the recording medium 500 into the PLC 100.
- the data recorded on the recording medium 500 may be written to the recording medium 500 by the support device 300 as shown by the arrow R2 in FIG. 1 or may be written to the recording medium 500 by another device.
- the PLC 100 may execute the maintenance operation of the PLC 100 by being instructed by the support device 300. More specifically, for example, the support device 300 instructs the PLC 100 to write the data recorded in the support device 300. In response to this, the PLC 100 writes the data recorded in the support device 300.
- the support device 300 may also record information specifying the maintenance operation in the support device 300 as well.
- the information specifying the maintenance operation is written by the PLC 100 itself. More specifically, when the PLC 100 executes the maintenance operation by writing the data recorded in the recording medium 500 into the PLC 100, the PLC 100 further writes in the PLC 100 information specifying the maintenance operation. At this time, the PLC 100 may record information specifying the maintenance operation on the recording medium 500.
- FIG. 2 is a diagram schematically showing an example of the hardware configuration of the support device 300.
- the support device 300 includes a central processing unit (CPU) 302, a read only memory (ROM) 304, a random access memory (RAM) 306, and a hard disk drive (HDD) 308.
- the CPU 302 executes various programs including an OS (Operating System).
- the ROM 304 stores a BIOS (Basic Input / Output System) and various data.
- the RAM 306 provides a work area for storing data necessary for execution of the program in the CPU 302.
- the HDD 308 stores programs and the like executed by the CPU 302 in a non-volatile manner.
- the CPU 302 and the RAM 306 constitute an example of a controller.
- the hard disk 308 may store data (program data and / or batch file data) transmitted to the PLC 100 and a history of maintenance operations performed on the PLC 100.
- a program storage unit 330 indicates an area for storing a program of an application for performing a maintenance operation.
- the data storage unit 331 indicates an area for storing data to be transmitted to the PLC 100.
- the maintenance history storage unit 332 indicates an area for storing the history of the maintenance operation.
- the programs and data stored in the hard disk 308 can be recorded on a recording medium that can be attached to and detached from the support device 300, and can be distributed independently of the support device 300 itself.
- the support device 300 also includes a keyboard 310 and a mouse 312 for receiving operations from the user, a monitor 314 for presenting information to the user, and SD (Secure Digital). And a memory card interface 316.
- SD Secure Digital
- an SD memory card is employed as an example of the recording medium 500.
- the CPU 302 reads the data recorded in the recording medium 500 via the SD memory card interface 316 and records the data in the recording medium 500.
- the support device 300 further includes a communication interface (IF) 318 for communicating with the PLC 100 or the like.
- IF communication interface
- FIG. 3 is a diagram showing an example of the hardware configuration of the PLC 100.
- the PLC 100 includes a processor 122, a main memory 124, a non-volatile memory 126, an LED (Light Emitting Diode) 128, an input device 132, a connector 134, and an SD memory card interface 136. including.
- the processor 122 controls the operation of the PLC 100 by executing a program stored in the non-volatile memory 126 or the like.
- the main memory 124 can be used as a work area of the processor 122.
- the non-volatile memory 126 stores various data such as a program.
- the LED 128 is an example of a notification unit, and the lighting operation is controlled by the processor 122.
- Input device 132 receives an input of information from the outside, and is formed of, for example, a button or the like.
- the connector 134 is provided to connect to an external device including a recording medium such as a USB (Universal Serial Bus) memory.
- Processor 122 may communicate with external devices via connector 134.
- the SD memory card interface 136 is used to read data recorded in an SD memory card, which is an example of the recording medium 500. The processor 122 reads the data recorded on the recording medium 500 via the SD memory card interface 136.
- FIG. 4 is a diagram for describing an outline of an example of the maintenance operation of PLC 100 in the control system of the present embodiment.
- the left side of FIG. 4 shows the state of the PLC 100 before the maintenance operation.
- the right side of FIG. 4 shows the state of the PLC 100 after the maintenance operation.
- System firmware is software that provides the basic functions of the PLC 100.
- the system firmware is, for example, software for realizing a basic function (program execution, communication, sensing, etc.) of PLC 100, an OS (Operating System), or a hardware resource mounted on PLC 100 (for example, a display device or (Including memory control software).
- the additional function is a function unique to the manufacturing apparatus on which the PLC 100 is mounted.
- One example is a temperature control function or a special communication function.
- the additional function is a function that is different from the basic function of the PLC 100 to increase the competitiveness of the PLC 100, and that is desired to increase the value of the control device. That is, the application function may differ for each PLC 100 and for each manufacturing apparatus on which the control device is mounted.
- the application function (additional function) is also referred to as “add-on firmware” and is realized by a type of firmware of the PLC 100.
- System firmware 150 and additional function A 170 are stored, for example, in non-volatile memory 126.
- the PLC 100 also includes a management memory 160 for storing information for specifying a maintenance operation in the PLC 100.
- Management memory 160 is formed of, for example, non-volatile memory 126.
- the processor 122 executes the additional function A170 to realize a specific function.
- the support device 300 writes the additional function B (an application program for realizing the function B) in the non-volatile memory 126 of the PLC 100 as an example of the maintenance operation of the PLC 100.
- the state of the PLC 100 shifts to the state shown on the right side of FIG.
- the PLC 100 further includes an additional function B171.
- PLC100 itself can also perform the maintenance operation of the said PLC100. More specifically, the processor 122 of the PLC 100 can write the application program of the additional function B recorded in the recording medium 500 into the non-volatile memory 126. Also, the processor 122 writes the data recorded in the data storage unit 331 of the support device 300 in the non-volatile memory 126 in response to an instruction from the support device 300.
- FIG. 5 is a diagram schematically showing an example of the history of the maintenance operation recorded in the non-volatile memory 126 of the PLC 100. As shown in FIG.
- the history of the maintenance operation includes the date and time when the maintenance operation was performed, information (“device” in FIG. 5) for specifying the device that provided the data of the maintenance operation, and the contents of the maintenance operation And.
- the content is, for example, the name of a downloaded program. Further, in the history, a number for specifying each maintenance operation is assigned.
- the maintenance operation of the number “1” in FIG. 5 is started (or completed) at 9:10:15 on Jan. 5, 2014, V2 of the FW (firmware) program (a type of system firmware).
- This is a version upgrade to 01, which means that data was provided from the computer (PC) specified by the ID “AAA”.
- the ID of the PC is an example of information for specifying the support device 300.
- the computer with the ID “AAA” means the support device 300. That is, the maintenance operation of the number “1” means that the support device 300 has performed the maintenance operation.
- the processing content of “version upgrade” is specified based on the content of the data recorded in the non-volatile memory 126 at the start of the maintenance operation.
- the CPU 302 is a program having the same file name as the file name of the program written in the maintenance operation in the nonvolatile memory 126 of the PLC 100 at the start of the maintenance operation, and is a program of an older version than the program If the content is written, the content of the maintenance operation is identified as "version upgrade".
- the maintenance operation of the number “3" in Fig. 5 was started (or completed) on January 9, 2014 at 10:01:01, and the version V 1.00 DB (database) connection function (program) Means delete.
- the value of “device” of the maintenance operation of the number “3” is “PC: BBB”. This means that the computer specified by the ID "BBB” has executed the deletion.
- Program deletion may include not only erasing program data from the non-volatile memory 126 but also making the processor data 122 unreadable by rewriting the directory or the like.
- FIG. 6 is a diagram schematically showing an example of the history of the maintenance operation stored in the maintenance history storage unit 332 of the support device 300. As shown in FIG.
- the history of the maintenance operation includes the date and time when the maintenance operation was performed, information (“PLC” in FIG. 6) for specifying the PLC targeted for the maintenance operation, and the contents of the maintenance operation And. Further, in the history, a number for specifying each maintenance operation is assigned.
- the maintenance operation of the number “3” in FIG. 6 is started (or completed) at 11:42:53 on Jan. 7, 2014, for the PLC specified by the serial number “45678”, version V1. It means that it is the addition of (program) of DB (database) connection function of .00.
- the serial number is one specific example of the ID of the PLC 100.
- FIG. 7 is a diagram schematically showing an example of the history of the maintenance operation recorded on the recording medium 500. As shown in FIG.
- the history of the maintenance operation includes the date and time when the maintenance operation was performed, information (“PLC” in FIG. 7) for specifying the PLC targeted for the maintenance operation, and the contents of the maintenance operation And. Further, in the history, a number for specifying each maintenance operation is assigned.
- the maintenance operation of the number “1” in FIG. 7 is started (or completed) at 14:51:16 on January 8, 2014, and is version V1 in the PLC specified by the serial number “56789”. It means that it is the addition of (the program of) the robot function of .01.
- FIG. 8 is a flowchart of an example of processing for maintenance operation of the PLC 100 by the support device 300.
- CPU 302 establishes communication with PLC 100 in step SA10. More specifically, for example, a worker inputs an instruction for the maintenance operation of PLC 100 to support device 300. In response to this, the CPU 302 requests the PLC 100 to establish communication. Communication between the support device 300 and the PLC 100 is established by the processor 122 of the PLC 100 responding to the request. Then, control proceeds to step SA12.
- step SA12 the CPU 302 writes the data designated to be written to the PLC 100 in the nonvolatile memory 126 of the PLC 100. Then, control proceeds to step SA14.
- the information specifying the data to be written is input to the support device 300 by the worker, for example. More specifically, the program storage unit 330 of the HDD 308 stores information that associates a function with a program for realizing the function. Then, the worker specifies the function. Thus, the CPU 302 identifies a program associated with the designated function as data to be written to the PLC 100.
- step SA14 the CPU 302 determines whether the writing of data to the non-volatile memory 126 has ended normally.
- the control proceeds to step SA18 (YES in step SA14).
- step SA16 NO in step SA14.
- step SA16 the CPU 302 notifies that the maintenance operation has abnormally ended, and ends the processing of FIG.
- the notification is realized, for example, by displaying a message indicating that on the monitor 314.
- the CPU 302 writes the following three pieces of information (A1 to A3) in the maintenance history storage unit 332.
- PLC ID is an ID of PLC 100 (an example of information for specifying PLC 100), and corresponds to “PLC” in FIG.
- the CPU 302 reads the ID of the PLC 100 from the non-volatile memory 126 or the like of the PLC 100.
- step SA20 the CPU 302 writes the following three pieces of information (B1 to B3) in the management memory 160 of the PLC 100, and ends the processing of FIG.
- FIG. 9 is a flowchart of another example of the processing for the maintenance operation of the PLC 100 by the support device 300.
- the process executed by the CPU 302 of the support device 300 is shown on the left, and the process executed by the processor 122 of the PLC 100 is shown on the right.
- communication is established between the support device 300 and the PLC 100 (steps S10 and S30). More specifically, for example, a worker inputs an instruction for the maintenance operation of PLC 100 to support device 300. In response to this, the CPU 302 requests the PLC 100 to establish communication. Communication between the support device 300 and the PLC 100 is established by the processor 122 of the PLC 100 responding to the request.
- step S12 the CPU 302 transmits the maintenance information to the PLC 100 and instructs the PLC 100 to write the maintenance information.
- the maintenance information is, for example, data designated to be written to the PLC 100 in the support device 300.
- the data is specified, for example, in the same manner as specified in step SA12.
- step S32 the processor 122 receives the maintenance information. Then, control proceeds to step S34.
- step S34 the processor 122 writes the maintenance information received in step S32 in the non-volatile memory 126. Then, control proceeds to step S36.
- step S36 the processor 122 notifies the support device 300 of the result of the data writing in step S34.
- the notified result is, for example, that the writing of the data ended normally or that the writing of the data ended abnormally.
- step S14 the CPU 302 determines whether the result notified from the PLC 100 indicates that the data writing has ended normally. Then, if the CPU 302 determines that the result indicates that the processing has ended normally, the control proceeds to step S18 (YES in step S14). On the other hand, when the CPU 302 determines that the result indicates abnormal termination, the control proceeds to step S16 (NO in step S14).
- step S16 the CPU 302 notifies that the maintenance operation has abnormally ended, and ends the process of FIG.
- the notification is realized, for example, by displaying a message indicating that on the monitor 314.
- step S18 the CPU 302 writes the following three pieces of information (A1 to A3) in the maintenance history storage unit 332.
- step S18 Execution content A2) Date and time A3) PLC ID
- the information (A1 to A3) written in step S18 is the same as the information (A1 to A3) written in step SA18 (see FIG. 8).
- step S20 the CPU 302 instructs the PLC 100 to write the next three pieces of information (B1 to B3) in the management memory 160, and ends the process of FIG.
- step S20 Execution content B2) Date and time B3) ID of support device
- the information (B1 to B3) instructed to be written in step S20 is the same as the information (B1 to B3) written to the management memory 160 by the CPU 302 in step SA20 (see FIG. 8).
- step S38 the processor 122 determines whether the instruction has been received.
- the processor 122 waits until determining that the instruction has been received (NO in step S38). Then, if processor 122 determines that the instruction has been received, control proceeds to step S40 (YES in step S38).
- step S38 the processor 122 writes the information (B1 to B3) in the management memory 160 according to the instruction from the support device 300, and ends the process of FIG.
- FIG. 10 is a flowchart of an example of processing of a maintenance operation performed by the PLC 100 writing data stored in the recording medium 500 into the non-volatile memory 126.
- the process of FIG. 10 is started, for example, by the worker operating the start button (an example of the input device 132) of the PLC 100.
- step S50 processor 122 determines whether an SD memory card (recording medium 500) is attached to SD memory card interface 136 or not. Then, if processor 122 determines that it is attached, control proceeds to step S 54 (YES in step S 50), and if it is determined that it is not attached, control proceeds to step S 52 (NO in step S 50).
- step S52 the processor 122 reports an error indicating that the recording medium 500 is not loaded, and returns the control to step S50.
- An example of the notification is that the processor 122 turns on the LED 128.
- step S54 the processor 122 executes a maintenance operation. More specifically, the maintenance information recorded on the recording medium 500 is written to the non-volatile memory 126.
- the maintenance information is, for example, data of system firmware and additional functions recorded to be written to the PLC 100 in the recording medium 500.
- step S56 the processor 122 determines whether the maintenance operation in step S54 has ended normally.
- the processor 122 determines that the maintenance operation has ended normally, for example, when the writing of the data in step S54 has ended normally.
- the processor 122 also determines that the maintenance operation has abnormally ended when the writing of the data in step S 54 ends abnormally. Then, if the processor 122 determines that the processing has ended normally, the control proceeds to step S60 (YES in step S56), and if it is determined that the processing ends abnormally, the control proceeds to step S58 (NO in step S56).
- step S58 the processor 122 reports an error indicating that the maintenance operation has abnormally ended, and ends the processing of FIG.
- An example of the notification is that the processor 122 blinks the LED 128.
- step S60 the processor 122 writes the following three pieces of information (C1 to C3) on the recording medium 500 (SD memory card).
- step S62 the processor 122 writes the following three pieces of information (D1 to D3) in the management memory 160.
- D1) Execution content D2) Date and time D3) ID of SD memory card This adds information about one maintenance operation in the history as shown in FIG. "D1) Execution content” corresponds to the “content” of FIG. The "D2) date and time” corresponds to the "date and time” in FIG. “D3) ID of SD memory card” is an ID of the recording medium 500 (an example of information for specifying the recording medium 500), and corresponds to the “device” of FIG.
- the processor 122 reads the ID of the recording medium from the recording medium 500.
- the processor 122 ends the process of FIG. ⁇ Display of history of maintenance operation (1)>
- the CPU 302 can display the history of the maintenance operation (see FIG. 6) stored in the maintenance history storage unit 332 on the monitor 314.
- the CPU 302 can display the history of the maintenance operation (see FIG. 5) stored in the management memory 160 on the monitor 314.
- FIG. 11 is a diagram showing an example of a display in which the history of the maintenance operation in the support apparatus 300 and the history of the maintenance operation in the PLC 100 are combined.
- the history of the maintenance operation illustrated in FIG. 11 includes “date and time”, “device”, “PLC”, and “content”. “Date and time” in FIG. 11 corresponds to “date and time” in FIGS. 5 and 6.
- the “device” of FIG. 11 corresponds to the “device” of FIG.
- the value of "device” in FIG. 11 is "PC".
- PLC in FIG. 11 corresponds to “PLC” in FIG.
- the value of “PLC” in FIG. 11 is the ID of the PLC 100.
- a number is assigned to each maintenance operation.
- the maintenance operation of the numbers “1” to “3” in FIG. 11 corresponds to the maintenance operation of the numbers “1” to “3” in FIG.
- the maintenance operations of the numbers “4” and “5” in FIG. 11 correspond to the maintenance operations of the numbers “2” and “3” in FIG.
- the maintenance operation of the number “1” in FIG. 5 overlaps with the maintenance operation of the number “1” in FIG.
- the “overlap” means, for example, that the maintenance content, the date and time, and the ID of the PLC 100 subjected to the maintenance operation are common.
- the maintenance operation of the number "1" of FIG. 5 and the maintenance operation of the number "1" of FIG. 6 are one maintenance operation (number "1" of FIG. 11). It is shown as.
- the CPU 302 can process the history displayed as shown in FIG. 11 in a predetermined correspondence. For example, the CPU 302 can extract only the information on the maintenance operation for the PLC 100 of a specific serial number from the history of FIG.
- the CPU 302 can load the history of the maintenance operation stored in the management memory 160 of the PLC 100 into the HDD 308. Further, when the recording medium 500 is attached to the SD memory card interface 316, the CPU 302 fetches the history of the maintenance operation stored in the recording medium 500 from the history stored in the maintenance history storage unit 332 and the PLC 100. It can be displayed in combination with the history.
- FIG. 12 is a diagram showing an example of the display of the history of the maintenance operation when the recording medium 500 of the ID “2B63-3AA4” is attached.
- the history of FIG. 12 includes values of items (“date and time”, “device”, “PLC” and “content”) similar to the history of FIG.
- the maintenance operation of the numbers “1” to “3” in FIG. 12 corresponds to the maintenance operation of the numbers “1” to “3” in FIG.
- the maintenance operation of the number “4” in FIG. 12 corresponds to the information of the maintenance operation stored only in the recording medium 500.
- the maintenance operation of the number "5" of FIG. 12 corresponds to the maintenance operation of the number "4" of FIG.
- the maintenance operation of the number "6" of FIG. 12 corresponds to the maintenance operation of the number "5" of FIG.
- the CPU 302 can load the history of the maintenance operation stored in the management memory 160 of the PLC 100 into the HDD 308.
- the CPU 302 can also load the history of the maintenance operation stored in the recording medium 500 (ID “2B63-3AA4”) into the HDD 308.
- the CPU 302 stores the history of the maintenance operation stored in the other storage medium 500 (ID "3C87-2EB5"), the maintenance history storage. It can be displayed in combination with the history stored in the unit 332 and the history acquired from the PLC 100 and the recording medium 500.
- FIG. 13 is a diagram showing an example of the display of the history of the maintenance operation when the recording medium 500 of the ID “3C87-2EB5” is attached.
- the history of FIG. 13 includes values of items (“date and time”, “device”, “PLC” and “content”) similar to the history of FIG.
- the maintenance operation of the numbers “1” to “2” and “4” to “6” in FIG. 13 corresponds to the maintenance operation of the numbers “1” to “2” and “3” to “5” in FIG.
- the maintenance operation of the number “3” in FIG. 13 corresponds to the information of the maintenance operation stored only in the recording medium 500 (ID “3C87-2EB5”).
- the maintenance operation of the number "7" of FIG. 13 corresponds to the maintenance operation of the number "5" of FIG.
- the CPU 302 duplicates the history of the maintenance operation stored in the recording medium 500 and the history stored in the maintenance history storage unit 332 or the history already fetched from the PLC 100 or the recording medium 500. In this case, only one of the overlapping parts can be displayed.
- the history of the maintenance operation in the PLC 100 can be recorded in the PLC 100. Thereby, in the support device 300, the history of the maintenance operation of the PLC 100 can be verified.
- the history can also include a device (support device 300 or recording medium 500) that has recorded data written to the PLC 100 in each maintenance operation. This makes it possible to identify which device has been involved in the execution of which maintenance operation.
- the history can also include information of the user who has performed the maintenance operation. This makes it possible to verify who performed the maintenance operation.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- Programmable Controllers (AREA)
- Testing And Monitoring For Control Systems (AREA)
- Stored Programmes (AREA)
Abstract
Description
図1は、本発明の一実施の形態である制御システムの構成の一例を概略的に示す図である。図1に示されるように、制御システムは、PLC100と、支援装置300とを含む。PLC100は、FAシステムの制御を司る制御機器の一例である。PLC100は、FAシステムにおいて、たとえば、リレー、および、モータを駆動するサーボモータドライバなどの動作を制御する。支援装置300は、PLC100と通信可能な情報処理装置の一例である。支援装置300は、たとえば汎用のコンピュータによって構成される。PLC100において実行され得るプログラムについての、各種パラメータの設定、プログラミング、モニタリング、デバッグなどを行なう。
図2は、支援装置300のハードウェア構成の一例を概略的に示す図である。図2に示されるように、支援装置300は、CPU(Central Processing Unit)302と、ROM(Read Only Memory)304と、RAM(Random Access Memory)306と、ハードディスクドライブ(HDD)308とを含む。CPU302は、OS(Operating System)を含む各種プログラムを実行する。ROM304は、BIOS(Basic Input/Output System)や各種データを格納する。RAM306は、CPU302でのプログラムの実行に必要なデータを格納するための作業領域を提供する。HDD308は、CPU302で実行されるプログラムなどを不揮発的に格納する。制御システムでは、CPU302とRAM306とによって、コントローラの一例が構成される。
メモリカードインタフェース316とを含む。本実施の形態では、記録媒体500の一例としてSDメモリカードが採用される。CPU302は、SDメモリカードインタフェース316を介して、記録媒体500に記録されたデータを読み込み、また、記録媒体500にデータを記録する。支援装置300は、さらに、PLC100などと通信するための通信インタフェース(IF)318を含む。
図3は、PLC100のハードウェア構成の一例を示す図である。図3に示されるように、PLC100は、プロセッサ122と、メインメモリ124と、不揮発性メモリ126と、LED(Light Emitting Diode)128と、入力装置132と、コネクタ134と、SDメモリカードインタフェース136とを含む。
図4は、本実施の形態の制御システムにおけるPLC100のメンテナンス動作の一例の概要を説明するための図である。図4の左側には、メンテナンス動作前のPLC100の状態が示されている。図4の右側には、メンテナンス動作後のPLC100の状態が示されている。
本実施の形態の制御システムでは、PLC100は、当該PLC100のメンテナンス動作の履歴(メンテナンス動作履歴)を記憶する。図5は、PLC100の不揮発性メモリ126に記録されるメンテナンス動作の履歴の一例を模式的に示す図である。
本実施の形態の制御システムでは、支援装置300は、メンテナンス動作を特定する情報を、メンテナンス動作履歴として記憶する。図6は、支援装置300のメンテナンス履歴記憶部332に記憶されるメンテナンス動作の履歴の一例を模式的に示す図である。
本実施の形態の制御システムでは、PLC100は、記録媒体500に記録されたデータを不揮発性メモリ126に書き込むことによってメンテナンス動作を実行すると、当該記録媒体500に、当該メンテナンス動作を特定する情報を書き込む。図7は、記録媒体500に記録されるメンテナンス動作の履歴の一例を模式的に示す図である。
図8は、支援装置300によるPLC100のメンテナンス動作のための処理の一例のフローチャートである。
A2)日時
A3)PLCのID
これにより、図6に示されたような履歴において、1つのメンテナンス動作についての情報が追加される。「A1)実行内容」は、図6の「内容」に対応する。「A2)日時」は、図6の「日時」に対応する。「A3)PLCのID」は、PLC100のID(PLC100を特定する情報の一例)であり、図6の「PLC」に対応する。CPU302は、PLC100の不揮発性メモリ126等から、PLC100のIDを読み込む。
ステップSA20で、CPU302は、PLC100の管理メモリ160に、次の3つの情報(B1~B3)の書き込み、図8の処理を終了させる。
B2)日時
B3)支援装置のID
管理メモリ160に情報B1~B3が書き込まれることにより、図5に示されたような履歴において、1つのメンテナンス動作についての情報が追加される。「B1)実行内容」は、図5の「内容」に対応する。「B2)日時」は、図5の「日時」に対応する。「B3)支援装置のID」は、支援装置300のIDであり、図5の「デバイス」に対応する。支援装置300のIDは、たとえばHDD308に格納されている。
図9は、支援装置300によるPLC100のメンテナンス動作のための処理の他の例のフローチャートである。図9では、左側に、支援装置300のCPU302によって実行される処理が示され、右側に、PLC100のプロセッサ122によって実行される処理が示されている。
A2)日時
A3)PLCのID
ステップS18において書き込まれる情報(A1~A3)は、ステップSA18(図8参照)において書き込まれる情報(A1~A3)と同じである。
ステップS20で、CPU302は、PLC100に対して、管理メモリ160への次の3つの情報(B1~B3)の書き込みを指示して、図9の処理を終了させる。
B2)日時
B3)支援装置のID
ステップS20において書き込みを指示される情報(B1~B3)は、ステップSA20(図8参照)においてCPU302が管理メモリ160に書き込む情報(B1~B3)と同じである。
図10は、PLC100が、記録媒体500に格納されたデータを不揮発性メモリ126に書き込むことによって実行されるメンテナンス動作の処理の一例のフローチャートである。図10の処理は、たとえば作業員がPLC100の開始ボタン(入力装置132の一例)を操作することによって、開始される。
C2)日時
C3)PLCのID
これにより、図7に示されたような履歴において、1つのメンテナンス動作についての情報が追加される。「C1)実行内容」は、図7の「内容」に対応する。「C2)日時」は、図7の「日時」に対応する。「C3)PLCのID」は、PLC100のIDであり、図7の「PLC」に対応する。
ステップS62で、プロセッサ122は、管理メモリ160に、次の3つの情報(D1~D3)を書き込む。
D2)日時
D3)SDメモリカードのID
これにより、図5に示されたような履歴において、1つのメンテナンス動作についての情報が追加される。「D1)実行内容」は、図5の「内容」に対応する。「D2)日時」は、図5の「日時」に対応する。「D3)SDメモリカードのID」は、記録媒体500のID(記録媒体500を特定する情報の一例)であり、図5の「デバイス」に対応する。プロセッサ122は、記録媒体500から、当該記録媒体のIDを読み込む。
<メンテナンス動作の履歴の表示(1)>
CPU302は、メンテナンス履歴記憶部332に格納されたメンテナンス動作の履歴(図6参照)をモニタ314に表示することができる。
CPU302は、PLC100の管理メモリ160に格納されたメンテナンス動作の履歴を、HDD308に取り込むことができる。また、CPU302は、SDメモリカードインタフェース316に記録媒体500が装着された場合、当該記録媒体500に格納されているメンテナンス動作の履歴を、メンテナンス履歴記憶部332に格納された履歴およびPLC100から取り込んだ履歴と組み合わせて表示することができる。
CPU302は、PLC100の管理メモリ160に格納されたメンテナンス動作の履歴を、HDD308に取り込むことができる。CPU302は、また、記録媒体500(ID「2B63-3AA4」)に格納されたメンテナンス動作の履歴を、HDD308に取り込むことができる。さらに、CPU302は、SDメモリカードインタフェース316に別の記録媒体500が装着された場合、当該別の記録媒体500(ID「3C87-2EB5」)に格納されているメンテナンス動作の履歴を、メンテナンス履歴記憶部332に格納された履歴、ならびに、PLC100および記録媒体500から取り込んだ履歴と組み合わせて表示することができる。
Claims (13)
- 生産システムを制御するための制御機器であって、
記憶装置と、
可搬型記録媒体に記録された前記制御機器のファームウェアを前記記憶装置に書き込むように構成されたプロセッサとを備え、
前記プロセッサは、前記記憶装置に、前記ファームウェアの書き込みを特定する情報を書き込むように構成されている、制御機器。 - 前記ファームウェアの書き込みを特定する情報は、前記記憶装置に書き込まれたファームウェアの名称を特定する情報を含む、請求項1に記載の制御機器。
- 前記ファームウェアの書き込みを特定する情報は、前記可搬型記録媒体を特定する情報を含む、請求項1または請求項2に記載の制御機器。
- 生産システムを制御するための制御機器と、前記制御機器と通信可能な支援装置とを備える制御システムであって、
前記制御機器は、
第1の記憶装置と、
前記支援装置と通信するための第1のインタフェースとを含み、
前記支援装置は、
第2の記憶装置と、
前記制御機器と通信するための第2のインタフェースと、
前記第2のインタフェースを介して、前記第1の記憶装置に、前記第2の記憶装置に記録された前記制御機器のファームウェアを書き込むように構成されたコントローラとを含み、
前記コントローラは、さらに、前記第1の記憶装置に、前記ファームウェアの書き込みを特定する情報を書き込むように構成されている、制御システム。 - 前記コントローラは、さらに、前記第2の記憶装置に、前記ファームウェアの書き込みを特定する情報を書き込み、
前記支援装置は、前記第1の記憶装置内の前記ファームウェアの書き込みを特定する情報と、前記第2の記憶装置内の前記ファームウェアの書き込みを特定する情報とを表示するように構成された表示手段をさらに含む、請求項4に記載の制御システム。 - 前記制御機器は、当該制御機器に対して着脱可能な可搬型記録媒体に記録された当該制御機器のファームウェアを、前記第1の記憶装置に書き込むように構成されたプロセッサをさらに含み、
前記プロセッサは、前記可搬型記録媒体に記録されたファームウェアの前記第1の記憶装置への書き込みを特定する情報を前記第1の記憶装置に書き込むように構成されており、
前記表示手段は、さらに、前記可搬型記録媒体に記録されたファームウェアの前記第1の記憶装置への書き込みを特定する情報を表示するように構成されている、請求項4または請求項5に記載の制御システム。 - 生産システムを制御するための制御機器と通信可能な支援装置であって、
記憶装置と、
前記制御機器と通信するためのインタフェースと、
前記インタフェースを介して、前記制御機器に、前記記憶装置に記録された当該制御機器のファームウェアを書き込むように構成されたコントローラとを含み、
前記コントローラは、前記制御機器に、当該制御機器へのファームウェアの書き込みを特定する情報を書き込むように構成されている、支援装置。 - 前記制御機器へのファームウェアの書き込みを特定する情報は、前記制御機器を特定する情報を含む、請求項7に記載の支援装置。
- 生産システムを制御するための制御機器のコンピュータによって実行される、当該制御機器のメンテナンスの管理方法であって、
可搬型記録媒体に記録された前記制御機器のファームウェアを当該制御機器の記憶装置に書き込むステップと、
前記制御機器の記憶装置に、前記ファームウェアの書き込みを特定する情報を書き込むステップとを備える、制御機器のメンテナンスの管理方法。 - 前記ファームウェアの書き込みを特定する情報は、前記可搬型記録媒体を特定する情報を含む、請求項9に記載の制御機器のメンテナンスの管理方法。
- 生産システムを制御するための制御機器と通信可能な支援装置において実行される、制御機器へのファームウェアの書き込みの管理方法であって、
前記制御機器に、当該制御機器のファームウェアを書き込むステップと、
前記制御機器に、当該制御機器のファームウェアを書き込みを特定する情報を書き込むステップとを備える、制御機器のメンテナンスの管理方法。 - 前記制御機器のファームウェアを書き込みを特定する情報は、前記制御機器を特定する情報を含む、請求項11に記載の制御機器のメンテナンスの管理方法。
- 生産システムを制御するための制御機器であって、
記憶装置と、
前記制御機器のファームウェアを前記記憶装置から削除するように構成されたプロセッサとを備え、
前記プロセッサは、前記記憶装置に、前記ファームウェアの削除を特定する情報を書き込むように構成されている、制御機器。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201580012294.2A CN106068481B (zh) | 2014-03-14 | 2015-01-15 | 控制设备、控制***、支援装置以及控制设备的维护的管理方法 |
US15/123,301 US10108187B2 (en) | 2014-03-14 | 2015-01-15 | Control device, control system, support device, and control-device maintenance management method |
EP15762443.8A EP3104236B1 (en) | 2014-03-14 | 2015-01-15 | Control device, control system, support apparatus, and control-device maintenance management method |
JP2016507377A JP6414590B2 (ja) | 2014-03-14 | 2015-01-15 | 制御機器、制御システム、支援装置、および、制御機器のメンテナンスの管理方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014052681 | 2014-03-14 | ||
JP2014-052681 | 2014-03-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015136966A1 true WO2015136966A1 (ja) | 2015-09-17 |
Family
ID=54071420
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/050880 WO2015136966A1 (ja) | 2014-03-14 | 2015-01-15 | 制御機器、制御システム、支援装置、および、制御機器のメンテナンスの管理方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10108187B2 (ja) |
EP (1) | EP3104236B1 (ja) |
JP (1) | JP6414590B2 (ja) |
CN (1) | CN106068481B (ja) |
WO (1) | WO2015136966A1 (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 |
---|---|---|---|---|
JP6551259B2 (ja) * | 2016-02-26 | 2019-07-31 | オムロン株式会社 | マスタ装置、スレーブ装置、エラー監視システム、マスタ装置の制御方法、および制御プログラム |
KR102217332B1 (ko) * | 2016-12-26 | 2021-02-18 | 미쓰비시덴키 가부시키가이샤 | 엘리베이터의 수복 지원 시스템 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006330866A (ja) * | 2005-05-24 | 2006-12-07 | Keyence Corp | プログラマブル・ロジック・コントローラ |
JP2006330867A (ja) * | 2005-05-24 | 2006-12-07 | Keyence Corp | プログラム変更履歴管理システム及びこれに適用されるプログラム編集装置並びにプログラム |
JP2008257415A (ja) * | 2007-04-04 | 2008-10-23 | Yokogawa Electric Corp | プログラム書き込み機能を有するコントローラ |
JP2010097478A (ja) * | 2008-10-17 | 2010-04-30 | Yokogawa Electric Corp | プログラマブル・ロジック・コントローラ |
WO2013168224A1 (ja) * | 2012-05-08 | 2013-11-14 | 三菱電機株式会社 | プログラマブルロジックコントローラ、プログラミングツール及びプログラム・パラメータ編集システム |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1116324A (ja) | 1997-06-19 | 1999-01-22 | Oputoromu:Kk | 電子回路を有する記憶媒体 |
JP3077667B2 (ja) * | 1998-04-24 | 2000-08-14 | 日本電気株式会社 | 磁気テープ装置及びコンピュータ読み取り可能な磁気テープ媒体 |
JP2002297388A (ja) | 2001-03-29 | 2002-10-11 | Yaskawa Electric Corp | システムパートプログラムのダウンロード方法、それに用いるシステムメモリおよびシステムパートプログラム |
US7213052B2 (en) * | 2001-03-31 | 2007-05-01 | Minolta Co., Ltd. | Data communication apparatus capable of rewriting firmware |
CA2357382A1 (en) * | 2001-09-17 | 2003-03-17 | Soma Networks, Inc. | Software update method, apparatus and system |
JP4145749B2 (ja) * | 2003-08-12 | 2008-09-03 | パイオニア株式会社 | 情報記録媒体、情報記録媒体用の記録装置及び記録方法、情報記録媒体用の再生装置及び再生方法、記録又は再生制御用のコンピュータプログラム、並びに制御信号を含むデータ構造 |
JP2005236795A (ja) * | 2004-02-20 | 2005-09-02 | Nec Corp | 無線通信システム、及び無線通信システムにおける無線通信端末局のファームウェア更新方法 |
US7730326B2 (en) * | 2004-11-12 | 2010-06-01 | Apple Inc. | Method and system for updating firmware stored in non-volatile memory |
JP4929726B2 (ja) * | 2005-03-07 | 2012-05-09 | 富士ゼロックス株式会社 | 画像処理システム |
CN101151597A (zh) * | 2005-03-29 | 2008-03-26 | 富士通株式会社 | 信息处理装置、程序以及存储介质 |
JP2007012123A (ja) * | 2005-06-29 | 2007-01-18 | Matsushita Electric Ind Co Ltd | リムーバブルメディア記録再生装置の記録・再生動作抑止方法、記録動作抑止方法、ファームウエア更新方法およびファームウエアが格納されたファイル |
JPWO2007108127A1 (ja) * | 2006-03-23 | 2009-07-30 | 三菱電機株式会社 | システムプログラムダウンロードシステム |
JP2008102865A (ja) * | 2006-10-20 | 2008-05-01 | Mitsubishi Electric Corp | 制御装置および制御装置内部情報取得システム |
US20080109647A1 (en) * | 2006-11-07 | 2008-05-08 | Lee Merrill Gavens | Memory controllers for performing resilient firmware upgrades to a functioning memory |
US7978580B1 (en) * | 2007-04-17 | 2011-07-12 | Marvell International Ltd. | Calibrating optical drive write parameters during writing |
JP2009032076A (ja) * | 2007-07-27 | 2009-02-12 | Canon Inc | 制御プログラムの更新方法 |
JP2009223586A (ja) | 2008-03-15 | 2009-10-01 | Omron Corp | ビルディング・ブロック型のplc |
KR101219432B1 (ko) * | 2008-03-18 | 2013-01-11 | 삼성전자주식회사 | 화상형성장치 및 그 펌웨어 이력정보 제공방법 |
US20130198443A1 (en) | 2008-09-30 | 2013-08-01 | Rockwell Automation Technologies, Inc. | Systems and methods for programming a plurality of motor drives |
JP5564956B2 (ja) * | 2010-01-15 | 2014-08-06 | 富士通株式会社 | 情報処理装置及び情報処理装置のファームウェア更新方法 |
US8713559B2 (en) * | 2010-11-15 | 2014-04-29 | Schneider Electric It Corporation | System and method for updating firmware |
US8924778B2 (en) * | 2010-12-29 | 2014-12-30 | Lsi Corporation | Method to synchronize a replacement controller's firmware version to the native configuration database version on a simplex array |
CN102693181A (zh) * | 2011-03-25 | 2012-09-26 | 鸿富锦精密工业(深圳)有限公司 | 分位刷写***及方法 |
US20130318516A1 (en) * | 2011-04-29 | 2013-11-28 | Edward D. Knapton | Computer system firmware update |
CN103558809B (zh) * | 2012-05-09 | 2019-06-18 | 布里斯托尔D/B/A远程自动化解决方案公司 | 配置过程控制设备的方法和装置 |
JP6101073B2 (ja) * | 2012-12-27 | 2017-03-22 | 日本電産サンキョー株式会社 | 周辺装置、周辺装置の制御方法、ファームウェアのダウンロードシステム、およびプログラム |
TWI502507B (zh) * | 2013-01-22 | 2015-10-01 | Wistron Corp | 電池韌體更新方法、可攜式電子裝置及充電電池模組 |
US9092300B2 (en) * | 2013-04-18 | 2015-07-28 | Ottr Products, Llc | Peripheral device and method for updating firmware thereof |
JP6433844B2 (ja) * | 2015-04-09 | 2018-12-05 | 株式会社ソニー・インタラクティブエンタテインメント | 情報処理装置、中継装置、情報処理システム、およびソフトウェアアップデート方法 |
-
2015
- 2015-01-15 EP EP15762443.8A patent/EP3104236B1/en active Active
- 2015-01-15 CN CN201580012294.2A patent/CN106068481B/zh active Active
- 2015-01-15 JP JP2016507377A patent/JP6414590B2/ja active Active
- 2015-01-15 WO PCT/JP2015/050880 patent/WO2015136966A1/ja active Application Filing
- 2015-01-15 US US15/123,301 patent/US10108187B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006330866A (ja) * | 2005-05-24 | 2006-12-07 | Keyence Corp | プログラマブル・ロジック・コントローラ |
JP2006330867A (ja) * | 2005-05-24 | 2006-12-07 | Keyence Corp | プログラム変更履歴管理システム及びこれに適用されるプログラム編集装置並びにプログラム |
JP2008257415A (ja) * | 2007-04-04 | 2008-10-23 | Yokogawa Electric Corp | プログラム書き込み機能を有するコントローラ |
JP2010097478A (ja) * | 2008-10-17 | 2010-04-30 | Yokogawa Electric Corp | プログラマブル・ロジック・コントローラ |
WO2013168224A1 (ja) * | 2012-05-08 | 2013-11-14 | 三菱電機株式会社 | プログラマブルロジックコントローラ、プログラミングツール及びプログラム・パラメータ編集システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP3104236A4 * |
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 |
---|---|
JPWO2015136966A1 (ja) | 2017-04-06 |
JP6414590B2 (ja) | 2018-10-31 |
EP3104236A4 (en) | 2018-04-11 |
EP3104236B1 (en) | 2021-05-12 |
CN106068481B (zh) | 2020-03-10 |
US20170068240A1 (en) | 2017-03-09 |
CN106068481A (zh) | 2016-11-02 |
EP3104236A1 (en) | 2016-12-14 |
US10108187B2 (en) | 2018-10-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4462449B2 (ja) | 制御システム設定装置 | |
US10705500B2 (en) | Support device, method, and recording medium for simplifying control program changing operation | |
JP6357770B2 (ja) | 制御装置および通信制御方法 | |
JP5583305B2 (ja) | プログラマブルロジックコントローラ、プログラミングツール及びプログラム・パラメータ編集システム | |
WO2015136966A1 (ja) | 制御機器、制御システム、支援装置、および、制御機器のメンテナンスの管理方法 | |
WO2015075790A1 (ja) | シーケンスプログラム作成支援装置 | |
JP6260005B2 (ja) | 機能設定方法 | |
KR20160086957A (ko) | 엔지니어링 툴 프로그램 및 네트워크 시스템 | |
JP6442131B2 (ja) | 制御システムおよび制御装置 | |
JP6171385B2 (ja) | コントローラおよび情報処理装置 | |
JP6337956B2 (ja) | 制御機器、制御システム、制御機器の制御方法、および、制御システムの制御方法 | |
JP6390696B2 (ja) | ライセンス情報管理装置、ライセンス情報管理方法、および、プログラム | |
WO2021044654A1 (ja) | 情報処理システム、プログラマブル表示器および情報処理装置 | |
JP6680313B2 (ja) | 制御装置および通信制御方法 | |
JPWO2019207679A1 (ja) | モニタ支援装置、モニタ支援方法およびモニタ支援プログラム | |
JP5951041B2 (ja) | プログラマブル表示器 | |
JP6705464B2 (ja) | 制御装置および通信制御方法 | |
WO2023248471A1 (ja) | 監視装置及びロボット監視システム | |
JP7415091B1 (ja) | プログラム、プログラム管理装置、プログラム管理システム、およびプログラム管理方法 | |
JP2008234379A (ja) | ソフトウェア生成装置ならびにソフトウェア生成方法 | |
JP2023094787A (ja) | シナリオ管理システム、シナリオ管理方法、及びシナリオ管理プログラム | |
JP2023096331A (ja) | シナリオ管理システム、シナリオ管理方法、及びシナリオ管理プログラム | |
JP2012058961A (ja) | ファイル編集装置、その制御方法、およびプログラム | |
JPH10333719A (ja) | プログラマブルコントローラのプログラミング装置 | |
JP2018022367A (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: 15762443 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016507377 Country of ref document: JP Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 2015762443 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15123301 Country of ref document: US Ref document number: 2015762443 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |