KR20130116081A - Developing method of portable avionics system test equipment - Google Patents

Abstract

PURPOSE: A method for developing a portable device for testing an electronic avionic system is provided to support the integration of the electronic avionic system and provide compatibility by offering a method for developing a portable device for testing an electronic avionic system which is usable at the outside of laboratory environment. CONSTITUTION: A least recently used (LRU) database is generated based on interface control doc (ICD) (A). The LRU database is imported to a project, DBSim.dll is generated by an export command (C). A portable test equipment (PTE) model type is determined, and a frame for the scheduling of a PTE model is defined (E). Operation with the model manager of serial (SE) is defined, and the PTE model is verified through a debug function (G). [Reference numerals] (100) Generate MFC AppWizard(DLL) new project; (200) Set project - activate library, RTT1; (300) Determine PTE I/O signal; (400) Add new driver endowed from CDriver based class; (500) Realize new driver by overriding virtual function; (600) Connect with Stream class defined in model; (700) Define feature value related to I/O; (A) Generate DB of given LRU based on ICD(Interface Control Doc); (AA) Model developing process; (B) Import generate LRU DB in project; (BB) Realize model Handshaking logic; (C) Generate DBSim.d11 through Export order; (CC) Add model Handshaking logic non-realizing flight model; (D) Determine module Type; (DD) Driver development process; (E) Define frame for model scheduling; (F) Define interlock with Model Manager of SE; (G) Verify module though debug function

Description

DEVELOPING METHOD OF PORTABLE AVIONICS SYSTEM TEST EQUIPMENT}

The present invention relates to a method for developing portable avionics test equipment, and more particularly, to a final integrated test and verification of a flight operation program, and a method for developing portable avionics test equipment capable of verifying avionics equipment.

The avionics integrated system is the final integrated test and verification of the flight operation program and the avionics equipment verification system.It is a test environment system that is operated for the purpose of verifying the compatibility of the avionics system, supporting ground / flight tests, and troubleshooting. .

Previously, avionics systems have been developed and validated in a constrained environment called laboratories for integration of avionics systems.In the case of out-of-lab environments, separate supporting equipment or equipment-specific equipment is available for functional verification and failure investigation of the equipment. Only the system developed for the characteristics of was used.

However, the separate support equipment used in the case of leaving the laboratory environment, or the system developed for the unique characteristics of the equipment is insufficient compatibility, there was a problem that must develop a system for each characteristic according to the test environment.

That is, by developing and using each system according to the test environment, there was a problem that the development period and development cost of the aircraft increases.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a method for developing a portable avionic system test equipment that can be used even in a laboratory environment.

In order to achieve the above object, the portable avionic system test equipment development method according to the present invention is based on the ICD (Interface Control Doc), LRU (MC (mission computer), MFD (multi-function display), CDU (control display) Device), Center Pedestal) step (A) to create a database, the step of importing the LRU database (B) to the project (B), and an Export command DBSim.dll Generating (C), determining a portable test equipment (PTE) model type (D), defining a frame for scheduling the PTE model (E), and a model manager of a SE A process of developing a PTE model, the method comprising: defining a linkage with (F) and verifying the PTE model through a debug function (G); And generating a new MFC AppWizard (DLL) project (100), setting the generated project (200), determining a PTE I / O signal (300), and inheriting from a C driver base class. Adding a received new driver (400), overriding a virtual function to implement the new driver (500), connecting to a stream class defined in the PTE model (600), and I It includes a process for developing a driver having a step (700) defining the / O-related characteristic value.

In addition, the portable avionic system test equipment development method according to the present invention, in the step (D), the PTE model type is characterized in that any one of ICD, Behavior, Dynamic.

In addition, in the step (D), if the PTE model type is Behavior, the method for developing the portable avionic system test equipment according to the present invention implements the step (D-1) of implementing the handshaking logic of the model. It further comprises.

In addition, in the step (D), if the PTE model type is Dynamic, adding the flight model interworking when implementing the handshaking logic of the model (D- It characterized in that it further comprises 1).

In addition, the method for developing a portable avionic system test equipment according to the present invention, in the step 300, the PTE I / O signal is characterized in that any one of the avionics input and output signals including MUX, ARINC, Serial, etc. do.

According to the present invention, by providing a method for developing a portable avionic system test equipment that can be used outside the laboratory environment, it is possible to support the integration of the avionics system in real time and to be compatible with other systems.

1 is a block diagram showing the configuration of an avionics integrated test system;
2 shows the software architecture of the avionics integrated test system.
3 shows monitoring of ARINC-429 data between a RALT model and MC on a portable test equipment.
4 illustrates monitoring of MUX data between the GPS / INS mall and MC on a portable test equipment.
5 is a floor chart showing a PTE development procedure according to the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings and the following description. However, the present invention is not limited to the embodiments described herein but may be embodied in other forms. Rather, the embodiments disclosed herein are provided so that the disclosure can be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like reference numerals designate like elements throughout the specification. It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. &Quot; comprises "and / or" comprising ", as used herein, unless the recited element, step, operation, and / Or additions.

1 is a configuration diagram showing the configuration of an avionics integrated test system.

Referring to FIG. 1, an integrated avionic test system according to the present invention includes an avionics simulation core console (ASC), an avionics equipment console (AEC), and an operator test console ( OTC: Operator Test Console).

The avionics integrated test system is a device that verifies and tests the system in conjunction with the mission computer software and the dynamic simulation data of the aircraft, and consists of the avionics equipment and simulation software of the actual aircraft.

First of all, the operator test console is the main interface of the user, which consists of a cockpit and co-pilots, and has a high frequency of access for the user. The LRU (MC), the MFD (Multifunction Display), the CDU (Control Display), and Center Pedestal ( It provides the electrical and mechanical interface for mounting and connecting the center support).

In addition, the avionics console unit is equipped with avionics equipment, and includes a REAL / SIM panel for switching between the simulation model and the actual equipment, a CBU for power distribution of the LRU, simulation signals and monitoring between the model and the actual equipment. It consists of a VME card file and the like.

Meanwhile, the avionics simulation console unit provides hardware and software interfaces between the avionics devices and includes interfaces for data monitoring and simulation.

The avionics simulation console consists of four computers:

OTW (Out Window) for pilot view and flight status, MMI (Man Machine Interface) for simulating operation and control, data injection, instrument / panel, and real-time I / O control and simulation software SIMENG (Simulation Engine) to run, and MON (Monitor) to monitor data and record / store data.

2 shows a software architecture of the avionics integrated test system.

Referring to FIG. 2, an object-oriented structure that can be reused even when a project is changed is designed. Therefore, in software of a portable test equipment, it is possible to design a driver form that can carry only an I / O module while maintaining a reuse module. The simulation engine, which is the basic framework of the software, and the user interface part are the same as those of the integrated avionics test system software. The DB, driver, and model can be newly implemented.

In the avionics integrated test system, simulating and monitoring the input / output data of the avant-garde components is a key function, so the development of portable test equipment requires the reconfiguration of the I / O card to be portable. Most avionics integrated system input / output cards have a VME rack type, which is limited to carry.

Referring to Table 1 below, the I / O types required for the development of portable test equipment can be identified based on the I / O card type of the Surion avionics integrated system developed by the applicant.

Portable test equipment can be defined as portable simulation equipment for signals such as MUX, ARINC, Discrete, and Serial using PCI or PCMCIA type cards. Each simulator of avionics had to use a dedicated developer application for each project or development. For example, FADEC, a fuel system equipment, uses a dedicated simulation equipment called the Portable Maintenance Access Terminal (PMAT). Due to PMAT's export license (E / L), FADEC could be validated using the ARINC data injection capabilities of portable test equipment. Of course, data can be simulated using the COTS application provided on the card itself, but there are various limitations such as creating a separate DB for each test, dynamic simulation, or inconvenience of the user interface.

Therefore, the portable test equipment according to the present invention has developed a new driver, a project-specific DB, and a model-specific scheduling environment in order to integrate the avionics simulation console consisting of four computers into one.

Here, the new driver does not mean a device driver of the card itself, but an interface driver between the simulation engine and the actual I / O card. That is, it provides data read / write function between SE and LRU.

All driver sources are integrated into a Real-time Library (RTL) Project solution file, which consists of separate projects for each driver. Each project is compiled into a dynamic link library. Table 2, shown below, lists the main driver DLLs included in the portable test equipment.

Each driver class uses C Driver as the base class, and overrides the virtual functions defined in the C Driver class to define the detailed behavior of each driver. In other components, you can use the pointer of the driver object to link directly and load it through SE's IO Manager.

In order to implement portable test equipment, in addition to the addition of drivers, a scheduling table and DB for interworking with Real LRUs must be implemented. The DB defines input / output data of LRUs per project and dynamic characteristic values per stream. For example, in the case of a MUX bus, RT (remote terminal) and sub address must be defined, and socket stream must define IP address appropriately for each data block. The scheduling table of the portable test equipment is determined by the test environment and the requirements, and the REAL / SIM can be selectively defined in the avionics integrated system as the actual equipment or model is selectively configured according to the test purpose.

If the entire navigation system is configured as a SIM using portable test equipment, the functionality of the mission equipment can be validated by applying various test scenarios without having to test flight on the ground.

The portable test equipment serial driver was developed using a combination of I / O configuration modules from Surion MEP SIL. MUX and ARINC are PCMCIA type and can be developed without changing H / W.However, serial card (RS-422) uses the same EXC-M4KSerial module as the VME board and PCI board. Develop.

As a method of verifying portable test equipment, it is validated using EXALT (Excalibur Analysis Laboratory Tools), a COTS data monitoring tool. EXALT is an application that can simultaneously monitor multiple bus types, including MIL-STD-1553, ARINC-429, Discrete, and RS-422 / 422/485, and provides the user with a variety of formats.

Figure 3 is a monitoring of the ARINC-429 data between the RALT model and MC on the portable test equipment, it can be seen that the dynamic altitude value is simulated.

4 monitors the MUX data between the GPS / INS mall and the MC on the portable test equipment.

5 is a floor chart showing a PTE development procedure according to the present invention.

Referring to FIG. 5, as a method for developing a portable avionic system test equipment, a corresponding LRU (MC (mission computer), MFD (multi-function display), CDU (control display), Center Pedestal based on the ICD (Interface Control Doc) (Central Support)) step (A) of creating a database, step (B) of importing the created LRU database into a project, and step of generating DBSim.dll through an export command ( C), determining a portable test equipment (PTE) model type (D), defining a frame for scheduling the PTE model (E), and defining an interworking with the SE (serial) model manager. A process of developing a PTE model, the method comprising: (F) and verifying (G) the PTE model through a debug function; And generating a new MFC AppWizard (DLL) project (100), setting the generated project (200), determining a PTE I / O signal (300), and inheriting from a C driver base class. Adding a received new driver (400), overriding a virtual function to implement the new driver (500), connecting to a stream class defined in the PTE model (600), and I A process for developing a driver having a step 700 of defining characteristic values of / O is included.

In the step (D), the PTE model type is preferably one of ICD, Behavior, and Dynamic.

Here, in the step (D), if the PTE model type is Behavior, it may further comprise the step (D-1) for implementing the handshaking (handshaking) logic of the model.

In addition, in the step (D), if the PTE model type is Dynamic, it may further include the step (D-1) of adding flight model interworking when implementing the handshaking logic of the model.

On the other hand, in the step 300, the PTE I / O signal is preferably any one of the avionics input and output signals including MUX, ARINC, Serial and the like.

In conclusion, portable test equipment allows simulation of all input and output signals in terms of avionic integration.

Thereby, almost all functions of the equipment can be verified without purchasing expensive simulation equipment.

In the future, portable avionics integration devices will reduce the risk of integration between other systems and leverage common portable integrated system architectures for the avionics system as well as other systems (fuel, engine and flight control).

This can reduce development schedules, reduce costs, and reduce development risks.

Although the embodiments of the present invention have been described above, various modifications may be made by those skilled in the art. Therefore, it should be understood that the present invention should not be construed as being limited to the above embodiments, but should be construed in accordance with the following claims.

Claims (5)

As a method of developing a portable avionics test equipment,
Generating (A) a database of the corresponding LRU (mission computer), MFD (multifunction display), CDU (center display), and Center Pedestal based on the Interface Control Doc (ICD);
Importing the generated LRU database into a project (B);
(C) generating a DBSim.dll through an export command,
Determining a portable test equipment (PTE) model type (D),
(E) defining a frame for scheduling the PTE model;
Defining (F) the linkage with the SE (serial) model manager,
A process of developing a PTE model comprising the step (G) of validating the PTE model via a debug function; And
Creating a new MFC AppWizard (DLL) project (100),
Setting the generated project (200);
Determining 300 a PTE I / O signal;
Adding a new driver inherited from the C driver base class (400),
Overriding a virtual function to implement the new driver (500),
Associating with a stream class defined in the PTE model (600);
A process for developing a hand-held avionics system test equipment comprising the step of developing a driver (700) defining an I / O related characteristic value. The method of claim 1,
In the step (D),
PTE model type is a portable avionic system test equipment development method, characterized in that any one of ICD, Behavior, Dynamic. 3. The method of claim 2,
In the step (D),
If the PTE model type is Behavior, further comprising the step (D-1) of implementing the handshaking logic of the model. 3. The method of claim 2,
In the step (D),
If the PTE model type is Dynamic, further comprising the step (D-1) of adding flight model interworking when implementing the handshaking logic of the model. The method of claim 1,
In step 300,
The PTE I / O signal is a portable avionic system test equipment development method, characterized in that any one of the avionics input and output signals including MUX, ARINC, Serial and the like.

Images