CoPilot® 1553 and CoPilot 1553 Plus

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

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 Plus displays

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

• 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

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

• Control CoPilot programmatically from third-party applications or programming environments (such as LabVIEW or C++) through the CoPilot Object Model
  • Example: In Microsoft Excel, run tests using CoPilot with the push of a macro button, pass data back and forth, and chart the results.
• Control OLE Automation-compliant applications from CoPilot's Script View window
  • Example: Use a CoPilot script to launch Internet Explorer, browse to a website or directory, and publish CoPilot data to the web.
• Host and edit documents/files from OLE Automation-compliant applications in CoPilot
  • Example: Open a Microsoft Word document in the CoPilot workspace, add and edit text, use the embedded Word menus and toolbars, and save the file.

Virtual Instruments

• The Quick View library of preconfigured controls can be launched in one step from data fields in the hardware tree
• The Control View window hosts a library of virtual controls that can source transmit data or display receive data through gauges, sliders, knobs, and a variety of aircraft instruments.
• Controls can be automatically generated by dragging a data field from the hardware tree into the control form
• Controls are easily customized through properties dialogs or the control property browser
• Easily add third-party ActiveX controls

Strip Charts

• The Strip View window is a dynamic, two-dimensional charting control for displaying one or more streams of real-time data
• Data fields may be dragged into the Strip View window and assigned to a single or multiple displays
• Quickly review the dataset or do in-depth analysis of data trends

Moving Map

• Map View is a container for displaying aircraft position by linking positional data to a real-time moving map display
• Choose stationary or floating mode, add waypoints, label objects, define view area, etc.
• Obtain the map background from a graphics file, or generate a photographic or topographical map using TerraServer

• Scripts can be imported directly into the Script Pane
• Scripts could be used to respond to bus events, trigger monitor recording, or create a sequence of unique data responses based on the value of incoming messages
• Scripts can be used to implement various protocols and interpreters
• Easily create custom reports and analysis tools
• Easily create programmable triggers
• Scripts could also be used to transfer information between CoPilot and other applications
• Scripts can be used to interact with data transferred on the databus or to facilitate analysis during software playback

• Analyze a monitor record with software playback by viewing the record repeatedly, examining the record through different displays, and by slowing and pausing at points of interest
• Use the playback tool bar in the Monitor View window to control speed and move to index points and breakpoints
• Utilize scripts with software playback to identify critical data, facilitate analysis, and create statistical information
• Limit the playback to a subset of the monitor record by setting the start and end index
• Use breakpoints to pause playback at specified points

• Create stable, repeatable tests for external RTs
• Replay the BC and selected RTs from the monitor record data source
• Concurrently monitor external RT responses (with a level C board)
• Playback speed is based on recorded time-tags
• Use breakpoints to pause hardware playback at specified points
• Pause and resume hardware playback with Monitor View controls
• Inject errors by modifying records in the monitor data source

• IRIG Timetag
• PowerPC user processor
• CompactFlash slot
• Mixed protocols
• High channel counts

The OmniBusBox enables computers and networks to interface with multiple avionics databuses via Ethernet or USB.