An Experimental Method for MIL-1394B Data Bus Network of an Aircraft Management System

Abstract

This application belongs to the field of bus network test technology, and particularly relates to a test method for the MIL-1394B data bus network of an aircraft management system. The method includes step S1: Based on the 1394B simulation verification software, configure the 1394B module of the aircraft management computer as a CC node, and configure the 1394B modules of other simulation devices as RN nodes to conduct basic characteristic test verification including ports, faults, and resets; step S2: Conduct data packet test verification including STOF packets, asynchronous stream packets, and transmitted and received messages; step S3: Conduct rate fault mode test verification including transmission rate and estimation mode; step S4: Based on autonomous CCDL verification and non-autonomous CCDL verification, conduct redundancy communication test verification. This application realizes the systematic test of the 1394B bus of the aircraft management system, taking into account the correctness and integrity of the test.

Description

Technical Field

[0001] This application belongs to the technical field of bus network testing, and particularly relates to a method for testing the MIL-1394B data bus network of an aircraft management system. Background Art

[0002] The emergence of the aircraft management system has integrated the traditional discrete flight control system, engine control system, and electromechanical system through comprehensive control, physics, and functions to form an integrated system, thereby improving the overall performance of the aircraft.

[0003] Based on the idea of forward design, the bus selection requirements of the aircraft management system were extracted, quantitative and qualitative requirements analysis of the aircraft management system was carried out, and compliance analysis of the airborne bus was performed according to the requirement indicators. It can be seen that the 1394B bus meets the system requirements.

[0004] IEEE 1394 was initially proposed by Apple. In 1995, the IEEE recognized FireWire as the IEEE 1394-1995 standard, and the improved standard was called 1394a. In 2002, the updated 1394 standard 1394b was introduced. Based on "IEEE 1394-1995" and "1394a", its bandwidth, transmission speed, distance, cost efficiency, etc. have been greatly improved. In 2006, the SAE adopted it as the standard for military and aerospace flight applications, namely the SAE AS5643 standard. For the AS5643 and AS5643_1 electrical layer standards, the SAE subsequently released relevant test protocols. The 1394 bus that meets the AS5643 and AS5643_1 standards is the 1394B bus.

[0005] Regarding the 1394B bus, in the prior art, research on 1394 simulation devices / simulation cards, 1394 bus fault research, 1394 test information research with FC as the transmission medium, IEEE 1394 bus test research, etc. have been carried out. However, these researches mainly focus on the testing of cable characteristics and electrical characteristics, and the coverage is not comprehensive. Summary of the Invention

[0006] To solve at least one of the above technical problems, this application designs a method for testing the MIL-1394B data bus network of an aircraft management system. On the one hand, it covers cable characteristics, and on the other hand, it covers system characteristics, ensuring the correctness and integrity of the test. Through basic characteristic tests, data packet tests, rate / fault mode tests, and redundancy communication tests, a systematic test of the 1394B bus of the aircraft management system is realized, taking into account the correctness and integrity of the test to solve or alleviate at least one problem in the background art.

[0007] The test method for the MIL-1394B data bus network of the aircraft management system in this application mainly includes:

[0008] Step S1: Based on the 1394B simulation verification software, configure the 1394B module of the aircraft management computer as a CC node, and configure the 1394B modules of other simulation devices as RN nodes to conduct basic characteristic test verifications including ports, faults, and resets;

[0009] Step S2: Conduct data packet test verifications including STOF packets, asynchronous stream packets, and transmitted and received messages;

[0010] Step S3: Conduct rate fault mode test verifications including transmission rate and estimation mode;

[0011] Step S4: Based on autonomous CCDL verification and non-autonomous CCDL verification, conduct redundancy communication test verifications.

[0012] Preferably, in step S1, conducting the basic characteristic test verifications includes:

[0013] Step S11: Conduct physical port connectivity verification according to whether the 1394B simulation verification software can identify the network topology;

[0014] Step S12: Conduct RN node fault reset verification according to whether the 1394B simulation verification software can identify the faulty RN node;

[0015] Step S13: Conduct RN node reset verification after fault recovery according to whether the 1394B simulation verification software can re-identify the RN node after the faulty RN node recovers;

[0016] Step S14: Conduct frequent power-on and power-off reset verification of the RN node according to whether the 1394B simulation verification software can identify the faulty RN node and re-identify the RN node after the faulty RN node recovers;

[0017] Step S15: Conduct reset verification of the CC node after fault recovery according to whether the 1394B simulation verification software can identify the faulty CC node and re-identify the RN node after the faulty CC node recovers;

[0018] Step S16: Conduct data format verification according to the data format transmitted on the bus checked by the 1394B simulation verification software;

[0019] Step S17: Conduct bit order verification according to whether the data monitored by the 1394B simulation verification software is the data in the data transmission buffer of the CC node;

[0020] Step S18: After the change in the number of Heartbeat frames at the CC node, perform Heartbeat fault verification based on whether the Heartbeats received by the RN nodes checked by the 1394B simulation verification software are consistent.

[0021] Step S19: After the change in the S_VPC value in the load data of the CC node, perform S_VPC fault verification based on whether the S_VPCs received by the RN nodes checked by the 1394B simulation verification software are consistent.

[0022] Preferably, in step S15, by disconnecting the 1394B module of the aircraft management computer, a fault reset is triggered, and by connecting the 1394B module of the aircraft management computer, a reset after fault recovery is triggered.

[0023] Preferably, in step S2, the packet test verification includes:

[0024] Step S21: Perform packet size verification based on whether the packet size recorded by the 1394B simulation verification software exceeds the set value.

[0025] Step S22: Configure the CC node to send several STOF packets, and perform STOF packet format verification based on whether the formats of each field recorded by the 1394B simulation verification software conform to the protocol.

[0026] Step S23: Configure the CC node to send STOF packets at a set frequency, and perform CC node STOF packet sending verification based on whether the period of the actually received STOF packets recorded by the 1394B simulation verification software and the set period are within the allowable accuracy range.

[0027] Step S24: Perform CC node asynchronous stream packet sending verification based on whether the asynchronous stream packet data sent by the CC node can be monitored by the 1394B simulation verification software and whether it is within the configured time window interval.

[0028] Step S25: Perform CC node asynchronous stream packet receiving verification based on whether the asynchronous stream data monitored by the 1394B simulation verification software is consistent with the asynchronous stream data received by the CC node.

[0029] Step S26: Configure the bus to send STOF packets at a set frequency, and perform RN node STOF packet receiving verification based on whether the period of the actually received STOF packets by the RN nodes recorded by the 1394B simulation verification software and the set period are within the allowable accuracy range.

[0030] Step S27: Perform RN node asynchronous stream packet sending verification based on whether the asynchronous stream packet data sent by the RN node can be monitored by the 1394B simulation verification software and whether it is within the configured time window interval.

[0031] Step S28: Verify the reception of asynchronous stream packets by the RN node based on whether the asynchronous stream data monitored by the 1394B simulation verification software is consistent with the asynchronous stream data received by the RN node.

[0032] Step S29: Verify the message transmission and reception between the CC node and multiple RN nodes based on whether the messages between the CC node and each RN node are sent within the configured offset time window, and whether the data content monitored by the 1394B simulation verification software is consistent with the data content configured in the software.

[0033] Preferably, in step S3, the verification of the rate fault mode test includes:

[0034] Step S31: Control the CC node to send the data in the configuration table to the RN node at a set frequency, obtain the transmission rate, and verify the transmission rate based on whether the transmission rate meets the requirements.

[0035] Step S32: Configure the CC node to continuously send a number of STOF packets, and verify the STOF packet rate based on whether the number of data packets continuously exceeding the specified time window is less than the set value.

[0036] Step S33: Inject corresponding faults according to the fault mode, monitor the message content transmitted on the bus with a bus analyzer, and determine whether there are phenomena such as bus reset and no response to verify the fault mode.

[0037] Preferably, in step S32, when the number of data packets continuously exceeding the specified time window is less than 3, the MIL-1394B data bus network passes the STOF packet rate verification.

[0038] Preferably, in step S4, the verification of the redundancy communication test includes:

[0039] Step S41: Verify the autonomous CCDL by loading the configuration table containing the autonomous CCDL and determining whether the CC node can receive the autonomous CCDL data packets.

[0040] Step S42: Verify the non-autonomous CCDL by loading the configuration table containing the non-autonomous CCDL and determining whether the CC node can receive the non-autonomous CCDL data packets.

[0041] The advantages and beneficial effects of this application are:

[0042] (1) A complete test method for the MIL-1394B data bus network of the aircraft management system. On the one hand, the test method covers the cable characteristics, and on the other hand, it covers the system characteristics.

[0043] (2) It is reliable and efficient. Through a systematic test method, the bus network test is standardized, the efficiency of the bus network test of the aircraft management system is improved, and the working cycle is shortened.

[0044] (3) The benefits are significant. This method has been applied to a certain model and achieved good benefits, taking into account the correctness and integrity of the test. Description of the Drawings

[0045] Figure 1 It is a flowchart of a preferred embodiment of the MIL-1394B data bus network test method for the aircraft management system of this application.

[0046] Figure 2 It is a flowchart for implementing the basic characteristics test of the present invention.

[0047] Figure 3 It is a flowchart of the data packet test of the present invention.

[0048] Figure 4 It is a flowchart of the rate / fault mode test of the present invention.

[0049] Figure 5 It is a flowchart of the redundancy communication test of the present invention. Detailed Embodiment

[0050] To make the purpose, technical solution and advantages of the implementation of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below in conjunction with the accompanying drawings in the embodiments of this application. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions from beginning to end. The described embodiments are part of the embodiments of this application, rather than all of the embodiments. The embodiments described below by referring to the accompanying drawings are exemplary and are intended to explain this application, and should not be construed as a limitation of this application. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application. The embodiments of this application will be described in detail below in conjunction with the accompanying drawings.

[0051] This application provides a MIL-1394B data bus network test method for an aircraft management system, as Figure 1 shown, mainly including:

[0052] Step S1: Based on the 1394B simulation verification software, configure the 1394B module of the aircraft management computer as a CC node, and configure the 1394B modules of other simulation devices as RN nodes to conduct basic characteristic test verification including ports, faults, and resets.

[0053] Step S2: Conduct packet experiment verification including STOF packets, asynchronous flow packets, and sending and receiving messages;

[0054] Step S3: Conduct rate fault mode experiment verification including transmission rate and valuation mode;

[0055] Step S4: Based on autonomous CCDL verification and non-autonomous CCDL verification, conduct redundant communication experiment verification.

[0056] In some alternative embodiments, in step S1, as Figure 2 shown, conducting the basic characteristic experiment verification includes:

[0057] S11: Perform physical port connectivity verification, and the experimental steps are:

[0058] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0059] (2) Configure the 1394B modules of other simulation devices as RN nodes;

[0060] (3) Initialize each node;

[0061] (4) Use the node topology function of the simulation software to observe the network topology;

[0062] (5) Check the topology scan result;

[0063] The pass criterion is: The simulation verification software can successfully identify the network topology. Among them, one CC node and the rest are RN nodes, indicating that the ports of these nodes can be normally connected.

[0064] S12: Perform RN node fault reset verification, and the experimental steps are:

[0065] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0066] (2) Configure the 1394B modules of other simulation devices as RN nodes;

[0067] (3) Initialize each node;

[0068] (4) Inject a fault into the RN node (disconnect the 1394B module of the actuator controller) to trigger a fault reset;

[0069] (5) Use the node topology function of the simulation software to observe the network topology;

[0070] (6) Check the topology scan result;

[0071] The pass criterion is as follows: The simulation verification software can successfully identify the topology. When an RN node fails, the node is no longer recognized in the topology graph, indicating that the node triggers a fault reset.

[0072] S13: Perform the reset verification after the RN node fault recovery. The test steps are as follows:

[0073] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node.

[0074] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes.

[0075] (3) Initialize each node.

[0076] (4) Inject a fault into the RN node (disconnect the 1394B module of the actuator controller) to trigger a fault reset.

[0077] (5) Use the node topology function of the simulation software to observe the network topology.

[0078] (6) Restore the faulty RN node (connect the 1394B module of the actuator controller) to trigger a reset after recovery.

[0079] (7) Use the topology function of the simulation software to observe the network topology.

[0080] (8) Check the topology scan result.

[0081] Pass criterion: The simulation verification software can successfully identify the topology. When an RN node fails, the node is no longer recognized in the topology graph. When the RN node recovers after a fault, the node is recognized again in the topology graph, indicating that the node resets after the fault recovery.

[0082] S14: Perform the frequent power-on / off reset verification of the RN node. The test steps are as follows:

[0083] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node.

[0084] (2) Configure the 1394B modules of other simulation devices as RN nodes.

[0085] (3) Initialize each node.

[0086] (4) Frequently power on / off the RN node (continuously disconnect / connect the 1394B module of the actuator controller 10 times at a 5s interval) to trigger a fault reset and a reset after fault recovery.

[0087] (5) Use the topology function of the simulation software to observe the network topology.

[0088] (6) Check the topology scan result;

[0089] Pass criterion: The simulation verification software can successfully identify the topology. When an RN node fails, the node is no longer recognized in the topology graph. When the RN node recovers after the failure, the node is recognized again in the topology graph, indicating that the node supports frequent power-on and power-off reset.

[0090] S15: Perform the reset verification after CC fault recovery. The test steps are as follows:

[0091] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0092] (2) Configure the 1394B modules of other simulation devices as RN nodes;

[0093] (3) Initialize each node;

[0094] (4) Inject a fault into the CC node (disconnect the 1394B module of the aircraft management computer) to trigger a fault reset;

[0095] (5) Recover the CC node fault (connect the 1394B module of the aircraft management computer) to trigger a reset after fault recovery;

[0096] (6) Use the topology function of the simulation software to observe the network topology;

[0097] (7) Check the topology scan result;

[0098] Pass criterion: The simulation verification software can successfully identify the topology. When a CC node fails, the node is no longer recognized in the topology graph. When the CC node recovers after the failure, the node is recognized again in the topology graph, indicating that the node supports the reset after CC node fault recovery.

[0099] S16: Perform the data format verification. The test steps are as follows:

[0100] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0101] (2) Configure the 1394B modules of other simulation devices as RN nodes;

[0102] (3) Initialize each node;

[0103] (4) Load the communication configuration table (generated before the test, the same below);

[0104] (5) Start communication and perform data transmission and reception;

[0105] (6) Use simulation software to check the transceiver results;

[0106] Passing criterion: All data on the bus needs to be arranged in 32-bit format, and all floating-point numbers must conform to the floating-point format.

[0107] S17: Perform bit order verification. The test steps are as follows:

[0108] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0109] (2) Use 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes;

[0110] (3) Initialize each node;

[0111] (4) Load the communication configuration table (the aircraft management computer sends data to the actuator controller);

[0112] (5) Write the data 0x12345678, 0x87654321, 0x11223344, 0x44332211 to the data buffer of the CC node in sequence;

[0113] (6) Check the node status through the simulation software;

[0114] (7) Observe the monitoring window of the 1394B bus simulation software through the simulation software and record the results;

[0115] Passing criterion: The data obtained through monitoring the 1394B bus simulation software is 0x12345678, 0x87654321, 0x11223344, 0x44332211 in sequence.

[0116] S18: Perform Heartbeat fault verification. The test steps are as follows:

[0117] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0118] (2) Use 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes;

[0119] (3) Initialize each node;

[0120] (4) Change the Heartbeat of the data sent by the CC node from incrementing by 1 per frame to incrementing by 2 per frame;

[0121] (5) Check the Heartbeat of the data received by the RN node through the simulation software;

[0122] (6) Record the results through simulation software;

[0123] Passing criterion: Heartbeat faults recorded by the 1394B bus simulation software.

[0124] S19: Perform S_VPC fault verification, and the test steps are as follows:

[0125] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0126] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes;

[0127] (3) Initialize each node;

[0128] (4) In the payload data of the data sent by the CC node, change S_VPC from the normal value to the normal value plus 1;

[0129] (5) Check the S_VPC of the data received by the RN node through the simulation software;

[0130] (6) Record the results through the simulation software;

[0131] Passing criterion: S_VPC faults recorded by the 1394B bus simulation software.

[0132] In some alternative embodiments, as Figure 3 shown, in step S2, performing the data packet test verification includes:

[0133] S21: Perform packet size verification, and the test steps are as follows:

[0134] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0135] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes;

[0136] (3) Initialize each node;

[0137] (4) Load the configuration table;

[0138] (5) Observe the monitoring function window of the simulation software and record the size of the data packet;

[0139] The passing criterion is: in the S100 mode of the transmission bit rate, the largest packet is 512 bytes.

[0140] S22: Perform STOF packet format verification. The test steps are as follows:

[0141] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node.

[0142] (2) Use 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes.

[0143] (3) Initialize each node.

[0144] (4) Load the configuration table and configure the CC node to send 100 STOF packets.

[0145] (5) Observe the recorded results in the monitoring window of the simulation software.

[0146] The pass criterion is that the format of each field of the packet conforms to the protocol, and the 1394B header of the STOF packet is the determined value 0x00281fa0.

[0147] S23: Perform STOF packet sending verification for the CC node. The test steps are as follows:

[0148] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node.

[0149] (2) Use 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes.

[0150] (3) Initialize each node.

[0151] (4) Load the configuration table and configure the CC node to send STOF packets at 20 ms intervals.

[0152] (5) Monitor the period value of the sent STOF packets through the monitoring window of the 1394B bus simulation software.

[0153] The pass criterion: After the node receives the STOF packet, the actual received period of the STOF packet and the set period are within the allowable accuracy range (200 us).

[0154] S24: Perform asynchronous stream packet sending verification for the CC node. The test steps are as follows:

[0155] (1) Use 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node.

[0156] (2) Use 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes.

[0157] (3) Initialize each node;

[0158] (4) Load the configuration table and send asynchronous stream packets;

[0159] (5) Check the content of the sent asynchronous stream packets through the 1394B bus monitoring window;

[0160] (6) Check the time offset of the sent asynchronous stream packets through the 1394B bus monitoring window;

[0161] Qualified criterion: The content of the asynchronous stream packets sent by the CC node is consistent with the content configured in the transmission data storage area, and the message is correctly sent within the configured time window.

[0162] S25: Perform verification on the CC node for receiving asynchronous stream packets. The test steps are as follows:

[0163] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0164] (2) Use the 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes;

[0165] (3) Initialize each node;

[0166] (4) Load the configuration table, and the aircraft management computer receives asynchronous stream packets;

[0167] (5) Read the content of the receiving data storage area of the CC node through the monitoring window of the simulation software;

[0168] (6) Read the receiving time offset of the CC node through the monitoring window of the simulation software;

[0169] Qualified criterion: The receiving time of the message is within the configured time window. The data content in the receiving data storage area of the CC node should be the same as the data monitored by the 1394B bus simulation software, and the receiving message status word does not report an error.

[0170] S26: Perform verification on the RN node for receiving STOF packets. The test steps are as follows:

[0171] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0172] (2) Use the 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes;

[0173] (3) Initialize each node;

[0174] (4) Load the configuration table and configure the bus to send STOF packets at a 20ms cycle;

[0175] (5) The actuator controller receives the STOF;

[0176] (6) Check the cycle value of the sent STOF packet through the 1394B bus simulation software monitoring window;

[0177] Qualified criterion: After the node receives the STOF packet, the cycle of the actually received STOF packet and the set cycle should be the same within the allowable accuracy range (200 us).

[0178] S27: Execute the verification of the RN node sending asynchronous stream packets. The test steps are as follows:

[0179] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0180] (2) Use the 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes;

[0181] (3) Initialize each node;

[0182] (4) Load the configuration table and send asynchronous stream packets;

[0183] (5) Check the content of the sent asynchronous stream packets through the 1394B bus monitoring window;

[0184] (6) Check the time offset of the sent asynchronous stream packets through the 1394B bus monitoring window;

[0185] Qualified criterion: The content of the asynchronous stream packets sent by the RN node is consistent with the content configured in the data storage area for sending, and the message is correctly sent within the configured time window.

[0186] S28: Execute the verification of the RN node receiving asynchronous stream packets. The test steps are as follows:

[0187] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as a CC node;

[0188] (2) Use the 1394B simulation verification software to configure the 1394B module of other simulation devices as RN nodes;

[0189] (3) Initialize each node;

[0190] (4) Load the configuration table and the aircraft management computer receives asynchronous stream packets;

[0191] (5) Read the content of the receive data storage area of the RN node through the simulation software monitoring window;

[0192] (6) Read the reception time offset of the RN node through the monitoring window of the simulation software;

[0193] Qualified criterion: The reception message time is within the configured time window. The data content in the data storage area of the RN node for receiving data should be the same as the data monitored by the 1394B bus simulation software, and the reception message status word has no error.

[0194] S29: Execute the message sending and receiving verification between the CC node and multiple RN nodes. The test steps are as follows:

[0195] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as the CC node;

[0196] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes;

[0197] (3) Initialize each node;

[0198] (4) Load the configuration table (the configuration table for multiple message sending and receiving between the CC node and each RN node has been generated before the test);

[0199] (5) Monitor the asynchronous stream packet offset and message content of the CC node sending and receiving on the bus and record the results;

[0200] (6) Monitor the asynchronous stream packet offset and message content of the RN node sending and receiving on the bus and record the results;

[0201] Qualified criterion: The messages between the CC node and each RN node can be sent out within the configured offset time window. The data content monitored by the bus simulation software is consistent with the data content configured by the software, and the messages received by each node can be correctly stored in the specified storage space, and the reception message status word has no error.

[0202] In some alternative embodiments, as Figure 3 shown, in step S3, performing the data packet test verification includes:

[0203] S31: Transmission rate verification. The test steps are as follows:

[0204] (1) Use the 1394B simulation verification software to configure the 1394B module of the aircraft management computer as the CC node;

[0205] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes;

[0206] (3) 1 CC node (aircraft management computer), 3 RN nodes (actuator controller, air data computer, engine interface unit);

[0207] (4) Initialize each node;

[0208] (5) Load the configuration table (the flight vehicle management computer sends data to the actuator controller, the air data computer, and the engine interface unit at a cycle of 15 ms, and the configuration table has been generated before the test);

[0209] (6) Check the node status through the configuration function window of the simulation software;

[0210] (7) Observe the monitoring function window of the simulation software and record the results;

[0211] The pass criterion is: through the record of the 1394B bus simulation software monitoring window, the transmission rate can be obtained as S100.

[0212] S32: Execute the STOF packet rate verification. The test steps are as follows:

[0213] (1) Use the 1394B simulation verification software to configure the 1394B module of the flight vehicle management computer as a CC node;

[0214] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes;

[0215] (3) Initialize each node;

[0216] (4) Load the configuration table and configure the CC node to send 100 STOF packets;

[0217] (5) Observe the recorded results of the data monitoring;

[0218] The pass criterion is: in the entire data stream, the STOF packets that exceed the specified time window by ±0.1% through the simulation software monitoring window. Among the 100 STOF packets captured by the data monitoring, the number of consecutive packets that exceed the specified time window is less than 3.

[0219] S33: Execute the fault mode verification. The test steps are as follows:

[0220] (1) Use the 1394B simulation verification software to configure the 1394B module of the flight vehicle management computer as a CC node;

[0221] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes;

[0222] (3) Initialize each node;

[0223] (4) Load the configuration table;

[0224] (5) Inject corresponding faults according to the fault modes, monitor the message content transmitted on the bus with a bus analyzer, and record the results.

[0225] Pass criterion: According to the occurred fault modes, observe whether phenomena such as bus reset and no response occur. The detection methods include reading the health status word and observing with simulation software, etc.

[0226] In some alternative embodiments, such as Figure 3 as shown, in step S4, the redundant communication test verification includes:

[0227] S41: Execute the autonomous CCDL verification. The test steps are:

[0228] (1) Use the 1394B simulation verification software to configure the 1394B module of the quadruple-redundancy aircraft management computer as a CC node.

[0229] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes.

[0230] (3) Initialize each node.

[0231] (4) Load the configuration table (the configuration table including the autonomous CCDL has been generated before the test).

[0232] (5) Observe the monitoring function window of the simulation software and record the size of the data packets.

[0233] The pass criterion is: The aircraft management computer can receive the autonomous CCDL data packets.

[0234] S42: Execute the non-autonomous CCDL verification. The test steps are:

[0235] (1) Use the 1394B simulation verification software to configure the 1394B module of the quadruple-redundancy aircraft management computer as a CC node.

[0236] (2) Use the 1394B simulation verification software to configure the 1394B modules of other simulation devices as RN nodes.

[0237] (3) Initialize each node.

[0238] (4) Load the configuration table (the configuration table including the non-autonomous CCDL has been generated before the test).

[0239] (5) Observe the monitoring function window of the simulation software and record the size of the data packets.

[0240] The pass criterion is: The aircraft management computer can receive the non-autonomous CCDL data packets.

[0241] This application designs a test method for the MIL-1394B data bus network of an aircraft management system. Through basic characteristic tests, data packet tests, rate / fault mode tests, and redundancy communication tests, it realizes the systematic tests of the 1394B bus of the aircraft management system, taking into account the correctness and integrity of the tests.

[0242] The above are only specific embodiments of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in this application should be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A test method for the MIL-1394B data bus network of an aircraft management system, characterized in that, Including: Step S1: Based on the 1394B simulation verification software, configure the 1394B module of the aircraft management computer as a CC node, and configure the 1394B modules of other simulation devices as RN nodes to conduct basic characteristic test verifications including ports, faults, and resets; Step S2: Conduct data packet test verifications including STOF packets, asynchronous stream packets, and transmitted and received messages; Step S3: Conduct rate fault mode test verifications including transmission rate and valuation mode; Step S4: Based on autonomous CCDL verification and non-autonomous CCDL verification, conduct redundant communication test verifications; Among them, in step S1, conducting the basic characteristic test verifications includes: Step S11: Conduct physical port connectivity verification according to whether the 1394B simulation verification software can identify the network topology; Step S12: Conduct RN node fault reset verification according to whether the 1394B simulation verification software can identify the faulty RN node; Step S13: Conduct reset verification after RN node fault recovery according to whether the 1394B simulation verification software can re-identify the RN node after the faulty RN node recovers; Step S14: Conduct frequent power-on and power-off reset verification of the RN node according to whether the 1394B simulation verification software can identify the faulty RN node and re-identify the RN node after the faulty RN node recovers; Step S15: Conduct reset verification after CC node fault recovery according to whether the 1394B simulation verification software can identify the faulty CC node and re-identify the RN node after the faulty CC node recovers; In step S2, conducting data packet test verifications includes: Step S21: Conduct data packet size verification according to whether the data packet size recorded by the 1394B simulation verification software exceeds the set value; Step S22: Configure the CC node to send several STOF packets, and conduct STOF packet format verification according to whether the formats of each field recorded by the 1394B simulation verification software conform to the protocol; Step S23: Configure the CC node to send STOF packets at a set frequency, and conduct verification of the CC node sending STOF packets according to whether the actual received STOF packet period recorded by the 1394B simulation verification software and the set period are within the allowed accuracy range; Step S24: Conduct verification of the CC node sending asynchronous stream packets according to whether the 1394B simulation verification software can monitor the asynchronous stream packet data sent by the CC node and whether it is within the configured time window interval; In step S3, conducting rate fault mode test verifications includes: Step S31: Control the CC node to send the data in the configuration table to the RN node at a set frequency, obtain the transmission rate, and conduct transmission rate verification according to whether the transmission rate meets the requirements; Step S32: Configure the CC node to continuously send several STOF packets, and conduct STOF packet rate verification according to whether the number of data packets continuously exceeding the specified time window is less than the set value; Step S33: Inject corresponding faults according to the fault mode, monitor the message content transmitted on the bus with a bus analyzer, and determine whether there are phenomena such as bus reset and no response to conduct fault mode verification.

2. The test method for the MIL-1394B data bus network of the aircraft management system according to claim 1, wherein In step S1, the verification of the basic characteristics test further includes: Step S16: Perform data format verification according to the data format transmitted on the bus checked by the 1394B simulation verification software; Step S17: Perform bit sequence verification according to whether the data monitored by the 1394B simulation verification software is the data in the data buffer sent by the CC node; Step S18: After the number of Heartbeat frames of the CC node changes, perform Heartbeat fault verification according to whether the Heartbeat received by the RN node checked by the 1394B simulation verification software is consistent; Step S19: After the S_VPC value in the load data of the CC node changes, perform S_VPC fault verification according to whether the S_VPC received by the RN node checked by the 1394B simulation verification software is consistent.

3. The test method for the MIL-1394B data bus network of the aircraft management system according to claim 1, wherein In step S15, the fault reset is triggered by disconnecting the 1394B module of the aircraft management computer, and the reset after the fault recovery is triggered by connecting the 1394B module of the aircraft management computer.

4. The test method for the MIL-1394B data bus network of the aircraft management system according to claim 1, wherein, In step S2, the verification of the data packet test further includes: Step S25: Perform CC node receiving asynchronous stream packet verification according to whether the asynchronous stream data monitored by the 1394B simulation verification software is consistent with the asynchronous stream data received by the CC node; Step S26: Configure the bus to send STOF packets at a set frequency, and perform RN node receiving STOF packet verification according to whether the period of the STOF packets actually received by the RN node recorded by the 1394B simulation verification software and the set period are within the allowable accuracy range; Step S27: Perform RN node sending asynchronous stream packet verification according to whether the asynchronous stream packet data sent by the RN node can be monitored by the 1394B simulation verification software and whether it is within the configured time window interval; Step S28: Perform RN node receiving asynchronous stream packet verification according to whether the asynchronous stream data monitored by the 1394B simulation verification software is consistent with the asynchronous stream data received by the RN node; Step S29: Perform CC node and multi-RN node sending and receiving message verification according to whether the messages between the CC node and each RN node are sent within the configured offset time window and according to whether the data content monitored by the 1394B simulation verification software is consistent with the data content configured by the software.

5. The test method for the MIL-1394B data bus network of the aircraft management system according to claim 1, characterized in that In step S32, when the number of data packets continuously exceeding the specified time window is less than 3, the MIL-1394B data bus network passes the STOF packet rate verification.

6. The test method for the MIL-1394B data bus network of the aircraft management system according to claim 1, characterized in that, In step S4, the verification of the redundant communication test includes: Step S41: Perform autonomous CCDL verification by loading a configuration table containing autonomous CCDL and according to whether the CC node can receive autonomous CCDL data packets; Step S42: Perform non-autonomous CCDL verification by loading a configuration table containing non-autonomous CCDL and according to whether the CC node can receive non-autonomous CCDL data packets.

Images