Avionics System Design - Co-Pilot 1553

Avionics System Design Lab Code : 405803
Lab Assignment # 5
Configuring Mil-Std-1553 Avionics Bus for Data

Exchange with Remote Terminals
using CoPilot Ver 6.0 Software
Prepared By
Assistant Professor Irfan Majid
Aeronautics and Astronautics Department
September Page 1 of 29
Avionics Engineering Program
2018
Contents
Aim
Learning Outcomes
Reference Documents
Grading Rubric
Simulation Handout
Review Questions
2018
Aim
1. The students will configure the Mil-Std-1553 Bus for data
exchange with specified Remote Terminals (RT) using CoPilot-6.0
software.
2. The students will demonstrate their work on assigned terminals.
3. Students will answer the review questions related to Mil-Std-
1553 Data Bus.
.
Learning Outcomes
After completion of this unit the student shall be able to:-
1. To configure Mil-Std-1553 Bus to connect RTs in receive and / or
transmit mode.
2. Assign sub-addresses to RT Modules.
3. Monitor data traffic on Data Bus.
References
1. Chapter 2: Military Avionics Systems
2. Condor Electronics Document
3. CoPilot-6.0 User Manual
2018
Grading Rubric
S. No Proficiency Allocated
Percentage
1 Demonstration correct configuration 50%
through simulation
2 Review Questions 50%
2018
Part-I
Create and Send a 1553 Message
The Bus Controller (BC) initiates activity on a MIL-STD-1553 bus. You can use
CoPilot’s Bus Controller mode to test real RTs on a 1553 databus. Within CoPilot
1553, all BC messages are composed using the Message Editor, and all messages are
stored and organized within the Message List.
Introduced in This Part
Message Editor, Data Editor, Message List
Objective
Define and transmit a single message named Set Altitude instructing RT01, SA02 to
receive three data words.
Start CoPilot6 Software by clicking the Program Icon on Desktop
In the Window that appears, as shown below, select “Check All” box and Click “OK”
2018
Program window will open with Default “AFDX” Project running. Stop the running
project by Clicking “Stop Button” in top right hand corner. Also close out two active
windows in the “Display Area” by Clicking the “x” Window Close Buttons. Click
“OK” Button on the confirmatory message box. Refer to Figure below:-
Open the “Hardware Explorer” by clicking the “Hardware Explorer” Tab as pointed
out in Figure below:-
2018
Right Click the “Demo 429 Board” Link in the Hardware Explorer Window, as
indicated by Red Ellipse” in Figure above. Select the “Delete” Option from the “Pop
Up” Menu that appears. Repeat for “Demo AFDX Card”. Click “OK” Button on the
confirmatory message box. If the Hardware Explorer Window closes Click “Hardwae
Explorer” Tab again. Click the “1553 Channel 0 Demo” Tab on top of display
window as marked by “Green Ellipse” in Figure above. Now following display shall
be visible:-
2018
Create a BC Message
First, create a BC message using the Message Editor.
► Right click the icon and choose Insert BC Message from the
context menu to open the Message Editor, as indicated by arrow in Figure above.
Following window shall open:-
2018
► Type Set Altitude in the Message Name field
The first step in implementing is giving the message a meaningful name.
► Click on the BC→RT option button to define an RT receive message

► Set RT field to “1”, SA (sub-address) field to” 2”, WC (Word Count) field to “3”.
(This means “Set Altitude” message will be sent to Remote Terminal 01, it is meant
for Sub-Address 2 of the RT and message will contain 3 words)
► Click the Apply button to apply the current choices (Do not close the window
yet)
The Window shall look as in following Figure:-
2018
When you press Apply, the message is added to the Message List in the hardware tree
(see figure bottom right). The message in the tree is still linked to the Message Editor
window, and any changes you make in the editing window are applied with the Apply
button.
Notice that this message in the hardware tree is identified as an RT receive message
by its icon:
The Set Altitude message defined in the Message Editor
The Set Altitude message in the Message List
2018
Define the Data
► Click the Data Editor button (in the Message Editor) to open the BC Message
Data Editor (Refer to “Red Ellipse” in Figure above)
Notice that only three data cells are available. This is because the word count for this
message is “3.”
► Click in the first data cell and type 1234, type 5678 in the next, and 9ABC in the
third (you can use the Tab key to advance to the next data cell)
Notice that data is entered in hexadecimal radix.
BC Message Data Editor for Set Altitude
Note: When physical card is present Icons and colors are used throughout CoPilot to
identify objects. The Data Editor window has a yellow background to indicate that it
is associated with a BC message (RT sub-addresses are green).
2018
Click the OK button to apply the new data, close the Data Editor, and return to the
Message Editor
► Click OK to close the Message Editor
Transmit a Single Message
Although you have now created a message, it is not scheduled and will not be
automatically transmitted. However, you can transmit this single message once on the
databus.
► Right click the Set Altitude message in the BC Message List to select it
(highlighted when selected) and choose Transmit message Asynchronously
from the context menu (see figure at right)
2018
Set Altitude context menu (Actual transmit confirmation box)
A warning message will appear since the demo card is a virtual card and not attached
to a databus (click OK to clear the warning dialog). If you had an actual Ballard
board, you would get a confirmation message box with a transmission report (see
second figure at right).
2018
Part – II
Run Default and Custom BC Schedules
The Bus Controller schedule directs the flow of information on the 1553 databus. The
BC schedule window allows the user to control the selection and frequency of
transmitted messages and define schedule elements such as frames, gaps, etc. An
automatic default schedule can also be selected.
Default and custom BC Schedules, BC icons, BC Schedule window
Objective
First, run a default BC schedule. Then, create and transmit a custom schedule
consisting of one RT transmit message (Get Position) and one RT receive message
(Set Altitude).
Run a Default Schedule
Note: Continue from work done in Part-I
► Click the Run button to begin simulation
The default schedule transmits all messages in the BC Message list (in this case, a
single message) within a 20 millisecond frame.
► Click the Stop button to stop transmitting
2018
Create a Custom BC Schedule
First, open the schedule window.
► Right click the BC icon and select Schedule >View Active Schedule from the
context menu to open the BC Schedule window, Refer Figure Below
The Window shown below shall appear:-
2018
2018
Define & Add a New Message
It is possible to access the Message Editor from within the BC Schedule window
to create a new message.
► Click on the New Message icon, indicated by Red Circle in Figure

above, to open the Message Editor (introduced in Part-I)
► Type Get Position in the Message Name box
► Click on the RT→BC (TX) option button to define an RT transmit message
► Click keys 1, 3, 2 to address this message to RT01, transmit SA03, with
2 data words
► Click OK to add this message to the BC Schedule, refer Figure below:-
Get Position is added to the same frame as Set Altitude (and it is added to the
Message List in the hardware tree and BC Scheduler). Based on the frame time,
each of the two messages will be transmitted once every 20 milliseconds.
► Click the Close button in the upper right-hand corner to close the BC
Schedule window
2018
Transmit the Custom Schedule
► Click the Run button in the CoPilot tool bar to start the simulation
► Click the Stop button to stop transmitting
2018
Part-III
Detect and Shadow RTs and SAs
This part depicts how CoPilot 1553 automatically detects RTs and subaddresses on
the MIL-STD-1553 databus. Then, using CoPilot’s special “shadow RT” mode, we’ll
monitor an RT without simulating it.
Introduced in This Lesson
RT icons in hardware tree; TSA tab in the RT Configuration Properties dialog; SAs in
the hardware tree
Objective
Automatically detect whether or not an RT is responding to the Bus Controller.

Examine the Terminal Simulation Assignment (TSA) window and shadow the
detected RT. Run the simulation again to auto-detect two sub-addresses.
2018
Automatically Detect an RT
CoPilot can automatically detect RTs on the MIL-STD-1553 databus.
► Right click on the branch and choose Configure RTs from the context
menu to open “RT Configuration Properties” Window, refer Figure below:-
“RT Configuration Properties” shows the status of all RTs key of all symbols and
colors used is listed on the window.
Shadow an RT
CoPilot 1553 allows you to “shadow” an RT on the bus, that is, to monitor and view
the activity of an RT without any interaction on the bus. Although we are not
2018
connected to a real terminal, the 1553 demo card can be used to illustrate the concept
by “shadowing” the messages to RT01 that were created in the previous lessons.
► Click the RT01 button to change its color to green background

► Click OK to close the TSA window
Shadowing allows you to view the changing data values through CoPilot views and
displays (such as Message View or MIL-STD- 1553 View) as they are being
transmitted and received by the external RT. With Co-Pilot 1553 Plus, you can view
data from shadowed RTs through strip charts, controls, or moving map dis-plays.
Refer to the figure below:-
2018
Automatically Detect SAs
CoPilot 1553 automatically detects sub-address activity associated with simulated or

shadowed RTs.
► Click the Run button to start Simulation mode
Note that the two detected sub-addresses appear in the hardware tree (Blue ellipse in
figure above). Data for shadowed SAs can be viewed, but not changed. This shadowed
SA data may be linked to and viewed through CoPilot display windows.
► Click the Stop button to return to Edit mode
2018
Part-IV
Configure and Simulate RTs and SAs
Remote terminals respond to commands from the Bus Controller. These BC

commands may direct the RT to receive data, to transmit data to the BC or another
RT, receive bus-wide broadcast commands, or to respond to mode codes. In most
cases, 1553 protocol requires the RT to respond to BC commands with a status word.
CoPilot allows the user to simulate all aspects of RT behavior as defined by MIL-
STD-1553.
RT Properties dialog, SA Properties dialog, Message View window, RT Sub-address

View window
Objective
Simulate an INS (Inertial Reference System) terminal at RT address 1. Configure

transmit sub-address 1 of RT01, define two data words in sub-address 3, and modify
those values during run time.
Simulate the Detected RT
In Part-III it was illustrated how an external RT could be shadowed. In this lesson, we

will simulate the behavior of a real RT (RT01).
► Right click on the branch in the hardware tree and choose Configure RTs
to open the RT Configuration dialog
► In the TSA tab, click on the RT01 button to select the simulation option (light
green) and click OK to close the dialog
2018
The light green button color indicates that this terminal is selected for simulation.
The black triangle indicates that this RT was configured by the user (in this case,
configured for simulation).
Configure the RT
► Right click RT01 and choose Properties to open the Properties dialog
Sub-addresses are activated automatically when the Auto-detect SAs option is

selected. Since the option is active by default, receive SA02 and transmit SA03 were
detected when CoPilot was run in Part-III.
► Click the transmit SA01 button (see figure)

► Click the RT01 tab and enter INS (Inertial Navigation System) in the
Name field
► Click OK to close the properties dialog
2018
RT 1 selected for explicit simulation in the TSA window
Name the Subaddresses
► Right click transmit SA01 and choose Properties to open the SA Properties
dialog
► Type True Heading in the Name box and click OK to close the window
2018
2018
► Repeat this process to name SA02 (type Altitude) and SA03 (type Present
Position)
Define and View SA Data
The Get Position message asks for two data words.
► Right click on the Present Position sub-address and select the Sub-address
View window
► Enter 4321 in the first data cell and DDDD in the second (do not close Sub-
address View window)
Page 27 of 29
► Click the Run button in the CoPilot tool bar
Present Position (SA03) responds to the BC Schedule by transmitting two data

words, the data is simulated to be transmitted and fields change to zero..
► Click the Stop button to end the simulation
Page 28 of 29
Review Questions
Q.1. Why Manchester-II Bi-phase Encoding is used in 1553 Data

Protocol?
Q.2 What is the purpose of Sub-Address in data transmission on

1553 Protocol.
Q.3 From the BC Message Selection you carried out in Part-I of

Lab Assignment draw a diagram showing what will be filled in six
segments of Command Word as per Figure 5 of Reference
document.
Q.4. What Multiplexing Scheme is used to transmit data on 1553

Data Bus?
Q.5. Although you did not use it there is a field for Frame Time in
Bus Scheduler. Why do you think this frame time is required to be
set?
Note: Each question carries 10 Marks
Page 29 of 29

Avionics System Design - Co-Pilot 1553

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avionics System Design - Co-Pilot 1553

Uploaded by

Copyright:

Available Formats

Avionics System Design Lab Code : 405803

Configuring Mil-Std-1553 Avionics Bus for Data

Aeronautics and Astronautics Department

Introduced in This Part

Message Editor, Data Editor, Message List

Start CoPilot6 Software by clicking the Program Icon on Desktop

First, create a BC message using the Message Editor.

► Type Set Altitude in the Message Name field

The first step in implementing is giving the message a meaningful name.

► Click on the BC→RT option button to define an RT receive message

The Window shall look as in following Figure:-

The Set Altitude message defined in the Message Editor

The Set Altitude message in the Message List

Define the Data

Notice that data is entered in hexadecimal radix.

BC Message Data Editor for Set Altitude

Transmit a Single Message

Set Altitude context menu (Actual transmit confirmation box)

Introduced in This Part

Default and custom BC Schedules, BC icons, BC Schedule window

Run a Default Schedule

Note: Continue from work done in Part-I

► Click the Run button to begin simulation

► Click the Stop button to stop transmitting

Create a Custom BC Schedule

First, open the schedule window.

The Window shown below shall appear:-

Define & Add a New Message

► Click on the New Message icon, indicated by Red Circle in Figure

► Click OK to add this message to the BC Schedule, refer Figure below:-

Transmit the Custom Schedule

► Click the Stop button to stop transmitting

Introduced in This Lesson

Automatically detect whether or not an RT is responding to the Bus Controller.

CoPilot can automatically detect RTs on the MIL-STD-1553 databus.

► Click the RT01 button to change its color to green background

Automatically Detect SAs

CoPilot 1553 automatically detects sub-address activity associated with simulated or

► Click the Run button to start Simulation mode

► Click the Stop button to return to Edit mode

Remote terminals respond to commands from the Bus Controller. These BC

Introduced in This Part

RT Properties dialog, SA Properties dialog, Message View window, RT Sub-address

Simulate an INS (Inertial Reference System) terminal at RT address 1. Configure

Simulate the Detected RT

In Part-III it was illustrated how an external RT could be shadowed. In this lesson, we

Sub-addresses are activated automatically when the Auto-detect SAs option is

► Click the transmit SA01 button (see figure)

RT 1 selected for explicit simulation in the TSA window

Name the Subaddresses

Define and View SA Data

The Get Position message asks for two data words.

Present Position (SA03) responds to the BC Schedule by transmitting two data

► Click the Stop button to end the simulation

Q.1. Why Manchester-II Bi-phase Encoding is used in 1553 Data

Q.2 What is the purpose of Sub-Address in data transmission on

Q.3 From the BC Message Selection you carried out in Part-I of

Q.4. What Multiplexing Scheme is used to transmit data on 1553

Note: Each question carries 10 Marks

You might also like