Distributed power distribution system controller, synchronization method and system based on TTP communication

Abstract

The application provides a distributed power distribution system controller based on TTP communication, a synchronization method and system. The method comprises the following steps: generating a TTP message description list, a primary and backup network message payload mapping, a local cache address and a standardized read-write interface based on a data mapping table; interconnecting multiple controller nodes through a dual-redundancy TTP-A network and a TTP-B network; correcting a local scheduling clock at a communication cycle boundary and a time slot boundary by using a TTP global time base; constructing a two-dimensional task list based on a time-triggered slot, a task type, a task priority, a deadline and a data dependency relationship; scheduling power distribution sampling, fault criterion, control output and state feedback tasks in a preconfigured fixed time slot and a redundant execution slot. The power distribution control task chain is combined with TTP deterministic time slot planning, primary and backup network consistency checking and timeout safety processing, thereby improving the fault tolerance of the aircraft distributed power distribution system during primary and backup power source switching.

Description

Technical Field

[0001] This application relates to the field of power distribution systems for large civil aircraft, and in particular to a distributed power distribution system controller, synchronization method and system based on TTP communication. Background Technology

[0002] With the continuous increase in the number of devices in the multiple electrical systems of large civil aircraft, the electrical equipment of the power distribution system is widely distributed in various areas of the fuselage. The power distribution system is usually composed of busbars, cables, circuit breakers, contactors and related protection devices. Its function is to reliably distribute the electrical energy output from the power system to various electrical devices, and it is a key component to ensure the safe and stable operation of the aircraft.

[0003] In a power distribution system, the controller's role is to collect the operating status of the power supply and distribution components and perform load switching and protection control according to the aircraft's power requirements. For example, the switching of primary and backup power circuits, the maintenance of power supply to critical loads, and the isolation between faulty branches all need to be completed simultaneously by multiple controller nodes. If each controller node's sampling, judgment, output of commands, or feedback of a certain status to the other cannot be scheduled in a regular manner according to a unified time base, it may lead to delays in primary and backup power switching, or even incorrect execution of control commands or malfunctions. Therefore, in order to enable the aircraft power distribution system to "work collaboratively, switch seamlessly, and execute commands consistently," in addition to the ability for controllers to communicate with each other, time logic must also be consistent in message transmission and reception, task scheduling, control output, and event logging.

[0004] In this context, the Time-Triggered Protocol (TTP) bus is a communication protocol designed for safety-critical embedded applications. Its strong determinism, support for time-triggered communication, and ability to implement dual-redundant networks make it suitable for use in distributed fault-tolerant real-time control systems composed of multiple intelligent nodes. As aircraft's multi-electric systems are upgraded and improved, the number of power distribution controllers and the scale of interfaces are increasing. This leads to growing operational costs and adaptation difficulties for existing architectures in terms of interface configuration consistency, node expansion, primary / backup network consistency determination, and deterministic scheduling of control tasks.

[0005] In addition, existing solutions often focus on communication links or single clock synchronization, without fully considering the sampling, fault criteria, control output and status feedback links of aircraft power distribution tasks. They also lack support for primary and backup network data consistency, safe handling after task timeout, and deterministic orchestration of multi-controller task chains. Summary of the Invention

[0006] This application provides a distributed power distribution system controller, synchronization method, and system based on TTP communication to solve the problems in existing aircraft power distribution systems, such as inconsistent time bases, error-prone interface configuration, difficulty in determining the consistency of primary and backup network data, and lack of determinism in handling task timeouts.

[0007] In a first aspect, this application provides a distributed power distribution system controller synchronization method based on TTP communication, applied to an aircraft power distribution system containing multiple controller nodes, the method comprising the following steps: S1: Architecture Construction; Construct a layered architecture for the controller software, including a hardware layer, a low-level driver layer, a middleware layer, and an application layer; The application layer includes a sampling module, a control module, and a communication module, while the middleware layer includes a time synchronization module, a task scheduling module, a data interface management module, and an execution monitoring module. S2: Mapping and Interface Generation; Based on the preset data mapping table, determine the production controller node, consumer controller node, data length, sampling period, transmission period, deadline, priority, security default value, primary and backup network slot number, message payload offset and local cache address of each power distribution control data item, and generate TTP message description list, transmission cache, reception cache and standardized inter-controller data read and write interface accordingly. S3: Network interconnection; The multiple controller nodes are interconnected through a dual-redundant TTP network to form a distributed control cluster; wherein each controller node is simultaneously connected to both TTP-A and TTP-B networks, and the TTP-A and TTP-B networks adopt corresponding bus cycles, time trigger slots, and message payload mappings. S4: Time synchronization; A time synchronization module is deployed in the intermediate layer. The time synchronization module latches the global time base when the TTP communication cycle starts interrupt and the time trigger slot starts interrupt, and corrects the local scheduling clock of each controller node according to the global time base. S5: Task scheduling planning; a two-dimensional task list is constructed based on the predefined time trigger slots of the TTP network, the data mapping table, and the power distribution task dependencies; wherein, the two-dimensional task list uses the time trigger slot number as the vertical index and the task type as the horizontal dimension, and each list unit stores an array of task description items sorted by priority and deadline; S6: System operation; The task scheduling module, based on the globally unified time base and the two-dimensional task list, plans the scheduling sampling, fault judgment, control output, communication interaction and status feedback tasks in the fixed time trigger slot and the pre-configured redundant execution slot, and takes calculated safety actions to complete the work of multiple controller nodes in case of timeout, invalid data or inconsistency between primary and backup network data, according to the actual situation.

[0008] In step S2, the data mapping table includes at least the data item identifier, production controller node, consumer controller node, data length, sampling period, sending period, deadline, priority, security default value, primary / backup network slot number, message payload offset, and local cache address.

[0009] After reading the data mapping table, the configuration tool groups the data items according to the production controller node and the transmission cycle, and generates message description lists, message payload mappings, transmission buffer structures, reception buffer structures, and standardized read / write interface functions for TTP-A and TTP-B networks.

[0010] After each controller node is powered on, it verifies the configuration version number and consistency check code; if the verification is successful, it enters the synchronous operation state; if the verification fails, it maintains the safe default output and reports the configuration error.

[0011] In step S4, the controller node latches the global time base TG0 when the TTP bus cycle start interrupt arrives, and calculates the start time Ti of each time trigger slot Ti=TG0+Offseti according to the preset slot offset table; when the deviation between the global time base and the local scheduling clock exceeds the preset tolerance threshold, the local scheduling clock is corrected.

[0012] In step S5, the task description item includes at least a task identifier, associated controller node, task type, execution cycle, cycle phase, worst execution time, deadline, dependent input data items, output data items, priority, safety actions, and overflow handling strategy; the task type includes at least emergency fault handling, critical load control, routine data sampling, and non-critical communication interaction.

[0013] The specific method for planning the time trigger slot in step S6 includes: Allocate fixed-time trigger slots or exclusive execution windows for emergency fault handling tasks and critical load control tasks, and occupy priority timing within the TTP bus cycle; Multiple tasks with logical associations of sampling, fault criteria, control output, and status feedback are allocated in time-sequentially triggered slots according to their data dependencies and control dependencies. The timing sequence of corresponding time trigger slots is planned for TTP-A network and TTP-B network, and the consistency of the same data item in the primary and backup networks is judged by the period number, sequence number, timestamp and verification information. Among them, the receiving controller node determines that the data item is valid when the timestamp difference between the primary and backup network messages is not greater than the preset synchronization deviation threshold and the verification information is valid. The preset synchronization deviation threshold is preferably not greater than 1 microsecond.

[0014] Step S6 further includes timeout handling: redundant execution slots are pre-set in the time-triggered slot planning, and the slot position, slot length, and TTP bus cycle of the redundant execution slots are determined during the system configuration phase; the execution monitoring module records the actual execution time of the task, and when a regular data sampling task, non-critical communication interaction task, or log task is not completed within the fixed time-triggered slot and its overflow handling strategy allows for continued execution, the task is added to the redundant slot waiting queue; when a redundant execution slot arrives, the task scheduling module selects the task to continue execution according to priority and deadline; for emergency fault handling tasks and critical load control tasks, if they are not completed within the deadline, a preset safety action is executed.

[0015] Furthermore, the sampling module is used to collect voltage, current, contactor status, temperature, or load status data of the corresponding power distribution unit in real time and temporarily store them in a local cache; the control module is used to generate power distribution control commands based on the sampled data, collaborative control data, and aircraft power demand; the communication module is used to upload sampled data, receive collaborative commands, and forward control commands through the dual-redundant TTP network; and the execution monitoring module is used to record the task start time, end time, execution status, and timeout status.

[0016] Furthermore, the dual-redundant TTP network configures the sending and receiving behavior, message period, message length, payload offset, and A / B network correspondence of each controller node in each time trigger slot through a predefined message description list, so as to achieve conflict-free deterministic communication access.

[0017] Furthermore, the synchronization method can be used for main / backup power switching, fault isolation, critical load power supply maintenance, or non-critical load unloading control in civil aircraft airborne special power systems.

[0018] Secondly, this application also provides a distributed power distribution system controller, applied in the above-mentioned TTP-based distributed power distribution system controller synchronization method, wherein the controller includes: The processor is used to execute programs in the software layered architecture and to invoke sampling, control, communication, time synchronization and monitoring-related tasks according to the two-dimensional task list; The TTP communication controller is used to simultaneously access the TTP-A network and the TTP-B network, and to send or receive messages in a predefined time slot according to the message description list. The system includes a memory and a local timer. The memory stores the data mapping table, message description list, two-dimensional task list, send buffer, receive buffer, and task execution records. The local timer provides a local scheduling clock to the task scheduling module after correction by the time synchronization module.

[0019] Thirdly, this application also provides an aircraft power distribution system, including multiple distributed power distribution system controllers as described in the second aspect interconnected via a dual-redundant TTP network. Each controller performs coordinated control of primary / backup power switching, fault isolation, critical load power supply maintenance, or non-critical load unloading by executing the distributed power distribution system controller synchronization method based on TTP communication as described in the first aspect.

[0020] Compared with the prior art, this application has the following beneficial effects: This application has at least the following beneficial effects: First, interface configuration consistency is high. Using a data mapping table as the common input for communication configuration, cache mapping, interface functions, and task triggering relationships can reduce manual configuration errors and ensure consistency between production nodes, consumer nodes, message payloads, and local caches.

[0021] Secondly, it ensures strong synchronization and consistency between the primary and backup networks. Through the joint judgment of TTP global time base, periodic boundary latching, slot boundary triggering, and A / B network period number, sequence number, timestamp, and verification information, multiple controller nodes can maintain a unified time base on the power distribution task chain.

[0022] Third, it offers strong real-time performance and good determinism. Through a two-dimensional task list and time-triggered slot planning, tasks are scheduled based on priority, deadline, and data dependencies, ensuring that tasks for handling emergency faults and controlling critical loads can be executed within a preset time sequence, reducing uncertainty and delays under event-triggered methods. Fourth, it boasts high fault tolerance and resource utilization. It can perform safety actions and degrade to a controllable state when a single channel is abnormal or data is invalid, or when there is a timeout or inconsistency between primary and backup network data (while absorbing non-critical task execution time fluctuations through redundant execution slots), improving robustness without altering the static planning of the TTP communication slots. Fifth, it is suitable for extended use in aviation power distribution. Common tasks in the system, such as primary / backup power switching, fault isolation, critical load maintenance, and non-critical load offloading, are bound to deterministic communication time slots, facilitating reuse when adding controller nodes or expanding the power distribution area. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a topology diagram of the controller nodes interconnected via a TTP network according to an embodiment of this application, wherein, in the case of dual redundancy, the TTP-A network and the TTP-B network can be arranged separately according to the same topology; Figure 2 This is a schematic diagram of the structure of the distributed power distribution system controller provided in the embodiments of this application; Figure 3 This is a schematic diagram of the task registration, polling execution, timeout monitoring, and redundant slot scheduling process based on TTP time slots provided in the embodiments of this application; Figure 4 This is a schematic diagram of the TTP bus time wheel cycle, time trigger slot division, and task scheduling timing planning provided in the embodiments of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0027] refer to Figures 1 to 4 This embodiment provides a method for synchronizing a distributed power distribution system controller based on TTP communication. This method does not simply utilize the TTP network for communication synchronization; instead, it further coordinates the sampling, fault diagnosis, control output, communication interaction, and status feedback tasks in aircraft power distribution control with data mapping tables, message description lists, time-triggered slots, and mission safety actions.

[0028] S1: Architecture Construction; The controller software architecture is set up as a hardware layer, a low-level driver layer, a middleware layer, and an application layer. The application layer includes a sampling module, a control module, and a communication module; the middleware layer includes a time synchronization module, a task scheduling module, a data interface management module, and an execution monitoring module. The sampling module is used to collect real-time operating data of the corresponding power distribution unit and temporarily store it in a local cache; the control module is used to generate power distribution control commands based on the sampled data, collaborative control data, and aircraft power requirements; the communication module is used to upload sampled data, receive collaborative commands, and forward control commands via the TTP network; the execution monitoring module is used to record task start time, end time, execution status, and timeout status.

[0029] For example, such as Figure 2As shown, the power distribution system consists of four regional power distribution controllers, each employing the aforementioned four-layer software architecture. The hardware layer may include an MCU, a dedicated TTP communication controller, a local timer, an analog acquisition interface, a discrete input interface, and a contactor drive interface. In the application layer, the sampling module acquires local busbar voltage, current, and contactor feedback status at 1ms intervals; the control module calculates load switching commands based on the sampled values ​​and collaborative data from the aircraft power grid management computer or adjacent controllers; the communication module completes TTP message transmission and reception according to the message description list; and the execution monitoring module calculates the actual execution time of each task and provides timeout status to the task scheduling module.

[0030] S2: Mapping and Interface Generation: Based on a pre-set data mapping table, a standardized set of data interfaces between various types of controllers is generated for the multiple controller nodes. The data mapping table includes at least the data item identifier, producer controller node, consumer controller node, data type, data length, sampling period, transmission period, deadline, priority, security default value, TTP-A network slot number, TTP-B network slot number, message payload offset, transmit buffer address, and receive buffer address. For example, the data item "BUS1_volT" here is the main bus voltage obtained by controller 1.

[0031] The data item displays a 32-bit floating-point data type, with a sampling period of 1ms and a transmission period of 5ms. The consumer controller nodes are controller 2 and controller 3, respectively, and the default safety value is invalid voltage. After reading this data item through the configuration tool, it is encapsulated into the periodic transmission messages of controller 1. The results of these messages are then used to generate the corresponding slot number, payload offset, transmit buffer structure, receive buffer structure, read / write interface functions, configuration version number, and consistency check code for TTP-A and TTP-B networks, respectively.

[0032] Specifically, the configuration tool performs the following processing: First, it reads the data mapping table and performs integrity verification to confirm that each data item has a unique data item identifier, a production controller node, at least one consumer controller node, data length, transmission period, deadline, and security default value; second, it groups the data items according to the production controller node and transmission period, and encapsulates data items from the same production controller node with the same or compatible transmission periods into the same TTP message; third, it allocates time trigger slots to the TTP message according to the data item priority and deadline, and calculates the offset address of each data item in the message payload; finally, it generates message description lists, transmission buffer structures, reception buffer structures, and standardized read / write interfaces for TTP-A and TTP-B networks.

[0033] After each controller node powers on, it first reads the configuration version number and consistency check code from its local memory and compares them with the version number and check code in the TTP network configuration. If they match, it is allowed to enter the synchronous operation state; if they do not match, the controller maintains the safe default output, prohibits the execution of new load switching commands, and reports the configuration anomaly through the available network channel. Therefore, the data mapping table is used not only to define the data format but also to constrain the consistency relationship between message payload, cache address, task input, and task output.

[0034] S3: Network Interconnection; Multiple controller nodes are interconnected using dual-redundant TTP to form a distributed control cluster. Each controller node is simultaneously connected to both TTP-A and TTP-B networks. In the dual-redundant TTP network, a predefined message description list is used to determine the correspondence between each controller node's sending and receiving behavior, message period, message length, payload offset, and the A / B networks within each time trigger slot.

[0035] like Figure 1 As shown, multiple controller nodes are connected via a TTP network. When implementing a dual-redundancy scheme, the TTP-A network and the TTP-B network can be arranged with the same topology. Each controller node's TTP communication controller is connected to two physical channels simultaneously. When one channel experiences a link failure, input message verification fails, or data times out, the receiving controller node can continue the power distribution control task based on a valid message from the other channel.

[0036] S4: Time Synchronization; A time synchronization module is deployed in the intermediate layer to obtain the global time base using the time triggering mechanism provided by the dual-redundant TTP network. When the TTP bus cycle start interrupt arrives, the controller node latches the global time base TG0 and calculates the start time Ti = TG0 + Offseti for each time trigger slot based on a pre-set slot offset table. The task scheduling module uses the start time of the aforementioned time trigger slots as the reference time for triggering tasks, instead of directly triggering tasks using the controller's locally running clock. For example, the TTP bus cycle can be selected as 5ms.

[0037] At the start of each TTP bus cycle, the TTP communication controller generates a cycle start interrupt. The time synchronization module reads the TTP network global time TG in the interrupt service routine and compares it with the local MCU's microsecond-level timer MT. The preset tolerance threshold is 10μs. If |TG-MT|>10μs, the local scheduling clock is corrected to TG; otherwise, the current scheduling clock is maintained. When the TTP-A and TTP-B networks receive the same data item, the receiving controller node compares the cycle number, sequence number, timestamp, and CRC check information. When the timestamp difference is not greater than the preset synchronization deviation threshold and the check is valid, the data received by the primary and backup networks is considered valid. In a preferred embodiment, the preset synchronization deviation threshold is 1μs.

[0038] When both primary and backup network data are valid and consistent, the controller uses the data from the higher priority or the preset primary channel. When one network channel data times out, the sequence number is discontinuous, or the CRC check fails, the controller uses valid data from the other network channel. When the data from both channels is invalid or exceeds the synchronization deviation threshold, the controller does not use the data item to trigger a new control output, but instead executes the security default value defined in the data mapping table or the security action defined in the task description item.

[0039] S5: Task Scheduling and Planning; A two-dimensional task list is constructed based on the predefined time-triggered slots, data mapping table, and power distribution task dependencies in the TTP network. Specifically, the task list uses the time-triggered slot number as the vertical index and the task type as the horizontal index. Each task list unit stores an array of task description items sorted by priority and deadline. These task description items include at least: task identifier, associated controller node, task type, execution cycle, cycle phase, worst-case execution time, deadline, dependent input data items, output data items, safety actions, and overflow handling strategies.

[0040] For example, task types can be categorized into four types: emergency fault handling, critical load control, routine data sampling, and non-critical communication interaction. For instance, with a 5ms bus cycle, this cycle can be divided into several fixed-time trigger slots, with one or more redundant execution slots reserved. For a controller with four regional power distribution zones, its 5ms cycle can be divided into four fixed control slots and one redundant execution slot. The four fixed control slots occupy a total of 4.5ms, while the redundant execution slot occupies 0.5ms. Each slot can register sampling, fault criteria, control output, status feedback, or other non-critical communication tasks. For the extended embodiment with eight controller nodes, as long as bandwidth and deadline constraints are met, slot number indices can be added or task descriptions can be changed without altering the basic rules of data mapping, primary / backup network consistency judgment, and redundant execution slot scheduling.

[0041] At the start of each time-triggered slot, the task scheduling module reads the current slot number `slotIndex` and the current cycle number `cycleIndex`, and accesses the two-dimensional task list `TaskMatrix[slotIndex][taskType]`. For the array of task description items in this list cell, the task scheduling module checks the following in order of priority and deadline: whether the current cycle number meets the task execution cycle and cycle phase requirements, whether the dependent input data items are valid within the valid time window, and whether the current time has not exceeded the task's latest start time. If the above conditions are met, the corresponding task function is called; if the dependent data is invalid, a safe default value is output according to the safety action in the task description item, the previous valid output is maintained, or a fault status is reported.

[0042] For example, Slot 1 can register the "Main Busbar Overvoltage Detection" task and the "Controller 1 Status Transmission" task; Slot 2 can register the "Backup Power Supply Connection Judgment" task; Slot 3 can register the "Contactor Drive Output" task; and Slot 4 can register the "Contactor Feedback Status Sampling and Confirmation" task. These tasks are executed continuously within the same TTP cycle or adjacent TTP cycles according to the logical chain of sampling, fault criterion, control output, and status feedback, thereby shortening the coordination delay for main / backup power supply switching and fault isolation.

[0043] S6: System Operation; The task scheduling module schedules tasks in the two-dimensional task list based on the globally unified time base, task priority, deadline, and time trigger slot planning. Time trigger slot planning includes: allocating fixed time trigger slots or exclusive windows for emergency fault handling tasks and critical load control tasks; arranging logically related tasks in time trigger slots with coherent timing in the order of sampling, fault criteria, control output, and status feedback; planning corresponding time trigger slot timing for TTP-A and TTP-B networks, and determining the consistency of the same data item in the primary and backup networks through cycle number, sequence number, timestamp, and verification information.

[0044] For example, after the system powers on, the TTP network establishes synchronization. Each controller first verifies the configuration version number and consistency check code, and then performs sampling, control calculation, and communication interaction according to the planned time trigger slots and task list. When a controller node fails or one of the network channels fails, the system degrades its operation based on valid data from the other channel and preset safety actions. When both channels are unavailable or critical tasks exceed their deadlines, the controller maintains the previous valid control command, outputs a safe default control state, or disconnects the faulty branch to ensure basic power distribution functions.

[0045] In a primary / backup power supply switching scenario, when controller 1 detects that the primary power supply circuit voltage is lower than a set threshold in Slot 1 and remains below the acknowledgment time for an extended period, controller 1 writes a fault flag, sampling timestamp, and fault level into its transmitted message. After receiving the fault flag in Slot 2, controller 2 combines the backup power supply status data to determine backup power supply access and generates a backup power supply contactor closing command. Upon receiving the closing command, controller 3 executes the contactor driving task. After collecting the contactor feedback status in Slot 4, controller 4 sends an acknowledgment message. Because these tasks are planned according to continuous time-triggered slots, fault detection, switching judgment, control output, and status feedback can be completed within the same TTP cycle or adjacent TTP cycles.

[0046] In scenarios involving critical load protection and non-critical load unloading, when any controller node detects overcurrent or overtemperature, the corresponding fault handling task is placed with the highest priority. Specifically, the task scheduling module locates the current or next preset fault handling slot and determines whether to execute the subsequent fault handling sequence based on the load level specified in the data mapping table. For critical loads such as flight control and avionics, power supply status checks, fault reporting, or backup power path switching are typically performed. For non-critical loads, disconnect commands are generated according to the input unloading sequence. The disconnect command is bound to the TTP time trigger slot, so each controller node can complete the disconnect action according to the input time base requirements under a unified global time base.

[0047] Redundant execution slots are reserved execution windows pre-planned during the system configuration phase. Their slot positions, lengths, and associated TTP bus cycles do not change temporarily during operation. The execution monitoring module records the start time before a task begins and the end time after the task ends, comparing the actual execution time with the worst-case execution time in the task description. For routine sampling, non-critical communication interactions, or log tasks, if their overflow handling strategy allows for continued execution, they are added to the redundant slot waiting queue. For emergency fault handling and critical load control tasks, if they are not completed by the deadline, they are not treated as ordinary overflow tasks; instead, safety actions are performed and a fault status is reported.

[0048] For example, when the power distribution system contains 8 controller nodes, the number of time slots can be increased or the task description items can be adjusted, provided that bandwidth, bus cycle, and task deadline constraints are met; a dedicated execution window can also be set for global fault handling tasks. As the number of controller nodes increases, the data mapping table correspondingly adds production nodes, consumer nodes, and message payload mappings, and the two-dimensional task list correspondingly adds slot number indexes or task description items, but the interface generation, primary / backup network consistency judgment, and redundant execution slot scheduling rules remain unchanged, thereby supporting the expansion of the power distribution area.

[0049] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A distributed power distribution system controller synchronization method based on TTP communication, applied to an aircraft power distribution system containing multiple controller nodes, characterized in that, The method includes the following steps: S1: Architecture Construction; Construct a layered architecture for the controller software, including a hardware layer, a low-level driver layer, a middleware layer, and an application layer; The application layer includes a sampling module, a control module, and a communication module, while the middleware layer includes a time synchronization module, a task scheduling module, a data interface management module, and an execution monitoring module. S2: Mapping and Interface Generation; Based on the preset data mapping table, determine the production controller node, consumer controller node, data length, sampling period, transmission period, deadline, priority, security default value, primary and backup network slot number, message payload offset and local cache address of each power distribution control data item, and generate TTP message description list, transmission cache, reception cache and standardized inter-controller data read and write interface accordingly. S3: Network interconnection; The multiple controller nodes are interconnected through a dual-redundant TTP network to form a distributed control cluster; wherein each controller node is simultaneously connected to both TTP-A and TTP-B networks, and the TTP-A and TTP-B networks adopt corresponding bus cycles, time trigger slots, and message payload mappings. S4: Time synchronization; A time synchronization module is deployed in the intermediate layer. The time synchronization module latches the global time base when the TTP communication cycle starts interrupt and the time trigger slot starts interrupt, and corrects the local scheduling clock of each controller node according to the global time base. S5: Task scheduling planning; a two-dimensional task list is constructed based on the predefined time trigger slots of the TTP network, the data mapping table, and the power distribution task dependencies; wherein, the two-dimensional task list uses the time trigger slot number as the vertical index and the task type as the horizontal dimension, and each list unit stores an array of task description items sorted by priority and deadline; S6: System operation; The task scheduling module schedules sampling, fault judgment, control output, communication interaction and status feedback tasks in fixed time trigger slots and pre-configured redundant execution slots according to the global unified time base, the two-dimensional task list and time trigger slot planning. It also executes preset safety actions when the task times out, the data is invalid or the main and backup network data are inconsistent, so as to realize the collaborative work of multiple controller nodes.

2. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, Step S2 includes: Read the data mapping table and perform integrity verification to confirm that each power distribution control data item has a production controller node, at least one consumer controller node, data length, transmission cycle, deadline time and security default value; The power distribution control data items are grouped according to the production controller node and the transmission cycle. The offset address of each data item in the TTP message payload is calculated, and the corresponding slot number, cycle number and load offset are generated for the TTP-A network and the TTP-B network. Based on the grouping results, a message description list, a sending cache structure, a receiving cache structure, standardized read / write interface functions, a configuration version number, and a consistency check code are generated. Each controller node verifies the configuration version number and consistency check code after power-on.

3. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, Step S4 includes: latching the global time base TG0 at the beginning of each TTP bus cycle, calculating the start time Ti=TG0+Offseti of each time trigger slot according to the preset slot offset table; the task scheduling module uses the start time of the time trigger slot as the task triggering reference, instead of directly triggering the task using the controller's local free running clock; when the deviation between the global time base and the local scheduling clock exceeds the preset tolerance threshold, the local scheduling clock is corrected.

4. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, Steps S5 and S6 include: Construct a task description item, which includes at least a task identifier, associated controller node, task type, execution cycle, cycle phase, worst-case execution time, deadline, dependent input data items, output data items, priority, safety actions, and overflow handling strategy; the task type includes at least emergency fault handling, critical load control, routine data sampling, and non-critical communication interaction. Allocate fixed-time trigger slots or exclusive execution windows for emergency fault handling tasks and critical load control tasks, and assign multiple tasks with sampling, fault criteria, control output and status feedback logic associations to timing-coherent time trigger slots within the same TTP bus cycle or adjacent TTP bus cycles according to their data dependency and control dependency relationships. The timing sequence of corresponding time trigger slots is planned for TTP-A network and TTP-B network, and the period number, sequence number and timestamp are written into the primary and backup network packets of the same data item; the receiving controller node compares the period number, sequence number, timestamp and verification information. If the timestamp difference between the primary and backup network packets is not greater than the preset synchronization deviation threshold and the verification information is valid, the data item is determined to be valid, wherein the preset synchronization deviation threshold is not greater than 1 microsecond.

5. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, Step S6 further includes a timeout handling mechanism: redundant execution slots are pre-set in the time-triggered slot planning, and the slot position, slot length, and TTP bus cycle of the redundant execution slots are determined during the system configuration phase; the execution monitoring module monitors the actual execution time of the tasks, and when a regular data sampling task, a non-critical communication interaction task, or a log task is not completed within the fixed time-triggered slot and its overflow handling strategy allows for continued execution, the task is added to the redundant slot waiting queue, and when the redundant execution slot arrives, the task scheduling module selects the task to continue execution according to priority and deadline; for emergency fault handling tasks and critical load control tasks, if they are not completed within their deadline, the safety action in the task description item is executed.

6. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, The sampling module is used to collect voltage, current, contactor status, temperature or load status data of the corresponding power distribution unit in real time and temporarily store them in a local cache. The control module is used to generate power distribution control commands based on sampled data, collaborative control data, and aircraft power demand; the communication module is used to upload sampled data, receive collaborative commands, and forward control commands through the dual-redundant TTP network; the execution monitoring module is used to record the task start time, end time, execution status, and timeout status.

7. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, The dual-redundant TTP network configures the sending and receiving behavior, message period, message length, payload offset, and A / B network correspondence of each controller node in each time trigger slot through a predefined message description list, so as to achieve conflict-free deterministic communication access.

8. The distributed power distribution system controller synchronization method based on TTP communication according to claim 1, characterized in that, The synchronization method is used for main / backup power switching, fault isolation, critical load power supply maintenance, or non-critical load unloading control in civil aircraft airborne special power systems.

9. A distributed power distribution system controller, applied in the synchronization method of a distributed power distribution system controller based on TTP communication as described in any one of claims 1 to 8, characterized in that, The controller includes: The processor is used to execute programs in the software layered architecture and to invoke sampling, control, communication, time synchronization and monitoring-related tasks according to the two-dimensional task list; The TTP communication controller is used to simultaneously access the TTP-A network and the TTP-B network, and to send or receive messages in a predefined time slot according to the message description list. The system includes a memory and a local timer. The memory stores the data mapping table, message description list, two-dimensional task list, send buffer, receive buffer, and task execution records. The local timer provides a local scheduling clock to the task scheduling module after correction by the time synchronization module.

10. An aircraft power distribution system, characterized in that, The system includes multiple distributed power distribution system controllers as described in claim 9, interconnected via a dual-redundant TTP network. Each controller works collaboratively in scenarios such as primary / backup power switching, fault isolation, critical load power supply maintenance, or non-critical load offloading by executing the distributed power distribution system controller synchronization method based on TTP communication as described in any one of claims 1 to 8.

Images