Search Results

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.

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.

One challenge that the space, aeronautical and automotive industries are facing today is the fast growing number of vehicles versus the slowly growing number of useful orbits, routes, and speedways. Furthermore, the adoption of “free-flight”, “speed-drive”, etc. policies in the near future will only aggravate it. All these factors increase the risk of collisions and the frequency of deviation maneuvers to avoid them. But they also create the opportunity to devise policies to mitigate such problems, including algorithms to propagate the uncertainties in vehicle motions and to predict the risk of their collisions. This work discusses the development and simulation of an algorithm for the propagation of navigation uncertainties in the trajectory of aerospace vehicles, to minimize the risk of collisions. The scenario of Satellites Formation Flying shall be used for the simulations, with focus on the prediction of the collision probability.

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 constant challenge for the mobility engineering is to build correctly, the right product at the right time, cost and quality. This challenge gives opportunities to adopt new paradigms in system development, especially in generation, migration and tests of controller codes. This work presents the automatic generation, migration, and tests of real time code to an embedded controller. This is part of the Attitude and Orbit Control System (AOCS) for the Multi-Mission Platform (MMP) of the National Institute for Space Research (INPE). The modeling and simulation paradigm associated with automatic code generation makes possible the migration of a real time embedded controller code to a wide variety of target processors and/or Real Time Operating Systems (RTOS) using the same controller model. The MATRIXx (XMath/SystemBuild/AutoCode/DocumentIt) modeling and simulation environment was used to analyze and design the controller and generate its real time code.

This work presents the first part of the analysis, design and simulation of the reconfigurable control architecture for the Multi-Mission Platform (MMP), a generic service module currently under design at INPE. Its control system can be switched among nine main Modes of Operation. The implementation followed the specifications when they were found, otherwise it was designed. The manager block of the control system was implemented as a finite state machine. The tests were based in simulations with the MatriX/SystemBuild software. They focused mainly on the worst cases that the satellite is supposed to endure in its mission.

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

This work presents the distributed simulation of the longitudinal mode of an aircraft by using the DoD High Level Architecture (HLA). The HLA is a general-purpose architecture for simulation reuse and interoperability. This architecture was developed under the leadership of the Defense Modeling and Simulation Office (DMSO) to support reuse and interoperability across the large numbers of different types of simulations developed and maintained by the DoD. To do this, the transfer function of the longitudinal mode of a hypothetical aircraft was implemented by means of a SystemBuild/MATRIXx model. The output of this model was connected to a Run-Time Infrastructure (RTI) and monitored on a remote computer. The connection between the model and the RTI was implemented by using a wrapper which was developed in C++. The HLA RTI implementation used in this work was the poRTIco.

Computer systems aboard aerospace vehicles have become more and more distributed in an attempt to solve “real-life” problems such as commonality and longevity of components and subsystems. On the other hand, distributed systems pose a much bigger challenge in system design than traditional, “monolithic” systems, whereby functions are performed by a single component combining hardware and software. “Determinism” (predictability in the occurrence of events), “causality” (temporal ordination of occurrence of events) and “synchronism” (simultaneousness in the occurrence of events) can be pointed out as major challenges in system design. This paper shall survey methods of analyzing determinism in network communications in distributed computer systems aboard aerospace vehicles in different network topologies using a representative model.

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 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.

This work presents the analysis, design and simulation of the reconfigurable control architecture for the contingency mode of the MultiMission Platform (MMP). The MMP is a generic service module currently under design at INPE. Its control system can be switched among nine main Modes of Operation and other Sub-Modes, according to ground command or information coming from the control system, mainly alarms. The implementation followed the specifications when they were found, otherwise it was designed. They cover operations from detumbling after launcher separation and solar acquisition, to achieving payload nominal attitude and orbital corrections maneuvers. The manager block of the control system was implemented as a finite state machine. The tests are based in simulations with the MatriX/SystemBuild software. They focused mainly on the worst cases that the satellite is supposed to endure in its mission, be it during modes or transitions between modes and submodes.

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

This paper presents some techniques for fault diagnosis in aerospace and automotive systems. A diagnosis technique is an algorithm to detect and isolate fault components in a dynamic process, such as sensor biases, actuator malfunctions, leaks and equipment deterioration. Fault diagnosis is the first step to achieve fault tolerance, but the redundancy has to be included in the system. This redundancy can be either by hardware or software. In situations in which it is not possible to use hardware redundancy only the analytical redundancy approach can be used to design fault diagnosis systems. Methods based on analytical redundancy need no extra hardware, since they are based on mathematical models of the system.

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.

The Multimission Platform (MMP) is a generic service module currently in Project at INPE. In the 2001 version, its control system can be switched between nine main Operation Modes and other submodes, according to information from satellite sensors and ground commands. The Nominal Mode stabilizes the MMP in three axes and takes it to a nominal attitude, using three reaction wheels. Each wheel has coarse and fine acquisition submodes. The use of multiple modes of control for specific situations frequently is simpler than projecting a single controller for all cases. However, besides being harder to warrant its general stability, the mere switching between these submodes generates bumps, which can reduce the performance and even damage the actuator or plant. In this work, we present an application of diverse methods to smooth the transition between control submodes of the Nominal Mode of the MMP.