A constrained cable structure simulation optimization method

Abstract

This invention relates to the field of cable structure simulation technology, specifically a method for optimizing constrained cable structure simulation. The method acquires the cable design data, including model, voltage level, specifications, standard type, customer constraints, material parameters, process parameters, and calculation accuracy, forming a design constraint dataset. Based on this dataset, a calculation parameter table is generated, and an electrical result dataset is calculated. The electrical result dataset is mapped to structural dimension constraints to generate structural hierarchy data, resulting in a cable cross-section simulation diagram. The hierarchy, scale, dimensions, material relationships, and electrical results of the cable cross-section simulation diagram are checked. Parameters or layers are corrected based on conflicting results, and the diagram is regenerated until a structural design scheme that satisfies the constraints is determined. A unified version of the technical specifications is then output. This method reduces errors from manual calculations and drawing, ensuring consistency between parameter results, structural diagrams, and production guidance data.

Description

Technical Field

[0001] This invention relates to the field of cable structure simulation technology, and in particular to a method for optimizing constrained cable structure simulation. Background Technology

[0002] The field of cable structure simulation technology involves the modeling of structural parameters, calculation of electrical parameters, representation of cross-sectional graphics, and management of process documents for wire and cable products in a computer environment. Traditional cable process design refers to a process engineer manually calculating electrical parameters based on cable type, specifications, voltage level, material information, process parameters, and applicable standards. This process involves using drawing tools to create cable cross-sectional diagrams, and then compiling the calculation results, diagrams, and process specifications into production guidance documents.

[0003] Current cable process design relies on process engineers manually calculating parameters such as resistance, impedance, and voltage drop, and manually drawing structural diagrams. There are many formulas and parameters from scattered sources, and the calculation results need to be repeatedly checked. The structural layer level and scale depend on experience judgment. Material and process information and graphic objects are difficult to synchronize. Version records and technical specifications are prone to inconsistencies. When standard customer requirements or specification adjustments occur in the design task, there is a lack of linkage verification path between parameters and layers, which leads to extended design cycles. Incorrect results, after entering production guidance, affect the judgment of cable structural dimensions and electrical performance. Summary of the Invention

[0004] To address the aforementioned technical problems, this invention provides a method for optimizing constrained cable structure through simulation, comprising the following steps: obtaining cable type, voltage level, specifications, standard type, customer constraints, material parameters, process parameters, and calculation accuracy from the cable design task to form a design constraint dataset; reading basic parameters matching the cable type, specifications, and standard type from the parameter database and structural dimension table based on the design constraint dataset to form a calculation parameter table and structural dimension constraints; generating an electrical result dataset containing resistance, impedance, capacitance, inductance, reactance, voltage drop, and current based on the calculation parameter table and preset cable electrical parameter calculation rules; mapping the design constraint dataset, electrical result dataset, and structural dimension constraints according to cable level type, dimension boundary, material field, and process field to form structural level data, and generating a cable cross-section simulation diagram based on the structural level data; performing consistency checks on the cable cross-section simulation diagram, structural level data, and electrical result dataset, with checks including level order, structural proportion, dimension boundary, material association, electrical results, and standardized output fields; if inconsistencies exist in the check comparison results, parameters or layers are corrected based on conflict records and regenerated; if no conflict records exist, the corresponding scheme is determined as the structural design scheme.

[0005] Furthermore, when forming the design constraint dataset, the system receives cable type, material code, process classification, specifications, structure table type, version number, standard type, parameter selection options, and display decimal places. It uses cable type, specifications, standard type, and version number as task index fields, parameter selection options as the basis for filtering calculation fields, and display decimal places as the result precision field. For inputs lacking task index fields, a missing marker is generated. For inputs with multiple version numbers under the same task index field, a set of version data is read according to the effective status corresponding to the version number, and the reading results are written into the design constraint dataset.

[0006] As a progressive approach, when generating the calculation parameter table, phase voltage, line voltage, number of cores, conductor outer diameter, insulation outer diameter, cable outer diameter, relative permittivity of insulation material, cable inductance, conductor-to-axis distance, DC resistance, conductor temperature coefficient, operating temperature, skin effect coefficient, proximity effect coefficient, frequency, ground leakage resistance, ground loop distance, current, cable length, motor power, and power factor are extracted from the design constraint dataset based on the parameter selection options. The fields are then grouped according to voltage parameters, current parameters, geometric dimension parameters, material correction parameters, operating condition correction parameters, and line environment parameters, so that the same calculation parameter table can be read by both electrical parameter calculation and structural level mapping.

[0007] Furthermore, when generating the electrical results dataset, geometric dimension parameters, material correction parameters, operating condition correction parameters, and line environment parameters are read according to the field grouping in the calculation parameter table; capacitance, inductance, reactance, AC resistance at operating temperature, positive sequence impedance, negative sequence impedance, zero sequence impedance, voltage drop, and current are calculated according to the preset cable electrical parameter calculation rules; each calculation result is bound to the corresponding input field grouping, calculation time, accuracy field, and result field name to form an electrical results dataset that can be read for structural hierarchy mapping and consistency verification.

[0008] Furthermore, when generating structural hierarchy data, the layers to be generated among conductor layer, insulation layer, filler layer, wrapping layer, inner sheath, wire armor layer, metal strip armor layer, and outer sheath are determined according to structural size constraints. For each layer to be generated, the hierarchy order, outer diameter boundary, center position, material field, process field, and electrical association field corresponding to the electrical result dataset are written. Cross-sectional graphic objects are generated according to the hierarchy order and outer diameter boundary, and the material field, process field, and electrical association field are bound to the cross-sectional graphic objects to obtain the cable cross-section simulation diagram.

[0009] Furthermore, when generating a conflict record, the hierarchical order, graphic size, display scale, material field, and process field of each layer in the cable cross-section simulation diagram are read; the hierarchical order of the layers is compared with the hierarchical order in the structural hierarchical data; the graphic size and display scale of the layers are compared with the structural dimensional constraints; the material field and process field of the layers are compared with the design constraint dataset; and the electrical result dataset is compared with the electrical performance requirements corresponding to the standard type and customer constraints. When any of the above comparison results are inconsistent, a conflict record containing the conflict object, conflict field, source data, target data, and processing type is written.

[0010] As a progressive solution, when correcting parameters or layers based on conflict records, if the conflict record's processing type is electrical result conflict, the corresponding input field group is read and the calculation parameter table is returned for parameter correction and recalculation; if the conflict record's processing type is structural dimension conflict, the corresponding structural dimension constraints are read and the structural hierarchy data is returned for outer diameter boundary or hierarchy order correction; if the conflict record's processing type is material association conflict or process field conflict, the corresponding material field or process field is read and the cable cross-section simulation diagram is returned for layer editing; the corrected calculation parameter table, structural hierarchy data, or cable cross-section simulation diagram re-enters consistency verification until no more conflict records are generated or a mark awaiting manual confirmation is generated.

[0011] Furthermore, after determining the structural design scheme, the design constraint dataset, electrical result dataset, structural hierarchy data, cable cross-section simulation diagram, and version number from the structural design scheme are written into the scheme record. Technical specification data is generated based on the scheme record, which includes cable type, specifications, voltage level, standard type, material field, process field, electrical result field, and structural hierarchy field. When the scheme record is read again, the version number is used as a unified index to synchronously read the electrical result field, structural hierarchy field, and cable cross-section simulation diagram.

[0012] As an additional constraint, the consistency check also includes handling of abnormal inputs. When the design constraint dataset lacks cable type, specification, voltage level, or standard type, the generation of the calculation parameter table is stopped and the missing field is output. When a parameter in the calculation parameter table is missing, the calculation of the corresponding electrical result field is stopped and a calculation failure flag is written to the electrical result dataset. When the structural dimension constraints and the electrical result dataset cannot be mapped to the same level, the generation of the corresponding layer is stopped and a mapping failure flag is written to the conflict record. When the same conflicting object still produces the same conflicting field after correction, the source data and target data before and after the most recent correction are retained and a flag for manual confirmation is generated.

[0013] Furthermore, when generating technical specification data, the cable model, specifications, voltage level, standard type, material field, process field, electrical result field, structural level field, and version number are read from the scheme record. The electrical result field is categorized into resistance, impedance, capacitance, inductance, reactance, voltage drop, and current and written into the electrical parameter table. The structural level field is categorized into conductor layer, insulation layer, filler layer, wrapping layer, inner sheath, armor layer, and outer sheath and written into the structural parameter table. The electrical parameter table, structural parameter table, and cable cross-section simulation diagram are bound to the same version of output data, so that the technical specification data, graphic objects, and parameter results have the same version index.

[0014] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, cable type, specifications, voltage level, standard type, customer constraints, material parameters, and process parameters are unified into a design constraint dataset. The calculation parameter table, electrical result dataset, structural hierarchy data, and cable cross-section simulation diagram flow continuously. Results such as resistance, impedance, capacitance, inductance, and voltage drop can directly participate in the generation and verification of structural diagrams. Conflict records drive parameter correction, layer editing, and regeneration. Parameter results, structural proportions, material relationships, and version output form a closed loop, reducing errors caused by manual calculations, manual drawing, and document splicing, ensuring consistency between production guidance documents and the confirmed structural design scheme. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the overall data flow topology for a constrained cable structure simulation optimization method. Figure 2 A schematic diagram of the data structure for designing the constraint dataset and the calculation parameter table; Figure 3 This is a diagram illustrating the formation of the electrical results dataset and the binding relationships between the results fields; Figure 4 A schematic diagram of object binding relationships for converting structural hierarchy data into cable cross-section simulation diagrams; Figure 5 A schematic diagram illustrating the closed-loop processing of consistency verification, conflict recording, and scheme recording. Detailed Implementation

[0016] The following implementation method illustrates the feasible process of a constraint cable structure simulation optimization method. In this document, the design constraint dataset refers to the data set formed by inputting cable design tasks and merging fields; the calculation parameter table refers to the data table extracted from the design constraint dataset, parameter database, and structural dimension table and grouped according to calculation purpose; the electrical result dataset refers to the result set formed after the calculation parameter table participates in electrical parameter calculations; the structural hierarchy data refers to the data set used to describe the hierarchical order, dimensional boundaries, material fields, process fields, and electrical association fields of the conductor layer, insulation layer, filler layer, wrapping layer, inner sheath, armor layer, and outer sheath in the cable cross-section; the cable cross-section simulation diagram refers to the visual object of the cable cross-section transformed from the structural hierarchy data; the conflict record refers to the combined record of conflict objects, conflict fields, source data, target data, and processing type formed during consistency verification; and the scheme record refers to the structural design scheme record formed by binding the design constraint dataset, electrical result dataset, structural hierarchy data, cable cross-section simulation diagram, and version number.

[0017] Please see Figure 1 This embodiment provides a method for optimizing constrained cable structure through simulation. The method is executed by a computer system, which includes a parameter database, a structural dimension table, an electrical parameter calculation component, a structural diagram generation component, a consistency verification component, a layer editing component, and a specification data output component. The parameter database stores basic data corresponding to cable type, specifications, voltage level, material parameters, process parameters, and standard type. The structural dimension table stores cable cross-section levels and their dimensional boundaries. The electrical parameter calculation component reads the calculation parameter table and generates an electrical result dataset. The structural diagram generation component converts the structural level data into a cable cross-section simulation diagram. The consistency verification component compares the correspondence between parameters, layers, dimensions, materials, processes, and electrical results. The layer editing component corrects layer order, graphic size, display scale, and material or process fields. The specification data output component converts the confirmed structural design scheme into technical specification data.

[0018] S1 retrieves the cable type, voltage rating, specifications, standard type, customer constraints, material parameters, process parameters, and calculation accuracy from the cable design task, forming a design constraint dataset. Please refer to [link / reference]. Figure 2The computer system receives cable model, material code, process classification, specifications, structure table type, version number, standard type, parameter selection options, and display decimal places. Cable model, specifications, standard type, and version number are written to the task index field, which is used to locate basic and version data within the same design task. Parameter selection options are written to the calculation field as filtering criteria to determine the range of parameters participating in subsequent calculations. Display decimal places are written to the result retention precision field to limit the numerical display precision in the electrical result dataset. Customer constraints, material parameters, and process parameters are written to the constraint field group. Customer constraints define the customer requirements that the structural scheme must meet; material parameters define the corresponding material fields for conductors, insulation, fillers, tape, inner sheath, armor, and outer sheath; and process parameters define the process fields required for structural diagram generation and technical specification data output.

[0019] In S1, the input fields are broken down into task index fields, constraint field groups, calculation field filtering criteria, and result retention precision fields. The computer system first checks whether the task index field contains cable type, specifications, voltage level, and standard type. If any of these fields is empty, the system does not proceed to the parameter table formation stage but outputs the missing fields, allowing subsequent processing to explicitly stop at the input stage. For cases where multiple version numbers exist for the same cable type, specification, and standard type, the computer system reads the version status corresponding to each version number and first determines whether a unique, active version exists. If a unique, active version exists, only that version is written to the design constraint dataset. If no unique, active version exists, but multiple versions are readable, the computer system does not perform a single design constraint dataset write operation. Instead, it uses the version number as an index to create separate candidate design constraint datasets, which are then compared as candidate solutions in subsequent consistency checks. Before a candidate solution is determined, different version fields are not mixed into the same dataset.

[0020] S2, based on the design constraint dataset, reads the basic parameters matching the cable type, specifications, and standard type from the parameter database and structural dimension table to form a calculation parameter table and structural dimension constraints. Please refer to [link / reference]. Figure 2 and Figure 3The computer system uses the task index field as the search key to read parameters from the parameter database, including voltage level, number of cores, conductor outer diameter, insulation outer diameter, cable outer diameter, relative permittivity of insulation material, cable inductance, conductor-to-axis distance, DC resistance, conductor temperature coefficient, operating temperature, skin effect coefficient, proximity effect coefficient, frequency, ground leakage resistance, ground loop distance, current, cable length, motor power, and power factor. The read parameters are grouped and written into the calculation parameter table according to voltage parameters, current parameters, geometric dimension parameters, material correction parameters, operating condition correction parameters, and line environment parameters. Each parameter field retains a field name, field value, unit field, source field, and precision field. The unit field is used to limit the reading scope of parameters within the same group and across groups in subsequent processing. The source field identifies whether the field comes from design input, the parameter database, or the structural dimension table. The precision field constrains the display status of the electrical result dataset.

[0021] In S2, the structural dimension table uses cable type, specification, standard type, and structural table type as search keys to output structural dimension constraints. Structural dimension constraints include the layer to be generated, layer order, outer diameter boundary, center position, material field entry, and process field entry. For conductor layer, insulation layer, filler layer, wrapping layer, inner sheath, wire armor layer, metal tape armor layer, and outer sheath, the structural dimension table provides a status field for each layer indicating whether it participates in the generation process. Layers participating in the generation are written to the layers to be generated; layers not participating in the generation are marked as inactive layers, and inactive layers do not enter the layer generation process of the cable cross-section simulation diagram. Structural dimension constraints and calculation parameter tables are bound to the same version number, ensuring that subsequent electrical calculations, structural layer mapping, and technical specification data output maintain the same version index.

[0022] S3, based on the calculation parameter table and the preset cable electrical parameter calculation rules, generates an electrical result dataset containing resistance, impedance, capacitance, inductance, reactance, voltage drop, and current. Please refer to [link / reference]. Figure 3The electrical parameter calculation component reads the grouped fields from the calculation parameter table. For capacitance, inductance, and reactance, the component reads geometric parameters, the relative permittivity of the insulation material, frequency, and line environment parameters, and generates corresponding result fields according to the preset cable electrical parameter calculation rules. For AC resistance at operating temperature, the component reads DC resistance, conductor temperature coefficient, operating temperature, skin effect coefficient, and proximity effect coefficient, and writes the temperature-corrected and effect-corrected results into the AC resistance result field. For positive-sequence impedance, negative-sequence impedance, and zero-sequence impedance, the component reads resistance, reactance, conductor-axis distance, ground leakage resistance, and ground loop distance, and writes them into the impedance result field in sequence. For voltage drop, the electrical parameter calculation component reads the phase voltage, line voltage, input current field (which serves as the input condition for voltage drop calculation), cable length, and power factor, and writes the calculation results into the voltage drop result field. For current, the electrical parameter calculation component reads the phase voltage, line voltage, cable length, motor power, and power factor, and writes the calculation results formed by the above non-current result data into the current result field. The input current field is only used as the data source for voltage drop calculation and is not used as the input source for the current result field itself.

[0023] In S3, the electrical results dataset not only stores numerical results, but also the result field names, corresponding input field groups, calculation time, precision field, calculation status, and subsequent call identifier. The calculation status indicates whether the result field produces a readable result; when a parameter is missing, the electrical parameter calculation component stops calculating the corresponding result field and writes a calculation failure flag to the electrical results dataset. The subsequent call identifier indicates whether the corresponding result field will be read by structural hierarchy mapping, consistency verification, or technical specification data output. Through this field binding method, resistance, impedance, capacitance, inductance, reactance, voltage drop, and current are not displayed as isolated results, but rather continue to be processed as input data for cable structure scheme selection and adjustment.

[0024] S4 maps the design constraint dataset, electrical result dataset, and structural dimensional constraints according to cable level type, dimensional boundaries, material fields, and process fields to form structural level data, and generates cable cross-section simulation diagrams based on the structural level data. Please refer to [link / reference]. Figure 4The structural diagram generation component reads the layers to be generated and their order from the structural dimensional constraints and creates a layer record for each layer. The layer record includes layer type, layer order, outer diameter boundary, center position, material field, process field, and electrical association field. The layer type distinguishes conductor layers, insulation layers, filler layers, wrapping layers, inner sheaths, wire armor layers, metal strip armor layers, and outer sheaths; the layer order determines the arrangement order of layers in the cable cross-section; the outer diameter boundary determines the size range of the graphic objects; the center position defines the common positioning reference for each cross-section graphic object; the material and process fields bind the material and process parameters in the design constraint dataset to specific layers; and the electrical association field associates the result fields in the electrical result dataset with the corresponding layer.

[0025] In S4, after the structural hierarchy data is generated, the structural diagram generation component reads the hierarchy records in hierarchical order. First, it places the graphic object corresponding to the conductor layer in the center position, and then generates the cross-sectional graphic objects corresponding to the insulation layer, filler layer, wrapping layer, inner sheath, armor layer, and outer sheath layer by layer according to the outer diameter boundary. Each cross-sectional graphic object is bound to its hierarchy record, and the binding relationship includes the graphic object identifier, hierarchy type, material field, process field, and electrical association field. Graphic objects of the same hierarchy in the cable cross-section simulation diagram are written to the same layer, and the layer order is consistent with the hierarchy order in the structural hierarchy data. When the user performs layer editing, the layer editing component reads the graphic object identifier of the layer being edited and writes the modified graphic size, display scale, material field, or process field back to the structural hierarchy data, ensuring that the visualized object and the underlying structural data maintain the same modification entry point.

[0026] S5 performs consistency checks on the cable cross-section simulation diagram, structural hierarchy data, and electrical result dataset. The checks include hierarchy order, structural proportions, dimensional boundaries, material relationships, electrical results, and standardized output fields. If inconsistencies are found, parameters or layers are corrected based on conflict records, and the dataset is regenerated. If no conflict records are found, the corresponding scheme is determined as the structural design scheme. Please refer to [link to relevant documentation]. Figure 5The consistency verification component first reads the layer order, graphic size, display scale, material field, and process field of each layer in the cable cross-section simulation diagram. Then, it reads the layer order, outer diameter boundary, material field, and process field from the structural layer data. It also reads the resistance, impedance, capacitance, inductance, reactance, voltage drop, and current result fields from the electrical result dataset. Layer order verification compares the layer order with the layer order in the structural layer data item by item. Structural scale verification compares the graphic size and display scale with the outer diameter boundary in the structural size constraints. Material association verification compares the layer material field with the material parameters in the design constraint dataset. Process field verification compares the layer process field with the process parameters in the design constraint dataset. Electrical result verification compares the electrical result dataset with the electrical performance requirements corresponding to the standard type and customer constraints. Standardized output field verification checks whether the cable model, specification, voltage rating, standard type, material field, process field, electrical result field, and structural layer field in the scheme record have the same version index.

[0027] In S5, when any verification object is inconsistent, the consistency verification component generates a conflict record. The conflict record includes the conflict object, conflict field, source data, target data, and processing type. The conflict object identifies the layer, level record, or electrical result field where the inconsistency occurs; the conflict field identifies the name of the inconsistent field; the source data records the value of the current layer, level record, or result field; the target data records the values ​​used for comparison in the design constraint dataset, structural dimension constraints, or electrical performance requirements; and the processing type distinguishes between electrical result conflicts, structural dimension conflicts, material association conflicts, process field conflicts, mapping failure conflicts, and version index conflicts. After a conflict record is generated, the system does not directly output a structural design scheme but instead enters the corresponding correction path based on the processing type.

[0028] When the conflict record processing type is electrical result conflict, the electrical parameter calculation component reads the input field group corresponding to the conflict field and returns to the calculation parameter table to perform parameter correction and recalculation. Parameter correction includes updating parameter fields, unit fields, or precision fields. The corrected calculation parameter table re-enters S3 to form a new electrical result dataset. When the processing type is structural dimension conflict, the structural diagram generation component reads the structural dimension constraints corresponding to the conflict object and returns the structural hierarchy data to perform outer diameter boundary or hierarchy order correction. The corrected structural hierarchy data re-enters S4 to form a new cable cross-section simulation diagram. When the processing type is material association conflict or process field conflict, the layer editing component reads the layer identifier corresponding to the conflict object and modifies the material field or process field. The modified layer record is written back to the structural hierarchy data and then re-enters S5. When the processing type is mapping failure conflict, the system stops generating the corresponding layer and retains a mapping failure mark in the conflict record, preventing the candidate scheme from entering the structural design scheme determination stage. When the same conflict object still produces the same conflict field after correction, the system retains the source data and target data before and after the most recent correction and generates a mark pending manual confirmation.

[0029] When the consistency verification component does not generate a conflict record, the system writes the current design constraint dataset, electrical result dataset, structural hierarchy data, cable cross-section simulation diagram, and version number into the scheme record, and identifies the corresponding scheme as the structural design scheme. Please refer to [link to relevant documentation]. Figure 5 The specification data output component reads cable type, specifications, voltage rating, standard type, material field, process field, electrical result field, structural level field, and version number from the scheme record. It then categorizes the electrical result field into resistance, impedance, capacitance, inductance, reactance, voltage drop, and current and writes it into the electrical parameter table. Similarly, it categorizes the structural level field into conductor layer, insulation layer, filler layer, wrapping layer, inner sheath, armor layer, and outer sheath and writes it into the structural parameter table. Finally, it binds the electrical parameter table, structural parameter table, and cable cross-section simulation diagram to the same version of output data. When the scheme record is read again, the version number serves as a unified index, enabling synchronous reading of parameter results, graphical objects, and technical specification data.

[0030] In one specific operating mode, the operator enters the cable model, voltage rating, specifications, and standard type into the input interface, and selects the parameters to be included in the calculation. The system uses the cable model, specifications, and standard type as task index fields, and reads parameters such as phase voltage, line voltage, number of cores, conductor outer diameter, insulation outer diameter, cable outer diameter, operating temperature, frequency, cable length, and power factor from the parameter database. It also reads the layer order and outer diameter boundaries of the conductor layer, insulation layer, wrapping layer, inner sheath, and outer sheath from the structural dimension table. After the calculation parameter table is generated, the electrical parameter calculation component performs calculations of capacitance, inductance, reactance, AC resistance, impedance, voltage drop, and current according to field groupings, and binds each result field to the input field grouping and accuracy field. The structural diagram generation component reads the outer diameter boundaries and layer order to generate a corresponding cable cross-section simulation diagram. If the outer sheath graphic dimensions are inconsistent with the structural dimensions constraints, the consistency check component generates a structural dimensions conflict record. The structural diagram generation component reads the structural dimensions constraints based on the conflict record and returns the structural level data to perform outer diameter boundary correction, generating a new cable cross-section simulation diagram and re-entering the consistency check. When no new conflict record is generated, the system outputs the corresponding technical specification data.

[0031] In another specific operating mode, when the standard type or customer constraint changes, the system does not directly use the electrical result dataset from the original scheme record. Instead, it writes the new standard type or customer constraint into the design constraint dataset and creates a new candidate scheme record according to the version number. The new candidate scheme record reads the basic parameters corresponding to the original cable model and specifications, and simultaneously reads the structural dimension constraints and electrical performance requirements according to the new standard type. The electrical parameter calculation component regenerates the electrical result dataset, the structural diagram generation component regenerates the structural hierarchy data and cable cross-section simulation diagram, and the consistency verification component compares the new electrical result fields with the new electrical performance requirements. If the voltage drop result field is inconsistent with the electrical performance requirements corresponding to the customer constraint, the system generates an electrical result conflict record, returns to the calculation parameter table, reads the input field groupings related to the voltage drop calculation, completes the parameter correction, and recalculates. Thus, changes in the standard type or customer constraint can be passed to the parameter results and structural graphical objects through the version index, conflict records, and regeneration path.

[0032] Please see Figures 1 to 5The components of the constrained cable structure simulation optimization method can be deployed in the same computer system or executed in different processing units within the same system, but the data item names should remain consistent across processing units. The design constraint dataset, calculation parameter table, electrical result dataset, structural hierarchy data, cable cross-section simulation diagram, conflict record, scheme record, and technical specification data have a sequential read-write relationship. The design constraint dataset provides the field source for the calculation parameter table and structural dimension constraints; the calculation parameter table provides the calculation input for the electrical result dataset; the electrical result dataset and structural dimension constraints jointly participate in the formation of structural hierarchy data; the structural hierarchy data forms the cable cross-section simulation diagram; the cable cross-section simulation diagram, structural hierarchy data, and electrical result dataset jointly undergo consistency verification; conflict records determine parameter correction, layer editing, or pending manual confirmation; and scheme records provide the basis for versioned output of technical specification data. Through the above data flow, the determination of the cable structure scheme does not rely on isolated manual calculation results or separately drawn graphic objects, but is formed jointly by parameters, layers, and specification data under the same constraint chain.

[0033] The specific field names, hierarchical objects, processing order, calculation result classification, conflict handling path, and output data format described in the above embodiments are used to explain the possible implementations of the present invention and should not limit the present invention to the specific embodiments listed. Without departing from the technical solutions described in the present invention and the technical solutions described in the application documents, any equivalent substitutions, equivalent modifications, equivalent combinations, order adjustments, module correspondence replacements, equivalent transformations of field names, equivalent inheritance of the executing entity, or equivalent changes in the carrier form that can be conceived by those skilled in the art should fall within the scope of protection of this patent; however, they should not be extended to unclaimed topics, nor should the substantive correspondence of technical objects be changed through changes in fields or drawing numbers.

Claims

1. A method for simulation optimization of constrained cable structures, characterized in that, include: Obtain cable type, voltage level, specifications, standard type, customer constraints, material parameters, process parameters and calculation accuracy from the cable design task to form a design constraint dataset; Based on the design constraint dataset, the basic parameters that match the cable type, specifications and standard type are read from the parameter database and structural dimension table to form a calculation parameter table and structural dimension constraints. Based on the calculation parameter table and the preset cable electrical parameter calculation rules, an electrical result dataset containing resistance, impedance, capacitance, inductance, reactance, voltage drop, and current is generated. The design constraint dataset, the electrical result dataset, and the structural dimension constraints are mapped according to cable level type, dimension boundary, material field, and process field to form structural level data, and a cable cross-section simulation diagram is generated based on the structural level data. The consistency of the cable cross-section simulation diagram, the structural hierarchy data, and the electrical result dataset is checked. The check objects include the hierarchy order, structural proportion, size boundary, material association, electrical results, and standardized output fields. If there are inconsistencies in the check comparison results, the parameters or layers are corrected according to the conflict records and then regenerated. If there are no conflict records, the corresponding scheme is determined as the structural design scheme.

2. The constraint cable structure simulation optimization method according to claim 1, characterized in that, The design constraint dataset includes: Receive cable model, material code, process classification, specifications, structure table type, version number, standard type, parameter selection items, and number of decimal places displayed; The cable model, specifications, standard type, and version number are used as task index fields, the parameter selection items are used as the calculation field filtering criteria, and the number of decimal places displayed are used as the result retention precision field. For inputs lacking a task index field, a missing marker is generated. For inputs with multiple version numbers under the same task index field, a set of version data is read according to the effective status corresponding to the version number, and the reading result is written into the design constraint dataset.

3. The constraint cable structure simulation optimization method according to claim 2, characterized in that, The calculation parameter table includes: Based on the parameter selection options, the following parameters are extracted from the design constraint dataset: phase voltage, line voltage, number of cores, conductor outer diameter, insulation outer diameter, cable outer diameter, relative permittivity of insulation material, cable inductance, conductor shaft distance, DC resistance, conductor temperature coefficient, operating temperature, skin effect coefficient, proximity effect coefficient, frequency, ground leakage resistance, ground loop distance, current, cable length, motor power, and power factor. The extracted parameters are grouped into fields according to voltage parameters, current parameters, geometric dimension parameters, material correction parameters, operating condition correction parameters, and line environment parameters; For parameters grouped within the same field, the source field, unit field, and precision field are retained, so that the calculated parameter table can be read by subsequent electrical parameter calculations and structural hierarchy mapping.

4. The method for simulation optimization of constrained cable structures according to claim 1, characterized in that, The generation of the electrical results dataset includes: Read the geometric dimension parameters, material correction parameters, operating condition correction parameters, and line environment parameters according to the fields in the calculation parameter table; The capacitance, inductance, reactance, AC resistance at operating temperature, positive sequence impedance, negative sequence impedance, zero sequence impedance, voltage drop, and current are calculated according to the preset cable electrical parameter calculation rules. Each calculation result is bound to the corresponding input field group, calculation time, precision field, and result field name to form the electrical result dataset that can be read for structural hierarchy mapping and consistency verification.

5. The method for simulation optimization of constrained cable structures according to claim 1, characterized in that, The data forming the structural hierarchy includes: The layers to be generated in the conductor layer, insulation layer, filler layer, wrapping layer, inner sheath, wire armor layer, metal strip armor layer, and outer sheath are determined based on the structural size constraints. Write the hierarchy order, outer diameter boundary, center position, material field, process field, and electrical association field corresponding to the electrical result dataset for each level to be generated; A cross-sectional graphic object is generated according to the hierarchical order and the outer diameter boundary, and the material field, the process field and the electrical association field are bound to the cross-sectional graphic object to obtain the cable cross-section simulation diagram.

6. The method for simulation optimization of constrained cable structures according to claim 1, characterized in that, The formation of the conflict record includes: Read the layer order, graphic size, display scale, material field, and process field of each layer in the simulation diagram of the cable cross-section; The layer hierarchy order is compared with the hierarchy order in the structural hierarchy data; the graphic size and display scale of the layer are compared with the structural size constraints; the material field and process field of the layer are compared with the design constraint dataset; and the electrical result dataset is compared with the electrical performance requirements corresponding to the standard type and customer constraints. If any of the above comparison results are inconsistent, write the conflict record containing the conflict object, conflict field, source data, target data, and processing type.

7. The method for simulation optimization of constrained cable structures according to claim 6, characterized in that, The parameters or layers corrected based on the conflict record include: When the processing type of the conflict record is electrical result conflict, the corresponding input field group is read and the calculation parameter table is returned for parameter correction and recalculation; When the processing type of the conflict record is structural size conflict, the corresponding structural size constraint is read and the structural hierarchy data is returned for correction of the outer diameter boundary or hierarchy order. When the conflict record is processed as a material-related conflict or a process field conflict, the corresponding material field or process field is read and the cable cross-section simulation diagram is returned for layer editing. The revised calculation parameter table, structural hierarchy data, or cable cross-section simulation diagram are re-entered for consistency verification until no more conflict records are generated or a mark awaiting manual confirmation is generated.

8. The method for simulation optimization of constrained cable structures according to claim 1, characterized in that, After determining the structural design scheme, the following is also included: Write the design constraint dataset, electrical result dataset, structural hierarchy data, cable cross-section simulation diagram, and version number from the structural design scheme into the scheme record; According to the above scheme, technical specification data is generated, which includes cable type, specifications, voltage level, standard type, material field, process field, electrical result field and structural level field; When the scheme record is read again, the version number is used as a unified index to synchronously read the electrical result field, the structural hierarchy field, and the cable cross-section simulation diagram.

9. The method for simulation optimization of constrained cable structures according to claim 1, characterized in that, The consistency check also includes abnormal input handling: When the design constraint dataset is missing cable type, specification, voltage level, or standard type, stop generating the calculation parameter table and output the missing fields. When a parameter in the calculation parameter table is missing, the calculation of the corresponding electrical result field is stopped and a calculation failure flag is written to the electrical result dataset; When the structural dimension constraints and the electrical result dataset cannot be mapped to the same level, stop generating the corresponding layer and write a mapping failure flag in the conflict record; When the same conflicting object still produces the same conflicting field after correction, retain the source data and target data before and after the most recent correction and generate a flag for manual confirmation.

10. The method for simulation optimization of constrained cable structures according to claim 8, characterized in that, Generating the technical specification data includes: Read the cable model, specifications, voltage level, standard type, material field, process field, electrical result field, structural level field, and version number from the scheme record; The electrical result fields are classified into resistance, impedance, capacitance, inductance, reactance, voltage drop and current and written into the electrical parameter table. The structural layer fields are classified into conductor layer, insulation layer, filling layer, wrapping layer, inner sheath, armor layer and outer sheath and written into the structural parameter table. The electrical parameter table, the structural parameter table, and the cable cross-section simulation diagram are bound to the same version of output data, so that the technical specification data, graphic objects, and parameter results have the same version index.

Images