A method and system for monitoring and controlling timing conflicts of start and stop of flour production line equipment

Abstract

The application relates to the technical field of centralized control, and discloses a flour production line equipment start-stop timing conflict monitoring control method and system. A centralized control node acquires production line data, establishes equipment linkage topology, determines a current timing node, and sorts and checks concurrent start-stop instructions; temporary operation states are formed by copying equipment states and path loads, the checked instructions are deduced item by item, load changes caused by target actions are written into and rewritten into path loads along material receiving directions, and when path loads are excessive, conflict propagation paths are formed and associated equipment is determined; the instructions are intercepted, delayed and released, only the corresponding equipment start-stop of the released instructions is controlled; actual start-stop states and actual loads are collected and compared with deduction results, when the actual start-stop states and actual loads are consistent with the deduction results, a control reference is updated, when the actual start-stop states and actual loads are inconsistent with the deduction results, associated instructions are suspended from being executed, timing nodes are rebuilt, and start-up and shutdown sets are allowed. The application can identify cross-equipment receiving conflicts caused by concurrent start-stop instruction superposition, and limit the influence range of execution deviation.

Description

Technical Field

[0001] This invention relates to the field of centralized control technology, specifically to a method and system for monitoring and controlling start-up and shutdown sequence conflicts of grinding production line equipment. Background Technology

[0002] A grinding mill production line typically consists of multiple devices connected in series, with material receiving relationships. The start-up and shutdown of each device are affected not only by its own status but also by the output status of upstream devices, the receiving capacity of downstream devices, the material transfer location, and the current load status. To maintain continuous processing, a centralized control node needs to implement unified scheduling of multiple physical devices based on production tasks and equipment status.

[0003] Existing centralized control schemes typically employ fixed start / stop sequences, static interlocking conditions, permitted start / stop sets, and single-item load limits to verify start / stop commands. If a command does not meet the current state, pre-start / stop conditions, or load acceptance conditions, the corresponding action is blocked. Some schemes also control related equipment according to preset routes and procedures.

[0004] However, when multiple start / stop commands arrive concurrently within the same control cycle, the fact that each command individually meets the static conditions does not guarantee that their sequential superposition will still meet the material receiving requirements. Changes in equipment status and path load caused by preceding actions will alter the executable conditions of subsequent commands. If the same temporary operating state is not continuously written back, it is difficult to identify cross-equipment receiving conflicts caused by accumulated material load. When the actual execution result differs from the projection result, continuing to release unexecuted commands based on the original projection state will cause the control baseline to fail, while indiscriminately stopping all commands will expand the scope of impact.

[0005] The information disclosed in this background section is intended only to enhance the understanding of the overall background of the invention and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0006] This invention provides a method and system for monitoring and controlling start-up and shutdown sequence conflicts in grinding production line equipment. It addresses the problems of existing centralized control schemes, which, after multiple concurrent start-up and shutdown commands have been statically verified, struggle to identify cross-equipment conflicts caused by the accumulation of equipment status and path load along the material receiving direction caused by the preceding action and superimposed on subsequent actions. Furthermore, when the actual execution results differ from the deduced results, subsequent unexecuted commands may still be released based on the failure control benchmark, and indiscriminately stopping all commands would expand the scope of impact.

[0007] The technical solution of this invention is as follows: On the one hand, this invention provides a method for monitoring and controlling start-up and shutdown timing conflicts of grinding production line equipment, including: acquiring production line data scheduled by a centralized control node; establishing an equipment linkage topology according to the material receiving direction, load transfer sequence, and pre-start / stop states to form a set of allowed start-up and shutdown operations and load receiving constraints; determining the current timing node based on equipment status changes, load values, and load transfer locations; sequentially sorting and issuing start-up and shutdown commands according to priority identifiers and arrival times to form a sequence of commands to be verified, and verifying them based on the allowed action range, pre-start / stop states, and load receiving constraints of the current timing node; copying the equipment status and path load of the current timing node to form a temporary operating state; deriving the commands that pass the verification item by item; for each deduction, writing the load change generated by the target action along the material receiving direction into the path load, and writing back the temporary equipment status, Path load serves as the basis for subsequent extrapolation. When the path load exceeds the rated capacity of the equipment, the conflict propagation path is determined along the load transmission direction, and associated equipment is identified by path nodes. Timing conflicts are identified based on cumulative extrapolation. Instructions that fail verification are intercepted, and retained and delayed instructions are determined according to the priority identifiers of each conflicting instruction. The remaining instructions that do not cause timing conflicts are released. According to the cumulative extrapolation order, only instructions with release identifiers are generated as target execution instructions to control the start and stop of the equipment. The actual start and stop status and actual load value of the target equipment and associated equipment corresponding to the executed target execution instructions are collected and compared with the extrapolation results. If they are consistent, the current timing node is updated with the valid temporary equipment status and valid path load corresponding to the release instruction as the basis for subsequent verification. If they are inconsistent, the unexecuted associated instructions are suspended, and the timing node and allowed start and stop sets are reconstructed according to the actual status and load value.

[0008] Furthermore, the establishment of the equipment linkage topology includes: extracting the equipment identifier, material input end, material output end, load flow direction, and rated capacity from the production line data; using the equipment identifier as a node, the material receiving relationship between the equipment as a directed connection, and determining the sequential relationship of each directed connection according to the load transmission order; associating the allowed start / stop status, start / stop preconditions, and rated capacity of each node with the equipment linkage topology.

[0009] Further, determining the current time sequence node includes: arranging the operating status and corresponding load value of each device according to the sampling time to form a state-load sequence; matching the state-load sequence with the preset device state combination and load transfer boundary of each operating stage to determine the current operating stage; and within the current operating stage, determining the current time sequence node based on the device node corresponding to the most recent state change and the load arrival position.

[0010] Furthermore, the process of forming a sequence of instructions to be verified includes: parsing the target device, target action, arrival time, and priority identifier in each concurrent start / stop instruction; first determining the order of instructions with different priorities according to the priority identifier, and then determining the order of instructions with the same priority according to the arrival time; when two instructions point to the same target device and the target actions are opposite, the instruction that arrives later is marked as an instruction to be verified in conflict.

[0011] Furthermore, the verification of the pre-start / stop state and load-bearing constraints includes: extracting the pre-start and post-start state of the target device from the device linkage topology, and determining whether they meet the pre-start / stop state corresponding to the target action; determining the load change after the target device starts / stops based on the target action, and including the load change in the expected load of each adjacent device along the material receiving direction; comparing the expected load of each adjacent device with its rated load-bearing capacity one by one to obtain the verification result of the load-bearing constraints.

[0012] Furthermore, the step-by-step deduction of the verified instructions includes: copying the device state and path load corresponding to the current timing node to form the temporary operating state; according to the sequence of instructions to be verified, for each verified instruction, copying the candidate state from the previous valid temporary operating state, changing the temporary start / stop state of the target device in the candidate state, and updating the candidate path load along the device linkage topology; when the candidate state does not generate timing conflicts, writing the candidate temporary device state and candidate path load back as a new valid temporary operating state as the basis for the deduction of the next instruction; when the candidate state generates timing conflicts, retaining the conflict snapshot and not writing the candidate state back, until all verified instructions are completed.

[0013] Furthermore, the determination of associated devices includes: when concurrent start / stop commands cause the same device to have opposite target actions at the same timing node, the target device is included in the associated devices; when the start / stop of the target device causes at least one of the following: the upstream device cannot output materials, or the downstream device cannot accept materials, the target device and the corresponding upstream and downstream devices are included in the associated devices; when the path load exceeds the rated capacity of any device, a conflict propagation path is determined along the load transmission direction, and the nodes on the conflict propagation path are included in the associated devices.

[0014] Furthermore, the interception, delay, and release include: generating a direct interception flag for concurrent start / stop instructions that fail to pass at least one of the checks on the allowed action range, start / stop pre-state, and load bearing constraints; for concurrent start / stop instructions that pass the aforementioned checks but cause timing conflicts in the simulation, determining the reserved instructions according to the priority flags of each concurrent start / stop instruction, generating a release flag for the reserved instructions, and generating a delayed execution flag for the remaining conflicting instructions; generating a release flag for the remaining concurrent start / stop instructions that do not cause timing conflicts, and only including instructions with release flags in the target execution instructions of this round.

[0015] Furthermore, the acquisition of actual start / stop status and actual load value includes: acquiring the operating status data of the target device corresponding to the executed target execution instruction and the associated devices affected by it; extracting the actual start / stop status of the corresponding device from the operating status data; acquiring the current fluctuation value of the corresponding device in the actual start / stop status; and determining the actual load value of the corresponding device based on the current fluctuation value.

[0016] On the other hand, the present invention also provides a monitoring and control system for start-up and shutdown timing conflicts of grinding production line equipment, characterized in that it includes: a linkage reference module, used to acquire production line data scheduled by the centralized control node, establish equipment linkage topology, form a set of allowed start-up and shutdown operations and load-bearing constraints, and determine the current timing node based on equipment status changes, load values, and load transfer locations; a concurrent command verification module, used to sequentially sort and concurrently issue start-up and shutdown commands according to priority identifiers and arrival times, form a sequence of commands to be verified, and verify them based on the allowed action range of the current timing node, the pre-start-up and shutdown states, and load-bearing constraints; and a status deduction and conflict identification module, used to copy the equipment status and path load of the current timing node to form a temporary operating state, deduce the commands that pass the verification item by item, and write the load change generated by the target action along the material receiving direction into the path load for each deduction, and write back the temporary equipment status and path load. As the basis for subsequent extrapolation, when the path load exceeds the rated capacity of the equipment, the conflict propagation path is determined along the load transmission direction, the associated equipment is identified by the path nodes, and the timing conflict is identified based on the cumulative extrapolation. The differential control module is used to intercept instructions that fail the verification, determine the retained instructions and delayed instructions according to the priority identifier of each conflicting instruction, and release the remaining instructions that do not cause timing conflicts. According to the cumulative extrapolation order, only the instructions with the release identifier are used to generate target execution instructions to control the start and stop of the equipment. The feedback reconstruction module is used to collect the actual start and stop status and actual load value of the target equipment and associated equipment corresponding to the executed target execution instructions, and compare them with the extrapolation results. If they are consistent, the current timing node is updated with the effective temporary equipment status and effective path load corresponding to the release instruction as the subsequent verification benchmark. If they are inconsistent, the unexecuted associated instructions are suspended, and the timing node and the allowed start and stop sets are reconstructed according to the actual status and load value.

[0017] The beneficial effects of this invention are as follows: This invention establishes a device linkage topology and current timing nodes to form a dynamic control benchmark shared by multiple physical devices. In the same temporary operating state, the temporary device status and path load are updated sequentially according to concurrent instructions, making the result of the previous instruction the basis for the deduction of the subsequent instruction. When the path load exceeds the rated capacity, a conflict propagation path is formed along the load transmission direction, and associated devices are identified by path nodes. This allows for the identification of cross-device load conflicts caused by the superposition of multiple actions before the instruction is issued. By intercepting, delaying, and releasing instructions, only instructions with release flags are executed. The actual start / stop status and actual load are compared with the deduction results. If they match, the control benchmark is updated; if they do not match, only unexecuted instructions within the associated range are suspended, and the control benchmark is rebuilt according to the actual data. This avoids continuing to release instructions based on the failure state and limits the impact range of execution deviations. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the overall process of the grinding production line equipment start-up and shutdown sequence conflict monitoring and control method provided in one embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the device linkage topology, load transmission direction, and current timing node formation relationship provided in one embodiment of the present invention; Figure 3 This is a schematic diagram of the sequential deduction of the same temporary running state and the continuous write-back of path load provided in one embodiment of the present invention; Figure 4 This is a schematic diagram of the conflict propagation path, associated device determination, and differential control process provided in one embodiment of the present invention; Figure 5 This is a schematic diagram of the start-stop timing conflict monitoring and control system module and flow direction of a grinding production line equipment provided in one embodiment of the present invention. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only for explaining the invention and are not intended to limit the invention; that is, the described embodiments are merely some embodiments of the invention, and not all embodiments. The components of the embodiments of the invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0020] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0021] It should be noted that relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0022] As mentioned earlier, multiple devices in a grinding production line operate continuously along the material receiving direction. The start-up and shutdown of each device are affected not only by its own state but also by the output state of upstream devices, the receiving capacity of downstream devices, the material transfer location, and the current load state. When multiple start-up and shutdown commands arrive concurrently within the same control cycle, the individual static conditions of each command do not necessarily mean that the material receiving requirements will still be met after being superimposed in the order of their arrangement. When the device state and path load generated by the preceding command are not continuously written back to the same temporary operating state, it is difficult to identify the cross-device timing conflicts formed by the accumulation of material load along the receiving direction. When the actual execution results of the physical equipment are inconsistent with the projected results, continuing to use the original projected results to release commands that have not yet been executed will also render the control baseline invalid.

[0023] To address this issue, the present invention provides a method and system for monitoring and controlling start-up and shutdown sequence conflicts in a grinding production line. A centralized control node establishes the equipment linkage topology and current sequence nodes based on production line data. Concurrent start-up and shutdown commands are sorted and statically verified. In the same temporary operating state, the path load generated by the target action is written back item by item. When the path load exceeds the rated capacity, a conflict propagation path is formed and the associated equipment is identified. Subsequently, commands are intercepted, delayed, or released. Only release commands are sent to the physical equipment, and the actual start-up and shutdown states and actual loads of the physical equipment are used to compare the effective projection results. If the feedback is inconsistent, only commands not yet executed within the scope of the conflict propagation path and associated equipment are suspended, and subsequent control benchmarks are reconstructed according to the actual results.

[0024] The following is combined with Figures 1 to 5This invention is described in detail.

[0025] Example 1: like Figure 1 As shown in the embodiment of the present invention, a method for monitoring and controlling start-up and shutdown timing conflicts of grinding production line equipment is provided. The executing entity can be a centralized control node that is communicatively connected to multiple physical devices in the grinding production line. The method mainly includes the following steps: S100: Obtain production line data from the centralized control node scheduling, establish equipment linkage topology according to material receiving direction, load transfer sequence and start / stop pre-state, and form a set of allowed start / stop and load receiving constraints. S200: Determine the current timing node based on changes in equipment status, load value, and load transfer location; S300: Order start and stop commands sequentially according to priority identifier and arrival time to form a sequence of commands to be verified, and verify them according to the allowable action range of the current timing node, the pre-start and stop status and load bearing constraints. S400: Copy the current timing node's equipment status and path load to form a temporary operating status. Perform item-by-item simulations of the verified instructions. For each simulation, write the load change generated by the target action into the path load along the material receiving direction, and write back the temporary equipment status and path load as the basis for subsequent simulations. When the path load exceeds the equipment's rated capacity, determine the conflict propagation path along the load transmission direction, identify the associated equipment by the path node, and identify timing conflicts based on the cumulative simulations. S500: Intercept commands that fail verification, determine the retained and delayed commands according to the priority identifier of each conflicting command, and release the remaining commands that do not cause timing conflicts; according to the cumulative deduction order, only the commands with the release identifier are used to generate the target execution command to control the start and stop of the equipment. S600: Collect the actual start / stop status and actual load value of the target device and associated devices corresponding to the executed target execution instructions, and compare them with the simulation results. If they are consistent, update the current timing node with the valid temporary device status and valid path load corresponding to the release instruction as the subsequent verification benchmark. If they are inconsistent, suspend the unexecuted associated instructions, and rebuild the timing node and the allowed start / stop set according to the actual status and load value.

[0026] Based on the above steps, the present invention forms a unified control benchmark by using the device linkage topology and the current timing node, continuously writes back the temporary device status and path load generated by the previous instruction and uses it as the basis for subsequent inference, and then limits the pause range of associated devices and execution deviations by using the conflict propagation path formed by the overload, so that the verification, entity execution and feedback reconstruction of concurrent start and stop instructions form a continuous control chain.

[0027] Example 2: To provide a more detailed explanation of the technical solutions provided in the above embodiments, the present invention also provides Embodiment Two. In Embodiment Two, the centralized control node divides the control cycle according to the existing scheduling configuration. The control cycle is derived from the cyclic scheduling cycle (e.g., 1 second) of the centralized control program of the production line. The production line data and concurrent start / stop instructions obtained within the same control cycle correspond to the equipment identifier, instruction identifier, sampling time, and topology version, and the following processes are executed sequentially.

[0028] Specifically, such as Figure 2 As shown, in this second embodiment, the establishment of the device linkage topology and the determination of the current timing node in steps S100 and S200 may include: S110. Extract the equipment identifier, material input end, material output end, load flow direction and rated capacity from the production line data; S120. Using equipment identifiers as nodes, material receiving relationships between equipment as directed connections, and determining the order of each directed connection according to the load transfer sequence. S130. Associate the allowed start / stop status, start / stop preconditions, and rated capacity of each node with the device linkage topology. After establishing the device linkage topology, the current timing node is further determined based on the device linkage topology and the collected device operating status, load value, and load transfer location. Specifically, this includes: S210. Arrange the operating status and corresponding load value of each device according to the sampling time to form a status-load sequence; S220. Match the state load sequence with the preset equipment state combinations and load transfer boundaries for each operating stage to determine the current operating stage; S230. During the current operating phase, the current timing node is determined based on the device node corresponding to the most recent state change and the location of the load arrival.

[0029] For example, steps S110 to S130 and steps S210 to S230 may further include the following processes: First, the sampling period for continuous operation data is determined by the existing data acquisition configuration of the production line (e.g., 0.2s), and the data validity period is jointly determined by the sampling period and the control period (e.g., 2 control periods). Centralized control nodes form node records based on equipment identifiers and directed connection records based on the connection relationship between the material output end and the material input end of the next equipment. The load transfer sequence, permitted start-up status, permitted shutdown status, pre-start status, pre-shutdown status, and rated load capacity are written into the corresponding nodes or connections. The rated load capacity is derived from equipment design parameters, nameplate parameters, or confirmed control configurations (e.g., the rated load capacity of node C is 8t / h). The rated load capacity, current load, expected load, path load, and actual load of the same node use the same equivalent material load capacity unit.

[0030] Secondly, the centralized control node arranges the operating status and corresponding load values ​​of each device in ascending order according to the sampling time. The original operating status can be uniformly mapped to comparable status codes such as starting, running, stopping, and stopping, according to the existing status definition of the production line. When there are duplicate records for the same device at the same sampling time, only the record with a valid data quality identifier and updated time is retained, and the average of contradictory start and stop states is not taken. The preset device status combinations and load transfer boundaries for each operating stage are derived from the existing sequence control configuration and material transfer relationships of the production line. The load transfer position is the current material migration position recorded by the production line data, the load arrival position is the specific equipment receiving position corresponding to the load transfer position in the current operating stage, and the load transfer boundary is a preset position condition used to determine whether the material enters or leaves the receiving area of ​​a specific equipment, for example, the material input side of device B.

[0031] Then, in a preferred embodiment, the currently active material receiving route of the grinding production line is A→B→C→D, and there is also an independent route E→F that does not share material receiving nodes with this route. The centralized control node reads the equipment identifier, input terminal, output terminal, and load flow direction of equipment A to equipment F from the continuous operation data, and registers A to B, B to C, C to D, and E to F as directed connections using A, B, C, D, E, and F as nodes, and writes the load transfer sequence number sequentially according to the material receiving direction. The rated receiving capacities of nodes B, C, and D are 10t / h, 8t / h, and 10t / h, respectively, and the nodes and connections are jointly associated with topology version V1 and valid identifier.

[0032] Subsequently, following this scenario, devices A and B are in a standby state within the current sampling window, while devices C and D are in an operating state. The current path loads of nodes B, C, and D are 5t / h, 6t / h, and 4t / h, respectively. The centralized control node arranges the above states and loads according to the sampling time to form a state-load sequence, and matches it item by item with the operating phase template. The state combination corresponds to the operating phase of "downstream device is running, upstream device is standby," the load arrival position is located on the material input side of device B, and the most recent state change corresponds to device A.

[0033] Finally, the centralized control node combines the operation phase identifier, the input side positions of device A and device B, and topology version V1 into the current timing node N1. N1 indexes the allowed start set, allowed stop set, start / stop pre-states, and load-bearing constraints, serving as the static verification benchmark for step S300 and the initial benchmark for copying the temporary operation state in step S400. If the rated load capacity field of device C is missing, the valid identifier for route B→C is invalid, multiple operation phases match simultaneously and cannot be distinguished by the load transfer location, or the most recent state change cannot correspond to a topology node, then a new current timing node is not submitted, and the relevant instructions remain unreleased until valid data is recovered, and S110 to S130 and S210 to S230 are re-executed.

[0034] Based on the aforementioned equipment linkage benchmark and current timing node, in this second embodiment, step S300, the concurrent start / stop instruction sorting and static verification may include: S310. Parse the target device, target action, arrival time, and priority identifier in each concurrent start / stop command; S320. First, determine the order of different priority instructions according to the priority identifier, and then determine the order of instructions with the same priority according to the arrival time. S330. When two instructions are directed to the same target device and the target actions are opposite, the instruction that arrives later is marked as a conflict-checking instruction. S340. Extract the preceding device status and subsequent device status of the target device from the device linkage topology, and determine whether they meet the start / stop preceding status corresponding to the target action. S350. Determine the load change after the target equipment starts and stops based on the target action, and include the load change in the expected load of each adjacent equipment along the material receiving direction. S360. Compare the expected load of each adjacent device with its rated capacity one by one to obtain the verification result of the load bearing constraint.

[0035] For example, steps S310 to S360 may further include the following processes: First, each concurrent start / stop instruction must record at least the instruction identifier, target device, target action, arrival time, priority identifier, and control cycle identifier. The resolution of the arrival time comes from the clock of the centralized control node and the instruction reception record (e.g., 1ms); the priority comes from the levels already configured for the production task (e.g., high, medium, low). Instructions with different priorities are first arranged by level, and instructions with the same priority are then arranged by arrival time. When arrival times are the same, the order is maintained by the reception sequence number.

[0036] Secondly, the centralized control node performs static verification item by item based on the permissible action range, upstream equipment status, downstream equipment status, and load capacity constraints indexed by N1. The load change generated by the target action comes from the current load of the target equipment, the load corresponding to the target start / stop state, and the currently activated material route (for example, the equivalent load change of instruction I1 is 1.5t / h), and is uniformly converted into units consistent with the rated capacity of adjacent equipment. If any permissible action range, start / stop upstream status, or load capacity constraint is not met, the corresponding instruction generates a direct interception flag; if at least one of the following occurs—missing field, non-existent target equipment, invalid topology version, or unreliable load unit conversion—the relevant instruction is not released.

[0037] Then, in a preferred embodiment, the allowed start set corresponding to N1 includes devices A, B, and E, and the allowed stop set includes devices C and D. The centralized control node receives instructions I1, I2, and I3 within the same control cycle: I1 requests device A to start, with high priority and arriving first; I2 requests device B to start, with medium priority; and I3 requests independent route device E to start, with low priority. The centralized control node sequentially parses the target device, target action, arrival time, and priority identifier of the three instructions to form a sequence of instructions to be verified: I1, I2, and I3.

[0038] Subsequently, during the static verification of I1, both equipment C and D were in an operating state capable of handling materials. The 1.5t / h load change corresponding to the start-up of equipment A was included in the expected loads of nodes B, C, and D, resulting in 6.5t / h, 7.5t / h, and 5.5t / h, respectively, all of which did not exceed the corresponding rated capacity. During the static verification of I2, the 1.2t / h load change corresponding to the start-up of equipment B was included in the expected loads of nodes C and D, resulting in 7.2t / h and 5.2t / h, which also did not exceed the corresponding rated capacity. I3 meets the allowable operating range and start / stop preconditions for the independent route E→F.

[0039] Finally, I1, I2, and I3 all form ordered instructions that have passed static verification and proceed to step S400. If another instruction I4 arrives later, requesting device A to stop, then I4 is marked as an instruction to be checked for conflict; whether I4 constitutes a conflict of opposite actions in the same timing node is determined by the temporary device state after the result of I1 is written back. If the target device field of I2 is missing, or if the rated capacity of node C and the expected load have not yet been unified in terms of units, then I2 remains unreleased and does not proceed to step S400.

[0040] like Figure 3 As shown, after completing the concurrent start / stop instruction sorting and static verification, in this second embodiment, step S400, the item-by-item deduction and path load write-back of the same temporary running state may include: S410. Copy the device status and path load corresponding to the current time node to form the temporary operating state; S420. According to the sequence of instructions to be verified, for each instruction that passes verification, copy the candidate state from the previous valid temporary operating state, change the temporary start / stop state of the target device in the candidate state, and update the candidate path load along the device linkage topology. S430. When no timing conflict occurs in the candidate state, the candidate temporary device state and candidate path load are written back as new valid temporary running states as the basis for the deduction of the next instruction. When a timing conflict occurs in the candidate state, the conflict snapshot is retained and the candidate state is not written back until all instructions that have passed the verification are completed.

[0041] For example, steps S410 to S430 may further include the following processes: First, the centralized control node copies the device state and path load corresponding to N1 to form an initial valid temporary state T(0). For the first instruction in the sequence to be verified... The instruction first copies the candidate state from the previous valid temporary state, changes the temporary start / stop state of the target device within the candidate state, and writes the load change generated by the target action to each affected node along the currently active material receiving route. Node In the The path load derived from the instruction is formed according to the following formula: in, For the first After the instruction is deduced, the node is... The path load, in t / h or other equivalent material load units consistent with the node's rated load capacity; The load of the previous valid path that did not cause a conflict and has already been written back; For the first The project's target action is transmitted to the node along the currently activated material receiving route. The equivalent load change originates from the current state of the target device, the state corresponding to the target action, and the current route configuration. The path load output by this formula, together with the temporary device state, constitutes the candidate state; only when the candidate state input is valid and no conflict occurs is it written back as a new valid temporary state and used as the basis for the derivation of the next instruction.

[0042] Secondly, candidate states and valid temporary states are distinguished. Candidate states can record device state changes, path load changes, and anomaly flags caused by this instruction. However, if a candidate state exhibits at least one of the following: reverse action of the same device, mismatch between preceding and following devices, excessive path load, or invalid input data, only a conflict snapshot is saved, and it is not submitted as a new valid temporary state. The estimated load of adjacent devices formed during the static verification phase does not replace the cumulative extrapolation performed along the complete activation route in this step.

[0043] Then, in a preferred embodiment, the centralized control node copies the device state corresponding to N1 and the path loads of nodes B, C, and D (5t / h, 6t / h, and 4t / h, respectively) to form T(0). When deducing I1, candidate state Tc(1) is copied using T(0), the temporary state of device A is changed to start, and a load change of 1.5t / h is written along A→B→C→D respectively. After substituting the above path load relationship, the candidate path loads of nodes B, C, and D are 6.5t / h, 7.5t / h, and 5.5t / h, respectively.

[0044] Subsequently, the candidate state input of I1 is valid, and no reverse action, mismatch, or overload occurs. Therefore, Tc(1) is written back as a valid temporary state T(1). When continuing to extrapolate I2, Tc(2) must be copied from T(1) instead of T(0), the temporary state of device B is changed to start, and a load change of 1.2t / h is written along B→C→D to obtain the candidate path loads of nodes C and D as 8.7t / h and 6.7t / h, respectively. This candidate result, along with I2, target device B, load change of 1.2t / h, and the current topology version V1, is sent to steps S440 to S460 for overload judgment and conflict propagation path determination.

[0045] Finally, before the candidate state of I2 is submitted, T(1) remains the only valid temporary state. Therefore, I3 subsequently copies the candidate state from T(1) and performs the deduction in the independent route E→F, without accepting the conflicting candidate load of I2. If the units of path load, rated capacity, or load change are inconsistent, or the currently active route is unclear, this numerical update will not be performed, the relevant instructions will be marked as invalid deduction input and will remain unreleased, and after reliable conversion or route confirmation, it will re-enter S410 to S430.

[0046] like Figure 4As shown, following the step-by-step deduction results of the same temporary operating state, in this second embodiment, the determination of the conflict propagation path, associated devices, and differentiated results in steps S400 and S500 may include: S440. When concurrent start / stop commands cause the same device to have opposite target actions at the same timing node, the target device is included in the associated devices. S450. When the start-up or shutdown of the target equipment causes the upstream equipment to be unable to output materials or the downstream equipment to be unable to accept materials, the target equipment and the corresponding upstream and downstream equipment shall be listed as associated equipment. S460. When the path load exceeds the rated capacity of any device, determine the conflict propagation path along the load transmission direction and list the nodes on the conflict propagation path as associated devices. After determining the conflict propagation path and associated devices, a differentiated processing identifier is further generated based on the static verification results and cumulative simulation results of each concurrent start / stop command. Specifically, this includes: S510. Generate a direct interception flag for concurrent start / stop commands that fail to pass at least one of the verification criteria: permitted action range, start / stop pre-state, and load bearing constraints. S520. For concurrent start-stop instructions that pass the aforementioned verification but cause timing conflicts in the simulation, determine the reserved instructions according to the priority identifier of each concurrent start-stop instruction, generate a release identifier for the reserved instructions, and generate a delayed execution identifier for the remaining conflicting instructions. S530: Generate release flags for the remaining concurrent start / stop instructions that do not cause timing conflicts.

[0047] For example, steps S440 to S460 and steps S510 to S530 may further include the following processes: First, nodes In the The load utilization rate derived from the instruction is calculated using the following formula: in, Dimensionless load utilization rate; The path load output in step S400; This represents the rated capacity of node j. The load utilization judgment boundary is derived from the physical relationship between the path load and the rated capacity (e.g., the over-capacity judgment boundary is 1). When When the value is greater than 1, the node will be... Once an excess node is identified, no additional security factor is assigned. The centralized control node takes the first excess node caused by this instruction as its starting point and proceeds along the currently active directed connections to subsequent nodes that still bear the same load change, until it reaches the terminal node, encounters an effective isolation boundary, or the subsequent nodes no longer bear the load change, thus forming a conflict propagation path. The effective isolation boundary is derived from the current route configuration of the production line (e.g., a route switching node that is in a closed state).

[0048] Secondly, the associated devices for opposite actions, the associated devices for receiving mismatches, and the nodes of the conflict propagation path are merged and deduplicated to form a set of associated devices. Differential control results are bound to this set: instructions that fail static verification are directly intercepted; instructions that pass static verification but cause conflicts in cumulative simulations are assigned retention and postponement items according to production priority; other instructions that do not cause conflicts are released. When production priorities are equal, retention items are first determined by arrival time; if arrival times are still the same, retention items are determined by reception sequence number. Postponed instructions retain the original instruction content and the reason for postponement, but their old verification results become invalid after control baseline updates or reconstruction.

[0049] Then, in a preferred embodiment, using the candidate path load of I2, the load utilization of node C is 8.7 / 8 = 1.0875, which is greater than 1. Therefore, node C is identified as the first overload node. The centralized control node accesses node D from node C along the currently active route. Both node C and node D are subjected to a load change of 1.2 t / h caused by I2, and node D is the end of the current route, thus forming a conflict propagation path of C→D. Devices C and D enter the overload associated device subset.

[0050] Subsequently, if I4 requests device A to stop after I1, then device A simultaneously has the opposite target actions of starting and stopping, and device A enters the subset of devices associated with the opposite action; if a stop command causes the preceding device to continue outputting while the subsequent device cannot take over, then the target device and the corresponding preceding and following devices enter the subset of devices associated with mismatched takeover. The union of the above three subsets forms the final set of associated devices, which serves as both the control command association range in step S500 and the feedback acquisition and selective pause range in step S600.

[0051] Finally, I1 did not cause a timing conflict and obtained a release flag; I2 passed the static check but caused an overrun on the C→D path, thus obtaining a delayed execution flag; I3 completed the deduction on the independent route E→F without causing a conflict and obtained a release flag. If there is an instruction that fails the allowed action range or start / stop pre-state check, the instruction directly obtains an interception flag. The differentiated results output release instructions I1 and I3 and their valid deduction snapshots, delayed instruction I2 and its conflict reason, and proceed to steps S540 to S560. When the currently active route cannot be determined, the propagation path is not inferred in multiple branches, nor are all branch nodes indiscriminately listed as associated devices; instructions that cause overruns remain unreleased and are re-deduced after the route flag becomes valid.

[0052] After generating the direct interception flag, delayed execution flag, and release flag, the instructions with the release flag are further converted into target execution instructions and sent to the corresponding physical devices according to the cumulative deduction order. Specifically, this includes: S540. In accordance with the cumulative deduction order, only instructions with release flags are included in the target execution instruction sequence for this round; S550: Match the target execution instruction with the original instruction identifier, control cycle identifier, target device, target action, execution order, current timing node version, associated device set identifier, and valid simulation snapshot identifier; S560: Send the target execution instruction to the corresponding physical device, and record the sending result, execution receipt, executed devices, and related instructions that have not yet been executed.

[0053] For example, steps S540 to S560 may further include the following processes: First, target execution instructions are generated only from instructions with a release flag; directly intercepted instructions and delayed instructions do not enter the entity control interface. Before each target execution instruction is issued, the centralized control node re-verifies the current timing node version and topology version; if the version changes, the release qualification for that instruction is cancelled and the process returns to step S300 for re-verification. The target execution instruction response timeout is derived from the control bus timing and device interface specifications (e.g., 0.5s). After the control interface returns a receipt confirmation and the entity device enters the state corresponding to the target action, an execution record is created; if a rejection, execution failure, or exceeding the response timeout period is returned, an execution exception record is created.

[0054] Secondly, in a preferred embodiment, steps S510 to S530 output the release flags of I1 and I3 and the delayed execution flag of I2. The centralized control node generates the target execution instructions corresponding to I1 and I3 according to the cumulative deduction order, and associates them with the control cycle P1, the current timing node N1, the topology version V1, the associated device set, and the corresponding valid deduction snapshot, respectively; I2 only retains the original instruction flag and the reason for the delay, and does not enter the entity control interface in this round.

[0055] Before issuing I1, the centralized control node confirms that N1 and V1 are still valid, and then sends the device A start command to the existing physical device control interface. When the physical control interface returns parameter reception confirmation and execution receipt within 0.5 seconds, I1 enters the list of executed devices and establishes feedback collection objects according to the scope of devices associated with I1. After I1 execution confirmation, it then decides whether to continue issuing I3 based on I3's own control baseline version and the scope of associated devices.

[0056] Finally, if I1 returns a rejection, execution failure, or communication timeout, the centralized control node will not continue to issue instructions that have not yet been executed within the scope of the devices associated with I1, and will send the execution exception, the list of executed devices, and the list of unexecuted associated instructions to step S600. The independent route E→F to which I3 belongs will not be indiscriminately stopped due to the conflict propagation path C→D; whether it continues to execute depends on I3's own control baseline version, entity acknowledgment status, and the scope of associated devices.

[0057] In this second embodiment, the entity execution result that receives the aforementioned target execution instruction, in step S600, the actual feedback comparison and control benchmark update or reconstruction may include: S610. Collect the operating status data of the target device and its associated devices corresponding to the executed target execution instruction, and extract the actual start / stop status of the corresponding device from the operating status data. S620. Collect the current fluctuation value of the corresponding device under the actual start-stop state, and determine the actual load value of the corresponding device based on the current fluctuation value. S630. Compare the actual start / stop status and actual load value with the valid deduction snapshot corresponding to the release command; S640. When the feedback is consistent, update the current timing node with the valid temporary device status and valid path load corresponding to the release command as the subsequent verification benchmark. S650. When feedback is inconsistent, suspend the associated instructions that have not yet been executed within the scope of the associated device set, and clear the old verification results of the suspended instructions and the delayed instructions. S660. Reconstruct the state load sequence according to the actual start / stop status and actual load value, rebuild the current timing node and the set of allowed start / stop, and return to step S300 for re-verification.

[0058] For example, steps S610 to S660 may further include the following processes: First, the feedback reconstruction module obtains the operating status data of the device and associated devices corresponding to the executed target instruction according to the control cycle identifier, instruction identifier, and device identifier. The feedback waiting time is derived from the existing control cycle, device response limit, and communication cycle (e.g., 3 control cycles). If no valid status and load feedback is obtained after the feedback waiting time, the old simulation snapshot is not submitted as the new current timing node. After communication is restored, the actual start / stop status and actual load of the target device and associated devices are obtained again, without assuming that the physical device has been executed or not yet executed.

[0059] Secondly, the current fluctuation values ​​of the corresponding equipment under actual start-up and shutdown conditions are determined relative to the stable operating baseline or the current state before the target execution command is issued. An effective correspondence between current fluctuations and equivalent material load is established for each piece of equipment, with the linear effective range derived from independent equipment calibration (e.g., the effective range of current fluctuations for equipment C is 0A to 4A). Within the linear effective range, the actual load is determined according to the following formula: in, For equipment The actual equivalent material load is consistent with the rated load capacity. For equipment The current fluctuation value under actual start-stop conditions, in amperes (A); For equipment Independent load and current conversion factors, when the actual load is expressed in t / hour, The unit is t / ( ); For equipment Zero-point correction amount, in t / . and It should not be shared across devices. When the current fluctuation exceeds the effective linear range, the actual load should be obtained by looking up the table according to the independent calibration of the device; when the current signal is distorted, exceeds the calibration range and there is no valid table lookup result or the device is not applicable, the actual load should be marked as invalid, and invalid conversion results should not be used to determine the consistency of feedback.

[0060] Then, the feedback comparison uses only the valid simulation snapshot corresponding to the release command, excluding states containing delays or conflicting candidates. The feedback reconstruction module first compares the actual start / stop state with the simulation state, and then calculates the deviation of the actual load and the simulation path load relative to the rated capacity using the following formula: in, For nodes Dimensionless feedback load deviation; The actual load obtained from the effective load acquisition results; To release the path load in the valid simulation snapshot corresponding to the instruction, the source is the valid path load that has been written back in step S400; For nodes Rated load capacity. Load consistency tolerance. Derived from the equipment's measurement accuracy, control resolution, and calibration residuals, and taken as a value not less than the measurement uncertainty (e.g., Only when the actual start-stop state matches the simulated state and Not greater than Only when the corresponding device provides feedback is it considered consistent.

[0061] Subsequently, in a preferred embodiment, after I1 is executed, the actual start-stop state of device C is collected and is consistent with the effective extrapolation snapshot, with a current fluctuation of 3.8A. The load and current conversion factor for device C is taken as 0.5t / ( The zero-point correction is taken as 6.0 t / h, and substituted into the actual load relationship, we get... t / h. I1 corresponds to the device C path load in the valid extrapolation snapshot. The rated capacity of equipment C is 8t / h, and the rated capacity of equipment C is 7.5t / h. Substituting these values ​​into the feedback load deviation relationship, we obtain... .

[0062] Furthermore, the load consistency tolerance of 0.03 is retained. Since 0.05 is greater than 0.03, even if the actual start-stop state of device C is the same as the projected state, the feedback from device C is still considered inconsistent. Based on the associated device set formed in step S400, the centralized control node only suspends the associated instructions that have not yet been executed within the scope of the C→D conflict propagation path, clears the old verification results of I2, and re-forms the state-load sequence according to the actual load of device C (7.9 t / h) and other valid actual states.

[0063] Finally, the centralized control node re-matches the operational phase and forms a new current timing node based on the most recently changed equipment and the actual load arrival location, reconstructing the allowed start set and allowed stop set. I2 returns to step S300, re-executes the static verification under the new control baseline, and re-executes the item-by-item deduction in the same temporary operating state after passing the static verification; if the subsequent actual load decreases and the new load-bearing constraints allow, I2 can obtain the release flag again. Conversely, when the actual start / stop state of all specified feedback objects is consistent with the deduced state and the load deviation is not greater than the corresponding tolerance, the effective temporary equipment state and path load corresponding to the release command are submitted as the new current timing node control baseline and directly used as the input for step S300 of the next control cycle.

[0064] Furthermore, if at least one of the following occurs: data loss, synchronization failure, incompatible feedback objects, invalid topology version, invalid actual load, or reconstruction failure, a new control baseline will not be submitted, and any unexecuted instructions within the associated device scope will remain unreleased. After data or communication is restored, the new actual status and actual load will be read first, and then the correspondence between objects, periods, and versions will be re-established; pause and postpone instructions must not bypass step S300 for re-verification and will be directly resumed.

[0065] Accordingly, this invention sequentially completes the following within the same control cycle: establishing the device linkage topology and current timing nodes; sorting and statically verifying concurrent start and stop commands; performing item-by-item deduction and path load write-back under the same temporary operating state; determining the conflict propagation path and associated devices; issuing differentiated commands; and comparing actual feedback and reconstructing the control benchmark. This allows the output of the previous processing step to directly become the input of the next processing step, and enables the actual execution results to continue entering the command verification of the next control cycle.

[0066] Example 3: Based on the same general inventive concept, this invention also protects a monitoring and control system for start-up and shutdown sequence conflicts in a grinding production line. For example... Figure 5 As shown, the system includes: The linkage benchmark module is used to acquire production line data from the centralized control node, establish equipment linkage topology, form sets of allowed start-ups and shutdowns and load-bearing constraints, and determine the current timing node based on equipment status changes, load values ​​and load transfer locations. The concurrent instruction verification module is used to sort concurrent start and stop instructions according to priority identifier and arrival time, form a sequence of instructions to be verified, and perform verification based on the allowed action range of the current timing node, the pre-start and stop status, and the load bearing constraints. The state simulation and conflict identification module is used to copy the equipment status and path load of the current time sequence node to form a temporary operating status. It simulates the verification instructions item by item. Each simulation writes the load change caused by the target action into the path load along the material receiving direction and writes back the temporary equipment status and path load as the basis for the subsequent simulation. When the path load exceeds the rated capacity of the equipment, it determines the conflict propagation path along the load transmission direction, identifies the associated equipment by the path node, and identifies the time sequence conflict based on the cumulative simulation. The differential control module is used to intercept instructions that fail the verification, determine the retained instructions and delayed instructions according to the priority identifier of each conflicting instruction, and release the remaining instructions that do not cause timing conflicts. According to the cumulative deduction order, only the instructions with the release identifier are used to generate the target execution instructions to control the start and stop of the equipment. The feedback reconstruction module is used to collect the actual start / stop status and actual load value of the target device and associated devices corresponding to the executed target execution instructions, and compare them with the simulation results. If they are consistent, the current timing node is updated with the valid temporary device status and valid path load corresponding to the release instruction as the subsequent verification benchmark. If they are inconsistent, the unexecuted associated instructions are paused, and the timing node and the allowed start / stop set are reconstructed according to the actual status and load value.

[0067] For example, the system can further operate collaboratively in the following manner: First, the linkage baseline module obtains equipment identification, material input end, material output end, load flow direction, rated capacity, equipment status, load value, and load transfer location from the existing data interface of the production line. It then outputs the current timing node, allowed start set, allowed stop set, and load capacity constraints to the concurrent command verification module, and the current equipment status, current path load, and topology version to the state deduction and conflict identification module. Finally, the feedback reconstruction module outputs the updated or reconstructed actual status and actual load to the linkage baseline module.

[0068] Secondly, the concurrent command verification module reads concurrent start / stop commands within the same control cycle, forming ordered passing items, directly intercepted items, and conflict-pending verification markers. Ordered passing items enter the state simulation and conflict identification module, while directly intercepted items enter the differentiated control module to form interception records. The state simulation and conflict identification module saves temporary operating states, candidate states, conflict snapshots, and valid simulation snapshots, completing equipment state changes, path load updates, overload judgments, conflict propagation path formation, and associated device determination. It then sends the conflict results, the set of associated devices, and the valid simulation snapshots corresponding to the release commands to the differentiated control module and the feedback reconstruction module.

[0069] Then, the differentiation control module generates physical start / stop outputs only for the release command and sends the target execution command to the existing physical equipment control interface on the production line. The physical equipment control interface returns the sending result and execution receipt; the feedback reconstruction module collects the actual start / stop status and actual load according to the scope of executed equipment and associated equipment. If consistent, the feedback reconstruction module submits an updated benchmark to the linkage benchmark module; if inconsistent, the feedback reconstruction module outputs the result of pausing associated unexecuted commands to the differentiation control module and outputs the actual status and actual load to the linkage benchmark module to complete the reconstruction.

[0070] Further, in a preferred embodiment, the linkage benchmark module forms the current timing node N1 according to the route A→B→C→D, and sends N1, the allowed start set, the allowed stop set, and the load acceptance constraint to the concurrent instruction verification module. The concurrent instruction verification module outputs the ordered passing items of I1, I2, and I3; the state deduction and conflict identification module writes back the valid temporary state after deducing I1, forms the C→D conflict propagation path and associated device set when deducing I2, and completes the deduction along the independent route E→F when deducing I3. The differentiated control module sends the target execution instructions corresponding to I1 and I3 to the physical device control interface, and retains the delayed execution record of I2.

[0071] Finally, after the operational status data is transmitted to the feedback reconstruction module, if the feedback from device C is inconsistent, the feedback reconstruction module sends the pause results of any unexecuted instructions within the C→D association range to the differential control module, and sends the actual status and actual load to the linkage reference module. After the linkage reference module reconstructs the current timing node and the allowed start / stop set, I2 returns to the concurrent instruction verification module for reprocessing. The above modules transmit data according to the same control cycle identifier, instruction identifier, device identifier, and topology version, and do not establish a second set of control paths parallel to the aforementioned main technology chain.

[0072] It should be noted that the above-described embodiments are used to illustrate the execution process and module collaboration relationships of the present invention, and do not constitute a limitation on the scope of protection of the present invention. The device numbers, routes, load values, control cycles, time parameters, tolerances, and conversion factors in the examples are all used to illustrate technical relationships and do not represent unique implementation parameters or experimental results that have been obtained.

[0073] The above description is merely a preferred embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for monitoring and controlling start-up and shutdown sequence conflicts in a grinding production line, characterized in that, include: Acquire production line data from centralized control node scheduling, establish equipment linkage topology according to material receiving direction, load transfer sequence and start / stop pre-state, and form allowable start / stop sets and load receiving constraints; The current timing node is determined based on changes in equipment status, load values, and load transfer locations. Start and stop commands are sent sequentially according to priority identifier and arrival time to form a sequence of commands to be verified, and the verification is performed based on the allowable action range of the current timing node, the pre-start and stop status, and the load bearing constraints. The device status and path load of the current timing node are copied to form a temporary operating status. The instructions that have passed the verification are simulated item by item. Each simulation writes the load change caused by the target action into the path load along the material receiving direction, and writes back the temporary device status and path load as the basis for the subsequent simulation. When the path load exceeds the rated capacity of the equipment, the conflict propagation path is determined along the load transmission direction, the associated equipment is determined by the path node, and the timing conflict is identified based on the cumulative simulation. Intercept instructions that fail verification, determine the retained and delayed instructions according to the priority identifier of each conflicting instruction, and release the remaining instructions that have not caused timing conflicts; According to the cumulative deduction order, only the instructions with the release flag are generated as target execution instructions to control the start and stop of the equipment; Collect the actual start / stop status and actual load value of the target device and associated devices corresponding to the executed target execution instructions, and compare them with the simulation results. If they are consistent, update the current timing node with the status of the effective temporary device and the load of the effective path corresponding to the release instruction as the subsequent verification benchmark. If they are inconsistent, suspend the unexecuted associated instructions, and rebuild the timing node and the allowed start / stop set according to the actual status and load value.

2. The method according to claim 1, characterized in that, The establishment of the device linkage topology includes: Extract the equipment identifier, material input end, material output end, load flow direction, and rated capacity from the production line data; Using equipment identifiers as nodes, material receiving relationships between equipment as directed connections, and determining the order of each directed connection according to the load transfer sequence; The allowed start / stop status, start / stop preconditions, and rated capacity of each node are associated with the device linkage topology.

3. The method according to claim 1, characterized in that, Determining the current timeline node includes: The operating status and corresponding load value of each device are arranged according to the sampling time to form a status-load sequence; The current operating stage is determined by matching the state load sequence with the preset equipment state combinations and load transfer boundaries for each operating stage. Within the current operating phase, the current timing node is determined based on the device node corresponding to the most recent state change and the location of the load arrival.

4. The method according to claim 1, characterized in that, The process of forming the sequence of instructions to be verified includes: Parse the target device, target action, arrival time, and priority identifier in each concurrent start / stop command; First, determine the order of instructions with different priorities according to the priority identifier, and then determine the order of instructions with the same priority according to the arrival time. When two instructions are directed to the same target device and the target actions are opposite, the later-arriving instruction is marked as a conflict-checking instruction.

5. The method according to claim 1, characterized in that, The verification of the pre-start / stop status and load-bearing constraints includes: Extract the preceding and subsequent device states of the target device from the device linkage topology, and determine whether they meet the start / stop preceding states corresponding to the target action. The load change after the target equipment starts and stops is determined based on the target action, and the load change is included in the expected load of each adjacent equipment along the material receiving direction. The expected load of each adjacent device is compared with its rated capacity one by one to obtain the verification result of the load bearing constraint.

6. The method according to claim 1, characterized in that, The instructions for the step-by-step deduction and verification include: The device status and path load corresponding to the current time sequence node are copied to form the temporary operating state; According to the sequence of instructions to be verified, for each instruction that passes verification, a candidate state is copied from the previous valid temporary operating state, the temporary start / stop state of the target device is changed in the candidate state, and the candidate path load is updated along the device linkage topology. When no timing conflict occurs in the candidate state, the candidate temporary device state and candidate path load are written back as a new valid temporary running state, which serves as the basis for the derivation of the next instruction. When a timing conflict occurs in the candidate state, the conflict snapshot is retained and the candidate state is not written back, until all instructions that have passed the verification are completed.

7. The method according to claim 1, characterized in that, The determination of associated devices includes: When concurrent start / stop commands cause the same device to have opposite target actions at the same timing node, the target device is listed as an associated device; When the start-up or shutdown of the target equipment causes at least one of the following: the upstream equipment cannot output materials or the downstream equipment cannot accept materials, the target equipment and its corresponding upstream and downstream equipment are listed as associated equipment. When the path load exceeds the rated capacity of any device, a conflict propagation path is determined along the load transmission direction, and the nodes on the conflict propagation path are listed as associated devices.

8. The method according to claim 1, characterized in that, The interception, delay, and release include: For concurrent start / stop commands that fail to pass at least one of the checks, such as the allowed action range, start / stop pre-state, and load bearing constraints, a direct interception flag is generated. For concurrent start / stop instructions that pass the aforementioned verification but cause timing conflicts during simulation, reserve instructions are determined according to the priority identifier of each concurrent start / stop instruction, release identifiers are generated for the reserved instructions, and delayed execution identifiers are generated for the remaining conflicting instructions. For the remaining concurrent start / stop instructions that do not cause timing conflicts, release flags are generated, and only instructions with release flags are included in the target execution instructions of this round.

9. The method according to claim 1, characterized in that, The collection of actual start / stop status and actual load values ​​includes: Collect the operating status data of the target device and its associated devices corresponding to the executed target execution instructions, and extract the actual start-stop status of the corresponding devices from the operating status data; Collect the current fluctuation values ​​of the corresponding device under the actual start-stop state, and determine the actual load value of the corresponding device based on the current fluctuation values.

10. A start-stop sequence conflict monitoring and control system for a grinding production line, characterized in that, include: The linkage benchmark module is used to acquire production line data from the centralized control node, establish equipment linkage topology, form sets of allowed start-ups and shutdowns and load-bearing constraints, and determine the current timing node based on equipment status changes, load values ​​and load transfer locations. The concurrent instruction verification module is used to sort concurrent start and stop instructions according to priority identifier and arrival time, form a sequence of instructions to be verified, and perform verification based on the allowed action range of the current timing node, the pre-start and stop status, and the load bearing constraints. The state simulation and conflict identification module is used to copy the equipment status and path load of the current time sequence node to form a temporary operating status. It simulates the verification instructions item by item. Each simulation writes the load change caused by the target action into the path load along the material receiving direction and writes back the temporary equipment status and path load as the basis for the subsequent simulation. When the path load exceeds the rated capacity of the equipment, it determines the conflict propagation path along the load transmission direction, identifies the associated equipment by the path node, and identifies the time sequence conflict based on the cumulative simulation. The differential control module is used to intercept instructions that fail the verification, determine the retained instructions and delayed instructions according to the priority identifier of each conflicting instruction, and release the remaining instructions that do not cause timing conflicts. According to the cumulative deduction order, only the instructions with the release identifier are used to generate the target execution instructions to control the start and stop of the equipment. The feedback reconstruction module is used to collect the actual start / stop status and actual load value of the target device and associated devices corresponding to the executed target execution instructions, and compare them with the simulation results. If they are consistent, the current timing node is updated with the valid temporary device status and valid path load corresponding to the release instruction as the subsequent verification benchmark. If they are inconsistent, the unexecuted associated instructions are paused, and the timing node and the allowed start / stop set are reconstructed according to the actual status and load value.

Images