CN113010358A - LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device - Google Patents

LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device Download PDF

Info

Publication number
CN113010358A
CN113010358A CN202110284696.5A CN202110284696A CN113010358A CN 113010358 A CN113010358 A CN 113010358A CN 202110284696 A CN202110284696 A CN 202110284696A CN 113010358 A CN113010358 A CN 113010358A
Authority
CN
China
Prior art keywords
test
ltpb
bus
script
rule
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110284696.5A
Other languages
Chinese (zh)
Other versions
CN113010358B (en
Inventor
路辉
马雨忻
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beihang University
Original Assignee
Beihang University
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beihang University filed Critical Beihang University
Priority to CN202110284696.5A priority Critical patent/CN113010358B/en
Publication of CN113010358A publication Critical patent/CN113010358A/en
Application granted granted Critical
Publication of CN113010358B publication Critical patent/CN113010358B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
    • G06F11/221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test buses, lines or interfaces, e.g. stuck-at or open line faults
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2273—Test methods

Abstract

The invention discloses an LTPB bus detection device applied to an avionics system and a method for testing a flow description language thereof; the test description language model (500) is installed in the computer (400) to form an LTPB bus detection device; the test description language model (500) is composed of a description language constraint rule customizing unit (200) and an XML test script unit (300). The test description language model (500) is based on an xml format and combined with the characteristics of an LTPB bus to formulate a test action set, a test index set, a test instrument set, a test control statement set, a signal attribute set and a description object set, and completes the test of the LTPB bus in an avionic system according to the test specification standard of each test item of the LTPB bus and four rules and four rule scripts formulated by the invention to form an executable code which can completely represent the test flow of a linear token data bus.

Description

LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device
Technical Field
The present invention relates to a description language method for token bus, and more particularly, to an LTPB bus device for detecting an LTPB bus serving as an avionics system, and a test flow description language method (LTPB-TDL method for short) applied to the LTPB bus.
Background
Avionics systems are the "brain" and "neural center" of aircraft, and have become the world-recognized most complex real-time system as combat environments have become complicated and aircraft mission missions have expanded. Mission requirements and advances in electronic information technology have led to avionics system architectures undergoing four generations of development. The current advanced avionics systems typically employ an integrated modular avionics system architecture and are driven by time-triggered technologies to evolve towards distributed architectures. The category of avionics systems includes all the electronics-related systems and devices that support an aircraft in completing its mission. Early avionics was primarily concerned with systems that supported aircraft takeoff, landing, guidance and navigation, and communication systems where aircraft members contacted the ground. With the development and maturity of aviation technology, airplanes gradually undertake a plurality of tasks such as transportation, reconnaissance, early warning, air combat, striking and the like. In order to improve the task capacity, communication and navigation systems are continuously enhanced and perfected, and airborne target detection and identification are also developed. The application of an electronic computer and a control technology enables the traditional mechanical connecting rod operation to be transited to fly by wire, the airborne fire control and the management of the externally-hung weapon are also transited from mechanical to electric control, and a flight control system, a fire control and externally-hung management system and the like also become an important component of avionics.
Bus-based networking is the central nervous system of modern avionics systems. The national military standard GJB 5034-2001 of the people's republic of China states that the linear token-passing multi-path data bus is abbreviated as LTPB. The token passing protocol running on the LTPB has the characteristics of system stability and high data rate, so that the token passing protocol is gradually applied to a military aviation data bus after a command response protocol is developed, the LTPB can realize distributed processing of bus data, messages can be prioritized according to actual requirements of an airplane, the message priority can be realized by setting different token rotation timers, and therefore the messages with high priority are guaranteed to have lower delay. The LTPB has very important theoretical value and potential application prospect in the field of avionic buses in China. Since test research is a necessary guarantee for reliable operation of the device, it is clear that the test items (test items), the test description language (test description language), and the test process (test process) of the LTPB are a prerequisite for the LTPB to be actually used in the actual device.
Traditional manual inspection and maintenance methods have been inadequate to support modern equipment testing and warranty requirements, and therefore automated testing techniques have evolved. The automatic test technology can automatically measure and diagnose a device under test (unit test) by a test equipment (test equipment), and can output or display a test result (test results) in an appropriate manner. The automatic test equipment can complete the automatic test of the tested equipment through the test script (test script), so that the test can be efficiently and conveniently carried out. The test script (test script) is a script file written by testers (testers) according to a test process (test process), the script file can form a program which can be directly executed by automatic test equipment after being analyzed, and the automatic test equipment executes the analyzed program line by line and completes a test function. The tester must follow the correct test procedure (test process) when writing the test script, and the formed test script (test script) is stable and reliable according to the appropriate test description language (test description language). The test description language (test description language) is used as a means for the communication between testers (testers) and the automatic test equipment, so that the test process (test process) can be described very accurately, and the function of automatic test can be realized after a software system is used for converting a test program into an executable code. The test process (test process) running in the automatic test equipment does not need a tester (testers) to directly operate the automatic test equipment, the tester (testers) only needs to write a test script (test script), and the test script (test script) covers all operations and parameters needing to be executed, so that the test efficiency is greatly improved, and meanwhile, the investment of human resources is reduced.
Description Language (Description Language) is a Language used to describe the structure and behavior of objects, and it can describe objects from abstract to concrete layer by layer, and a series of layered modules are used to represent complex digital system designs. Currently, common Test languages include ATML (automatic Test Markup Language), ATLAS (Abbreviated Test Markup Language for applications System, standard Test description Language), and so on, and the united states space agency adopts GOAL (Ground Operation aeronautical Language) as a Test Language of a foreign satellite Test System. Among various commonly used test languages, the ATML Language is a test description Language using XML (Extensible Markup Language) as a medium, and the syntax format of the test description Language conforms to the format of XML Schema, so that the test requirements, the test process (test process) and various test resources can be clearly described and represented.
Disclosure of Invention
In order to enable the LTPB bus protocol to be applied to avionics systems; on the other hand, the LTPB bus protocol can meet the use requirement of an avionics system; in the third aspect, when the LTPB bus used in the avionic system fails, the fault reason can be timely judged and detected; the invention designs an LTPB bus detection device applied to an avionics system and a method of a test flow description language thereof. The invention adopts XML as a test flow description language of an LTPB bus, and constructs four test flow description rules LTPB _ GZ ═ RT, RF, RS and RC as well as four bus test scripts LTPB _ JB ═ RTJB, RFJB, RSJB and RCJB } for test index items (test index items) of each stage of the LTPB and tested equipment (avionic system); the test flow of the LTPB bus can be completely represented through semantic definition and description representation of the LTPB _ GZ and the LTPB _ JB.
The invention relates to an LTPB bus detection device applied to an avionics system, which is provided with at least a computer; the method is characterized in that: the system also comprises a test description language model (500) stored in the computer;
the test description language model (500) transmits a test signal COM to a tested device, namely an LTPB bus in an avionics system, and receives a working signal WOR output by the LTPB bus in the avionics system (600)in(ii) a Third aspect tests the script program in the script unit (300) according to XML for the operating signal WORinCarrying out analysis; the fourth aspect outputs the test result and visually demonstrates it on the display of the computer (400);
the test description language model (500) comprises a description language constraint rule customizing unit (200) and an XML test script unit (300); the descriptive language constraint rule customizing unit (200) and the XML test script unit (300) are obtained by software programming;
the first aspect of the descriptive language constraint rule customizing unit (200) is used for receiving information of a validity testing method formulated in the LTPB bus standard (100); in the second aspect, four test flow description rules are set, namely a timer test flow description rule RT, a message frame format test flow description rule RF, a station management test flow description rule RS and a counter test flow description rule RC; the third aspect outputs the four test flow description rules to an XML test script unit (300);
the XML test script unit (300) is matched with the description language constraint rule customizing unit (200); namely:
matching the timer test flow description rule RT with a timer test script, and marking as RTJB;
matching the message frame format test flow description rule with RF is a message frame format test script which is marked as RFJB;
matching the station management test flow description rule RS is a station management test script which is marked as RSJB;
and the counter test script matched with the counter test flow description rule RC is marked as RCJB.
The device for detecting the LTPB and the test flow description language method thereof have the advantages that:
the invention firstly makes a constraint rule meeting the LTPB bus for avionic system communication according to the LTPB standard, and makes a language suitable for LTPB bus test flow description in an XML format, wherein the description language is defined aiming at the characteristics of the protocol, and a complete and reliable test script can be written through the test description language defined by the invention.
Secondly, the test flow description language structural formula of the invention has higher readability and intelligibility in the aspect of describing the test flow, and the semantics is very close to the meaning of an actual object, thereby being convenient for the understanding of a tester.
The invention defines the legality of the test script document through XML Schema, so that different test designers write test scripts which are mutually compatible, and the efficiency of test work is greatly improved.
And innovatively providing a test flow divided into three stages for testing in the aspect of classified test of the test flow, wherein the three stages are a cold start stage, a normal stage and an error stage, are independent from each other, and are easier for maintenance of the test process.
Drawings
Fig. 1 is a block diagram of an LTPB bus inspection apparatus applied to an avionics system according to the present invention.
FIG. 2 is a block diagram of the present invention for building a test description language model.
FIG. 3 is a block diagram of a type description based on a linear token data bus test description language.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings.
Index 100 referring to LTPB bus standard
According to the working characteristics of the linear token data buses of GJB8585-2015 and GJB8611-2015, the working phases are divided into a cold start phase, a normal working phase and an error response phase. The cold start defines the whole process from power-on to logic ring establishment, and the process of sending out a token applying frame from bus contention after power-on, sending a first round of token frame and searching for a subsequent station until the last station on the bus finds the first station as the subsequent station. This process is complete and signals that the bus can begin transmitting message signals. The indexes to be tested in the cold start stage include the following, and the related test contents include a test of a BIU (bus interface unit) initialization process and a test of a logic ring establishment process, wherein the test includes two conditions, namely the establishment of a logic ring when a message to be processed exists or not, and the test of a station management function controlled by BAT at a token application frame stage. The testing of the station management function comprises testing of the BIU under different working modes, testing of loading/report configuration and configuration report, testing of loopback test message and loopback test message response, testing of time report and testing of time synchronization message.
Table 1 test index items at the cold start stage:
Figure BDA0002979959020000041
stage of normal operation
The normal working phase refers to a state that the bus starts to send messages after a cold start phase and a logic loop is established, and all timers, counters and the like of the bus enter a normal working phase in the period. The normal working stage involves more test items, and the test items respectively comprise the test of physical layer indexes, wherein data symbols, the characteristics of optical and electrical bus medium interfaces of a transmitter and a receiver; the frame format test needs a bidirectional test, that is, a test of a transmission frame is needed when a data frame is transmitted, and a test of a reception frame is needed when the data frame is received. The test that each field needs to be covered when the Frame is sent and received is tested, and the test includes SD (Start limiter, Start Delimiter), ED (End limiter, End Delimiter), FT (Frame Type ), Px (Priority, Priority), SMC (state Management Code, Station Management Code), SA (Source Address ), DA (Destination Address, Destination Address), WC (World Count, word Count), INFO (Information ), MFCS (Message Frame Check Sequence, Message Frame Check Sequence), TFCS (Token Frame Check Sequence); testing timers, including testing 5 timers, including THT (Token Holding Timer), RAT (Ring acceptance Timer), TRT (Token Rotation Timer), and TPT (Token Passing Timer); the test of the communication quantity accumulation counter comprises the test of 7 counters including a counter for sending effective messages, a counter for sending application tokens, a counter for transmission interruption, a counter for frame effectiveness errors, a counter for receiving frame errors, a counter for receiving effective messages and a counter for receiving queue overflow. The specific index categories are shown in Table 2.
Table 2 test index items at normal working stage:
Figure BDA0002979959020000061
error response phase
The error response phase is a measure phase that the bus takes corresponding reaction when the bus has an error in a physical layer or a protocol layer, and is opposite to the normal working phase, and the phase is the reaction when the bus has an abnormal condition. The test indexes involved in the bus working phase comprise physical layer error injection, and the optical medium and the dielectric medium respectively comprise the test of the errors of sensitivity, signal rate, waveform, transmission gap and preamble; error injection in frame format, including applying for token frame, error test in general frame format and station management frame; the measurements of the BIU error registers, including the BIU error register associated with transmission and the BIU error register associated with reception, are shown in table 3.
Table 3 test index entries for the error response phase:
Figure BDA0002979959020000062
aiming at the test indexes of the three parts, wherein the test indexes are mainly aiming at four parts of a timer, an information frame format, a counter and a station management, the test of the test indexes is completed through a specified test set, a standard test method of the test indexes can be completely described through the set, a test script is written according to a formulated rule, the test script is analyzed through analysis software to form an executable code, and finally the test process is completed.
The invention provides a description method and a constraint rule of a test flow, each test set is defined by using an XML language format and is respectively a test action set Sact, a test index set So, a test instrument set SE, a test control statement set SC, a signal attribute set Sattr and a description object set Sdo, and the following describes elements and meanings thereof in each set in detail.
Set of test actions
In the invention, a test action set is marked as Sact, and elements contained in the Sact are represented as Sact in a set form
Figure BDA0002979959020000071
In the present invention, it is necessary to pay attention to writing of a test script related to a test action, and the test action rule script should be written according to an action rule. The test action task structural formula is as follows:
Figure BDA0002979959020000072
in the invention, under the condition that the testing personnel clearly divides the work of the testing equipment and the tested equipment, the < object >' stage in the testing action task structural formula can be omitted.
Set of test indexes
In the invention, a test index set is marked as So, and elements contained in So are represented as So in a set form
Figure BDA0002979959020000073
In testing index set
Figure BDA0002979959020000074
The Frame, Timer, and Counter in (1) are also a set of test objects, and the test objects correspond to each message, Timer, and Counter in the LTPB standard.
Figure BDA0002979959020000081
VMTC is a counter for sending effective messages, CTTC is a counter for sending application tokens, TAC is a counter for transmission interruption, FVEC is a counter for frame effectiveness errors, FREC is a counter for receiving frame errors, VMRC is a counter for receiving effective messages, and RQOC is a counter for receiving queue overflow.
Frame＝{Claim Token,Token,Message}。
Figure BDA0002979959020000082
SD start delimiter, FC frame control, SA source address, DA destination address, WC word count, INFO information, MFSC message frame check sequence, ED end delimiter.
Token ═ { SD, DA, TFCS, ED }. TFCS token frame check sequence.
Claim Token ═ { SD, FC, SA, FILL, ED }. FILL is a padding field. Timer ═ BAT, TPT, RAT, TRT, THT }. BAT bus activity timer, TPT token passing timer, RAT allowed in-loop timer, TRT token circulation timer, THT token holding timer.
Test instrument set
In the present invention, the test instrument set, denoted SE, contains elements expressed in set form as SE
Figure BDA0002979959020000083
Test control statement set
In the invention, a test control statement set is marked as SC, and elements contained in the SC are represented as SC in a set form
Figure BDA0002979959020000084
Set of signal properties
In the invention, a signal attribute set is marked as Sattr, and elements contained in the Sattr are expressed as Sattr in a set form
Figure BDA0002979959020000085
Description object set
In the present invention, an object set is described and denoted as Sdo, and elements contained in Sdo are represented in a set form as Sdo ═ { UUT, TEQ }.
Test start end flag
In the present invention, the test start/end flag is an important flag for the test, and is usually customized by the tester. The suggested definition mode is Test and Test index name, such as start and end mark TestTHT of THT timer, start and end mark TestPx of priority field, etc.
LTPB (I) bus detection device
The detection device for detecting the LTPB bus serving the avionics system is referred to as LTPB bus detection device in the present invention. Referring to fig. 1, the LTPB bus detection apparatus of the present invention includes a computer 400, a test description language model 500; the test description language model 500 is installed in the computer 400.
The test description language model 500 transmits a test signal COM to a device under test, namely an LTPB bus in an avionics system, in a first aspect, and receives a working signal WOR output by the LTPB bus in the avionics system 600 in a second aspectin(ii) a Third aspect tests the script program in the script unit 300 according to XML for the WOR of the working signalinCarrying out analysis; the fourth aspect outputs the test results and is visually presented on the display of the computer 400.
(II) building a test description language model 500
Referring to fig. 2, the test description language model 500 of the present invention includes a description language constraint rule customizing unit 200 and an XML test script unit 300; the descriptive language constraint rule customizing unit 200 and the XML test script unit 300 are obtained by software programming and installed in the computer 400.
A computer is a modern intelligent electronic device capable of automatically performing a large number of numerical calculations and various information processing at high speed in accordance with a program stored in advance. The lowest configuration is CPU 2GHz, memory 4GB and hard disk 10 GB; the operating system is windows7 and above.
The test script uses XML format, the analysis software platform is java program development platform, and the executable program of the testable device is formed after analysis based on DOM (document object model).
Descriptive language constraint rule customization Unit 200
In the present invention, the first aspect of the descriptive language constraint rule customizing unit 200 is configured to receive information of an effectiveness testing method formulated in the LTPB bus standard 100; in the second aspect, four test flow description rules are set, namely a timer test flow description rule RT, a message frame format test flow description rule RF, a station management test flow description rule RS and a counter test flow description rule RC; the third aspect outputs four test flow description rules to the XML test script unit 300.
The method for testing the effectiveness of the linear token-passing multi-path data bus refers to GJB 8611-2015.
XML test script Unit 300
In the present invention, the XML test script unit 300 is matched with the description language constraint rule customizing unit 200. Namely:
and the timer test script matched with the timer test flow description rule RT is recorded as RTJB.
And the message frame format test script matched with the message frame format test flow description rule RF is marked as RFJB.
And the station management test script matched with the station management test flow description rule RS is recorded as RSJB.
And the counter test script matched with the counter test flow description rule RC is marked as RCJB.
In the present invention, the information sources for writing the test script are:
the set of test actions
Figure BDA0002979959020000101
The set of test metrics
Figure BDA0002979959020000102
The above-mentioned
Figure BDA0002979959020000103
The Frame { Claim Token, Message };
the above-mentioned
Figure BDA0002979959020000104
(ii) said Token ═ { SD, DA, TFCS, ED };
the Timer is { BAT, TPT, RAT, TRT, THT };
the Claim Token ═ { SD, FC, SA, FILL, ED };
the test instrument set
Figure BDA0002979959020000105
The set of test control statements
Figure BDA0002979959020000106
The set of signal properties
Figure BDA0002979959020000107
The set of description objects Sdo ═ { UUT, TEQ }.
The test flow description rule RT of the timer is set as:
in the invention, when testing the timer, the description language structural formula in the timer test flow description rule RT is:
< test initiation flag >
< test apparatus >
< parameter configuration >
< timer parameter configuration >
< physical Address parameter configuration >
< test stimulus >
< frame Format configuration >
< performing test action task >
< description of feedback Signal >
< end of test flag >
In the invention, firstly, when a test equipment (test equipment) is definitely tested for a certain timer, parameters are required to be set, the set parameters comprise parameters of the corresponding timer, and the physical address and other parameters are configured according to the requirement of a test scheme of the timer. Other parameters may include the setting of the Maximum Station Address (MSA). Then, a test stimulus is given, the stimulus of the test is usually a loaded message, so it is necessary to configure the format of the information frame and then perform the test operation, and describe the feedback signal containing the data frame and the test time. And informing the test equipment (test equipment) of the type of the feedback signal, and finishing the test after obtaining the test result.
The timer test script RTJB is set as:
in the invention, the XML format is applied to the test script information source to describe the test flow under the limitation of the RT structural formula, so as to realize the matching with the RT.
In order to avoid loss of generality, the script language for the source of the test script information under the limitation of the RT structural formula is exemplified by the THT timer.
For example, for the test of the token holding timer THT, the description language of the test script is as follows:
Figure BDA0002979959020000111
Figure BDA0002979959020000121
in the present invention, the above script parameter is only used as a reference example, and the scope of the present invention is not limited to this parameter.
The message frame format test flow description rule RF is set to:
in the invention, the message frame format is tested, and the description language structural formula in the message frame format test flow description rule RF is as follows:
< test initiation flag >
< test apparatus >
< load and set message metrics >
< number of messages >
< index parameter >
< sending message frame >
< parsing message frame >
< end of test flag >
In the invention, no matter which type of message frame needs to write the test script RFJB applicable to the message frame according to the message frame format test flow description rule RF, firstly, a test device (test request) is specified, then the test index of the test device is informed of which specific field in the frame, the number of the sent messages and specific parameters of the index are set for the tested device (unit under test), then the tested device is made to send the messages, and the test device analyzes the messages and obtains the test result. This is the test rule for sending messages.
In the present invention, the test rule of the received message is the same as the test rule of the sent message.
The message frame format test script RFJB is set as:
in the invention, the XML format is applied to the test script information source to describe the test flow under the limitation of the RF structural formula, so as to realize the matching with RF.
In order to avoid loss of generality, the script language for the source of the test script information under the limitation of the RF structural formula is exemplified by the priority PX field of the message.
For example, a test script for the priority PX field of a message is described as follows:
Figure BDA0002979959020000131
Figure BDA0002979959020000141
in the present invention, the above script parameter is only used as a reference example, and the scope of the present invention is not limited to this parameter.
The station management test flow description rule RS is set as:
in the invention, when the station management is tested, the description language structural formula in the station management test flow description rule RS is:
Figure BDA0002979959020000142
in the test process of the station management message, it is consistent with the previous rule that the corresponding test equipment (test request) needs to be given, then the station management message is loaded to the tested equipment (unit test) or a register related to the station management is set, after the station management message is sent, the test equipment is used as a work station on the LTPB bus, corresponding response is made to the station management command, and a feedback message is fed back, or corresponding work mode and work state are adjusted, and the test equipment can analyze and obtain the feedback message on the LTPB bus, or read the register value of the test equipment to verify the correctness of the test.
The station management test script RSJB is set as:
in the invention, the XML format is applied to the test script information source to describe the test flow under the limitation of the RS structural formula, so as to realize the matching with the RS.
In order to avoid loss of generality, the test-back message and the test-back message response are used as examples to list the script language for the source of the test script information under the limitation of the RS structure.
For example, the test flow description for the loopback test message and the loopback test message response shall be:
Figure BDA0002979959020000143
Figure BDA0002979959020000151
in the present invention, the above script parameter is only used as a reference example, and the scope of the present invention is not limited to this parameter.
The counter test flow description rule RC is set to:
in the invention, when the counter is tested, the description language structural formula in the counter test flow description rule RC is as follows:
< test initiation flag >
< test apparatus >
< Power Up >
< resetting of counter >
< read counter >
< Loading frame >
< generating Transmission frame Condition >
< read counter >
< counter reset/Change Transmit frame Condition >
< load message >
< sending message >
< read counter >
< resetting of counter >
< read counter >
< end of test flag >
The test equipment (test equipment) is specified before starting the test, and the test of the counter must power up the device under test (unit test) so that the device under test performs a built-in self test. And setting hardware parameters of the workstation according to the test requirements of the counter, resetting the counter to be tested through a station management command, and returning a traffic accumulation report. And then loading the corresponding frame into the tested equipment according to a standard test scheme and generating a corresponding frame sending condition, reading the value of the tested counter after the frame sending is finished, and checking whether the value is consistent with the setting. And then changing the counter value or changing the sending condition, then repeatedly sending the frame, acquiring the counter value through the station management message, and observing whether the counter value meets the specification. Finally, the counter is reset and read before the test is finished, and the counter result should be 0.
The counter test script RCJB is set to:
in the invention, the XML format is applied to the test script information source to describe the test flow under the limitation of the RC structural formula, so as to realize the matching with the RC.
In order to avoid loss of generality, the script language for the test script information source under the limitation of the RC structural formula is listed by taking the counter for sending the application token as an example.
For example, a test script for sending an application token counter is as follows:
Figure BDA0002979959020000161
Figure BDA0002979959020000171
in the present invention, the above script parameter is only used as a reference example, and the scope of the present invention is not limited to this parameter.
In the invention, because the test device can not directly execute the test script file, the test script needs to be analyzed to form an executable code, and the test device executes the test operation according to the executable code. The invention adopts java language to analyze the test script, and the analysis idea is based on DOM analysis, and the DOM multi-branch tree is obtained through the object in the Java DOM4J packet. Firstly creating an SAXReader object for reading an xml file, then creating a Document object, wherein the Document object represents the whole xml file, and then obtaining a tree root element by a self-contained method getroot element in the Document object, wherein the tree root element is various Test elements in the Test Document. After the tree root element is obtained, the sub-elements under the root element can be obtained through the method element. In the implementation process, due to the set parameters such as the test repetition times, the java files are all object type variables, and the types of the object type variables need to be converted into adaptive types, so that the subsequent data operation is facilitated. When the specific operation is analyzed, the operation interface function of the test equipment is directly called, the test equipment can execute the corresponding operation, and data is returned when needed. The test and the script are analyzed by the LTPB bus detection device, and the custom function is called to execute the operation and return the parameter process to the simulation test equipment, so that the LTPB bus detection device can obtain the correct test result, and the reliability of the test script can be proved.
In the present invention, the multi-branch tree structure refers to the data structure and the application algorithm course written by Chen Wen Bo, pages 129-130, 1 st edition 2/2001.
Analyzing all test scripts through java language, verifying a software layer, executing a test after obtaining each node element of the multi-branch tree, simulating a test process and a feedback result through self-defined function call, and finally feeding back a correct result to a test user.
Referring to fig. 3, in the writing process of the script, the timer part includes five timers, i.e., THT, TPT, TRT, RAT, and BAT, the THT timer is taken as an example to give a test script, and the writing process of the script is described in detail below. Test start and end flags are first given, where the test start and end flags are user-defined. Next, according to a given test constraint rule RT, a test device is first specified, which belongs to the set of objects, TEQ. The type of TEQ may be selected from a collection of test instruments, and selectable objects include E-Receiver, dynameter, and the like. For the test of the THT, the test equipment is a workstation in the bus, and the test is performed after a logic loop is formed. Then, according to the RT rule, the parameters need to be configured, and the configuration action is a Config element in the test action set Sact. The parameter configuration including the timer needs to be established according to standards during the parameter configuration of the timer, the counting range of each timer is different, and the parameter configuration range of the THT counter is 0-65535us, namely the THT parameter is 0-65535us in the process of writing the test script. However, since the parameter ranges in the test script are all in international standard units, one-unit conversion is also required. The method of parameter configuration needs to be described in terms of the structural formula of the test action set. The parameters need to be set for both the test device TEQ and the device under test UUT. The specific configuration mode is that test excitation is given next, and the process of giving the test excitation is to find the action parameter corresponding to the excitation in the test action set Sact, wherein the action is mainly to Load a Load element, and the use method of the element needs to conform to the use method of the test action set. For the Load element, an index of Load needs to be indicated, where the index is a Message, since this step of loading the Message is usually only loading for the device under test, the tester may omit the loading object TEQ or UUT if the tester explicitly tests the device function. The Message field includes SD, FC, SA, DA, WC, INFO, MFCS, ED. However, the actual three fields of SD, ED, and MFCS do not require the user to write the script themselves because the values of these two fields specified in the standard are fixed for SD and ED, and for MFCS, the workstation has circuitry to automatically generate the MFCS without requiring the user to set it himself. However, for five fields of FC, SA, DA, WC, and INFO, the number of bits of each field is different, so the value range of the parameter setting is also different, for example, FC is a field of 8 bits, so the parameter value should be set to 0 to 255, and if the parameter exceeds this range when writing the script, the written script cannot run. When writing a test script, if the requirement of a tester on the normalization and consistency of the script is high, the tester can further restrict the test script through an xsd (XML Schema Definition) restriction document, because the xsd restriction document contains keywords such as "maxInclusive" and "minInclusive" and "engeration", test parameters can be restricted, after the Message is loaded, the Message is sent, the test action command Send is also obtained from a test action set Sattr, the sending object is a previously loaded Message object, and finally, the test action is an Analyze action, the concerned information is an SA field, namely, the SA field is analyzed and obtained after the Message on the bus is obtained.
Because the test device cannot directly execute the test script file, the test script needs to be analyzed to form an executable code, and the test device executes the test operation according to the executable code. The invention adopts java language to analyze the test script, the idea of the analysis is DOM analysis, and the DOM multi-branch tree is obtained through the object in the Java DOM4J packet. Firstly creating an SAXReader object for reading an xml file, then creating a Document object, wherein the Document object represents the whole xml file, and then obtaining a root element by a self-contained method getCootElement in the Document object, wherein the root element is various Test elements in the Test Document. After the root element is obtained, the child elements under the root element can be obtained through the method element. In the implementation process, due to the set parameters such as the test repetition times, all the variables are object type variables in the java file, and the types of the variables need to be converted into adaptive types, so that the subsequent data operation is facilitated. When the specific operation is analyzed, the operation interface function of the test equipment is directly called, the test equipment can execute the corresponding operation, and data is returned when needed.
In more detail, as for the parameter of the THT timer, when the TestTHT element, i.e. the test start flag, is resolved, it indicates that the THT test is started. And then, acquiring a TEQ element as a Station, establishing connection between the test equipment and the tested equipment, then configuring parameters, analyzing the test script to acquire physical address parameters of the UUT and the TEQ and THT parameters of the UUT, and configuring the parameters by the bus detection device. The testing device and the tested device after the parameters are configured are ready for testing. And analyzing the Load element in the analyzing process, and then detecting the Message element, which indicates that the Message element needs to be loaded on the tested device. And configuring according to the parameter values of the test elements in the test script, finishing loading the message when a Load element finishing mark is detected, finally sending the message, acquiring the message on the bus, analyzing the SA field, returning a correct test value according to the field result after the SA field is analyzed, and displaying the correct test value on a computer screen.
Table 4, the physical meaning of each letter states:
Figure BDA0002979959020000191
Figure BDA0002979959020000201
Figure BDA0002979959020000211

Claims (8)

1. an LTPB bus detection device applied to an avionics system is provided with at least a computer; the method is characterized in that: the system also comprises a test description language model (500) stored in the computer;
the test description language model (500) transmits a test signal COM to a tested device, namely an LTPB bus in an avionics system, and receives a working signal WOR output by the LTPB bus in the avionics system (600)in(ii) a Third aspect tests the script program in the script unit (300) according to XML for the operating signal WORinCarrying out analysis; the fourth aspect outputs the test result and visually demonstrates it on the display of the computer (400);
the test description language model (500) comprises a description language constraint rule customizing unit (200) and an XML test script unit (300); the descriptive language constraint rule customizing unit (200) and the XML test script unit (300) are obtained by software programming;
the first aspect of the descriptive language constraint rule customizing unit (200) is used for receiving information of a validity testing method formulated in the LTPB bus standard (100); in the second aspect, four test flow description rules are set, namely a timer test flow description rule RT, a message frame format test flow description rule RF, a station management test flow description rule RS and a counter test flow description rule RC; the third aspect outputs the four test flow description rules to an XML test script unit (300);
the XML test script unit (300) is matched with the description language constraint rule customizing unit (200); namely:
matching the timer test flow description rule RT with a timer test script, and marking as RTJB;
matching the message frame format test flow description rule with RF is a message frame format test script which is marked as RFJB;
matching the station management test flow description rule RS is a station management test script which is marked as RSJB;
and the counter test script matched with the counter test flow description rule RC is marked as RCJB.
2. The LTPB bus detection device for avionics systems according to claim 1, wherein: when testing the timer, the description language structural formula in the timer testing flow description rule RT is:
Figure FDA0002979959010000021
3. the LTPB bus detection device for avionics systems according to claim 1, wherein: testing the message frame format, wherein the description language structural formula in the message frame format testing flow description rule RF is as follows:
Figure FDA0002979959010000022
4. the LTPB bus detection device for avionics systems according to claim 1, wherein: when station management is tested, the description language structural formula in the station management test flow description rule RS is as follows:
Figure FDA0002979959010000023
5. the LTPB bus detection device for avionics systems according to claim 1, wherein: when the counter is tested, the description language structural formula in the counter test flow description rule RC is as follows:
Figure FDA0002979959010000031
6. the LTPB bus detection device for avionics systems according to claim 1, wherein: the test description language model (500) defines each element in a test action set Sact, a test index set So, a test instrument set SE, a test control statement set SC, a signal attribute set Sattr and a description object set Sdo by using an XML language format;
set of test actions
Figure FDA0002979959010000032
The test action task structural formula applied to the test action set Sact is as follows:
Figure FDA0002979959010000033
set of test indexes
Figure FDA0002979959010000034
Test instrument set
Figure FDA0002979959010000041
Test control statement set
Figure FDA0002979959010000042
Set of signal properties
Figure FDA0002979959010000043
Set of description objects Sdo ═ { UUT, TEQ }.
7. The LTPB bus detection device for avionics systems according to claim 1, wherein: the XML test script unit (300) compiles the test script from the following information sources:
the set of test actions
Figure FDA0002979959010000044
The set of test metrics
Figure FDA0002979959010000045
The above-mentioned
Figure FDA0002979959010000046
The Frame { Claim Token, Message };
the above-mentioned
Figure FDA0002979959010000047
(ii) said Token ═ { SD, DA, TFCS, ED };
the Timer is { BAT, TPT, RAT, TRT, THT };
the Claim Token ═ { SD, FC, SA, FILL, ED };
the test instrument set
Figure FDA0002979959010000048
The set of test control statements
Figure FDA0002979959010000049
The set of signal properties
Figure FDA00029799590100000410
The set of description objects Sdo ═ { UUT, TEQ }.
8. The method for testing the flow description language based on the LTPB bus detection device of claim 1, 2, 3, 4 or 5, wherein: and compiling the test script according to the description language structural formula.
CN202110284696.5A 2021-03-17 2021-03-17 LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device Active CN113010358B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110284696.5A CN113010358B (en) 2021-03-17 2021-03-17 LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110284696.5A CN113010358B (en) 2021-03-17 2021-03-17 LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device

Publications (2)

Publication Number Publication Date
CN113010358A true CN113010358A (en) 2021-06-22
CN113010358B CN113010358B (en) 2022-09-30

Family

ID=76408984

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110284696.5A Active CN113010358B (en) 2021-03-17 2021-03-17 LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device

Country Status (1)

Country Link
CN (1) CN113010358B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114441947A (en) * 2021-12-24 2022-05-06 成都天奥测控技术有限公司 Automatic test system signal routing method based on ATML
CN114757156A (en) * 2022-06-14 2022-07-15 成都飞机工业（集团）有限责任公司 Method, device, equipment and medium for compiling aircraft system test instruction

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101025686A (en) * 2007-03-22 2007-08-29 中兴通讯股份有限公司 Automation test system and test script generating and operating method
CN101079757A (en) * 2007-07-04 2007-11-28 北京航空航天大学 A testing device and operation method for broadband aviation electronic bus
CN102541730A (en) * 2011-12-08 2012-07-04 北京空间飞行器总体设计部 Semantic identification and automatic generation method for spacecraft test script
US20140059385A1 (en) * 2012-08-24 2014-02-27 Vce Company, Llc Compliance testing engine for integrated computing system
CN107608889A (en) * 2017-09-15 2018-01-19 杭州销冠网络科技有限公司 A kind of test script automatic generation method and system
CN111382055A (en) * 2018-12-29 2020-07-07 贝壳技术有限公司 Automatic unit testing method and device based on unified description language

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101025686A (en) * 2007-03-22 2007-08-29 中兴通讯股份有限公司 Automation test system and test script generating and operating method
CN101079757A (en) * 2007-07-04 2007-11-28 北京航空航天大学 A testing device and operation method for broadband aviation electronic bus
CN102541730A (en) * 2011-12-08 2012-07-04 北京空间飞行器总体设计部 Semantic identification and automatic generation method for spacecraft test script
US20140059385A1 (en) * 2012-08-24 2014-02-27 Vce Company, Llc Compliance testing engine for integrated computing system
CN107608889A (en) * 2017-09-15 2018-01-19 杭州销冠网络科技有限公司 A kind of test script automatic generation method and system
CN111382055A (en) * 2018-12-29 2020-07-07 贝壳技术有限公司 Automatic unit testing method and device based on unified description language

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114441947A (en) * 2021-12-24 2022-05-06 成都天奥测控技术有限公司 Automatic test system signal routing method based on ATML
CN114757156A (en) * 2022-06-14 2022-07-15 成都飞机工业（集团）有限责任公司 Method, device, equipment and medium for compiling aircraft system test instruction
CN114757156B (en) * 2022-06-14 2022-10-25 成都飞机工业（集团）有限责任公司 Method, device, equipment and medium for compiling aircraft system test instruction

Also Published As

Publication number Publication date
CN113010358B (en) 2022-09-30

Similar Documents

Publication Publication Date Title
CN113010358B (en) LTPB (Low temperature pluggable) bus detection device applied to avionics system and method for testing flow description language of LTPB bus detection device
US9218269B2 (en) Testing multiple target platforms
CN111124850A (en) MQTT server performance testing method, system, computer equipment and storage medium
CN106357457B (en) A kind of alarm test method, apparatus and system
US20080120521A1 (en) Automated Testing and Control of Networked Devices
CN112783794B (en) Aviation communication radio station software testing system
US20020091968A1 (en) Object-oriented data driven software GUI automated test harness
CN106209515B (en) Access network equipment automatization test system
CN108984393A (en) A kind of unit testing code automatic generation method and device
CN109977012A (en) Joint debugging test method, device, equipment and the computer readable storage medium of system
CN109783063B (en) Signal-oriented automatic test system self-checking program development method and device
CN114816980A (en) Automatic testing device and method for embedded communication system
CN109189679A (en) Interface test method and system, electronic equipment, storage medium
CN108319516A (en) A kind of test system and test method
CN109976992A (en) A kind of automatic software test method and system
US20230035673A1 (en) Information processing system, information processing apparatus, use method of information processing apparatus, user terminal, and program therefor
US20240045752A1 (en) Methods and apparatuses for troubleshooting a computer system
Crouch et al. P1687. 1: Accessing Embedded 1687 Instruments using Alternate Device Interfaces other than JTAG
CN110659215A (en) Open type industrial APP rapid development and test verification method
Efkemann A Framework for Model-based Testing of Integrated Modular Avionics
Wang et al. A Prepar3d Based Signal Simulation System for ARINC429 Bus
CN110175126A (en) Test case based on scripting language
Ciardi et al. Definition, Implementation and Testing of an XML-based Packet Description Language for Traffic Analysis in a SpaceWire Communication
Ziegler et al. An Ada based real-time closed-loop integration and regression test tool
Zhu et al. Design of Signal-Oriented Automatic Test System Software Based on Flowchart

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant