For More Information
800.829.1553
|
|
|
CoPilot 1553 is part of the CoPilot Family-a comprehensive software environment that interfaces to Ballard's MIL-STD-1553, ARINC 429,
ARINC 708/453, and ARINC 664/AFDX hardware products. CoPilot uses and features common to all of those protocols are summarized in the
CoPilot Key Features page. The examples below illustrate some of the features unique to the MIL-STD-1553 databus.
|
|
Using CoPilot and one or more of Ballard Technology's MIL-STD-1553 boards, users can easily analyze databus activity, quickly set up
and run Bus Controller schedules, simulate Remote Terminals, and monitor, analyze, and export bus activity. While communicating with
the databus, users can enter and display data in engineering units through simulated flight instruments or tabular displays. Data field
and interpreter definitions can be saved to and retrieved from a user-maintained database. Strip chart displays, advanced monitor
display features, and CoPilot's software playback mode simplify data discovery. The Automated Test Environment (ATE) implemented in
the latest release opens up exciting new possibilities for creating and exporting certified test 1553 procedures.
|
|
Other features include auto detection of remote terminals, error injection/detection, filtering of data before or after capture, and
a moving map display. Ballard's exclusive scripting control allows CoPilot to be customized with user-coded or example scripts.
|
BC Messages
|
CoPilot allows the user to simulate all aspects of BC behavior as defined by MIL-STD-1553B. Users can easily create BC messages
and edit message data.
|
Message Editor
- Transmit, receive, RT-to-RT, and mode code messages are constructed through an intuitive Message Editor
- Messages can be assigned individually to bus A or B
- Messages may be retransmitted based on user-defined retry criteria
Data Editor
- A hexadecimal data editor can be accessed from the Message Editor
- Macro buttons automate data initialization
- Messages may be tagged for error injection
- Other data editors are available for data fields
|  |
|
BC Schedule
|
|
|
- Define one or more frames with unique frame times
- Assign messages to specific frames
- Add gaps, branches, and retry conditions
- Loop the schedule indefinitely or a specified number of times
- Set synchronization or external trigger options
- Access the Message Editor window from inside the BC Schedule window
|
|
|
CoPilot makes it easy to quickly configure and customize up to 32 remote terminals. RTs (with their subaddresses and data fields)
can be automatically detected by CoPilot and are graphically represented in an Explorer-style tree, making it easy to visualize the
bus topology at a glance. RTs in the tree may represent both external and simulated terminals.
RT 31 is normally reserved for Broadcast messages, but may be reconfigured as a standard RT.
SA configuration, mode codes, and status word
options are defined in the RT Properties dialog.
|
|
|
Subaddress Configuration
- Transmit and receive SAs can be individually configured from the RT Properties window
- SAs can also be detected by CoPilot during simulation and automatically added to the hardware tree
Mode Codes
- Mode codes may be legalized globally (for all terminals on the databus) or individually for each terminal
- Default mode codes are based on MIL-STD-1553B, Release 2
- Broadcast mode codes are defined globally for all RTs on the databus
Status Word
- Unique status masks may be defined for each RT
|
|
The Bus Monitor preserves a sequence of 1553 messages in a file so that bus traffic can be examined later. A time-tag is attached to
each record placed in the file. Users can specify that all data will be recorded in the monitor file through a single checkbox or select
individual messages, RTs, or subaddress through filters. The Monitor View window contains advanced
analysis features, such as display filters, search commands, and formatting
options, that simplify the examination of captured data. The monitor file can be printed, exported, or
reexamined through CoPilot's powerful software playback feature, or retransmitted onto the 1553 databus
using hardware playback.
|
Monitor View Windows
- Monitor View windows are used to display, segment, save (to file), and replay monitored data (in software and hardware playback modes)
- Users can stop, start, or pause monitor recording from the Monitor View window
- Choose between Full and Form display modes, or two user-defined displays
- Toggle time-tag and radix displays
|
|
|
Monitor Filters
- During recording, filter the monitor record by remote terminal, subaddress, or message.
- After recording, use the same options to filter the Monitor View display
|
|
Monitor Analysis
- The monitor file can be searched based on the command definition, data values, error condition, or bookmark
- Analyze the contents of the monitor record using the Step, Go To Message, and Search commands
|
|
Export Monitor Data
- Export as an Excel file or a tab-delimited file
- Include the column titles and data words
- All or selected monitor records may be exported
- Export entire records or just data fields
- Records exported in .RAW format can be imported into Monitor View
|
|
Individual words, bit strings, and word segments within a message can be defined as data fields. Data
fields can be named and associated with an interpreter so that its data can be defined, translated, and viewed in "engineering
units." Thus, CoPilot relieves the user from the calculations necessary to convert the binary data passed on the bus into a
meaningful format. Data may be viewed and modified
in engineering units throughout the CoPilot environment. In addition, the engineering units definition can be saved to the custom 1553
database for reuse.
|
Data Fields and Interpreters
- Data fields can be named (e.g., "Altitude," see figure at right) and units of measurement can be specified (e.g., "feet")
- Engineering units are displayed in other CoPilot windows and views (see altimeter and LED controls in figure at right)
- Seven different interpreters allow data to be encoded in many formats (e.g., 2's complement, BCD, discretes, etc).
- A variety of data editors are available for data fields
|
|
|
Data Field Editors
- The Binary Editor allows field values to be set in hex, binary, or octal radixes
- The Engineering Unit Editor displays the engineering units and name of the field. Use the slider, buttons, or text box to set the value.
- The Data Generator creates a continuous stream of changing data based on one of eight function types (sawtooth, sine, data list, etc.)
- Data can also be modified dynamically while the bus is running using virtual instruments in the Control View window.
|
|
|
Engineering Units Displays
- Message View windows display the hex value of data words in the Data tab, but also the engineering units of fields in the Fields tab (see "Get Position" Message View at right)
- 1553 View is a tabular display of messages, RTs, SA, and fields (see figure at right)
- Data values, status word, and error status, etc. are continuously updated while the simulation is running
- Engineering units values can be viewed in all CoPilot displays, including Professional displays
|
|
Error detection is supported on all Ballard Technology MIL-STD-1553 boards. Error status is shown through the Monitor View and
Message/Subaddress View windows.
Error injection is available on 1553 level C and higher boards. Users may define protocol
errors (word, gap, or message errors) for all or tagged messages. With OmniBus level D boards, users may also generate zero crossing
distortion and variable transmit amplitude. Using the Error Injection window, users can define and control error injection during run time.
MIL-STD-1553 does not specify the internal formatting of data in transferred messages. Data in each 1553 message may be completely
redefined for each application. Once defined, however, the avionics systems assigned to RTs are often used without change in other
applications. The custom 1553 database allows CoPilot users to preserve and reuse these complex definitions.
|
Data Fields
- The 1553 database is populated with fields that can be imported and modified
- Additional data fields may be saved to and retrieved from the database
- A data field may be defined by name, units, start bit, width, interpreter type, and interpreter properties
Remote Terminals
- In addition, an entire RT definition, including subaddresses, data fields, and interpreters, can be saved to and loaded from the database
|
|
|
|
|