Search Results

This work presents the identification of the longitudinal mode of an aircraft by using time and frequency response methods. To do this, the transfer function was identified based on the sampled response to a step input. The transfer function was validated comparing the model step response with the original system step response. The identification of the system transfer function was performed by using the Fast Fourier Transform (FFT) and Bode Graphs methods. The model validation quantification was performed by means of the mean quadratic-error method applied to the step response difference. Based on that, the identified model was considered to be quite representative, thus proving the suitability of the applied methods.

This works presents the generation and customization of real time code for embedded controllers using a modeling and simulation environment. When the controller model is considered satisfactory, the developers can use a code generation tool to build a real time source code capable to be migrated to an embedded target processor. The code generation tool used is capable to generate real time code in ANSI C or ADA 95 languages. This process can be customized to adequate to a target processor and/or a Real Time Operating System (RTOS). The code customization can be achieved using a specific Template Programming Language (TPL) that specifies how the code will be generated. This technique makes it possible the instantiation of real time embedded controllers code using the same controller model to a wide variety of target processors and/or RTOSs.

In this work we present a new procedure for customizing, in the desired format, requirements reports generated by a Requirements Engineering Environment. This environment includes tools for: 1- capturing textual and pictoric requirements; 2- templating requirements documents that can be adjustable to the formats required by the certification authorities or system engineering groups; 3- translating features from/to the main word processors used in the industry (Word, Excel, etc. formats); 4- managing requirements configuration. It provides gains of productivity, correctness, reusability, traceability, coverage, etc, improving the efficiency of the projects. The procedure emphasizes items 2 and 3, and is illustrated with some examples driven from the aerospace industry.

This paper presents the first of four parts of the academic design of an Attitude Control System (ACS) for the Multi-Mission Platform (MMP) and its migration to a Real Time Operating System. The MMP is a three axis stabilized artificial satellite now under development at the National Institute for Space Research (INPE). Such design applied some software engineering concepts as: 1)visual modeling; 2)automatic code generation; 3)automatic code migration; 4)soft real time simulation; and 5)hard real time simulation. A block diagram based modeling and a virtual time simulation of the MMP ACS in its nominal operational mode were built in the MatrixX 7.1 environment satisfying the three axis pointing and stabilization requirements. After that, its AutoCode module was used to generate C ANSI code representing the block diagram model. Time characteristics were added to the ACS generated code to make it the real time control software of MMP nominal operational mode.

This paper presents the automatic code generation process of the academic design of an Attitude Control System (ACS) for the Multi-Mission Platform (MMP). The MMP is a three axis stabilized artificial satellite now under development at the National Institute for Space Research (INPE). Such design applied some software engineering concepts as: 1)visual modeling; 2)automatic code generation; 3)automatic code migration; 4)soft real time simulation; and 5)hard real time simulation. A block diagram based modeling and a virtual time simulation of the MMP ACS in its nominal operational mode were built in the MatrixX 7.1 environment satisfying the three axis pointing and stabilization requirements. After that, its AutoCode module was used to generate C ANSI code representing the block diagram model. Four operating systems were used for code migration: 1)Windows 2000; 2)Mandrake Linux 10.1; 3)RedHawk Linux 2.1; and 4)RTEMS 4.6.2.

A major trend in modern aerospace and automotive systems is to integrate computing, communication and control into different levels of the vehicle and/or its supervision. A well fitted architecture adopted by this trend is the Common Bus Network Architecture. A Networked Control System (NCS) is called when the control loop is closed through a communication network. The presence of this communication network introduces new characteristics (sharing bus, delays, jitter etc.) to be considered at design time of a control system. This work focuses on the influences of data bus protocols on an aircraft Fly-By-Wire (FBW) networked control system. We intent to show, through simulations, the influences of sharing bus on a real time control system. To compare effects, we choose the CAN Bus protocol where the medium access control is event driven; and the TTP protocol where the medium access control is time driven.

In this work we discuss some types of simulation architectures and standards, their characteristics and applications to the simulation and control of aerospace vehicles. This includes: the basic definitions, types and characteristics of simulators and simulations (physical, computational, hybrid, etc.; discrete events, discrete time, continuous time, etc; deterministic, stochastic, etc.) their basic compromise (simplicity x fidelity), their man-machine interfaces and interactions (virtual, constructive, live, etc.), their evolution law (time, events, mixed, etc.), their architectures (“stand-alone”, PIL, HIL, MIL, DIS, HLA, etc.), their standards (OMBA, SIMNET, ALSP, DIS, HLA 1.3, HLA 1516, ASIA, AP2633, etc.) and their applications to the simulation and control of aerospace vehicles. This is illustrated by some examples driven from the aerospace industry

Nowadays, given the shrinking budgets and deadlines of the aerospace and automotive industries, the importance and need of the requirements engineering is becoming more and more evident. This means that progressively more users face a difficult task on the different environments of project development: 1) to write better requirements; and 2) to do it faster than ever. It would be nice if they had some tools to help them and abbreviate such a difficult task. This work summarizes the development of a new tool that does exactly that. Its wizard guides the user through the steps necessary to create good requirements when writting a requirements document, depending on the kind of requirements document desired. For example: there are significant differences between user requirements and system requirements documents. The wizard script is composed by a serie of questions related to the parts of the scheme to build a complete and effective requirement.

This paper aims at discussing the use of dissimilar hardware architecture to mitigate DESIGN ERRORS in a flight control system application, as one of the possible design techniques that, combined with the usage of development processes, will satisfy the safety objectives for airborne systems. To accomplish its purpose, the paper starts by understanding the origins of DESIGN ERRORS in micro-coded devices and the concerns of airworthiness certification authorities (or simply certification authorities from now on). After that, an overview of the aeronautical industry efforts in terms of development processes and certification requirements to mitigate DESIGN ERRORS will be presented. At this point, the dissimilar architecture is proposed as an effective mean to mitigate the problem of DESIGN ERRORS. Finally, a Flight Control System application using dissimilar architecture is proposed as a case study.

This paper presents the preliminary results of an "a posteriori" exercise of application of a Requirements Traceability Automation Tool (RT tool) to a set of documents. The documents have been prepared according to established Space System Engineering methodologies and with attention to text quality, but without attention to requirements traceability because the processes and methodologies used during their preparation predates the emergence of the processes and methodologies developed by Requirements Engineering (RE). This study is intended to determine some of the benefits of using a RT tool when compared with the previously used processes and methodologies. The set of documents under scrutiny have been prepared in the frame of the development of the CBERS-3 satellite (China-Brazil Earth Resources Satellite) and is composed of system, subsystem and equipment specification and covering documents related to the Electrical Power Subsystem (EPS) of the satellite.

On several engineering applications high Reliability is one of the most wanted features. The aspects of Reliability play a key role in design projects of aircraft, spacecraft, automotive, medical, bank systems, and so, avoiding loss of life, property, or costly recalls. The highly reliable systems are designed to work continuously, even upon external threats and internal Failures. Very convenient is the fact that the term 'Failure' may have its meaning tailored to the context of interesting, as its general definition refers to it as "any deviation from the specified behavior of a system". The above-mentioned 'deviation' may refer to: performance degradation, operational misbehavior, deviation of environmental qualification levels, Safety hazards, etc. Nevertheless, Reliability is not the only requirement for a modern system. Other features as Availability, Integrity, Security and Safety are always part of the same technical specification, in a same level of importance.

Complex systems such as satellites, aircrafts, automobiles and air traffic controls are becoming increasingly complex and highly integrated as prescribed by the SAE ARP 4754 Standard. They integrate many technologies and they work in very demanding environments sometimes with little or no maintenance due to the severe conditions of operation. To survive such harsh operating conditions, they require very high levels of reliability, to be reached by a diversity of approaches, processes, components, etc. By their turn, the processes of analysis and decision making shall be improved progressively, as experience accumulates and suggests modifications and adaptations. According to this philosophy, in this work, we discuss a proposal for improving the results of the Reliability Analysis and FMEA/FMECA of the CBERS Satellite Program, conducted at the National Institute for Space Research-INPE, since 1987.

In this work we discuss some types of simulators and simulations, their characteristics and applications to the simulation and control of aerospace vehicles. This includes: the basic definitions, types and characteristics of simulators and simulations (physical, computational, hybrid, etc.; discrete events, discrete time, continuous time, etc; deterministic, stochastic, etc.) their basic compromise (simplicity × fidelity), their man-machine interfaces and interactions (virtual, constructive, live, etc.), their evolution law (time, events, mixed, etc.), their architectures (“standalone”, PIL, HIL, MIL, DIS, HLA, etc.), their environments (discrete, continuous, hybrid, etc.) and their applications to the simulation and control of aerospace vehicles. This is illustrated by some examples driven from the aerospace industry

Cyber-physical systems are joint instances of growing complexity and high integration of elements in the information and physical domains reaching high levels of difficulty to engineer an operate them. This happens with satellites, aircraft, automobiles, smart grids and others. Current technologies as computation, communication and control integrate those domains to communicate, synchronize and operate together. However, the integration of different domains brings new challenges and adds new issues, mainly in real time distributed control systems, beginning with time synchronization. In this paper, we present a discussion on time synchronization and their effects in distributed cyber-physical control systems. To do that, we review the literature, discuss some time synchronization techniques used in cyber-physical systems, and illustrate them via model and simulation of a system representative of the aerospace area.

Switching controls are those that can switch between control or plant modes to perform their functions. They have the advantage of being simpler to design than an equivalent control system with a single mode. However, the transients between those modes can introduce steps or overshootings in the state variables, and this can degrade the performance or even damage the control or the plant. So, the smoothing of such transients is vital for their reliability and mantainability. This is can be of extreme importance in the aerospace and automotive fields, plenty of switchings between manual and autopilot modes via relays, or among gears via clutches, for example. In this work, we present a first strategy for smoothing transients in switching controls of aerospace and automotive systems.

Systems such as satellites, airplanes, cars and air traffic controls are becoming more and more complex and/or highly integrated. These systems integrate several technologies inside themselves, and must be able to work in very demanding environments, sometimes with few, or none, maintenance services, because of their severe conditions of work. To survive to such severe work conditions, the systems must present high levels of reliability, which are achieved through different approaches and processes. Therefore, it is necessary that the processes of decision analysis and making are progressively improved, taking into account experiences collected before by several technological communities, and then propose efficient modifications in the local processes. These experiences influence the proposition and improvement of several Reliability Standards Series taken by four different approaches and several technological communities.

Systems are becoming increasingly more complex. To follow this increasingly complexity, systems engineering must evolve rapidly with the introduction of new methodologies, processes, tools, etc. Due to this rapid evolution, little attention is dedicated to the study of the history of its evolution. Currently there is the initiative of installation of a chapter of INCOSE (International Council on Systems Engineering) in Brazil and from this initiative emerged the interest of recovering the history of systems engineering in the country. There are indications that the introduction of systems engineering into Brazil occurred in the late 1960's, directly from NASA and that its first applications in Brazil were in Space Systems Engineering. This paper recovers the origins of systems engineering, of its introduction into Brazil, and of its use in space systems engineering.

In this work, the problem of fault detection, isolation, and reconfiguration (FDIR) for Networked-Control Systems (NCS) of aerospace vehicles is discussed. The concept of fault-tolerance is introduced from a generic structure, and a review on quantitative and qualitative methods (state estimation, parameter estimation, parity space, statistic testing, neural networks, etc.) for FDIR is then performed. Afterwards, the use of networks as loop-closing elements is introduced, followed by a discussion on advantages (flexibility, energy demand, etc.) and challenges (networks effects on performance, closed-loop fault-effects on safety, etc.) represented thereby. Finally, examples of applications on aerospace vehicles illustrate the importance of the discussion herein exposed.

Systems such as satellites, aircrafts, automobiles and air traffic controls are becoming increasingly complex and highly integrated, as prescribed by the SAE ARP 4754 Standard. They integrate many technologies and they work in very demanding environments, sometimes with little or no maintenance, due to the severe conditions of operation. To survive such harsh operating conditions, they require very high levels of reliability, to be reached by a diversity of approaches, processes, components, etc. By their turn, the processes of analysis and decision making shall be improved progressively, as experience accumulates and suggests modifications. Most of this can be translated in models. According to this philosophy, in this work, we discuss the use of Model Based Reliability for improving the results of the Reliability Analysis and FMEA/FMECA of a satellite program, as those conducted at the National Institute for Space Research-INPE, since 1979.

Systems such as satellites, airplanes, cars and air traffic controls are becoming more complex and/or highly integrated. These systems integrate several technologies inside themselves, and must be able to work in very demanding environments, sometimes with few or none maintenance services due to their severe conditions of work. To survive such severe work conditions, the systems must present high levels of reliability, which are achieved through different approaches, processes, etc. These unfold in many: levels of aggregation (systems, subsystems, equipments, components, etc.), phases of their lifecycles (conception, design, manufacturing, assembly, integration, tests, operation, etc.), environments (land, sea, air, space, etc.), types of components/applications/experiences/technological communities (nuclear, aerospace, military, automotive, medical, commercial, etc.), leaded by the widespread use of semiconductors.