Bus control software design method
By designing the bus control software in the LINK networking mode for the 10M1553B avionics bus, the bottleneck problems of the aircraft suspension system bus in terms of communication capacity and weapon access number are solved, efficient network management and message scheduling are achieved, and the overall performance of the system is improved.
Patent Information
- Application Number
- CN202411712670.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-27
- Publication Date
- 2025-04-18
AI Technical Summary
The GJB289A bus, which is widely used in existing aircraft suspension systems, has bottlenecks in terms of communication capacity and weapon access quantity, and it is difficult to meet the needs of new weapons installation.
A bus control software is designed to be applied to the LINK networking mode based on the 10M1553B avionics bus. Through the architecture design and message scheduling mechanism of the bus control software, network management and message scheduling control of multi-terminal network communication are realized.
It realizes efficient network management, message arrangement and communication transmission control, and has the ability to dynamically equalize the time slices of periodic messages and event messages transmission, avoids the problem of excessive instantaneous load of a single terminal, and improves the efficiency of message organization and scheduling.
Smart Images
Figure CN119847960A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the technical field of airborne bus control software design, and in particular relates to a bus control software design method. Background Art
[0002] Small and smart weapons are beginning to be used, and the number of aircraft mounted weapons is gradually increasing. The GJB289A bus widely used in aircraft suspension systems is currently facing bottlenecks in communication capacity and the number of weapons connected. In order to meet the needs of installing new weapons and improve the communication capabilities of the weapon bus, the 10Mbps command response data bus technology suitable for aircraft small suspension management systems is gradually being used.
[0003] In this type of bus, the bus control software is responsible for the management and message dispatching of all remote terminals in the bus, and is the core technology for the practical application of the 10Mbps bus network. In order to better adapt to the application scenarios of small hanging object management systems for various types of fighters, bombers, drones and transport aircraft, it is necessary to carry out network management and message dispatching control design based on multi-terminal networking communication in LINK mode. Summary of the invention
[0004] In view of this, the present invention provides a bus control software design method for network management and message scheduling control based on multi-terminal networking communication in LINK mode, which can better adapt to the application scenarios of small hanging object management systems of various types of fighters, bombers, drones and transport aircraft.
[0005] The technical solution of the present invention is:
[0006] A bus control software design method is applied in the LINK networking mode based on the 10M 1553B avionics bus; including the architecture design of the bus control software and the message scheduling mechanism design of the bus control software;
[0007] The bus control software is used for bus initialization, message organization and scheduling, and bus network management;
[0008] The message scheduling mechanism of the bus control software is used to organize and schedule periodic events.
[0009] Furthermore, the scheduling mechanism is used for data communication between the controller and the network terminal:
[0010] The scheduling mechanism includes:
[0011] Plan and set the scheduling cycle, divide the proportion of the periodic message scheduling time slice and the dynamic refresh event message scheduling time slice in the scheduling cycle, and divide them according to the transmission characteristics of the bus message, the total number of messages in the cycle and event, the length of the message, the refresh rate of the event message, and the message transmission cycle;
[0012] The periodic message scheduling time slice is used to transmit the periodic messages that need to be organized and scheduled within the current scheduling period; the dynamic refresh event message scheduling time slice is used to complete the scheduling transmission of event messages according to the refresh rate requirements of the event messages.
[0013] Furthermore, the periodic message scheduling time slice includes a start identification frame, a system maintenance frame, a system real-time clock, a message frame, and a periodic message that needs to be scheduled within the current period.
[0014] Furthermore, the start identification frame is used to indicate the beginning of the current scheduling cycle, and the system maintenance frame is used to maintain the online and offline status of the terminals in the system.
[0015] Furthermore, the system real-time clock configures the transmission period according to user requirements.
[0016] Furthermore, in order to avoid the jitter of network periodic message scheduling and the risk of centralized scheduling for a certain RT during system planning,
[0017] When setting the periodic messages that need to be scheduled in this cycle, consider the message length, scheduling cycle, total number of periodic messages, and number of periodic messages for each RT, complete the arrangement of messages that need to be scheduled in each cycle, and evenly distribute all periodic messages in the system to each scheduling cycle.
[0018] Furthermore, the system maintenance frame queries the number and information of network terminals currently on the network and performs statistics. The statistical information is the network terminal on-line list, and periodic messages organize and send messages to the network terminals on the network based on the on-line list; if a network terminal does not respond twice during the message organization and scheduling process, the system maintenance frame will mark it as offline, and will no longer organize messages for this network terminal.
[0019] Furthermore, a refresh event message scheduling table is provided in the dynamic refresh event message scheduling time slice; the refresh event message scheduling table is arranged according to the number of each network terminal and the refresh rate requirement;
[0020] Furthermore, in the dynamic refresh event message scheduling time slice, according to the dynamic refresh event message scheduling table, the bus controller uses the message refresh flag word and the control information of the vector word of the network terminal to organize the transmission of new data message frames related to the network terminal that has accessed the Internet.
[0021] Furthermore, in the dynamic refresh event message scheduling time slice, the bus controller only organizes the data frame transmission of the network terminal accessing the Internet. When a transmission failure occurs, a retry is automatically performed on another channel of the bus controller, and the retry message is executed within the current transmission cycle.
[0022] If the same network terminal does not respond to bus commands twice in a row, the bus controller will log the network terminal off the network, put the network terminal information into the system maintenance query table, and no longer organize the sending of messages related to the network terminal until the network terminal is back online.
[0023] The beneficial effects of the present invention are:
[0024] The present invention is based on the multi-terminal networking communication scenario under the LINK mode, realizes efficient network management, message arrangement and communication transmission control, has the ability to dynamically and evenly divide the transmission time slices of periodic messages and event messages, realizes uniform scheduling of messages of each terminal, avoids the problem of excessive instantaneous load of a single terminal, improves the efficiency of message organization and scheduling, and can better adapt to the application scenarios of small suspension management systems of various types of fighters, bombers, drones and transport aircraft. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0026] Figure 1 This is the working diagram of LINK mode;
[0027] Figure 2 BC software control timing diagram. DETAILED DESCRIPTION
[0028] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
[0029] The following describes the embodiments of the present disclosure through specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.
[0030] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this device and / or practice this method.
[0031] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The illustrations only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.
[0032] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.
[0033] In one embodiment of the present invention, a bus control software design method is proposed, which is applied in a LINK networking mode based on a 10M1553B avionics bus; it includes the architecture design of the bus control software and the message scheduling mechanism design of the bus control software;
[0034] The bus control software is used for bus initialization, message organization and scheduling, and bus network management;
[0035] The message scheduling mechanism of the bus control software is used to organize and schedule periodic events.
[0036] In this embodiment, the scheduling mechanism is used for data communication between the controller and the network terminal:
[0037] The scheduling mechanism includes:
[0038] Plan and set the scheduling cycle, divide the proportion of the periodic message scheduling time slice and the dynamic refresh event message scheduling time slice in the scheduling cycle, and divide them according to the transmission characteristics of the bus message, the total number of messages in the cycle and event, the length of the message, the refresh rate of the event message, and the message transmission cycle;
[0039] The periodic message scheduling time slice is used to transmit the periodic messages that need to be organized and scheduled within the current scheduling period; the dynamic refresh event message scheduling time slice is used to complete the scheduling transmission of event messages according to the refresh rate requirements of the event messages.
[0040] In this embodiment, the periodic message scheduling time slice includes a start identification frame, a system maintenance frame, a system real-time clock, a message frame, and a periodic message that needs to be scheduled within the current period.
[0041] In this embodiment, the start identification frame is used to indicate the beginning of the scheduling period, and the system maintenance frame is used to maintain the network access status of the terminals in the system.
[0042] In this embodiment, the system real-time clock configures the transmission period according to user requirements.
[0043] In this embodiment, in order to avoid the risk of network periodic message scheduling jitter and centralized scheduling for a certain RT during system planning,
[0044] When setting the periodic messages that need to be scheduled in this cycle, consider the message length, scheduling cycle, total number of periodic messages, and number of periodic messages for each RT, complete the arrangement of messages that need to be scheduled in each cycle, and evenly distribute all periodic messages in the system to each scheduling cycle.
[0045] In this embodiment, the system maintenance frame queries the number and information of the network terminals currently on the network and performs statistics. The statistical information is the network terminal on-line table, and the periodic message organizes and sends messages to the network terminals on the network based on the on-line table; if a network terminal does not respond twice during the message organization and scheduling process, the system maintenance frame will mark it as offline, and no longer organize messages for this network terminal.
[0046] In this embodiment, a refresh event message scheduling table is provided in the dynamic refresh event message scheduling time slice; the refresh event message scheduling table is arranged according to the number of each network terminal and the refresh rate requirement;
[0047] In this embodiment, in the dynamic refresh event message scheduling time slice, according to the dynamic refresh event message scheduling table, the bus controller uses the refresh flag word of the bus controller and the control information of the vector word of the network terminal to organize the sending of new data message frames related to the network terminal that has accessed the Internet.
[0048] In this embodiment, in the dynamic refresh event message scheduling time slice, the bus controller only organizes the data frame transmission of the network terminal accessing the Internet. When a transmission failure occurs, a retry is automatically performed on another bus controller channel, and the retry message is executed within the current transmission cycle.
[0049] If the same network terminal does not respond to bus instructions twice in a row, the bus controller will log the network terminal off the network, put the network terminal information into the system maintenance query table, and no longer organize the sending of messages related to the network terminal until the network terminal is back online.
[0050] In this embodiment, the bus controller is a key component of the bus system. In addition to issuing instructions, it must also continuously monitor the bus and the information transmitted on the bus. Most of the monitoring tasks (such as parity check, timeout pause, etc.) are implemented in hardware. The bus control algorithm and judgment are implemented in software.
[0051] In this embodiment, in the bus communication mode based on the LINK mode, the BC is directly connected to the logical hub responsible for controlling the RT line communication, and the bus does not require external RT addressing. Therefore, in this networking mode, when the BC software performs message scheduling, it only needs to fill in the RT addressing channel in the command word. The working diagram of the LINK mode is shown in FIG. Figure 1 shown.
[0052] This embodiment mainly illustrates the bus control software design architecture, bus message scheduling method and network maintenance mechanism in the LINK networking mode.
[0053] Figure 1 The figure is a schematic diagram of the LINK mode operation. The figure illustrates the bus addressing operation in the LINK mode: The operation requirements of the link mode are as follows:
[0054] Instructions from the BC shall only be sent in connection with the desired physical RT location and the RT address set to zero in the instruction word.
[0055] Broadcast messages (RT address 31) should be sent to all RTs simultaneously.
[0056] The hub does not need to look at any other RT lines for RT response information.
[0057] There is a physical mapping from a specific hub connection (physical RT wire pair) to a specific RT physical location.
[0058] The RT shall utilize the default address (0), respond only to command words with its RT address (0), and only accept messages with address 0 or address 31 (broadcast).
[0059] Figure 2 BC software control timing diagram. The figure illustrates the control flow of BC software scheduling bus messages.
[0060] The BC software (bus control software) consists of three parts: bus initialization, message organization and scheduling, and network management. The timing of BC software message scheduling is as follows: Figure 2as shown in .
[0061] In this embodiment, in the initialization function, the dynamic loading of bus messages and the acquisition of key information are completed. The user software calls the initialization interface function of the BC software and completes the addition of bus messages according to the usage requirements. After the BC control software receives the instruction from the user software to complete the message addition, it distributes the periodic messages evenly in each executed small cycle according to the designed periodic message arrangement algorithm and the configured period and delay requirements of the periodic messages. For ordinary event messages, the messages are classified and counted according to the message category.
[0062] In the bus message scheduling and processing function, the scheduled periodic messages are sent according to the time slice of the timer. For ordinary event messages, when the RT of the corresponding channel is found to be online, the message is organized and scheduled according to the user's sending requirements or the RT's sending requirements within the sending time slice specified in each small cycle.
[0063] In the network maintenance function, the BC software uses bus maintenance messages to achieve the management of terminals going online and offline and message organization control enablement for the entire network. Maintenance messages are organized and sent using timer asynchronous insertion. The order in which maintenance messages are sent is the bus terminal maintenance netlist defined by the system, which contains all RT channel numbers that will be used in the system. After the BC software generates maintenance messages according to the netlist, it queries each RT in turn according to the agreed time slice. When the RT is online, the maintenance message of the RT is removed from the maintenance netlist, enabling its corresponding periodic and event message organization functions; when the RT is offline, the RT is re-added to the bus terminal maintenance netlist. Close its corresponding periodic and event message organization functions.
[0064] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present disclosure should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.
Claims
1. A bus control software design method, applied in a LINK networking mode based on a 10M 1553B avionics bus; characterized in that: Including the architecture design of bus control software and the message scheduling mechanism design of bus control software; The bus control software is used for bus initialization, message organization and scheduling, and bus network management; The message scheduling mechanism of the bus control software is used to organize and schedule periodic event messages.
2. The bus control software design method according to claim 1, characterized in that: The scheduling mechanism is used for data communication between the controller and the network terminal: The scheduling mechanism includes: Plan and set the scheduling cycle, divide the proportion of the periodic message scheduling time slice and the dynamic refresh event message scheduling time slice in the scheduling cycle, and divide them according to the transmission characteristics of the bus message, the total number of messages in the cycle and event, the length of the message, the refresh rate of the event message, and the message transmission cycle; The periodic message scheduling time slice is used to transmit the periodic messages that need to be organized and scheduled within the current scheduling period; the dynamic refresh event message scheduling time slice is used to complete the scheduling transmission of event messages according to the refresh rate requirements of the event messages.
3. The bus control software design method according to claim 2, characterized in that: The periodic message scheduling time slice includes the start identification frame, system maintenance frame, system real-time clock, message frame and the periodic message that needs to be scheduled within this cycle.
4. The bus control software design method according to claim 3, characterized in that: The start identification frame is used to indicate the beginning of the current scheduling cycle, and the system maintenance frame is used to maintain the online and offline status of the terminals in the system.
5. The bus control software design method according to claim 4, characterized in that: The system real-time clock configures the transmission cycle according to user requirements.
6. The bus control software design method according to claim 5, characterized in that: In system planning, in order to avoid the risk of network periodic message scheduling jitter and centralized scheduling for a certain RT, When setting the periodic messages that need to be scheduled in this cycle, consider the message length, scheduling cycle, total number of periodic messages, and number of periodic messages for each RT, complete the arrangement of messages that need to be scheduled in each cycle, and evenly distribute all periodic messages in the system to each scheduling cycle.
7. The bus control software design method according to claim 6, characterized in that: The system maintenance frame queries the number and information of the network terminals currently on the network and performs statistics. The statistical information is the network terminal on-line table. The periodic message organizes and sends messages to the network terminals on the network based on the on-line table. If a network terminal does not respond twice during the message organization and scheduling process, the system maintenance frame will mark it as offline and will no longer organize messages for this network terminal.
8. The bus control software design method according to claim 7, characterized in that: In the dynamic refresh event message scheduling time slice, a refresh event message scheduling table is set; the refresh event message scheduling table is arranged according to the number of each network terminal and the refresh rate requirement.
9. The bus control software design method according to claim 8, characterized in that: In the dynamic refresh event message scheduling time slice, according to the dynamic refresh event message scheduling table, the bus controller uses the refresh flag word of the bus controller and the control information of the vector word of the network terminal to organize the sending of new data message frames related to the network terminals that have accessed the Internet.
10. The bus control software design method according to claim 9, characterized in that: In the dynamic refresh event message scheduling time slice, the bus controller only organizes the data frame transmission of the network terminal on the Internet. When a transmission failure occurs, it automatically retries on another bus controller channel, and the retry message is executed within the current transmission cycle. If the same network terminal does not respond to bus instructions twice in a row, the bus controller will log the network terminal off the network, put the network terminal information into the system maintenance query table, and no longer organize the sending of messages related to the network terminal until the network terminal is back online.