|
FEATURED PRODUCTS
|
Ethernet/USB for MIL-STD-1553
- IRIG Timetag
- PowerPC user processor
- CompactFlash slot
- Variable amplitude
The OmniBusBox enables computers and networks to interface with up to four MIL-STD-1553 dual-redundant databuses or a combination of MIL-STD-1553 with other protocols via Ethernet or USB.
|
For More Information
800.829.1553
|
|
OmniBus 1553
OmniBus 1553 refers to the MIL-STD-1553 capabilities available for all modular OmniBus platforms. Each module provides one or two dual redundant 1553 channels. Total channel count and functionality depend on the number and type of modules on the platform. All models provide Bus Controller (BC), Remote Terminal (RT), and monitor operation and support all 1553 message types. Models with multi-terminal simulation and error injection are available (see ordering information).
OmniBus 1553 offers ease-of-use and many advanced features. On-board processors automatically handle all protocol related activity, freeing users to focus on their applications.
OmniBus Product Family
Ballard's OmniBus products connect computers or networks to one or more
avionics databuses. Separate web pages provide information on OmniBus
platforms (PCI,
cPCI,
PMC,
VME,
USB/Ethernet), avionics protocols
(MIL-STD-1553,
ARINC 429,
ARINC 708,
ARINC 717,
and CSDB),
serial ports (RS-422/232/423),
and Discrete I/O.
Applications for OmniBus products include testing, simulation, and operational uses of avionics databuses. OmniBus products are built around an intelligent platform that can host one or more protocol modules. This flexible architecture accommodates mixed protocols, high channel counts, and unsurpassed processing power.
Bus Controller
- Specify no-response timeout value up to 102.4 µs in units of 0.1 µs
- Automatic schedule (based on specified message frequencies) or custom schedule, including:
- Multiple frames and programmable frame times
- Programmable inter-message gap times
- Conditional retries and branches for exception processing
- Schedule operation modes:
- Continuous (until explicitly halted)
- Specified number of loops
- Single-step mode (for debugging)
- Configure schedule to wait for each message to be triggered or for a single starting trigger
- Custom protocols are supported by variable word lengths and programmable pre-sync pulses
- Programmable sync out signal on all or selected messages (multiple sync lines available)
- Insert aperiodic messages into a running BC schedule
Remote Terminals
- Multi-terminal simulation with up to 31 RTs (Level B4 or higher channels)
- Configurable response time for MIL-STD-1553A or B (default)
- Specify a response time value up to 25.5 µs, in units of 0.1 µs
- Programmable status word bits
- Auto Busy option automatically sets the Busy bit of the status word after each command
- Programmable sync out signal on all or selected messages (multiple sync lines available)
- Configure/legalize all or selected SAs and mode codes
- Support for all 1553B mode codes
- Selectable mode code subaddress (00000, 11111, both, or neither)
- Enable broadcast reception on a per-RT basis
- RT 31 functions as broadcast terminal or valid RT address
Monitor
- Monitor concurrently with terminal simulation (Level C or higher channels)
- Create a sequential record in board memory or stream to file (with a simple program)
- Monitor and record all traffic on fully loaded buses
- Capture all traffic or filter by RT, SA, or tagged BC messages
- Each monitored message includes:
- Command/status/data words
- Time-tag
- Detected errors
- Transmission bus (A/B)
- RT response time(s)
- RT “Shadow Monitor” mode allows message activity of external RTs to be monitored
Message Data
- Buffering schemes facilitate data handling:
- Single buffers (default)
- Ping-pong double buffers ensure data integrity
- Circular lists transmit a repeated pattern, such as a sine wave
- FIFO list buffers can handle sequences of data, such as file transfers
- Data initialization options: zeros, incremental, or command word values
- Each message record can track activity by min, max, or elapsed time
Time-Tags
- Use 32-bit binary timer or 64-bit IRIG timer (displays day/hour/min/sec/ms/µs)
- IRIG timer options:
- Select IRIG-B or IRIG-A format
- Generate IRIG signal or sync up to an IRIG signal (on-board or external)
- Initialize timer to time of day or other value
Error Injection
- Protocol error injection (Level C and above):
- Parity
- Bit count
- Inverted sync
- Manchester
- Gap
- Word count (relative and absolute)
- Advanced error injection (Level D):
- Variable transmit amplitude
- Zero crossing distortion on leading or mid-bit (± 5 to 250 ns, in 5 ns increments)
- Trigger error injection from an external signal
- Inject errors in all or tagged messages
Interrupts/Logging
- Configurable event log can be polled and can generate interrupts to the host PC
- The following events may be user-selected for logging/interrupts:
- When the monitor is full or halts
- On a user-specified frequency of monitored messages
- When tagged messages (BC or RT) are sent or received
- When the BC schedule halts or pauses
- When the BC schedule encounters a user-inserted Log Event command
- When a list buffer is empty or full
The Downloads section contains data sheets with complete information on MIL-STD-1553 functionality for OmniBus products.
PCI AND cPCI
 The OmniBus PCI and cPCI boards can host 1 or 2 on-board cores with circuitry to support 1 or 2 protocol modules. Because each on-board core has its own dedicated DSP, the OmniBus PCI/cPCI boards can host up to 32 ARINC 429 channels without relying on the host processor or risking data loss from an overloaded DSP.
Ethernet/USB
 The OmniBusBox device hosts 2 on-board cores with circuitry to support 2 protocol modules. Because each on-board core has its own dedicated DSP, the OmniBusBox device can host up to 32 ARINC 429 channels without relying on the host processor or risking data loss from an overloaded DSP.
|
|
VME
 The OmniBus VME boards can host 2 or 4 on-board cores with circuitry to support up to 4 protocol modules. Because each on-board core has its own dedicated DSP, the OmniBus VME boards can host up to 64 ARINC 429 channels without relying on the host processor or risking data loss from an overloaded DSP.
PMC
The OmniBus PMC board brings the power and flexibility of OmniBus 1553 products to the PMC form-factor. This COTS based device offers a rugged, conduction cooled, dual channel 1553 interface. The OmniBus 1553 PMC is able to withstand extreme temperatures, shock and vibration making it ideal for interfacing to MIL-STD-1553 databuses in harsh environments.
|
CoPilot
 The easiest way to use the MIL-STD-1553 functionality of your OmniBus board is with CoPilot, Ballard's Windows-based software. CoPilot is an intuitive, interactive program that simplifies the testing and simulation of MIL-STD-1553 systems. In CoPilot, you can simulate the Bus Controller, up to 32 RTs, and monitor, record, and export bus activity. Data can be entered and displayed in engineering units and data definitions may be saved to the 1553 database. CoPilot features include virtual instruments, strip charts, moving map displays, scripting, and software playback mode. CoPilot also supports ARINC 429, ARINC 708, ARINC 664/FADX, and serial. Because CoPilot can host multiple cards, channels, and databuses, it is the ideal tool for operating OmniBus products. CoPilot may be purchased as part of an OmniBus system or separately.
|
|
BTIDriver API
 Alternatively, software developers can use the included Application Program Interface (API) to quickly develop custom applications. OmniBus products can be easily configured and operated with only a few API calls. The comprehensive library also includes a broad range of functions for specialized needs.
Drivers
Driver software is available for Windows®, Linux®, LabVIEW, LabVIEW RT, VxWorks®, INTEGRITY® and other operating systems. Availability varies by product. Contact Ballard for specific details for your desired Omnibus product.
PowerPC
An SDK is available for advanced users who are developing software to run on the PowerPC (available on OmniBusBox, OmniBus VME, and OmniBus PMC).
|
OmniBus Part Numbers
The part number for an OmniBus product is a combination of the platform number, module number(s), CoPilot code, and options. This results in thousands of possible part number combinations. Contact Ballard sales for assistance in determining the best OmniBus order number to fit your needs. Each platform core can accept one module. A core without a module may be used for future expansion.
Example Part Numbers
|
112-544-544
|
|
OmniBus PCI board with two 2 channel (level C) MIL-STD-1553 modules
|
|
162-544-423
|
|
OmniBusBox with a 2 channel (level C) MIL-STD-1553 and a 8R/8T ARINC 429 module
|
XXX :: Platform Number
| # | Description |
| 111 | PCI w/ 1 core |
| 112 | PCI w/ 2 cores |
| 121 | 3U cPCI w/ 1 core |
| 122 | 3U cPCI w/ 2 cores |
| 141 | PMC w/ 1 fixed core
(MIL-STD-1553 only) |
| 152 | 6U VME w/ 2 cores and PMC site |
| 154 | 6U VME w/ 4 cores (no PMC site) |
| 162 | OmniBusBox w/ 2 cores |
CoPilot Code
To include CoPilot add "CP-" before the OmniBus order number.
Example: CP-112-544-544
Options
Contact Ballard sales for information on available OmniBus options.
|
|
YYY :: MIL-STD-1553 Module Numbers
| # |
CH0 Level |
CH1 Level |
| 510 |
A |
— |
| 520 |
B4 |
— |
| 530 |
B32 |
— |
| 540 |
C |
— |
| 550 |
D |
— |
| 511 |
A |
A |
| 522 |
B4 |
B4 |
| 533 |
B32 |
B32 |
| 544 |
C |
C |
| 555 |
D |
D |
| 551 |
D |
A |
Other channel level combinations available. Contact sales for more information.
Multi-Protocol
OmniBus products are capable of concurrently hosting more than one avionics protocol on a single product.
See the OmniBus protocol pages for a list of available module numbers:
MIL-STD-1553,
ARINC 429,
ARINC 708,
ARINC 717,
CSDB,
Serial,
Discrete I/O
|
|
|
Adobe Acrobat is required to view PDF documents. Click Here to download a free version of Acrobat Reader. |
|
|
|