Looking for Thunderbolt 3 device? Click here.
High density ARINC can be used for development or deployment
Designed for embedded, laboratory and simulator applications, the RCEI-830A supports maximum data throughput on all channels while providing onboard message scheduling, label filtering, multiple buffering options, receive message time-tagging and error detection, and IRIG-B receiver (AM or DC/TTL) and generator (DC/TTL).
Multiple channel configurations provide optimum application flexibility
The RCEI-830A supports up to 32 ARINC 429 channels, (16 receivers and 16 transmitters), and is available in various ARINC 429 channel counts. Configurations with ARINC 717 provide support for both ARINC 717 HBP (Harvard Bi-Phase) and BPRZ (Bi-Polar Return to Zero) across a range of bit rate/sub-frame combinations. Optional support includes avionics discrete I/O, and IRIG time synchronization. Various bus adapter configurations are also available, supporting PCI, PCI Express®, and CompactPCI platforms.
Software tools minimize integration effort, shorten time to implementation
Abaco Systems’ software tools and solutions significantly reduce the time required to integrate ARINC 429 and other avionics protocols into an application. Included with the RCEI-830A is Abaco Systems’ flexible, high-level API support for Microsoft Windows® 7, 8, 8.1, 10, Server 2012 R1/R2, Vista, XP, VxWorks®, Linux Kernel Versions 2.6 and 3.x, and Integrity operating systems. This powerful API supports multiple cards, and is compatible with Abaco Systems' API support on PCI, PCI Express®, PC/104-Plus, Express Card, CompactPCI/PXI, and XMC platforms. Support for BusTools/ARINC, our flexible, Windows-based GUI Bus Analyzer, LabVIEW and LabVIEW Real-Time is optionally available.
Software & Drivers
Request a Quote
Contact an Expert
Thunderbolt 3: a path forward for avionics data bus interfaces and Abaco’s ARINC 615-3 data loader
Engineers using avionics data bus interfaces and data loaders are facing a growing problem: the demise of the PCMCIA and ExpressCard interfaces, and the inadequacy of USB as an alternative. There is, however, a way forward.