An industrial software compatibility adaptation method and system
By generating causal chains of field events and normalizing response data and aligning node responses, the problem of timing offset after SCADA configuration engineering migration was solved, achieving accurate compatibility and adaptation and reducing the impact on other event chains, thus improving the relevance and field usability of the adapted data.
Patent Information
- Application Number
- CN202611194600.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-07
- Publication Date
- 2026-11-17
AI Technical Summary
After migrating the SCADA configuration project to the target operating system, the timing of field events shifts between acquisition, alarm, event sequence recording, and linkage actions, making it difficult to locate and adapt to compatibility anomalies.
By analyzing the point acquisition relationships, alarm trigger relationships, event sequence recording relationships, and linkage action relationships in the SCADA configuration project, a causal chain of field events is generated. The same field event excitation sequence is input into the benchmark and target operating systems to normalize the response data and align the node responses. The node sequence and time offset are identified, and parameters such as the acquisition task phase, communication buffer, and alarm scanning cycle are adjusted to generate adapted processing data.
Under normal conditions of screen loading and functional use cases, the system accurately identifies and adjusts timing offsets in the target operating system, improving the accuracy of locating cross-operating system compatibility anomalies in SCADA configuration engineering, reducing the impact on other event chains, and enhancing the relevance and on-site availability of the adapted data.
Smart Images

Figure CN123114787A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of industrial software compatibility and adaptation technology, specifically to an industrial software compatibility and adaptation method and system. Background Technology
[0002] When industrial software is migrated to different operating system environments, compatibility adaptation is required to ensure the continuity of original engineering configurations, data interactions, and business operations. Traditional compatibility adaptation methods typically focus on software installation, startup, dependency library installation, interface display, interface connectivity, and functional use case execution.
[0003] For SCADA configuration engineering, even after screen loading, point communication, alarm configuration, and linkage configuration have passed testing, differences in operating system scheduling, communication caching, database writing, and service response may still cause sequence shifts in the acquisition, alarm, event sequence recording, and linkage actions of field events occurring within close time intervals. Existing methods struggle to detect inconsistencies in event timing under seemingly normal operating conditions and also find it difficult to identify the adaptation targets that need adjustment. Summary of the Invention
[0004] This invention provides an industrial software compatibility adaptation method and system, which solves the problem that after SCADA configuration engineering is migrated to the target operating system, the surface functions are normal, but the timing of field events is offset between acquisition, alarm, event sequence recording and linkage action, resulting in compatibility anomalies that are difficult to locate and adapt.
[0005] To achieve the above objectives, in one aspect, the present invention provides an industrial software compatibility adaptation method, the method comprising: S1: Obtain the SCADA configuration project in the industrial software to be adapted; parse the point acquisition relationship, alarm trigger relationship, event sequence recording relationship, linkage action relationship and status readback relationship in the SCADA configuration project, and generate the cause-effect chain of field events.
[0006] S2: Generate a field event excitation sequence with event injection timestamps based on the triggering conditions, acquisition cycle, alarm delay, event sequence recording resolution, and linkage trigger waiting time in the field event causal chain.
[0007] S3: Deploy the SCADA configuration project in the base operating system and the target operating system respectively. Input point change events according to the event injection timescale in the field event excitation sequence, and collect base event chain response data and target event chain response data with response timescales. Using the event injection timescale as the time zero point, normalize the response timescales in the base event chain response data and target event chain response data to obtain base normalized response data and target normalized response data. Match response records belonging to the same field event in the base normalized response data and target normalized response data according to the node order and point identifier in the field event causal chain to generate node response alignment results. Calculate the node order offset and node time offset of the target operating system relative to the base operating system based on the node response alignment results to generate a time-series offset node set.
[0008] S4: Based on the node type in the time-series offset node set, map the time-series offset nodes to the acquisition task phase, communication buffer threshold, alarm scan cycle, event sequence record temporary storage window, event sequence record sorting rule, linkage trigger waiting time and status readback matching window to generate adaptation processing data; update the SCADA configuration project running parameters in the target operating system based on the adaptation processing data to generate the adapted SCADA configuration project.
[0009] Furthermore, the method for generating the causal chain of on-site events includes: Extract the point identifier and collection period from the point collection relationship to generate point event source nodes indexed by the point identifier.
[0010] Based on the location identifier and alarm triggering conditions in the alarm triggering relationship, an alarm node is generated, and a first directed edge is established from the location event source node to the alarm node; based on the location identifier and record triggering conditions in the event sequence record relationship, an event sequence record node is generated, and a second directed edge is established from the location event source node to the event sequence record node.
[0011] The composite triggering conditions in the linkage action relationship are decomposed into atomic conditions to obtain atomic condition nodes; the atomic condition nodes containing point identifiers are bound to the corresponding point event source nodes; the linkage actions are extracted from the linkage action relationship to generate linkage action nodes; logical intermediate nodes are generated according to the logical operation relationship in the composite triggering conditions, and linkage directed edges are established between atomic condition nodes, logical intermediate nodes and linkage action nodes.
[0012] Based on the state readback relationship, extract the readback points corresponding to the linkage action nodes, generate state readback nodes, and establish readback directed edges from the linkage action nodes to the state readback nodes; based on the acquisition period, alarm delay, event sequence recording resolution, linkage trigger waiting time and state readback matching window, configure edge timing constraints for the first directed edge, the second directed edge, the linkage directed edge and the readback directed edge, and generate the on-site event causal chain.
[0013] Furthermore, the method for generating a field event excitation sequence with an event injection time stamp based on the triggering conditions, acquisition cycle, alarm delay, event sequence recording resolution, and linkage triggering waiting time in the field event causal chain includes: Extract the path extending from the point event source node to the non-point node from the causal chain of the on-site events to generate the target event sub-chain; the non-point nodes include alarm nodes, event sequence record nodes, linkage action nodes and status readback nodes; determine the boundary time corresponding to each edge timing constraint according to the edge timing constraint value corresponding to the target event sub-chain.
[0014] Based on the point event source nodes, atomic condition nodes, and logical intermediate nodes in the target event subchain, determine the set of point event source nodes participating in the same target event subchain, and extract the point identifier and trigger value from the trigger conditions corresponding to the target event subchain.
[0015] Based on the edge timing constraint value and the preset disturbance ratio, set the boundary pre-time marker and boundary post-time marker before and after the boundary time, and use the boundary time as the boundary time marker; generate a point change event group based on the point identifier, trigger value, boundary pre-time marker, boundary time marker and boundary post-time marker.
[0016] Based on the synchronization satisfaction relationship corresponding to the logical intermediate node, position change events at different points within the position change event group are configured with the same event injection time stamp; based on the alternative satisfaction relationship corresponding to the logical intermediate node, position change events at different points within the position change event group are configured with different event injection time stamps; the position change event group is arranged according to the node order in the target event sub-chain to generate a field event excitation sequence with event injection time stamps.
[0017] Furthermore, the method for matching response records belonging to the same on-site event in the baseline normalized response data and the target normalized response data according to the node order and location identifier in the causal chain of the on-site event to generate node response alignment results includes: The event injection timestamp, location identifier, and trigger value are extracted from each entry of the field event excitation sequence to generate a field event identifier.
[0018] Based on the location identifier in the on-site event identifier and the node identifier associated with the location identifier in the on-site event causal chain, the response records corresponding to the on-site event identifier and whose normalized response timestamps fall into the preset matching window are extracted from the baseline normalized response data and the target normalized response data, and a baseline response record group and a target response record group are generated.
[0019] Based on the source module identifier of the response record, the baseline response record group and the target response record group are respectively divided into point acquisition response record, alarm response record, event sequence record response record, linkage action response record and status readback response record; According to the node order in the causal chain of the on-site events, the baseline response record and the target response record of the same node type are arranged in ascending order by normalized response time scale.
[0020] Within the same node type, the baseline response record and the target response record with the smallest absolute value of the normalized response time difference that is not greater than a preset matching threshold are paired with the baseline response record and the target response record. The baseline response record and the target response record that do not form a pair are marked as unmatched response records. The node response alignment result is generated based on the pair of response records and the unmatched response records.
[0021] Furthermore, the method for mapping time-series offset nodes to acquisition task phases, communication buffer thresholds, alarm scan cycles, event sequence record temporary storage windows, event sequence record sorting rules, linkage trigger waiting times, and status readback matching windows based on the node types in the time-series offset node set, and generating adaptive processing data includes: From the node response alignment results corresponding to the time-series offset node set, obtain the node type, node time offset, node sequence offset, and unmatched response record marker to generate node offset features.
[0022] According to the node order in the causal chain of the on-site events, the time-series offset node is compared with the adjacent upstream node to determine the offset source type of the time-series offset node; the offset source type includes the offset processed by this node and the offset transmitted upstream.
[0023] When the offset source type is upstream propagation offset, the adjacent upstream node with the smallest offset increment in the offset propagation comparison results is marked as the offset source node of the time-series offset node.
[0024] When the offset source type is "this node processing offset", corresponding adjustment items are generated according to the node type; when the node type is "point event source node", acquisition task phase adjustment item and communication buffer threshold adjustment item are generated; when the node type is "alarm node", alarm scan cycle adjustment item is generated; when the node type is "event sequence record node", event sequence record temporary storage window adjustment item and event sequence record sorting rule adjustment item are generated; when the node type is "linked action node", linkage trigger waiting time adjustment item is generated; when the node type is "status readback node", status readback matching window adjustment item is generated.
[0025] Based on the node offset characteristics, the adjustment items corresponding to the offset processed by this node, and the offset source node corresponding to the upstream transmitted offset, adaptation processing data is generated.
[0026] Furthermore, the method for determining the offset source type of a time-series offset node by comparing its offset propagation with that of its adjacent upstream nodes according to the node order in the causal chain of the on-site events includes: Based on the causal chain of the on-site events, extract the set of adjacent upstream nodes of the time-series offset node; extract the node time offset, node sequence offset, and unmatched response record marker of each adjacent upstream node in the time-series offset node and the set of adjacent upstream nodes from the node response alignment result.
[0027] Based on the edge timing constraint values of the connection timing offset node and the adjacent upstream node, as well as the preset tolerance coefficient, the allowable transmission offset range is determined; the offset increment between the node time offset of the timing offset node and the node time offset of each adjacent upstream node is calculated.
[0028] When there is an offset increment that falls within the allowed transmission offset range, the node sequence offset direction determined by the node sequence offset is consistent, and neither the temporal offset node nor the adjacent upstream node has an adjacent upstream node with an unmatched response record, the offset source type of the temporal offset node is determined to be upstream transmission offset.
[0029] When there is no node that simultaneously satisfies the conditions that the offset increment falls within the allowed offset range, the node sequence offset direction is consistent, and neither the time-series offset node nor its adjacent upstream node has an unmatched response record, the offset source type of the time-series offset node is determined to be the offset processed by this node.
[0030] Furthermore, the method for generating adaptation processing data based on the node offset characteristics, the adjustment item corresponding to the current node's processing offset, and the offset source node corresponding to the upstream transmitted offset includes: Using the time-series offset node corresponding to the offset processed by this node as the adjustment reference node, the set of affected downstream nodes is determined based on the directed edges originating from the adjustment reference node in the causal chain of the on-site events.
[0031] Based on the edge timing constraint value of each node in the affected downstream node set, the current parameter value of the corresponding adjustment item, and the preset safety coefficient, the parameter safety boundary of the corresponding adjustment item is determined; based on the node time offset, node sequence offset, and parameter response polarity of the corresponding adjustment item in the node offset feature, the adjustment direction and candidate adjustment magnitude of the corresponding adjustment item are determined; based on the current parameter value, adjustment direction, and candidate adjustment magnitude, the candidate parameter value is obtained.
[0032] When a candidate parameter value falls within the parameter safety boundary, the candidate adjustment range is retained; when a candidate parameter value exceeds the parameter safety boundary, the candidate adjustment range is corrected based on the difference between the boundary value corresponding to the adjustment direction in the parameter safety boundary and the current parameter value.
[0033] Based on the adjustment items for retaining candidate adjustment ranges, the adjustment items for correcting candidate adjustment ranges, and the offset source node, adaptation processing data is generated.
[0034] Based on the same inventive concept, this invention also provides an industrial software compatibility adaptation system, the system comprising: The causal chain construction module is used to obtain the SCADA configuration project in the industrial software to be adapted; it parses the point acquisition relationship, alarm trigger relationship, event sequence recording relationship, linkage action relationship and status readback relationship in the SCADA configuration project to generate the causal chain of field events.
[0035] The critical excitation generation module is used to generate a sequence of on-site event excitations with event injection timestamps based on the triggering conditions, acquisition period, alarm delay, event sequence recording resolution, and linkage trigger waiting time in the on-site event causal chain.
[0036] The response offset analysis module is used to deploy the SCADA configuration project on the base operating system and the target operating system respectively. It inputs point change events according to the event injection timestamps in the field event excitation sequence, and collects base event chain response data and target event chain response data with response timestamps. Using the event injection timestamps as the zero point, it normalizes the response timestamps in the base event chain response data and target event chain response data to obtain base normalized response data and target normalized response data. According to the node order and point identifier in the field event causal chain, it matches response records belonging to the same field event in the base and target normalized response data to generate node response alignment results. Based on the node response alignment results, it calculates the node order offset and node time offset of the target operating system relative to the base operating system, generating a time-series offset node set.
[0037] The adaptation data generation module is used to map the time-series offset nodes to the acquisition task phase, communication buffer threshold, alarm scan cycle, event sequence record temporary storage window, event sequence record sorting rules, linkage trigger waiting time and status readback matching window according to the node type in the time-series offset node set, and generate adaptation processing data; and update the SCADA configuration project running parameters in the target operating system according to the adaptation processing data to generate the adapted SCADA configuration project.
[0038] Compared with the prior art, the beneficial effects of the present invention are: 1. By analyzing the point acquisition relationships, alarm trigger relationships, event sequence recording relationships, linkage action relationships, and status readback relationships in the SCADA configuration project, a causal chain of field events is generated. The same field event excitation sequence is input into the base operating system and the target operating system. The response data of the base event chain and the target event chain are normalized and the node response is aligned. Under the condition that the screen loading, point communication, and functional use cases are all normal, the node sequence offset and node time offset between acquisition, alarm, event sequence recording, linkage action, and status readback in the target operating system can be identified. This avoids judging the compatibility status solely based on installation startup, interface connectivity, and function execution results, and improves the accuracy of locating cross-operating system compatibility anomalies in SCADA configuration projects.
[0039] 2. By generating pre-boundary, post-boundary timescales through edge timing constraints, and combining atomic condition nodes, logical intermediate nodes, synchronization satisfaction relations, and alternative satisfaction relations, the field event excitation sequence is arranged so that the critical acquisition, alarm delay, event sequence recording, linkage triggering, and status readback processes in the same target event sub-chain are triggered centrally. At the same time, the offset transmission comparison of adjacent upstream nodes distinguishes the processing offset of this node from the upstream transmission offset, and introduces parameter safety boundaries when generating adaptation processing data. This can reduce the repeated parameter tuning of downstream transmission offsets, reduce the impact of acquisition task phase, communication buffer threshold, alarm scan cycle, event sequence recording temporary window, linkage trigger waiting time, and status readback matching window adjustment on other event chains, and improve the relevance and field usability of adaptation processing data. Attached Figure Description
[0040] Figure 1 This is a flowchart of an industrial software compatibility adaptation method according to the present invention; Figure 2 This is a block diagram of an industrial software compatibility and adaptation system according to the present invention. Detailed Implementation
[0041] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0042] This invention is applicable to industrial software compatibility and adaptation scenarios where SCADA configuration engineering is migrated from a base operating system to a target operating system. It is particularly suitable for production site monitoring engineering where there are requirements for consistency of event timing among point acquisition, alarm triggering, event sequence recording, linkage actions and status readback.
[0043] Example 1: As Figure 1 As shown, this embodiment provides an industrial software compatibility adaptation method, the method including: Obtain the SCADA configuration project from the industrial software to be adapted; parse the point acquisition relationship, alarm trigger relationship, event sequence recording relationship, linkage action relationship and status readback relationship in the SCADA configuration project, extract the point identifier and acquisition cycle from the point acquisition relationship, and generate point event source nodes indexed by the point identifier.
[0044] Based on the location identifier and alarm triggering conditions in the alarm triggering relationship, an alarm node is generated, and a first directed edge is established from the location event source node to the alarm node; based on the location identifier and record triggering conditions in the event sequence record relationship, an event sequence record node is generated, and a second directed edge is established from the location event source node to the event sequence record node.
[0045] The composite triggering conditions in the linkage action relationship are decomposed into atomic conditions to obtain atomic condition nodes; the atomic condition nodes containing point identifiers are bound to the corresponding point event source nodes; the linkage actions are extracted from the linkage action relationship to generate linkage action nodes; logical intermediate nodes are generated according to the logical operation relationship in the composite triggering conditions, and linkage directed edges are established between atomic condition nodes, logical intermediate nodes and linkage action nodes.
[0046] Based on the state readback relationship, extract the readback points corresponding to the linkage action nodes, generate state readback nodes, and establish readback directed edges from the linkage action nodes to the state readback nodes; based on the acquisition period, alarm delay, event sequence recording resolution, linkage trigger waiting time and state readback matching window, configure edge timing constraints for the first directed edge, the second directed edge, the linkage directed edge and the readback directed edge, and generate the on-site event causal chain.
[0047] In this embodiment, the SCADA configuration project of circulating water pump station CWP_01 is used as a fixed example object. Point identifier LT101_HH corresponds to the high-level switch quantity of the water tank, with a collection period of 200ms; point identifier P101_FB corresponds to the operation feedback of circulating water pump No. 1, with a collection period of 100ms; point identifier P101_CMD corresponds to the start command of circulating water pump No. 1, with a collection period of 100ms. The alarm trigger condition is LT101_HH=1, and the alarm delay is 600ms; the recording trigger condition is LT101_HH changing from 0 to 1, and the event sequence recording resolution is 10ms; the linkage action relationship is that when LT101_HH=1 and P101_FB=0, P101_CMD=1 is output, and the linkage trigger waiting time is 300ms; the status readback relationship is that after P101_CMD=1, P101_FB=1 is read, and the status readback matching window is 800ms.
[0048] Extract the path extending from the point event source node to the non-point node from the on-site event causal chain to generate the target event sub-chain; the non-point nodes include alarm nodes, event sequence record nodes, linkage action nodes and status readback nodes.
[0049] Based on the edge timing constraint values corresponding to the target event subchain, determine the boundary time corresponding to each edge timing constraint; wherein, the edge timing constraint value This corresponds to the acquisition period, alarm delay, event sequence recording resolution, linkage trigger waiting time, and status readback matching window. The boundary moment corresponding to the acquisition period is the position where the distance from the start of the previous acquisition period is equal to the acquisition period itself; the boundary moment corresponding to the alarm delay is the position where the duration of the alarm trigger condition reaches the alarm delay; the boundary moment corresponding to the event sequence recording resolution is the position where the difference between the injected time stamps of adjacent events equals the event sequence recording resolution; the boundary moment corresponding to the linkage trigger waiting time is the position where the linkage trigger waiting time is reached after the composite trigger condition is met; and the boundary moment corresponding to the status readback matching window is the position where the status readback matching window is reached after the linkage action is output.
[0050] Based on the point event source nodes, atomic condition nodes, and logical intermediate nodes in the target event subchain, determine the set of point event source nodes participating in the same target event subchain, and extract the point identifier and trigger value from the trigger conditions corresponding to the target event subchain.
[0051] Based on the edge timing constraint value and the preset perturbation ratio, a pre-boundary time marker and a post-boundary time marker are set before and after the boundary time, and the boundary time is used as the boundary time marker; in this embodiment, the preset perturbation ratio... Set to 0.05, the minimum injection resolution for event injection tools. Take 2ms. Boundary perturbation step size. When the acquisition period of LT101_HH is 200ms, The timescales before, after, and before the boundary are 190ms, 200ms, and 210ms, respectively. When the alarm delay is 600ms, The time stamps before, at, and after the boundary are 570ms, 600ms, and 630ms, respectively. When the event sequence recording resolution is 10ms, The timescales before, after, and before the boundary are 8ms, 10ms, and 12ms, respectively. When the trigger wait time is 300ms, The timescales before, after, and before the boundary are 285ms, 300ms, and 315ms, respectively. When the state readback matching window is 800ms, The timescales before, after, and before the boundary are 760ms, 800ms, and 840ms, respectively.
[0052] A point change event group is generated based on the point identifier, trigger value, pre-boundary timescale, boundary timescale, and post-boundary timescale; Based on the synchronization satisfaction relationship corresponding to the logical intermediate node, position change events at different points within the position change event group are configured with the same event injection time stamp; based on the alternative satisfaction relationship corresponding to the logical intermediate node, position change events at different points within the position change event group are configured with different event injection time stamps; the position change event group is arranged according to the node order in the target event sub-chain to generate a field event excitation sequence with event injection time stamps.
[0053] Synchronization satisfies the relationship LT101_HH=1 and P101_FB=0. Taking AND logic operation as an example, the intermediate logical node is the AND node, and the output of the AND node is true if and only if the outputs of the atomic condition nodes corresponding to LT101_HH=1 and P101_FB=0 are both true. When the event injection timestamp is 200ms, the PLC / RTU protocol simulator writes LT101_HH=1 and P101_FB=0 at the same event injection timestamp. In the case where multiple point change events corresponding to one of the relationships independently trigger the same linkage action node, the point change events are written according to different event injection timestamps, and the interval between the two event injection timestamps is not less than the minimum injection resolution of the event injection tool. Taking the OR logical operation as an example, the intermediate logical node is the OR node, and the output of the OR node is true if and only if the output of any atomic condition node is true. Each record in the point change event group includes an event injection timestamp, a point identifier, a trigger value, and a target event sub-chain identifier. The target event sub-chain identifier is generated by concatenating the point event source node identifier and the non-point node identifier; when the target event sub-chain includes a linked action node, the target event sub-chain identifier is also concatenated with the linked action node identifier. The event injection timestamp is the planned output time of the point change event at the PLC / RTU protocol simulator output terminal; the PLC / RTU protocol simulator compensates for the actual output time according to the injection link delay, so that the deviation between the actual output time and the event injection timestamp is no greater than the minimum injection resolution of the event injection tool.
[0054] When the target event subchain does not contain logical intermediate nodes, the point change event is written separately according to the boundary pre-timescale, boundary timescale, and boundary post-timescale of the corresponding point event source node; when the target event subchain contains multiple point event source nodes but does not form a synchronous satisfaction relationship or an alternative satisfaction relationship, the point change event is written sequentially according to the node order in the target event subchain.
[0055] The benchmark operating system was based on the original operating environment of the circulating water pump station CWP_01, which had been running continuously for 30 days without any missed alarms, disordered event sequence records, or false triggering of linkage actions. Before the benchmark operating system was put into adaptation and comparison, 100 single-point displacement events were input into LT101_HH, with an interval of 5 seconds between two adjacent single-point displacement events. 100 sets of point acquisition response records, alarm response records, and event sequence record response records were collected. The standard deviation of response jitter was measured. , For the first Normalized response time scale corresponding to sub-single-point displacement events; omission rate , This represents the number of times a complete response record was not generated. Total number of single-point shift events; sequence reversal rate. , Record the number of times the response record order is inconsistent with the event injection timestamp order. When , and At that time, the benchmark operating system serves as the benchmark environment. If , or Replace the base operating system or recalibrate the SCADA configuration engineering communication drive parameters.
[0056] Point change events are input to the SCADA configuration project via an industrial Ethernet from a PLC / RTU protocol simulator. The PLC / RTU protocol simulator records the output time stamp. The communication driver recording input of the SCADA configuration project receives the time stamp. Injected link latency Inject link jitter In this embodiment, 20 calibration pulses are input consecutively to obtain... , Event injection time stamps in the on-site event stimulus sequence The actual output timestamp of the PLC / RTU protocol simulator before writing to it. according to Settings. If If the time exceeds 2ms, discard the baseline event chain response data and target event chain response data collected in this round, and re-execute the point change event input.
[0057] The SCADA configuration project is deployed in the base operating system and the target operating system respectively. According to the event injection time stamp of the field event excitation sequence, the point change event is input, and the base event chain response data and the target event chain response data with response time stamp are collected.
[0058] Using the event injection timestamp as the zero point, the response timestamps in the baseline event chain response data and the target event chain response data are normalized to obtain baseline normalized response data and target normalized response data. The data fields of the response record include source module identifier, node identifier, location identifier, response timestamp, response value, and record sequence number. The source module identifier RTDB represents a location acquisition response record, the source module identifier ALM represents an alarm response record, the source module identifier SOE represents an event sequence record response record, the source module identifier ACT represents a linkage action response record, and the source module identifier FB represents a status readback response record. The normalized response timestamps in the baseline normalized response data and the target normalized response data... , For response timestamps.
[0059] The event injection timestamp, location identifier, and trigger value are extracted from each entry of the field event excitation sequence to generate a field event identifier.
[0060] Based on the location identifiers in the on-site event identifiers and the node identifiers associated with the location identifiers in the on-site event causal chain, response records corresponding to the on-site event identifiers and whose normalized response timestamps fall within a preset matching window are extracted from the baseline normalized response data and the target normalized response data, generating a baseline response record group and a target response record group; wherein, the preset matching window ; This is the algebraic sum of the temporal constraint values of the directed edges traversed by the target event subchain. The temporal constraint values of the edges corresponding to nodes not traversed by the target event subchain are not included. 2J represents the link jitter margin, used to absorb the two-sided delay fluctuations between the PLC / RTU protocol simulator output and the SCADA configuration engineering communication driver receiver. In this embodiment, LT101_HH triggers P101_CMD and reads back the target event sub-chain that has not passed through the event sequence recording node in P101_FB, including a collection period of 200ms, an alarm delay of 600ms, a linkage trigger waiting time of 300ms, and a status readback matching window of 800ms. , Preset matching threshold , The resolution is used to record the event sequence. In this embodiment, .
[0061] Based on the source module identifier of the response record, the baseline response record group and the target response record group are respectively divided into point acquisition response record, alarm response record, event sequence record response record, linkage action response record and status readback response record; according to the node order in the cause-and-effect chain of the on-site event, the baseline response record and the target response record of the same node type are respectively arranged in ascending order by normalized response time scale.
[0062] Within the same node type, the baseline response record and the target response record with the smallest absolute value of the normalized response time difference that is not greater than a preset matching threshold are paired with the baseline response record and the target response record. The baseline response record and the target response record that do not form a pair are marked as unmatched response records. The node response alignment result is generated based on the pair of response records and the unmatched response records.
[0063] Based on the node response alignment results, calculate the node sequence offset and node time offset of the target operating system relative to the base operating system, and generate a time-offset node set; node time offset , For the target normalized response data nodes The normalized response time scale, For nodes in the baseline normalized response data Normalized response timescale. Node sequence offset. , For nodes The ranking position in the target normalized response data. For nodes The ranking position of a node in the baseline normalized response data. The direction of node order offset is determined by the sign of the node order offset; a node order offset greater than 0 indicates that the corresponding node's ranking position in the target normalized response data has shifted backward, a node order offset less than 0 indicates that the corresponding node's ranking position in the target normalized response data has shifted forward, and a node order offset equal to 0 indicates that the corresponding node has not undergone order offset; when the node order offsets of two nodes are both equal to 0, or when the node order offsets of two nodes have the same sign, the node order offset directions of the two nodes are determined to be consistent.
[0064] When the target normalized response data lacks a response record that matches the baseline response record, the node... Unmatched response records are marked as target missing; when there are response records in the target normalized response data that do not form a response record pair with the baseline response record, the node... Unmatched response records are marked as newly added targets.
[0065] From the node response alignment results corresponding to the time-series offset node set, obtain the node type, node time offset, node sequence offset, and unmatched response record marker to generate node offset features; extract the set of adjacent upstream nodes of the time-series offset node according to the on-site event causal chain; extract the node time offset, node sequence offset, and unmatched response record marker of each adjacent upstream node in the time-series offset node and the set of adjacent upstream nodes from the node response alignment results.
[0066] The allowable propagation offset range is determined based on the edge timing constraint values of the connection timing offset node and the adjacent upstream node, as well as a preset tolerance coefficient; in this embodiment, the preset tolerance coefficient... Set to 0.10. The timing constraint value of the edge connecting the adjacent upstream node and the timing offset node is 0.10. At that time, the allowed transmission offset range is , When the adjacent upstream node or the time-series offset node is an event sequence record node, A data acquisition period of 200ms corresponds to... Alarm delay of 600ms corresponds to Event sequence recording resolution 10ms corresponds to If the time offset of a timing offset node is 85ms, the time offset of its adjacent upstream node is 78ms, and the offset increment is 7ms, then the allowable offset range for the corresponding connection edge is... Furthermore, if the node sequence offset direction is consistent based on the node sequence offset, and neither the time-series offset node nor its adjacent upstream nodes have any unmatched response records, then the offset source type record for the time-series offset node is recorded as an upstream propagated offset. The offset increment represents the new time offset of the time-series offset node relative to its adjacent upstream nodes; if the offset increment falls within the allowed propagated offset range, it means that the node time offset of the time-series offset node has not been significantly amplified relative to its adjacent upstream nodes, and the consistent node sequence offset direction indicates that the time-series offset node has not experienced a new sequence offset relative to its adjacent upstream nodes, and the offset of the time-series offset node can be interpreted by the propagation of its adjacent upstream nodes.
[0067] Calculate the offset increment between the node time offset of the time offset node and the node time offset of each adjacent upstream node.
[0068] When there is an offset increment that falls within the allowed transmission offset range, the node sequence offset direction determined by the node sequence offset is consistent, and neither the temporal offset node nor the adjacent upstream node has an adjacent upstream node with an unmatched response record, the offset source type of the temporal offset node is determined to be upstream transmission offset.
[0069] When there is no node that simultaneously satisfies the following conditions: the offset increment falls within the allowed transmission offset range, the node sequence offset direction is consistent, and neither the time-series offset node nor its adjacent upstream node has an unmatched response record, the offset source type of the time-series offset node is determined to be the node's processing offset. The offset source type includes the node's processing offset and the upstream transmission offset.
[0070] When the offset source type is upstream propagation offset, the adjacent upstream node with the smallest offset increment in the offset propagation comparison results is marked as the offset source node of the time-series offset node.
[0071] When the offset source type is "this node processing offset", corresponding adjustment items are generated according to the node type; when the node type is "point event source node", acquisition task phase adjustment item and communication buffer threshold adjustment item are generated; when the node type is "alarm node", alarm scan cycle adjustment item is generated; when the node type is "event sequence record node", event sequence record temporary storage window adjustment item and event sequence record sorting rule adjustment item are generated; when the node type is "linked action node", linkage trigger waiting time adjustment item is generated; when the node type is "status readback node", status readback matching window adjustment item is generated.
[0072] Using the time-series offset node corresponding to the offset processed by this node as the adjustment reference node, the set of affected downstream nodes is determined based on the directed edges originating from the adjustment reference node in the causal chain of the on-site events.
[0073] Based on the edge timing constraint value of each node in the affected downstream node set, the current parameter value of the corresponding adjustment item, and the preset safety coefficient, the parameter safety boundary of the corresponding adjustment item is determined; based on the node time offset, node sequence offset, and parameter response polarity of the corresponding adjustment item in the node offset feature, the adjustment direction and candidate adjustment magnitude of the corresponding adjustment item are determined; based on the current parameter value, adjustment direction, and candidate adjustment magnitude, the candidate parameter value is obtained.
[0074] When a candidate parameter value falls within the parameter safety boundary, the candidate adjustment range is retained; when a candidate parameter value exceeds the parameter safety boundary, the candidate adjustment range is corrected based on the difference between the boundary value corresponding to the adjustment direction in the parameter safety boundary and the current parameter value.
[0075] Based on the adjustment items for retaining candidate adjustment ranges, the adjustment items for correcting candidate adjustment ranges, and the offset source node, adaptation processing data is generated. This adaptation processing data is written to a copy of the SCADA configuration project's operating parameters, while the original SCADA configuration project's operating parameters in the target operating system remain unchanged. The copy of the SCADA configuration project's operating parameters includes the parameter name, parameter scope, current parameter value, candidate parameter value, adjustment range, parameter safety boundary, parameter response polarity, and offset source node. The parameter scope is divided into point-level parameters, target event sub-chain-level parameters, and project-wide parameters. Point-level parameters only apply to the corresponding point event source node; target event sub-chain-level parameters apply to nodes within the same target event sub-chain; and project-wide parameters apply to all target event sub-chains within the SCADA configuration project.
[0076] Preset safety factor Set the safety factor to 0.80. This indicates that a 20% timing margin is reserved in the edge timing constraint value. The parameter safety boundary is obtained by intersecting the project allowable boundary, the affected downstream node constraint boundary, and the project global constraint boundary. The project allowable boundary comes from the parameter configuration range of the SCADA configuration project; the affected downstream node constraint boundary comes from the edge timing constraint value corresponding to each node in the affected downstream node set; the project global constraint boundary comes from the minimum edge timing constraint value of the target event sub-chain that is not included in the affected downstream node set within the SCADA configuration project. The lower limit of the parameter safety boundary is determined by the maximum value among the lower limits of all boundaries, and the upper limit of the parameter safety boundary is determined by the minimum value among the upper limits of all boundaries. If the lower limit of the parameter safety boundary is greater than the upper limit of the parameter safety boundary, the candidate adjustment magnitude of the corresponding adjustment item is recorded as 0, and a safety boundary conflict mark is recorded in the adaptation processing data.
[0077] The polarity of the parameter response is determined by the SCADA configuration engineering operating parameter table, historical adaptation records, or single-parameter calibration tests. Single-parameter calibration tests change only the current parameter value of one adjustment item, keeping the remaining SCADA configuration engineering operating parameters unchanged. When the node response timestamp shifts backward after the parameter value of the adjustment item increases, the parameter response polarity is recorded as +1; when the node response timestamp shifts forward after the parameter value of the adjustment item increases, the parameter response polarity is recorded as -1. When the adjustment item mainly affects the node sequence offset or the unmatched response record marker, the parameter response polarity is determined based on the direction of decrease in the node sequence offset or the direction of decrease in the number of unmatched response records.
[0078] The current parameter value for the alarm scan cycle adjustment item is 400ms, the PLC task cycle is 100ms, and the alarm delay is 600ms. The project allowable boundaries are... The affected downstream node constraint boundary is The global constraint boundary of the project is The safety boundary of the alarm scan cycle adjustment parameter is: The 500ms is determined by the minimum allowable alarm scan cycle upper limit of the remaining target event sub-chains within the SCADA configuration project. If the node time offset is +80ms, the parameter response polarity of the alarm scan cycle adjustment item is +1. A parameter response polarity of +1 indicates that increasing the parameter value shifts the response timescale backward, affecting the damping coefficient. Take 0.70, damping coefficient This is used to limit the magnitude of a single adjustment, preventing adjacent nodes from experiencing a reverse shift in response after a single adjustment completely offsets the node's time offset. Candidate adjustment magnitude , A positive node time offset indicates that the alarm response in the target operating system is later than the alarm response in the base operating system. The adjustment direction for the alarm scan cycle adjustment item is to decrease it, and the candidate parameter value is... 344ms The candidate adjustment range is retained for 56ms.
[0079] The response polarity of the parameter in the event sequence record temporary window adjustment item is determined according to the node sequence offset. When the node sequence offset is not 0 and the unmatched response record is marked as empty, the adjustment direction of the event sequence record temporary window adjustment item is increase, and the candidate adjustment magnitude is the larger of the event sequence record resolution and the absolute value of the normalized response time scale difference of the corresponding response record. The current parameter value of the event sequence record temporary window is 20ms, the event sequence record resolution is 10ms, the absolute value of the normalized response time scale difference of the corresponding response record is 14ms, the candidate adjustment magnitude is 14ms, and the candidate parameter value is 34ms. If the parameter safety boundary of the event sequence record temporary window adjustment item is... The candidate adjustment range is retained for 14ms.
[0080] The parameter response polarity of the communication cache threshold adjustment item is determined jointly by the number of newly added response records and the node time offset. When the number of newly added response records is greater than 0 and the absolute value of the node time offset is not greater than the preset matching threshold, the adjustment direction of the communication cache threshold adjustment item is to increase; when the node time offset is positive and the number of newly added response records is 0, the adjustment direction of the communication cache threshold adjustment item is to decrease. The parameter response polarity of the status readback matching window adjustment item is determined by the unmatched response record marker; the adjustment direction is to increase when the target is missing and to decrease when the target is added. The parameter response polarity of the linkage trigger waiting time adjustment item is +1; increasing the parameter value shifts the linkage action response time marker backward, and decreasing the parameter value shifts the linkage action response time marker forward. The parameter response polarity of the acquisition task phase adjustment item is determined by the phase direction of the acquisition task; shifting the acquisition task phase forward shifts the point acquisition response time marker forward, and shifting the acquisition task phase backward shifts the point acquisition response time marker backward. The acquisition task phase adjustment item is implemented by adjusting the start execution time of the SCADA configuration engineering communication drive scan task or the polling scheduling offset.
[0081] When a candidate parameter value exceeds the parameter safety boundary, the candidate adjustment range is corrected according to the boundary value corresponding to the adjustment direction within the parameter safety boundary. If the current parameter value for the alarm scan cycle adjustment item is 400ms, the candidate adjustment direction is decrease, and the candidate adjustment range is 350ms, then the candidate parameter value is 50ms. The parameter safety boundary for the alarm scan cycle adjustment item is... The boundary value corresponding to the reduction direction is 100ms, and the adjustment range of the candidate correction is... The corrected candidate parameter value is 100ms.
[0082] The SCADA configuration project operating parameters in the target operating system are updated based on the adaptation processing data to generate the adapted SCADA configuration project. After the adaptation processing data is generated, a copy of the SCADA configuration project operating parameters in the target operating system is used to generate a candidate adapted project. The field event excitation sequence is input into the candidate adapted project again to collect the adapted event chain response data. The adapted event chain response data is processed according to the same normalization and response record matching rules to generate the adapted node response alignment result. When the maximum absolute value of the time offset of the adapted node does not exceed the preset matching threshold of 20ms, the sequential offset of the adapted nodes is 0, the number of unmatched response records is 0, and the readback status of the status readback node P101_FB is consistent with the action output result of the linkage action node P101_CMD, the candidate adapted project is determined to be the adapted SCADA configuration project. If any condition is not met, a copy of the SCADA configuration engineering operation parameters is retained, and the adaptation processing data is regenerated according to the alignment result of the adapted node response. The maximum number of update rounds corresponding to the preset round threshold is 3 rounds in this embodiment. If the condition is still not met after 3 rounds of updates, a manual review mark is recorded in the adaptation processing data.
[0083] Example 2: Based on the same inventive concept, such as Figure 2 As shown, this embodiment also provides an industrial software compatibility adaptation system, the system comprising: The causal chain construction module is used to obtain the SCADA configuration project in the industrial software to be adapted; it parses the point acquisition relationship, alarm trigger relationship, event sequence recording relationship, linkage action relationship and status readback relationship in the SCADA configuration project to generate the causal chain of field events.
[0084] The critical excitation generation module is used to generate a sequence of on-site event excitations with event injection timestamps based on the triggering conditions, acquisition period, alarm delay, event sequence recording resolution, and linkage trigger waiting time in the on-site event causal chain.
[0085] The response offset analysis module is used to deploy the SCADA configuration project on the base operating system and the target operating system respectively. It inputs point change events according to the event injection timestamps in the field event excitation sequence, and collects base event chain response data and target event chain response data with response timestamps. Using the event injection timestamps as the zero point, it normalizes the response timestamps in the base event chain response data and target event chain response data to obtain base normalized response data and target normalized response data. According to the node order and point identifier in the field event causal chain, it matches response records belonging to the same field event in the base and target normalized response data to generate node response alignment results. Based on the node response alignment results, it calculates the node order offset and node time offset of the target operating system relative to the base operating system, generating a time-series offset node set.
[0086] The adaptation data generation module is used to map the time-series offset nodes to the acquisition task phase, communication buffer threshold, alarm scan cycle, event sequence record temporary storage window, event sequence record sorting rules, linkage trigger waiting time and status readback matching window according to the node type in the time-series offset node set, and generate adaptation processing data; and update the SCADA configuration project running parameters in the target operating system according to the adaptation processing data to generate the adapted SCADA configuration project.
[0087] It should be noted that the specific methods by which each module performs operations in the system described in the above embodiments have been described in detail in the embodiments related to the method, and will not be elaborated here.
[0088] Finally, it should be noted that although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.
Claims
1. An industrial software compatibility adaptation method, characterized in that, The method includes: Obtain the SCADA configuration project from the industrial software to be adapted; parse the point acquisition relationship, alarm trigger relationship, event sequence recording relationship, linkage action relationship and status readback relationship in the SCADA configuration project, and generate the cause-effect chain of field events; Based on the triggering conditions, acquisition cycle, alarm delay, event sequence recording resolution, and linkage triggering waiting time in the on-site event causal chain, an on-site event excitation sequence with event injection timestamps is generated. The SCADA configuration project is deployed in the baseline operating system and the target operating system, respectively. Input point change events according to the event injection timestamps in the field event excitation sequence, and collect baseline event chain response data and target event chain response data with response timestamps. Using the event injection timestamps as the zero point, normalize the response timestamps in the baseline and target event chain response data to obtain baseline normalized response data and target normalized response data. Match response records belonging to the same field event in the baseline and target normalized response data according to the node order and point identifiers in the field event causal chain to generate node response alignment results. Calculate the node order offset and node time offset of the target operating system relative to the baseline operating system based on the node response alignment results to generate a time-series offset node set. Based on the node type in the set of time-series offset nodes, the time-series offset nodes are mapped to the acquisition task phase, communication buffer threshold, alarm scan cycle, event sequence record temporary storage window, event sequence record sorting rule, linkage trigger waiting time and status readback matching window to generate adaptation processing data; based on the adaptation processing data, the SCADA configuration project running parameters in the target operating system are updated to generate the adapted SCADA configuration project.
2. The industrial software compatibility adaptation method according to claim 1, characterized in that, The method for generating the causal chain of on-site events includes: Extract the point identifier and collection period from the point acquisition relationship to generate point event source nodes indexed by the point identifier; generate alarm nodes according to the point identifier and alarm triggering conditions in the alarm triggering relationship, and establish a first directed edge from the point event source node to the alarm node; generate event sequence recording nodes according to the point identifier and recording triggering conditions in the event sequence recording relationship, and establish a second directed edge from the point event source node to the event sequence recording node. The composite triggering conditions in the linkage action relationship are decomposed into atomic conditions to obtain atomic condition nodes; the atomic condition nodes containing point identifiers are bound to the corresponding point event source nodes; the linkage actions are extracted from the linkage action relationship to generate linkage action nodes; logical intermediate nodes are generated according to the logical operation relationship in the composite triggering conditions, and linkage directed edges are established between atomic condition nodes, logical intermediate nodes and linkage action nodes. Based on the state readback relationship, extract the readback points corresponding to the linkage action nodes, generate state readback nodes, and establish readback directed edges from the linkage action nodes to the state readback nodes; based on the acquisition period, alarm delay, event sequence recording resolution, linkage trigger waiting time and state readback matching window, configure edge timing constraints for the first directed edge, the second directed edge, the linkage directed edge and the readback directed edge, and generate the on-site event causal chain.
3. The industrial software compatibility adaptation method according to claim 2, characterized in that, The method for generating a field event excitation sequence with event injection timestamps based on the triggering conditions, acquisition period, alarm delay, event sequence recording resolution, and linkage triggering waiting time in the field event causal chain includes: Extract the path extending from the point event source node to the non-point node from the on-site event causal chain to generate the target event sub-chain; the non-point nodes include alarm nodes, event sequence record nodes, linkage action nodes and status readback nodes; Based on the edge timing constraint values corresponding to the target event subchain, determine the boundary time corresponding to each edge timing constraint; based on the point event source nodes, atomic condition nodes, and logical intermediate nodes in the target event subchain, determine the set of point event source nodes participating in the same target event subchain, and extract the point identifier and trigger value from the trigger conditions corresponding to the target event subchain; Based on the edge timing constraint value and the preset disturbance ratio, set the pre-boundary time marker and post-boundary time marker before and after the boundary time, and use the boundary time as the boundary time marker; generate a point change event group based on the point identifier, trigger value, pre-boundary time marker, boundary time marker, and post-boundary time marker; Based on the synchronization satisfaction relationship corresponding to the logical intermediate node, position change events at different points within the position change event group are configured with the same event injection time stamp; based on the alternative satisfaction relationship corresponding to the logical intermediate node, position change events at different points within the position change event group are configured with different event injection time stamps; the position change event group is arranged according to the node order in the target event sub-chain to generate a field event excitation sequence with event injection time stamps.
4. The industrial software compatibility adaptation method according to claim 3, characterized in that, The method for matching response records belonging to the same on-site event in the baseline normalized response data and the target normalized response data according to the node order and location identifier in the causal chain of the on-site event to generate node response alignment results includes: The event injection time stamp, location identifier, and trigger value are extracted from each entry of the field event excitation sequence to generate a field event identifier. Based on the location identifier in the field event identifier and the node identifier associated with the location identifier in the field event causal chain, response records corresponding to the field event identifier and whose normalized response time stamps fall into a preset matching window are extracted from the baseline normalized response data and the target normalized response data to generate a baseline response record group and a target response record group. Based on the source module identifier of the response record, the baseline response record group and the target response record group are respectively divided into point acquisition response record, alarm response record, event sequence record response record, linkage action response record and status readback response record; according to the node order in the cause-and-effect chain of the on-site event, the baseline response record and the target response record of the same node type are respectively arranged in ascending order by normalized response time scale; Within the same node type, the baseline response record and the target response record with the smallest absolute value of the normalized response time difference that is not greater than a preset matching threshold are paired with the baseline response record and the target response record. The baseline response record and the target response record that do not form a pair are marked as unmatched response records. The node response alignment result is generated based on the pair of response records and the unmatched response records.
5. The industrial software compatibility adaptation method according to claim 4, characterized in that, The method for mapping time-series offset nodes to acquisition task phases, communication buffer thresholds, alarm scan cycles, event sequence record temporary storage windows, event sequence record sorting rules, linkage trigger waiting times, and status readback matching windows based on the node types in the time-series offset node set, and generating adaptive processing data includes: From the node response alignment results corresponding to the time-series offset node set, obtain the node type, node time offset, node sequence offset, and unmatched response record marker to generate node offset features; According to the node order in the causal chain of the on-site event, the time-series offset node is compared with the adjacent upstream node to determine the offset source type of the time-series offset node; the offset source type includes the offset processed by this node and the offset transmitted upstream; when the offset source type is the offset transmitted upstream, the adjacent upstream node with the smallest offset increment in the offset transmission comparison result is marked as the offset source node of the time-series offset node. When the offset source type is "this node processing offset", corresponding adjustment items are generated according to the node type; when the node type is "point event source node", acquisition task phase adjustment item and communication buffer threshold adjustment item are generated; when the node type is "alarm node", alarm scan cycle adjustment item is generated; when the node type is "event sequence record node", event sequence record temporary storage window adjustment item and event sequence record sorting rule adjustment item are generated; when the node type is "linked action node", linkage trigger waiting time adjustment item is generated; when the node type is "status readback node", status readback matching window adjustment item is generated. Based on the node offset characteristics, the adjustment items corresponding to the offset processed by this node, and the offset source node corresponding to the upstream transmitted offset, adaptation processing data is generated.
6. The industrial software compatibility adaptation method according to claim 5, characterized in that, The method for determining the offset source type of a time-series offset node by comparing its offset propagation with that of its adjacent upstream nodes according to the node order in the causal chain of the on-site event includes: Based on the causal chain of the on-site events, extract the set of adjacent upstream nodes of the time-series offset node; extract the node time offset, node sequence offset, and unmatched response record marker of each adjacent upstream node in the time-series offset node and the set of adjacent upstream nodes from the node response alignment result; Based on the edge timing constraint values of the connection timing offset node and the adjacent upstream node, as well as the preset tolerance coefficient, determine the allowable propagation offset range; calculate the offset increment between the node time offset of the timing offset node and the node time offset of each adjacent upstream node. When there is an offset increment that falls within the allowed transmission offset range, the node sequence offset direction determined by the node sequence offset is consistent, and neither the temporal offset node nor the adjacent upstream node has an adjacent upstream node with an unmatched response record, the offset source type of the temporal offset node is determined to be upstream transmission offset. When there is no node that simultaneously satisfies the conditions that the offset increment falls within the allowed offset range, the node sequence offset direction is consistent, and neither the time-series offset node nor its adjacent upstream node has an unmatched response record, the offset source type of the time-series offset node is determined to be the offset processed by this node.
7. The industrial software compatibility adaptation method according to claim 5, characterized in that, The method for generating adaptation processing data based on the node offset characteristics, the adjustment item corresponding to the current node's processed offset, and the offset source node corresponding to the upstream transmitted offset includes: Using the time-series offset node corresponding to the offset processed by this node as the adjustment reference node, the set of affected downstream nodes is determined based on the directed edges starting from the adjustment reference node in the causal chain of the on-site events. Based on the edge timing constraint value of each node in the affected downstream node set, the current parameter value of the corresponding adjustment item, and the preset safety coefficient, the parameter safety boundary of the corresponding adjustment item is determined; based on the node time offset, node sequence offset, and parameter response polarity of the corresponding adjustment item in the node offset features, the adjustment direction and candidate adjustment magnitude of the corresponding adjustment item are determined; based on the current parameter value, adjustment direction, and candidate adjustment magnitude, candidate parameter values are obtained. When a candidate parameter value falls within the parameter safety boundary, the candidate adjustment range is retained; when a candidate parameter value exceeds the parameter safety boundary, the candidate adjustment range is corrected based on the difference between the boundary value corresponding to the adjustment direction in the parameter safety boundary and the current parameter value; and adaptation processing data is generated based on the adjustment items for retaining the candidate adjustment range, the adjustment items for correcting the candidate adjustment range, and the offset source node.
8. An industrial software compatibility adaptation system, used to perform the method according to any one of claims 1 to 7, characterized in that, The system includes: The causal chain construction module is used to obtain the SCADA configuration project in the industrial software to be adapted; it parses the point acquisition relationship, alarm trigger relationship, event sequence recording relationship, linkage action relationship and status readback relationship in the SCADA configuration project to generate the causal chain of field events. The critical excitation generation module is used to generate a field event excitation sequence with event injection timestamps based on the triggering conditions, acquisition cycle, alarm delay, event sequence recording resolution, and linkage trigger waiting time in the field event causal chain. The response offset analysis module is used to deploy the SCADA configuration project on the base operating system and the target operating system respectively. It inputs point change events according to the event injection timestamps in the field event excitation sequence, and collects base event chain response data and target event chain response data with response timestamps. Using the event injection timestamps as the zero point, it normalizes the response timestamps in the base event chain response data and target event chain response data to obtain base normalized response data and target normalized response data. According to the node order and point identifiers in the field event causal chain, it matches response records belonging to the same field event in the base normalized response data and target normalized response data to generate node response alignment results. Based on the node response alignment results, it calculates the node order offset and node time offset of the target operating system relative to the base operating system, generating a time-series offset node set. The adaptation data generation module is used to map the time-series offset nodes to the acquisition task phase, communication buffer threshold, alarm scan cycle, event sequence record temporary storage window, event sequence record sorting rules, linkage trigger waiting time and status readback matching window according to the node type in the time-series offset node set, and generate adaptation processing data; and update the SCADA configuration project running parameters in the target operating system according to the adaptation processing data to generate the adapted SCADA configuration project.
