Airborne execution unit batch test method

Through hardware line multiplexing and automated testing processes, the problem of insufficient hardware resources when multiple airborne unit tests are solved in the existing technology, efficient testing of multiple devices is achieved, and testing efficiency is improved.

CN119322711APending Publication Date: 2025-01-17TIANJIN JINHANG COMP TECH RES INST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411443144.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-16
Publication Date
2025-01-17

AI Technical Summary

Technical Problem

When testing multiple airborne execution units, the prior art has a lot of hardware wiring, resulting in insufficient resources of the test equipment and high production pressure, and low testing work efficiency.

Method used

A batch testing method for airborne execution units was designed. Through hardware line multiplexing and automated testing software processes, simultaneous testing of multiple airborne execution units is realized, including hardware line design and testing software execution process, and power supply and 1553B are optimized. The wiring method of bus, discrete signals and straight-through lines is used to reduce the number of hardware wiring using the output method of 1 to 6, and an efficient testing process is formulated.

Benefits of technology

It greatly reduces the hardware resource requirements of test equipment, reduces the testing workload, improves the testing efficiency of mass production, and realizes efficient testing of multiple airborne execution units.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119322711A_ABST
    Figure CN119322711A_ABST
Patent Text Reader

Abstract

The invention relates to an airborne execution unit batch test method, and belongs to the technical field of electronics. According to the method, existing hardware resources of certain test equipment are fully excavated and utilized, multiple output excitation and input response lines needing to be used in the test process are reasonably reused in the aspect of hardware, and a high-automation and full-coverage test process is provided in the aspect of software. On one hand, one test device can test a plurality of execution units at the same time, and the production and use requirements of the test device are reduced; and on the other hand, a large amount of repeated test work in the delivery process is reduced, and the test work efficiency of batch production of equipment is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention belongs to the field of electronic technology, and in particular relates to a batch testing method for airborne execution units. Background Art

[0002] The airborne execution unit is an airborne device responsible for completing information conversion between bus signals and discrete signals. Its interface is mainly based on the 1553B bus interface, discrete input optocoupler and output relay. The function of a single device is relatively simple, and the number of signals tested is small. The total number of devices delivered in a batch is large, and during the delivery test, the workload of testing the execution unit is large.

[0003] It is known that a single device of an airborne execution unit requires the test equipment to provide interface characteristics and line quantities, which are as follows: a to f, a total of 6 groups (input and output directions are for the test equipment):

[0004] Group a: power supply signal, output, 28V (valid) / disconnected (invalid), one of which is used for the working power of the onboard execution unit, and two are used for the signal power of the onboard execution unit control output;

[0005] Group b: 1553B bus, input / output, as bus BC, 1 A / B dual channel;

[0006] Group C: Discrete electrical signal, input, 28V (valid) / disconnect (invalid), 4 channels;

[0007] Group d: discrete state signal, output, ground (valid) / disconnect (invalid), 7 channels;

[0008] Group e: through-line discrete electrical signal, output, ground (valid) / disconnect (invalid), 6 channels;

[0009] Group f: DC line discrete electrical signal, input, ground (valid) / disconnect (invalid), 6 channels;

[0010] like Figure 1 As shown, the existing test equipment contains a power board, a mainboard, a 1553 board and a discrete board. The power board is responsible for converting 220V AC power into 28V and 5V DC power. The 5V power is used as the working power of other boards, and the 28V power is used as the power supply for the equipment output by the test equipment and the 28V signal power. The test software runs in the mainboard and is displayed on the human-computer interaction display screen. At the same time, the mainboard communicates with the 1553 board and the discrete board through the local bus. Figures 2 to 5 As shown in the sequence, the test equipment needs to meet the following four test requirements for a single airborne execution unit:

[0011] 1. The test equipment software controls the internal 28V relay to output a 28V power supply signal to provide 28V working power and signal power to the onboard execution unit; the 28V working power is used for the power required for the onboard execution unit's own work, and the signal power is used for the onboard execution unit to output discrete signal power.

[0012] 2. The test equipment provides a ground / open signal to the onboard execution unit, which converts it into a 1553B signal and feeds it back to the test equipment through the 1553B bus; the test equipment receives the 1553B bus data bit to determine whether the conversion function of the onboard execution unit is normal.

[0013] 3. The test equipment sends control data bits to the onboard execution unit through the 1553B bus, and the onboard execution unit converts it into a 28V / disconnect signal (discrete quantity) and feeds it back to the test equipment; the test equipment determines whether the conversion function of the onboard execution unit is normal by receiving the 28V / disconnect signal.

[0014] 4. The test equipment provides a ground / open signal to the airborne execution unit, which is transmitted back to the test equipment through a through line inside the airborne execution unit; the test equipment determines whether the through line of the airborne execution unit is normal by turning on and off the optical coupler.

[0015] From the above number of lines, we can know that a single airborne execution unit requires 3+7+4+6+6=26 hardware connections provided by the test equipment. If 6 airborne execution units are tested at the same time, at least 156 hardware connections are required. This exceeds the hardware resources of existing test equipment and puts heavy pressure on the design and production of test cables.

[0016] Therefore, it is necessary to design a test method that can simultaneously test up to 6 airborne execution units based on the above-mentioned existing technical conditions and foundations, so as to reduce the hardware and software burden of the testing work and improve the efficiency of the testing work. Summary of the invention

[0017] 1. Technical issues to be resolved

[0018] The technical problem to be solved by the present invention is: to design a test method that can test up to 6 airborne execution units at the same time, specifically including a hardware line multiplexing scheme and a test software execution process, so as to reduce the hardware and software burden of the test work and improve the test work efficiency.

[0019] (II) Technical solution

[0020] In order to solve the above technical problems, the present invention provides an airborne execution unit batch testing method, which includes hardware circuit design and test software execution process design;

[0021] It is known that a single device of an airborne execution unit requires the test equipment to provide a total of 6 groups of signals from a to f. The hardware circuit design method includes the following design of the 6 groups of signals from a to f:

[0022] Group a: power supply signal, 28V / disconnected, of which 1 is used for working power of the airborne execution unit, and 2 are used for signal power of the airborne execution unit control output; for the 3 power supply signals of each airborne execution unit, 1 is for working power, 6 airborne execution units are powered separately, and the remaining 2 are signal power; the test equipment uses a 1-to-6 output mode to provide the remaining 2 power supplies to the 6 airborne execution units at the same time;

[0023] Group B: For the 1553B bus, the test equipment is used as bus BC, and the six airborne execution units are used as RT. Both the test equipment and the airborne execution units have dual channels A and B. They can be connected normally through the coupler to complete the test;

[0024] Group C: 4 discrete 28V / disconnect signals returned from each onboard actuator and input to the test equipment. The test equipment can only provide input lines one-to-one;

[0025] Group d: 7 discrete ground / disconnect signals output to each airborne execution unit. The test equipment uses a 1-to-6 output mode to output these 7 signals to 6 airborne execution units at the same time. The same signal output to the 6 airborne execution units is valid / invalid at the same time, and different signals output to the same airborne execution unit are independent of each other. Therefore, the test equipment needs to provide a total of 7 discrete ground / disconnect signals.

[0026] Group e: discrete ground / disconnect signals of 6 test through-lines output to each airborne execution unit. The test equipment uses a 1-to-6 output mode to output these 6 signals to 6 airborne execution units at the same time; therefore, the test equipment needs to provide a total of 6 discrete ground / disconnect signals;

[0027] Group f: 6 direct lines from each onboard execution unit to the test equipment. The test equipment can only provide one-to-one input lines;

[0028] The test software execution process design is to develop a process for the test equipment to test the 6 onboard execution units based on the designed hardware circuit.

[0029] Preferably, group d is the test equipment for the onboard execution unit to convert discrete quantity signals into 1553B bus data for transmission back, and group e is only used for the internal through-line test of the onboard execution unit.

[0030] Preferably, it is assumed that the test device provides 6 test interfaces, which are numbered 1 to 6, and each test interface can be arbitrarily connected to or not connected to the onboard execution unit; when the user starts testing on the test device, the test process is executed in the following order, wherein the test operations of test interfaces 1 to 6 are completely consistent and are uniformly replaced by X:

[0031] 1) Through the test interface X, the state of the 7 discrete ground / disconnect signals of group d is output to each airborne execution unit as ground, and the state of the 1 discrete ground / disconnect signal of group e is output as ground, that is, there is a valid signal output to the airborne execution unit in group e;

[0032] 2) Determine through test interface X whether the discrete ground / disconnection signal corresponding to the signal in group e in group f returned from the airborne execution unit is ground; if the ground of a certain interface is valid, it means that the test interface is normally connected to an airborne execution unit, and continue to execute step 3); if the ground is invalid, it means that the test interface is not connected to the airborne execution unit, and the test process is terminated;

[0033] 3) For the valid test interface X, first open the two signal circuits of group a signal to it; after an interval of 1 second, open the working power of the onboard execution unit of group a signal, and start the timer at the same time;

[0034] 4) When the timer reaches 200ms, determine whether the c group of 4 28V / open signals returned by the test interface X from the onboard execution unit are valid. If valid, it means that the onboard execution unit has a signal output failure after power-on. The fault information is recorded and the subsequent test process is terminated; if invalid, proceed to the next step;

[0035] 5) When the timer reaches 1s, a handshake message is sent to all normal airborne execution units through the A channel via the 1553B bus, and the response of the airborne execution unit is waited; the handshake message is sent 5 times in succession, with an interval of 1s each time; if the airborne execution unit responds during this period, the software version number of the airborne execution unit is extracted from the response information and displayed, the bus data corresponding to the d group signal is extracted and the A channel is considered normal, and the subsequent status judgment is performed; if there is no response during this period, it is judged that the airborne execution unit under the test interface X has a bus communication fault, the fault information is recorded and the subsequent test process is terminated; after judging that the bus A channel is normal, a handshake message is sent through the B channel again, and 50ms is waited to judge whether the airborne execution unit has a response, and the judgment is only made once; if there is a response, the B channel is recorded as normal, otherwise the B channel fault is recorded and the next step is executed;

[0036] 6) Determine whether the 7 bus data bits corresponding to the 7 discrete ground / disconnect signals of group d are all 1, that is, all valid. If all are valid, it means that the airborne execution unit correctly converts the d discrete ground / disconnect signals into the corresponding 1553B bus data and reports it to the test equipment; otherwise, it means that there is a conversion failure between the airborne execution unit and the d discrete signals corresponding to the invalid data bits. Record the fault information and proceed to the next step;

[0037] 7) Output one of the 7 discrete ground / disconnect signals of group d as disconnected, and extract the 7 data bits corresponding to the group d signal from the data received by the 1553B bus; determine whether the response signal corresponding to the input stimulus of the onboard execution unit in the 7 data bits is 0, that is, invalid, invalid represents normal; valid represents fault, record the fault information and then execute the next step;

[0038] 8) Send 4 bus data bits corresponding to the 4 28V / open discrete signals of group c to the test interface X of the airborne execution unit through the 1553B bus. If one of the 4 bus data bits is 1, wait for 50ms to determine whether the response signal corresponding to the input stimulus of the airborne execution unit among the 4 signals of group c returned by the airborne execution unit to the test device is 28V valid; if it is valid, it means that the airborne execution unit has correctly converted the bus signal into the corresponding 28V discrete signal; if a signal is invalid, it means that the conversion function of the airborne execution unit of the signal is faulty, and the fault information is recorded and the next step is continued;

[0039] 9) Send 4 bus data bits corresponding to the 4 28V / open discrete signals of group c to the test interface X of the airborne execution unit through the 1553B bus, and one of the 4 bus data bits is 0: wait for 50ms to determine whether the response signal corresponding to the input stimulus of the airborne execution unit among the 4 signals of group c returned by the airborne execution unit to the test equipment is 28V valid; if it is valid, it means that the airborne execution unit has correctly converted the bus signal into the corresponding 28V discrete signal; if a signal is invalid, it means that the conversion function of the airborne execution unit of the signal is faulty, record the fault information and proceed to the next step.

[0040] 10) Determine whether the remaining 5 ground / open signal states of group f are all invalid. Invalid means normal; valid means fault. Record the fault information and proceed to the next step.

[0041] 11) Output the remaining 5 ground / open signals of group e to the airborne execution unit test interface X as ground valid, and then determine whether the corresponding 5 input signals in group f are all ground valid; if they are all valid, it means that the direct-through connection inside the airborne execution unit is normal; if a signal is invalid, it means that the corresponding direct-through connection inside the airborne execution unit is abnormal, record the fault information, and the test operation ends.

[0042] Preferably, after the test operation is completed, the onboard execution unit is powered on and the previous signal test results are displayed; at the same time, the 4-way 28V power supply of group C is periodically checked to see if it is valid. If it becomes valid, it means that the onboard execution unit executes the 28V signal power output uncontrollably, and there is a functional abnormality. The fault information is recorded and displayed; after the user stops the test, all power supplies are disconnected, the test result file is generated and the test is exited.

[0043] Preferably, step 7) is a test of converting discrete quantities of the onboard execution unit to 1553B bus quantities, steps 8) and 9) are tests of converting 1553B bus quantities of the onboard execution unit to discrete quantities, and step 11) is a test of the through-line function of the onboard execution unit; in order to reliably test the possible hardware output line adhesion and short circuit conditions of the onboard execution unit, it is necessary to set the output excitation to only 1 valid at a time, and the rest are invalid 0, and at the same time, determine whether the corresponding response has only 1 valid path and the rest are invalid; if there is asynchrony, it means that there is adhesion and short circuit in the hardware.

[0044] Preferably, for steps 7) and 11), during the test process, after a certain signal is output effectively, effective excitation will be output simultaneously to up to 6 airborne execution units, that is, the responses of up to 6 airborne execution units can be judged at the same time without having to test each airborne execution unit separately.

[0045] Preferably, the onboard execution unit is an onboard device responsible for completing information conversion between bus signals and discrete quantity signals.

[0046] The present invention also provides a system for implementing the method.

[0047] The invention also provides an application of the method in the field of electronic technology.

[0048] The invention also provides an application of the system in the field of electronic technology.

[0049] (III) Beneficial effects

[0050] The present invention fully exploits the existing hardware resources of a certain test equipment, reasonably reuses multiple output excitation and input response lines needed in the test process in terms of hardware, and proposes a highly automated, full-coverage test process in terms of software. On the one hand, it can enable one test equipment to complete the test of multiple execution units at the same time, reducing the production and use requirements of the test equipment; on the other hand, it reduces the testing work of a large number of repeated operations in the delivery process, and improves the test work efficiency of mass production of equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 It is the internal structure diagram of the existing test equipment;

[0052] Figures 2 to 5 They are schematic diagrams of hardware connection relationships for achieving different test requirements when the current test equipment performs unit tests on a single airborne unit;

[0053] Figure 6 It is a schematic diagram of the output multiplexing circuit of the hardware circuit multiplexing solution implemented by the test method of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, content and advantages of the present invention more clear, the specific implementation methods of the present invention are further described in detail below in conjunction with the drawings and examples.

[0055] The present invention proposes an airborne execution unit batch testing method by combining software technology and hardware technology, which is used to efficiently complete the airborne execution unit batch testing work.

[0056] 1. Hardware line multiplexing solution

[0057] It is known that a single device of an airborne execution unit requires the test device to provide a total of 6 groups of signals from a to f (the input and output directions are for the test device). The following describes the multiplexing method for the 6 groups of signals from a to f:

[0058] Group a: power supply signal, 28V (valid) / disconnected (invalid), of which 1 is used for the working power of the airborne execution unit, and 2 are used for the signal power of the airborne execution unit control output; for the 3 power supply signals of each airborne execution unit, 1 is for working power, and the 6 airborne execution units must be powered separately, and the remaining 2 are signal power, which belongs to low power use or small load output (used to drive optocouplers) inside the airborne execution unit. Therefore, the test equipment can use the 1-to-6 output method to provide the remaining 2 power supplies to the 6 airborne execution units at the same time. Therefore, there are 6+2=8 power supply lines in total.

[0059] Group b: For the 1553B bus, the test equipment acts as bus BC, and the six airborne execution units act as RT. Both the test equipment and the airborne execution units have dual channels A and B, and they can complete the test by connecting them normally through a coupler.

[0060] Group C: For the 4 discrete 28V / disconnect signals returned from each onboard execution unit and input to the test equipment, the test equipment can only provide one-to-one input lines. Because during the test, the status of these 4*6=24 signals must be tested independently, and the hardware line adhesion and short circuit must be detected, so they cannot be reused.

[0061] Group d: For the 7 discrete ground / disconnect signals output to each airborne execution unit, the test equipment uses a 1-to-6 output method to output these 7 signals to the 6 airborne execution units at the same time; the same signal output to the 6 airborne execution units is valid / invalid at the same time, and different signals output to the same airborne execution unit are independent of each other; therefore, the test equipment needs to provide a total of 7 discrete ground / disconnect signals.

[0062] Group e: For the discrete ground / disconnect signals of the 6 test direct lines output to each airborne execution unit, the test equipment uses a 1-to-6 output method to simultaneously output these 6 signals to the 6 airborne execution units; therefore, the test equipment needs to provide a total of 6 output discrete ground / disconnect signals; the difference between this group and group d is that group d is an airborne execution unit that converts discrete quantity signals into 1553B bus data return test equipment, while group e is only used for internal direct line testing of airborne execution units.

[0063] Group f: For the 6 direct lines (discretely / disconnected) returned from each onboard execution unit and input to the test equipment, the test equipment can only provide one-to-one input lines. Because during the test, the status of these 6*6=36 signals must be tested independently, and the hardware line adhesion and short circuit must be detected, so they cannot be reused.

[0064] So the output multiplexing circuit schematic diagram is shown in Figure 6 shown.

[0065] In summary, the total number of hardware lines that the test equipment needs to provide is: 8+24+7+6+36=81, which is nearly half less than the originally planned 156, greatly improving the utilization of hardware resources.

[0066] 2. Test software execution process

[0067] Next, based on the designed hardware circuit, the software flow of the test equipment to test 6 airborne execution units is formulated. Assume that the test equipment provides 6 test interfaces, numbered 1 to 6, and each test interface can be connected or not connected to an airborne execution unit at will.

[0068] When the user clicks Start Test on the test equipment software interface, the test software executes in the following order, where the test operations of test interfaces 1 to 6 are exactly the same and are uniformly replaced by X:

[0069] 1) Through the test interface X, the state of the 7 discrete ground / disconnect signals of group d is output to each airborne execution unit as ground (valid), and the state of the 1 discrete ground / disconnect signal of group e is ground (valid), that is, there is a valid signal output to the airborne execution unit in group e;

[0070] 2) Determine through test interface X whether the discrete ground / disconnection signal corresponding to the signal in group e in group f returned from the airborne execution unit is ground (valid); if the ground of a certain interface is valid, it means that the test interface is normally connected to an airborne execution unit, and continue to execute step 3); if the ground is invalid, it means that the test interface is not connected to the airborne execution unit, and the test process is terminated;

[0071] 3) For the valid test interface X, the test software first opens the two signal circuits of group a to it; after an interval of 1 second, it opens the working power of the onboard execution unit of group a signal, and starts the timer at the same time;

[0072] 4) When the timer reaches 200ms, determine whether the c group of 4 28V / open signals returned by the test interface X from the onboard execution unit are valid. If valid, it means that the onboard execution unit has a signal output failure after power-on. The fault information is recorded and the subsequent test process is terminated; if invalid, proceed to the next step;

[0073] 5) When the timer reaches 1s, the test software sends a handshake message to all normal onboard execution units through the A channel via the 1553B bus, and waits for the response of the onboard execution unit; the handshake message is sent 5 times in succession, with an interval of 1s each time; if the onboard execution unit responds during this period, the onboard execution unit software version number is extracted from the response information and displayed, the bus data corresponding to the d group signal is extracted and the A channel is considered normal, and the subsequent status judgment is performed; if there is no response during this period, it is judged that the onboard execution unit under the test interface X has a bus communication fault, the fault information is recorded and the subsequent test process is terminated; after judging that the bus A channel is normal, the test software sends a handshake message through the B channel again, and waits 50ms to judge whether the onboard execution unit has a response, and only judges once; if there is a response, the B channel is recorded as normal, otherwise the B channel fault is recorded and the next step is executed;

[0074] 6) Determine whether the 7 bus data bits corresponding to the 7 discrete ground / disconnect signals of group d are all 1, that is, all valid. If all are valid, it means that the onboard execution unit correctly converts the d discrete ground / disconnect signals into the corresponding 1553B bus data and reports it to the test equipment; otherwise, it means that there is a conversion failure between the onboard execution unit and the d discrete signals corresponding to the invalid data bits. The test software records the failure information and proceeds to the next step;

[0075] 7) The test software outputs one of the 7 discrete ground / disconnect signals of group d as disconnected, and extracts the 7 data bits corresponding to the group d signal from the data received by the 1553B bus; determines whether the response signal corresponding to the input stimulus of the onboard execution unit in the 7 data bits is 0, that is, invalid, invalid represents normal; valid represents fault, and executes the next step after recording the fault information (the processing method is the same as step 6);

[0076] 8) The test software sends 4 bus data bits corresponding to the 4 28V / open discrete signals of group c to the test interface X of the airborne execution unit through the 1553B bus. If one of the 4 bus data bits is 1 (indicating valid), then after waiting for 50ms, it is determined whether the response signal corresponding to the input stimulus of the airborne execution unit among the 4 signals of group c returned by the airborne execution unit to the test device is 28V valid; if it is valid, it means that the airborne execution unit has correctly converted the bus signal into the corresponding 28V discrete signal; if a signal is invalid, it means that the conversion function of the airborne execution unit of the signal is faulty, and the test software records the fault information and proceeds to the next step;

[0077] 9) The test software sends 4 bus data bits corresponding to the 4 28V / open discrete signals of group c to the test interface X of the airborne execution unit through the 1553B bus. One of the 4 bus data bits is 0 (indicating invalid). The subsequent specific operations are the same as step 8): After waiting for 50ms, it is determined whether the response signal corresponding to the input stimulus of the airborne execution unit among the 4 signals of group c returned by the airborne execution unit to the test equipment is 28V valid; if it is valid, it means that the airborne execution unit has correctly converted the bus signal into the corresponding 28V discrete signal; if a signal is invalid, it means that the conversion function of the airborne execution unit of the signal is faulty, and the test software records the fault information and proceeds to the next step.

[0078] 10) The test software determines whether the remaining 5 ground / open signal states of group f are all invalid. Invalid means normal; valid means fault. Record the fault information and proceed to the next step.

[0079] 11) The test software outputs the remaining 5 ground / open signals of group e to the airborne execution unit test interface X as ground valid, and then determines whether the 5 corresponding input signals in group f are all ground valid; if they are all valid, it means that the direct line connection inside the airborne execution unit is normal; if a signal is invalid, it means that the corresponding direct line connection inside the airborne execution unit is abnormal, the fault information is recorded, and the test operation ends;

[0080] 12) After the above test operation is completed, the test software continues to supply power to the onboard execution unit and displays the previous signal test results (including normal and fault information) on the interface; at the same time, it periodically checks whether the 4-way 28V power of group C is valid. If it becomes valid, it means that the onboard execution unit executes the 28V signal power output uncontrollably, and there is a functional abnormality. The fault information is recorded and displayed; after the user stops the test, the test software disconnects all power supplies, generates a test result file and exits.

[0081] Among them, step 7) is a test of the onboard execution unit discrete quantity to 1553B bus quantity, steps 8) and 9) are the onboard execution unit 1553B bus quantity to discrete quantity test, and step 11) is the through line function test of the onboard execution unit. What they have in common is that there is a one-to-one correspondence between the stimulus and the response signal. In order to reliably test the possible hardware output line adhesion and short circuit of the onboard execution unit, the test software needs to set the output stimulus to only 1 channel valid each time, and the rest are invalid 0, and at the same time determine whether the corresponding response is only valid for the corresponding 1 channel, and the rest are invalid; if there is asynchrony, it means that there is a adhesion short circuit in the hardware.

[0082] For steps 7) and 11), since the hardware design has adopted a 1-to-6 multiplexing method for hardware lines, during the test process, after the test software outputs a certain signal effectively, it will simultaneously output effective stimulation to up to 6 airborne execution units. That is, the test software can simultaneously determine the responses of up to 6 airborne execution units without having to test each airborne execution unit separately, thereby saving test time.

[0083] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the technical principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for batch testing of airborne execution units, characterized in that: The method includes hardware circuit design and test software execution process design; It is known that a single device of an airborne execution unit requires the test equipment to provide a total of 6 groups of signals from a to f. The hardware circuit design method includes the following design of the 6 groups of signals from a to f: Group a: power supply signal, 28V / disconnected, of which 1 is used for working power of the airborne execution unit, and 2 are used for signal power of the airborne execution unit control output; for the 3 power supply signals of each airborne execution unit, 1 is for working power, 6 airborne execution units are powered separately, and the remaining 2 are signal power; the test equipment uses a 1-to-6 output mode to provide the remaining 2 power supplies to the 6 airborne execution units at the same time; Group B: For the 1553B bus, the test equipment is used as bus BC, and the six airborne execution units are used as RT. Both the test equipment and the airborne execution units have dual channels A and B. They can be connected normally through the coupler to complete the test; Group C: 4 discrete 28V / disconnect signals returned from each onboard actuator and input to the test equipment. The test equipment can only provide input lines one-to-one; Group d: 7 discrete ground / disconnect signals output to each airborne execution unit. The test equipment uses a 1-to-6 output mode to output these 7 signals to 6 airborne execution units at the same time. The same signal output to the 6 airborne execution units is valid / invalid at the same time, and different signals output to the same airborne execution unit are independent of each other. Therefore, the test equipment needs to provide a total of 7 discrete ground / disconnect signals. Group e: discrete ground / disconnect signals of 6 test through-lines output to each airborne execution unit. The test equipment uses a 1-to-6 output mode to output these 6 signals to 6 airborne execution units at the same time; therefore, the test equipment needs to provide a total of 6 discrete ground / disconnect signals; Group f: 6 direct lines from each onboard execution unit to the test equipment. The test equipment can only provide one-to-one input lines; The test software execution process design is to develop a process for the test equipment to test the 6 onboard execution units based on the designed hardware circuit.

2. The method according to claim 1, characterized in that Group d is the test equipment for the airborne execution unit to convert discrete quantity signals into 1553B bus data for transmission back, and group e is only used for the internal through-line test of the airborne execution unit.

3. The method according to claim 1, characterized in that Assume that the test equipment provides 6 test interfaces, numbered 1 to 6, and each test interface can be connected or not connected to the onboard execution unit at will; when the user starts testing on the test equipment, the test process is executed in the following order, where the test operations of test interfaces 1 to 6 are completely the same and are uniformly replaced by X: 1) Through the test interface X, the state of the 7 discrete ground / disconnect signals of group d is output to each airborne execution unit as ground, and the state of the 1 discrete ground / disconnect signal of group e is output as ground, that is, there is a valid signal output to the airborne execution unit in group e; 2) Determine through test interface X whether the discrete ground / disconnection signal corresponding to the signal in group e in group f returned from the airborne execution unit is ground; if the ground of a certain interface is valid, it means that the test interface is normally connected to an airborne execution unit, and continue to execute step 3); if the ground is invalid, it means that the test interface is not connected to the airborne execution unit, and the test process is terminated; 3) For the valid test interface X, first open the two signal circuits of group a signal to it; after an interval of 1 second, open the working power of the onboard execution unit of group a signal, and start the timer at the same time; 4) When the timer reaches 200ms, determine whether the c group of 4 28V / open signals returned by the test interface X from the onboard execution unit are valid. If valid, it means that the onboard execution unit has a signal output failure after power-on. The fault information is recorded and the subsequent test process is terminated; If invalid, proceed to the next step; 5) When the timer reaches 1s, a handshake message is sent to all normal airborne execution units through the 1553B bus via the A channel, and the response of the airborne execution unit is waited for; The handshake message is sent down 5 times in succession, each time at an interval of 1s; if the airborne execution unit responds during this period, the software version number of the airborne execution unit is extracted from the response information and displayed, the bus data corresponding to the group d signal is extracted and the A channel is considered normal, and the subsequent status judgment is performed; if there is no response during this period, it is judged that the airborne execution unit under the test interface X has a bus communication fault, the fault information is recorded and the subsequent test process is terminated; after judging that the bus A channel is normal, the handshake message is sent down through the B channel again, and wait for 50ms to judge whether the airborne execution unit has a response, and the judgment is only made once; if there is a response, the B channel is recorded as normal, otherwise the B channel fault is recorded and the next step is performed; 6) Determine whether the 7 bus data bits corresponding to the 7 discrete ground / disconnect signals of group d are all 1, that is, all valid. If all are valid, it means that the airborne execution unit correctly converts the d discrete ground / disconnect signals into the corresponding 1553B bus data and reports it to the test equipment; otherwise, it means that there is a conversion failure between the airborne execution unit and the d discrete signals corresponding to the invalid data bits. Record the fault information and proceed to the next step; 7) Output one of the 7 discrete ground / disconnect signals of group d as disconnected, and extract the 7 data bits corresponding to the group d signals from the data received by the 1553B bus; determine whether the response signal corresponding to the input stimulus of the onboard execution unit in the 7 data bits is 0, that is, invalid, and invalid represents normal; Valid indicates a fault, and the next step is executed after recording the fault information; 8) Send 4 bus data bits corresponding to the 4 28V / open discrete signals of group c to the test interface X of the airborne execution unit through the 1553B bus. If one of the 4 bus data bits is 1, wait for 50ms to determine whether the response signal corresponding to the input stimulus of the airborne execution unit among the 4 signals of group c returned by the airborne execution unit to the test device is 28V valid; if it is valid, it means that the airborne execution unit has correctly converted the bus signal into the corresponding 28V discrete signal; if a signal is invalid, it means that the conversion function of the airborne execution unit of the signal is faulty, and the fault information is recorded and the next step is continued; 9) Send 4 bus data bits corresponding to the 4 28V / open discrete signals of group c to the test interface X of the airborne execution unit through the 1553B bus, and one of the 4 bus data bits is 0: wait for 50ms to determine whether the response signal corresponding to the input stimulus of the airborne execution unit among the 4 signals of group c returned by the airborne execution unit to the test equipment is 28V valid; if it is valid, it means that the airborne execution unit has correctly converted the bus signal into the corresponding 28V discrete signal; if a signal is invalid, it means that the conversion function of the airborne execution unit of the signal is faulty, record the fault information and proceed to the next step. 10) Determine whether the remaining 5 ground / open signal states of group f are all invalid, and invalid means normal; Valid means fault, record the fault information and proceed to the next step; 11) Output the remaining 5 ground / open signals of group e to the airborne execution unit test interface X as ground valid, and then determine whether the 5 corresponding input signals in group f are all ground valid; if all are valid, it means that the through line connection inside the airborne execution unit is normal; If a signal is invalid, it means that the corresponding direct line connection inside the onboard execution unit is abnormal, the fault information is recorded, and the test operation ends.

4. The method according to claim 3, characterized in that After the test operation is completed, the onboard execution unit is powered on and the previous signal test results are displayed; at the same time, the 4-way 28V power of group C is periodically checked to see if it is valid. If it becomes valid, it means that the onboard execution unit is not controlled to execute the 28V signal power output, and there is a functional abnormality. The fault information is recorded and displayed; After the user stops the test, all power supplies are disconnected, the test result file is generated and the system exits.

5. The method according to claim 3, characterized in that Step 7) is a test of the onboard execution unit discrete quantity to 1553B bus quantity, steps 8) and 9) are the onboard execution unit 1553B bus quantity to discrete quantity test, and step 11) is the onboard execution unit through line function test; in order to reliably test the possible hardware output line adhesion short circuit of the onboard execution unit, it is necessary to set the output excitation to only one channel valid each time, and the rest are invalid 0, and at the same time determine whether the corresponding response is only valid for the corresponding one channel, and the rest are invalid; If there is a lack of synchronization, it means there is a sticky short circuit in the hardware.

6. The method according to claim 3, characterized in that For steps 7) and 11), during the test process, after a certain signal is output effectively, effective stimulation will be output to up to 6 airborne execution units at the same time, that is, the response of feedback from up to 6 airborne execution units can be judged at the same time without having to test each airborne execution unit separately.

7. The method according to claim 1, characterized in that The airborne execution unit is an airborne device responsible for completing information conversion between bus signals and discrete quantity signals.

8. A system for implementing the method according to any one of claims 1 to 7.

9. Application of the method according to any one of claims 1 to 7 in the field of electronic technology.

10. Application of the system according to claim 8 in the field of electronic technology.