SCADA webpage HMI system

Abstract

The SCADA webpage HMI system is provided with an address continuation source specifying unit and an address continuation unit. An address continuation source specifying unit specifies an existing component of the first screen serving as an address continuation source for a new component of the second screen serving as an address continuation object. When the address following source specifying unit specifies the address following source of the new component as the existing component, the new component and the existing component perform the same processing, and the address allocation unit has allocated the address to the existing component, the address following unit follows the address of the existing component to the new component. The web browser displays the HMI screen, updates the display of the existing component of the first screen and the new component of the second screen on the basis of the common display signal, and transmits an operation signal corresponding to the operation of the existing component and the new component to the common address of the PLC.

Description

Technical Field

[0001] The present invention relates to a SCADA web page HMI system. Background Art

[0002] Supervisory Control and Data Acquisition (SCADA) is known as a mechanism for monitoring and controlling social infrastructure systems. Examples of these systems include steel mills, power transmission and distribution systems, water and sewage systems, building management systems, and road systems. SCADA is a type of industrial control system that uses computers to monitor and control systems. SCADA requires immediate responsiveness (real-time performance) that matches the system's processing capabilities.

[0003] SCADA has HMI (Human Machine Interface), monitoring control system, remote input and output (RIO) and communication platform as subsystems.

[0004] An HMI displays data about the target process (device being monitored) and components such as operation buttons (also called "operational components" or "items") on the HMI screen, allowing operators to control the target process by monitoring the process or operating the operation buttons. A supervisory control system collects signal data (PLC signals) from the process and issues control instructions to the process. A supervisory control system consists of a PLC (Programmable Logic Controller). Remote input / output devices connect to sensors installed within the process, convert sensor signals into digital data, and transmit this digital data to the supervisory control system. A communication platform connects the supervisory control system to the remote input / output devices.

[0005] In a SCADA system with this structure, it is necessary to accurately transmit operation and display signals between the supervisory control system (PLC) and the HMI. To achieve this, it is necessary not only to associate the operation and display signals with the display components on the HMI screen, but also to properly manage the address information used to send and receive the operation and display signals, such as the item names of the operation and display signals, and the addresses of the operation and display signals stored in the supervisory control system (PLC) and the HMI.

[0006] In recent years, with the large-scale development of factories, industrial control systems have also become large-scale. In large-scale industrial control systems, it is necessary to process address information assigned to tens of thousands or even hundreds of thousands of items.

[0007] However, when the HMI screen designer manually inputs the signal names of the operation signals and display signals, and the addresses of the operation signals and display signals stored in the monitoring control system (PLC) and the HMI, it becomes a very heavy burden for the designer, requires a huge amount of time, and becomes a cause of operational errors.

[0008] To reduce such work time and work errors, for example, a design support device described in Patent Document 1 has a function of automatically allocating addresses for transmitting and receiving operation signals and display signals between a supervisory control system (PLC) and an HMI connected via a network.

[0009] Prior art literature

[0010] Patent Literature

[0011] Patent Document 1: Japanese Patent Application Laid-Open No. 2011-81430 Summary of the Invention

[0012] Problems to be solved by the invention

[0013] However, sometimes a newly created HMI screen contains a new component that is identical to an existing component on an existing HMI screen (a new component associated with the same operation signal or display signal). In this case, even if a PLC address has already been assigned to the existing component, a new PLC address is assigned to the new component. This requires PLC software changes, which increases the designer's workload. Furthermore, the increased number of PLC addresses increases the address area within the PLC, increasing the amount of data sent to and received from the PLC.

[0014] The present disclosure is made to solve the above-mentioned problems. The purpose of the present disclosure is to provide a SCADA web page HMI system that, when adding or modifying an HMI screen, only adds new components that perform the same processing as existing components, eliminating the need to modify the PLC software, thereby reducing designer work time and minimizing the address area used within the PLC and the amount of data sent to and received by the PLC.

[0015] Means for solving problems

[0016] The first aspect relates to a SCADA webpage HMI system. The SCADA webpage HMI system is capable of updating the display state of at least one component displayed on an HMI screen on a web browser based on a display signal corresponding to a signal received from a PLC, and sending an operation signal corresponding to an operation of the at least one component to the PLC. The SCADA webpage HMI system includes an HMI design device for creating multiple HMI screens, and the HMI design device includes an address allocation unit for allocating addresses to all components on the created HMI screens. The SCADA webpage HMI system includes an address inheritance source designation unit and an address inheritance unit. An existing HMI screen is set as a first screen, an additional or modified HMI screen is set as a second screen, components on the first screen are set as existing components, and components on the second screen are set as new components. The address inheritance source designation unit designates an existing component as the address inheritance source for a new component to be inherited. If the address inheritance source designation unit designates an existing component as the address inheritance source for the new component, the new component and the existing component are processed identically, and the address allocation unit has already allocated an address to the existing component, the address inheritance unit inherits the address of the existing component to the new component. The web browser displays the HMI screen, updates the display of existing components on the first screen and new components on the second screen based on a common display signal, and sends operation signals corresponding to the operation of the existing components and the new components to a common address of the PLC.

[0017] The second aspect is based on the first aspect and further has the following features: the existing component and the new component are display components that update the display status on the first screen and the second screen based on the display signal, or are operation components for sending operation signals to the PLC.

[0018] The third aspect, in addition to the first aspect or the second aspect, has the following features: the SCADA web HMI system further includes an address transfer result generating unit that generates address transfer information that records the component name of the existing component and the component name of the new component.

[0019] Effects of the Invention

[0020] According to the present disclosure, new components that perform the same processing as existing components can be assigned the same addresses as existing components. This eliminates the need to install processing to activate new components in the PLC software; new components can be activated based on the addresses of existing components. This allows the HMI screen to be modified without changing the PLC software, reducing designer workload. Furthermore, the address area used within the PLC and the amount of data sent to and received by the PLC can be minimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1This is a diagram showing the configuration of a SCADA web HMI system according to an embodiment.

[0022] Figure 2 This is a block diagram showing an example of the hardware configuration of a SCADA web HMI design device and a SCADA web HMI execution device.

[0023] Figure 3 This is a block diagram that explains the main processing performed in the engineering tool and web browser.

[0024] Figure 4 This is a diagram showing an example of a drawing creation screen displayed by an engineering tool.

[0025] Figure 5 This is a diagram showing an example of a first screen and a second screen which are HMI screens created by drawing processing.

[0026] Figure 6 middle, Figure 6 (a) means Figure 5 FIG. 1 is a diagram showing an example of the in-screen component information of the first screen. Figure 6 (b) means Figure 5 FIG. 1 is a diagram showing an example of the on-screen component information of the second screen shown.

[0027] Figure 7 This is a diagram showing an example of the in-screen component information of the second screen after the input address is inherited from the source.

[0028] Figure 8 This is a flowchart for explaining the flow of the address allocation process 14 .

[0029] Figure 9 This is a diagram showing an example of allocation processing rules.

[0030] Figure 10 This is a diagram showing an example of the on-screen component information of the first screen after the address allocation process is executed.

[0031] Figure 11 This is an example of the on-screen component information of the second screen after the address assignment process and the address adoption process are executed.

[0032] Figure 12 This is a diagram showing an example of address takeover information generated after the address takeover process is executed. DETAILED DESCRIPTION

[0033] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. However, when numerical values such as the number, quantity, amount, range, etc. of each element are mentioned in the embodiments shown below, unless otherwise specifically stated or determined to be that value in principle, the present invention is not limited to the mentioned value. In addition, the configurations and the like described in the embodiments shown below are not necessarily essential in the present disclosure, unless otherwise specifically stated or determined to be that configuration in principle. Furthermore, the same reference numerals are assigned to the common elements in each figure, and duplicate descriptions are omitted.

[0034] <Overall system>

[0035] Figure 1 FIG. is a diagram showing the configuration of the SCADA web HMI system according to the embodiment. The SCADA web HMI system includes a SCADA web HMI design device (hereinafter also referred to as "HMI design device") 1 as an HMI development environment. The SCADA web HMI system includes, as subsystems, a SCADA web HMI execution device (also referred to as an HMI execution device)) 3 as an HMI execution environment, a monitoring and control system 4, a communication platform 5, a remote input / output device (RIO) 6, and a monitored object device 7.

[0036] The monitoring and control system 4 includes a programmable logic controller (PLC) having an address area 41 therein. The communication platform 5 connects the monitoring and control system 4 to the remote input / output device. The remote input / output device 6 is connected to sensors provided in the monitored object device 7, converts the signals of the sensors into digital data, and sends the digital data to the monitoring and control system 4. The monitored object device 7 is sensors, actuators, etc. that make up a factory.

[0037] <HMI design device>

[0038] The HMI design device 1 executes an engineering tool 10. The engineering tool 10 has functions capable of creating / editing drawings, saving drawing data in SVG (Scalable Vector Graphics) format, and an extended function. As an example, the drawing creation / editing function and the SVG data saving function are implemented by Microsoft Visio (registered trademark). In the HMI design device 1, a GUI is installed as a user interface for executing the engineering tool 10. The engineering tool 10 generates interface information 21 and HMI screen data 22 required for the HMI execution device 3 as an HMI execution environment to function. The interface information 21 and the HMI screen data 22 constitute web HMI data 2.

[0039] Figure 2This is a block diagram showing a hardware configuration example of the SCADA web HMI design device 1 and the SCADA web HMI execution device 3 . Figure 3 This is a block diagram for explaining main processing executed in the engineering tool 10 and the web browser 32 .

[0040] Each process described below in the HMI design device 1 is performed by Figure 2 The processing circuit shown is implemented by connecting at least one processor 1a, memory 1b, display 1c, and input / output interface 1d. Memory 1b stores programs describing the various processes executed by the engineering tool 10. Input / output interface 1d includes input devices such as a keyboard and mouse, as well as output devices capable of outputting web page HMI data 2 to files. Processor 1a executes programs read from memory 1b to implement the various processes described below in the HMI design device 1.

[0041] like Figure 3 As shown, the engineering tool 10 can execute, as main processes, drawing processing 11, component data generation processing 12, in-screen component information generation processing 13, address allocation processing 14, interface information generation processing 15, and HMI screen data generation processing 16. Each process executed by the engineering tool 10 will be described below.

[0042] (Cartographic Processing)

[0043] First, refer to Figure 4 as well as Figure 5 , a drawing process 11 for creating drawings used as HMI screens will be described. Figure 4 1c is a diagram showing an example of a drawing creation screen 100 displayed on the engineering tool 10. The drawing creation screen 100 is displayed on the display 1c.

[0044] The drawing processing 11 displays a template area 101 and a drawing area 102 in a drawing creation screen 100. The template area 101 displays master shapes 101a, 101b, and 101c of a plurality of components required for drawing creation, and the drawing area 102 displays drawings for the HMI screen. The drawing processing 11 selects a prototype from the template area 101 by operating the input / output interface 1d by the designer, and places the selected prototype in the drawing area 102. Figure 4 In the example shown, a prototype 101 a of a two-choice button item in the template area 101 is dragged and dropped into the drawing area 102 , thereby placing a two-choice button item 102 a in the drawing area 102 .

[0045] Figure 5This figure shows an example of HMI screens created through graphics processing, namely, a first screen G100 and a second screen G200. A two-selection button 111 is located on the first screen G100, and a two-selection button 112 is located on the second screen G200 at a different position from the first screen G100. The first screen G100 corresponds to the existing screen in the claims, while the second screen G200 corresponds to the new screen in the claims. The two-selection button 111 corresponds to the existing component in the claims, while the two-selection button 112 corresponds to the new component in the claims.

[0046] (Component data generation process)

[0047] Next, the component data generation process 12 will be described. Figure 4 When components are placed in the drawing area 102 shown, unique component data is automatically generated. Although not shown in the figure, the component data is data that associates the placement information of the components placed in the drawing area 102 with component identifiers, attribute identifiers, and component types.

[0048] Configuration information is static screen display data, such as the shape, position, and size of components placed in the drawing area 102. This information ensures that the component's appearance remains unchanged regardless of the value of the received PLC signal. Configuration information can be modified within the drawing area 102. A component identifier is a unique identifier, such as a component number, that identifies each component placed in a drawing. An attribute identifier indicates the dynamic display attributes of the component.

[0049] The component data generation process 12 generates a "component name" that combines the screen identifiers G100 and G200 of the HMI screen and the component identifier 1PL2, and generates an "item name" that combines the component name and the attribute identifier. The item name is unique in the SCADA web HMI system.

[0050] The component data generation process 12 generates one "component type" for each component. For example, a component type "PL" is generated for an operating component, and a component type "SL" is generated for a light display component.

[0051] (Processing of generating in-screen component information)

[0052] Next, refer to Figure 6 The in-screen component information generation process 13 will be described. Figure 6 (a) means Figure 5 FIG. 1 is a diagram showing an example of the on-screen component information 131 of the first screen G100 shown. Figure 6 (b) means Figure 5FIG. 1 is a diagram showing an example of the on-screen component information 132 of the second screen G200 shown.

[0053] The on-screen component information generation process 13 is executed when component data is generated by the component data generation process 12. This process generates tabular on-screen component information 131 and 132 for screens G100 and G200, respectively. Each component in the on-screen component information 131 and 132 contains the component name, component type, and item names of operation signals and display signals. The addresses of the operation signals and display signals are recorded after the address allocation process 14, described later, is executed.

[0054] Here, the component name of the address inheritance source is manually input by the HMI screen designer using the input / output interface 1d before executing the address inheritance process 140 described later and before executing the address assignment process 14. Therefore, the input / output interface 1d corresponds to the "address inheritance source specifying unit" in the claims. Figure 7 This diagram shows an example of the on-screen component information 132 of the second screen G200 after the component name of the first screen G100 is input as the address inheritance source.

[0055] When the address inheritance process 140 is executed in the address assignment process 14 described later, in order to associate the components of the address inheritance source, the "component name of the address inheritance source" is specified for each component. Figure 7 In the example shown, the on-screen component information 132 for the second screen G200 is edited, and the component name "G100_1PL2," the component name of the operational component placed on the first screen G100, is entered in the "Address Transfer Source" column. Here, the address transfer target component name "G200_1PL2" and the address flow source component name "G100_1PL2" are of the same component type PL and are therefore processed in the same manner. This means that they are associated with the same operation signal or display signal.

[0056] (Address allocation processing)

[0057] Next, refer to Figures 8 to 10 The address allocation process 14 will be described. The address allocation process 14 is executed by the designer of the HMI screen. The address allocation process 14 allocates addresses to all components of each screen G100 and G200. Figure 8 This is a flowchart for explaining the flow of the address allocation process 14 . Figure 9 This is a diagram showing an example of the allocation processing rule 141 . Figure 10 14 is a diagram showing an example of the in-screen component information 131 of the first screen G100 after execution of the address assignment process 14. The address assignment process 14 corresponds to the "address assignment means" in the claims.

[0058] When executing Figure 8 In the routine shown, first, the in-screen component information 131 and 132 generated in the in-screen component information generation process 13 are read (step S10). Next, the number of component names in the in-screen component information G100 and G200 is substituted into the variable N, and "1" is substituted into the counter variable i as the initial value (step S11). Next, the allocation processing rule 141 for allocating addresses is read (step S12). Figure 9 As shown, the allocation processing rule 141 defines the association between the number of bits of the operation signal and the number of bits of the display signal for each component type. Figure 9 In the example shown, the number of bits of the operation signal and the number of bits of the display signal are defined according to the component type. The engineering tool 10 has an allocation processing rule 141. The allocation processing rule 141 is stored in the memory 1b.

[0059] Next, a determination is made as to whether the value of the counter variable i is less than N (step S13). If the value of the counter variable i is less than N, a determination is made as to whether an address inheritance source has been specified (step S14). If an address inheritance source has been specified, the process proceeds to step S17, described below, to execute the address inheritance process 140. If an address inheritance source has not been specified, the process proceeds to step S15. The process of step S14 corresponds to the "address inheritance source specifying means" in the claims.

[0060] In step S15, addresses are assigned based on the assignment processing rule 141, based on the on-screen component information corresponding to the i-th component name in the on-screen component information 131 and 132. Specifically, based on the on-screen component information corresponding to the i-th component name and the number of bits of the operation signal and the number of bits of the display signal included in the assignment processing rule 141 read out in step S12, addresses are assigned to the operation signal sent from the SCADA webpage HMI execution device 3 to the supervisory control system (PLC) 4, and addresses are assigned to the display signal sent from the supervisory control system (PLC) 4 to the SCADA webpage HMI execution device 3. Then, i+1 is substituted into the variable i, and the process returns to step S13.

[0061] The address information generation process 14 can be executed for each of the screens G100 and G200. When the address information generation process 14 is executed for the first screen G100, as shown in FIG. Figure 10 As shown, based on the allocation processing rule 141 , addresses are allocated to the item names “G100_1PL1_CMD” and “G100_1PL2_CMD” of the operation signal and the item names “G100_1PL1_SL” and “G100_1PL2_SL” of the display signal of the component name “G100_1PL2”.

[0062] The address information generation process 14 includes an address use process 140 including steps S17 to S24. Figure 2 As shown, the address transfer process 140 is executed as a part of the address information generation process 14. The address transfer process 140 can transfer addresses from the operation items arranged on the first screen G100 to the operation items on the second screen G200.

[0063] (Address information is used as is)

[0064] Reference Figure 11 as well as Figure 12 The following describes the address information inheritance process 140. The address information inheritance process 140 corresponds to the "address inheritance source specifying unit" and the "address inheritance unit" in the claims.

[0065] The address information inheritance process 140 is executed when it is determined in step S13 that the value of the counter variable i is smaller than N and when it is determined in step S14 that the address inheritance source is designated.

[0066] In step S17, based on the component information within the screen, it is determined whether the component type of the source address transfer is the same as the component type of the target address transfer. If the component type of the source address transfer is different from the component type of the target address transfer, the process proceeds to step S22, where an error message is displayed and the routine ends. If the component types are the same, the process proceeds to step S18.

[0067] In step S18, based on the on-screen component information 131 of the first screen G100, it is determined whether the component from which the address is taken over has been assigned an address. If the component from which the address is taken over has not been assigned an address, the process proceeds to step S22. If the component from which the address is taken over has been assigned an address, the process proceeds to step S19.

[0068] In step S19 , the same address as that of the component at the address takeover source is allocated to the component at the address takeover destination. Figure 11 1 is a diagram showing an example of the screen component information 132 of the second screen G200 after the address information generation process 14 and the address use process 140 are executed. Figure 11 As shown, the same address as the address assigned to the component in the first screen G100 is assigned to the component in the second screen G200. When the address adoption process 140 is executed in the address information generation process 14, the address adoption source component name "G100_1PL2" is used to associate the address adoption source component with each component.

[0069] Next, the number of component names used in the address is substituted into variable k (step S20). Next, i + k is substituted into variable i (step S21), and the process returns to step S13. Address allocation processing 14 continues. If it is determined in step S13 that the value of counter variable i is greater than N, the process proceeds to step S23.

[0070] In step S23, as Figure 10 and Figure 11 As shown in FIG. 1 , the result of address allocation is added to the in-screen component information 131 and 132. Next, address use information is generated (step S24). Figure 12 This figure shows an example of address adoption information 142 generated after executing address adoption processing 140. Address adoption information 142 allows the component names of the address adoption source and the component names of the address adoption target to be stored in an associated manner. The process of step S24 corresponds to the "address adoption result generating means" in the claims. After step S24, this routine ends.

[0071] (Interface Information Generation Processing)

[0072] After the address allocation process 14 is completed, the interface information generation process 15 generates interface information 21 in a format that can be read by the SCADA web HMI execution device 3 based on the on-screen component information. The interface information 21 defines the relationship between the names and addresses of the various items of the operation signals sent from the SCADA web HMI execution device 3 to the supervisory control system (PLC) 4 and the display signals sent from the supervisory control system (PLC) 4 to the SCADA web HMI execution device 3.

[0073] (HMI screen data generation and processing)

[0074] The HMI screen data generation process 16 generates HMI screen data 22 in a format that can be read by the SCADA web HMI execution device 3 based on the arrangement information of each component generated by the component data generation process 12 .

[0075] The web HMI data 2, which includes the interface information 21 and HMI screen data 22 generated by the engineering tool 10, can be read by the SCADA web HMI execution device 3. Based on the web HMI data 2, the SCADA web HMI execution device 3 updates the display of HMI screens, such as the first screen G100 and the second screen G200. Specifically, the HMI screen display is updated based on the HMI screen data 22, which represents static information such as the shape, position, and size of components, and the values received from the PLC 4, which represent dynamic information. The interface information 21 defines the address information assigned to the display items and operation items of each component within the HMI screen.

[0076] <HMI Execution Device>

[0077] The processing of the HMI execution device 3 is implemented by Figure 2 the processing circuit shown. The processing circuit includes at least one processor 3a, a memory 3b, a display 3c, an input / output interface 3d, and a network interface 3e. The memory 3b stores programs recorded regarding the processing executed by the HMI execution device 3. The input / output interface 3d includes input devices such as a keyboard and a mouse, and a device capable of reading in web page HMI data 2 (interface information 21 and HMI screen data 22). The network interface 3e is a device connected to the monitoring and control system 4 and capable of transmitting and receiving signal data and control instructions. The processor 3a implements the following various processes of the HMI execution device 3 by executing the program read out from the memory 3b.

[0078] (Web Server)

[0079] The web server 31 reads in the web page HMI data 2. The web server 31 configures the interface information 21 and the HMI screen data 22 of the web page HMI data 2 as HMI web runtime content, and becomes a state capable of transmitting and receiving signals between the web browser 32 and the monitoring and control system (PLC) 4.

[0080] The processing of the HMI server runtime 311 operating on the web server 31 is as follows. That is, the HMI server runtime 311 incorporates an application server and supplies HMI web runtime content to the web browser 32. The HMI server runtime 311 communicates with the monitoring and control system 4 (PLC), and when the PLC signal received from the monitoring and control system 4 is a signal related to the HMI screen currently displayed on the web browser 32, it sends the PLC signal to the web browser 32. The HMI server runtime 311 sends the signal data from the monitored object device 7 to the HMI web runtime 321, and sends the control instruction from the HMI web runtime 321 to the monitoring and control system 4.

[0081] (Web Browser)

[0082] Refer to Figure 3The processing of the web browser 32 will be described below. The web browser 32 reads the web HMI data 2 (interface information 21 and HMI screen data 22) and displays the HMI screen for monitoring the factory. The HMI screen includes components (parts) that display the status of the monitored device 7 and components (parts) used to operate the monitored device 7 via the monitoring control system 4. The web browser 32 can display and update the HMI screen based on signals received from the monitoring control system (PLC) 4. The web browser 32 changes the appearance of the components configured on the HMI screen based on the value of the PLC signal received from the monitoring control system 4 via the web server 31.

[0083] The two-choice buttons 111 and 112 configured on the first screen G100 and the second screen G200 displayed as HMI screens operate based on the address information written into the interface information 21. For the two-choice buttons 111 and 112 configured on the first screen G100 and the second screen G200, common address information is defined for the operation signals from the HMI execution device 3 to the supervisory control system (PLC) 4, and the display signals from the supervisory control system (PLC) 4 to the SCADA web page HMI execution device 3, through the aforementioned address inheritance processing 140. Therefore, if PLC software corresponding to the two-choice button 111 on the first screen G100 is created, it is not necessary to create PLC software corresponding to the two-choice button 112 on the second screen G200, thereby reducing the work time of the PLC software designer.

[0084] As described above, according to this embodiment, the address allocation process 14 includes an address adoption process 140, which allows new components that perform the same processing as existing components to adopt and be assigned the same addresses as existing components. Therefore, there is no need to implement processing for activating new components in the PLC software; new components can be activated based on the addresses of existing components. Therefore, only the second screen G200 can be modified without changing the PLC software, reducing the designer's work time. Furthermore, the address area 41 used within the PLC 4 and the amount of data sent to and received by the PLC 4 can be kept to the necessary minimum.

[0085] While the above embodiments have been described, the present disclosure is not limited to the above embodiments and can be implemented with various modifications within the scope of the present disclosure. For example, in the above embodiments, the case of newly creating (adding) a second screen G200 in addition to the existing first screen G100 is described as an example, but the present disclosure can also be applied to the case of modifying the first screen G100 to create the second screen G200.

[0086] In the above embodiment, the example of manually entering all component names of the adopted address source is described. However, for example, a configuration may be employed in which the initial character "G" as part of the component name is manually entered, and multiple component names containing that character are displayed as candidates, from which selection can be made. This can reduce input errors compared to manual entry, and is particularly advantageous when there are many component names adopted from the source.

[0087] In the above embodiment, the drawing data in SVG format is used, but the format of the drawing data is not limited thereto. When the web browser 32 supports WebGL, the drawing data may also be in a format compatible with WebGL.

[0088] In the above embodiment, the HMI execution device 3 includes the web server 31 and the web browser 32 . However, a configuration may be adopted in which a plurality of client terminals are connected to the web server 31 and the web browser 32 is displayed on the display of each client terminal.

[0089] Description of Reference Numerals

[0090] 1…HMI design device, 1d…I / O interface (address inheritance source designation unit), 10…Engineering tool, 11…Drawing process, 12…Component data generation process, 13…In-screen component information generation process, 14…Address assignment process (address assignment unit), 140…Address inheritance process (address inheritance source designation unit, address inheritance unit), 142…Address inheritance information, 15…Interface information generation process, 16…HMI screen data generation process, 3…HMI execution device, 32…Web browser, 4…Monitoring control system (PLC), 41…Address area, 7…Monitored device, G100…First screen, Existing screen, HMI screen, 111…Two-choice button (existing component), G200…Second screen, New screen, HMI screen, 112…Two-choice button (new component).

Claims

1. A SCADA web HMI system capable of updating the display status of at least one component displayed on an HMI screen on a web browser based on a display signal corresponding to a signal received from a PLC, and sending an operation signal corresponding to an operation of the at least one component to the PLC, wherein: The SCADA web HMI system includes an HMI design device for creating a plurality of HMI screens, and the HMI design device includes an address allocation unit for allocating addresses to all components on the created HMI screens. The SCADA web HMI system has: The address inheritance source designation unit sets the existing HMI screen as the first screen, the added or modified HMI screen as the second screen, sets the component of the first screen as the existing component, and sets the component of the second screen as the new component, and designates the existing component as the address inheritance source for the new component as the address inheritance target; as well as The address inheriting unit inherits the address of the existing component to the new component if the address inheriting source designating unit designates the existing component as the address inheriting source of the new component, the new component is processed in the same manner as the existing component, and the address assigning unit has assigned an address to the existing component. The web browser displays the HMI screen, updates the display of the existing components of the first screen and the new components of the second screen based on a common display signal, and sends the operation signals corresponding to the operations of the existing components and the new components to the common address of the PLC.

2. The SCADA webpage HMI system according to claim 1, wherein: The existing components and the new components are display components that update the display states on the first screen and the second screen based on the display signal, or operation components that transmit the operation signal to the PLC.

3. The SCADA webpage HMI system according to claim 1 or 2, wherein: The SCADA web HMI system also has: The address transfer result generating unit generates address transfer information recording the component name of the existing component and the component name of the new component.

Images