This application is a 371 application of the International PCT application serial no. PCT/JP2018/007412, filed on Feb. 28, 2018, which claims the priority benefits of Japan application no. 2017-106175, filed on May 30, 2017. The entirety of each of the above-mentioned patent applications is hereby incorporated by reference herein and made a part of this specification.
The present invention relates to a HMI (human machine interface) development support technology for supporting HMI development of control equipment.
Currently, industrial control equipment such as a PLC (programmable logic controller) or the like is equipped with an indicator capable of operation input, that is, a HMI. An operator can know states of the control equipment and a FA (factory automation) system including the control equipment by viewing a screen of the HMI. In addition, the operator can perform various settings such as a parameter setting and the like on each equipment of the FA system including the control equipment by performing an operation input on the screen of the HMI.
Then, in order to create the screen and function of the HMI, for example, a HMI development support device as shown in patent literature 1 is variously designed.
Patent literature 1: Japanese Laid-Open No. 2009-157580
However, in a conventional HMI development support device, basically, only one HMI project is displayed and edited, and comparison with other HMI projects is not easy. In addition, in the conventional HMI development support device, the HMI projects can only be displayed on the screen respectively even in a multi-window configuration, and detailed comparison in items of the HMI projects is not easy.
Accordingly, an objective of the present invention is to provide a HMI development support technology with which it is possible to easily compare a plurality of HMI projects.
The HMI development support device of the present invention includes a HMI editing unit and a display unit. The HMI editing unit performs editing of a HMI project which is configured by a plurality of objects. The HMI editing unit has a comparison processing unit which forms a comparison screen for highlighting differences between a reference HMI project and the HMI project being edited and displays the comparison screen on the display unit. In addition, in the HMI development support device, the comparison screen is a screen that highlights different attribute values in objects of the reference HMI project and objects of the HMI project being edited.
In the configuration, the differences between the reference HMI project and the HMI project being edited are easily recognized visually for each attribute value.
In addition, in the HMI development support device, the comparison processing unit forms the comparison screen for highlighting objects of the reference HMI project and objects of the HMI project being edited in which attribute values are different from each other and variables are common.
In the configuration, the differences are easily recognized visually for each displayed object.
In addition, in the HMI development support device, the comparison processing unit has a merge processing unit which reflects the attribute values of the objects of the reference HMI project on the attribute values of the objects of the HMI project being edited.
In the configuration, the attribute values of the objects of the reference HMI project is easily reflected on the objects of the HMI project being edited.
In addition, in the HMI development support device, the merge processing unit reflects selected attribute values when a plurality of attribute values is different.
In the configuration, merge can be selectively made for each attribute value.
In addition, the HMI development support device includes a temporary storage unit which temporarily stores the HMI project being edited. On receiving cancel of processing for reflecting the attribute values, the merge processing unit returns to the HMI project being edited that is read out from the temporary storage unit.
In the configuration, the attribute values of the objects before the merge are securely restored even if the merge is cancelled.
According to the present invention, a plurality of HMI projects can be easily compared.
A HMI development support technology of an embodiment of the present invention is described with reference to the drawings.
As shown in
The calculation unit 11 is a so-called CPU or the like and executes programs that are read out. A HMI editing program 210 is stored in the storage unit 12. The calculation unit 11 reads out and executes the HMI editing program 210, and thereby implements editing of a HMI project.
The HMI editing program 210 has a main editing unit 211 and a comparison processing unit 212. The main editing unit 211 is a part executing main processing of the editing of the HMI project.
The comparison processing unit 212 is a part executing comparison processing of the HMI project. The comparison processing refers to the processing for comparing the HMI project being edited and a reference HMI project. The comparison processing unit 212 has a merge processing unit 213.
The merge processing unit 213 is a part executing merge processing of the HMI project. The merge processing refers to the processing for reflecting attribute values and the like of the reference HMI project on the HMI project being edited. Besides, specific contents of the comparison processing and the merge processing are described later.
Besides, the comparison processing unit 212 may be executed by a call from the main editing unit 211. In addition, the comparison processing unit 212 may be described as a part of the main editing unit 211. Similarly, the merge processing unit 213 may be described as a part of the comparison processing unit 212. In addition, the merge processing unit 213 may be executed by a call from the comparison processing unit 212.
A HMI project storage unit 220 is assigned to the storage unit 12. A HMI project edited in the past is stored with a history thereof in the HMI project storage unit 220.
The operation input unit 13 is, for example, a mouse or a keyboard, and receives operation input to a HMI editing screen and outputs the operation input to the calculation unit 11.
The display unit 14 is, for example, a liquid crystal display or the like, and displays a HMI editing screen that corresponds to the processing of the HMI editing program 210 executed by the calculation unit 11.
The temporary storage unit 15 is a volatile memory or the like and temporarily stores the HMI project being edited. Besides, the temporary storage unit 15 may also temporarily store a reference object.
The communication control unit 16 executes communication between the calculation unit 11 and an external device. For example, the communication control unit 16 executes communication between the calculation unit 11 and an external control equipment or server.
Besides, the above-described HMI project storage unit 220 can also be omitted when the latest version of the HMI project installed on the control equipment is set as a reference online.
In addition, the above-described communication control unit 16 can also be omitted when the comparison processing is performed offline.
The HMI development support device 10 having this configuration executes the comparison processing and the merge processing of the HMI project as shown below.
The HMI development support device 10 receives selection of the reference HMI project (S11).
When the HMI development support device 10 is offline (S101: NO) or receives comparison of an offline inquiry even in the online state (S102: NO), search of a reference candidate HMI project is performed on the HMI project storage unit 220 (S112). At this time, the HMI development support device 10 refers to variables of the objects included in the HMI project being edited, and extracts the HMI projects having the same variable as reference candidates. The HMI development support device 10 displays a list of the reference candidates (S113). The HMI development support device 10 receives selection of the reference HMI project from the list of the reference candidates according to specification of the operation input unit 13 and the like (S114).
The HMI development support device 10 acquires a screen structure and attribute values of the reference HMI project (S12). The HMI development support device 10 temporarily stores the screen structure and the attribute values of the reference HMI project and a screen structure and attribute values of the HMI project being edited (S13).
The HMI development support device 10 compares the attribute values of the reference HMI project with the attribute values of the HMI project being edited (S14).
If there are differences between the attribute values of the reference HMI project and the attribute values of the HMI project being edited (S15: YES), the HMI development support device 10 displays a comparison screen on which the differences are highlighted (S16). Specifically, the HMI development support device 10 highlights the attribute values and the objects corresponding to the differences on the comparison screen.
On the other hand, if there are no differences (S15: NO), the HMI development support device 10 displays a normal comparison screen (S17). Specifically, the HMI development support device 10 display a comparison screen without highlights.
As shown in
The editing target attribute value list 412 and the reference attribute value list 422 are displayed adjacently. The editing target attribute value list 412 and the reference attribute value list 422 are displayed so that individual attribute values are adjacent. In this way, comparison between individual attribute values of the HMI project being edited and individual attribute values of the reference HMI project is easy.
The editing target object arrangement 411 and the reference object arrangement 421 are displayed to clamp the editing target attribute value list 412 and the reference attribute value list 422. In this way, comparison between object arrangements of the HMI project being edited and object arrangements of the reference HMI project is easy.
Furthermore, as shown in
The type of the tags, that is, the type of the differences is displayed on a tag reference area 44 of the comparison screen 140. Specifically, “Dif” means that an object in which variables are the same exists in both the HMI project being edited and the reference HMI project but the attribute values are different. “Lso” means that the object does not exist in the HMI project being edited but exists in the reference HMI project. “Rso” means that the object does not exist in the reference HMI project but exists in the HMI project being edited. “Cpy” means that the attribute value or the object itself is copied by the merge processing described later from the reference HMI project to the HMI project being edited.
For example, in the example of
In addition, in the example of
Furthermore, on the comparison screen 140, the differences are highlighted for each attribute value in the editing target attribute value list 412 and the reference attribute value list 422. For example, in the example of
Besides, not only Prp (property), but Eve (event action) and Anm (animation) can also be set as the attribute values of object, and they are highlighted as long as there are differences, and the tags are displayed on the objects of the editing target display area 41 and the reference display area 42. The Prp, Eve, and Anm are selected by an attribute value item switching tag 43 of the comparison screen 140, and thereby the display can be switched.
Accordingly, by having the configuration and processing of the HMI development support device 10, the programmer can easily and more reliably recognize the differences between the HMI project being edited and the reference HMI project. Furthermore, the programmer can easily and more reliably recognize the differences for each attribute value.
Next, the merge processing is described.
The HMI development support device 10 receives selection of a merge target of the HMI project being edited (S21). The merge target may be selected in object unit or in attribute value unit. The HMI development support device 10 receives merge processing of the selected object and the selected attribute values (S22).
If an object of the editing target object arrangement 411 is selected (S23: YES), the HMI development support device 10 performs merge in object unit (S24). That is, the HMI development support device 10 replaces all attribute values which are differences in the selected object with the attribute values of the objects having the same variables in the reference HMI project. In this way, even when a plurality of attribute values in the object is different, all the different attribute values can be equalized by one operation.
On the other hand, if the attribute values of the editing target attribute value list 412 are selected (S23: NO), the HMI development support device 10 performs merge with the selected attribute values only (S25). That is, the HMI development support device 10 replaces only the selected attribute values that are differences with the attribute values of the objects having the same variables in the reference HMI project. In this way, when a plurality of attribute values in the object is different, it is possible to equalize only the necessary attribute values.
The HMI development support device 10 updates a display of the comparison screen 140 corresponding to a merge result (S26). Accordingly, the programmer can immediately recognize the merge result.
If a cancel operation of merge is received (S27: YES), the HMI development support device 10 cancels the merge and redisplays the HMI project being edited before the merge processing which is stored in the temporary storage unit 15 (S28). Besides, if the cancel processing of merge is not performed (S27: NO), the HMI development support device 10 does not perform the cancel processing.
First, as shown in
When “Merge” is selected, the HMI development support device 10 reads out the attribute values of the “Button 1” object of the reference HMI project.
The HMI development support device 10 overwrites the attribute values of the “Button 1” object of the HMI project being edited with the attribute values of the “Button 1” object of the reference HMI project that are read out.
As shown in
In addition, in the editing target attribute value list 412, as shown in
First, as shown in
When “Merge” is selected, the HMI development support device 10 reads out the attribute values of the item “BCU” of the “Button 1” object of the reference HMI project.
The HMI development support device 10 overwrites the attribute values of the item “BCU” of the “Button 1” object of the HMI project being edited with the attribute values of the item “BCU” of the “Button 1” object of the reference HMI project that are read out.
As shown in
In addition, in the editing target attribute value list 412, as shown in
Accordingly, by having the configuration and processing of the HMI development support device 10, the programmer can easily perform merge for the HMI project being edited in object unit or in attribute value unit. Furthermore, the programmer can immediately recognize the merge result.
| Number | Date | Country | Kind |
|---|---|---|---|
| JP2017-106175 | May 2017 | JP | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2018/007412 | 2/28/2018 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2018/220922 | 12/6/2018 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 5974254 | Hsu | Oct 1999 | A |
| 7071934 | Faoro | Jul 2006 | B1 |
| 20010013877 | Fujino | Aug 2001 | A1 |
| 20070153708 | Dominick | Jul 2007 | A1 |
| 20080104016 | Atmaja | May 2008 | A1 |
| 20080303819 | Latour et al. | Dec 2008 | A1 |
| 20120304148 | Braun | Nov 2012 | A1 |
| 20130262373 | Rampson | Oct 2013 | A1 |
| 20130262420 | Edelstein | Oct 2013 | A1 |
| 20140278307 | Hosey et al. | Sep 2014 | A1 |
| 20150095755 | Bonk | Apr 2015 | A1 |
| 20150199113 | Prabhat | Jul 2015 | A1 |
| 20160061579 | Tsujimoto | Mar 2016 | A1 |
| 20180364897 | Takashima | Dec 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 102591635 | Jul 2012 | CN |
| 104142881 | Nov 2014 | CN |
| H0434662 | Feb 1992 | JP |
| H04370805 | Dec 1992 | JP |
| H11154108 | Jun 1999 | JP |
| 2009157580 | Jul 2009 | JP |
| 2012064156 | Mar 2012 | JP |
| 2015079493 | Apr 2015 | JP |
| 2016014951 | Jan 2016 | JP |
| 2016024528 | Feb 2016 | JP |
| 2016218977 | Dec 2016 | JP |
| 2011154989 | Dec 2011 | WO |
| 2012176365 | Dec 2012 | WO |
| 2016139805 | Sep 2016 | WO |
| 2016157540 | Oct 2016 | WO |
| Entry |
|---|
| “Notification of Written Submission of Publications of Japan Counterpart Application”, dated Nov. 10, 2020, with English translation thereof, p. 1-p. 13. |
| “Office Action of Japan Counterpart Application”, dated Nov. 10, 2020, with English translation thereof, p. 1-p. 13. |
| “International Search Report (Form PCT/ISA/210) of PCT/JP2018/007412,” dated Apr. 24, 2018, with English translation thereof, pp. 1-5. |
| “Office Action of Japan Counterpart Application”, dated Sep. 15, 2020, with English translation thereof, p. 1-p. 06. |
| “Search Report of Europe Counterpart Application”, dated Jan. 26, 2021, p. 1-p. 8. |
| “Office Action of China Counterpart Application” with English translation thereof, dated Dec. 28, 2021, p. 1-p. 17. |
| Number | Date | Country | |
|---|---|---|---|
| 20210081078 A1 | Mar 2021 | US |