A method for visualizing and quickly programming configuration of silicon steel transverse shear piece type parameters

Abstract

The application discloses a kind of silicon steel transverse shear piece type parameter visual quick programming configuration method, specifically relates to transverse shear programming configuration field, for solving the problem that single piece completes boundary and group production boundary are not consistent;By obtaining the transverse shear piece type configuration data formed by visual configuration, the piece type execution model, group constraint model and piece type parameter relationship diagram are generated by parsing, and the piece type execution model is unfolded based on the piece type parameter relationship diagram Continuous piece sequence is unfolded, and forms piece sequence state object and continuous piece sequence state table;Then, according to the continuous piece sequence state table, the control boundary recognition is executed, the double-evidence boundary discrimination processing is carried out on the candidate stoppage control boundary, and the control boundary recognition result is generated;Finally, boundary control data and boundary prompt data are generated, and are combined with piece type parameter relationship diagram to form transverse shear piece type programming configuration package.

Description

Technical Field

[0001] This invention relates to the field of cross-cutting programming configuration, and more specifically, to a method for rapid programming configuration of silicon steel cross-cutting sheet parameters through visualization. Background Technology

[0002] Cross-cutting of silicon steel is typically used to process coils or sheets into silicon steel sheets of different shapes according to the requirements of transformer core stacking. With the increasing automation of cross-cutting equipment, sheet type parameters are often input through a visual configuration interface, and then converted into programming configuration data that the cross-cutting programming system can read. This configuration data includes not only the processing sequence of sheet types such as oblique joints, straight joints, and overlapping joints, but also thickness recording, material grouping, stacking, and operational control boundaries such as pause, stop, and single-step debugging within the continuous sheet sequence. For silicon steel cross-cutting, the processing outline of the sheet type itself is only one part of the cross-cutting control; the grouping relationship between different sheet sequence positions during continuous production also affects the triggering position of the equipment's operational control commands.

[0003] Existing visual rapid programming methods typically focus more on single-piece configuration and processing. For example, they generate corresponding processing sequences based on the piece outline, punching and shearing actions, and processing order, and treat the completed single-piece processing position as a pauseable, stopable, or single-step adjustable location. This approach is applicable to general sheet metal cross-cutting or single-piece processing tasks. However, in silicon steel cross-cutting production, the completion of single-piece processing does not necessarily mean that continuous production grouping conditions have been met. Even if a piece sequence position has completed shearing, it may still be in the middle of a thickness-recording unit, or in a position where a material handling grouping unit or stacking grouping unit has not yet closed. If a stopable boundary is generated at such positions, the equipment needs to re-determine whether the current piece sequence belongs to the original grouping unit when resuming operation, which can easily lead to problems such as broken pieces within the group, misalignment of upper and lower layer material handling, difficulty in determining the position of replacement pieces, and chaotic stacking order.

[0004] Furthermore, the grouping conditions in silicon steel cross-cutting production are continuous and interconnected. Thickness counting typically requires accumulating the number of sheets or thickness results according to the continuous sheet sequence; material handling grouping requires maintaining the correspondence between the upper and lower sheet sequence positions; and stacking grouping requires ensuring that the sheet sequence positions advance continuously according to the target arrival order. If the programming configuration data only records the sheet type execution order without establishing a stable association between the executable sheet type units and the thickness counting, material handling, and stacking grouping conditions, then the subsequent operation control boundary can only be judged based on the single sheet processing completion position, making it difficult to identify sheet sequence positions where the single sheet processing completion state is inconsistent with the group process completion state. Therefore, in the process of visualizing and rapidly programming the silicon steel cross-cutting sheet type parameters, it is necessary to unify the sheet type execution model, grouping constraint model, and continuous sheet sequence state, and reliably identify candidate stopable control boundaries, so that the generated cross-cutting sheet type programming configuration package can simultaneously reflect the sheet type processing sequence, grouping constraint relationship, and operation control boundary. Summary of the Invention

[0005] To overcome the aforementioned deficiencies in the prior art, embodiments of the present invention provide a method for rapid programming configuration of silicon steel cross-cutting sheet parameters through visualization. This method acquires cross-cutting sheet configuration data generated through visualization configuration, parses and generates a sheet execution model, a group constraint model, and a sheet parameter relationship diagram. Based on the sheet parameter relationship diagram, the sheet execution model is continuously expanded into a sheet sequence, forming a sheet sequence state object and a continuous sheet sequence state table. Then, control boundary identification is performed based on the continuous sheet sequence state table, and dual-evidence boundary discrimination processing is applied to candidate stopable control boundaries to generate control boundary identification results. Finally, boundary control data and boundary prompt data are generated and combined with the sheet parameter relationship diagram to form a cross-cutting sheet programming configuration package, thereby solving the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention provides the following technical solution: A method for rapid programming configuration of parameters for cross-cutting silicon steel sheets, comprising: S1: Obtain the cross-cutting slicing configuration data formed by the visual configuration, perform structured parsing on the cross-cutting slicing configuration data, generate the slicing execution model and the group constraint model, and construct the slicing parameter relationship diagram based on the relationship between the two. S2: Based on the slice parameter relationship diagram, the slice execution model is continuously expanded into slice sequence to generate slice sequence state objects, and the group constraint model is applied to the slice sequence state objects to obtain a continuous slice sequence state table. S3: Perform control boundary identification based on the continuous slice state table, and perform dual evidence boundary discrimination processing on the candidate stopable control boundaries obtained by the control boundary identification to generate control boundary identification results; S4: Generate boundary control data and boundary prompt data based on the control boundary identification results, and combine the boundary control data, boundary prompt data and the slice type parameter relationship diagram to generate a cross-cut slice type programming configuration package.

[0007] Furthermore, in step S1, the structured parsing includes: reading the configuration content used to limit the processing order from the cross-cutting sheet configuration data, identifying the sheet configuration items that can be executed by cross-cutting as executable sheet units, and forming a sheet parsing sequence according to the processing order; at the same time, reading the configuration content of thickness recording, material grouping, and stacking grouping to form a constraint parsing set containing constraint items, and reading the configuration reference relationship between executable sheet units and constraint items to form an association index set.

[0008] Furthermore, in step S1, a slice execution model is generated based on the slice parsing sequence. The slice execution model includes the slice execution nodes corresponding to the executable slice units, the sequential connection relationship, and the termination node. A group constraint model is generated based on the constraint parsing set. The group constraint model includes the constraint object, the target completion state, and the allowed judgment scale. Then, based on the association index set, the slice nodes and constraint nodes are connected to generate a slice parameter relationship diagram.

[0009] Furthermore, in step S2, the constraint terms corresponding to each executable slice unit in the slice execution model are read based on the slice parameter relationship diagram, and a slice expansion sequence is formed along the sequential connection relationship in the slice execution model; according to the continuous slice expansion range, the executable slice units in the slice expansion sequence are expanded into slice state objects one by one, and a slice position is assigned to each slice state object, so that the slice position is consistent in the continuous slice state table, control boundary identification results, boundary control data and boundary prompt data.

[0010] Furthermore, in step S2, the single-piece processing completion status of the slice sequence status object is marked according to the endable node in the slice type execution model; the constraint items corresponding to the slice sequence status object are obtained through the slice type parameter relationship diagram, and the group constraint model is called to generate the constraint completion quantity. The constraint completion quantity is compared with the corresponding target completion status. When all the constraint items for the same slice sequence status object have reached the target completion status, the group process completion status is marked.

[0011] Furthermore, in step S3, each chip sequence state object is read sequentially according to its position in the continuous chip sequence state table, and an initial boundary marker sequence is generated based on the single-chip processing completion state and the group process completion state. Chip sequence positions that do not meet the single-chip processing completion state are written as non-candidate states, chip sequence positions that meet the single-chip processing completion state but do not meet the group process completion state are marked as candidate restricted control boundaries, and chip sequence positions that meet both the single-chip processing completion state and the group process completion state are marked as candidate stopable control boundaries.

[0012] Furthermore, in step S3, when performing dual-evidence boundary discrimination processing on the candidate stopable control boundary, the corresponding fragment state object is obtained from the continuous fragment state table, and the deviation of the fragment state object from the target completion state is calculated according to the group constraint model to obtain the group redundancy; then, taking the fragment position where the candidate stopable control boundary is located as the center, the fragment neighborhood in the initial boundary marker sequence is read to calculate the fragment stability.

[0013] Furthermore, in step S3, the group redundancy is converted into first evidence, the fragment order stability is converted into second evidence, and a non-training evidence fusion analysis is performed based on the first and second evidence to obtain the boundary credibility and evidence conflict degree. When the boundary credibility meets the shutdown determination condition and the evidence conflict degree meets the consistency determination condition, the corresponding candidate shutdown control boundary is confirmed as a shutdown control boundary. When the boundary credibility does not meet the shutdown determination condition or the evidence conflict degree does not meet the consistency determination condition, the corresponding candidate shutdown control boundary is downgraded and labeled as a restricted control boundary.

[0014] Furthermore, in step S4, according to the chip sequence position and final boundary attribute in the control boundary identification result, the chip sequence position corresponding to the stopable control boundary is written into the allowed trigger position set, and the chip sequence position corresponding to the restricted control boundary is written into the restricted trigger position set; then, boundary control data is generated according to the correspondence between chip sequence position and run control command. For each chip sequence position in the allowed trigger position set, the pause command, stop command, and single-step debugging command corresponding to that chip sequence position are all set as allowed trigger attributes; for each chip sequence position in the restricted trigger position set, the pause command, stop command, and single-step debugging command corresponding to that chip sequence position are all set as restricted trigger attributes.

[0015] Furthermore, in step S4, boundary hint data is generated based on the formation path of the restricted control boundary, and the slice parameter relationship diagram, boundary control data, and boundary hint data are written into the cross-cut slice programming configuration package. After the cross-cut slice programming configuration package is written, the slice sequence state objects in the continuous slice sequence state table are traced back by slice sequence position, and the corresponding executable slice unit and constraint item in the slice parameter relationship diagram are read to perform slice sequence position consistency verification on the cross-cut slice programming configuration package.

[0016] The technical effects and advantages of the present invention, a method for rapid programming configuration of silicon steel cross-cutting sheet parameters through visualization, are as follows: This invention establishes a correspondence between the sheet type execution model and the group constraint model through a sheet type parameter relationship diagram, enabling the sheet type processing sequence and continuous grouping conditions in the cross-cutting sheet type configuration data to be expressed in the same configuration chain. Compared with the method of generating control programs only around the outline of a single sheet type or processing step, this processing method can retain the constraint relationship between thickness recording, material grouping, and stacking grouping on executable sheet type units at the configuration data level, reducing boundary identification deviations caused by the separation of sheet type sequence and grouping conditions.

[0017] This invention stores the single-piece processing completion status and the group process completion status in parallel through a continuous wafer sequence status table, so that control boundary identification no longer depends solely on the single-piece processing end position. For wafer sequence positions where a single piece has been completed but the thickness recording unit, material handling grouping unit, or stacking grouping unit has not yet been completed, they can be identified as restricted control boundaries. For candidate stop-the-machine control boundaries, dual-evidence boundary discrimination processing is used for confirmation or downgrading, so that the control boundary identification results are consistent with the continuous production group status.

[0018] This invention transforms the control boundary identification results into boundary control data and boundary prompt data, and combines them with the sheet type parameter relationship diagram to form a cross-cutting sheet type programming configuration package. This ensures that the trigger position of the cross-cutting operation control command and the boundary prompt content in the visual configuration interface have the same sheet sequence position source. This configuration package can simultaneously retain the sheet type processing sequence, group constraint relationship, final boundary attributes, and prompt content, reducing the uncertainty in sheet sequence tracing, sheet replacement judgment, and material handling verification during shutdown recovery. Attached Figure Description

[0019] Figure 1 This is an overall flowchart of the method for visually and rapidly programming and configuring parameters of silicon steel cross-cutting sheets according to the present invention; Figure 2 This is a schematic diagram illustrating the structured analysis of cross-cutting sheet configuration data and the generation of a sheet type parameter relationship diagram according to the present invention. Detailed Implementation

[0020] 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.

[0021] Please see Figure 1 - Figure 2 This invention provides a method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets, comprising: This invention uses cross-cutting sheet configuration data generated through visual configuration as the processing object. First, it performs structured analysis on the sheet processing sequence and continuous production grouping conditions, forming a sheet execution model and a group constraint model respectively. A correspondence between executable sheet units and constraint items is established through a sheet parameter relationship diagram. Then, based on the sheet parameter relationship diagram, the sheet execution model is continuously expanded into a sheet sequence, generating a sheet sequence state object at each sequence position. The group constraint model is then applied to the sheet sequence state object, forming a continuous sheet sequence state table recording the sheet execution state, single-sheet processing completion state, group process completion state, and constraint matching results. On this basis, control boundary identification is performed on the continuous sheet sequence state table, distinguishing between candidate restricted control boundaries and candidate stopable control boundaries. The candidate stopable control boundaries undergo dual-evidence boundary discrimination processing to obtain control boundary identification results. Finally, the control boundary identification results are converted into boundary control data and boundary prompt data, and written together with the sheet parameter relationship diagram into the cross-cutting sheet programming configuration package.

[0022] In this embodiment, the rapid programming configuration method for visualized parameters of silicon steel cross-cutting sheets is executed by the cross-cutting programming data processing unit. The cross-cutting programming data processing unit receives the cross-cutting sheet configuration data generated by the visualized configuration interface, performs structured processing on the sheet processing sequence, thickness recording conditions, material handling grouping conditions, stacking grouping conditions, and operating boundary configuration, and outputs a cross-cutting sheet programming configuration package. The cross-cutting programming data processing unit can be located in the cross-cutting programming system or in a data processing server connected to the visualized configuration interface. Its function is to convert the visualized configuration results into programming configuration data that can be read by the cross-cutting control system or the cross-cutting programming system.

[0023] S1: Obtain the cross-cutting slicing configuration data formed by the visualization configuration, perform structured parsing on the cross-cutting slicing configuration data, generate the slicing execution model and the group constraint model, and construct the slicing parameter relationship diagram based on the relationship between the two.

[0024] Step S1 takes the cross-shearing sheet configuration data generated by the visual configuration interface as input. The cross-shearing sheet configuration data includes the configuration content required for the sheet processing sequence and the configuration content required for continuous production grouping conditions. The configuration content required for the sheet processing sequence is used to determine the execution order of silicon steel sheets in the cross-shearing process, and the configuration content required for continuous production grouping conditions is used to determine which positions in the continuous sheet sequence belong to the same thickness sheet recording unit, material handling grouping unit, or stacking grouping unit.

[0025] The cross-cutting programming data processing unit first reads the configuration content used to define the processing sequence from the cross-cutting sheet type configuration data. It identifies each sheet type configuration item that can be executed by cross-cutting as an executable sheet type unit and arranges them according to the processing sequence given in the visual configuration interface to form a sheet type parsing sequence. The sheet type parsing sequence refers to the sequence of executable sheet type units arranged according to the processing sequence defined by the cross-cutting sheet type configuration data. Its arrangement order is used to generate the sequential connection relationship in the sheet type execution model. If the same sheet type appears consecutively in the visual configuration, the cross-cutting programming data processing unit retains it as a different sequence position in the sheet type parsing sequence according to its appearance position in the configuration, so that subsequent consecutive sheet sequence expansions can reference each sheet one by one according to the actual cross-cutting production sequence.

[0026] The cross-cutting programming data processing unit continues to read the configuration content used for limiting thickness counting, material grouping, and stacking in the cross-cutting sheet configuration data. It parses the grouping conditions that can be invoked by the sheet sequence status object into constraint items, forming a constraint parsing set. The constraint parsing set is a set of constraint items obtained from parsing the continuous production grouping conditions in the cross-cutting sheet configuration data. Each constraint item maintains the correspondence between the constraint object, the target completion state, and the allowable judgment scale. The constraint object points to the sheet sequence range or group unit that needs to be jointly judged in the continuous sheet sequence. The target completion state represents the state that the constraint object should meet when reaching the group process completion state. The allowable judgment scale is used for subsequent normalization of deviations. Simultaneously, the cross-cutting programming data processing unit reads the configuration reference relationship between executable sheet units and constraint items in the visual configuration, forming an association index set. The association index set records the corresponding source between executable sheet units and constraint items.

[0027] After forming the slice parsing sequence, the cross-cutting programming data processing unit generates the slice execution model according to the order of the executable slice units in the slice parsing sequence. Starting from the first position of the slice parsing sequence, the cross-cutting programming data processing unit sequentially obtains each executable slice unit and establishes a corresponding slice execution node for it. Adjacent executable slice units are connected sequentially according to their order in the slice parsing sequence. The direction of this sequential connection is consistent with the processing order specified in the cross-cutting slice configuration data, indicating that the process proceeds to the next executable slice unit after the previous one is completed. All slice execution nodes and their sequential connections together constitute the slice execution model.

[0028] When generating the slice execution model, the cross-cutting programming data processing unit also generates an end-of-processing node on the corresponding slice execution node based on the processing end position of each executable slice unit in the cross-cutting slice configuration data. The end-of-processing node is used for subsequent judgment of the single-slice processing completion status of the slice sequence status object; when the executable slice unit corresponding to the slice sequence status object reaches the end-of-processing node, the single-slice processing completion status is marked as satisfied; when the end-of-processing node is not reached, the single-slice processing completion status is marked as unsatisfied.

[0029] The cross-cutting programming data processing unit then takes the constraint parsing set as input and the sheet type execution model as a reference for constraint object matching to generate a group constraint model. The cross-cutting programming data processing unit sequentially reads the constraint items in the constraint parsing set, determines the constraint object corresponding to each constraint item, and keeps the constraint object, target completion state, and allowable judgment scale within the same constraint item. For multiple executable sheet type units belonging to the same thickness sheet counting unit, material handling grouping unit, or stacking grouping unit, the cross-cutting programming data processing unit maps them to the same constraint item, so that when subsequently generating sheet sequence state objects, it can obtain the sheet type execution state based on the sheet type execution model and obtain the grouping conditions at that sheet sequence position based on the group constraint model.

[0030] Subsequently, the cross-cutting programming data processing unit takes the slice execution model, group constraint model, and associated index set as input, and performs a two-part relational graph construction process to generate a slice parameter relational graph. The cross-cutting programming data processing unit first sets each executable slice unit in the slice execution model as a slice node in the slice parameter relational graph, and then sets each constraint item in the group constraint model as a constraint node in the slice parameter relational graph. The order in which slice nodes are generated is consistent with the processing order in the slice execution model, and the order in which constraint nodes are generated is consistent with the parsing order of constraint items in the group constraint model. For cases where the same slice appears multiple times in the slice parsing sequence, the slice node in the slice parameter relational graph uses its sequence position in the slice parsing sequence as a unique index; the configuration references in the associated index set also point to the corresponding slice node with this sequence position, enabling the same slice name or the same slice outline to be connected to the corresponding constraint node at different processing positions. Subsequently, the cross-cutting programming data processing unit reads the configuration reference relationship between each executable slice unit and constraint item from the associated index set, connects the corresponding slice node to the corresponding constraint node, and forms a connection edge representing the constraint relationship.

[0031] When an executable sheet type unit belongs to a thickness recording unit, a material handling grouping unit, and a stacking grouping unit simultaneously, the cross-cutting programming data processing unit connects the sheet type node to the corresponding multiple constraint nodes according to the multiple reference relationships recorded in the associated index set. When multiple executable sheet type units belong to the same grouping constraint item, the cross-cutting programming data processing unit connects the multiple sheet type nodes to the same constraint node. The resulting sheet type parameter relationship diagram maintains both the processing order in the sheet type execution model and the restriction relationship of the constraint items on the executable sheet type units in the grouping constraint model.

[0032] After step S1 is completed, the cross-cutting programming data processing unit outputs the slice execution model, the group constraint model, and the slice parameter relationship diagram. The slice execution model provides the processing sequence required for continuous slice unfolding, the group constraint model provides the constraint items required for determining the completion status of the group process, and the slice parameter relationship diagram provides the correspondence between executable slice units and constraint items.

[0033] S2: Based on the slice parameter relationship diagram, the slice execution model is continuously expanded to generate a slice state object, and the group constraint model is applied to the slice state object to obtain a continuous slice state table.

[0034] Step S2 takes the slice execution model, group constraint model, and slice parameter relationship diagram output from step S1 as input. The cross-cutting programming data processing unit reads the group constraint items corresponding to each executable slice unit in the slice execution model based on the slice parameter relationship diagram, and expands the slice execution model from the sequential structure at the configuration level into slice sequence state objects in the continuous production process.

[0035] The cross-cutting programming data processing unit first reads the executable slice units and their sequential connection relationships in the slice execution model, and then reads the constraint nodes connected to each executable slice unit in the slice parameter relationship diagram. The reading process is performed sequentially according to the processing order in the slice execution model, so that the slice processing order and group constraint relationships are obtained synchronously in the same traversal path. The cross-cutting programming data processing unit takes the first executable slice unit in the slice execution model as the expansion starting point, and visits the subsequent executable slice units one by one along the sequential connection relationship to form a slice expansion sequence. The slice expansion sequence is a sequence of executable slice units arranged according to the actual cross-cutting production order and can be called by continuous slice expansion. It comes from the slice execution model and does not change the processing order determined in step S1.

[0036] Before generating the slice sequence state object, the cross-cutting programming data processing unit first determines the continuous slice sequence expansion range. The continuous slice sequence expansion range refers to the range of slice positions that need to be expanded into slice sequence state objects in this cross-cutting slice type programming configuration. If the cross-cutting slice type configuration data provides the number of consecutive production slices, the slice sequence range corresponding to the number of consecutive production slices is used as the continuous slice sequence expansion range; if the cross-cutting slice type configuration data does not provide the number of consecutive production slices but the group constraint model can determine the group slice sequence range, the maximum slice sequence range covered by the group constraint model is used as the continuous slice sequence expansion range; if the cross-cutting slice type configuration data provides both the number of consecutive production slices and the group slice sequence range, the slice sequence range corresponding to the number of consecutive production slices is used as the main expansion boundary, and the group slice sequence range is used as the constraint matching boundary. If a slice sequence position is within the continuous slice sequence expansion range but does not match any group constraint item, a slice sequence state object is still generated for that slice sequence position, and the processing path for the unmatched group constraint item is executed in the subsequent boundary identification.

[0037] The cross-cutting programming data processing unit uses the first executable slice unit in the slice unfolding sequence as the unfolding starting point, and generates slice state objects one by one according to the processing order. When the slice unfolding sequence reaches the last position and the continuous slice unfolding range has not yet ended, it returns to the beginning of the slice unfolding sequence according to the sequential connection relationship in the slice execution model and continues unfolding until the end position of the continuous slice unfolding range is reached. The number of slice state objects generated in this way is consistent with the number of slice positions in the continuous slice unfolding range.

[0038] The slice position is generated starting from the first slice output position within the continuous slice sequence expansion range, and increments sequentially according to the order of slice output in continuous production. Each time the cross-cut programming data processing unit generates a slice sequence state object, it assigns a slice position to that object. This slice position remains consistent across the continuous slice sequence state table, the initial boundary marker sequence, the control boundary identification result, the boundary control data, and the boundary hint data, ensuring that all of these objects can trace back to the same slice sequence state object.

[0039] The cross-cutting programming data processing unit creates a slice sequence state object at each slice sequence position, writing the current slice sequence position, the corresponding executable slice unit, the slice execution status, and the correspondence of constraints read from the slice parameter relationship diagram into the same slice sequence state object. Subsequently, the cross-cutting programming data processing unit marks the single-slice processing completion status of the slice sequence state object according to the end-of-life node of the corresponding executable slice unit in the slice execution model. If the executable slice unit corresponding to the current slice sequence position has reached the end-of-life node in the slice execution model, the slice sequence state object is marked as satisfying the single-slice processing completion status; if the current slice sequence position has not yet reached the corresponding end-of-life node, it is marked as not satisfying the single-slice processing completion status.

[0040] After completing the single-piece processing completion status calibration, the cross-cutting programming data processing unit calls the group constraint model to perform constraint item matching and group process completion status determination for each piece sequence status object. The cross-cutting programming data processing unit first reads the corresponding executable piece type unit from the piece sequence status object, then obtains the constraint items connected to the executable piece type unit through the piece type parameter relationship diagram, and finally reads the constraint object, target completion status, and allowable judgment scale of the corresponding constraint item from the group constraint model.

[0041] When the cross-cutting programming data processing unit performs group constraint matching on the piece sequence status object, it first determines whether the current piece sequence position falls within the constraint object range corresponding to the constraint item. If the current piece sequence position belongs to a certain thickness recording unit, material handling grouping unit, or stacking grouping unit, then the constraint item is written into the matching result of the piece sequence status object. When multiple constraint items act on the same piece sequence status object at the same time, the cross-cutting programming data processing unit writes them item by item according to the connection relationship in the piece type parameter relationship diagram, so that the same piece sequence status object can simultaneously reflect the constraint status of thickness recording, material handling grouping, or stacking grouping.

[0042] Before determining the completion status of the grouped process, the cross-cutting programming data processing unit first generates a constraint completion quantity for each group constraint item acting on the current slice state object. The constraint completion quantity refers to the completion result that has been formed with the continuous slice sequence within the constraint object range of the current slice state object and can be used to determine the target completion status. For the thickness recording condition, the constraint completion quantity is taken as the number of slices that have been unfolded and have met the single-slice processing completion status within the current thickness recording unit, or the thickness accumulation result corresponding to the number of slices. When the thickness recording condition takes the thickness accumulation result as the target completion status, the cross-cutting programming data processing unit reads the single-slice thickness value of the executable slice unit corresponding to the current slice state object from the cross-cutting slice configuration data, or reads the configured single-slice thickness value from the corresponding thickness recording constraint item in the group constraint model, and accumulates it according to the order of the unfolded slice positions within the current thickness recording unit to obtain the thickness accumulation result. For the material handling grouping condition, the constraint completion measure is the number of piece sequence pairs that have reached the target hierarchical relationship within the current material handling grouping unit. The target hierarchical relationship is given by the corresponding material handling grouping constraint item in the grouping constraint model, which specifies the correspondence between upper-level piece sequence positions and lower-level piece sequence positions within the same material handling grouping unit. After reading this correspondence, the cross-cutting programming data processing unit uses a set of upper-level piece sequence positions and lower-level piece sequence positions as a material handling pair. When all piece sequence positions in this material handling pair have generated piece sequence state objects, and the corresponding piece sequence state objects all meet the single-piece processing completion state, this material handling pair is counted in the number of piece sequence pairs that have reached the target hierarchical relationship. For the stacking grouping condition, the constraint completion measure is the number of pieces that have consecutively reached the stacking requirements within the current stacking grouping unit. The stacking requirements are given by the corresponding stacking grouping constraint item in the grouping constraint model, which limits the target arrival order of piece sequence positions within the same stacking grouping unit. The cross-cutting programming data processing unit starts from the initial slice sequence position of the stacking group unit and reads the slice sequence status objects one by one according to the target arrival order. When a slice sequence status object that meets the single-piece processing completion state and conforms to the target arrival order is read continuously, the number of slice sequences that have continuously arrived at the stacking requirements is accumulated. When a slice sequence position that has not generated a slice sequence status object, does not meet the single-piece processing completion state, or does not conform to the target arrival order is read, the continuous counting stops, and the accumulated number before stopping is used as the constraint completion amount of the stacking group constraint item.

[0043] The cross-cutting programming data processing unit compares the constraint completion amount with the target completion state of the corresponding constraint item on the same scale, and calibrates the group process completion state based on the comparison result. When a sequence state object matches only one group constraint item, the cross-cutting programming data processing unit determines the group process completion state of the sequence state object based on the comparison result of that group constraint item. When a sequence state object matches multiple group constraint items simultaneously, the cross-cutting programming data processing unit generates constraint completion amounts for each group constraint item and compares them with the corresponding target completion state. Only when all group constraint items reach the target completion state or fall within the completion range limited by the corresponding allowable judgment scale, is the sequence state object calibrated as satisfying the group process completion state. If any group constraint item acting on the sequence state object fails to reach the target completion state and does not fall within the completion range limited by the corresponding allowable judgment scale, the group process completion state of the sequence state object is calibrated as unsatisfied.

[0044] For example, when five consecutive pieces are configured into the same thickness recording unit, the cross-cutting programming data processing unit can mark the single-piece processing completion state of the first to fourth pieces when unfolding the corresponding piece sequence state objects. However, the thickness recording condition has not yet reached the target completion state, so the corresponding piece sequence state object is marked as not meeting the group process completion state. When unfolding to the piece sequence state object corresponding to the fifth piece, the thickness recording condition reaches the target completion state. If the material handling grouping condition and stacking grouping condition matched by the piece sequence state object also reach the corresponding target completion state, then the piece sequence state object is marked as meeting the group process completion state.

[0045] The cross-cutting programming data processing unit writes the generated and calibrated slice state objects into a continuous slice state table according to their slice position. Each entry in the continuous slice state table corresponds to a slice state object and records the slice type execution status, single-piece processing completion status, group process completion status, and matching result with the group constraint model for that slice state object. After step S2 is completed, the continuous slice state table serves as the input for control boundary identification in step S3.

[0046] S3: Perform control boundary identification based on the continuous slice state table, and perform dual evidence boundary discrimination processing on the candidate stopable control boundaries obtained by the control boundary identification to generate control boundary identification results.

[0047] Step S3 takes the continuous slice state table output in step S2 as input and continues to call the group constraint model generated in step S1. The cross-cutting programming data processing unit performs control boundary identification on the continuous slice state table. First, it generates an initial boundary marker sequence, and then performs dual-evidence boundary discrimination processing on the candidate stopable control boundaries, finally forming the control boundary identification result.

[0048] The cross-cutting programming data processing unit reads the slice status objects sequentially according to their positions in the continuous slice status table, and simultaneously reads the single-piece processing completion status and group process completion status corresponding to each slice status object. If the current slice status object does not meet the single-piece processing completion status, then that slice position is not considered as a control boundary candidate position, and a non-candidate status is written into the initial boundary marker sequence; if the current slice status object meets the single-piece processing completion status, then it continues to determine whether it meets the group process completion status.

[0049] When both the single-piece processing completion state and the group process completion state are simultaneously satisfied, the cross-cutting programming data processing unit initially marks the piece sequence position as a candidate stopable control boundary and writes the candidate stopable state into the initial boundary marker sequence. When only the single-piece processing completion state is satisfied but the group process completion state is not, the cross-cutting programming data processing unit initially marks the piece sequence position as a candidate restricted control boundary and writes the candidate restricted state into the initial boundary marker sequence. Thus, the initial boundary marker sequence forms a discrete marker for each piece sequence position in the continuous piece sequence state table, and the candidate stopable state, the candidate restricted state, and the non-candidate state together serve as adjacent comparison objects for piece sequence stability calculation.

[0050] After completing the initial boundary marking sequence, the cross-cutting programming data processing unit only performs dual-evidence calculations on candidate stopable control boundaries. Candidate restricted control boundaries retain their restricted attributes and are included in the summary of control boundary identification results. For the first... For each candidate stopable control boundary, the cross-cutting programming data processing unit first retrieves the corresponding slice state object from the continuous slice state table, then reads the matching result between the slice state object and the group constraint model, and determines the number of group constraint terms acting on the slice state object. Before entering the calculation of the grouped redundancy formula, the cross-cutting programming data processing unit first checks the number of grouped constraint terms n_b; only when n_b is greater than or equal to 1 will it continue to perform subsequent normalization and mean square synthesis.

[0051] Before normalizing the deviation, the cross-cutting programming data processing unit verifies the allowable judgment scale Λ_b,r item by item; only when every Λ_b,r is greater than 0 is the division operation between the deviation and the allowable judgment scale performed. If any Λ_b,r is not greater than 0, the grouped redundancy formula below is not executed, and the abnormal path of invalid allowable judgment scale is handled as described later. For each matched grouped constraint item, the cross-cutting programming data processing unit first generates the constraint completion amount, and then compares the constraint completion amount with the target completion status on the same scale to obtain the deviation. Then read the allowable decision criteria from the group constraint terms. The deviations are normalized. For thickness-based sheet counting conditions, the deviation is the absolute value of the difference between the target completion number of sheets or the cumulative thickness and the constraint completion amount; for material grouping conditions, the deviation is the number of missing sheets between the target pairing quantity and the number of already in place pairings; for stacking grouping conditions, the deviation is the number of missing sheets between the target stacking sequence number and the number of already consecutively in place sequence. After all normalized deviations are generated, the cross-cutting programming data processing unit performs mean square synthesis and converts them into grouping margins. ; in, Indicates the first The group redundancy of each candidate stopable control boundary is used to represent the degree of fit between the candidate stopable control boundary and the group process completion state; The sequence number representing the candidate stopable control boundary is derived from the set of slice positions initially identified as candidate stopable control boundaries; Indicates the action on the first The number of group constraints for each candidate stopable control boundary corresponding to a segmented state object is derived from the matching result between the segmented state object and the group constraint model. Indicates the first The first candidate stopable control boundary matched by Grouped constraint terms; Indicates the first The candidate stopable control boundary is at the first The deviation from the target completion state under each group constraint; Indicates the first The candidate stopable control boundary is at the first The permissible decision criterion under each group constraint term is derived from the corresponding constraint term in the group constraint model. If the permissible decision criterion is given by a number, then This refers to the allowed number of deviated wafers, the allowed number of deviated pairs, or the allowed number of deviated stacks; if the allowable judgment criterion is given by the cumulative thickness, then... To allow for cumulative deviations from thickness.

[0052] when When the value is 0, it indicates that the slice state object corresponding to the candidate stopable control boundary has not matched a group constraint term. The cross-cutting programming data processing unit does not calculate the group redundancy and downgrades the candidate stopable control boundary to a restricted control boundary. Simultaneously, it records the reason for the failure to match a group constraint term. If there is... Grouped constraint terms not greater than 0 indicate that the corresponding grouped constraint terms lack a valid permissible decision criterion. The cross-cutting programming data processing unit does not use this candidate stopable control boundary in the evidence fusion analysis, but downgrades and labels it as a restricted control boundary, and records the anomaly reason for the invalid permissible decision criterion. The above anomaly reason is included in the control boundary identification result along with the restricted control boundary and is called when generating boundary prompt data in step S4.

[0053] The group process completion status is used to provide a Boolean judgment result on whether the chip sequence status object has met the group completion condition. The group redundancy is used to continue to represent the degree of process fit between the candidate stopable control boundary and the target completion status in the Boolean judgment result. For the same group constraint, reaching the group process completion status means that the deviation has fallen within the acceptable range defined by the allowable judgment scale, and the deviation is not necessarily 0; the group redundancy continues to distinguish the stability of the candidate stopable control boundary based on the magnitude of the deviation within the allowable judgment scale.

[0054] After completing the group redundancy calculation, the cross-shear programming data processing unit uses the slice sequence position of the same candidate stopable control boundary as the center and reads the boundary markers within its slice sequence neighborhood from the initial boundary marker sequence. The slice sequence neighborhood is the range of boundary markers read forward and backward from the slice sequence position of the candidate stopable control boundary, based on the preset neighborhood width given by the process safety configuration in the cross-shear slice configuration data. For example, if the process safety configuration records that the slice sequence neighborhood reads two slice sequence positions forward and two slice sequence positions backward, then the cross-shear programming data processing unit uses the slice sequence position of the candidate stopable control boundary as the center, reads the two boundary markers before and two after that slice sequence position from the initial boundary marker sequence, and uses these boundary markers together as the slice sequence neighborhood for calculating slice sequence stability. If the candidate stopable control boundary is located at the beginning or end of the continuous slice sequence state table, the slice sequence neighborhood is truncated according to the actual boundary of the continuous slice sequence state table.

[0055] The cross-cutting programming data processing unit compares adjacent boundary markers within the slice sequence neighborhood according to slice position. If two adjacent boundary markers are different, it is counted as one change, and the number of changes is obtained. The maximum number of changes that can occur within the slice order neighborhood. Subtract 1 from the actual number of boundary markers read. When the actual number of boundary markers read within the slice order neighborhood is... hour, When the number of boundary markers actually read within the slice order neighborhood, q_b, is 1, there are 0 pairs of adjacent markers that can change. The cross-cutting programming data processing unit does not use C_b^max as a divisor, nor does it substitute it into the following formula. Instead, it directly sets the slice order stability Q_b to 1. When q_b is greater than or equal to 2, C_b^max = q_b - 1 and is not less than 1. The cross-cutting programming data processing unit calculates the slice order stability using the following formula: ; in, Indicates the first The slice order stability of a candidate stopable control boundary is used to indicate whether the boundary markers within the slice order neighborhood of the candidate stopable control boundary are stable. Indicates the first The number of times the adjacent boundary markers within the slice sequence neighborhood of a candidate haltable control boundary change; Indicates the first The maximum number of changes that can occur within the slice order neighborhood of a candidate haltable control boundary; Indicates the first The number of boundary markers actually read within the slice order neighborhood corresponding to each candidate haltable control boundary is derived from the initial boundary marker sequence. When the slice order neighborhood contains only one boundary marker, then... When the value is 0, the slice order stability of the candidate haltable control boundary is treated as 1, and the process continues into evidence mapping. Here, q_b represents the number of boundary markers actually read within the slice order neighborhood, i.e., the number of samples; C_b^max represents the number of adjacent marker pairs formed by the above samples, which is also the maximum number of possible variations used in the normalization denominator. These two values ​​have different meanings.

[0056] The cross-cutting programming data processing unit converts grouped redundancy into first evidence and fragment order stability into second evidence. The first evidence represents the degree of support of grouped redundancy for the establishment of candidate stopable control boundaries or restricted control boundaries, while the second evidence represents the degree of support of fragment order stability for the establishment of candidate stopable control boundaries or restricted control boundaries. In one embodiment, the preset evidence mapping rule uses a monotone complementary mapping method, mapping grouped redundancy and fragment order stability to basic probability assignments on two discriminant propositions, respectively. Higher grouped redundancy or fragment order stability indicates higher support for the establishment of candidate stopable control boundaries; lower grouped redundancy or fragment order stability indicates higher support for the establishment of restricted control boundaries. When using linear complementary mapping, the first and second evidence are formed according to the following relationship: ; ; in, The degree to which the primary evidence supports the establishment of the candidate stopable control boundary is derived from group redundancy. ; The degree to which the first piece of evidence supports the establishment of the restricted control boundary originates from... ; The degree to which the second piece of evidence supports the establishment of the candidate haltable control boundary is derived from slice order stability. ; The degree to which the second piece of evidence supports the establishment of the restricted control boundary originates from... ; This indicates that the candidate stopable control boundary condition is met; This indicates the conditional proposition that the restricted control boundary is valid.

[0057] The cross-cutting programming data processing unit then performs non-training evidence fusion analysis, combining the first and second pieces of evidence according to evidence synthesis rules to obtain boundary confidence and evidence conflict degree. The evidence conflict degree is first calculated as the product of the contradictory directions of the two pieces of evidence: ; in, Indicates the first The degree of evidence conflict for each candidate haltable control boundary is used to indicate the degree of contradiction between the first and second pieces of evidence. A higher degree of evidence conflict indicates a greater inconsistency between the group constraint side and the fragment order stability side in their judgments of the same candidate haltable control boundary.

[0058] Boundary confidence is obtained by normalizing the consistent support terms in the direction of the candidate haltable control boundary: ; in, Indicates the first The boundary confidence of a candidate stopable control boundary is used to indicate the degree of support for confirming the candidate stopable control boundary as a stopable control boundary. This represents the consistency normalization term in the synthesis of evidence, used to exclude conflicting parts between the first and second pieces of evidence.

[0059] Before using boundary confidence to determine whether a shutdown is permissible, the cross-cutting programming data processing unit first checks whether the degree of evidence conflict meets the consistency criteria. If the degree of evidence conflict exceeds a preset conflict limit, or if the degree of evidence conflict causes the consistency normalization term to fail, the shutdown is initiated. When the boundary confidence level cannot be calculated, the cross-cutting programming data processing unit no longer calculates the normalized boundary confidence level, but directly sends the candidate stopable control boundary into the degradation path and marks it as a restricted control boundary. Only when the degree of evidence conflict meets the consistency determination condition and Boundary confidence is calculated only when it can be used for normalization calculations, based on the evidence synthesis rules.

[0060] The preset credibility requirements and preset conflict limits are synchronously written into the process safety configuration when the cross-sliding sheet configuration data is generated, or are pre-saved in the boundary control strategy of the cross-sliding control system. Both the preset credibility requirements and preset conflict limits are dimensionless values ​​between 0 and 1, respectively, and are in the same numerical domain as the boundary credibility and evidence conflict level. In one embodiment, the process safety configuration records the lower limit of boundary credibility and the upper limit of evidence conflict level. For example, when the lower limit of boundary credibility is configured as 0.75 and the upper limit of evidence conflict level is configured as 0.30, the cross-sliding programming data processing unit reads 0.75 as the preset credibility requirement and 0.30 as the preset conflict limit. When the boundary credibility corresponding to a candidate stopable control boundary is greater than or equal to 0.75 and the evidence conflict level is less than or equal to 0.30, it is determined that the corresponding judgment condition is met. In another implementation, the boundary control strategy records the lower limit of boundary confidence and the upper limit of evidence conflict corresponding to the current chip type. For example, if these are recorded as 0.80 and 0.25 respectively, the cross-cutting programming data processing unit reads 0.80 as a preset confidence requirement and 0.25 as a preset conflict limit, and compares and determines the candidate stopable control boundaries corresponding to the current chip type accordingly. If neither the cross-cutting chip type configuration data nor the boundary control strategy provides a preset confidence requirement or a preset conflict limit, the cross-cutting programming data processing unit adopts a conservative default approach, downgrading the corresponding candidate stopable control boundary to a restricted control boundary, and recording the reason for the missing threshold in the control boundary identification result. Before performing the final boundary determination, the cross-cutting programming data processing unit reads the preset confidence requirement and the preset conflict limit, using the preset confidence requirement as the lower limit comparison value of boundary confidence and the preset conflict limit as the upper limit comparison value of evidence conflict. When the boundary confidence is greater than or equal to the preset confidence requirement, it is determined that the stopable determination condition is met; when the boundary confidence is less than the preset confidence requirement, it is determined that the stopable determination condition is not met. When the degree of conflict of evidence is less than or equal to the preset conflict limit, it is determined that the consistency judgment condition is met; when the degree of conflict of evidence is greater than the preset conflict limit, it is determined that the consistency judgment condition is not met. If both the cross-cutting wafer configuration data and the boundary control strategy provide the above values, the process safety configuration corresponding to the current wafer type in the cross-cutting wafer configuration data shall prevail.

[0061] The cross-cutting programming data processing unit performs a two-condition judgment on each candidate stopable control boundary. If the boundary credibility corresponding to the candidate stopable control boundary meets the stopable judgment condition and the evidence conflict degree meets the consistency judgment condition, then the candidate stopable control boundary is confirmed as a stopable control boundary; if the boundary credibility does not meet the preset credibility requirement, or the evidence conflict degree exceeds the preset conflict limit, then the candidate stopable control boundary is downgraded and marked as a restricted control boundary. The downgrade marking is performed by preserving the original slice order position, that is, the boundary position is not deleted, only its final boundary attribute is rewritten from a candidate stopable control boundary to a restricted control boundary.

[0062] After all candidate stopable control boundaries have been confirmed or downgraded, the cross-cutting programming data processing unit summarizes the confirmed stopable control boundaries, the candidate restricted control boundaries formed by the initial calibration, and the restricted control boundaries formed by the downgrade, and generates control boundary identification results. The control boundary identification results retain the slice sequence position and final boundary attributes corresponding to each boundary, and serve as the direct basis for generating boundary control data and boundary prompt data in step S4.

[0063] S4: Generate boundary control data and boundary prompt data based on the control boundary identification results, and combine the boundary control data, boundary prompt data and the slice type parameter relationship diagram to generate a cross-cut slice type programming configuration package.

[0064] Step S4 takes the control boundary identification result output in step S3 and the sheet type parameter relationship diagram output in step S1 as input. The cross-cutting programming data processing unit generates boundary control data and boundary prompt data based on the control boundary identification result, and then combines the boundary control data, boundary prompt data, and sheet type parameter relationship diagram to generate a cross-cutting sheet type programming configuration package.

[0065] The cross-cutting programming data processing unit reads each boundary position from the control boundary identification results in sequential order and distinguishes the final boundary attribute corresponding to that position. When a stopable control boundary is read, the position is written to the allowed trigger position set; when a restricted control boundary is read, the position is written to the restricted trigger position set. The allowed trigger position set is formed by the confirmed stopable control boundaries and represents the triggerable position of the run control command; the restricted trigger position set is formed by the restricted control boundaries and represents the restricted position of the run control command. The restricted trigger position set includes the position corresponding to the restricted control boundary formed by the continuation of the candidate restricted control boundary, and the position corresponding to the restricted control boundary formed by the downgrading of the candidate stopable control boundary.

[0066] The cross-cutting programming data processing unit generates boundary control data based on the set of allowed trigger positions and the set of restricted trigger positions. The boundary control data is generated according to the correspondence between slice positions and run control instructions. The cross-cutting programming data processing unit uses the slice position order in the continuous slice position status table as the slice position index and the run control instructions corresponding to continuous run, pause, stop, and single-step debugging as the instruction index to form an instruction triggering permission relationship. Continuous run instructions are executed according to the slice order in the continuous slice position status table. For each slice position within the allowed trigger position set, the cross-cutting programming data processing unit writes the corresponding pause instruction, stop instruction, and single-step debugging instruction into the allowed trigger attribute, meaning all three instructions are allowed to be triggered at that slice position. For each slice position within the restricted trigger position set, the cross-cutting programming data processing unit writes the corresponding pause instruction, stop instruction, and single-step debugging instruction into the restricted trigger attribute, meaning all three instructions are restricted at that slice position. When the cross-cutting control system reads boundary control data, it first matches the current slice position, then reads the trigger attributes of the pause command, stop command and single-step debugging command under that slice position, and allows or restricts the triggering of the corresponding operation control command accordingly.

[0067] For example, when five consecutive pieces form the same thickness recording unit, although the first to fourth pieces have already completed single-piece shearing, they are marked as restricted control boundaries in step S3. The cross-cutting programming data processing unit writes these four piece sequence positions into the restricted trigger position set. The fifth piece reaches the completion state in both the thickness recording condition and the material grouping condition, and is confirmed as a stopable control boundary after passing the dual-evidence boundary discrimination processing. The cross-cutting programming data processing unit writes the corresponding piece sequence position of the fifth piece into the allowed trigger position set. After the boundary control data is formed, when the cross-cutting control system reads this data, pause, stop, and single-step debugging commands can only be triggered at the corresponding piece sequence position of the fifth piece.

[0068] The cross-cutting programming data processing unit continues to generate boundary prompt data based on the set of restricted trigger positions and the control boundary identification results. The cross-cutting programming data processing unit reads each restricted control boundary item by item and determines the formation path of that restricted control boundary in step S3. The formation path includes restricted control boundaries formed by the continuation of candidate restricted control boundaries, and restricted control boundaries formed by the downgrading of candidate stopable control boundaries through dual-evidence boundary discrimination processing; the formation path originates from the boundary determination process retained in the control boundary identification results.

[0069] For restricted control boundaries formed by the continuation of candidate restricted control boundaries, the cross-cutting programming data processing unit reads the single-piece processing completion status and group process completion status of the corresponding slice sequence state object at the slice sequence position, and generates boundary prompt data to indicate inconsistencies between the single-piece processing completion status and the group process completion status. For restricted control boundaries formed by the downgrading of candidate stopable control boundaries, the cross-cutting programming data processing unit reads the boundary credibility and evidence conflict degree of the slice sequence position in the dual evidence boundary discrimination process, and generates boundary prompt data to indicate that the candidate stopable control boundary has failed the dual evidence boundary discrimination process. If the restricted control boundary is caused by a failure to match a group constraint, an invalid allowable judgment scale, or a missing threshold, the cross-cutting programming data processing unit reads the abnormal reason recorded in the control boundary identification result and writes the abnormal reason into the boundary prompt data of the corresponding slice sequence position. Each boundary prompt data uses the slice sequence position corresponding to the restricted control boundary as an index and maintains a correspondence with the formation path of that slice sequence position; when the visual configuration interface reads the boundary prompt data, it first matches the slice sequence position and then displays the boundary inconsistency risk corresponding to that slice sequence position.

[0070] Subsequently, the cross-scissor programming data processing unit takes boundary control data, boundary warning data, and slice parameter relationship diagram as input and performs configuration package combination processing. The cross-scissor programming data processing unit first writes the slice parameter relationship diagram into the cross-scissor slice programming configuration package, ensuring that the cross-scissor slice programming configuration package retains the correspondence between executable slice units in the slice execution model and constraint terms in the group constraint model; then it writes boundary control data, enabling the cross-scissor slice programming configuration package to provide operation control command trigger position constraints to the cross-scissor control system; finally, it writes boundary warning data, enabling the cross-scissor slice programming configuration package to provide warning content corresponding to the restricted control boundaries to the visual configuration interface.

[0071] After the slice parameter relationship diagram, boundary control data, and boundary warning data are written into the same cross-cut slice programming configuration package, the three maintain correspondence through slice order position, slice order state object, and boundary attributes. After writing is complete, the cross-cut programming data processing unit performs a slice order position consistency check. The cross-cut programming data processing unit reads the slice order position from the boundary control data and boundary warning data one by one, and traces back to the slice order state object corresponding to the same slice order position in the consecutive slice order state table. Then, it reads the corresponding executable slice unit and constraint item in the slice parameter relationship diagram from the slice order state object. If a slice position can be traced back to the corresponding executable slice unit and constraint, the boundary control data and boundary hint data corresponding to that slice position are retained. If a slice position cannot be traced back to the corresponding executable slice unit and constraint, the cross-cut programming data processing unit marks that slice position as a consistency check failure position, suspends the output of the cross-cut slice programming configuration package, and regenerates the correspondence between the boundary control data, boundary hint data and slice parameter relationship diagram based on the consistency check failure position. After regeneration, the slice position consistency check is performed again until all slice positions can be traced back to the corresponding executable slice unit and constraint.

[0072] After the cross-scissor blade programming configuration package is generated, when the cross-scissor control system reads the cross-scissor blade programming configuration package, it determines the allowed trigger positions for operation control commands such as continuous operation, pause, stop, or single-step debugging based on the boundary control data. When the visual configuration interface reads the cross-scissor blade programming configuration package, it displays the risk of boundary inconsistency at the corresponding blade sequence position of the restricted control boundary based on the boundary prompt data. When the cross-scissor programming data processing unit performs subsequent configuration review or program generation, it traces the executable blade unit and constraint items corresponding to each boundary position based on the blade parameter relationship diagram.

[0073] Through steps S1 to S4, the cross-slitting sheet configuration data is parsed into a sheet execution model and a group constraint model, and a correspondence between the sheet processing sequence and continuous grouping conditions is established through a sheet parameter relationship diagram. The sheet execution model is expanded into a continuous sheet sequence status table, which stores the single sheet processing completion status and the group process completion status at the same sheet sequence position. The continuous sheet sequence status table is further converted into control boundary identification results. Candidate stopable control boundaries are confirmed or downgraded after being judged by group redundancy, sheet sequence stability, boundary credibility, and evidence conflict degree. The finally generated cross-slitting sheet programming configuration package contains a sheet parameter relationship diagram, boundary control data, and boundary prompt data, which can uniformly provide the sheet processing sequence, group constraint relationship, operation control boundary, and visual prompt content to the cross-slitting control system or cross-slitting programming system.

[0074] The above embodiments are merely preferred embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, or improvements 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 rapid programming configuration of parameters for cross-cutting silicon steel sheets, characterized in that, include: S1: Obtain the cross-cutting slicing configuration data formed by the visual configuration, perform structured parsing on the cross-cutting slicing configuration data, generate the slicing execution model and the group constraint model, and construct the slicing parameter relationship diagram based on the relationship between the two. S2: Based on the slice parameter relationship diagram, the slice execution model is continuously expanded into slice sequence to generate slice sequence state objects, and the group constraint model is applied to the slice sequence state objects to obtain a continuous slice sequence state table. S3: Perform control boundary identification based on the continuous slice state table, and perform dual evidence boundary discrimination processing on the candidate stopable control boundaries obtained by the control boundary identification to generate control boundary identification results; S4: Generate boundary control data and boundary prompt data based on the control boundary identification results, and combine the boundary control data, boundary prompt data and the slice type parameter relationship diagram to generate a cross-cut slice type programming configuration package.

2. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 1, characterized in that, In step S1, the structured parsing includes: reading the configuration content used to limit the processing order from the cross-cutting sheet configuration data, identifying the sheet configuration items that can be executed by cross-cutting as executable sheet units, and forming a sheet parsing sequence according to the processing order; at the same time, reading the configuration content of thickness recording, material grouping, and stacking grouping to form a constraint parsing set containing constraint items, and reading the configuration reference relationship between executable sheet units and constraint items to form an association index set.

3. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 2, characterized in that, In step S1, a slice execution model is generated based on the slice parsing sequence. The slice execution model includes the slice execution nodes corresponding to the executable slice units, the sequential connection relationship, and the termination node. A group constraint model is generated based on the constraint parsing set. The group constraint model includes the constraint object, the target completion state, and the allowed judgment scale. Then, based on the association index set, the slice nodes and constraint nodes are connected to generate a slice parameter relationship diagram.

4. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 1, characterized in that, In step S2, the constraint terms corresponding to each executable slice unit in the slice execution model are read based on the slice parameter relationship diagram, and a slice expansion sequence is formed along the sequential connection relationship in the slice execution model; according to the continuous slice expansion range, the executable slice units in the slice expansion sequence are expanded into slice state objects one by one, and a slice position is assigned to each slice state object, so that the slice position is consistent in the continuous slice state table, control boundary identification results, boundary control data and boundary prompt data.

5. The method for rapid programming configuration of visualized parameters for silicon steel cross-cutting sheets according to claim 4, characterized in that, In step S2, the single-piece processing completion status of the slice sequence state object is marked according to the endable node in the slice type execution model; the constraint items corresponding to the slice sequence state object are obtained through the slice type parameter relationship diagram, and the constraint completion quantity is generated by calling the group constraint model. The constraint completion quantity is compared with the corresponding target completion status. When all constraint items for the same slice sequence state object have reached the target completion status, the group process completion status is marked.

6. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 5, characterized in that, In step S3, each chip sequence state object is read in the order of its position in the continuous chip sequence state table, and an initial boundary marker sequence is generated based on the single-chip processing completion state and the group process completion state. Chip sequence positions that do not meet the single-chip processing completion state are written as non-candidate states, chip sequence positions that meet the single-chip processing completion state but do not meet the group process completion state are marked as candidate restricted control boundaries, and chip sequence positions that meet both the single-chip processing completion state and the group process completion state are marked as candidate stopable control boundaries.

7. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 6, characterized in that, In step S3, when performing dual-evidence boundary discrimination processing on the candidate stopable control boundary, the corresponding fragment state object is obtained from the continuous fragment state table, and the deviation of the fragment state object from the target completion state is calculated according to the group constraint model to obtain the group redundancy; then, taking the fragment position where the candidate stopable control boundary is located as the center, the fragment neighborhood in the initial boundary marker sequence is read to calculate the fragment stability.

8. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 7, characterized in that, In step S3, group redundancy is converted into first evidence, fragment order stability is converted into second evidence, and non-training evidence fusion analysis is performed based on the first and second evidence to obtain boundary credibility and evidence conflict degree. When the boundary credibility meets the shutdown determination condition and the evidence conflict degree meets the consistency determination condition, the corresponding candidate shutdown control boundary is confirmed as a shutdown control boundary. When the boundary credibility does not meet the shutdown determination condition or the evidence conflict degree does not meet the consistency determination condition, the corresponding candidate shutdown control boundary is downgraded and labeled as a restricted control boundary.

9. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 8, characterized in that, In step S4, according to the slice position and final boundary attribute in the control boundary identification result, the slice position corresponding to the stopable control boundary is written into the allowed trigger position set, and the slice position corresponding to the restricted control boundary is written into the restricted trigger position set. Next, boundary control data is generated according to the correspondence between chip sequence positions and operation control instructions. For each chip sequence position in the set of allowed trigger positions, the pause instruction, stop instruction, and single-step debugging instruction corresponding to that chip sequence position are all set as allowed trigger attributes. For each chip sequence position in the set of restricted trigger positions, the pause instruction, stop instruction, and single-step debugging instruction corresponding to that chip sequence position are all set as restricted trigger attributes.

10. The method for rapid programming configuration of visualized parameters for cross-cutting silicon steel sheets according to claim 9, characterized in that, In step S4, boundary hint data is generated based on the formation path of the restricted control boundary, and the slice parameter relationship diagram, boundary control data, and boundary hint data are written into the cross-cut slice programming configuration package. After the cross-cut slice programming configuration package is written, the slice sequence state objects in the continuous slice sequence state table are traced back by slice sequence position, and the corresponding executable slice unit and constraint item in the slice parameter relationship diagram are read to perform slice sequence position consistency verification on the cross-cut slice programming configuration package.

Images