A method and system for pre-configuration of overhead contact arm based on ODA technology

Abstract

The present invention discloses a method and system for pre-configuration of an overhead contact network arm based on ODA technology, which obtains on-site measurement data of an anchor section to which a target work point belongs; according to the arm type in the on-site measurement data, a arm geometric constraint model corresponding to the arm type and the codes of each component constituting the arm are queried and obtained in a pre-established working condition database; according to the codes of each component constituting the arm obtained from the working condition database, the size information of each component corresponding to the code of each component is queried and obtained in a component database; the size information of each component and the pre-set basic design parameter information are used as driving parameters of the arm geometric constraint model, and the arm geometric constraint model is parametrically driven by a pre-configured ODA drawing component to generate an arm pre-configuration diagram. The present invention uses the ODA technology to implement the pre-configuration calculation process of the overhead contact network arm, which releases the dependence on large-scale drawing software such as AutoCAD software.

Description

Technical Field

[0001] The invention relates to the technical field of electrified railway overhead contact network arm pre-configuration, and in particular to an overhead contact network arm pre-configuration method and system based on ODA technology. Background Art

[0002] At present, the contact network arm pre-assembly calculation technology is mainly based on the existing commercial CAD graphics software technology to realize parameter calculation and drawing. Prior art CN105740539B-the arm pre-assembly method based on the parametric geometric constraint model, by reading the construction site measurement data, calling the CAD constraint model, working conditions and component parameters of the contact network arm pre-assembly, calculates the structural position, geometric dimensions and other information of the components required for the contact network arm assembly, and forms CAD file graphics and data tables. The existing contact network arm pre-assembly technology is based on the constraint relationship of CAD graphics software, and needs to rely on commercial CAD software platforms such as AutoCAD. It is affected by the software version and operating system compatibility, and the development and use are slightly complicated, and it is difficult to realize network deployment and release, which is not convenient for promotion and use. Summary of the invention

[0003] The present application provides a contact network arm pre-assembly method and system based on ODA technology to solve the problem that the existing contact network arm pre-assembly technology is based on the constraint relationship of CAD graphics software, needs to rely on commercial CAD software platforms such as AutoCAD, and is not easy to promote and use.

[0004] According to the first aspect, an embodiment provides a method for pre-configuring an overhead contact arm based on the ODA technology, the method comprising:

[0005] Acquire on-site measurement data of the anchor section to which the target work point belongs, wherein the on-site measurement data includes a pillar number and an arm type associated with the pillar number;

[0006] According to the arm type in the field measurement data, query and obtain the arm geometric constraint model corresponding to the arm type and the codes of the components constituting the arm in the pre-established working condition database;

[0007] According to the codes of the components constituting the arm obtained from the working condition database, the size information of each component corresponding to the component code is searched in the component database;

[0008] The dimension information of each component constituting the arm and the pre-set basic design parameter information are used as driving parameters of the arm geometric constraint model, and the arm geometric constraint model is parametrically driven by using the pre-configured ODA drawing component to generate an arm pre-configuration diagram, and text and dimension annotations are added to the obtained arm pre-configuration diagram;

[0009] Add a technical parameter information description table to the arm pre-configuration drawing, and obtain the final arm pre-configuration diagram result after verification.

[0010] Furthermore, the on-site measurement data specifically include pillar number, pillar mileage, arm type, curve radius, track width, outer rail superelevation, side limit, pillar inclination rate, lower base height, upper and lower arm bases, small mileage side span, large mileage side span, and pillar type.

[0011] Furthermore, the working condition database specifically includes the arm type, the arm geometric constraint model block name corresponding to the arm type, and the coding of each component that constitutes the arm.

[0012] Furthermore, the parts database specifically includes the type, dimension value, description information, and manufacturer information of the parts corresponding to the part codes.

[0013] Furthermore, the basic design parameters include contact suspension wire parameters, wire library parameters, meteorological condition parameters and auxiliary parameters.

[0014] Furthermore, the contact suspension conductor parameters are used to set and manage basic parameter information related to the contact suspension conductor, specifically including the type of load-bearing cable, load-bearing cable tension, contact wire type, contact wire tension, elastic cable tension, ordinary suspension string unit density, elastic suspension string unit density, conductor height, and structure height parameter information; the wire library parameters are used to manage basic data information of conductor wires; the meteorological condition parameters are used to manage meteorological condition parameter data information associated with the project; the auxiliary parameters are used to manage non-universal or fixed parameter data information that is not related to the project.

[0015] Furthermore, the pre-configured ODA drawing component is used to parametrically drive the arm geometry constraint model and generate the arm pre-configuration diagram, which specifically includes:

[0016] Load the ODA SDK drawing component, which includes the Kernel component and the Drawing component. The Drawing component includes the core modules DbConstraints and DwgConstraints in the Extensions component.

[0017] Create an instance based on the drawing component, initialize the ODA SDK core service, and perform ODA SDK authorization verification;

[0018] Create a local database OdDbDatabase, which serves as a carrier of the graphic file data information to be constructed;

[0019] Create a layer in the local database OdDbDatabase and set basic setting information of the layer;

[0020] Parse the pre-configured drive parameters, obtain the storage path of the arm geometric constraint model block according to the arm geometric constraint model block name obtained by the analysis, obtain the graphic data information of the arm geometric constraint model block according to the storage path and copy it to the local database OdDbDatabase, and insert the block at the specified position of the drawing space of the local database OdDbDatabase;

[0021] The driving parameters are transferred to drive the geometric constraints of the blocks, and the variables are assigned values ​​to obtain the pre-configured graphics of the arm after driving.

[0022] Furthermore, text and dimension annotations are added to the obtained arm-cantilever pre-configuration diagram, specifically including:

[0023] Load the database object OdDbDatabase;

[0024] Find the layer table storing layer information in the database OdDbDatabase;

[0025] Check whether there is an annotation layer in the layer table. If not, create a new annotation layer, set the basic setting information of the annotation layer, and add the newly created annotation layer to the layer table;

[0026] Find the annotation style table that stores annotation styles in the database OdDbDatabase;

[0027] Create a new dimension style object, set the dimension style properties, and add the created dimension style object to the dimension style table;

[0028] Determine the type of annotation you need to add and select the linear annotation type;

[0029] Set the starting point for the linear annotation object, set the end point for the linear annotation object, set the text position for the linear annotation object, and set the text content for the linear annotation object;

[0030] Apply dimension styles to linear dimension objects to complete text and dimension operations.

[0031] Furthermore, the driving parameters are transferred to drive the geometric constraints of the blocks, and the variables are assigned values ​​to obtain the pre-configured graphics of the arm after driving, which specifically includes:

[0032] Locate the database object OdDbDatabase;

[0033] Retrieve and locate the block table in the database OdDbDatabase to record, store and manage all block definitions;

[0034] Use the block table iterator to quickly traverse the fast table to find the entry record of the target block;

[0035] Get the parameterized network object associated with the entry record of the target block;

[0036] Traverse all operation objects in the parameterized network object, find the operation object involving constraints, check whether each operation object is a two-dimensional constraint group type, if so, traverse the dependent object set associated with the current operation object, find the related variable object, otherwise, skip the current operation object;

[0037] Compare the parameter name of each variable object to determine whether it is the target variable. If so, modify the parameters of the target variable object to complete the parameter drive. Otherwise, skip the current variable object.

[0038] Check whether all dependent objects have been processed. If not, continue to process unprocessed dependent objects until all dependent objects have been processed.

[0039] Apply parameter constraint changes to the operation object to complete the graphic transformation.

[0040] According to the second aspect, an embodiment provides a contact network arm pre-configuration system based on ODA technology, the system comprising:

[0041] A field measurement module, used to obtain field measurement data of the anchor section to which the target work point belongs, wherein the field measurement data includes a pillar number and an arm type associated with the pillar number;

[0042] A working condition query module is used to query and obtain the arm geometric constraint model corresponding to the arm type and the codes of the components constituting the arm in a pre-established working condition database according to the arm type in the field measurement data;

[0043] A component query module is used to query and obtain the size information of each component corresponding to each component code in the component database according to the codes of each component constituting the arm obtained from the working condition database;

[0044] A parametric driving module is used to use the size information of each component constituting the arm and the pre-set basic design parameter information as the driving parameters of the arm geometric constraint model, use the pre-configured ODA drawing component to perform parametric driving of the arm geometric constraint model, generate a arm pre-configuration diagram, and add text and dimension annotations to the obtained arm pre-configuration diagram;

[0045] The pre-configuration result generation module is used to add a technical parameter information description table to the arm pre-configuration drawing, and obtain the final arm pre-configuration chart result after verification.

[0046] The present application provides a contact network arm pre-configuration method and system based on ODA technology, which obtains field measurement data of the anchor section to which a target work point belongs, wherein the field measurement data includes a pillar number and an arm type associated with the pillar number; according to the arm type in the field measurement data, a arm geometric constraint model corresponding to the arm type and the codes of each component constituting the arm are queried and obtained in a pre-established working condition database; according to the codes of each component constituting the arm obtained from the working condition database, the size information of each component corresponding to the code of each component is queried and obtained in a component database; the size information of each component constituting the arm and the pre-set basic design parameter information are used as driving parameters of the arm geometric constraint model, and the arm geometric constraint model is parametrically driven by a pre-configured ODA drawing component to generate an arm pre-configuration diagram, and text and dimension annotations are added to the obtained arm pre-configuration diagram; a technical parameter information description table is added to the arm pre-configuration drawing, and the final arm pre-configuration diagram result is obtained after verification. The present invention intends to break away from the dependence on commercial CAD drawing software such as AutoCAD, and adopts software technology based on ODA graphics engine and supporting CAD geometric constraint algorithm to realize the pre-configuration calculation process of contact network arm, and combines Web development technology to realize the independent and flexible deployment and operation of the contact network arm pre-configuration calculation platform that is independent of any CAD software, so as to meet the scalability, diversity and interactive friendliness of the contact network arm pre-configuration calculation results. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 A flowchart of a method for pre-configuring an overhead contact network arm based on ODA technology provided by one embodiment of the present invention;

[0048] Figure 2 A specific implementation flow chart of a contact network arm pre-configuration method based on ODA technology provided by one embodiment of the present invention;

[0049] Figure 3 A field measurement data template in a contact network arm pre-configuration method based on ODA technology provided by an embodiment of the present invention;

[0050] Figure 4 A contact network structure diagram in a contact network arm pre-configuration method based on ODA technology provided by one embodiment of the present invention;

[0051] Figure 5 A flow chart of field measurement data verification in a method for pre-configuration of an overhead contact arm based on ODA technology provided by one embodiment of the present invention;

[0052] Figure 6A schematic diagram of source data before and after splitting in a method for pre-configuring an overhead contact network arm based on ODA technology provided by an embodiment of the present invention;

[0053] Figure 7 Contents of a working condition database in a method for pre-configuring an overhead contact network arm based on ODA technology provided by an embodiment of the present invention;

[0054] Figure 8 Contents of a parts database in a method for pre-assembling a contact network arm based on ODA technology provided by an embodiment of the present invention;

[0055] Fig. 9 A schematic diagram of a cantilever geometric constraint model in a method for pre-assembling a cantilever of a contact network based on ODA technology provided by one embodiment of the present invention;

[0056] Fig.10 A schematic diagram of non-reference constraints and reference constraints in a method for pre-configuration of an overhead contact network arm based on ODA technology provided by one embodiment of the present invention;

[0057] Fig.11 A graphical workflow diagram of ODASDK construction in a method for pre-configuring a contact network arm based on ODA technology provided by an embodiment of the present invention;

[0058] Fig.12 An ODASDK parametric geometric constraint driven flow chart in a contact network arm pre-configuration method based on ODA technology provided by one embodiment of the present invention;

[0059] Fig.13 A flowchart of Chinese characters and dimension information marking in a method for pre-configuration of an overhead contact arm based on ODA technology provided by an embodiment of the present invention;

[0060] Fig.14 A result of arm pre-configuration in a contact network arm pre-configuration method based on ODA technology provided by one embodiment of the present invention;

[0061] Fig.15 A schematic diagram of the logical structure of a contact network arm pre-configuration system based on ODA technology is provided for one embodiment of the present invention. DETAILED DESCRIPTION

[0062] The present invention is further described in detail below by specific embodiments in conjunction with the accompanying drawings. Wherein similar elements in different embodiments adopt associated similar element numbers. In the following embodiments, many detailed descriptions are for making the present application better understood. However, those skilled in the art can easily recognize that some features can be omitted in different situations, or can be replaced by other elements, materials, methods. In some cases, some operations related to the present application are not shown or described in the specification, this is to avoid the core part of the present application being overwhelmed by too much description, and for those skilled in the art, it is not necessary to describe these related operations in detail, and they can fully understand the related operations according to the description in the specification and the general technical knowledge in the art.

[0063] In addition, the features, operations or characteristics described in the specification can be combined in any appropriate manner to form various implementations. At the same time, the steps or actions in the method description can also be interchanged or adjusted in a manner that is obvious to those skilled in the art. Therefore, the various sequences in the specification and the drawings are only for the purpose of clearly describing a certain embodiment and are not meant to be a required sequence, unless otherwise specified that a certain sequence must be followed.

[0064] The first embodiment of the present invention provides a contact network arm pre-configuration method based on ODA technology. The arm pre-configuration method of this embodiment is described below in conjunction with the "contact network arm pre-configuration computing platform" provided in this embodiment.

[0065] First, the "contact network arm pre-configuration computing platform" provided in this embodiment is explained. The platform adopts the B / S mode, and users can run it with the help of a web browser to realize the convenient use of the Web-based application of this technical solution.

[0066] Platform architecture overview: (1) The computing platform adopts a front-end and back-end separation architecture design. The front-end uses the Vue framework and focuses on UI logic rendering; the back-end uses the C++ programming language to implement data services and parametric geometry drivers based on ODA technology, graphic file construction and generation, and other logic implementations. (2) The front-end and back-end interact with each other through API interfaces to achieve high cohesion and low coupling of applications, reduce concurrency and load pressure on back-end servers, and pursue high availability and high performance.

[0067] Advantages of the platform's technical solution: (1) By applying the B-side request for the pre-configuration calculation of the overhead contact network arm, local resources are greatly saved. (2) The user management module realizes hierarchical management and authority isolation of the pre-configuration calculation project to ensure the division of responsibilities and data security. (3) The ODA graphic results can be previewed online, which is convenient for users to adjust and correct the pre-configuration data information and update the pre-configuration design plan in a timely manner. (4) Convenient and fast pre-data import applications are realized, such as batch import of field measurement data files and data error correction adjustments, which improves data processing efficiency and accuracy. (5) The calculation platform supports the construction of formatted list reports for pre-configuration calculation results, increases the reuse and circulation of data, and facilitates data management and communication. (6) Completes all-round support for the pre-configuration calculation of the overhead contact network arm, improving user experience and work efficiency.

[0068] The front-end technical architecture of the platform: (1) It is designed using the Vue framework and is responsible for user information data interaction and data entry. (2) It provides a modular entry interface, including the entry of pre-configured information data, work site information data, and construction site data. (3) The front-end page also serves as the editing and management entry for the digital models of various types of contact network arms, including geometric constraint drive, size and text information annotation, etc., to facilitate user operation and management.

[0069] Backend technical architecture of the platform: (1) The backend is written in C++ and developed using C++ REST SDK. It encapsulates and provides data interaction API interface capabilities and drawing driver capabilities to achieve data interaction and processing with the front-end page. (2) Establish data interaction and processing with MySQL as the core database to achieve persistent storage and efficient management of data. (3) Use OpenXLSX to read, write and edit Excel files. (4) With the help of ODA technology graphics drawing function, geometric constraint driving, dimension and text information annotation of parametric digital models are achieved. (5) Graphic file format export functions such as PDF.

[0070] Platform database technical architecture: (1) MySQL is used as the data storage and management platform to store the information data and digital model index entered by the front-end page. (2) Assembly method: The front-end page calls the interface provided by the back-end interface through the RESTful API to realize the data interaction between the front-end and back-end; the back-end interface receives the front-end request, performs data processing and builds graphic files, and realizes the persistent storage and management of data; the back-end service is based on the technical support of the ODA drawing component, providing meta-capability support for the pre-configuration and construction of the wrist and arm. The platform is adjusted through data calculation based on the ODA technology. (3) Usage method: Users enter pre-configuration data information and digital models through the front-end page; the back-end interface processes user requests, stores data in the database, and provides drawing drive capabilities for drawing and annotating digital models; users can export related graphic files and report files through the front-end page to facilitate data display and sharing. (4) Functional description: Platform function design: Provides major modules such as user information management, functional permissions, project management, design parameter configuration, wire data management, field test data management, design data management, rapid pre-configuration and drawing, and results data preview.

[0071] The first embodiment of the present invention provides a method for pre-assembling an overhead contact arm based on ODA technology, and the specific steps are as follows: Figure 1 shown.

[0072] like Figure 1 As shown, in step S100, the on-site measurement data of the anchor section to which the target work point belongs is obtained, wherein the on-site measurement data includes a pillar number and an arm type associated with the pillar number.

[0073] Configure the basic data of the project in the "Project Information" panel of the platform, so that designers can quickly understand and edit the basic information of the work project. In the "Work Site Information" panel, users need to set the basic data of the work site, such as the anchor section range, and designers upload and import the on-site anchor section measurement data associated with the work site. The platform provides a cantilever measurement template, and its specific data style is as follows Figure 3 As shown, the on-site measurement data specifically include pillar number, pillar mileage, cantilever type, curve radius, track surface width, outer rail superelevation, side limit, pillar inclination rate, lower base height, upper and lower cantilever bases, small mileage side span, large mileage side span, and pillar type.

[0074] The wrist and support are generally dependent on each other, such as Figure 4As shown, the arm is generally installed and attached to the pillar. Therefore, the installation point of the arm is generally based on the pillar as the reference point, so all the associated data are classified into one category and recorded as a row of data. With "pillar number" as the unique identifier, its data meaning and use can be briefly described as follows; Pillar number: The number of the pillar here, which is also the unique identifier of the data, used to uniquely identify each pillar. Pillar mileage: The location information of the pillar, indicating the specific mileage position of the pillar on the railway line. Arm type: The model type of the arm attached to the pillar here, used to locate the model type to be pre-equipped with the arm. Curve radius: The curve radius of the line where the pillar is located here, indicating the degree of curvature of the railway at this position. Track width: The width of the railway track, usually refers to the distance between the center lines of the track. Outer rail superelevation: The height difference between the outer rail and the inner rail in the curved section of the railway, used to reduce the centrifugal force when the train passes the curve. Side limit: The minimum safe distance between the railway building or facility and the center line of the track to ensure the safety of train operation. Pillar inclination: The degree of inclination of the pillar relative to the vertical direction, to ensure the stability of the pillar when bearing load. Lower base height: The height of the lower base of the pillar, used to support and fix the pillar. Upper and lower cantilever base: The fixed base on the pillar used to install the upper and lower cantilever. Short mileage side span: The horizontal distance between the pillar and the previous pillar in the short mileage direction. Long mileage side span: The horizontal distance between the previous pillar and the current pillar in the long mileage direction. Pillar type: The specific type of pillar, usually classified according to its design and purpose. Usually divided into "HK" and "SD", different types will have different calculations. Insulator type: The type of insulating device installed on the pillar, used to isolate current and ensure safety.

[0075] The field measurement data table uses the "pillar number" as a unique identifier, so each row of data in the table is referred to as "pillar data". The pillar number refers to the number of the pillar here, which is also the unique identifier of the data, used to uniquely identify each pillar. The arm type refers to the model type of the arm attached to the pillar here, which is used to locate the model type of the arm to be pre-configured. Combined with the "field measurement data" imported by the user, each row of pillar data is verified and calculated to determine whether the data content is correct and conforms to the basic design logic. The data verification logic is as follows: Figure 5 As shown, the details are as follows:

[0076] Determine whether the "arm type" of each row of data is a conversion column. If so, adjust its "pillar number" and "arm type" to split the source data into two. If "electrical phase separation" is encountered, split the original data into three. For example, if the "pillar number" of the original data is "1307 small", the "pillar numbers" of the two rows of data after splitting are displayed as "1307 small-1" and "1307 small-2" respectively. The "arm type" of the original data is "5ZFA", and the "pillar numbers" of the two rows of data after splitting are displayed as "5ZFA1" and "5ZFA2" respectively. The rest of the data is consistent with the source data. Data splitting examples are as follows Figure 6 As shown, the source data is Figure 6 As shown in (a) in the figure, the data is split into Figure 6 As shown in (b) in .

[0077] For the pre-configuration design of the arm, the pillars can generally be divided into two categories. One is that one arm is attached to a pillar, which we call the "middle pillar". Correspondingly, one line of data can be used to represent its basic information of "pillar number" and "arm type". The other is that two arms are attached to one pillar (special scenarios, such as electrical phase separation, are three arms attached to one pillar). In this case, since both arms are based on the pillar as the reference point data, the source measurement data still represents all its information in one line of data. However, data processing is required when performing data calculations. It is necessary to locate the arm data and perform pre-configuration calculations for each arm. Therefore, it is necessary to split and assign values ​​to the original data, and then add suffix identifiers to the "pillar number" and "arm pre-configuration" field information values ​​to distinguish them. Import the adjusted measurement data into the database system for storage, set the joint primary key of "work site ID", "pillar number" and "arm type" to ensure data uniqueness. If storage abnormalities are found, remind the user to adjust the data in time.

[0078] like Figure 1 As shown, in step S200, according to the arm type in the field measurement data, the arm geometric constraint model corresponding to the arm type and the codes of the components constituting the arm are queried in the pre-established working condition database.

[0079] like Figure 1 As shown, in step S300, according to the codes of the components constituting the arm obtained from the working condition database, the size information of each component corresponding to the component code is queried in the component database.

[0080] The "Configuration Parameters" panel of the platform consists of two core components: one is the working condition table data on the right side of the page that records the overall assembly composition of the arm, and the other is the parts table data on the left side of the page that records different specifications and models. There is a mapping relationship between the two data. The page divides the data through column design for comparison and viewing, which is convenient for users to flexibly query and adjust the data.

[0081] The first is to record the working table data of the overall assembly composition of the arm, such as Figure 7 As shown in the figure, users can set the overall parameter configuration of the components of the arm to be assembled on the page, including "arm type" (WorkCondition), "geometric constraint model block name" (ConstraintNum) and the component model code used for each component (D201-D253, in the actual application of arm calculation, these "component model codes" will be used as search keywords to query the component table to obtain the size length value of the numbered part). The configuration parameters of this table will directly affect the calculation results and final design drawings of the arm assembly. Users can flexibly set the working condition data parameters according to actual engineering needs and construction environment to ensure the accuracy and reliability of the calculation.

[0082] The second is to record the parts table data of different specifications and models, such as Figure 8 As shown in the figure, users can edit and set the detailed data of various types and specifications of parts required for the arm assembly, including the type, size value, description information, manufacturer and other specific information of the parts. By setting the specific parameter data of these parts and associating with the "working condition table" data, the part size required for the overall structure assembly of the arm is determined, and this data is used as the basis to provide core data for subsequent pre-configuration calculation drive graphic transformation.

[0083] According to the imported field measurement data, the "arm type" of each row is used as the search keyword to search and locate the data in the "operating condition table", and the "constraint block" information corresponding to the "arm type" and the associated component code are obtained. The platform is designed with two output modes: "single-line output" and "batch output". "Single-line output" means that the platform will use the row selected by the user as the data source each time to drive the output. "Batch output" will use all the data in the imported table as the data source for automatic driven output, and the user will review and preview after all the graphics are built.

[0084] In this embodiment, the “constraint block” is a pre-configured CAD constraint model of the contact network arm, which is generally presented in a DWG format file. The specific content is as follows: Fig. 9As shown, it can be seen that each line of the figure in the figure is subject to constraint control and has clear control parameter data. The essential logic of parametric drive can be briefly described as follows: change the original "CAD constraint model" constraint control parameters; because the constraint control parameters of the line are changed, the corresponding constraint line will also be changed. Constraint control generally defaults to changing the "length" attribute of the line, and the "angle" of the line can also be changed as needed; the change of the "CAD constraint model" drive is the final result of the joint action of multiple constraint control parameters. There are multiple constraint parameters that are interrelated and mutually restricted. Therefore, the "CAD constraint model" file is the original material file for the "computing platform" to pre-configure the wrist and arm. Its file storage information is divided into two parts. One part is the "CAD constraint model" file entity, which is stored in the file storage system of the server, and the other part records a row of data in the "material library" table of the database, recording the "constraint model name" and "storage path". The corresponding logic is to query with "arm type" as the search keyword to obtain the name of the "CAD constraint model" model; then query the "material library" with the name of the "CAD constraint model" model as the search keyword to obtain its "storage path". The two key data information of the "CAD constraint model" model name and "storage path" will be used in the subsequent application practice of parametric drive functions.

[0085] The component code is the code name of each component in the arm structure. There is a dedicated table in the database (such as Figure 8 (b) in the table is responsible for recording the size, category, weight, marking information, type description, manufacturer code and other information of each component. Since components with the same name can correspond to multiple specifications, it is necessary to use the "component code" as the primary key (unique identifier) ​​of the database table to distinguish them. The "working condition table" mentioned in this embodiment mainly records the "arm type", "constraint block" and parameters of each component of the arm structure (each component corresponds to a different component, so its value corresponds to the component code). The specific content of the table includes: "arm type" corresponds to the table field "WorkCondition"; "constraint block name" corresponds to the table field "ConstraintNum"; "components of the arm structure", using codes as table segments for easy storage and display.

[0086] By querying the working condition table with "arm type" as the query keyword, the "constraint block name" and the "component code" of each component of the arm structure can be obtained. By querying the "parts list" with "component code" as the query keyword, the size information of the parts of this part can be obtained, that is, the length dimension that the graphics of this part should be drawn can be obtained, which can be used as the target value for the subsequent constraint control.

[0087] like Figure 1 As shown, in step S400, the dimension information of the components constituting the arm and the pre-set basic design parameter information are used as driving parameters of the arm geometric constraint model, and the pre-configured ODA drawing component is used to parametrically drive the arm geometric constraint model to generate a arm pre-configuration diagram, and text and dimension annotations are added to the obtained arm pre-configuration diagram.

[0088] In this embodiment, the basic design parameters include contact suspension conductor parameters, wire library parameters, meteorological condition parameters and auxiliary parameters. The contact suspension conductor parameters are used to set and manage basic parameter information related to the contact suspension conductor, including the type of catenary, the tension of the catenary, the type of contact wire, the tension of the contact wire, the tension of the elastic cable, the unit density of the ordinary suspension string, the unit density of the elastic suspension string, the height of the conductor, and the parameter information of the structure height; the wire library parameters are used to manage the basic data information of the conductor wire, including the conductor model, cross-section, diameter, unit mass and other information; the meteorological condition parameters are used to manage the meteorological condition parameter data information associated with the project, including the highest temperature, the lowest temperature, the temperature when the maximum wind is blowing, the temperature when ice is covered, the temperature when the arm and the positioner are normal, the temperature when the contact is free of relaxation, the maximum wind speed, the wind speed when ice is covered, the structural wind speed, etc.; the auxiliary parameters are used to manage non-universal or fixed parameter data information that is not related to the project.

[0089] In this embodiment, in combination with the set basic design parameters, it is necessary to adjust the design parameters such as "guide height" and "structure height". At the same time, the "locator" angle value is calculated. Specifically, first of all, for the arm pre-configuration, the main sources of its driving parameters are two categories. One is the driving parameter content obtained by combining the query data results of the "working condition table" and "parts table", and the other is the "basic design parameter" data set by the designer, specifically "guide height" and "structure height" and "locator angle".

[0090] "Conductor height": conductor installation height. "Structure height": usually refers to the installation height or hanging height of the overhead contact arm. This refers to the vertical distance between the overhead contact bracket or supporting structure and the overhead contact wire (or contact wire). These two parameters determine the installation position of the arm and the drive parameters of the corresponding position of the arm pre-matching. For example, in the specific example, "Structure height" 1600 corresponds to the drive parameter "D402", and "Conductor height" 5300 corresponds to the drive parameter "D401". The locator angle refers to the angle between the overhead contact arm and the horizontal line. This angle is set to ensure the correct distance and position between the overhead contact wire (or contact wire) and the railway track in order to provide good contact and ensure the reliability and safety of power transmission. The locator angle calculation requires the use of the "contact wire tension", "load wire tension", "diameter", "unit mass", "ice thickness", "ice density", "conductor height", "structure height", "first suspension string distance" data values ​​in the design parameters. Applied to the pre-matching example, the locator angle corresponds to the drive parameter "D228".

[0091] Combining the data results of the above steps, the target block and all parameter values ​​that need to be driven (CAD constraints that need to be driven) are obtained. Here, the "target block" is the CAD constraint model pre-configured for the contact network arm, which specifically refers to the corresponding "constraint block name" obtained by querying the "operating condition table" with the processed "arm type" name.

[0092] Finally, the driver function in the ODA SDK drawing component is used to parametrically drive the target block, and the target graphics are obtained by driving the data values ​​summarized in the previous step. In this example, the ODA SDK development kit is used to load the two core components of Kernel and Drawings in the kit to realize functions such as graphics drawing, layer and text style management, and dimension and text information annotation, and the core modules "DbConstraints" and "DwgConstraints" in the Extensions component are used to realize functions such as geometric constraint driving of parametric digital models. The main contents include: "Graphics construction and editing" based on ODASDK components, "parametric driving of geometric constraint blocks", "text and dimension information annotation", "obtaining output parameters (reference constraints)", etc.

[0093] 1. The construction logic of the arm pre-configuration drawing, such as Fig.11 As shown, the specific steps include:

[0094] (1) Load the ODA SDK drawing component, which includes the Kernel component and the Drawing component. The Drawing component includes the core modules DbConstraints and DwgConstraints in the Extensions component.

[0095] Specifically, load the ODA dynamic link library file, load the core modules DbConstraints and DwgConstraints. To use ODA components for graphics construction, you need to first configure the ODA-related development environment. The specific operation is to load and configure the ODA SDA-provided header file (.h), dynamic link library (dll), static link library (lib) and other resource files in the development compiler. Mainly load the following components:

[0096] Kernel: Kernel is the basic component of ODA SDK, providing low-level mathematical operations, geometric processing and other basic functions. These functions are the basis for building advanced CAD applications. It includes the following main functions: Mathematical library: supports various geometric calculations, such as matrix operations, vector calculations, etc. Geometry processing: processes basic geometric shapes and operations, such as points, lines, and surfaces. Memory management: provides an efficient memory management mechanism to ensure the performance of CAD applications.

[0097] Drawing: Drawing component is a higher-level module in ODA SDK, which is specially used to process CAD drawing files. It provides the functions of reading, modifying and saving drawing files. Drawing component supports various CAD file formats, such as DWG and DGN. It includes the following main functions: File reading and writing: supports reading and writing various CAD file formats. Graphics operation: provides operations of creating, modifying and deleting graphic objects. Layer management: supports the creation and management of layers, and controls the display and hiding of layers.

[0098] In the Drawing component, there are several important extension classes, including DbConstraints and DwgConstraints under Extensions, and PdfModuleVI.

[0099] DbConstraints and DwgConstraints: These two classes are mainly used to handle constraints in CAD files. DbConstraints: This class is used to handle constraints at the database level. It can manage geometric constraints and dimensional constraints in drawings to ensure that objects in drawings maintain predetermined relationships and sizes. For example, you can set a parallel constraint between two line segments, or set a radius constraint for a circle. DwgConstraints: This class is specifically used for constraint management in the DWG file format. It inherits from DbConstraints and provides additional functions and optimizations for the DWG file format. DwgConstraints allows you to set and manage various constraints on geometric objects in DWG files to ensure that the files remain consistent in different software. PdfModuleVI: PdfModuleVI is an important module in the Drawing component, used to process PDF files. It provides the function of exporting CAD drawings to PDF files and supports various operations on PDF files, including: PDF export: Convert CAD drawings to high-quality PDF files, support multi-page export and various PDF settings. PDF operation: supports operations on PDF files, such as adding watermarks, merging PDF files, etc. PDF display: provides basic PDF file display functions, allowing PDF files to be viewed in CAD applications.

[0100] (2) Create an instance based on the drawing component, initialize the ODA SDK core service, and perform ODA SDK authorization verification.

[0101] Specifically, after configuring the development environment, you can start coding development. To use ODA components, you need to first create an ODA service object (Services). This service object will be used as the main service entry for calling ODA components to detect and load the basic ODA services that users need to use. The ODA component will also set default values ​​for its internal data (initialization operation). This step is required for all ODA component development.

[0102] Because the ODA component will first search whether the executing user has purchased the authorized service before providing service capabilities, only after authorization verification can ODA provide the corresponding service capabilities. Therefore, ODA authorization verification operation is required before executing ODA core services. The specific operation is: after purchasing ODA authorization, the official website will provide the corresponding "OdActivationInfo" file, which is placed under the project's "\ThirdParty\activation". The ODA component will automatically search and verify during retrieval verification.

[0103] (3) Create a local database OdDbDatabase, which serves as a carrier of the graphic file data information to be constructed.

[0104] Specifically, a graphic file (such as a DWG file) is actually a data storage format used to record various drawing data such as the geometric point information, style attributes, layer information, etc. A DWG file can be regarded as a complex data container that contains all the information required to build and display graphics.

[0105] When using ODA SDK to build graphics, you need to create an OdDbDatabase object as a database container each time. This database container has the following main responsibilities: Data storage: record all drawing data, including point information, lines, graphic objects, etc. Style management: manage the style properties of graphics, such as line type, color, fill, etc. Layer management: support the creation and management of layers, and control the display and hiding status of layers. Text and annotation: record text objects and annotation information, used to display text content and size information on drawings.

[0106] (4) Create a layer in the local database OdDbDatabase and set basic setting information of the layer.

[0107] The database container can manage layers. Therefore, after creating a database container, users can create, modify and manage layers, and assign graphic objects to different layers to better organize and control the display of drawings. At the same time, you can set the basic settings of this layer, such as setting the graphic color, visibility, whether to lock, etc. The specific operation is: construct a layer table object OdDbLayerTable for the local data object OdDbDatabase, and add an OdDbLayerTablerRecord object to it.

[0108] (5) Parse the pre-configured drive parameters, obtain the storage path of the arm geometric constraint model block according to the arm geometric constraint model block name obtained by the analysis, obtain the graphic data information of the arm geometric constraint model block according to the storage path and copy it to the local database OdDbDatabase, and insert the block at the specified position of the drawing space of the local database OdDbDatabase. The specific operations are as follows:

[0109] a. The parsing function inputs the "pre-configured parameters" information, extracts the name of the key data information "target constraint block", and maps it with a MAP container to accept the parameter variable key name and key value that needs to be driven. The pre-configured parameters are the driving parameter values ​​of the different parts of the wrist-arm structure described previously, that is, the parameter values ​​shown in "D205", "D206", etc. shown in the chart. The computing platform will process and package all "pre-configured parameters" in a fixed format and pass them to the "ODA graphics construction" process node. Therefore, the main thing is to parse the data of the "pre-configured parameters" passed in with the corresponding format logic, interpret them one by one, and store them in a data storage container for the convenience of the subsequent process steps.

[0110] b. Use the name of "target constraint block" as a keyword to query the database and locate the path of the "target block". This step is the same as the previous step in parsing parameters. The computing platform will pass two types of key data to the "ODA Graph Construction" process node. One type is the "pre-configured parameters" mentioned in the previous step, and the other type is the name of the "target constraint block" that needs to be driven. Use the name of the "target constraint block" to query the "material table" to obtain the path of the "target block". The "pre-configured parameters", "target constraint block" name and the corresponding file path will be used as subsequent key parameters.

[0111] c. Use the Services instance object and take the path of the "target constraint block" as the input parameter, call the readFile function, and obtain the data container OdDbDatabase (referred to as CloneDatabase) where the "target block" is located. Take the name of the "target constraint block" and the corresponding file path in the previous step as parameters, call the ODA component's read document service (readFile function), obtain the data storage container OdDbDatabase that reads the "target constraint block" file, and you can get all the graphic data information related to the "target constraint block" file.

[0112] d. Load the OdDbDatabase object where the "target constraint block" is located and obtain the block table object OdDbBlockTable.

[0113] Each Database object contains multiple table objects. According to different uses, there are OdDbLayerTable involved in layer management, OdDbBlockTable involved in graphic blocks, and OdDbSymbelTable involved in design symbol library. This step is mainly to retrieve and locate the graphic object data in the data storage container of the "target constraint block" file. The data storage container OdDbDatabase is responsible for recording graphic drawing data, including point information, lines, graphic objects, etc., which are generally recorded in the block table object (OdDbBlockTable).

[0114] In ODA SDK, OdDbBlockTable and OdDbBlockTableRecord are key components for managing blocks in drawing files. Blocks are an important structure in drawings that can contain a group of graphic objects and are inserted and managed as a single object. OdDbBlockTable is a special table in the OdDbDatabase object that is used to store and manage all block definitions. It is equivalent to a container that contains all blocks in the drawing file (including model space, layout space, and user-defined blocks).

[0115] e. Use the block table iterator OdDbSymbolTableIterator to traverse and search all OdDbBlockTableRecord objects in the target block, and trace the OdDbBlockTableRecord object corresponding to the "target constraint block".

[0116] Since there are multiple entries in a block table, each entry corresponds to a specific block, so it is necessary to search the table for the entry corresponding to the "target constraint block" (OdDbBlockTableRecord). OdDbBlockTableRecord is an entry in OdDbBlockTable, which is used to define a specific block. Each OdDbBlockTableRecord contains the specific graphic data and attributes of the block. Its main responsibilities include: Defining block content: storing all graphic objects in the block (such as lines, circles, text, etc.). Managing block properties: maintaining the block's name, insertion point, hierarchy and other properties. Supporting block operations: providing interfaces to add, modify and delete graphic objects in blocks.

[0117] f. Use the wblockClone block copy function to copy the OdDbBlockTableRecord object corresponding to the "target constraint block" to the created local data object OdDbDatabase.

[0118] This step is equivalent to adding a new OdDbBlockTableRecord object data in the block table object OdDbBlockTable of the local data object OdDbDatabase. This data is the "target constraint block" we need. That is, the target constraint block entry retrieved and read in the previous step that already exists in the file is cloned and copied to the data container OdDbDatabase of the newly created file.

[0119] g. Insert the OdDbBlockTableRecord object corresponding to the newly added "target constraint block" in the local data object OdDbDatabase into the specified position of the drawing space ModelSpace.

[0120] That is, the "target constraint block" is recorded in the OdDbBlockTableRecord object in the form of OdDbBlockReferencePtr, and the placement point of the block is set, that is, the insertion point coordinates are set. This step is mainly to set the ownership and attribute information of the target constraint block entry added by the clone copy, that is, to set the location and storage form of the block corresponding to the target constraint block entry inserted into the data container of the newly created file.

[0121] h. After completing the copy of the "target constraint block" to the local database, release the data object OdDbDatabase where the source file is located to avoid resource occupation and memory overhead. The data container of the "target constraint block" is read to obtain the target constraint block entry and clone it. After completing the operation, the access to the data container of the "target constraint block" should be ended. Similarly, the memory resources storing the data should be cleaned up to improve efficiency and avoid subsequent file access occupation and other special situations.

[0122] (6) Transfer the driving parameters to drive the geometric constraints of the block, assign values ​​to the variables, and obtain the pre-configured graphics of the arm after driving. The specific operations are as follows:

[0123] a. Use the parsed driven parameter variables to perform parametric geometric constraint drive on the loaded "target constraint block". The specific practice of the "geometric constraint drive of parametric digital model" process will be described in detail in the subsequent stages. By applying parameter driven transformation, the size presented by the "target constraint block" can be consistent with the pre-set component size length, and the target graphics after pre-set data drive are obtained.

[0124] b. After applying the parameterized driver transformation, the data in the OdDbDatabase where it is located will be transformed. Therefore, it is necessary to re-parse the data in the data object OdDbDatabase and parse the parameterized variables OdDbAssocVariable associated with the parameterized graphics in the OdDbBlockTableRecord object step by step.

[0125] In the data container OdDbDatabas, the data information of the "reference constraint" is in the associated variable OdDbAssocVariable under the constraint block entry OdDbBlockTableRecord. Therefore, it is necessary to locate the associated variable OdDbAssocVariable to extract the reference constraint data from it. Each associated variable OdDbAssocVariable corresponds to a constraint data.

[0126] Since there are multiple constraint relationships in the target constraint block, and there are dependencies between them, but there are rules and orders to follow. Constraints are mainly divided into two categories: "non-reference constraints" that are actively driven to change according to the parameters input by the user, and "reference constraints" that are passively changed due to active driving. The specific logic is as follows:

[0127] Fig.10 In (a), D1, D2, and D3 are non-reference constraints, and D1 is a reference constraint. Fig.10 The length constraint relationship shown in (a) is D1 + O1 + D2 = D3. Therefore, when the user actively modifies the parameter value of D1, the parameter values ​​of D2 and D3 remain unchanged. Then O1 will be calculated according to the length constraint formula D1+O1+D2=D3 to obtain O1 = D3 - D2- D1. Thus, a passive transformation occurs. Fig.10 As shown in (b) in the figure, the specific example is as follows: when the user inputs D1 = 00, D2 = 200, D3 = 1100, O1 will passively change to O1 = 300.

[0128] Therefore, the operation logic of step a is mainly to set the graphic transformation of "non-reference constraints", and the "reference constraints" affected by it will also change, and the constraint data will also change accordingly. Steps b and c are mainly to obtain the data of the "reference constraints" that change accordingly.

[0129] c. Get the value of each OdDbAssocVariable object marked as "O***" as the output parameter value. The specific practice of the "get output parameter (reference constraint)" process will be described in detail in the subsequent stages.

[0130] The specific process of geometric constraint-driven parametric digital model is as follows: Fig.12 As shown, the details are as follows:

[0131] (1) Locate the database object OdDbDatabase.

[0132] (2) Retrieve and locate the block table in the database OdDbDatabase that records, stores and manages all block definitions.

[0133] Specifically, search for the block table object OdDbBlockTable. Each Database object contains multiple table objects. According to different uses, there are LayerTable for layer management, BlockTable for blocks, and SymbelTable for design symbol libraries. Retrieve and locate the block table OdDbBlockTable in the database container that records, stores, and manages all block definitions. The block table itself is also equivalent to a container, which contains all blocks in the drawing file, including model space, layout space, and user-defined blocks.

[0134] (3) Use the block table iterator to quickly traverse the fast table to find the entry record that locates the target block.

[0135] Specifically, use the block table iterator OdDbSymbolTableIterator to traverse and search all OdDbBlockTableRecord objects in the target block to track down the target OdDbBlockTableRecord object. Since the block table contains multiple block records, if you want to quickly access each record data in the block table one by one, you need to create a block table iterator to facilitate fast traversal and search for the entry record OdDbBlockTableRecord of the target block.

[0136] (4) Find the target block record OdDbBlockTableRecord and obtain the parameterized network object OdDbAssocNetwork associated with it.

[0137] (5) Traverse all operation objects OdDbAssocAction in the parameterized network object OdDbAssocNetwor to find the constraint operations involved. Check whether each operation object OdDbAssocAction is a two-dimensional constraint group type OdDbAssoc2dConstraintGroup. If so, proceed to the next operation; otherwise, skip the operation object and continue to check the next one.

[0138] (6) Get the collection of associated dependency objects OdDbAssocDependency and traverse these dependency objects to find the related variable objects OdDbAssocVariable.

[0139] (7) Compare the parameter name of each variable object OdDbAssocVariable to determine whether it is the target variable. If it is the target variable, proceed to the next step; otherwise, skip the variable object and continue to check the next one.

[0140] (8) Use the setExpression function to modify the parameters of the target variable object OdDbAssocVariable to complete the parameter drive.

[0141] (9) Check whether all associated dependent objects OdDbAssocDependency have been processed. If there are still unprocessed dependent objects, return to step 7 and continue until all dependent objects are processed.

[0142] (10) Use the evaluate function to apply constraint drive to the operation object OdDbAssocAction. The previous operations only changed the values ​​of its constraint parameters and did not actually drive the parameter constraint changes. However, this step applies all previously assigned constraint parameters at once to perform graphic transformation.

[0143] The process of "Get output parameters (reference constraints)" can be briefly described as follows:

[0144] (1) Locate the database object OdDbDatabase.

[0145] (2) Retrieve and locate the block table in the database OdDbDatabase that records, stores and manages all block definitions.

[0146] Specifically, search for the block table object OdDbBlockTable. Each Database object contains multiple table objects. According to different uses, there are LayerTable for layer management, BlockTable for blocks, and SymbelTable for design symbol libraries. Retrieve and locate the block table OdDbBlockTable in the database container that records, stores, and manages all block definitions. The block table itself is also equivalent to a container, which contains all blocks in the drawing file, including model space, layout space, and user-defined blocks.

[0147] (3) Use the block table iterator to quickly traverse the fast table to find the entry record that locates the target block.

[0148] Specifically, use the block table iterator OdDbSymbolTableIterator to traverse and search all OdDbBlockTableRecord objects in the target block to track down the target OdDbBlockTableRecord object. Since the block table contains multiple block records, if you want to quickly access each record data in the block table one by one, you need to create a block table iterator to facilitate fast traversal and search for the entry record OdDbBlockTableRecord of the target block.

[0149] (4) Find the target block record OdDbBlockTableRecord and obtain the parameterized network object OdDbAssocNetwork associated with it.

[0150] (5) Traverse all operation objects OdDbAssocAction in the parameterized network object OdDbAssocNetwork to find the constraint operations involved. Check whether each operation object OdDbAssocAction is a two-dimensional constraint group type OdDbAssoc2dConstraintGroup. If so, proceed to the next operation; otherwise, skip the operation object and continue to check the next one.

[0151] (6) Get the collection of associated dependency objects OdDbAssocDependency and traverse these dependency objects to find the related variable objects OdDbAssocVariable.

[0152] (7) Compare the parameter name of each variable object OdDbAssocVariable to determine whether it is the target variable. If it is the target variable, proceed to the next step; otherwise, skip the variable object and continue to check the next one.

[0153] (8) Use the getExpression function on the target variable object OdDbAssocVariable to obtain the current parameter value, that is, to obtain the reference constraint value corresponding to the output parameter.

[0154] (9) Check whether all associated dependent objects OdDbAssocDependency have been processed. If there are still unprocessed dependent objects, return to step 7 and continue until all dependent objects are processed.

[0155] 2. Text and dimension information marking process

[0156] After obtaining the arm pre-configuration drawing, it is necessary to mark the size and data information of the parts on the block, draw the graphic frame and table, and print and display some key information. Linearly mark the generated parametric graphics and mark the size distance of some parts so that users can cut and assemble the raw materials according to the marked distance. Fig.13 As shown in the figure, the specific steps of text and dimensioning include:

[0157] (1) Load the database object OdDbDatabase.

[0158] (2) Find the layer table OdDbLayerTable that stores layer information in the database OdDbDatabase.

[0159] (3) Check whether there is an annotation layer in the layer table. If not, create a new annotation layer, set the basic setting information of the annotation layer, and add the newly created annotation layer to the layer table.

[0160] When the "annotation layer" does not exist, the annotation layer object OdDdLayerTableRecord should be created immediately. Set basic properties such as name, color and line width for the newly created annotation layer.

[0161] (4) Find the dimension style table OdDbDimStyleTable that stores dimension styles in the database OdDbDatabase.

[0162] (5) Create a new dimension style object, set the dimension style properties, and add the created dimension style object to the dimension style table. Specifically, set basic properties such as line width, endpoint marker width, arrow style, etc. for the dimension style, and add the newly created and set dimension style to the dimension style table.

[0163] (6) Determine the type of dimension you want to add and select the linear dimension type. Determine the type of dimension you want to add (such as linear dimension, angular dimension, or radius dimension). Usually, the linear dimension OdDbAlignedDimension is used.

[0164] (7) Set the starting point (XLine1Point) for the linear dimension object. Set the end point (XLine2Point) for the linear dimension object. Set the text position for the linear dimension object. Set the text content for the linear dimension object.

[0165] (8) Set the annotation style used for the linear annotation object. Complete the addition of text and dimension annotation. After completing the drawing, dimension annotation and information printing, save and output in DWG and PDF file formats to obtain the target arm pre-configuration drawing corresponding to the "pillar number" and "arm type".

[0166] like Figure 1 As shown, in step S500, a technical parameter information description table is added to the arm pre-configuration drawing, and after verification, the final arm pre-configuration chart result is obtained.

[0167] The technical parameter information description table includes input parameters and output parameters. The input parameters are derived from field measurement data, and the output parameters are variable objects whose values ​​will change due to changes in the values ​​of the associated drive parameters (i.e., the aforementioned "reference constraints"). The output graph will be displayed and previewed on the platform page. The designer confirms whether the arm pre-configuration diagram is correct. If it is correct, the arm pre-configuration calculation diagram is completed. Otherwise, the user will be required to adjust the working condition pre-configuration parameters. The final pre-configuration diagram result is as follows: Fig.14shown.

[0168] Corresponding to the above-disclosed contact network arm pre-configuration method based on ODA technology, the embodiment of the present invention also discloses a contact network arm pre-configuration system based on ODA technology, such as Fig.15 As shown, it specifically includes:

[0169] A field measurement module, used to obtain field measurement data of the anchor section to which the target work point belongs, wherein the field measurement data includes a pillar number and an arm type associated with the pillar number;

[0170] A working condition query module is used to query and obtain the arm geometric constraint model corresponding to the arm type and the codes of the components constituting the arm in a pre-established working condition database according to the arm type in the field measurement data;

[0171] A component query module is used to query and obtain the size information of each component corresponding to each component code in the component database according to the codes of each component constituting the arm obtained from the working condition database;

[0172] A parametric driving module is used to use the size information of each component constituting the arm and the pre-set basic design parameter information as the driving parameters of the arm geometric constraint model, use the pre-configured ODA drawing component to perform parametric driving of the arm geometric constraint model, generate a arm pre-configuration diagram, and add text and dimension annotations to the obtained arm pre-configuration diagram;

[0173] The pre-configuration result generation module is used to add a technical parameter information description table to the arm pre-configuration drawing, and obtain the final arm pre-configuration chart result after verification.

[0174] It should be noted that for the detailed description of a contact network arm pre-configuration system based on ODA technology provided in an embodiment of the present invention, reference can be made to the relevant description of a contact network arm pre-configuration method based on ODA technology provided in an embodiment of the present application, which will not be repeated here.

[0175] The above specific examples are used to illustrate the present invention, which is only used to help understand the present invention and is not intended to limit the present invention. For those skilled in the art, according to the concept of the present invention, some simple deductions, modifications or substitutions can be made.

Claims

1. A method for pre-assembling an overhead contact arm based on ODA technology, characterized in that: The method comprises: Acquire on-site measurement data of the anchor section to which the target work point belongs, wherein the on-site measurement data includes a pillar number and an arm type associated with the pillar number; According to the arm type in the field measurement data, query and obtain the arm geometric constraint model corresponding to the arm type and the codes of the components constituting the arm in the pre-established working condition database; According to the codes of the components constituting the arm obtained from the working condition database, the size information of each component corresponding to the component code is searched in the component database; The dimension information of each component constituting the arm and the pre-set basic design parameter information are used as the driving parameters of the arm geometric constraint model, and the pre-configured ODA drawing component is used to perform parameter-driven operation on the arm geometric constraint model to generate an arm pre-configuration diagram, and text and dimension annotations are added to the obtained arm pre-configuration diagram, including: loading the ODA SDK drawing component; creating an instance and initializing the ODA SDK core service, and performing authorization verification; creating a local database OdDbDatabase as a carrier of graphic file data information; creating a layer in the OdDbDatabase and setting basic setting information; parsing the pre-configured driving parameters, obtaining the graphic data information of the arm geometric constraint model block and copying it to the local database OdDbDatabase, and inserting the block at the specified position of the drawing space of the local database OdDbDatabase; using the driving parameters to drive the block geometric constraints to obtain the arm pre-configuration diagram; Add a technical parameter information description table to the arm pre-configuration drawing, and obtain the final arm pre-configuration chart result after verification; The on-site measurement data specifically include pillar number, pillar mileage, cantilever type, curve radius, track surface width, outer rail superelevation, side limit, pillar inclination rate, lower base height, upper and lower cantilever bases, small mileage side span, large mileage side span, and pillar type.

2. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 1, characterized in that: The working condition database specifically includes the arm type, the arm geometric constraint model block name corresponding to the arm type, and the coding of each component constituting the arm.

3. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 1, characterized in that: The parts database specifically includes the type, dimension value, description information, and manufacturer information of the parts corresponding to the part codes.

4. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 1, characterized in that: The basic design parameters include contact suspension wire parameters, wire library parameters, meteorological condition parameters and auxiliary parameters.

5. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 4, characterized in that: The contact suspension wire parameters are used to set and manage basic parameter information related to the contact suspension wire, specifically including the type of catenary wire, the tension of the catenary wire, the type of contact wire, the tension of the contact wire, the tension of the elastic wire, the unit density of the ordinary suspension wire, the unit density of the elastic suspension wire, the height of the wire, and the parameter information of the structure height; The wire library parameters are used to manage basic data information of conductor wires; the meteorological condition parameters are used to manage meteorological condition parameter data information associated with the project; and the auxiliary parameters are used to manage non-universal or fixed parameter data information that is not related to the project.

6. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 1, characterized in that: The drawing component includes a Kernel component and a Drawing component, and the Drawing component includes the core modules DbConstraints and DwgConstraints in the Extensions component.

7. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 6, characterized in that: Add text and dimension annotations to the obtained arm pre-configuration drawing, including: Load the database object OdDbDatabase; Find the layer table storing layer information in the database OdDbDatabase; Check whether there is an annotation layer in the layer table. If not, create a new annotation layer, set the basic setting information of the annotation layer, and add the newly created annotation layer to the layer table; Find the annotation style table that stores annotation styles in the database OdDbDatabase; Create a new dimension style object, set the dimension style properties, and add the created dimension style object to the dimension style table; Determine the type of annotation you need to add and select the linear annotation type; Set the starting point for the linear annotation object, set the end point for the linear annotation object, set the text position for the linear annotation object, and set the text content for the linear annotation object; Apply dimension styles to linear dimension objects to complete text and dimension operations.

8. A method for pre-assembling an overhead contact arm based on ODA technology as claimed in claim 6, characterized in that: The driving parameters are transferred to drive the geometric constraints of the blocks, and the variables are assigned values ​​to obtain the pre-configured graphics of the arm after driving, including: Locate the database object OdDbDatabase; Retrieve and locate the block table in the database OdDbDatabase to record, store and manage all block definitions; Use the block table iterator to quickly traverse the fast table to find the entry record of the target block; Get the parameterized network object associated with the entry record of the target block; Traverse all operation objects in the parameterized network object, find the operation object involving constraints, check whether each operation object is a two-dimensional constraint group type, if so, traverse the dependent object set associated with the current operation object, find the related variable object, otherwise, skip the current operation object; Compare the parameter name of each variable object to determine whether it is the target variable. If so, modify the parameters of the target variable object to complete the parameter drive. Otherwise, skip the current variable object. Check whether all dependent objects have been processed. If not, continue to process unprocessed dependent objects until all dependent objects have been processed. Apply parameter constraint changes to the operation object to complete the graphic transformation.

9. A contact network arm pre-assembly system based on ODA technology, characterized in that: The system comprises: The field measurement module is used to obtain the field measurement data of the anchor section to which the target work point belongs. The field measurement data includes the pillar number and the arm type associated with the pillar number, specifically including the pillar number, pillar mileage, arm type, curve radius, rail surface width, outer rail superelevation, side limit, pillar inclination rate, lower base height, upper and lower arm bases, small mileage side span, large mileage side span, and pillar type; A working condition query module is used to query and obtain the arm geometric constraint model corresponding to the arm type and the codes of the components constituting the arm in a pre-established working condition database according to the arm type in the field measurement data; A component query module is used to query and obtain the size information of each component corresponding to each component code in the component database according to the codes of each component constituting the arm obtained from the working condition database; The parametric driving module is used to use the size information of each component constituting the wrist and the pre-set basic design parameter information as the driving parameters of the wrist geometric constraint model, use the pre-configured ODA drawing component to perform parametric driving of the wrist geometric constraint model, generate a wrist pre-configuration diagram, and add text and dimension annotations to the obtained wrist pre-configuration diagram, including: loading the ODA SDK drawing component; creating an instance and initializing the ODA SDK core service, and performing authorization verification; creating a local database OdDbDatabase as a carrier of graphic file data information; creating a layer in the OdDbDatabase and setting basic setting information; parsing the pre-configured driving parameters, obtaining the graphic data information of the wrist geometric constraint model block and copying it to the local database OdDbDatabase, and inserting the block at the specified position of the drawing space of the local database OdDbDatabase; using the driving parameters to drive the block geometric constraints to obtain the wrist pre-configuration graphics; The pre-configuration result generation module is used to add a technical parameter information description table to the arm pre-configuration drawing, and obtain the final arm pre-configuration chart result after verification.

Images