Search Results

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.

In this work we discuss the fault avoidance and the fault tolerance approaches for increasing the reliability of aerospace and automotive systems. This includes: the basic definitions/concepts (reliability, maintainability, availability, redundancy, etc.), and characteristics (a priori analysis, a posteriori analysis, physical/hardware redundancy, analytical/software redundancy, etc.) of both approaches, their mathematical background and models (exponential, Weilbull, etc.), their basic theory, their methods and techniques (fault trees, dependence diagrams, Markov chains, etc.), some of their standards (SAE-ARP4761, AC 25.1309, etc.) and simulation environments (Cafta, etc.), and their applications to the reliability analysis and reliability improvement of aerospace and automotive vehicles. This is illustrated by some examples driven from the aerospace and automotive industries.

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.

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

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

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.

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.

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 effect of sharing bus between the control system and the other devices connected to the bus foreigner to control. These last devices are called interferences. We intented to show, through simulations, the influence of sharing bus on real time control systems performance. To compare effects, we choose the CanBus protocol where the medium access control is event driven; and the TTP protocol where the medium access control is time driven.

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.

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.

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.

Many control systems switch between control modes according to necessity. That is often simpler than designing a full control to all situations. However, this creates new problems, as determining the composed system stability and the transient during switching. The latter, while temporary, may introduce overshooting that degrade performance and damage the plant. This is particularly true for the MultiMission Platform (MMP), a generic service module currently under design at INPE. Its control system can be switched among nine main Modes of Operation and other submodes, according to ground command or information coming from the control system, mainly alarms. It can acquire one and three axis stabilization in generic attitudes, with actuators including magnetotorquers, thrusters and reaction wheels.

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.

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.

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.

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.

Resistance Spot Welding is a manufacturing process widely used in several industrial segments, such as automotive, electronics, aerospace and others. It stands out from other welding processes, as it does not require addition material to join parts. This type of process needs to be robust and reliable in order to ensure the quality of the welded joint produced, as any variation in the quality of the weld point can affect the functionality and safety of the final product. The resistance spot welding process uses different technologies and operating sequences that depend on various characteristics, factors and parameters. The combinations and values of these allow for numerous possibilities, making their adjustments time-consuming, costly and exhaustive, so it is necessary to apply statistical techniques to optimize the process. In the literature, it is possible to find several statistical techniques for the optimization of the process.

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.