Installation Guide for the Avionics Rig - ASAS TN · PDF fileAirtel ATN Ltd (Ireland) QinetiQ...

MA-AFAS IN STRICT CONFIDENCE Contract No.: G4RD-2000-00228Report No.: 560/78718Issue: 1.0

IN STRICT CONFIDENCE Page i

CONTRACT N° : G4RD-2000-00228

PROJECT N° : GRD1-1999-10516

ACRONYM : MA-AFAS

TITLE : THE MORE AUTONOMOUS - AIRCRAFT IN THE FUTUREAIR TRAFFIC MANAGEMENT SYSTEM

D41 - Installation Guide for the Avionics Rig

AUTHOR: BAE SYSTEMS

PROJECT CO-ORDINATOR : BAE SYSTEMS

PRINCIPAL CONTRACTORS :Airtel ATN Ltd (Ireland) QinetiQ (UK)ETG (Germany) EUROCONTROL (France)NLR (Netherlands)

ASSISTANT CONTRACTORS:AMS (Italy) DLR (Germany)ENAV (Italy) FRQ (Austria)Galileo Avionica (Italy) Indra Sistemas (Spain)NATS (UK) SCAA (Sweden)S-TT (Sweden) Skysoft (Portugal)SOFREAVIA (France) Stasys Limited (UK)Thales-ATM (France)

Report Number : 560/78718Project Reference number : MA-AFAS – WP4.1-BAESYSTEMSDate of issue of this report : 29 May 2003Issue No: 1.0PROJECT START DATE : 1/3/2000 DURATION : 36 months

Project funded by the EuropeanCommunity under the ‘Competitive andSustainable Growth’ Programme (1998-2002)

This document is proprietary of the MA-AFAS consortium members listed on the frontpage of this document. The document is supplied on the express understanding that it isto be treated as confidential and may not be used or disclosed to others in whole or inpart for any purpose except as expressly authorised under the terms of CEC Contractnumber G4RD-2000-00228


IN STRICT CONFIDENCE Page iii

LIST OF EFFECTIVE PAGES AND CHANGE HISTORY

Insert latest changed pages. Destroy superseded pages

TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 29CONSISTING OF THE FOLLOWING

Page No. Date Issue DCR Page No. Date Issue DCR

All 1.0 -


IN STRICT CONFIDENCE Page iv

DISTRIBUTION LIST

This Document is distributed as below.

Additional copies held by unnamed recipients will not be updated.

Paper Copies Name Address

MASTER Library BAE SYSTEMS, Rochester

MA-AFAS Library Avionic Systems

ElectronicCopies

Name Address

European Commission EC, Brussels

MA-AFAS Consortium Members [email protected]

MA-AFAS Web Site

mailto:[email protected]


IN STRICT CONFIDENCE Page v

Contents1 SCOPE ...........................................................................................................................................1

1.1 Purpose ......................................................................................................................................11.2 System Overview .......................................................................................................................11.3 Document Overview ...................................................................................................................1

2 REFERENCED DOCUMENTS.......................................................................................................2

3 INSTALLATION INSTRUCTIONS .................................................................................................3

3.1 Flying Rig....................................................................................................................................33.1.1 Physical Installation........................................................................................................33.1.2 Electrical Installation ......................................................................................................4

3.1.2.1 Signal Connections ........................................................................................................53.1.2.2 Ethernet Connection ......................................................................................................63.1.2.3 Power Connection..........................................................................................................6

3.2 Laboratory Rig............................................................................................................................63.2.1 Physical Installation........................................................................................................6

3.2.1.1 Chassis Installation ........................................................................................................63.2.1.2 Component Installation ..................................................................................................6

3.2.2 Electrical Installation ......................................................................................................73.2.2.1 Signal Connections ........................................................................................................73.2.2.2 Power Connection..........................................................................................................8

3.3 Component Replacement...........................................................................................................93.3.1 Externally Mounted Components...................................................................................9

3.3.1.1 PEC Removal...............................................................................................................103.3.1.2 PEC Insertion ...............................................................................................................103.3.1.3 MVME761 Insertion......................................................................................................103.3.1.4 Hard Drive Removal and Insertion...............................................................................11

3.3.2 Internally Mounted Components ..................................................................................113.3.2.1 Fitting the MVME761P2 Adapters................................................................................12

4 SOFTWARE INSTALLATION......................................................................................................14

5 ACCEPTANCE TESTING ............................................................................................................15

APPENDIX A MVME5100 JUMPER SETTINGS ...............................................................................16

APPENDIX B DEVELOPMENT ENVIRONMENT INSTALLATION ..................................................17

B1 On-Site Tornado Settings.........................................................................................................17B1.1 FTP Server Configuration ...................................................................................................17B1.2 Tornado Registry Configuration ..........................................................................................17B1.3 Target Server Setup............................................................................................................17

APPENDIX C CPDLC GROUND STATION.......................................................................................20

C1 General.....................................................................................................................................20C2 Physical Connections ...............................................................................................................20

C2.1 Power Panel ........................................................................................................................20C2.2 Ethernet...............................................................................................................................20C2.3 Ground Transponder ...........................................................................................................20

C3 Ethernet Configuration .............................................................................................................21C3.1 Power Panel ........................................................................................................................21C3.2 LINUX PC............................................................................................................................21

C4 Communications Configuration ................................................................................................21C4.1 Cygwin.................................................................................................................................22C4.2 Configuration Files ..............................................................................................................22


IN STRICT CONFIDENCE Page vi

FiguresFigure 1 Flying Rig Fixing Holes .........................................................................................................3Figure 2 Avionics Rig - Rear Panel .....................................................................................................4Figure 3 Signal Connection Panel.......................................................................................................5Figure 4 VME Card positioning............................................................................................................7Figure 5 Laboratory Rig Signal Connections.......................................................................................8Figure 6 Laboratory Rig Power Connection ........................................................................................9Figure 7 Chassis Interior ...................................................................................................................12Figure 8 MVME761P2 Adapter Layout..............................................................................................13Figure 9 Configure Target Servers Window......................................................................................18Figure 10 Ground Components for CPDLC ........................................................................................20Figure 11 cfgB.sh Template ................................................................................................................22Figure 12 start_cfgB_R2.sh Template.................................................................................................23Figure 13 Part of the maafas_cfgC_R2.inp File ..................................................................................23

TablesTable 1. Signal Connections ...............................................................................................................6Table 2. Laboratory Rig Connectors ...................................................................................................8Table 3. MVME5100 Jumper Settings ..............................................................................................16


IN STRICT CONFIDENCE Page 1

1 SCOPE

1.1 Purpose

This document sets out the actions required to install MA-AFAS Avionics Rig equipment at each ofthe identified testing facilities.

Currently, this includes the following:

QinetiQ (Lab and BAC1-11)

DLR (Lab and ATTAS)

AMS (Rome)

1.2 System Overview

Two variants have been built to support the MA-AFAS trials programme; a flying rig and a laboratoryrig. A third variant uses the processor and I/O cards and a HDD housed in an existing chassis whichis provided by DLR and qualified for use in the ATTAS.

The flying rig is the AFMS flight trials rig that has been upgraded to include more powerful PowerPCprocessors. The rig comprises a 9U 12 card VME chassis, powered from the 240V AC mains supply,that holds two PowerPC 5100 Single Board Computers (FMU and CMU), a 9.1Gbyte hard disk drive,two, 16-channel ARINC 429 interface cards and an RS232/RS422 serial interface card.

The laboratory rig is similar to the flying rig but is based on a smaller 6U, 12 card VME chassis andonly contains a single ARINC 429 interface card.

Photographs of each of these rigs are included later in this document.

1.3 Document Overview

The structure of this document is as follows:

Section 1 provides a brief overview of this document and the system to which it applies,

Section 2 provides full details of any other documents referenced from this document,

Section 3 gives the instructions and guidance needed for the successful installation of the MA-AFAShardware at each of the identified sites,

Section 4 gives the process whereby software updates may be installed into any of the installations.

Section 5 provides guidance on test procedures to be undertaken following installation of thehardware.



2 REFERENCED DOCUMENTSARINC 429 ARINC Characteristic 429Pt1-15, Mark 33 Digital Information Transfer System

(DITS), Part 1, Functional Description, Electrical Interface, Label Assignmentsand Word Formats, Dated: September 1, 1995.

D31 Interface Control Drawing for the In House Test Platform; 560/79697; Issue 1,published by BAE SYSTEMS.

D41 Users Guide for the MA-AFAS Avionics Rig, 560/80240, Issue 1, published byBAE Systems.


IN STRICT CONFIDENCE

3 INSTALLATION INSTRUCTIONSThis guide covers the installation of all variants of the MA-AFAS Avionics Rigs in the order in whichthe installations are expected to be carried out.

3.1 Flying Rig

The Flying Pig will primarily be installed into a number of test facilities that are maintained andcontrolled by QinetiQ using form AED40 documentation . The installation information presented in thisdocument is therefore general to cover those instances where the rig is to be operated outsideQinetiQ; e.g. at Rochester during manufacture and test.

3.1.1 Physical Installation

The Flying Rig is designed to be housed in a standard 19" rack using 8, M5 or M6 affixing screws. Fig1 shows the location of the mounting holes on the right side of the Avionics Rig front panel; the holeson the left hand side are identically placed.

Figure 1 Flying Rig Fixing Holes

Fitting the unit into a 19" rack requires the unit to be lifted into its required position and 8 saffixed. When used in the laboratory, the screws should be hand tight using a correctly sizscrewdriver.

MountingHoles

Page 3

crewsed



Caution

! The Flying Avionics Rig is heavy andcumbersome. A two man lift is advised

To avoid overheating the electronic components within the chassis during use, care should beexercised to avoid obstructing the free airflow to the Ventilation Inputs (see Fig 1) and Outputs (seeFig 2).

3.1.2 Electrical Installation

All electrical connections for the rig are available at the rear of the unit as shown in Figs 2 and 3.When fitted to an open rack, or a rack with a rear door, the connections can be made following thephysical installation. If an enclosed rack is used, then the connections should be made prior to thephysical installation.

Note: To avoid personal injury and possible damage to the equipment all connections shall be madewith the unit unpowered.

Figure 2 Avionics Rig - Rear Panel

t

SignalConnectionPanel

EthernetHub

Power Inle

Page 4



3.1.2.1 Signal Connections

There are two locations on the rear of the Avionics Rig where signal connections should be made:The Signal Connection Panel and the Ethernet Hub. These are identified in Fig 2.

The Signal Connection Panel (Fig 3) provides the connections for the serial interfaces (ARINC 429,RS232 and RS422), the 28V DC discrete signals (not used) and the video connections for theNavigation display.

Figure 3 Signal Connection Panel

The order of connection for the signals is not important; definition of each connector is1. Note that for the RTAVS/LATCH configuration of this equipment, all five co-ax connused but in the BAC1-11 aircraft installation, only the RGB connectors (D7 to D9) are u

Connector Type Destination/Source Fo

D1 25 way D-Type female Not Used Disc

D2 25 way D-Type male VDL Mode 4 Transponder RS4

D3 9 way D-Type male XKD Switchbox RS2

D4 9 way D-Type female Cursor Control Device RS2

D5 44 way D-Type male MCDU, ADC, Autopilot, SBAS,GBAS, Data Puddle

ARIN

D6 44 way D-Type male Cockpit Printer ARIN

D7-R Co-ax Nav Display Vide

D8-G Co-ax Nav Display Vide

D9-B Co-ax Nav Display Vide

Discretes

RS422

ARINC 429/1

ARINC 429/2

e

r

r

2

3

3

o

o

o

RS232/2

1
RS232/
Video, Red

Video, Green

Video, Blue

Vertical Sync

Horiz. Sync

Page 5

given in Tablectors will besed.

mat

etes

2

2

2

C 429

C 429



Connector Type Destination/Source Format

D10-VS Co-ax Nav Display * Video

D11-HS Co-ax Nav Display * Video

* Not connected in aircraft - see text

Table 1. Signal Connections

Currently, there will be no connection to connector D1.

3.1.2.2 Ethernet Connection

The Avionics Rig incorporates an 8 port ethernet hub, mounted internally but with the 8 RJ45 portsavailable externally (see Fig 2). Ports 1 and 2 are reserved for use by the Avionics Rig and port 8 isreserved for use with a site network. The other 5 ports are available for use in the aircraft installation.

3.1.2.3 Power Connection

The power connection is a standard IEC Inlet Port. There is no facility on the Avionics Rig to adjustthe input voltage range, it is preset to 240V ac.

Connection to the Avionics Rig should only be attempted with the power switched OFF.

The System utilises potentially LETHAL VOLTAGES. It mustnot be operated unless installed as specified in thisdocument.Equipment must be disconnected from power before andduring any close inspection of the equipment interior.Warning

3.2 Laboratory Rig

Four rigs have been commissioned for use in test facilities throughout Europe. These sites include theATTAS at DLR, Germany, at AMS, Rome and at BAES Rochester. The rig used at DLR will not needa chassis; only the components will be supplied by BAES for installation in the ATTAS chassis.

3.2.1 Physical Installation

3.2.1.1 Chassis Installation

The Laboratory Rig is designed to be housed in a standard 19" rack using 8, M5 or M6 affixingscrews. The location of the mounting holes on the rig front panel can be seen in Figs 4 and 5.

It is expected that an open rack be used to allow free airflow to the ventilation input and output grilles.If an enclosed rack is used then steps should be taken to ensure a free flow of air to the unit.

3.2.1.2 Component Installation

The components that make up the Avionics Rig are as follows:


1 MVME5100 PowerPC (FMU) fitted with Peritek Graphics adapter and IPMC761

1 MVME5100 PowerPC (CMU) fitted with PMC408 I/O adapter and IPMC761

2 MVME761P2-001 adapters (fitted to rear connector of PowerPCs)

1 MVME761-001 Transition Module fitted with 2 SIM530 I/O adapters

1 SBS ARINC429 Interface Adapter

Hard Drive Unit

Figure 4 shows the normal location of these cards within the chassis (except for the MVME761P2-001adapters which are fitted internally). For standalone use (i.e. not ATTAS), the FMU must occupy theleftmost slot of the VME bus because it acts as the VME bus master. When used in the ATTASchassis, board locations are not important although the MVME761-001 adapter needs to be adjacentto the CMU because of the ribbon cable that connects the two together, and the FMU needs to beclose to the Hard Drive Unit (SCSI cable connects these two).

FMU

ARINC429 I/O


Figure 4 VME Card positioning

3.2.2 Electrical Installation

3.2.2.1 Signal Connections

All signal connections are made at the front of the unit directly onto the electronic cards. Fig 5identifies each of the connectors and Table 2 identifies the type and destination/source of the

The connections should be made whilst the unit is unpowered; the order in which the connecmade is not important.

Note that the Discretes connection is currently not used.

U
CM
ti

MVME761

HDDTray

Page 7

signals.

ons are


Nav Display/Monitor

IN STRICT CONFIDENCE Pag

Figure 5 Laboratory Rig Signal Connections

Connector Type Destination/Source

Discretes 37 way D-Type female Not Used

RS422 HD26 socket VDL Mode 4 Transponder

RS232/1 9 way D-Type female Cursor Control Device

RS232/2 9 way D-Type female Displays Control Panel

ARINC 429 44 way D-Type female MCDU, ADC, Autopilot, SBAS,GBAS, Data Puddle

Video 15 way D-Type female Nav Display/Monitor

CMU LAN 1 RJ45 socket Ethernet Hub

FMU LAN 1 RJ45 socket Ethernet Hub

Table 2. Laboratory Rig Connectors

3.2.2.2 Power Connection

The power connection is a standard IEC Inlet Port mounted on the rear of the chassis as shown in6. There is no external facility on the Laboratory Rig to adjust the input voltage range, it is preset to240V ac.

Connection to the rig should only be attempted with the power switched OFF.

Note: To conform to the requirements of BS EN60950, the socket outlet shall be close to theequipment and easily accessible.

1

RS232/1

e

Discretes

RS232/2

1
RS422/
2
RS422/
CMU LAN1

ARINC 429

FMU LAN

VentilationInput

8

Fig


VentilationInput

VentilationOutput


Figure 6 Laboratory Rig Power Connection

The System utilises potentially LETHAL VOLTAGES. It mustnot be operated unless installed as specified in thisdocument.Equipment must be disconnected from power before andduring any close inspection of the equipment interior.Warning

3.3 Component Replacement

The MA-AFAS rigs comprise a VME chassis that contains a Hard Drive Unit and a number of Printed Electronic Circuit (PEC) cards. In some installations, the installer may be required to aremove some, or all, of the components. To accomplish this, the following procedures should followed.

Many of the semiconductor components used in themanufacture of the equipment are sensitive to ElectrostaticDischarge, which can cause them to fail. All ESD sensitiveparts, assemblies and equipment should be handled withESD precautions.Caution

3.3.1 Externally Mounted Components

This section deals with those components (depicted in Fig 4) that are removed from the front oChassis. The removal and replacement procedure is the same for each type of PEC.

n
PowerConnectio
Page 9

VMEdd orbe

f the



3.3.1.1 PEC Removal

The following procedure should be carried out at an ESD workstation with the operator and equipmentat the same voltage potential:

a) Any cables should be unplugged from the connectors on the PEC front panel. This mayinclude cables to other PEC’s adjacent to the PEC to be removed in cases where thesecables interfere with the extraction process.

b) The two retaining screws at the top and bottom of the PEC front panel should be loosened.Note that these screws are of the captive type and should not be removed completely. In thecase of the MVME761, this action will allow the item to be removed from the chassis byunplugging the ribbon cable from the connector on the MVME761. To facilitate this action, itmay be desirable to remove one, or more, blanking plates covering slots adjacent to the PEC.This is achieved by loosening the captive screws at the top and bottom of the blanking plate.

c) For the other type of card which have extraction ’ears’ fitted, the operator can now extract thecard by pushing the ’ears’ apart with the thumbs of each hand. I.e. the upper ear should bepushed up and out, and the lower ear should be pushed down and out. By this action, thecard will be extracted approximately 1cm, sufficient to disengage the two 96 way connectorsthat attach the card to the motherboard.

d) The PEC is now free to be completely removed from the chassis by sliding the cardperpendicularly out from the chassis along its internal guide rails. The card should be storedin a suitable anti-static bag.

3.3.1.2 PEC Insertion

To insert MVME5100 or ARINC429 PEC’s, the following procedure should be carried out at an ESDworkstation with the operator and equipment at the same voltage potential:

a) Any cables should be unplugged from the connectors on the front panels of PEC’s adjacent tothe PEC to be removed in cases where these cables may interfere with the insertion process.

b) Remove the PEC from it’s protective anti-static bag and, holding the ears on the front panel,insert the PEC into the plastic guide rails of the required slot. Slide the card into the chassisuntil only 1cm of the PEC protrudes from the chassis.

c) Position the two ears in the inserted position and, using the thumb of each hand, use the earsto apply pressure to the PEC and firmly push the card home into the chassis. At this stage,the PEC front panel should be flush with the other card front panels and the blanking plates.

d) Tighten the two retaining screws at the top and bottom of the PEC front panel and re-connectany connecting cables to the unit.

3.3.1.3 MVME761 Insertion

To insert a MVME761 PEC, the following procedure should be carried out at an ESD workstation withthe operator and equipment at the same voltage potential. The procedure described assumes that theassociated MVME761P2 and ribbon cable has already been fitted as described in section 3.3.2.1:

a) Any cables should be unplugged from the connectors on the front panels of PEC’s adjacent tothe PEC to be removed in cases where these cables may interfere with the insertion process.To facilitate the insertion process, adjacent blanking plates may be removed to allow easieraccess to the ribbon cable.

b) Remove the PEC from it’s protective anti-static bag and, holding the front panel, connect theribbon cable to the connector at the rear of the unit.



c) Taking care that the ribbon cable does not get trapped, insert the PEC into the plastic guiderails of the required slot. Slide the card into the chassis until the PEC is flush with other cardfront panels and blanking plates in the chassis.

d) Tighten the two retaining screws at the top and bottom of the PEC front panel, replace anyblanking plates removed during the insertion process, and re-connect any connecting cablesto the unit.

3.3.1.4 Hard Drive Removal and Insertion

The HDD is mounted on a mounting tray that is removed from the front of the chassis using thefollowing procedure. Fig 4 shows the front view of the mounting tray and Fig 7 shows the rear view ofthe tray. The removal/insertion process may be facilitated by the removal of the rear panel of thechassis.

a) Remove the entire left hand side of the chassis by releasing the 4 captive screws positionedat each corner of the aluminium front panel that holds the HDD.

b) Slide the mounting tray assembly forward on its runners until the connecting cables can bereached. Disconnect both the power cable and the ribbon cable that connects the HDD to thechassis. Slide the mounting tray assembly clear of the chassis.

c) The HDD is fitted to a HDD adapter tray. This in turn is attached to the mounting trayassembly. In order to remove the HDD for replacement, the HDD adapter tray should bedetached from the mounting tray assembly by the removal of the 4 screws that hold the twoitems together.

d) Lastly, the HDD Adapter Tray should be removed from the HDD by releasing the 4 screwsthat join the items. Note: some HDD adapter trays comprise two spacer rails that ’fill the gap’between the HDD and the mounting tray assembly. As such, these items may be individuallyfitted to each side of the HDD by 2 screws.

e) Replacement of the HDD into the chassis is the reversal of the above procedure. Care shouldbe exercised when replacing the HDD into the HDD Adapter Tray as often this fitment allowsa lot of freedom in placement of the HDD.

3.3.2 Internally Mounted Components

This Installation Guide does not deal with maintenance issues so this section only deals with theremoval and fitting of the internal MVME761P2 adapter boards and doesn’t attempt to describe fittingof any other internal component. The location of the two MVME761P2 adapters is shown in Fig 7.



Figure 7 Chassis Interior

3.3.2.1 Fitting the MVME761P2 Adapters

There are two MVME761P2 adapters fitted to the MA-AFAS chassis; one on the rear of the FMUprocessor, the other on the rear of the CMU processor. To gain access to the rear of the VMEmotherboard, the rear panel of the chassis (see Fig 6) should be removed by releasing the 4 captivescrews holding the panel to the chassis frame.

The adapters are attached to the VME motherboard using a single 96way connector which connectsto the lower (P2) connector on the motherboard. Note that on some motherboards, the P2 connectorsdo not have shrouds as shown in Fig 7, instead there are only 96 pins in rectangular arrays. In thiscase, care should be exercised to ensure that the adapters are in the correct orientation (as shown inthe Figure) and that all 96 pins align and mate correctly with the socket on the adapter.

The adapter(s) should be oriented as shown in Fig 7, i.e. component side towards the left hand wall othe chassis. For each adapter the process will be easier if the ribbon cable is attached to the adapterprior to fitting the adapter to the motherboard: J2 is used for the SCSI cable and J3 for the MVME761interface ribbon cable (see Fig 8 for the locations of these connectors).

HDD inMountingTray

RibbonCable

761P2Adapters

HDDPowerConnector

f

SCSICable



Figure 8 MVME761P2 Adapter Layout



4 SOFTWARE INSTALLATIONFor development configurations, the operational software will be held on a support PC, either Desktopor Laptop, and transferred to the Avionics Rig at system initialisation using the facilities provided bythe Tornado2 development environment. Software updates will be provided from Rochester, ascomplete packages that replace those already on the PC hard drive. By convention, releases ofsoftware will reside in the directory:

C:/MA-AFAS/Build_xx

Where xx indicates the build and will comprise A, B, C1, C2 etc. The correct version of software willthen be selected using two script files, FmuScript.spt and CmuScript.spt as described in the AvionicsRig Users Guide. The setup of Tornado at Rochester will not be described in this document, butAppendix B gives details of using Tornado2 on-site.

During development, software for the flight rigs will be held on a host PC; either Laptop or Desktop(IHTP). Software installation here is a matter of copying or unzipping the distribution to the hard drivein the directory identified above.

When the system is mature enough, software for the Flight rigs will be held on the internal hard driveunit controlled by the FMU. Upon despatch from the Rochester factory, each rig will contain the realtime operating system and the latest available software. Thus, the only installation needed will be theincorporation of periodic software updates. To perform a software update, relevant files will betransferred from an In House Test Platform (IHTP) to the rig using the facilities provided by theTornado development system.

Configuration of the Software used in the Avionics Rig is included in the Avionics Rig Users Manual.



5 ACCEPTANCE TESTINGCurrently, testing of the units will be accomplished using the standard flight software.



APPENDIX A MVME5100 JUMPER SETTINGS

The MVME5100 processor cards have a number of user modifiable jumpers fitted. For MA-AFAS,both FMU and CMU processors can be configured the same as defined in Table 3

Jumper Settings Description

J4 No Jumpers (of 4) LAN2 on front connector

J6, J20 2 and 3 connected SBC Mode

J7 1 and 2 connected Bank A

J10, J17 1,3 and 2,4 connected LAN2 on front connector

J15 2 and 3 connected AUTO SCON

J16 1 and 2 connected Flash Programming Enabled

Table 3. MVME5100 Jumper Settings



APPENDIX B DEVELOPMENT ENVIRONMENT INSTALLATION

B1 On-Site Tornado Settings

When used stand alone on-site, the Tornado2 environment has to be self contained. I.e. the PC thathosts Tornado 2 must also provide the necessary Tornado Registry and Tornado FTP functions.These are provided by two applications; Tornado Registry and FTP Server.

On standalone installations, the host PC must have a common ihtpguest account for non-BAESusage. This account should be set up to run the two applications at startup. It is not deemednecessary to have these two services start before ihtpguest login.

B1.1 FTP Server Configuration

Configuration of the FTP server is achieved once the application is running. Using the Security Dropdown menu, the Users/Rights option should be selected. This generates a window that allows thecreation of a new user by use of the New User… button. Pressing this will invoke another window thatshould be used to add the user ‘tornado’. Pressing OK causes the password window to be displayed.The password ‘tornado’ should be input here; twice for confirmation. The User/Rights Security Dialogwill again be displayed.

The home directory for user tornado should be added next. By convention, this is C:/MA-AFAS. TheDone button closes the window and saves the data.

By default, FTP logging is disabled. To enable it, the Logging:Log Options menu item should be used.This provides a dialog box for the user to define the level of logging require. A good minimum is toenable logging of Gets, Puts and Warnings. OK stores the options and removes the dialog box. Note:it is not necessary to have the FTP Server window in view during normal operation. It can therefore beminimised.

B1.2 Tornado Registry Configuration

There is no configuration required for the Tornado Registry application. However, the WindowsRegistry needs to be modified to identify to the target servers where the Tornado registry is hosted.

This is achieved by using a .reg file, with the following contents, to modify the registry:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Wind River Systems\Tornado 2.0]"WIND_REGISTRY"="rc2475"

The relevant PC name, or ‘localhost’, should be inserted instead of RC2475 (which is the identifier forthe Rochester central registry server) but everything else should appear as above. The registry filecan then be ‘run’, using the ihtpguest login account, by double clicking on its icon, to insert the newdata into the Windows registry.

B1.3 Target Server Setup

The Tornado2 application is used to control each of the PowerPC processors in the Avionics Rig.Before loading the software from the host to the target for the first time, the Tornado Target serversneed to be configured. This is done from the main window of Tornado2 using the Tools:TargetServer:Configure…. Pull down menu item. This invokes the ‘Configure Target Servers’ window asshown in Fig 9. On new installations, this window will not identify any target servers. Note that thisdata is stored in the user profile area of the C drive and so is available only to the logged in user.



Figure 9 Configure Target Servers Window

For a new configuration, the ‘New’ button should be clicked; this will add a default configuration,called Configuration 1, to the window. This default configuration can then be modified for the specificproject needs.

Firstly, the Description panel is used to identify the Target Server. The default Configuration 1 shouldbe replaced by the appropriate PowerPC identifier; e.g. ma-afas01 to ma-afas10. The Add Descriptionto Menu item should be checked and the PowerPC identifier repeated in the Target Server Namepanel.

Next, the Target Server Properties pull down menu should be used to define the target server asfollows:



Authorizations: This should be left as the default setting.

Backend: set to wdbrpc with 60 timeout and 6000 retries.

Core File and Symbols: This identifies the location of the VxWorks kernel that is downloaded tothe target at switch-on. For on-site installations, the default for the FMUprocessor is C:/ma-afas/build_xx/bin/VxWorks/fmu/VxWorks and for theCMU C:/ma-afas/build_xx/bin/VxWorks/cmu/ma-afasyy-VxWorks. xxindicates the software build (e.g. D3, E1 etc) and yy the CMU processornumber (i.e. 02, 04, 06, 08 or 10).

Memory Cache Size: This should be specified as 16384.

Target Server File System: This should be left as the default setting.

Console and Redirection: The Redirect Target I/O option should be checked.

Logging: This should be left as the default setting

Miscellaneous: This should be left as the default setting.

Finally, the Target Name/IP Address Box should be used to identify the IP Address of the PowerPC.

The information entered does not need saving as it is automatically stored on data entry. The Copybutton can be used to create a copy of the Target Server properties that can then be edited to asubsequent PowerPC. It is usual for only 2 Target Servers to be specified for any single installationand user.

The Target Server Window can be removed by use of the Cancel button, and the target serversstarted using the procedure identified in the Avionics Rig User Guide.



APPENDIX C CPDLC GROUND STATION

C1 General

The ground installation for the Controller Pilot Data Link Communications (CPDLC) comprises theTaxi and ATC Tool (TAT), a Windows PC and a Ground VDL Mode 4 Transponder as shown in Fig10.

IHTPApplication

GroundRouterApplication

Windows PC

GroundTransponder

LINUX PCPower Panel

TAXI and ATC Tool

Figure 10 Ground Components for CPDLC

Connections between the TAT and the Windows applications are achieved using ethernet. Theconnection to the transponder is RS232.

Installation of the ground station involves physical connection, ethernet configuration andcommunications configuration of the units.

C2 Physical Connections

C2.1 Power Panel

The rear of the power panel hosts 9 connector for power, data and video connection. For MA-AFAS,only the power (#1) and ethernet (#5) connectors are used.

Power is supplied to the Power Panel from a DC power supply. The PP can accept voltages in therange 18 to 60 V and consumes 25W of power. On connector #1, pin 1 is +V and pin 8, ground.

The ethernet connection is via connector #5 which is a standard RJ45 connector.

C2.2 Ethernet

The Power Panel, Linux PC and the Windows PC all need to be connected via ethernet to a centralhub/switch. If the transponder is used then this ethernet LAN can be separate from that of the flyingrig. However, if the ethernet test network is to be used to connect the ground and air routers that thesame LAN should be used for both systems.

C2.3 Ground Transponder

The ground transponder is powered from the mains or +28V DC supply dependant upon the unitused.



Data connection between the transponder and the Windows PC is achieved using a 9 pin Null modemcable from COM 1 of the PC to the Display connector of the transponder mounting tray.

C3 Ethernet Configuration

C3.1 Power Panel

Setup for the Power Panel is achieved using the host Linux PC. At switch on, the PP uses theBOOTP protocol to request its ethernet parameters from a BOOTP server. The PC performs thisservice and thus requires a bootptab file in the /etc directory. Data in the bootptab file comprises asingle entry for each supported Power Panel:

ma-afas1:hn:ha=0001BB000097

where ma-afas1 is the network name of the Power Panel, hn indicates that the BOOTP server shouldtell the Power Panel its name and hn=0001BB000097 is the MAC address of the PP as shown in thetop left hand corner of the PP display at switch on.

Associated with the bootptab entry is the inclusion of the Power Panel IP address in the host machinehosts file (also in the /etc directory). The following line is used in the hosts file on the Frequentismachine in association with the above bootptab entry:

10.4.71.34 ma-afas1

The result of this is that the PP with the MAC address of 00:01:BB:00:00:97 is given the networkname of ma-afas1 and the IP address of 10.4.71.34.

C3.2 LINUX PC

The PC used to control the Power Panel is a standard LINUX PC running REDHAT (7.2 or 8.0). Assuch, the IP Address configuration is standard, and is modified using the System:NetworkConfiguration menu item. (Alternatively, Control Panel:Network Configuration) This invokes theNetwork Configuration window that, through the Edit button, gives access to the Ethernet Devicewindow. Note: To edit the network data the superuser password is required for the machine andshould be entered at the prompt.

The Devices panel of the Ethernet Device GUI can then be used to set the IP Address, Net mask anddefault gateway for the PC. For the Frequentis unit at Rochester, the required values for these threeitems are 10.4.71.35, 255.255.192.0 and 10.4.127.254.

The Hosts panel of the Ethernet Device GUI can be used to identify the IP address of the PowerPanel; in the above example, the name of the PP is ma-afas1 and the IP address is 10.4.71.34.

Following modification of the data, clicking Close will cause a ‘Save Changes?’ confirmation dialogbox to appear. On clicking ‘Yes’, the new values are saved and used. (Note: it is not necessary toreboot the PC for the values to take effect.)

C4 Communications Configuration

Four router configurations are available for use on MA-AFAS; Air or Ground router with RS232/422 orethernet connections.

The router application uses a script file to set up the required configuration and invoke the software.The filename of the script identifies the particular configuration using the codes B (ethernet), C(RS232), 1 (air router) and 2 (ground router). Each script file identifies the ethernet addresses for theparticular installation.



For a ground router interfacing to a transceiver, two files are used to invoke the software; CfgC.sh andStart_configC_R2.sh, and these are run from within a Cygwin shell.

C4.1 Cygwin

Cygwin provides a UNIX environment for Windows. It is a freely available application that is used onMA-AFAS to run the Airtel provided ground router software.

Cygwin is best installed direct from the Internet (see www.cygwin.com) and is invoked using thedesktop icon. This brings up a shell window that can be used to run the router software.

C4.2 Configuration Files

The standard file set from Airtel includes a number of configuration files for both Air and Groundrouters. For the ground router, four files should be configured with installation specific details; cfgB.sh,cfgC.sh, start_cfgB_R2.sh and start_cfgC_R2.sh. The template for the cfgB.sh and cfgC.sh files isgiven in Fig 11 and shows that 3 configuration items are required.

## Configuration B#

# Router 1 is an Airborne ESexport AAS_R1_IP={IP Address of CMU}

# Router 2 is a Ground ESexport AAS_R2_ATNR={Full pathname}/gnd_aas.exeexport AAS_R2_IP={IP Address of Ground Router}

Figure 11 cfgB.sh Template

Fig 12 gives the template for the start_cfgB.sh and start_cfgC.sh files. Configuration of these two filescomprises the definition of the full path to the top level scripts directory (aas-scripts).

Note that the directory {pathname}/aas-logs must exist or log files will not be stored.

In the RS232/422 configuration, the default COM port used is COM1. If the PC hosting the groundrouter requires the use of COM port 2 for connection to the Avionics Rig, file maafas_cfgC_R2.inp inthe …/aas-scripts/scenarios directory will need to be modified. Fig 13 shows the relevant portion ofthe file that defines the COM port used: SerialPort 0 defines COM1 and SerialPort 1 defines COM2.Note: It is important that no extra lines are introduced into this script file, as this will cause errors atrun time.

http://www.cygwin.com/



#!/bin/bash

if [[ -z $AAS_R2_ATNR ]]then echo "AAS_R2_ATNR not set" exit 1fi

if [[ -z $AAS_R1_IP ]]then echo "AAS_R1_IP not set" exit 1fi

if [[ -z $AAS_R2_IP ]]then echo "AAS_R2_IP not set" exit 1fi

export AAS_TEST={full pathname}/aas-scriptsexport SCENARIOS=$AAS_TEST/scenariosexport SCRIPTS=$AAS_TEST/scriptsexport DATE_TIME=‘date ’+%d%m%y_%H%M%S’‘export LOGS=$AAS_TEST/../aas-logs/

export AAS_IPADDRESS=$AAS_R2_IP. $AAS_TEST/env_Gnd.shexport ATNR=$AAS_R2_ATNR

$ATNR -i scenarios/maafas_cfgB_R2.inp | tee ${LOGS}/${DATE_TIME}_maafas_cfgB_R2.out

Figure 12 start_cfgB_R2.sh Template

define circuitFM circdefine circuitFMInterface 3define hostFM $vdl4SNPAgnddefine securityFM $secATSCAdefine serialPort 0redir input ${SCRIPTS}/cir_vdl4_cre.inpwait 5

Figure 13 Part of the maafas_cfgC_R2.inp File

Installation Guide for the Avionics Rig - ASAS TN · PDF fileAirtel ATN Ltd (Ireland) QinetiQ...

Documents

Transcript of Installation Guide for the Avionics Rig - ASAS TN · PDF fileAirtel ATN Ltd (Ireland) QinetiQ...