Search Results

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.

The architecture is a concept very broad and important that is directly connected to the realization of a system. It defines what the system is capable of doing, how it accomplishes its mission and how the system is. Currently, the development of system architectures is considered a domain of knowledge where science meets art. In some specific areas, the methods on the development of system architectures are already well formalized. However, when analyzing the evaluation of system architectures such as those for multi-domain control systems, it is clear that there is still much room for rationalization. In these cases, the search for new methods for the evaluation of system architectures is currently in the state of art. In this work we discuss methods used in the verification and validation of control systems architectures of cyber-physical systems based on models and systems metrics.

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.

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.

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.

The increasing use of Global Navigation Satellite Systems-GNSS in future Aeronautical Navigation Systems-ANS is a current trend in the aeronautical operation and regulation communities. This trend implies the adoption of elements and interactions of a degree of complexity that is still being discussed around the world. Faced with that, we believe that a requirements based approach is an effective tool to deal with such highly complex and integrated systems. In this work we discuss a requirements based approach to future Aeronautical Navigation Systems based on Global Navigation Satellite Systems. To do that, we first briefly present the concept of Communication, Navigation, Surveillance/Air Traffic Management - CNS/ATM, and the current and potential benefits of the adoption of its paradigms.

Companies are gradually developing: 1) complex and/or highly integrated systems including vehicles (as satellites, airplanes, cars, etc.) or equipment (as computers, cell phones, no breaks, etc.) to use under 2) increasingly varied or inhospitable environments, and to survive under 3) increasingly long life cycles and unavoidable changes in staff & facilities & technologies. The overall decision to use (by time, cost, quality, of functions, services, etc.) such end systems under 2 require 4) high Dependability (Reliability, Maintainability, Availability, Correction, Safety, Security, etc.) of them. The overall survival in use (by health monitoring, housekeeping, retrofit, upgrade, etc.) of such end systems under 3 require 5) high Suportability (Maintainability, Adaptability, Availability, Robustness, etc.) of them coupled with the support systems.

Currently, aerospace and automotive industries are developing complexand/or highly integrated systems, whose services require greater confidence to meet a set of specifications that are increasingly demanding, such as successfully operating a communications satellite, a commercial airplane, an automatic automobile, and so on. To meet these requirements and expectations, there is a growing need for fault treatment, up to predict faults and monitor the health of the components, equipment, subsystems or systems used. In the last decades, the approaches of 1) Fault Prevention, 2) Fault Detection/Tolerance and 3) Fault Detection/Correction have been widely studied and explored.

Current systems such as: satellites, aircrafts, automobiles, turbines, power controls and traffic controls are becoming increasingly complex and/or highly integrated as prescribed by the SAE-ARP-4754 Standard. Such systems and their control systems use many modes of operation and many forms of redundancy to achieve high levels of performance and high levels of reliability under changing environments and phases of their lifecycle. The environment disturbances, environment variability, plant non-linear dynamics, plant wear, plant faults, or the non-symmetric plant operation may cause de-synchronization in phase or time among: 1) simultaneous units in the same normal mode of operation; 2) successive units in successive normal modes of operation; 3) main and spare units from normal to faulty modes of operation. So, techniques to reduce those causes or their effects are becoming important aspects to consider in the design of such systems.

Current systems such as satellites, aircrafts, automobiles, turbines, power controls and traffic controls are becoming increasingly complex and/or highly integrated as prescribed by the SAE-ARP-4754a Standard. Such systems operate in a real time distributed environment which frequently requires a common knowledge of time among different devices, levels and granularities. So, temporal correctness is mostly needed, besides logical correctness. It can be achieved by hardware clocks and devices, software clocks and algorithms, or both, to avoid or tolerate, within appropriate margins, the time faults or failures that may occur in aerospace and automotive systems. This paper presents an overview of clock synchronization algorithms and their uses in aerospace and automotive systems. It is based on a review of the literature, discussion and comparison of some clock synchronization algorithms with different policies.

Real-time critical systems are those whose failures may cause loss of transactions/data, missions/batches, vehicles/properties, or even people/human life. Accordingly, some regulations prescribe their maximum acceptable probability of failures to range from about 10−4 to 10−10 failures per hour. Examples of such systems are the ones involving nuclear plants, aircrafts, satellites, automobiles, or traffic controls. They are becoming increasingly complex and/or highly integrated as prescribed by the SAE-ARP-4754A Standard. Those systems include, most of the time, real time critical software that must be specified, designed, implemented, validated, verified and accredited (VVA). To do that, models, specially the V-Model, are frequently adopted, together with methods and tools which perform software VVA to ensure compliance (of correctness, reliability, robustness, etc.) of software to several specific standards such as DO178-B/DO-178C (aviation) or IEC 26262 (automotive) among others.

The aerospace and automotive electronic systems are getting more complex and/or highly integrated, as defined by ARP 4754A, making extensive use of microelectronics and digital memories which, in turn, operates in higher frequencies and lower voltages. In addition, the aircraft are flying in higher altitudes, and polar routes are getting more frequent. These factors raise the probability of occurrence of hazardous effects like the Single Event Upsets in their embedded electronic systems. These must be designed in a way to tolerate and assure the immunity to the Single Event Upsets, based upon criteria such as reliability, availability and criticality. This paper proposes an overview of an assurance process of immunity of embedded electronic systems to Single Event Upsets caused by ionizing particles by means of a review of literature and an analysis of standards as ECSS-E-ST-10-1, NASA Single Event Effects Criticality Analysis and IEC TS 62396-1.

Internet of Things (IoT) for real-time applications are demanding more and more high performance, precision, accuracy, modularity, integration, dependability and other attributes in a complex and/or highly integrated environment. Such systems need to provide coordination among the integrated components (e.g. sensors, computer, controller and networks) for enabling the application to take real-time measurements and to translate into controllable, observable and smart actions with strict timing requirements. Therefore, coordination and synchronization are required to ensure the controllable, observable and smart actions of real-time IoT systems. This paper shows the design issues about the coordination and synchronization in the internet of things applied to real-time applications. We also show the current coordination and synchronization techniques and their design issues when applied to IoT systems.

In this work we discuss current trends driving the aerospace and automotive systems architectures. This includes trends as: 1) pos-globalization and regionalization; 2) the formation of knowledge oligopolies; 3) commonality, standardization and even synergy (of components, tools, development process, certification agents, standards); 4) reuse and scalability; 5) synergy of knowledge and tools convergence; 6) time, cost and quality pressures and innovation speed; 7) environmental and safety issues; and 8) abundance of new technologies versus scarcity of skilled manpower to apply them.

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.

Modeling and Simulation (M&S) of dynamic systems based on computers is a multidisciplinary field that involves several knowledge areas and tools, and is broadly used in all development areas of space industry such as rocket and satellite design and construction. Once space systems are divided into several subsystems for ease of engineering, their models are divided the same way for the same reason. Such models may be done using different computational tools that are based on either physical flows, informational flows, or hybrid flows, depending on the subsystem nature. This is specially true for a satellite propulsion subsystem, and its physical (volume, mass, energy, enthalpy, entropy, linear momentum, etc.) flows. This paper presents the modeling and simulation of a satellite propulsion subsystem by physical and signal flows. To accomplish this task, two different computational tools were used: AMESim and MatLab.

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

In this work we discuss some types of simulation environments and laboratories, 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 (“stand-alone”, PIL, HIL, MIL, DIS, HLA, etc.), and especially, their environments (discrete, continuous, hybrid, etc.) and laboratories (physical, computational, hybrid, etc.), and their applications to the simulation and control of aerospace vehicles. This is illustrated by some examples driven from the aerospace industry.

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