CAD-based plug-in calling method, integrated system and computer equipment

Abstract

The invention provides a plug-in calling method based on CAD, an integrated system and computer equipment, and the method comprises the steps: configuring plug-ins corresponding to CAD software and / or tools, each plug-in comprising a plug-in executable file and a plug-in command; constructing a plug-in folder to store each plug-in; when the plug-in service is started, traversing all available plug-ins in the plug-in folder, and obtaining executable file paths and plug-in commands of all the available plug-ins; after the plug-in service is started, a plug-in calling request is received, and the plug-in calling request comprises a plug-in command name and an input parameter of a current plug-in to be called; matching an access path of a plug-in executable file corresponding to the current to-be-called plug-in according to the plug-in command name; and executing the plug-in executable file according to the access path and the input parameter, obtaining a plug-in output result and returning the plug-in output result. According to the scheme, when the integration function of the CAD system and the PDM system is expanded, core codes do not need to be modified, and therefore the flexibility and customization of the system are improved.

Description

Technical Field

[0001] The present invention relates to the field of CAD technology, and in particular to a plug-in calling method, integrated system and computer equipment based on CAD. Background Art

[0002] CAD (Computer-Aided Design) is a technology that uses computers and their graphic devices to help designers perform design work. CAD technology is widely used in various design fields, such as machinery, architecture, electronics, aerospace, automobiles, shipbuilding, clothing, graphic design and other industries. PDM system, that is, Product Data Management system, is a software solution specifically used to manage product-related information and processes. PDM system is mainly used in discrete manufacturing, but it is also applicable to other industries, such as aerospace, automobiles, electronic equipment, medical devices, etc. Any field involving complex product design and manufacturing can benefit from PDM system.

[0003] The integration of CAD system and PDM system can complement each other's functions and roles, significantly enhancing the efficiency and control of the entire product development process from design to production. The traditional way of integrating CAD system and PDM system usually adopts a closed architecture. However, this method requires modifying the source code and recompiling the entire application when adapting to new tools, new versions or expanding functions, which undoubtedly increases the cost of software development, reduces the maintainability of the software, and limits the customizability of the software. Therefore, there is an urgent need for a method that can expand the integration function of the CAD system and the PDM system without modifying the core code, thereby improving the flexibility and customization of the system. Summary of the invention

[0004] The purpose of the present invention is to provide a CAD-based plug-in calling method, integrated system and computer equipment, so as to achieve the expansion of the integrated function of the CAD system and the PDM system without modifying the core code, thereby improving the flexibility and customization of the system.

[0005] The technical solution provided by the present invention is as follows:

[0006] The present invention provides a CAD-based plug-in calling method, comprising the steps of:

[0007] Configuring plug-ins corresponding to CAD software and / or tools, each of the plug-ins corresponds to at least one of the CAD software and / or tools, and each of the plug-ins includes a corresponding plug-in executable file and a plug-in command;

[0008] Construct a plug-in folder to store each of the plug-ins;

[0009] When the plug-in service is started, all available plug-ins in the plug-in folder are traversed to obtain the executable file paths and plug-in commands of all available plug-ins;

[0010] After the plug-in service is started, a plug-in calling request is received, wherein the plug-in calling request includes a plug-in command name and input parameters of the plug-in to be called;

[0011] Matching the access path of the plug-in executable file corresponding to the plug-in to be called currently according to the plug-in command name;

[0012] The plug-in executable file corresponding to the plug-in to be called is executed according to the access path and the input parameter corresponding to the plug-in to be called, the plug-in output result is obtained, and the plug-in output result is returned.

[0013] This application implements CAD functions by configuring plug-ins corresponding to various CAD software and / or tools and calling plug-ins. Since plug-ins can be developed, tested and deployed independently, they can be easily added, modified or removed as needed without affecting the functions of the core system or other plug-ins, thereby improving the flexibility and customization of the system, meeting the specific needs of different users, and can be independently developed without affecting the main program, which helps to shorten the development cycle and reduce development costs.

[0014] In some embodiments, it further comprises:

[0015] The plug-in call request is received through the http interface, and the plug-in output result is returned according to the http service.

[0016] In some embodiments, it further comprises:

[0017] A temporary directory file is constructed, wherein the temporary directory file is used to write the input parameters corresponding to the current plug-in to be called after receiving the plug-in call request, and to write the plug-in output result after executing the plug-in executable file corresponding to the current plug-in to be called.

[0018] In some embodiments, it further comprises:

[0019] Acquire a corresponding command line template according to the plug-in command name, wherein the command line template includes an access path, an input file path, and an output file path of the plug-in executable file corresponding to the plug-in to be called;

[0020] Generate a command line according to the command line template;

[0021] Execute the command line to determine the plug-in executable file corresponding to the plug-in to be called from the plug-in folder, read the input parameters corresponding to the plug-in to be called from the temporary directory file, and write the output result of the plug-in into the temporary directory file according to the output file path.

[0022] In some implementations, the method further includes: after the plug-in output result is returned according to the http interface, or after the number of files stored in the temporary directory file reaches a preset value, clearing the temporary directory file.

[0023] In some implementations, the command line template also includes a log file path corresponding to the current plug-in to be called;

[0024] When executing the command line, the method further includes: recording a plug-in execution log during the execution of the plug-in executable file corresponding to the plug-in to be called, and writing the plug-in execution log into the temporary directory file according to the log file path;

[0025] When the plug-in output result is returned according to the http interface, it also includes: returning the plug-in execution log.

[0026] In some implementations, the plug-in includes a business plug-in and an interface plug-in;

[0027] The plug-in calling method also includes:

[0028] Build a plug-in runtime environment for plug-in discovery and loading, and provide a standard plug-in access interface.

[0029] In a second aspect, the present application provides an integrated system of CAD and PDM, on which a computer program or instruction is stored, and when the computer program or instruction is executed by a processor, the steps of the CAD-based plug-in calling method described in the first aspect are implemented.

[0030] In a third aspect, the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the CAD-based plug-in calling method described in the first aspect.

[0031] In a fourth aspect, the present application provides a computer storage medium having a computer program or instruction stored thereon, wherein when the computer program or instruction is executed by a processor, the steps of the CAD-based plug-in calling method described in the first aspect are implemented.

[0032] According to a CAD-based plug-in calling method, integrated system and computer equipment provided by the present invention, plug-ins corresponding to various CAD software and / or tools are configured, and CAD functions are implemented by calling the plug-ins. Since the plug-ins can be developed, tested and deployed separately, they can be easily added, modified or removed according to needs without affecting the functions of the core system or other plug-ins, thereby improving the flexibility and customization of the system, meeting the specific needs of different users, and can be independently developed without affecting the main program, which helps to shorten the development cycle and reduce development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The preferred implementation scheme will be described below in a clear and understandable manner with reference to the accompanying drawings to further illustrate the above-mentioned characteristics, technical features, advantages and implementation methods of the present solution.

[0034] Figure 1 It is a schematic diagram of the overall process of an embodiment of the present invention;

[0035] Figure 2 This is an overall schematic diagram of plug-in calling according to an embodiment of the present invention;

[0036] Figure 3 is a schematic diagram of plug-in calling according to an embodiment of the present invention;

[0037] Figure 4 This is a schematic diagram of plug-in service startup according to an embodiment of the present invention;

[0038] Figure 5 It is a schematic diagram of a plug-in main program according to an embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings and other implementation methods can be obtained based on these drawings without creative work.

[0040] In order to simplify the drawings, only the parts related to the present invention are schematically shown in each figure, and they do not represent the actual structure of the product. In addition, in order to simplify the drawings and facilitate understanding, in some figures, only one of the parts with the same structure or function is schematically drawn or marked. In this article, "one" not only means "only one", but also means "more than one".

[0041] CAD (Computer-Aided Design) is a technology that uses computers and their graphics equipment to help designers perform design work. CAD technology is widely used in various design fields, such as machinery, architecture, electronics, aerospace, automobiles, shipbuilding, clothing, graphic design and other industries. PDM system, namely Product Data Management system, is a software solution specifically used to manage product-related information and processes. The main features and functions of CAD include: Graphic generation: CAD software can generate two-dimensional (2D) and three-dimensional (3D) graphics, including wireframe models, surface models and solid models; Precision drawing: CAD software can draw lines, arcs, curves and other geometric elements with high precision, and supports dimensioning and tolerance annotation; Modification and editing: Users can easily modify existing designs, such as moving, rotating, scaling objects, and adding or deleting features; Parametric design: CAD software allows users to design based on parameters and constraints, which means that the design can be automatically adjusted as parameters change; Data management: CAD systems can store and manage large amounts of design data, including graphic files, attribute information and version control ; Visualization and rendering: Advanced CAD software provides realistic rendering and animation functions, allowing designers to preview the appearance and performance of products; Simulation and analysis: Some CAD software integrates tools such as finite element analysis (FEA) and computational fluid dynamics (CFD) for simulation of physical properties such as structure, thermal, and fluid; Output and communication: CAD software supports the export of multiple file formats, such as PDF, DXF, DWG, etc., which is convenient for sharing designs with other designers or manufacturers; Integration and interoperability: Modern CAD systems are usually able to integrate with PDM (product data management), PLM (product life cycle management) and CAM (computer-aided manufacturing) systems to form a complete digital design and manufacturing process. The application scope of CAD software includes: Mechanical design: used to design and analyze complex mechanical parts and assemblies; Architectural design: Architects use CAD to draw architectural plans, elevations, and cross-sections; Circuit design: Electronic engineers use CAD software to design circuit board layouts; Civil engineering: used for the design of infrastructure such as roads, bridges, and tunnels; Industrial design: Designers use CAD to create product prototypes and models. CAD technology has greatly improved design efficiency and quality, reduced design cycles, and reduced the cost of design and manufacturing. With the development of technology, CAD software is becoming more and more intelligent. Combined with technologies such as artificial intelligence and big data, it provides designers with more innovative tools and possibilities.

[0042] PDM systems are mainly used in discrete manufacturing, but are also applicable to other industries, such as aerospace, automotive, electronic equipment, medical devices, etc. Any field involving complex product design and manufacturing can benefit from PDM systems. The main functions of PDM systems include: Data management: store and manage all product-related information, such as CAD (Computer-Aided Design) models, engineering drawings, technical documents, bills of materials (BOMs), product specifications and standards, etc.; Version control: ensure the version consistency of product data, track every change history, so that team members can access the latest and correct data version; Workflow management: automate the approval process in the product development process, such as design review, change request and release process; Change management: control the change process of product data to ensure that all affected team members are aware of the changes and that the changes are appropriately Applied to all relevant documents and data; Collaborative work: Promote cross-departmental and cross-regional team collaboration, ensure that all relevant personnel can access the required information in real time, and improve team efficiency and communication; Security and permission management: Provide access control to ensure that sensitive data is only visible to authorized users and protect intellectual property rights; Search and retrieval: Provide powerful search functions to facilitate the search for specific data or documents; Lifecycle management: Support the entire lifecycle management of products from conceptual design to retirement, including design, development, manufacturing, sales and service stages; Integration capabilities: Integrate with other enterprise systems (such as ERP, CRM, SCM) to ensure data consistency and process continuity. The benefits of adopting a PDM system include: Improve efficiency: Increase product development speed by automating workflows and reducing redundant tasks; Reduce errors: Version control and change management help reduce errors caused by inconsistent data; Enhance collaboration: Improve information sharing between teams and promote better decision-making; Cost savings: Save costs by avoiding duplication of work and reducing scrap rates; Compliance: Help meet industry standards and regulatory requirements and maintain product data compliance.

[0043] The integration of CAD system and PDM system can make their respective functions and roles complement each other, significantly enhancing the efficiency and control of the entire product development process from design to production. The integration of CAD system and PDM system can achieve the following effects: 1) Data consistency and integrity: CAD system is responsible for creating and modifying product design data, while PDM system is responsible for managing the version and life cycle of these data; the integration of CAD system and PDM system ensures the accuracy and latest status of design data in PDM system, avoiding errors and delays caused by inconsistent data. 2) Collaborative work and project management: When designers design in CAD system, they can directly obtain and update the latest design files and component information from PDM system; the workflow management function in PDM system can help track the design progress and ensure that all team members follow the same process and standards. 3) Version control and history tracking: PDM system can manage different versions of CAD design files and record the history of each change, which is crucial for tracing back problems and understanding the design evolution process. 4) Resource reuse and standardization: The component library and standard parts library in PDM system can allow designers to quickly find and reuse verified components in CAD environment, avoid duplication of work, and promote design standardization. 5) Permission management and security: The PDM system provides access control to ensure that only authorized users can access and modify specific design data, protecting intellectual property and trade secrets. 6) Connection with ERP (Enterprise Resource Planning) and MES (Manufacturing Execution System): As the center of product information, PDM can ensure the consistency and timeliness of information such as production plans, bills of materials (BOM) and manufacturing instructions through integration with ERP and MES systems. 7) Accelerate time to market: Through integration, design changes can be communicated to all relevant parties, including suppliers and manufacturers, more quickly, thereby speeding up product development and manufacturing. 8) Data analysis and decision support: Integration enables the PDM system to collect and analyze design data, providing corporate decision makers with insights into design trends, cost optimization and quality improvement. In summary, the integration of CAD and PDM is an indispensable part of the modern product development process. It promotes seamless communication between design, engineering, procurement, production and supply chain management, and improves overall business efficiency and competitiveness.

[0044] The core challenges faced when integrating CAD tools with PDM systems include: 1) Diversity and version differences of CAD tools: The CAD market is full of tools of various brands and versions. Each tool has its own unique data structure and API (application programming interface). Even for the same software, there may be interface changes between different versions, which increases the complexity and workload of integration; each time the CAD software is updated or upgraded, the integration interface needs to be re-verified and adjusted to ensure compatibility with the PDM system and complete functionality. 2) Differences in development languages ​​and technology stacks: The APIs provided by CAD vendors may support different programming languages, such as C++, .NET, Java, Python, etc., which requires integrated developers to have a wide range of programming skills; differences in technology stacks may also be reflected in operating systems, databases, network protocols, etc., increasing challenges in technical compatibility and uniformity. 3) Customized requirements for business scenarios: Different companies have different business processes and work habits, and standardized integration solutions often cannot fully meet specific needs; deep customization is required, such as supporting specific bill of materials (BOM) processing logic, workflow, permission management, data mapping rules, etc., which requires an in-depth understanding of the company's specific business processes and customized development capabilities.

[0045] The traditional way of integrating CAD systems with PDM systems usually adopts a closed architecture. However, this method requires modifying the source code and recompiling the entire application when adapting to new tools, new versions, or expanding functions, which undoubtedly increases the cost of software development, reduces the maintainability of the software, and limits the customizability of the software. Therefore, there is an urgent need for a method that can expand the integration functions of the CAD system and the PDM system without modifying the core code, thereby improving the flexibility and customization of the system.

[0046] This application uses a plug-in integration approach to integrate the CAD system and the PDM system. The main advantages of using a plug-in integration approach are: 1) Modularity and flexibility: The plug-in architecture allows the system to be decomposed into independent modules, and each module (plug-in) can be developed, tested and deployed separately; this modular design improves the flexibility of the system because plug-ins can be easily added, modified or removed as needed without affecting the functions of the core system or other plug-ins; diversified plug-ins can meet the specific needs of different users and provide personalized solutions; the plug-in architecture can provide more refined control, allowing users to decide which functions they want to use, which can improve satisfaction and efficiency. 2) Easy to expand: Plug-ins can be added to the system at any time to introduce new functions or enhance existing functions without making major changes to the core system; this scalability means that the system can gradually develop over time to adapt to changing needs. 3) Reduce development costs and time: Since plug-ins can be developed independently without affecting the main program, they can be carried out in parallel, which helps to shorten the development cycle and reduce development costs; using existing plug-ins can also avoid reinventing the wheel and reduce the need to build functions from scratch. 4) Easy to maintain and upgrade: The failure or need to update a single plug-in usually does not affect the entire system, and it can be repaired or replaced independently, simplifying the maintenance process; plug-in updates and upgrades can be performed in the background without affecting users, improving the stability and availability of the system. 5) Promote reuse: Plug-ins can be reused by multiple projects or users, reducing the need to develop duplicate functions and improving resource utilization efficiency; developers can focus on building unique functions rather than infrastructure or general functions. 6) Reduce risk: By dividing the system into small, manageable plug-ins, potential problems or security vulnerabilities can be better isolated and managed, reducing overall risk. In the integration of CAD systems and PDM systems, this modular design approach not only achieves a high degree of functional cohesion and loose coupling, but also greatly improves the maintainability and scalability of the system; at the same time, each module can be developed and tested independently, further improving the efficiency and quality of software development. When integrating CAD systems and PDM systems through plug-in integration, the plug-in calling method is particularly important. The following will describe the plug-in calling method in detail with the attached figure:

[0047] In one embodiment, the reference specification Figure 1 The present invention provides a plug-in calling method based on CAD, comprising the steps of:

[0048] S100, configuring plug-ins corresponding to CAD software and / or tools, each plug-in corresponding to at least one CAD software and / or tool, and each plug-in including a corresponding plug-in executable file and a plug-in command;

[0049] S200, construct a plug-in folder to store each plug-in;

[0050] S300, when the plug-in service is started, traverse all available plug-ins in the plug-in folder to obtain executable file paths and plug-in commands of all available plug-ins;

[0051] S400: After the plug-in service is started, a plug-in call request is received, where the plug-in call request includes a plug-in command name and input parameters of the plug-in to be called;

[0052] S500, matching the access path of the plug-in executable file corresponding to the plug-in to be called currently according to the plug-in command name;

[0053] S600: Execute the plug-in executable file corresponding to the current plug-in to be called according to the access path and the input parameters corresponding to the current plug-in to be called, obtain the plug-in output result, and return the plug-in output result.

[0054] This application implements CAD functions by configuring plug-ins corresponding to various CAD software and / or tools and calling plug-ins. Since plug-ins can be developed, tested and deployed separately, they can be easily added, modified or removed according to needs without affecting the functions of the core system or other plug-ins, thereby improving the flexibility and customization of the system, meeting the specific needs of different users, and can be independently developed without affecting the main program, which helps to shorten the development cycle and reduce development costs. When implementing plug-in calls, each plug-in is stored in a plug-in folder. When the system receives a plug-in call request, it can determine the access path of the plug-in executable file corresponding to the current plug-in to be called based on the plug-in command name and input parameter information contained in the plug-in call request. Through this access path, the required plug-in can be determined from the plug-in folder, and then the plug-in task can be executed and the required plug-in output result can be output based on the input parameters and the plug-in executable file, thereby realizing the execution of CAD software and / or tool tasks in the form of plug-ins.

[0055] This application does not limit CAD software and / or tools. Each CAD software and tool can be configured with corresponding plug-ins. The specific form of the plug-in is not limited. It only needs to be able to perform tasks corresponding to the CAD software and / or tool.

[0056] In one embodiment, the reference specification Figure 2When the caller calls the corresponding CAD software and / or tool through the integrated system, the plug-in service corresponds to multiple plug-ins, and each plug-in corresponds to at least one CAD software and / or tool. The system selects the corresponding plug-in to start according to the call request to obtain the required output result, and finally returns the output result to the integrated system. The system can adopt a variety of transmission methods when receiving the call request and returning the output result. For example, in a specific implementation method, an http access interface is set, and the system receives the plug-in call request through the http interface and returns the plug-in output result according to the http interface. In other implementation methods, other access methods can also be selected, such as socket, wireless communication, Bluetooth, etc., which are not limited in this application.

[0057] In one embodiment, the reference specification Figure 3 When calling a plug-in, the caller can initiate a plug-in call request to the plug-in service center by inputting, selecting, etc., and provide the plug-in command name and plug-in command input parameters of the plug-in to be called. The plug-in service center receives the plug-in call request and returns the plug-in output results through the http interface.

[0058] The plug-in calling method of this application also includes:

[0059] Construct a temporary directory file. The temporary directory file is used to write the input parameters corresponding to the current plug-in to be called into the temporary directory file after receiving the plug-in call request, and write the plug-in output results into the temporary directory file after executing the plug-in executable file corresponding to the current plug-in to be called, so that the plug-in service center can realize the return of the plug-in output results through the http service.

[0060] The plug-in calling method of this application also includes:

[0061] Obtain the corresponding command line template according to the plug-in command name, the command line template includes the access path, input file path and output file path of the plug-in executable file corresponding to the current plug-in to be called; generate a command line according to the command line template; execute the command line to determine the plug-in executable file corresponding to the current plug-in to be called from the plug-in folder, and read the input parameters corresponding to the current plug-in to be called from the temporary directory file, and write the plug-in output result into the temporary directory file according to the output file path.

[0062] In a specific implementation, the command line template may also include a log file path corresponding to the current plug-in to be called; when executing the command line, it also includes: recording the plug-in execution log during the execution of the plug-in executable file corresponding to the current plug-in to be called, and writing the plug-in execution log to a temporary directory file according to the log file path; when returning the plug-in output result according to the http interface, it also includes: returning the plug-in execution log. That is, when returning the plug-in output result, this solution can also synchronously return the plug-in execution log during the plug-in execution process, so as to monitor and manage the plug-in execution process.

[0063] The present application does not limit the storage form of files, such as the storage of the plug-in executable file of the plug-in in the plug-in folder, the storage of input parameters in the temporary directory file, the storage of the plug-in output results in the temporary directory file, and the storage of the plug-in execution log in the temporary directory file, which can be adjusted according to the specific scenario. For example, in a specific implementation, the files of the present application are stored in .json format.

[0064] In a specific implementation, the plug-in calling method of the present application also includes: clearing the temporary directory file after returning the plug-in output result according to the http interface; or, clearing the temporary directory file when the number of files stored in the temporary directory file reaches a preset value, so as to avoid the temporary directory file occupying a large amount of memory after multiple calls to the plug-in, and facilitate the management of the input file path, output file path and log file path.

[0065] In one embodiment, the reference specification Figure 4 When the plug-in service is started, it also includes: traversing all available plug-ins in the plug-in folder, obtaining the executable file paths and plug-in commands of all available plug-ins and displaying them, so that the caller can determine the name, path, etc. of the plug-in to be called, and then initiate a plug-in call request to the plug-in service center through input, selection, etc.

[0066] In one embodiment, the reference specification Figure 5 , the plug-ins include business plug-ins and interface plug-ins; the plug-in calling method also includes: building a plug-in running environment for plug-in discovery and loading, and providing a standard plug-in access interface.

[0067] The plug-in runtime environment includes the business plug-in runtime environment and the interface plug-in runtime environment. The business plug-in runtime environment is used to discover, load, and provide plug-in access interfaces for business plug-ins. Specifically, it includes: defining plug-in interface standards, including data exchange formats, function call protocols, and event handling mechanisms; developing plug-ins according to the defined interface standards, and there is no restriction on the technology stack for developing plug-ins, and only needs to be developed according to the interface specifications; the interface implemented by the plug-in is described in the plug-in description file; the developed plug-in is deployed in the specified directory; when the main program starts, the business plug-in runtime environment scans the plug-ins in the specified directory and loads them; the main program or third-party caller can initiate a call to the plug-in through the interface. The interface plug-in runtime environment is used to discover, load, and provide plug-in access interfaces for interface plug-ins. Specifically, it includes: there is no restriction on the technology stack for interface plug-in development, but the completed interface plug-in must be an html page; after the interface plug-in is developed, it is deployed to the specified directory, with one subdirectory for each plug-in, and the subdirectory must contain index.html as the interface entry; when the main program starts, the interface plug-in runtime environment scans the plug-ins in the specified directory and loads them. ; The main program or third-party caller can initiate a call to the plug-in through the interface. The interface can start the interface according to the directory name of the plug-in, and can control the size and position of the interface window through the interface parameters, and perform operations such as placing it to the front, minimizing, maximizing, and closing it. When implementing the plug-in calling method, it can also include an integrated plug-in manager, which is used to display, register, and unregister installed plug-ins.

[0068] In one embodiment, the present application provides an integrated system of CAD and PDM, on which a computer program or instruction is stored, and when the computer program or instruction is executed by a processor, the steps of the CAD-based plug-in calling method of the aforementioned embodiment are implemented.

[0069] In one embodiment, the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the CAD-based plug-in calling method of the aforementioned embodiment.

[0070] In one embodiment, the present application provides a computer storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implements the steps of the CAD-based plug-in calling method of the aforementioned embodiment.

[0071] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0072] The memory may be an internal storage unit of the simulation system, such as a hard disk or memory of an intelligent device. The memory may also be an external storage device of the intelligent device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the intelligent device. Further, the memory is used to store the computer program and other programs and data required by the verification method of the FPGA. The memory may also be used to temporarily store data that has been output or is to be output.

[0073] The communication bus is a circuit that connects the elements described and implements transmission between these elements. For example, the central processing unit receives commands from other elements through the communication bus, decrypts the received commands, and performs calculations or data processing according to the decrypted commands. The memory may include program modules, such as a kernel, middleware, an application programming interface (API) and an application. The program module may be composed of software, firmware or hardware, or at least two of them. The input / output interface forwards commands or data entered by the user through the input / output interface (such as a sensor, keyboard, touch screen). The communication interface connects the speed measurement device of the artificial heart with other network devices, user devices, and networks. For example, the communication interface can be connected to the network via wired or wireless connection to connect to other external network devices or user devices. Wireless communication may include at least one of the following: wireless fidelity (WiFi), Bluetooth (BT), near field communication technology (NFC), global satellite positioning system (GPS) and cellular communication, etc. Wired communication may include at least one of the following: universal serial bus (USB), high-definition multimedia interface (HDMI), asynchronous transmission standard interface (RS-232), etc. The network may be a telecommunication network and a communication network. The communication network may be a computer network, the Internet, the Internet of Things, or a telephone network. The verification device of the FPGA may be connected to the network via a communication interface, and the protocol used by the speed measuring device of the artificial heart and other network devices to communicate may be supported by at least one of an application, an application programming interface (API), a middleware, a kernel, and a communication interface.

[0074] The CAD-based plug-in calling method of the present application can be implemented with program codes executable by a computing device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0075] It should be noted that the above embodiments can be freely combined as needed. The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention.

Claims

1. A plug-in calling method based on CAD, characterized in that: Includes steps: Configuring plug-ins corresponding to CAD software and / or tools, each of the plug-ins corresponds to at least one of the CAD software and / or tools, and each of the plug-ins includes a corresponding plug-in executable file and a plug-in command; Construct a plug-in folder to store each of the plug-ins; When the plug-in service is started, all available plug-ins in the plug-in folder are traversed to obtain the executable file paths and plug-in commands of all available plug-ins; After the plug-in service is started, a plug-in call request is received, wherein the plug-in call request includes a plug-in command name and input parameters of the plug-in to be called; Matching the access path of the plug-in executable file corresponding to the plug-in to be called currently according to the plug-in command name; The plug-in executable file corresponding to the plug-in to be called is executed according to the access path and the input parameter corresponding to the plug-in to be called, a plug-in output result is obtained, and the plug-in output result is returned.

2. The plug-in calling method according to claim 1, characterized in that: Also includes: The plug-in call request is received through the http interface, and the plug-in output result is returned according to the http interface.

3. The plug-in calling method according to claim 2, characterized in that: Also includes: A temporary directory file is constructed, wherein the temporary directory file is used to write the input parameters corresponding to the current plug-in to be called after receiving the plug-in call request, and to write the plug-in output result after executing the plug-in executable file corresponding to the current plug-in to be called.

4. The plug-in calling method according to claim 3, characterized in that: Also includes: Acquire a corresponding command line template according to the plug-in command name, wherein the command line template includes an access path, an input file path, and an output file path of the plug-in executable file corresponding to the plug-in to be called; Generate a command line according to the command line template; Execute the command line to determine the plug-in executable file corresponding to the plug-in to be called from the plug-in folder, read the input parameters corresponding to the plug-in to be called from the temporary directory file, and write the output result of the plug-in into the temporary directory file according to the output file path.

5. The plug-in calling method according to claim 4, characterized in that: Also includes: After the plug-in output result is returned according to the http interface, or the number of files stored in the temporary directory file reaches a preset value, the temporary directory file is cleared.

6. The plug-in calling method according to claim 4, characterized in that: The command line template also includes a log file path corresponding to the current plug-in to be called; When executing the command line, the method further includes: recording a plug-in execution log during the execution of the plug-in executable file corresponding to the plug-in to be called, and writing the plug-in execution log into the temporary directory file according to the log file path; When the plug-in output result is returned according to the http interface, it also includes: returning the plug-in execution log.

7. The plug-in calling method according to claim 1, characterized in that: The plug-ins include business plug-ins and interface plug-ins; The plug-in calling method also includes: Build a plug-in runtime environment for plug-in discovery and loading, and provide a standard plug-in access interface.

8. A CAD and PDM integrated system having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the CAD-based plug-in calling method described in any one of claims 1 to 7 are implemented.

9. A computer device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the steps of the CAD-based plug-in calling method according to any one of claims 1 to 7.

10. A computer storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the CAD-based plug-in calling method described in any one of claims 1 to 7 are implemented.

Images