soultrain escreveu:O Rafale usa uma arquitectura que começou a ser desenhada pela ASAAC (Allied Standards Avionics Architecture Council) que deu lugar à norma STANAG 4626. É o que no Rafale é chamado MDPU (Modular Data Processing Unit). Modular porque o Software é independente do processamento, ou seja, a qualquer altura pode-se aumentar a capacidade de processamento sem ser necessário alterar código.
[[]]'s
A ASAAC (
http://en.wikipedia.org/wiki/Allied_Sta ... re_Council ) definiu um conjunto de padrões de arquitetura no campo do
IMA (Integrated Modular Avionics).
O IMA é usado como padrão desde a decada de 90 no campo militar e civil.
O F-22 e os caças de 4a geração empregam essa filosofia de arquitetura.
No Rafale o IMA-Integrated Modular Avionics se chama MDPU, no F-22 CIP, no F-16 MMC, no 777 AIMS, no 787 Common Core System, na familia Falcon EASy-Enhanced Avionics System e assim por diante.
Com relação a norma da OTAN STANAG 4626:
STANAG 4626 is a NATO standard which define a set of Open Architecture Standards for Avionics Architecture, particularly in the field of Integrated Modular Avionics. The purpose of this standard is to establish uniform requirements for the architecture for Integrated Modular Avionics (IMA) systems as defined by the ASAAC program.
[edit]History
This STANAG was proposed by the UK Ministry of Defence, and originated from the ASAAC effort. As for ASAAC, many major European Avionics companies participate in its definition, such as:
BAE Systems
GE Aviation Systems (formerly Smiths Aerospace)
Dassault Aviation
Thales Group
EADS
ESG Elektroniksystem- und Logistik-GmbH
It is believed that the IMA concept originated with the avionics design of the fourth generation jet fighters. It has been in use in fighters such as Lockheed Martin F-22 and F-35, or Dassault Aviation Rafale since the beginning of the '90s. Standardization efforts were ongoing at this time (see ASAAC or STANAG 4626), but no final documents were issued then.
It must be noted that there is no overall hardware or software standard that defines all the mandatory components used in an IMA architecture. However, parts of the API involved in an IMA network has been standardized, such as:
- ARINC 653 for the software avionics partitioning constraints to the underlying Real-time operating system (RTOS), and the associated API
- AFDX for the data network bus.
ARINC 653 (Avionics Application Standard Software Interface) is a software specification for space and time partitioning in Safety-critical avionics Real-time operating systems. It allows to host multiple applications of different software levels on the same hardware in the context of a Integrated Modular Avionics architecture.
Como vc pode afirmar que a capacidade de processanento do Rafale é o dobro do F-22? Especulação? Realmente continuo curioso.
[]s
OBS.:
Gripen NG:
Design for Flexibility and Security
Gripen NG takes advantage of the latest
ARINC 653
integrated modular avionics
standard that provides for the separation
of critical functions onboard the aircraft.
ARINC 653 sets out new design rules for
safety, security and the integration of both
common and user-specific capabilities.
Modular object-orientated software architecture
allows system changes to be
made, verified and certified in an efficient
manner. Each ARINC 653 partition can
isolate an individual customer’s specific
data. This makes it possible to host several
software criticality levels in the same
computer. Most significantly it allows
critical and non-flight critical application
software to be kept completely apart.
With many current avionics systems almost
every avionics change forces the user to
reverify the entire aircraft each time, to
ensure that flight safety functions have
not been affected. With Gripen NG, those
critical functions are never touched when
a user adds new operational capabilities to
the aircraft. This makes the upgrade and
modification schedule speedy, and much
less expensive.
The use of open standards across all aspects
of the avionics core computer system (i.e.
ARINC 653, MIL-STD-1553 and Ethernet),
provides easier and cheaper development of
functions to customers and partners, with
none of the expense and complication of
propriety solutions.