CN112639642A - SCADA network HMI server device - Google Patents
SCADA network HMI server device Download PDFInfo
- Publication number
- CN112639642A CN112639642A CN202080004662.XA CN202080004662A CN112639642A CN 112639642 A CN112639642 A CN 112639642A CN 202080004662 A CN202080004662 A CN 202080004662A CN 112639642 A CN112639642 A CN 112639642A
- Authority
- CN
- China
- Prior art keywords
- name
- screen
- hmi
- plug
- plc signal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims abstract description 44
- 230000008569 process Effects 0.000 claims abstract description 43
- 230000008859 change Effects 0.000 claims abstract description 22
- 238000000605 extraction Methods 0.000 claims abstract description 13
- 238000012545 processing Methods 0.000 claims description 52
- 238000012544 monitoring process Methods 0.000 claims description 15
- 239000000284 extract Substances 0.000 abstract description 19
- 238000004891 communication Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 12
- 101100190617 Arabidopsis thaliana PLC2 gene Proteins 0.000 description 6
- 101100408456 Arabidopsis thaliana PLC8 gene Proteins 0.000 description 6
- 101100464304 Caenorhabditis elegans plk-3 gene Proteins 0.000 description 6
- 101100093534 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) RPS1B gene Proteins 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000009467 reduction Effects 0.000 description 3
- 101100285426 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) HMI1 gene Proteins 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 229910000831 Steel Inorganic materials 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004886 process control Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 239000010959 steel Substances 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
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
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM]
- G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS], computer integrated manufacturing [CIM] characterised by the network communication
-
- 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
-
- 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/30—Nc systems
- G05B2219/33—Director till display
- G05B2219/33139—Design of industrial communication system with expert system
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- General Engineering & Computer Science (AREA)
- Manufacturing & Machinery (AREA)
- Quality & Reliability (AREA)
- Programmable Controllers (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A browser-based HMI server apparatus is speeded up. An HMI terminal (20) that executes a web browser (21) and a PLC (2) are connected to an HMI server device (10). The HMI server device (10) is provided with a change PLC signal extraction process (16) and a browser display update process (18). A varying PLC signal extraction process (16) extracts a varying PLC signal name and a varying PLC signal value of a varying PLC signal. A browser display update process (18) extracts a screen name and a plug-in name associated with a PLC signal name identical to a changed PLC signal name from screen information (13), extracts a browser name associated with the extracted screen name from browser information (15), and transmits update data including the extracted plug-in name and the changed PLC signal value to an executing web browser (21) corresponding to the extracted browser name.
Description
Technical Field
The present invention relates to a SCADA Web HMI server (SCADA Web HMI server) apparatus for operating a SCADA HMI on a Web browser (Web browser).
Background
Scada (supervisory Control And Data acquisition) is known as a mechanism for monitoring And controlling a social infrastructure system. The social infrastructure system includes a steel rolling system, a power transmission and transformation system, a sewer treatment system, a building management system, a road system, and the like.
SCADA is a type of industrial control system that performs computer-based system monitoring and process control. In SCADA, adaptability (real-time property) matching the processing performance of the system is required.
SCADA is generally composed of the following subsystems.
(1)HMI(Human Machine Interface)
The HMI is a mechanism that presents data of a target process (monitoring target device) to an operator so that the operator can monitor and control the process. For example, patent document 1 discloses a SCADA HMI provided with an HMI screen that operates on a SCADA client.
(2) Monitoring control system
The supervisory control system collects signal data on the process and sends control commands to the process. The system is composed of a Programmable Logic Controller (PLC) and the like.
(3) Remote Input/Output device (Remote Input Output: RIO)
The remote input/output device is connected to a sensor provided in the process, converts a signal of the sensor into digital data, and transmits the digital data to the supervisory control system.
(4) Communication Infrastructure (Communication Infrastructure)
The communication infrastructure connects the supervisory control system with the remote input output devices.
Documents of the prior art
Patent document
Patent document 1: japanese patent laid-open publication No. 2017-27211
Disclosure of Invention
Technical problem to be solved by the invention
The SCADA client in patent document 1 operates by a high-performance computer capable of executing the supervisory control logic. In addition, in the case where a plurality of SCADA clients are provided, it is necessary to prepare a high-performance computer of the SCADA client station and to separately install the monitoring control logic. In addition, even when the SCADA client has a multi-monitor configuration, it is necessary to install a monitor control logic for each HMI screen displayed on the monitor. Therefore, cost reduction of the SCADA HMI is desired.
To achieve cost reduction of SCADA HMI, the present inventors developed a browser-based HMI subsystem. By performing the network application programming of the monitoring control logic in the server, there is no need to install a separate monitoring control logic in the client terminal (network terminal). The client terminal may display only the result of the monitoring control logic processed by the server on the web browser. Therefore, the client terminal may be a computer with a low specification of the degree of operation of the web browser. For example, even a portable terminal such as a tablet computer can monitor and control the system. This enables a configuration in which a plurality of client terminals and a server are connected to each other at low cost. In addition, a network terminal that does not include the monitoring control logic is called a thin client.
However, in plant monitoring, it is necessary to process PLC signals up to several tens of thousands of points at high speed and reflect them on an HMI screen. Therefore, a browser-based HMI subsystem is expected to be speeded up.
The present invention has been made to solve the above-mentioned problems. The invention aims to provide a SCADA network HMI server device which reduces data processing amount and accelerates signal processing.
Means for solving the problems
In order to achieve the above object, the SCADA network HMI server apparatus of the present invention is configured as follows.
The SCADA network HMI server device is connected with a Human Machine Interface (HMI) terminal and a Programmable Logic Controller (PLC). The HMI terminal executes at least one web browser that displays an HMI screen configured with a plug-in that displays the status of the plant. And the SCADA network HMI server device sends updating data for updating the state of the plug-in according to the PLC signal received from the PLC.
The SCADA network HMI server device includes at least one processor and a memory storing a program. The program, when executed by the at least one processor, causes the at least one processor to execute a process including the following process.
The screen information management process manages screen information obtained by associating a screen name of the HMI screen, a plug-in name of the plug-in disposed on the HMI screen, and a PLC signal name of the PLC signal for changing a state of the plug-in.
The browser information management process manages browser information obtained by associating a browser name of an executing web browser with the screen name of the HMI screen displayed in the executing web browser.
The PLC signal extracting process receives a plurality of PLC signals from the PLC, and extracts a PLC signal name and a PLC signal value of a PLC signal having a variation among the plurality of PLC signals.
The browser display update processing extracts the screen name and the plug-in name associated with the same PLC signal name as the changed PLC signal name from the screen information, extracts a browser name associated with the extracted screen name from the browser information, and transmits the update data including the extracted plug-in name and the changed PLC signal value to the executing web browser corresponding to the extracted browser name.
In a preferred aspect, the screen information management processing reads in a first screen device list, a second screen device list, and a derived device list. The first screen device list is information obtained by associating a first screen name of a first HMI screen, a first plug-in name of a first plug-in arranged on the first HMI screen, and a first PLC signal name of a PLC signal for changing a state of the first plug-in. The second screen device list is information obtained by associating at least a second screen name of a second HMI screen with a second plugin name of a second plugin disposed on the second HMI screen. The derived device list is information obtained by associating the second plug-in name with the first plug-in name of the first plug-in that affects the state of the second plug-in.
Further, the screen information management processing reads these device lists, and adds first screen information, second screen information, and additional screen information to the screen information. The first screen information is information obtained by associating the first screen name, the first plug-in name, and the first PLC signal name. The second screen information is information obtained by associating at least the second screen name with the second plug-in name. The additional screen information is information obtained by associating the second screen name, the first plug-in name linked to the second plug-in name via the derived device list, and the first PLC signal name of the first screen device list associated with the first plug-in name.
In the browser display update process, when the changed PLC signal name is the same as the first PLC signal name, the update data including the first plug-in name and the changed PLC signal value is transmitted to the on-execution web browser that is displaying the second HMI screen.
Further, the executing web browser that is displaying the second HMI screen receives the update data including the changed PLC signal value of the first PLC signal that changes the state of the first plugin. Then, the executing web browser inputs the change PLC signal value of the first PLC signal to a script (script) predetermined for a change in the state of the second plug-in, and changes the state of the second plug-in based on an operation result of the script.
Effects of the invention
According to the present invention, the SCADA HMI server apparatus transmits update data only to the web browser that is executing to display an HMI screen in which a plug-in corresponding to a PLC signal that has been changed is arranged. That is, the HMI server 10 may perform signal processing only for PLC signals that have changed among the received PLC signals. Therefore, the data processing amount can be greatly reduced. The update data is transmitted not in units of HMI terminals but in units of web browsers. Therefore, when a plurality of web browsers are executed on one HMI terminal, the update data is transmitted only to the executing web browser that is displaying the HMI screen on which the plug-in related to the update data is arranged. As a result, the data processing amount of the HMI terminal can be reduced without performing processing in the web browser unrelated to the update data.
According to the present invention, it is possible to reduce the cost of network application programming by the HMI subsystem and to increase the speed by reducing the data processing amount.
Drawings
Fig. 1 is a diagram for explaining a system configuration of a SCADA in embodiment 1 of the present invention.
Fig. 2 is a block diagram for explaining the configuration of the SCADA network HMI server apparatus according to embodiment 1 of the present invention.
Fig. 3 is a diagram showing an example of a device list read into the SCADA HMI server apparatus according to embodiment 1 of the present invention.
Fig. 4 is a diagram for explaining an example of signal processing of the SCADA network HMI server apparatus according to embodiment 1 of the present invention.
Fig. 5 is a block diagram for explaining the configuration of the SCADA network HMI server apparatus according to embodiment 2 of the present invention.
Fig. 6 is a diagram showing an example of a device list and a derived device list read in the SCADA HMI network server apparatus according to embodiment 2 of the present invention.
Fig. 7 is a diagram for explaining an example of signal processing of the SCADA network HMI server apparatus according to embodiment 2 of the present invention.
Fig. 8 is a block diagram showing an example of a hardware configuration of the HMI terminal and the network HMI server.
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. However, in the embodiments described below, when the number, the amount, the range, and the like of each element are mentioned, the present invention is not limited to the mentioned number except for the case where the number is specifically and explicitly indicated and the case where the number is obviously specified in principle. The structure and the like described in the embodiments shown below are not necessarily essential to the present invention, unless otherwise specifically indicated or clearly specified in principle. In addition, the same reference numerals are given to the common elements in the drawings, and redundant description is omitted.
< integral Structure >
Fig. 1 is a diagram for explaining a system configuration of SCADA. The SCADA includes a Human Machine Interface (HMI)1, a Programmable Logic Controller (PLC)2 as a supervisory control system, a communication device 3 as a communication infrastructure, and an RIO4 as subsystems. The SCADA is connected to the monitoring target apparatus 5 via the PLC2 or the RIO 4.
The PLC2 (supervisory control system), the communication device 3 (communication infrastructure), and the RIO4 are not described in the background art. The monitoring target device 5 is a sensor, an actuator, or the like constituting a plant that monitors a control target.
The HMI1(SCADA network HMI system) includes a SCADA network HMI server device 10 (hereinafter referred to as HMI server device 10) and at least one HMI terminal 20.
The HMI server apparatus 10 is connected to the PLC2 via a computer network. The HMI server apparatus 10 is connected to the HMI terminal 20 via a computer network. The HMI server 10 may be connected to a plurality of HMI terminals 20. When there is no need to distinguish between the HMI terminals, only the HMI terminal 20 is described.
The HMI terminal 20 is a thin client terminal that does not include a monitoring control logic, and executes at least one web browser 21. The web browser 21 displays an HMI screen on which a plug-in for displaying the status of the plant is arranged. Specifically, the HMI terminal 20 includes at least one monitor (display 20e in fig. 8). A web browser 21 is displayed on a monitor in a full screen. When the HMI terminal 20 has a plurality of monitors, the web browser 21 is displayed on each monitor in a full screen. That is, the HMI terminal 20 executes a plurality of web browsers 21.
The HMI server apparatus 10 executes an HMI server application 11. The HMI server application 11 has a web server function for communicating with the HMI terminal 20 and an I/O server function (application server function) for communicating with the PLC 2. The HMI terminal 20 executes a web browser 21. The HMI1 as an execution environment operates as a web application in which a Script (for example, Java Script (registered trademark)) operating on the web browser 21 and the HMI server application 11 coordinate with each other.
The HMI server apparatus 10 transmits update data for updating the state of the plug-in to the web browser 21 in accordance with the PLC signal received from the PLC 2. The HMI server apparatus 10 receives a control command from the web browser 21 and transmits it to the PLC 2.
< SCADA network HMI Server device >
With reference to the examples shown in fig. 2 and 3, a characteristic process of the HMI server application 11 operating in the HMI server device 10 according to embodiment 1 will be described.
In fig. 2, the HMI server 10 is connected to an HMI terminal a (20A) and an HMI terminal B (20B). The HMI terminal a includes a first monitor and a second monitor. The HMI terminal B includes a third monitor. On the first monitor, browser a1 is displayed in full screen (21a 1). On the second monitor, browser a2 is displayed in full screen (21a 2). On the third monitor, browser B1 is displayed in full screen (21B 1). In fig. 2, the browser a1 displays the HMI screen G1, the browser a2 displays the HMI screen G2, and the browser B1 displays the HMI screen G3, but the HMI screens displayed by the respective web browsers can be freely changed by an operation of an operator. In the case where there is no need to distinguish between the web browsers, it is simply referred to as a web browser 21.
As shown in fig. 8, the HMI server 10 includes at least one processor 10a and a memory 10b storing a program. The program is executed by the processor 10a, thereby causing the processor 10a to execute processes including the following respective processes.
The HMI server application 11 generates a communication target for communicating with the web browser 21 and a communication target for communicating with the PLC at the start thereof.
Then, the HMI server application 11 reads the screen data 31 of the HMI screen on which the plug-in is arranged and the device list 32 at the start thereof.
The screen data 31 is vector data defined for each HMI screen. As an example, the Vector data is data in the Scalable Vector Graphics (SVG) format. The SVG data includes, as attributes of SVG elements, the name, shape, position, color, and size of a plug-in to be placed on the HMI screen. The file name of the picture data 31 includes a picture name.
The device list 32 is data defined for each HMI screen. As an example, the data is in Comma-Separated Values (CSV) format. The device list 32 includes, as fields, a plug-in name (item name), a type, a comment, an output PLCID, a PLC address, and a communication address (fig. 3). The plug-in name is, for example, a name obtained by combining a screen name and a device number in the screen. Further, the name may be a combination of plug-in types. Each plug-in name is a name inherent in the HMI 1. The file name of the device list 32 includes a screen name.
In addition, the HMI server application 11 generates the content of each HMI screen based on the read screen data 31 and device list 32. The content includes SVG data and picture information. The HMI server application 11 transmits content corresponding to an HMI screen requested from the web browser 21 to the web browser 21. The web browser 21 receives the content and displays the HMI screen.
The HMI server application 11 stores the PLC signal received from the PLC2 in the PLC signal status information 17. The PLC signal state information 17 stores information obtained by associating a PLC signal name of a received PLC signal with a PLC signal value. The PLC signal name is, for example, a name obtained by combining the PLC address and the output PLCID in fig. 3. Each PLC signal name is a name unique to the HMI 1.
The screen information management process 12 manages screen information 13 in which a screen name of an HMI screen, a card name of a card placed on the HMI screen, and a PLC signal name of a PLC signal for changing a state of the card are associated with each other.
The screen information 13 is generated based on the device list 32 defined for each HMI screen. In fig. 3, as examples of the device list 32, a G1 device list 32a on the HMI screen G1, a G2 device list 32b on the HMI screen G2, and a G3 device list 32c on the HMI screen G3 are described. Fig. 3 shows screen information 13 generated based on these device lists.
The browser information management processing 14 manages the browser information 15 in which the browser name of the executing web browser 21 and the screen name of the HMI screen displayed by the executing web browser 21 are associated with each other. That is, the displayed HMI screen is managed not by the HMI terminal but by the browser (monitor unit). The browser name is a name obtained by combining an HMI terminal name and a monitor number (browser number). Each browser name is a name unique to the HMI 1.
In fig. 2, the browser information management process 14 manages, as the browser information 15, information in which the browser name (a1) of the web browser 21a1 under execution is associated with the screen name (G1), information in which the browser name (a2) of the web browser 21a2 under execution is associated with the screen name (G2), and information in which the browser name (B1) of the web browser 21B1 under execution is associated with the screen name (G3).
The browser information 15 is updated, for example, when the web browser 21 is started, when the web browser 21 is ended, or when an HMI screen displayed by the web browser 21 is shifted to another HMI screen.
The varied PLC signal extraction process 16 receives a plurality of PLC signals from the PLC2, and extracts a signal name (varied PLC signal name) and a signal value (varied PLC signal value) of a PLC signal that has been varied among the plurality of PLC signals.
Specifically, the changed PLC signal extraction process 16 compares the value (previous value) of each PLC signal stored in the PLC signal state information 17 with the value (present value) of each PLC signal received this time, and determines whether there is a change. The changed PLC signal extraction process 16 extracts a signal name (changed PLC signal name) and a signal value (changed PLC signal value) of the changed PLC signal when there is a change.
The browser display updating process 18 extracts, from the screen information 13, a screen name and a plug-in name associated with the same PLC signal name as the changed PLC signal name extracted by the changed PLC signal extracting process 16.
Further, the browser display update processing 18 extracts a browser name associated with the extracted screen name from the browser information 15.
Further, the browser display update process 18 transmits update data including the extracted plug-in name and the extracted changed PLC signal value to the executing web browser 21 corresponding to the extracted browser name.
According to the browser display update process 18, the transmitted update data is only data related to the PLC signal having a change. Therefore, the data amount is extremely small. The update data is transmitted to the running web browser 21 in a limited manner while the HMI screen on which the plug-in corresponding to the changed PLC signal is placed is being displayed. Therefore, the update data is not sent to the web browser that does not need to be updated.
< HMI terminal >
The web browser 21 in execution designated as the transmission destination by the browser display update processing 18 receives the update data. The web browser 21 changes the state (numerical value, color, shape, position) of the plug-in corresponding to the plug-in name included in the update data according to the changed PLC signal value.
When a plurality of web browsers are operating in the HMI terminal 20, the update data is processed only by the web browser 21 that is displaying the HMI screen on which the plug-in related to the update data is arranged. Therefore, the web browser 21 unrelated to the update data does not perform processing, and the data processing amount of the HMI terminal 20 is reduced. The HMI terminal 20 is a computer with a low specification of the degree of operation of the web browser 21 due to the reduction of the data processing amount. For example, even a portable terminal such as a tablet computer can monitor and control the system.
< flow of Signal processing >
The flow of signal processing in embodiment 1 will be described with reference to an example shown in fig. 4.
Fig. 4 is a diagram for explaining a process of updating the state of the plug-in G1_1 arranged on the screen G1 of the browser a1 in accordance with the PLC signal P1_1 from the PLC 2. P1_1 is a name obtained by combining the PLC address (1) and the output PLCID (P1) in the G1 device list 32a in fig. 3.
In step S1, the changed PLC signal extraction process 16 receives a plurality of PLC signals (P1_1, P2_1, P3_1) from the PLC 2.
In step S2, the changed PLC signal extraction process 16 compares the value (previous value) of each PLC signal stored in the PLC signal state information 17 with the value (present value) of each PLC signal received this time, and determines whether there is a change. The changed PLC signal extraction process 16 extracts a changed PLC signal name and a changed PLC signal value of the changed PLC signal when there is a change. In the example of fig. 4, the PLC signal with the change is P1_ 1.
In step S3, the HMI server application 11 updates the PLC signal value corresponding to the PLC signal name (P1_1) stored in the PLC signal state information 17 with the present value.
In step S4, the browser display updating process 18 extracts, from the screen information 13, the screen name (G1) and the plug-in name (G1_1) associated with the PLC signal name (P1_1) that is the same as the extracted change PLC signal name.
In step S5, the browser display updating process 18 extracts the browser name (a1) associated with the extracted screen name (G1) from the browser information 15.
In step S6, the browser display update process 18 transmits update data including the extracted plug-in name (G1_1) and the extracted changed PLC signal value to the communication partner communicating with the executing web browser corresponding to the extracted browser name (a 1).
In step S7, the update data is sent to the browser a1 via the communication object.
Thereafter, the browser A1 receives the update data, and changes the state of the plug-in G1_1 according to the changed PLC signal value. For example, the display color of plug-in G1_1 changes.
As described above, the HMI server 10 in embodiment 1 transmits update data only to the running web browser 21 that is displaying the HMI screen on which the plug-in corresponding to the changed PLC signal is arranged. That is, the HMI server 10 may perform signal processing only for PLC signals having a change in the received PLC signals. Therefore, the data processing amount can be greatly reduced. The update data is transmitted not in units of HMI terminals but in units of web browsers. Therefore, when a plurality of web browsers 21 are executed on one HMI terminal, the update data is transmitted only to the executing web browser 21 that is displaying the HMI screen on which the plug-in related to the update data is arranged. As a result, the web browser 21 unrelated to the update data does not perform processing, and the data processing amount of the HMI terminal 20 can be reduced.
However, the processing at the time of startup of the web browser 21 and at the time of HMI screen transition of the web browser 21 is as follows. First, when the web browser 21 is started up or when the HMI screen of the web browser 21 is migrated, information of a newly opened HMI screen is transmitted from the browser (for example, 21a1) to the HMI server application 11, and based on this, the HMI server application 11 updates the browser information 15. Next, the HMI server application 11 extracts a PLC signal necessary for the HMI screen using the screen information 13. Next, the HMI server application 11 acquires a PLC signal value necessary for the HMI screen from the PLC signal status information 17, and transmits the value to the browser.
Next, embodiment 2 of the present invention will be described with reference to examples shown in fig. 5 to 7.
The HMI server apparatus 10 in embodiment 1 described above executes a process of transmitting update data only to the web browser 21 that is displaying a plug-in associated with a changed PLC signal. The above-described screen information 13 is required in this processing. The screen information 13 is generated based on the device list 32 defined for each HMI screen. The device list 32 is information obtained by associating screen names of the HMI screen, plug-in names (item names) of the plugs arranged on the HMI screen, and PLC signal names of PLC signals for directly changing the states of the plugs. In principle, the inherent plug-in names defined in the device list 32 are associated with the inherent PLC signal names.
However, the state of a plug-in placed on one HMI screen may be affected by the state of a plug-in placed on another HMI screen. For example, when a signal value of a first PLC signal corresponding to a first plug-in placed on a first HMI screen satisfies a specific condition, a use state of a second plug-in placed on a second HMI screen may be changed from disable (invalid) to enable (valid). Such processing is important as security processing for improving the security of plug-in operation.
In this case, the second plug-in is arranged on the second HMI screen, but the first plug-in is not arranged. Therefore, the device list of the second HMI screen in which the first plugin is not arranged does not include information obtained by associating the first plugin name with the first PLC signal name. Additionally, the first plug-in is directly related to the first PLC signal and the second plug-in is only indirectly related. Therefore, the device list of the second HMI screen does not include information obtained by associating the second plug-in name with the first PLC signal name. Therefore, the update data relating to the first plug-in is not transmitted to the web browser on which the second HMI screen on which the second plug-in is arranged is displayed. Therefore, according to the configuration for speeding up described in embodiment 1, there is a technical problem that the above-described security processing cannot be realized.
In embodiment 2, a derived device list is imported to cope with such a situation,
< SCADA network HMI Server device >
With reference to the examples shown in fig. 5 and 6, a description will be given of characteristic processing of the HMI server application 11 operating in the HMI server 10 in embodiment 2.
The configuration shown in fig. 5 is the same as the configuration in fig. 2, except that a derived device list 33 is added, and screen information management processing 12a is provided instead of the screen information management processing 12.
The screen information management process 12a manages screen information 13 in which a screen name of an HMI screen, a card name of a card placed on the HMI screen, and a PLC signal name of a PLC signal for changing a state of the card are associated with each other. The PLC signal name is, for example, a name obtained by combining the PLC address and the output PLCID in fig. 6. Each PLC signal name is a name unique to the HMI 1.
The screen information 13 is generated based on the device list 32 and the derived device list 33 defined for each screen. Fig. 6 shows, as examples of the device list 32, a G1 device list 32a on the HMI screen G1, a G2 device list 32b on the HMI screen G2, a G4 device list 32d on the HMI screen G4, and a derived device list 33. Fig. 6 shows screen information 13 generated based on the device list 32 and the derivative device list 33.
A method of generating screen information 13 based on the device list 32 and the derived device list 33 will be described with reference to an example shown in fig. 6.
First, the screen information management process 12a reads in the first screen device list (G1 device list 32a, G2 device list 32b), the second screen device list (G4 device list 32d), and the derived device list 33.
The first screen device list is configured by information obtained by associating a first screen name of the first HMI screen, a first plug-in name of a first plug-in arranged on the first HMI screen, and a first PLC signal name of a first PLC signal for changing a state of the first plug-in. For example, the G1 device list 32a in fig. 6 includes information obtained by associating the first screen name (G1), the first card name (G1_1), and the first PLC signal name (P1_ 1). Here, the first PLC signal name corresponds to a name obtained by combining the output PLCID and the PLC address.
The second screen device list is configured by information obtained by associating at least a second screen name of the second HMI screen with a second plugin name of a second plugin disposed on the second HMI screen. Preferably, the second screen device list includes information obtained by associating a second screen name of the second HMI screen, a second plugin name of a second plugin disposed on the second HMI screen, and a second PLC signal name of a second PLC signal for changing a state of the second plugin, as in the first screen device list. Here, the second PLC signal name corresponds to a name obtained by combining the output PLCID and the PLC address.
For example, the G4 device list 32d in fig. 6 includes information obtained by associating the second screen name (G4), the second card name (G4_1), and the second PLC signal name (P4_ 1). Here, the second PLC signal name corresponds to a name obtained by combining the output PLCID and the PLC address.
The derived device list 33 is link information for linking information of one device list 32 with information of the other device list 32. The derived device list 33 is information obtained by associating the second plug-in name with the first plug-in name of the first plug-in that affects the state of the second plug-in. Information linking such plug-ins to each other is not contained in the second screen device list. In the example of fig. 6, the derived device list 33 includes information obtained by associating the second plug-in name (G4_1) with the first plug-in name (G1_ 1). The file name of the derived device list 33 includes a screen name.
The screen information management processing 12a reads the device list 32 and the derivative device list 33, and adds the first screen information, the second screen information, and the additional screen information to the screen information 13.
The first screen information is information obtained by associating the first screen name, the first plug-in name, and the first PLC signal name.
The second screen information is information obtained by associating at least the second screen name and the second plug-in name. Preferably, the second screen information is information obtained by associating the second screen name, the second plug-in name, and the second PLC signal name, as in the first screen information.
The additional screen information is information obtained by associating a second screen name defined in the second screen device list, a first plug-in name linked to the second plug-in name via the derived device list 33, and a first PLC signal name of the first screen device list associated with the first plug-in name. In fig. 6, the screen information 13 includes additional screen information in which the second screen name (G4) of the G4 device list 32d, the first plug-in name (G1_1) linked to the second plug-in name (G4_1) via the derived device list 33, and the first PLC signal name (P1_1) of the G1 device list 32a associated with the first plug-in name (G1_1) are associated with each other.
In this way, the screen information management processing 12a copies the information of the first plug-in (G1_1) that affects the state of the second plug-in (G4_1) of the second HMI screen (G4) from the first screen device list (G1 device list 32a) using the derived device list 33.
The browser display updating process 18 extracts, from the screen information 13, a screen name and a plug-in name associated with the same PLC signal name as the changed PLC signal name extracted by the changed PLC signal extracting process 16.
Further, the browser display update processing 18 extracts the browser name associated with the extracted screen name from the browser information 15.
Further, the browser display update processing 18 transmits update data including the extracted plug-in name and the extracted changed PLC signal value to the executing web browser corresponding to the extracted browser name.
According to such processing, the browser display update processing 18 transmits the update data including the first plug-in name (G1_1) and the changed PLC signal value to the executing web browser (B1) that is displaying the second HMI screen (G4) when the changed PLC signal name is the same as the first PLC signal name (P1_ 1).
< HMI terminal >
The web browser (B1) receives update data including a change PLC signal value of the first PLC signal (P1_1) for changing the state of the first plugin (P1_1) while the second HMI screen (G4) is being displayed. Then, the on-the-fly web browser (B1) inputs the change PLC signal value of the first PLC signal (P1_1) to a script predetermined for the state change of the second plug-in (G4_1), and changes the state of the second plug-in (G4_1) based on the operation result of the script.
For example, the script of the second plug-in (G4_1) is a program for changing the use state of the second plug-in (G4_1) from disable to enable when the changed PLC signal value of the first PLC signal (P1_1) is a value indicating a specific browser name and the value matches the browser name of the web browser (G4) under execution.
The running web browser (a1) is the same as that of embodiment 1, and therefore, its description is omitted.
< flow of Signal processing >
The flow of signal processing in embodiment 2 will be described with reference to an example shown in fig. 7.
Fig. 7 is a diagram for explaining a process of updating the state of the plug-in G1_1 arranged on the screen G1 of the browser a1 and updating the use state of the plug-in G4_1 arranged on the screen G4 of the browser B1 in accordance with the PLC signal P1_1 from the PLC 2. The plug G1_1 and the plug G1_2 disposed on the screen G1 are buttons that can be selected only from one of them, and the plug G1_1 is selected.
In step S1, the changed PLC signal extraction process 16 receives a plurality of PLC signals (P1_1, P2_1, P3_1) from the PLC 2.
In step S2, the changed PLC signal extraction process 16 compares the value (previous value) of each PLC signal stored in the PLC signal state information 17 with the value (present value) of each PLC signal received this time, and determines whether there is a change. The changed PLC signal extraction process 16 extracts a changed PLC signal name and a changed PLC signal value of the changed PLC signal when there is a change. In the example of fig. 7, the PLC signal with the change is P1_ 1.
In step S3, the HMI server application 11 updates the PLC signal value corresponding to the PLC signal name (P1_1) stored in the PLC signal state information 17 with the present value.
In step S4, the browser display updating process 18 extracts, from the screen information 13, screen names (G1, G4) and plug-in names (G1_1) that are associated with the same PLC signal name (P1_1) as the extracted change PLC signal name.
In step S5, the browser display update processing 18 extracts the browser names (a1, B1) associated with the extracted screen names (G1, G4) from the browser information 15.
In step S6, the browser display update process 18 transmits update data including the extracted plug-in name (G1_1) and the extracted changed PLC signal value to the communication partner communicating with the executing web browser corresponding to the extracted browser name (a 1).
In step S7, the update data is sent to the executing web browser a1 via the communication object.
Thereafter, the browser A1 receives the update data, and changes the state of the plug-in G1_1 according to the changed PLC signal value. For example, the display color of plug-in G1_1 changes.
After the process of step S5, in step S8, the browser display update process 18 transmits update data including the extracted plug-in name (G1_1) and the extracted changed PLC signal value to the communication partner communicating with the executing web browser corresponding to the extracted browser name (B1).
In step S9, the update data is transmitted to the executing web browser via the communication object (B1).
Thereafter, the web browser (B1) receiving the update data including the changed PLC signal value of the first PLC signal (P1_1) changing the state of the first plug-in (P1_1) while the second HMI screen (G4) is being displayed.
Then, the executing web browser (B1) inputs the changed PLC signal value of the first PLC signal (P1_1) to a script predetermined for the state change of the second plug-in (G4_ 1). The script is a program for changing the use state of the second plug-in (G4_1) from disable to enable when the changed PLC signal value of the first PLC signal (P1_1) is a value indicating the browser name (B1) and the value matches the browser name of the web browser (B1) under execution.
The executing web browser (B1) changes the state of the second plug-in (G4_1) based on the operation result of the script that sets the change PLC signal value as the input value. In the example of fig. 7, the lock release condition is satisfied, and the use state of the second plug-in (G4_1) is changed from disable (invalid) to enable (valid).
As described above, according to the HMI server apparatus 10 and the HMI terminal 20 in embodiment 2, the state of a plug in a certain HMI screen can be changed according to the state of a plug in another screen. Therefore, according to the system of embodiment 2, the above-described security processing can be realized while adopting the configuration for speeding up described in embodiment 1. Further, by using the derived device list 33, information of the linked device list can be copied and added to the screen information, so that the design job can be made efficient.
< example of hardware Structure >
Fig. 8 is a block diagram showing an example of the hardware configuration of the HMI server 10 and the HMI terminal 20.
The above-described processes of the HMI server 10 are realized by a processing circuit. The processing circuit is configured by connecting a processor 10a, a memory 10b, and a network interface 10 c. The processor 10a realizes each function of the HMI server 10 by executing various programs stored in the memory 10 b. The network interface 10c is a device that is connected to the PLC2 and the HMI terminal 20 via a computer network and can transmit and receive PLC signals and control commands.
The above-described processes of the HMI terminal 20 are realized by a processing circuit. The processing circuit is formed by connecting a processor 20a, a memory 20b, a network interface 20c, an input interface 20d and at least one display 20 e. The processor 20a realizes each function of the HMI terminal 20 by executing various programs stored in the memory 20 b. The network interface 20c is connected to the HMI server 10 and is capable of transmitting and receiving PLC signals and control commands. The input interface 20d is an input device such as a keyboard, a mouse, or a touch panel. A plurality of displays 20e may be provided. The HMI terminal 20 may be a portable terminal such as a tablet pc.
While the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present invention.
Description of the reference numerals
1 HMI
2 PLC
3 communication device
4 RIO
5 monitoring object device
10 HMI server device
10a processor
10b memory
10c network interface
11 HMI server application
12. 12a Picture information management processing
13 picture information
14 browser information management processing
15 browser information
16-change PLC signal extraction process
17 PLC Signal State information
18 browser display update processing
20. 20A, 20B HMI terminal
20a processor
20b memory
20c network interface
20d input interface
20e display
21. 21a1, 21a2, 21b1 web browser
31 picture data
32. 32a, 32b, 32c, 32d device list
33 derive a device list.
Claims (3)
1. An SCADA network HMI server apparatus, which is a data acquisition and monitoring control network human machine interface server apparatus, connected to an HMI terminal and a Programmable Logic Controller (PLC), and transmitting update data for updating a state of a plug-in according to a PLC signal received from the PLC, the HMI terminal executing at least one web browser that displays a Human Machine Interface (HMI) screen in which a plug-in displaying a state of a plant is arranged, the SCADA network HMI server apparatus comprising:
at least one processor; and
a memory for storing a program, wherein the program is stored in the memory,
the program is executed by the at least one processor to cause the at least one processor to perform a process comprising:
a screen information management process of managing screen information in which a screen name of the HMI screen, a plug-in name of the plug-in arranged on the HMI screen, and a PLC signal name of the PLC signal for changing a state of the plug-in are associated with each other;
a browser information management process of managing browser information in which a browser name of an executing web browser and the screen name of the HMI screen displayed in the executing web browser are associated with each other;
a varied PLC signal extraction process of receiving a plurality of PLC signals from the PLC and extracting a varied PLC signal name and a varied PLC signal value of a PLC signal varied among the plurality of PLC signals; and
and a browser display update process of extracting the screen name and the plug-in name associated with a PLC signal name identical to the changed PLC signal name from the screen information, extracting the browser name associated with the extracted screen name from the browser information, and transmitting the update data including the extracted plug-in name and the changed PLC signal value to the executing web browser corresponding to the extracted browser name.
2. A SCADA network HMI server apparatus according to claim 1,
the screen information management processing reads a first screen device list, a second screen device list, and a derived device list, adds additional screen information to the screen information,
the first screen device list is obtained by associating a first screen name of a first HMI screen, a first plug-in name of a first plug-in arranged on the first HMI screen, and a first PLC signal name of a first PLC signal for changing the state of the first plug-in,
the second screen device list is obtained by associating at least a second screen name of a second HMI screen with a second plug-in name of a second plug-in configured on the second HMI screen,
the derived device list is obtained by associating the second plug-in name with the first plug-in name of the first plug-in that affects the status of the second plug-in,
the additional screen information is obtained by associating the second screen name, the first plug-in name linked to the second plug-in name via the derived device list, and the first PLC signal name of the first screen device list associated with the first plug-in name,
the browser display update processing transmits the update data including the first plug-in name and the changed PLC signal value to an executing web browser that is displaying the second HMI picture, when the changed PLC signal name is the same as the first PLC signal name.
3. A SCADA network HMI server apparatus according to claim 2,
an executing web browser that is displaying the second HMI screen,
receiving the update data including the changed PLC signal value of the first PLC signal that changes the state of the first card,
and inputting the change PLC signal value of the first PLC signal to a script predetermined for a state change of the second card, and changing the state of the second card based on an operation result of the script.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2019137202A JP7245742B2 (en) | 2019-07-25 | 2019-07-25 | SCADA web HMI server device |
| JP2019-137202 | 2019-07-25 | ||
| PCT/JP2020/027141 WO2021015022A1 (en) | 2019-07-25 | 2020-07-10 | Scada web hmi server device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112639642A true CN112639642A (en) | 2021-04-09 |
Family
ID=74193951
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202080004662.XA Pending CN112639642A (en) | 2019-07-25 | 2020-07-10 | SCADA network HMI server device |
Country Status (5)
| Country | Link |
|---|---|
| JP (1) | JP7245742B2 (en) |
| CN (1) | CN112639642A (en) |
| PH (1) | PH12021550355A1 (en) |
| TW (1) | TWI761886B (en) |
| WO (1) | WO2021015022A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4084435A1 (en) * | 2021-04-27 | 2022-11-02 | OMRON Corporation | Diagnosing and/or controlling an industrial controller |
| US20230259087A1 (en) | 2021-06-10 | 2023-08-17 | Toshiba Mitsubishi-Electric Industrial Systems Corporation | Scada web hmi system |
| JP7464196B2 (en) | 2021-06-10 | 2024-04-09 | 東芝三菱電機産業システム株式会社 | SCADA Web HMI System |
| CN116034338A (en) * | 2021-07-07 | 2023-04-28 | 东芝三菱电机产业系统株式会社 | SCADA webpage HMI system |
| CN116710865A (en) | 2021-12-27 | 2023-09-05 | 东芝三菱电机产业系统株式会社 | SCADA webpage HMI client device and SCADA webpage HMI system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002108600A (en) * | 2000-10-02 | 2002-04-12 | Digital Electronics Corp | Terminal device for control system and recording medium and control system |
| JP2006099258A (en) * | 2004-09-28 | 2006-04-13 | Digital Electronics Corp | Editor unit, program for enabling computer to function as editor unit, recording medium storing same program, control system and indicator unit |
| US20080168092A1 (en) * | 2007-01-10 | 2008-07-10 | General Electric Company | Systems and methods for turbine control simulation |
| CN101361031A (en) * | 2006-01-24 | 2009-02-04 | 株式会社东芝 | Factory control system and interlock reason confirming method |
| JP2014132489A (en) * | 2014-03-10 | 2014-07-17 | Bank Of Tokyo-Mitsubishi Ufj Ltd | Online system, program creation device and screen control program creation device |
| CN104412243A (en) * | 2012-06-26 | 2015-03-11 | 三菱电机株式会社 | Equipment management system and program |
| CN108667861A (en) * | 2017-03-28 | 2018-10-16 | 比亚迪股份有限公司 | By browser to the method, system and server of device real-time monitoring |
| CN109862064A (en) * | 2018-11-22 | 2019-06-07 | 中国铁建重工集团有限公司 | A kind of configuration method and device for equipment remote monitoring |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3748232B2 (en) * | 2002-03-20 | 2006-02-22 | 株式会社デジタル | Data transmission device, display device, and control system |
| US20040260404A1 (en) * | 2003-06-23 | 2004-12-23 | Russell Thomas C. | Method and apparatus for self-configuring supervisory control and data acquisition (SCADA) system for distributed control |
| US7904181B2 (en) * | 2004-06-01 | 2011-03-08 | Ils Technology Llc | Model for communication between manufacturing and enterprise levels |
| JP2006072442A (en) * | 2004-08-31 | 2006-03-16 | Digital Electronics Corp | Control system |
| JP5656912B2 (en) * | 2012-05-07 | 2015-01-21 | 三菱電機株式会社 | Monitoring control system display device and monitoring control system |
| TW201531058A (en) * | 2014-01-28 | 2015-08-01 | Univ Nat Formosa | Equipment room environment monitoring system |
| TW201531653A (en) * | 2014-02-12 | 2015-08-16 | Univ Nat Formosa | Cloud monitoring and regulating system of water heater |
| JP6157548B2 (en) * | 2015-09-25 | 2017-07-05 | 株式会社コンテック | Surveillance image creation device, creation program, and creation method |
| US20180059921A1 (en) * | 2016-09-01 | 2018-03-01 | Honeywell International Inc. | Custom gui control for visualizing field data |
| CN109906413A (en) * | 2016-11-10 | 2019-06-18 | 三菱电机株式会社 | Information display device, information display system and display control method |
-
2019
- 2019-07-25 JP JP2019137202A patent/JP7245742B2/en active Active
-
2020
- 2020-07-10 WO PCT/JP2020/027141 patent/WO2021015022A1/en active Application Filing
- 2020-07-10 CN CN202080004662.XA patent/CN112639642A/en active Pending
- 2020-07-20 TW TW109124429A patent/TWI761886B/en active
-
2021
- 2021-02-19 PH PH12021550355A patent/PH12021550355A1/en unknown
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002108600A (en) * | 2000-10-02 | 2002-04-12 | Digital Electronics Corp | Terminal device for control system and recording medium and control system |
| JP2006099258A (en) * | 2004-09-28 | 2006-04-13 | Digital Electronics Corp | Editor unit, program for enabling computer to function as editor unit, recording medium storing same program, control system and indicator unit |
| CN101361031A (en) * | 2006-01-24 | 2009-02-04 | 株式会社东芝 | Factory control system and interlock reason confirming method |
| US20080168092A1 (en) * | 2007-01-10 | 2008-07-10 | General Electric Company | Systems and methods for turbine control simulation |
| CN104412243A (en) * | 2012-06-26 | 2015-03-11 | 三菱电机株式会社 | Equipment management system and program |
| JP2014132489A (en) * | 2014-03-10 | 2014-07-17 | Bank Of Tokyo-Mitsubishi Ufj Ltd | Online system, program creation device and screen control program creation device |
| CN108667861A (en) * | 2017-03-28 | 2018-10-16 | 比亚迪股份有限公司 | By browser to the method, system and server of device real-time monitoring |
| CN109862064A (en) * | 2018-11-22 | 2019-06-07 | 中国铁建重工集团有限公司 | A kind of configuration method and device for equipment remote monitoring |
Non-Patent Citations (1)
| Title |
|---|
| 江克猛;: "单机版WinCC6.2在连铸机HMI中的应用", 可编程控制器与工厂自动化, no. 09 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021015022A1 (en) | 2021-01-28 |
| TWI761886B (en) | 2022-04-21 |
| PH12021550355A1 (en) | 2021-10-04 |
| TW202115552A (en) | 2021-04-16 |
| JP7245742B2 (en) | 2023-03-24 |
| JP2021022071A (en) | 2021-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112639642A (en) | SCADA network HMI server device | |
| CN102073448B (en) | For the method and apparatus of the data that Dynamic Announce is associated with Process Control System | |
| US11595468B2 (en) | Data capture on a serial device | |
| US11619924B2 (en) | Combined visualization thin client HMI system and method | |
| US20160149861A1 (en) | Firewall with Application Packet Classifier | |
| EP2246758A2 (en) | Electronic operator interface based controller and device automatic downloads | |
| CN101211171A (en) | Plant control system, monitoring operation device, and plant monitoring program | |
| ITMI20071074A1 (en) | "AUTOMATED SYSTEM FOR TEXTILE MACHINE CONTROL" | |
| CN111417907A (en) | Method and apparatus for creating and managing intelligent programmable logic controller solutions | |
| CN114080593A (en) | SCADA webpage HMI system and HMI client | |
| CN112166389A (en) | Hybrid rendering HMI terminal device | |
| US20200150613A1 (en) | Method and device for operating and controlling a machine installation by means of a graphical development interface and generation of a field bus configuration | |
| JP2015090548A (en) | Control device | |
| JP6575311B2 (en) | Network system and control device | |
| JP7478925B2 (en) | SCADA Web HMI Client Device and SCADA Web HMI System | |
| CN113641350A (en) | Software development environment providing system, method, and non-transitory computer-readable medium | |
| KR20050086185A (en) | Home appliance network system and its operating method | |
| JP7468784B2 (en) | SCADA Web HMI Client Device and SCADA Web HMI System | |
| JP2012050275A (en) | Digital protection control device | |
| EP4224311A1 (en) | Protocol driver creating device | |
| CN108415701B (en) | Information processing apparatus and system, user interface creation method, and storage medium | |
| CN117121436A (en) | Control system, processing apparatus, and control method | |
| TW202303306A (en) | Scada web hmi system | |
| CN115812184A (en) | SCADA webpage HMI system | |
| CN115941818A (en) | Method for analyzing and controlling hot loading industrial control protocol and system with same |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |