Reliability
is the only thing that matters in the aerospace world. A new technology
may be impressive, but if it isn’t reliable, it’s worthless
on the flight line. MIL-STD-1553 is still so important because it’s
so reliable. It has a well-deserved reputation for delivering commands
when a pilot wants to turn left, drop a bomb or fire a missile. We also
have a well-deserved reputation for delivering the products that get
aerospace applications off the ground.
Products
|
|
This
advanced solution offers a less expensive architecture than regular
1Mbit 1553, while providing up to 10 times the data throughput.
This interface is an excellent choice for flight controls, actuators,
electro-pneumatic controllers or similar applications of standard
1553 requiring higher data rates.
|
|
AFDX
is a deterministic protocol for real time application on Ethernet
media, also known as ARINC 664 Part 7. AFDX is intended for aircraft
flight critical interfaces, including Engines, Flight Controls,
Navigation Systems. With both hardware-based and software loadable
AFDX, we support AFDX across evolving platforms to protect your
avionics investment.
|
|
Our
ARINC solutions provide feature-rich functionality, ease of use
and exceptional performance for embedded, test and simulation
applications. Most interfaces offer individual channel programmability
for source or sink, and an optional IRIG B receive time stamp.
The PCI and PMC interfaces offer on-board transmit channel listen
feature. They provide a user-friendly design to the host system
with on-board management of transmission, receive, and data logging
execution.
|
|
The
streamlined, single- or multi-session interface software provides
intuitive Microsoft® Windows®-based ARINC 615-3/603 data
loading. The single-session software loads one ARINC 615-3/603
compatible LRU at a time. The multi-session integrated hardware/software
solution supports up to 16 simultaneous upload or download sessions
with ARINC 615/603 compatible LRUs.
|
|
By
taking advantage of the revolutionary advances in capacity, performance
and cost-effectiveness of a new generation of programmable logic
devices (PLDs), we can provide military system designers with
new and exciting protocol communications options. The military
electronics industry is rapidly moving to deploy these higher
levels of integration provided by System on a Chip (SoC) or integrated
I/O implementations.
Various configurations of IP Core are available, including lightweight,
no-API required, 1MBit, 10MBit multi-drop, and 10MBit point to point MMSI
Cores.
|
|
GE
is your partner for Avionics interfaces, including catalogue
(COTS) and Custom and Build to Order products. These products
are application specific custom builds or software/hardware/configuration
modifications from our COTS products and have pricing and delivery
quoted per order.
|
|
Our
powerful application software gives you simplified control over
receive, transmit, logging and analysis functions. You can analyze
bus traffic, quickly generate or modify messages and view received
data in engineering units. Our tools provide a full suite of
advanced features for use in the laboratory, in flight, on the
flight line, or in any application requiring real-time data acquisition
and analysis.
|
|
We
offer a wide range of intelligent MIL-STD-1553 interface hardware
to meet demanding application needs. Our 1553 product line combines
high-speed encoding/decoding, large onboard memory, intelligent
protocol processing and advanced board-level functionality. This
enables accurate buffering and recording of bus traffic with
no data loss while simultaneously scheduling 1553 messages without
host intervention.
|
|
Interface
to a wide range of avionics protocols with our single-board, multi-protocol
solutions for PCI, CompactPCI, PC/104, PCMCIA, VME, VXI and PMC
platforms. Many of our ARINC 429 boards offer options for additional
commercial avionics protocols. For additional flexibility, we offer
modular board solutions for PCI, CompactPCI, VME and VXI platforms.
Optionally supported protocols include: ARINC 561/568 6-wire, ARINC
573/717, ARINC 419, ARINC 582, ARINC 708/453, RS-232/422/485, ARINC
615-3 and CSDB.
|
|
TTEthernet
(Time-Triggered Ethernet) is a scalable, open real-time Ethernet
platform used for safety-related applications primarily in avionics,
transportation and industrial automation. TTEthernet sets new
standards for flexibility, modularity and scalability in Ethernet-based
systems. It is compatible to IEEE 802.3 Ethernet and integrates
transparently with Ethernet network components. TTEthernet has
been designed for safe and highly available real-time applications.
This technology offers deterministic real-time communication
and TCP/IP Ethernet traffic in parallel on the same network.
It enables the integration of standard Ethernet controllers and
allows implemention in hardware or software. TTEthernet simplifies
the design of fault-tolerant and high availability solutions.
|
|
TTP
(Time-Triggered Protocol) is an open and modular control system
platform technology that supports the design of upgradeable,
reusable and easy-to-integrate systems. As a time-triggered fieldbus,
it can significantly impact the design of modern electronics
and control system architectures for next-generation vehicles
and industrial applications.
As a fault-tolerant time-triggered
protocol, TTP provides autonomous fault-tolerant message transport
at known times and with minimal
jitter by employing a TDMA (Time-Division Multiple Access)
strategy on replicated communication channels. TTP offers fault-tolerant
clock synchronization that establishes the global time base
without
relying on a central time server.
TTP provides a membership service
to inform every correct node about the consistency of data
transmission. This mechanism can
be viewed as a distributed acknowledgment service that informs
the application promptly if an error in the communication system
has occurred. If state consistency is lost, the application
is notified immediately. Additionally, TTP includes the service
of clique avoidance to detect faults outside the fault hypothesis,
which cannot be tolerated at the protocol level. |
|