SCADA (Supervisory Control And Data Acquisition) system interface point rerouting method, system, equipment, medium and product

Abstract

The invention discloses an SCADA (supervisory control and data acquisition) system interface point rerouting method, system, equipment, medium and product, and relates to the field of SCADA systems, the method comprises the following steps: in each HMI (human machine interface) of an SCADA system, respectively receiving a pre-configured variable redirection script for binding two preset logic point identifiers, the picture logic point identifier is directly associated with the picture element in the current HMI interface and is not directly associated with the physical equipment monitored by the SCADA system, and the equipment logic point identifier is opposite; when a trigger instruction for the variable redirection script of any HMI interface is received, after it is detected that the logic point identifier of the current picture is bound with the logic point identifiers of other devices, the binding relation is unbound; and binding the unbound current picture logic point identifier and the unbound current equipment logic point identifier so as to complete redirection of the picture elements and the physical equipment in the HMI interface. The expansibility of the system is improved.

Description

Technical Field

[0001] This application relates to the field of SCADA systems, and in particular to a SCADA system interface point rerouting method, system, device, medium and product. Background Technology

[0002] In modern industrial automated production systems, SCADA systems are the core hub for realizing production process monitoring, equipment control, and data management. HMI interfaces, as the direct carrier for operators to interact with physical equipment (such as motors, sensors, robots, conveyor lines, etc.), directly determine the operating efficiency and adjustment costs of the production line through their development quality and adaptability.

[0003] Currently, the development of HMI interfaces and device associations for SCADA systems in the industry generally adopts a "hard binding" model. This means that during the development phase, the operation controls on the HMI interface are directly associated with the hardware addresses of specific physical devices (such as device unique identifiers, register addresses, and variable names). However, the existing SCADA system's HMI interface is hard-bound to the physical device address. When adding a new device, a separate HMI operation and display interface needs to be developed for it, which takes an average of 3-5 person-days per device, resulting in poor system scalability. Summary of the Invention

[0004] The purpose of this application is to provide a SCADA system interface point rerouting method, system, device, medium and product that can improve system scalability.

[0005] To achieve the above objectives, this application provides the following solution: In a first aspect, this application provides a SCADA system interface point rerouting method, the method comprising: In each HMI interface of the SCADA system, a pre-configured variable redirection script is received. The variable redirection script is configured to bind two preset logical point identifiers. The screen logical point identifier is directly associated with the screen element in the current HMI interface, but not directly associated with the physical device monitored by the SCADA system. The device logical point identifier is directly associated with the physical device monitored by the SCADA system, but not directly associated with the screen element in the current HMI screen. After binding the two logical point identifiers, the operation on the screen element in the current HMI interface corresponding to the screen logical point identifier is equivalent to the operation on the physical device associated with the device logical point identifier. When a trigger instruction is received for the variable redirection script for any HMI interface, after detecting that the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound together, the binding relationship is unbound, and the unbound current screen logical point identifier and current device logical point identifier are bound together to complete the redirection of screen elements in the HMI interface to the physical device. Output the redirected HMI interface.

[0006] Secondly, this application provides a SCADA system interface point rerouting system, the system comprising: The receiving module is used to receive pre-configured variable redirection scripts in each HMI interface of the SCADA system. The variable redirection scripts are configured to bind two preset logical point identifiers. The screen logical point identifier is directly associated with the screen element in the current HMI interface, but not directly associated with the physical device monitored by the SCADA system. The device logical point identifier is directly associated with the physical device monitored by the SCADA system, but not directly associated with the screen element in the current HMI screen. After binding the two logical point identifiers, the operation on the screen element in the current HMI interface corresponding to the screen logical point identifier is equivalent to the operation on the physical device associated with the device logical point identifier. The processing module is used to, when receiving a trigger instruction for the variable redirection script for any HMI interface, after detecting that the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound together, unbind the binding relationship, and bind the unbound current screen logical point identifier and the current device logical point identifier together to complete the redirection of screen elements in the HMI interface to the physical device. The output module is used to output the redirected HMI interface.

[0007] Thirdly, this application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the SCADA system interface point rerouting method described in any one of the above.

[0008] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the SCADA system interface point rerouting method described in any one of the above descriptions.

[0009] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the SCADA system interface point rerouting method described above.

[0010] According to the specific embodiments provided in this application, the following technical effects are disclosed: This application provides a SCADA system interface point rerouting method, system, device, medium, and product. This disclosure uses a pre-configured variable redirection script to bind screen logic points associated only with HMI interface elements to device logic points associated only with physical devices. When a command is triggered, the old binding can be dynamically unbound and a new binding established. This breaks the rigid limitations of traditional hard-coded binding between the interface and device, allowing flexible switching of associations without code modification. It also achieves dynamic redirection that takes effect immediately upon triggering (no downtime required, ensuring monitoring continuity). Furthermore, the pre-configured script lowers the operational threshold (non-developers can perform independent operation and maintenance), while ensuring that interface operations are equivalent to device operations. Ultimately, this improves the flexibility, response efficiency, and ease of operation and maintenance of the SCADA system interface and device association, ensuring the accuracy and security of industrial control. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating a SCADA system interface point rerouting method according to an exemplary embodiment; Figure 2 This is a process diagram of a fire pump room in a SCADA system interface, illustrated according to an exemplary embodiment. Figure 3 This is a wastewater treatment process diagram in the SCADA system interface according to an exemplary embodiment; Figure 4 This is a schematic diagram of a variable redirection script in a SCADA system interface according to an exemplary embodiment; Figure 5 This is a schematic diagram of the functional modules of a SCADA system interface point rerouting system according to an exemplary embodiment; Figure 6 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0013] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0014] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0015] Figure 1 This is a flowchart illustrating a SCADA system interface point rerouting method according to an exemplary embodiment, such as... Figure 1 As shown, the method includes the following steps S101-S103: In step S101, each HMI interface of the SCADA system receives a pre-configured variable redirection script. The variable redirection script is configured to bind two preset logical point identifiers. The screen logical point identifier is directly associated with the screen element in the current HMI interface, but not directly associated with the physical device monitored by the SCADA system. The device logical point identifier is directly associated with the physical device monitored by the SCADA system, but not directly associated with the screen element in the current HMI screen. After binding the two logical point identifiers, the operation on the screen element in the current HMI interface corresponding to the screen logical point identifier is equivalent to the operation on the physical device associated with the device logical point identifier.

[0016] HMI (Hardware Management Interface) is a visual interface in a SCADA system where operators interact directly. It is used to monitor equipment status and issue control commands, such as the unit monitoring interface in a power plant and the pump control interface in a water plant.

[0017] Screen elements are the smallest visual units in an HMI interface that carry display / operation functions. They are the direct objects through which operators interact with the system. Common types include: Display types: numerical display boxes (e.g., "Water pump outlet pressure: 0.8MPa"), indicator lights (e.g., "Green light for operation / Red light for fault"), trend graphs (e.g., "Temperature change within 1 hour"); Operational controls include: control buttons (such as "start / stop button"), drop-down selection boxes (such as "pump group switching: 1# / 2#"), and sliding regulators (such as "valve opening: 0-100%)).

[0018] The VarRedir script defines the binding relationship between two logical point identifiers (LPIDs), for example: VarRedir(screen logical point identifier, device logical point identifier). The screen logical point identifier is only bound to HMI screen elements (such as the "motor start button" or "temperature display screen" on the HMI) and does not directly connect to any physical device. For example, screen logical point identifier = LPID100 is bound to the "conveyor belt control button" on the HMI, but it doesn't know which conveyor belt it controls. The device logical point identifier is only bound to physical devices (such as "conveyor belt #3" or "temperature sensor #5" in a factory) and does not directly connect to any HMI screen elements. For example, device logical point identifier = LPID200 is bound to the physical address of conveyor belt #3 (such as register address 0x0025), and it does not correspond to any HMI screen element itself.

[0019] Once two LPIDs are bound, operations on HMI screen elements associated with the screen logical point identifier (such as clicking the conveyor belt control button) are equivalent to operations on physical devices associated with the device logical point identifier (such as controlling the start of conveyor belt number 3).

[0020] The operation on the HMI screen element corresponding to the screen logical point identifier includes at least one of the following operations: reading the physical device operating parameters, writing the control command to the physical device, and switching the working mode of the physical device.

[0021] When configuring the current HMI interface, users can write multiple VarRedir scripts to the current HMI interface in batches, for example: VarRedir(LPID1,LPID2); VarRedir(LPID3,LPID4); VarRedir(LPID5,LPID6); In this context, LPID1, LPID3, and LPID5 represent screen logical point identifiers, while LPID2, LPID4, and LPID6 represent device logical point identifiers. LPID1 points to LPID2, LPID3 points to LPID4, LPID5 points to LPID6, and so on. These VarRedir scripts logically constitute a virtual global routing table.

[0022] The VarRedir scripts here are executable code snippets specific to SCADA systems, which are written and configured in advance by engineers during the project configuration phase.

[0023] The script only contains binding rules for two sets of logical point identifiers (LPIDs) and does not contain specific device control code (such as motor starting voltage parameters). You can switch the controlled object by modifying the LPID binding in the script later without rewriting the script itself.

[0024] In step S102, when a trigger instruction for the variable redirection script for any HMI interface is received, after detecting that the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound together, the binding relationship is unbound, and the unbound current screen logical point identifier and current device logical point identifier are bound together to complete the redirection of screen elements in the HMI interface to physical devices.

[0025] In one embodiment, the variable redirection (VarRedir) script is sent by a preset trigger control on the HMI interface, such as... Figure 2 As shown, there are two HMI interfaces: one for the fire pump room and the other for the sewage treatment. When the virtual button "Fire Pump Room" is clicked, the trigger command for the variable redirection script of the fire pump room HMI interface is received. When the virtual button "Sewage Treatment" is clicked, the trigger command for the variable redirection script of the sewage treatment HMI interface is received.

[0026] The operator triggers a preset trigger control on the HMI interface. Clicking this button is the "trigger instruction for the variable redirection script".

[0027] After receiving the trigger command of the variable redirection script, the system needs to check whether the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound. If they are bound, the binding relationship between the current screen logical point identifier and other device logical point identifiers is unbound. After unbinding, the unbound current screen logical point identifier and the current device logical point identifier are bound together to complete the redirection of screen elements in the HMI interface to the physical device. If the current screen logical point identifier and other device logical point identifiers are not bound together, the current screen logical point identifier and the current device logical point identifier are bound together directly.

[0028] For example, the current variable redirection (VarRedir) script triggered by the trigger command is: VarRedir(LPID1, LPID2). When the system receives this trigger command, it first checks whether the current screen logical point identifier LPID1 in the current variable redirection script is bound to other device logical point identifiers (excluding LPID2). If they are bound, the binding relationship between the current screen logical point identifier LPID1 and other device logical point identifiers is unbound. After unbinding, the unbound current screen logical point identifier LPID1 and the current device logical point identifier LPID2 are bound together to complete the redirection of screen elements in the HMI interface to physical devices. If the current screen logical point identifier LPID1 and other device logical point identifiers are not bound together, the current screen logical point identifier LPID1 and the current device logical point identifier LPID2 are bound together directly. In this way, LPID1 can control the physical device corresponding to LPID2.

[0029] It is worth noting that the association between screen elements and screen logical point identifiers in the HMI interface will not change, and the association between LPID2 and physical devices will also not change.

[0030] In one embodiment, detecting the binding of the current screen logical point identifier and other device logical point identifiers in the current variable redirection script includes: Detect whether the current screen logical point identifier is a database point; If the current screen logical point identifier is a database point, then the current screen logical point identifier in the current variable redirection script is bound to other device logical point identifiers.

[0031] In practical applications of SCADA (Supervisory Control and Data Acquisition) systems, variable redirection scripts play a crucial role in establishing data links between control logic and physical devices. Logic point identifiers are the key mapping carriers that associate scripts with databases and physical devices. Specifically, when the system detects that a screen logic point identifier in the current variable redirection script has been bound (especially after detecting that the screen logic point identifier already exists in the SCADA system database), it needs to perform an unbinding operation according to a preset procedure. For example, it first pauses the data read / write link associated with the logic point identifier to avoid data loss or script execution errors during the unbinding process, and then clears the binding mapping relationship between the database and the logic point identifier.

[0032] In one possible implementation, during redirection, it checks whether the current screen logical point identifier is a database point. If it is a database point, it assumes the current screen logical point identifier is already bound to another physical device, and then unbinds it. It then checks if the format of the current device logical point identifier matches the database point format. If it does, it checks if the current device logical point identifier exists in the screen process. If it does, it queries the database to see if the current device logical point identifier is saved. If it doesn't exist, it creates the current device logical point identifier in the screen process. After creation, it queries the database to see if the current device logical point identifier is saved. If the database saves the current device logical point identifier, it returns the ID corresponding to the saved identifier and sends the ID to the system. The system binds the current screen logical point identifier to the current device logical point identifier. During runtime, the screen element corresponding to the current screen logical point identifier points to the ID of the current device logical point identifier in the database. Then, the database looks up the corresponding physical device based on the ID. Thus, the screen element corresponding to the current screen logical point identifier points to the physical device corresponding to the current device logical point identifier. If the database does not save the current device logical point identifier, the process ends, and the redirection fails.

[0033] In step S103, the redirected HMI interface is output.

[0034] In the redirected HMI interface, since the current screen logical point identifier and the current device logical point identifier are bound, the screen element corresponding to the current screen logical point identifier in the HMI interface points to the physical device corresponding to the current device logical point identifier.

[0035] This disclosure uses a pre-configured variable redirection script to bind screen logic points that are only associated with HMI interface elements to device logic points that are only associated with physical devices. When a command is triggered, the old binding can be dynamically unbound and a new binding can be established. This breaks the rigid limitation of traditional hard-coded binding between the interface and the device, allowing flexible switching of associations without modifying the code. It also achieves dynamic redirection that takes effect immediately upon triggering (without downtime, ensuring monitoring continuity). Furthermore, the pre-configured script lowers the operational threshold (non-developers can perform independent operation and maintenance), while ensuring that interface operations are equivalent to device operations. Ultimately, this improves the flexibility, response efficiency, and ease of operation and maintenance of the SCADA system interface and device association, ensuring the accuracy and security of industrial control.

[0036] In one embodiment, each screen element in the HMI interface corresponds to a screen logic point identifier.

[0037] When configuring logical point identifiers for each screen element in the HMI interface, click the screen element to be configured on the HMI canvas (e.g., the pressure display box for pump #1), ensuring the element is selected (usually a selection border or anchor point will appear around the element); bring up the attribute panel of the screen element through the menu bar (e.g., attribute options) or right-click menu (e.g., element attributes) of the design tool (the panel usually contains category labels such as appearance data association events); in the attribute panel, find the configuration category related to data association (some tools directly label it as logical point or tag association), and locate the core configuration item, logical point identifier point number or association identifier (the naming may vary slightly between different tools, but the function is the same); in the input box of logical point identifier, enter the identifier code that conforms to the system's preset naming rules (e.g., following the rule of functional domain + device number + data type, entering PMP_01_P represents the pressure of pump #1); if the system has a preset logical point library, you can also directly select an existing identifier through the drop-down option of the input box to reduce manual input errors; click the OK or Apply button in the attribute panel to save the configuration, and the configuration is complete.

[0038] In one embodiment, the above method further includes the following steps A1-A3: A1. Receive a new HMI interface generation instruction; the HMI interface generation instruction includes screen elements in the HMI interface.

[0039] When users (such as SCADA system maintenance personnel and process managers) have a need to add a new HMI interface (for example, when new production line equipment is added to the plant or the original monitoring dimensions are expanded, a new interface is needed to achieve visual management), they can trigger the new HMI interface generation command through the "New Interface" function of the HMI design tool.

[0040] This instruction does not only contain a request to "create an interface," but also includes the screen elements to be included in the new HMI interface, that is, the physical devices to which the new HMI interface will be associated.

[0041] A2. Generate a new HMI interface that includes screen elements.

[0042] After receiving instructions from A1, the HMI design tool will generate a visual representation of the new interface based on the screen elements.

[0043] A3. Receive the variable redirection script pre-configured in the new HMI interface.

[0044] This disclosure supports configuration variable redirection scripts after a new HMI interface is generated, enabling new interfaces to be flexibly associated with physical devices, improving the scalability of the SCADA system interface, and adapting to new system interface requirements.

[0045] In related technologies, if a new HMI interface is configured, professionals are required to redevelop the new interface, which results in poor system scalability. However, in this disclosure, if the process flow of the new HMI interface is the same as that of the existing HMI interface, it is only necessary to configure the corresponding variable redirection script for the same physical equipment. When switching to the new HMI interface, step S102 is executed to update the process flow, thereby improving the system scalability.

[0046] In the traditional model, when adding or replacing equipment, a corresponding HMI operation and display interface needs to be developed separately for each equipment. This not only takes an average of 3-5 person-days per equipment, but also results in extremely poor system scalability and difficulty in quickly adapting to business changes.

[0047] In existing SCADA systems, screen elements in the HMI interface (such as start buttons, temperature display boxes, and fault indicator lights) are directly associated with the hardware addresses of physical devices (such as the IP addresses of sensors and the port numbers of controllers). Once a device is updated or added, the original "element-address" association will become invalid. Technicians must rewrite the interface code and debug the binding relationship. The whole process is time-consuming and laborious, and the design logic of the existing interface cannot be reused.

[0048] To address this issue, this application uses a variable redirection script to establish a connection between two functionally independent logical point identifiers, replacing the traditional "interface-device hard binding." The "screen logical point identifier" is directly associated only with screen elements of the HMI interface, responsible for carrying the interface's operational feedback and display rules, and does not involve any physical device information. The "device logical point identifier," on the other hand, is directly associated only with the physical device monitored by the SCADA system, serving as the device's "identity identifier" within the system, and is not bound to any interface element. After the two are bound together through the variable redirection script, operations on screen elements are indirectly transmitted to the target device, forming a link of "screen element → screen logical point identifier → device logical point identifier → physical device."

[0049] When a new HMI interface needs to be added, if the physical devices involved in the interface have already appeared in a previous HMI interface (for example, adding a "Workshop 2 Water Pump Monitoring Interface", where the physical devices are similar to those in "Workshop 1"), there is no need for professionals to redevelop a completely new interface. Technicians only need to configure a variable redirection script for the new interface, defining the association between "the screen logic point identifier of the new interface" and "the target device logic point identifier".

[0050] When demonstrating the new HMI interface to users later (i.e., when the system receives the trigger command for the variable redirection script), the script will automatically perform two key operations: First, it unbinds the device logical point identifier from the old interface (to avoid conflicts caused by the same device being associated with multiple interfaces simultaneously); second, it rebinds the device logical point identifier to the physical device required for the new interface. Throughout the entire process, the association between HMI screen elements and screen logical point identifiers remains unchanged, and the interface operation logic and display effects seen by the user are consistent with the old interface, requiring no relearning.

[0051] The advantages of this design are significant: on the one hand, it completely eliminates the 3-5 person-days / device time required to develop a new interface in the traditional model, and the adaptation of new interfaces can be quickly completed simply by configuring scripts; on the other hand, it fundamentally solves the problem of poor scalability of the existing system. When adding or replacing devices in the future, only the binding relationship in the variable redirection script needs to be adjusted, without modifying the HMI interface itself. This achieves flexible adaptation where "device iteration does not affect the interface and interface reuse does not depend on the device", which greatly improves the efficiency of the SCADA system in responding to business changes.

[0052] For example, such as Figure 2 The diagram shown is the process diagram of a fire pump room. In the fire pump, based on business requirements, the variable redirection scripts are VarRedir(a1.pv, "BPCS\state\MOV_STATERUN_2103.pv"), VarRedir(a2.pv, "BPCS\state\MOV_STATERUN_2104.pv"), and VarRedir(a3.pv, "BPCS\state\MOV_STATERUN_2105.pv"). [Additional information is needed for this purpose.] Figure 3 Taking wastewater treatment hardware as an example, such as Figure 2 and Figure 3 As shown, the hardware equipment in a fire pump room is similar to that in a sewage treatment plant. When configuring the process flow for sewage treatment, it should be based on business needs, such as... Figure 4 As shown, the predefined variable redirection scripts for wastewater treatment are VarRedir(a1.pv, "ws\state\MOV_STATERUN_2103.pv") and VarRedir(a2.pv, "ws\state\MOV_STATERUN_2104.pv").

[0053] Upon receiving the trigger command from the variable redirection script of the HMI interface corresponding to wastewater treatment, it detects that a1.pv and a2.pv are database points. Then, it unbinds the binding relationship of a1.pv and a2.pv, binds a1.pv to "ws\state\MOV_STATERUN_2103.pv", and binds a2.pv to "ws\state\MOV_STATERUN_2104.pv". Thus, when displaying the HMI interface corresponding to wastewater treatment, the screen element corresponding to a1.pv points to the physical device corresponding to ws\state\MOV_STATERUN_2103.pv, and the screen element corresponding to a2.pv points to the physical device corresponding to ws\state\MOV_STATERUN_2104.pv.

[0054] In one embodiment, the HMI interface that receives the pre-configured variable redirection script is the main interface; after the main interface is redirected, all sub-interfaces corresponding to the main interface are also redirected accordingly.

[0055] A variable redirection script can be pre-configured in the main interface, and this variable redirection script will also take effect in the corresponding sub-interfaces of the main interface. That is, after the variable redirection script is triggered in the main interface, not only the main interface will be redirected in terms of screen elements and physical devices, but all sub-interfaces will also be redirected in the same way.

[0056] At this point, when the system receives the display command for the sub-interface, it will output the redirected sub-interface.

[0057] After the main interface is redirected, the sub-interfaces are automatically redirected synchronously, eliminating the need to configure each sub-interface individually, reducing repetitive operations, significantly improving the redirection efficiency of multi-level (main-sub) interface systems, and reducing operational complexity.

[0058] Based on the same inventive concept, this application also provides a SCADA system interface point rerouting system for implementing the SCADA system interface point rerouting method described above. The solution provided by this system is similar to the implementation scheme described in the above method. Therefore, the specific limitations of one or more SCADA system interface point rerouting system embodiments provided below can be found in the limitations of the SCADA system interface point rerouting method described above, and will not be repeated here.

[0059] In one exemplary embodiment, such as Figure 5 As shown, a SCADA system interface point rerouting system is provided, including: The receiving module 11 is used to receive pre-configured variable redirection scripts in each HMI interface of the SCADA system. The variable redirection scripts are configured to bind two preset logical point identifiers. The screen logical point identifier is directly associated with the screen element in the current HMI interface and not directly associated with the physical device monitored by the SCADA system. The device logical point identifier is directly associated with the physical device monitored by the SCADA system and not directly associated with the screen element in the current HMI screen. After binding the two logical point identifiers, the operation on the screen element in the current HMI interface corresponding to the screen logical point identifier is equivalent to the operation on the physical device associated with the device logical point identifier. The processing module 12 is used to, when receiving a trigger instruction for the variable redirection script for any HMI interface, after detecting that the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound together, unbind the binding relationship, and bind the unbound current screen logical point identifier and the current device logical point identifier together to complete the redirection of screen elements in the HMI interface to the physical device. Output module 13 is used to output the redirected HMI interface.

[0060] In an exemplary embodiment, the processing module 12 is specifically used for: Detect whether the current screen logical point identifier is a database point; If the current screen logical point identifier is a database point, then the current screen logical point identifier in the current variable redirection script is bound to other device logical point identifiers.

[0061] In an exemplary embodiment, the processing module 12 is further configured to: After detecting that the current screen logical point identifier is not bound to other device logical point identifiers, the current screen logical point identifier is bound to the current device logical point identifier.

[0062] In an exemplary embodiment, the HMI interface for receiving the pre-configured variable redirection script is the main interface; the processing module 12 is further configured to: After the main interface is redirected, all sub-interfaces corresponding to the main interface are also redirected accordingly.

[0063] In an exemplary embodiment, the receiving module 11 is further configured to: receive a display instruction from the sub-interface; The output module 13 is also used to output the redirected sub-interface.

[0064] In one exemplary embodiment, the apparatus further includes: The instruction receiving module is used to receive a new HMI interface generation instruction; the HMI interface generation instruction includes screen elements in the HMI interface. The generation module is used to generate a new HMI interface, including screen elements; The script receiving module is used to receive the variable redirection scripts pre-configured for the new HMI interface.

[0065] In one exemplary embodiment, the processing module is further configured to: After detecting that the current logical point identifier in the current variable redirection script is not bound, the current device logical point identifier is bound to the physical device corresponding to the current variable redirection script.

[0066] In one embodiment, the processing module is further configured to: send a trigger instruction for a variable redirection script via a preset trigger control in the HMI interface.

[0067] In one exemplary embodiment, a computer device is provided, which may be a server or a terminal, and its internal structure diagram may be as follows. Figure 6 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media to run. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a SCADA system interface point rerouting method.

[0068] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0069] In one exemplary embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0070] In one exemplary embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0071] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0072] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0073] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).

[0074] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0075] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0076] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for rerouting interface points in a SCADA system, characterized in that, The method includes: In each HMI interface of the SCADA system, a pre-configured variable redirection script is received. The variable redirection script is configured to bind two preset logical point identifiers. The screen logical point identifier is directly associated with the screen element in the current HMI interface, but not directly associated with the physical device monitored by the SCADA system. The device logical point identifier is directly associated with the physical device monitored by the SCADA system, but not directly associated with the screen element in the current HMI screen. After binding the two logical point identifiers, the operation on the screen element in the current HMI interface corresponding to the screen logical point identifier is equivalent to the operation on the physical device associated with the device logical point identifier. When a trigger instruction is received for the variable redirection script for any HMI interface, after detecting that the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound together, the binding relationship is unbound, and the unbound current screen logical point identifier and current device logical point identifier are bound together to complete the redirection of screen elements in the HMI interface to the physical device. Output the redirected HMI interface.

2. The method according to claim 1, characterized in that, The detection of the binding of the current screen logical point identifier and other device logical point identifiers in the current variable redirection script includes: Detect whether the current screen logical point identifier is a database point; If the current screen logical point identifier is a database point, then the current screen logical point identifier in the current variable redirection script is bound to other device logical point identifiers.

3. The method according to claim 1, characterized in that, The method further includes: After detecting that the current screen logical point identifier is not bound to other device logical point identifiers, the current screen logical point identifier is bound to the current device logical point identifier.

4. The method according to claim 1, characterized in that, The method further includes: The HMI interface for receiving pre-configured variable redirection scripts is the main interface. After the main interface is redirected, all sub-interfaces corresponding to the main interface are also redirected accordingly.

5. The method according to claim 4, characterized in that, The method further includes: Receive display instructions from the sub-interface; Output the redirected sub-interface.

6. The method according to claim 1, characterized in that, The method further includes: Receive a new HMI interface generation instruction; the HMI interface generation instruction includes screen elements in the HMI interface; Generate a new HMI interface that includes visual elements; Receive the pre-configured variable redirection script for the new HMI interface.

7. A SCADA system interface point rerouting system, characterized in that, The system includes: The receiving module is used to receive pre-configured variable redirection scripts in each HMI interface of the SCADA system. The variable redirection scripts are configured to bind two preset logical point identifiers. The screen logical point identifier is directly associated with the screen element in the current HMI interface, but not directly associated with the physical device monitored by the SCADA system. The device logical point identifier is directly associated with the physical device monitored by the SCADA system, but not directly associated with the screen element in the current HMI screen. After binding the two logical point identifiers, the operation on the screen element in the current HMI interface corresponding to the screen logical point identifier is equivalent to the operation on the physical device associated with the device logical point identifier. The processing module is used to, when receiving a trigger instruction for the variable redirection script for any HMI interface, after detecting that the current screen logical point identifier and other device logical point identifiers in the current variable redirection script are bound together, unbind the binding relationship, and bind the unbound current screen logical point identifier and the current device logical point identifier together to complete the redirection of screen elements in the HMI interface to the physical device. The output module is used to output the redirected HMI interface.

8. A computer device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program to implement the steps of the SCADA system interface point rerouting method according to any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the SCADA system interface point rerouting method as described in any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the SCADA system interface point rerouting method as described in any one of claims 1-6.

Images