HMI (Human Machine Interface) equipment system based on Web technology and development, deployment and operation method

Abstract

The invention provides an HMI (Human Machine Interface) equipment system based on a Web technology and a development deployment and operation method, and belongs to the technical field of industrial automation HMI. The method aims at solving the problems that traditional HMI development depends on a special client, deployment is complex, real-time interactivity is poor and maintenance is inconvenient. The system comprises an HMI integrated development platform and HMI equipment, the development and deployment method is executed by an HMI integrated development platform, provides a Web development environment, supports visual data variable definition and drag-and-drop interface design, and deploys a configuration file to an automatically discovered HMI device in a one-key manner after compiling; the operation method is executed by HMI equipment, communication with industrial equipment is established after a configuration file is analyzed, Web interface service is provided through a built-in embedded Web server, and real-time data active pushing is achieved based on the WebSocket technology. The system also supports remote maintenance. According to the invention, the lightweight and cross-platform development and deployment of the HMI are realized, the real-time performance of data interaction is improved, the equipment maintenance management is simplified, and the method is suitable for various industrial automation monitoring scenes.

Description

Technical Field

[0001] This invention relates to the field of industrial automation and human-machine interaction technology, and in particular to a human-machine interface (HMI) device system and development method based on Web technology. Background Technology

[0002] Human-Machine Interface (HMI) is a key component in industrial automation systems that enables information exchange between operators and machines. It connects operators to equipment, allowing for functions such as status monitoring, parameter setting, and alarm handling. Traditional HMI devices typically employ embedded systems and run dedicated, closed HMI software.

[0003] Traditional HMI system development typically relies on proprietary desktop software provided by specific vendors and tied to specific operating systems. This results in cumbersome development environments, difficulties in migration and efficient team collaboration, and poor cross-platform compatibility, as projects cannot be ported across different operating systems. Furthermore, limited by traditional development technologies, existing HMIs offer poor user interface experiences and weak data visualization capabilities, failing to meet the demands of modern industry for refined management. In terms of deployment and maintenance, traditional methods often require engineers to carry portable computers to the field and connect devices via cables for updates, a cumbersome and time-consuming process that can lead to production downtime. Simultaneously, limited remote access and maintenance methods prevent managers from monitoring equipment status anytime, anywhere, and hinder the ability to quickly obtain logs for remote diagnosis when equipment problems occur. Moreover, existing web-based HMIs lack container technology for edge device deployment, and lack a closed loop combining automatic device discovery and configuration file compilation and deployment.

[0004] Therefore, existing HMI systems generally suffer from problems such as high development and maintenance costs, poor cross-platform compatibility, fixed functions, complex deployment and maintenance, and limited access methods. Summary of the Invention

[0005] To address the shortcomings of existing technologies, the purpose of this invention is to provide a Web-based HMI device system and its development, deployment, and operation method, thereby solving the technical problems of existing HMI systems, such as limited development environment, weak cross-platform capabilities, poor user experience, cumbersome deployment and maintenance processes, and lack of remote access capabilities.

[0006] According to the present invention, an HMI project development and deployment method is executed by an HMI integration development platform and includes the following steps: A web-based development environment is provided for creating HMI projects, which includes defining data variables and designing user interfaces; Compile the HMI project into a configuration file that can be parsed by the target HMI device; Deploy the configuration file to the HMI device.

[0007] Preferably, the HMI integrated development platform is deployed based on container technology and accessed through a web browser.

[0008] Preferably, the defined data variables include the ability to map variables to data points of external industrial equipment by visually configuring the communication protocols, network parameters and register addresses associated with industrial equipment. It also supports the definition of discrete, analog, character and array variable types and the configuration of variable attributes, and supports batch import and export of variables through files. The user interface design is accomplished through a drag-and-drop visual editor that provides industrial-specific components, including dashboards and trend charts.

[0009] Preferably, the deployment is completed with a single click after selecting an automatically discovered HMI device in the network on the HMI integration development platform.

[0010] Preferably, it further includes: remotely maintaining the HMI device through a host computer communication service connection established between the HMI integrated development platform and the HMI device, wherein the remote maintenance includes obtaining the operation log of the HMI device or updating the firmware of the HMI device.

[0011] According to the present invention, an HMI device operation method is executed by an HMI device and includes the following steps: Receive and parse the configuration file generated according to the HMI project development and deployment method; The built-in real-time data service establishes a communication connection with the industrial equipment specified in the configuration file, reads and writes industrial equipment data according to the preset scanning cycle, processes the collected raw data through the built-in data processing service, makes real-time alarm judgments and generates alarm events based on variable alarm rules, and simultaneously stores historical data and alarm events locally. The user interface defined in the configuration file is provided as a web page through a built-in embedded web server for access by a web browser. The real-time data communication engine integrated into the embedded web server actively pushes the real-time data and alarm events processed by the data processing service to the web browser accessing the web page. Preferably, the real-time data communication engine is implemented based on WebSocket technology. After the browser loads the web page, it establishes a long WebSocket connection with the engine. Real-time data and alarm events are pushed to the browser in the form of data frames through this long connection. The engine has a heartbeat detection and disconnection reconnection mechanism.

[0012] According to the present invention, a Web-based HMI device system includes: The HMI integrated development platform is configured to execute the HMI project development and deployment method described above. The HMI integrated development platform includes a project management module, a data variable module, a visual editor module, and a compilation and deployment module. An HMI device is configured to execute the HMI device operation method, wherein the HMI device has built-in real-time data service, data processing service, embedded web server and host computer communication service.

[0013] Preferably, the HMI integrated development platform is deployed based on container technology, packaging applications, runtime dependencies, configuration files, and industrial protocol gateways into standardized container images, which can be deployed on various mainstream server operating systems and edge computing devices; The platform is configured to be accessible via a web browser.

[0014] Preferably, the host computer communication service of the HMI device establishes a persistent communication connection with the HMI integrated development platform based on WebSocket technology, which can periodically report the device's operating status information and support receiving remote maintenance instructions issued by the platform, and performing operations such as obtaining operating logs or updating firmware.

[0015] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention provides an integrated development platform based on Web and container technologies, which enables cross-platform compatibility of the development environment and collaborative team development, thereby reducing development and maintenance costs.

[0016] 2. This invention utilizes modern Web technology stack and real-time communication technology to enhance the user interface performance of HMI and the interactive experience of remote access.

[0017] 3. This invention enables agile deployment and online updates of functions by compiling the project into a configuration file and deploying it via a network with one click, thereby reducing production downtime.

[0018] 4. By integrating Web service capabilities and remote operation and maintenance channels into HMI devices, this invention enables flexible remote access and convenient remote maintenance, reducing the difficulty and cost of operation and maintenance. Attached Figure Description

[0019] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This invention provides a schematic diagram of the overall architecture of an HMI device system based on Web technology, as shown in an embodiment of the invention. Figure 2 This is a block diagram of the core service module inside the HMI device provided in an embodiment of the present invention. Detailed Implementation

[0020] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0021] Example 1 This embodiment provides a Web-based HMI device system and its corresponding development and operation method. For example... Figure 1 As shown, the system mainly includes an HMI integrated development platform and at least one HMI device. Developers or users can access the HMI integrated development platform via a standard web browser to develop, manage, and deploy HMI projects. Completed projects are then deployed to the HMI device located in the industrial field. The HMI device interacts with industrial equipment (such as programmable logic controllers, sensors, actuators, etc.) in real time via the network to monitor industrial processes. Simultaneously, the HMI device itself can also act as a web server, allowing developers or users to remotely access and operate it directly through a browser. Furthermore, the device can report its own operational status to the HMI integrated development platform for centralized remote maintenance and management.

[0022] In this embodiment, the development and deployment process of the HMI project begins with the deployment of the HMI integrated development platform. As an optional implementation, the HMI integrated development platform itself is packaged as a standardized container image, such as a Docker image. That is, the HMI integrated development platform is an integration platform developed based on web technology. Unlike traditional desktop software that relies on a specific operating system environment, this platform is based on Docker container technology, packaging core components such as applications, runtime dependencies, and configuration files into standardized container images. The containers have a built-in cloud-native industrial protocol gateway, enabling the platform to locate devices within the local area network and establish connections.

[0023] This approach decouples the platform deployment process from the underlying operating system. Specifically, administrators can install a container engine (such as Docker version 20.10) on a physical server or virtual machine running CentOS 7.9, and then quickly start the HMI integrated development platform service with a single command. This container-based deployment method not only simplifies the installation and deployment process but also achieves cross-platform compatibility. The same container image can be deployed on various mainstream server operating systems such as Windows Server, Ubuntu, CentOS, and Kylin, and even on resource-constrained edge computing devices without modification, thus greatly improving the flexibility and applicability of the solution.

[0024] Once the platform is deployed, developers and users do not need to install any dedicated client software on their local computers. Developers only need to enter the HMI integrated development platform's access address in the address bar of a modern web browser (such as Google Chrome, Mozilla Firefox, or Microsoft Edge) to access the platform's login interface. Understandably, this purely web-based access method eliminates many problems caused by inconsistent client software versions and poor operating system compatibility in traditional development models, enabling development teams to collaborate anytime, anywhere using computers with any mainstream operating system.

[0025] After logging into the platform, developers can use the various functional modules provided by the platform to create HMI projects. The HMI integrated development platform includes a project management module, a data variable module, a visual editor module, and a compilation and deployment module.

[0026] Specifically, the development process begins with creating a new project in the project management module. Taking the creation of a "Production Line 1 Monitoring System" as an example, the developer clicks the "New Project" button on the interface, enters the project name and description in the pop-up dialog box, and the system initializes an independent storage space and configuration environment for the project. The project management module also supports full lifecycle management of projects, including editing, deleting, copying, and archiving as templates. New projects do not need to start from scratch; templates can be reused and modified, shortening the project startup cycle. It supports assigning member permissions by project, and allows flexible configuration of read-only permissions, edit permissions, etc., ensuring project data security.

[0027] Next, the developer enters the data variable module to define and configure the data points required for the HMI project. This step builds a bridge between the backend industrial equipment (such as PLCs, sensors, and controllers) and the front-end user interface. In this embodiment, it is assumed that the industrial equipment to be monitored is a Siemens S7-1200 PLC. The developer first selects to add a new device connection in the device connection management interface of the data variable module, selects "Modbus TCP" as the protocol type, and enters the PLC's IP address "192.168.1.50" and port number "502" on the network. It should be noted that the platform has built-in support for various mainstream industrial communication protocols (such as Modbus TCP / RTU, OPC UA, EtherNet / IP, etc.). Developers do not need to write any low-level communication code; they can achieve accurate mapping between variables and external device data points simply through visual configuration.

[0028] This data variable module also supports the definition of various commonly used industrial variable types, such as discrete quantities, analog quantities, character types, and array types. Developers can customize attributes such as variable names, data ranges, units, and alarm thresholds. After the connection configuration is complete, developers can begin defining specific HMI variables. For example, the following variables can be created: 1. Variable name MotorSpeed, data type "floating-point", used to represent the real-time speed of the main conveyor motor. This variable is associated with the previously configured PLC connection, and its corresponding Modbus address is specified as holding register 40001. In addition, the unit "rpm", numerical range (0-3000), and high and low alarm thresholds (e.g., high alarm 2800, low alarm 100) can be set for this variable. 2. Variable name ValveStatus, data type "Boolean", used to represent the on / off state of the cooling water valve. This variable is associated with the PLC's coil register 00001. 3. Variable name ProductCount, data type "integer", used to accumulate the daily product output. This variable is associated with the PLC's holding register 40010. In addition, the data variable module supports batch import and export of variables via CSV files, which significantly improves the efficiency of configuring large numbers of variables.

[0029] Next, developers enter the visual editor module to design the user interface. This visual editor module, as the platform's "core creation unit," provides a visual editor that allows developers to quickly build professional-grade industrial HMI interfaces without requiring extensive front-end development experience. It mainly consists of three parts: a component library, a canvas, and a property bar. Developers can drag and drop the required interface elements from the component library located on the left side of the interface onto the canvas in the middle. The component library pre-installs a rich set of industrial-specific components, including basic controls (supporting custom colors, fonts, and styles), data visualization components (which can bind variables and display data changes in real time, such as trend charts displaying historical data curves), and industrial-specific components (such as icons for valves, pumps, motors, etc., supporting animation effect configuration). It also supports the development and import of custom components to meet the interface requirements of special scenarios. By binding variables defined in the data variable module to elements, components can respond to data changes in real time. For example, a developer drags a "dashboard" component onto the canvas. After selecting the dashboard component, the property bar on the right side of the interface will display all the component's configurable properties. In the data binding options in the properties panel, developers can select the variable `MotorSpeed` previously defined in the data variable module from the drop-down list. After binding, the pointer on the dashboard will reflect changes in motor speed in real time. Developers can also adjust the dashboard's range, scale, color, and other appearance styles in the properties panel. Similarly, developers can drag a "switch" component onto the canvas and bind its data source to the `ValveStatus` variable. To implement control functionality, event responses can be configured for this switch component: in the "click" event, by writing a simple script or configuring options, the opposite value (0 or 1) can be written to the `ValveStatus` variable when the switch state changes. The platform will automatically send this write request to the PLC via the configured communication protocol. Additionally, a "Data Display" text box component can be dragged and bound to the `ProductCount` variable to display cumulative production on the interface in real time. To implement historical data analysis, developers can drag a "Historical Trend Chart" component onto the canvas and add a curve to it in the properties panel; the data source for this curve is also bound to the `MotorSpeed` variable. By combining drag-and-drop, binding, and configuration, even engineers without a professional programming background can quickly build powerful and aesthetically pleasing HMI interfaces.

[0030] Once all interface designs and data bindings are complete, the developer clicks the "Compile" button in the top toolbar of the editor to launch the compilation and deployment module. The compilation and deployment module first performs a validity check on the entire project, such as checking for unbound variables or incomplete component property configurations, and generates a detection report. After successful verification, the module compiles and packages the entire HMI project, including device connection information, variable definitions, page layout, component properties, and event scripts, into a lightweight configuration file that can be parsed by the target HMI device. In one embodiment of this invention, this configuration file can be a JSON file, such as project.json. This design, which separates project logic from the runtime environment, is key to enabling dynamic definition and deployment of functions.

[0031] After compilation, developers can click the "Deploy" button. At this point, the compilation and deployment module will perform network discovery, automatically scanning and listing all online HMI devices on the current local area network. For example, the list might show "HMI-Device-01 (IP: 192.168.1.201)" located in the workshop. After selecting the target device, the developer clicks "One-Click Deployment." Correspondingly, the HMI integration development platform will securely push the previously generated project.json configuration file to the target HMI device via the network. The entire deployment process is visualized, displaying file transfer progress, device reception status, and project loading results.

[0032] At this point, the HMI project development and deployment methodology executed by the HMI integration development platform is complete. The following section will refer to the appendix... Figure 2 The operating method executed by the HMI device is described as follows: Once the HMI device receives the project.json configuration file pushed by the HMI integration development platform, its internal service modules begin to work collaboratively. Specifically, the HMI device first receives and parses the configuration file. Based on the device connection information in the file, the device establishes a communication connection with the target industrial equipment (i.e., the PLC with IP address 192.168.1.50 mentioned above) through its built-in real-time data service. The real-time data service includes a built-in high-precision timer scheduler. This scheduler periodically reads and writes the corresponding register addresses of the PLC via the Modbus TCP protocol according to the scan cycle defined for each variable in the configuration file (the user-preset scan cycle), thereby achieving efficient and reliable data exchange with the industrial site.

[0033] The collected raw data is then sent to the data processing service. This service performs a series of processing steps on the data, such as range conversion and filtering for analog quantities, or status checks for digital quantities. More importantly, the service performs real-time alarm checks based on the alarm rules defined for the variables in the configuration file (e.g., MotorSpeed>2800). Once an alarm is triggered, the data processing service generates an alarm event containing information such as alarm time, content, and level. Simultaneously, the service also includes a lightweight database (e.g., SQLite) to persistently store historical data (e.g., historical values ​​of MotorSpeed) and generated alarm events locally for use in querying historical trend charts or historical alarm lists.

[0034] The processed real-time data and alarm events are ultimately delivered to the embedded web server. The embedded web server is the core of HMI device 2's web-based access. This server runs continuously after the device starts up and listens on an HTTP port (e.g., port 80). When a developer or user accesses the HMI device's IP address (http: / / 192.168.1.201) through a browser, the embedded web server responds to the request and sends the dynamically rendered user interface (based on the project.json configuration file) to the browser as a standard web page (composed of HTML, CSS, and JavaScript).

[0035] To achieve real-time data updates, the embedded web server integrates a crucial real-time data communication engine. As an optional implementation, this engine is based on WebSocket technology. Once the browser loads the web page, the JavaScript code in the page establishes a long-lived WebSocket connection with the real-time data communication engine on the server. Subsequently, any real-time data changes processed by the data processing service (e.g., the MotorSpeed ​​value changing from 1500 to 1510) or newly generated alarm events will be actively and instantly pushed by the real-time data communication engine to all connected browser clients via this WebSocket connection in the form of data frames. Upon receiving the pushed data, the JavaScript on the browser side immediately updates the components bound to the interface; for example, the dashboard pointer will smoothly rotate, and the values ​​in the data display boxes will be refreshed accordingly. Understandably, this server-push-based model, compared to the traditional client-side polling model, reduces communication overhead and latency, thus providing users with a truly real-time interactive experience.

[0036] In addition, the HMI device also runs a host computer communication service. This service, also based on WebSocket technology, is responsible for establishing a persistent communication connection with the HMI integration development platform and periodically reporting its core status information to the platform, such as CPU utilization, memory usage, and connection status (normal or disconnected) with industrial equipment. This mechanism allows administrators to centrally monitor the health status of all deployed devices on the HMI integration development platform. Furthermore, this service also supports remote maintenance. For example, when a field device malfunctions, the administrator can send a command to the target HMI device to retrieve logs via this connection on the platform. Upon receiving the command, the host computer communication service will read the local system log file and send the contents back to the platform, thus achieving remote fault diagnosis. Similarly, when a new device firmware is released, the administrator can also initiate a firmware update command through the platform. The device will automatically download, verify, and install the update package; the entire process requires no on-site personnel and does not affect normal production monitoring.

[0037] In summary, this embodiment, through the collaborative work of the HMI integrated development platform and HMI devices, fully realizes a closed-loop solution from cloud development and networked deployment to real-time terminal operation and remote maintenance. This invention aligns with the trend of industrial automation towards lightweighting, cross-platform compatibility, and remote operation, providing core support for intelligent manufacturing. Example 2 This embodiment is applied to the high-temperature production environment of a hot rolling mill in steel. The HMI integrated development platform serves as a unified design and control center, located in the computer room or cloud; HMI devices are deployed on-site at the rolling mill control panel, coiling control room, etc., responsible for real-time monitoring of the roughing mill, finishing mill, and laminar flow cooling system.

[0038] Engineers created a "Hot Rolling Master Control" project on the HMI integrated development platform. First, in the data configuration phase, engineers defined a series of I / O points that would be collected or distributed later, mapping key process parameters such as "finishing mill exit temperature," "rolling force," and "strip speed" to specific DB block addresses in the PLC. Considering the unique characteristics of hot rolling, the platform pre-configured a library of graphics elements specific to the steel industry (such as diagrams of heating furnaces, descaling boxes, and mill stands), as well as a series of auxiliary components including trend charts and alarms. Engineers constructed a "rolling line panorama" by dragging and dropping, dynamically binding the previously configured I / O points to graphic element attributes to achieve real-time updates and displays of parameters such as temperature and speed, enabling complex animation logic: when the slab is extracted from the heating furnace, the corresponding rectangular graphic element on the screen begins to move following the PLC data, simulating the slab's conveying trajectory on the roller conveyor. Simultaneously, configurations can be made in the trend or alarm components to achieve data monitoring and anomaly alarms for hot rolling production.

[0039] After engineers complete the configuration and logical association of the full-line monitoring screens from steel tapping from the heating furnace, roughing, finishing and coiling transport chain on the HMI integrated development platform, they compile the entire hot rolling main control project and deploy it to specific HMI equipment terminals on site (such as the finishing mill control console HMI or the coiling control room HMI).

[0040] After receiving the project compilation file, the HMI device first performs a security verification, then parses the file and renders a high-fidelity monitoring screen consistent with the platform design. This includes a dynamic rolling line diagram, an animation simulating the movement of a red-hot slab, and a real-time temperature control curve for laminar flow cooling. Simultaneously, based on the preset L1-level basic automation PLC drive protocol (such as Siemens S7 or a proprietary high-speed protocol) in the configuration file, the HMI device establishes a high-real-time communication link with the field PLC. It reads key process data such as rolling force, stand speed, strip temperature, and coiling tension in real time with millisecond-level scan cycles and accurately pushes this data to the screen components. This ensures that the numerical fluctuations displayed on the screen perfectly match the actual movements of the on-site machinery, achieving real-time monitoring and precise intervention of the steel rolling production process.

[0041] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0042] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A method for developing and deploying an HMI project, executed by an HMI integrated development platform, characterized in that, Includes the following steps: A web-based development environment is provided for creating HMI projects, which includes defining data variables and designing user interfaces; Compile the HMI project into a configuration file that can be parsed by the target HMI device; Deploy the configuration file to the HMI device; The deployment is completed with a single click after selecting an automatically discovered HMI device in the network on the HMI integrated development platform.

2. The HMI project development and deployment method according to claim 1, characterized in that, The HMI integrated development platform is deployed based on container technology and accessed through a web browser.

3. The HMI project development and deployment method according to claim 1, characterized in that, The defined data variables include the ability to map variables to external industrial equipment data points by visually configuring the communication protocols, network parameters, and register addresses associated with industrial equipment. It also supports the definition of discrete, analog, character, and array variable types and the configuration of variable attributes, and supports batch import and export of variables via files.

4. The HMI project development and deployment method according to claim 1, characterized in that, The user interface design is accomplished through a drag-and-drop visual editor that provides industrial-specific components, including dashboards and trend charts.

5. The HMI project development and deployment method according to claim 1, characterized in that, Also includes: The HMI device is remotely maintained through a host computer communication service connection established between the HMI integrated development platform and the HMI device. The remote maintenance includes obtaining the operating logs of the HMI device or updating the firmware of the HMI device.

6. A method for operating an HMI device, executed by an HMI device, characterized in that, Includes the following steps: Receive and parse the configuration file generated by the method according to any one of claims 1-5; The built-in real-time data service establishes a communication connection with the industrial equipment specified in the configuration file, reads and writes industrial equipment data according to the preset scanning cycle, processes the collected raw data through the built-in data processing service, makes real-time alarm judgments and generates alarm events based on variable alarm rules, and simultaneously stores historical data and alarm events locally. The user interface defined in the configuration file is provided as a web page through a built-in embedded web server for access by a web browser. The real-time data communication engine integrated into the embedded web server actively pushes the real-time data and alarm events processed by the data processing service to the web browser accessing the web page.

7. The HMI device operation method according to claim 6, characterized in that, The real-time data communication engine is implemented based on WebSocket technology. After the browser loads the web page, it establishes a long WebSocket connection with the engine. Real-time data and alarm events are pushed to the browser in the form of data frames through this long connection. The engine has a heartbeat detection and disconnection reconnection mechanism.

8. A Web-based HMI device system, characterized in that, include: An HMI integrated development platform is configured to execute the HMI project development and deployment method according to any one of claims 1 to 5, wherein the HMI integrated development platform includes a project management module, a data variable module, a visual editor module, and a compilation and deployment module; An HMI device is configured to perform the HMI device operation method as described in claim 6 or 7, wherein the HMI device has built-in real-time data service, data processing service, embedded web server and host computer communication service.

9. The HMI device system based on Web technology according to claim 8, characterized in that, The HMI integrated development platform is deployed based on container technology, packaging applications, runtime dependency libraries, configuration files and industrial protocol gateways into standardized container images, which can be deployed on a variety of mainstream server operating systems and edge computing devices. The platform is configured to be accessible via a web browser.

10. The HMI device system based on Web technology according to claim 8, characterized in that, The host computer communication service of the HMI device establishes a persistent communication connection with the HMI integrated development platform based on WebSocket technology. It can periodically report the device's operating status information and support receiving remote maintenance instructions issued by the platform, as well as performing operations such as obtaining operating logs or updating firmware.

Images