A method and system for aircraft electrical system design based on physical architecture

Abstract

This application belongs to the field of aircraft electrical system design technology, specifically relating to a physical architecture-based aircraft electrical system design method and system. The physical architecture-based aircraft electrical system design method includes: Step 1, creating a prototype device based on the physical architecture device; Step 2, defining virtual device pins on the prototype device; Step 3, matching connector types and pins for the virtual device pins; Step 4, defining the prototype signals from the device to the prototype device based on the interface connection relationship of the physical architecture device, and assigning specific pins for the prototype signals from the prototype device to the prototype device; Step 5, adding electrical attributes to the prototype signals and grouping the prototype signals.

Description

Technical Field

[0001] This application belongs to the field of aircraft electrical system design technology, specifically relating to a physical architecture-based aircraft electrical system design method and system. Background Technology

[0002] With the development of aviation technology, aircraft electrical systems are gradually moving towards multi-functionality, high power, and integration, resulting in increasing complexity and making multi-supplier and interdisciplinary collaboration the norm. The rapid updates in aviation equipment place increasingly stringent demands on the development efficiency and reliability of these complex electrical systems.

[0003] Current aircraft electrical system design is document-centric, making collaboration difficult, hindering rapid version management and change control, heavily reliant on manual labor, and resulting in a high error rate. Therefore, this application is submitted. Summary of the Invention

[0004] The purpose of this application is to provide a physical architecture-based aircraft electrical system design method and system, which will change the design of aircraft electrical systems from a document-centric approach to a data-centric approach, and realize collaborative design and rapid change of aircraft electrical system design.

[0005] The technical solution of this application is:

[0006] A physical architecture-based aircraft electrical system design method, comprising:

[0007] Step 1: Create a prototype device based on the physical architecture device;

[0008] Step 2: Define the virtual device pins on the prototype device;

[0009] Step 3: Match the connector type and pins of the virtual device;

[0010] Step 4: Based on the physical architecture device interface connection relationship, define the principle signals between the device and the device, and assign specific pins for the principle signals from the device to the device.

[0011] Step 5: Add electrical attributes to the schematic signals and group the schematic signals;

[0012] Electrical attributes include chapter number, steady-state current, maximum current, minimum operating voltage, whether it is 360-degree shielded, function code, redundancy, circuit function code, electromagnetic compatibility category, first two digits of serial number, wire type, color, wire gauge, special wire code, and laying code;

[0013] Chapter numbers are used to define the system in which the principle signal resides.

[0014] A physical architecture-based aircraft electrical system design method, used to implement the above-mentioned physical architecture-based aircraft electrical system design method, including a user end;

[0015] The user end includes connector predefined user end, electrical system design user end, and electrical attribute editing user end;

[0016] The predefined connector user end is used to create a schematic device based on the physical architecture device. It defines virtual device pins on the schematic device according to the number of signals, defines the number and model of connector ports, and matches the virtual device pins with connector models and pins to generate a mapping relationship and give the virtual device pins engineering meaning.

[0017] The electrical system design user end is used to define the principle signals between the device and the physical architecture based on the device interface connection relationship, and to assign specific pins of the principle signals from the device to the device.

[0018] The electrical attribute editing client is used to add electrical attributes to schematic signals and group schematic signals;

[0019] Electrical attributes include chapter number, steady-state current, maximum current, minimum operating voltage, whether it is 360-degree shielded, function code, redundancy, circuit function code, electromagnetic compatibility category, first two digits of serial number, wire type, color, wire gauge, special wire code, and laying code;

[0020] Chapter numbers are used to define the system in which the principle signal resides.

[0021] Optionally, the above-mentioned physical architecture-based aircraft electrical system design system also includes an interface server;

[0022] The interface server provides clients with interfaces for querying, modifying, and creating databases and files;

[0023] The interface server is deployed in a distributed manner.

[0024] Optionally, the above-mentioned physical architecture-based aircraft electrical system design system also includes a database server;

[0025] Database servers are used to store and manage structured data related to aircraft electrical system design;

[0026] Structured data related to aircraft electrical system design specifically includes architectural equipment, principle equipment, and principle signals.

[0027] Optionally, the above-mentioned physical architecture-based aircraft electrical system design system also includes a file server;

[0028] The file server is used to store and manage unstructured or semi-structured data related to aircraft electrical system design;

[0029] Unstructured or semi-structured data related to aircraft electrical system design includes documents, 3D models, configuration files, and log files.

[0030] This application has at least the following beneficial technical effects:

[0031] A physical architecture-based aircraft electrical system design system and method are disclosed, which allows multiple engineers to collaborate on the design. After the aircraft electrical system design is completed, engineers can change the connector model or pin configuration through predefined user terminals without redesigning the aircraft electrical system. This enables collaborative design and rapid modification of aircraft electrical systems based on physical architecture. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of the aircraft electrical system design method based on physical architecture provided in the embodiments of this application;

[0033] Figure 2 This is a schematic diagram illustrating connector type and pin matching for virtual device pins provided in an embodiment of this application;

[0034] Figure 3 This is a schematic diagram of the principle signal connection relationship object provided in the embodiments of this application;

[0035] Figure 4 This is a schematic diagram of the composition of the aircraft electrical system design system based on physical architecture provided in the embodiments of this application;

[0036] Figure 5 This is a layered schematic diagram of the aircraft electrical system design system based on physical architecture provided in the embodiments of this application.

[0037] To better illustrate this embodiment, some content in the accompanying drawings may be omitted, enlarged, or reduced. They are for illustrative purposes only and should not be construed as limiting the scope of this application. Detailed Implementation

[0038] To make the technical solution and advantages of this application clearer, the technical solution of this application will be described in a clearer and more complete manner below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only some embodiments of this application, and are only used to explain this application, not to limit this application. It should be noted that, for ease of description, only the parts related to this application are shown in the accompanying drawings, and other related parts can be referred to the general design.

[0039] Furthermore, unless otherwise defined, the technical or scientific terms used in this application description shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The word "comprising" as used in this application description indicates that the concept preceding the word encompasses the concepts listed following the word and their equivalents, without excluding other related concepts.

[0040] Furthermore, the terms indicating location used in the description of this application are only used to indicate relative directions or positional relationships. When the absolute position of the described object changes, its relative positional relationship may also change accordingly. It should also be noted that, unless otherwise explicitly specified and limited, terms such as "installation" and "connection" used in the description of this application should be interpreted broadly. For example, a connection can be a fixed connection or a detachable connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium. Those skilled in the art can understand its specific meaning in this application according to the specific circumstances.

[0041] A physical architecture-based design method for aircraft electrical systems, such as Figure 1 As shown.

[0042] Step 1: Create a prototype device based on the physical architecture device.

[0043] Step 2: Define the virtual device pins on the physical device.

[0044] Define virtual device pins on the physical device based on the number of signals.

[0045] Step 3: Match the connector type and pins of the virtual device.

[0046] Define the number and model of connector ports, and perform connector model and pin matching for virtual device pins. Define its harness end connectors and tail accessories, generate mapping relationships, and assign engineering meanings to the virtual device pins, such as... Figure 2 As shown.

[0047] Step 4: Based on the physical architecture device interface connection relationship, define the principle signals between the device and the device, and assign the principle signals to specific pins at the device end.

[0048] Aircraft electrical system design is based on the slave-to-pivot relationship of physical architecture device interfaces. Principle signals are created on a per-physical architecture device interface basis. Based on the connection relationship between the physical architecture device interface and other physical architecture devices, the end-to-end device of the principle signal is determined. The slave-to-end pin assignment of the principle signal is performed by reading the predefined connectors and connector pins of the principle device.

[0049] Based on the number of signals, a corresponding number of virtual device pins are introduced to establish a connection between the principle signals and the virtual device pins, and to disconnect them from the connector pins. When the connector model and pins are changed, only the mapping relationship between the virtual device pins and the connector pins needs to be updated. There is no need to update the connection relationship of the principle signals again, thus enabling rapid changes to the connector model or pins.

[0050] The distribution of schematic signals from end to end is achieved through the selection of connectors and connector pins that match the schematic device, establishing connections with virtual device pins. A connection relationship object is created to express the relationship between schematic signals and physical architecture interface instances, physical architecture device instances, and virtual device pins. The connection relationship object is as follows: Figure 3 As shown.

[0051] Based on the connection relationships of the physical architecture device interfaces, the end device of the principle signal created under the interface needs to be determined. It is necessary to consider the one-to-many (one physical architecture device is connected to the interfaces of multiple other physical architecture devices through one interface) and many-to-many (one physical architecture device is connected to the interfaces of multiple other physical architecture devices through multiple interfaces) scenarios.

[0052] Step 5: Add electrical attributes to the schematic signals and group the schematic signals.

[0053] Electrical attributes include chapter number, steady-state current, maximum current, minimum operating voltage, whether it is 360-degree shielded, function code, redundancy, circuit function code, electromagnetic compatibility category, first two digits of serial number, wire type, color, wire gauge, special wire code, laying code, etc.

[0054] Chapter numbers are used to define the system in which the principle signals reside, making it easier to organize the principle signals and generate schematic diagrams under that system node.

[0055] A physical architecture-based aircraft electrical system design system is provided to implement the physical architecture-based aircraft electrical system design method disclosed in the above embodiments, such as... Figures 4-5 As shown, it includes the user client, interface server, database server, and file server.

[0056] The user end includes connector predefined user end, electrical system design user end, and electrical attribute editing user end.

[0057] The predefined connector user end is used to create a prototype device based on the physical architecture device. It defines virtual device pins on the prototype device according to the number of signals, defines the number and model of connector ports, and matches the virtual device pins with connector models and pins to generate a mapping relationship, giving the virtual device pins engineering meaning.

[0058] The electrical system design user terminal is used to define the principle signals between devices based on the physical architecture device interface connection relationships, and to assign specific pins for the principle signals from the end to the end. Aircraft electrical system design is based on the end-to-end relationships of physical architecture device interfaces. Principle signals are created on a per-physical architecture device interface basis. Based on the connection relationships between physical architecture device interfaces and other physical architecture devices, the end-to-end devices for the principle signals are determined. The end-to-end pin assignment of the principle signals is performed by reading the predefined connectors and connector pins of the principle devices.

[0059] The electrical attribute editing client is used to add electrical attributes to schematic signals and group them. Electrical attributes include section number, steady-state current, maximum current, minimum operating voltage, whether it is 360-degree shielded, function code, redundancy, circuit function code, electromagnetic compatibility category, the first two digits of the serial number, wire type, color, wire gauge, special wire code, and laying code. The section number defines the system in which the schematic signal resides.

[0060] The client is used by users to perform front-end aircraft electrical system design operations. The interface server provides the client with interfaces to query, modify, and create databases and files. The database server is used to store and manage structured data related to aircraft electrical system design, such as architecture equipment, principle equipment, principle signals, etc. The file server is used to store and manage unstructured or semi-structured data related to aircraft electrical system design, such as documents, 3D models, configuration files, log files, etc.

[0061] The API server is deployed in a distributed manner, achieving load balancing by increasing the number of service nodes and resolving the issue of resource scarcity on a single server caused by a large number of online users and access requests during peak periods. Simultaneously, to address the problem of excessively long processing times due to large amounts of data retrieved in a single access request, each API server call is processed using multi-threading, fully utilizing server resources and improving interaction efficiency.

[0062] Connector predefined user terminals, electrical system design user terminals, and electrical attribute editing user terminals are deployed according to the number of users. Users access the database server and file server by calling the interface server to search, create, and modify data and files, thereby realizing collaborative design of aircraft electrical systems.

[0063] The physical architecture-based aircraft electrical system design system disclosed in the above embodiments allows multiple engineers to collaborate on the design. After the aircraft electrical system design is completed, engineers can change the connector model or pin configuration through predefined user terminals without having to redesign the aircraft electrical system. This enables collaborative design and rapid modification of the aircraft electrical system based on the physical architecture.

[0064] The technical solution of this application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. Those skilled in the art should understand that the scope of protection of this application is obviously not limited to these specific embodiments. Without departing from the principles of this application, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will all fall within the scope of protection of this application.

Claims

1. A physical architecture-based aircraft electrical system design method, characterized in that, include: Step 1: Create a prototype device based on the physical architecture device; Step 2: Define the virtual device pins on the prototype device; Step 3: Match the connector type and pins of the virtual device; Step 4: Based on the physical architecture device interface connection relationship, define the principle signals between the device and the device, and assign specific pins for the principle signals from the device to the device. Step 5: Add electrical attributes to the schematic signals and group the schematic signals.

2. The aircraft electrical system design method based on physical architecture according to claim 1, characterized in that, Electrical attributes include chapter number, steady-state current, maximum current, minimum operating voltage, whether it is 360-degree shielded, function code, redundancy, circuit function code, electromagnetic compatibility category, first two digits of serial number, wire type, color, wire gauge, special wire code, and laying code; Chapter numbers are used to define the system in which the principle signal resides.

3. A physical architecture-based aircraft electrical system design method, used to implement the physical architecture-based aircraft electrical system design method of claim 1, characterized in that, Including the user end; The user end includes connector predefined user end, electrical system design user end, and electrical attribute editing user end; The predefined connector user end is used to create a schematic device based on the physical architecture device. It defines virtual device pins on the schematic device according to the number of signals, defines the number and model of connector ports, and matches the virtual device pins with connector models and pins to generate a mapping relationship and give the virtual device pins engineering meaning. The electrical system design user end is used to define the principle signals between the device and the physical architecture based on the device interface connection relationship, and to assign specific pins of the principle signals from the device to the device. The electrical attribute editing client is used to add electrical attributes to schematic signals and group schematic signals.

4. The aircraft electrical system design system based on physical architecture according to claim 3, characterized in that, Electrical attributes include chapter number, steady-state current, maximum current, minimum operating voltage, whether it is 360-degree shielded, function code, redundancy, circuit function code, electromagnetic compatibility category, first two digits of serial number, wire type, color, wire gauge, special wire code, and laying code; Chapter numbers are used to define the system in which the principle signal resides.

5. The aircraft electrical system design system based on physical architecture according to claim 4, characterized in that, It also includes the interface server; The interface server provides clients with interfaces for querying, modifying, and creating databases and files.

6. The aircraft electrical system design system based on physical architecture according to claim 5, characterized in that, The interface server is deployed in a distributed manner.

7. The aircraft electrical system design system based on physical architecture according to claim 6, characterized in that, It also includes a database server; Database servers are used to store and manage structured data related to the design of aircraft electrical systems.

8. The aircraft electrical system design system based on physical architecture according to claim 7, characterized in that, Structured data related to aircraft electrical system design specifically includes architectural equipment, principle equipment, and principle signals.

9. The aircraft electrical system design system based on physical architecture according to claim 8, characterized in that, It also includes file servers; The file server is used to store and manage unstructured or semi-structured data related to aircraft electrical system design.

10. The aircraft electrical system design system based on physical architecture according to claim 9, characterized in that, Unstructured or semi-structured data related to aircraft electrical system design includes documents, 3D models, configuration files, and log files.

Images