615A Dataloader®

User Guide

80459 Revision N
February 13 , 2015
 615A Dataloader
User Guide

PROPRIETARY STATEMENT: This is confidential and proprietary information of

Teledyne Controls and may not be used or disclosed by the recipient without the
prior written consent of Teledyne Controls and then only in accordance with
specific written instructions of Teledyne Controls. By receipt hereof, in addition
to any obligation the recipient has under any confidentiality agreement with
Teledyne Controls, neither recipient nor its agents, representatives or employees
will copy, reproduce or distribute this information, in whole or in part, at any time,
without the prior written consent of Teledyne Controls and that it will keep
confidential all information contained herein.
© Copyright 2011-2015 by Teledyne Controls All rights reserved. Printed in the U.S.A.

No part of this document may be transmitted, reproduced, or copied in any form or by

any means without the prior written consent of Teledyne Controls Inc. Due to Teledyne
controls commitment to constantly improve the quality and performance of our products,
information contained in this document is subject to change without notice.

Teledyne Controls
SBU of Teledyne Electronics Technologies
501 Continental Boulevard.
El Segundo, CA 90245

Phone : (310) 382 - 5816 (AOG Support)

Fax (310) 765-3604/5

80459 Revision N February 13, 2015 Page I

 615A Dataloader
User Guide

RECORD OF REVISIONS
Affected
Rev No. Issue Date Inserted By Description Pages

Original 6/4/03 Vince Brown Original Issue

Issue
A 05/27/2004 Vince Brown Added Compare Load 5, 6, 7, 8, 9,
Section; updated screen 10, 11, 12, 13,
shots. 14, 15
B 07/19/2004 Vincent Brown Deleted Compare Load 5-9, 11
Section; updated screed
shots
C 03/10/2006 J.Maurer Update for Media Defined All
Download &Software
Version 12.0
D 11/16/2006 Gerald Tamayo Update Screen shots to All
current version.
E 04/03/2008 Gerald Tamayo Include installation on All
Windows PC. Add block
size configuration.
F 07/11/2008 Gerald Tamayo Update ARINC 615A 24-40
Configuration Options
Guide
G 01/27/2009 David Moshier Update ARINC 615A CAN 39-40
Configuration Options
H 03/30/2009 David Moshier Update ARINC 615A CAN 39-40
Configuration Options
J 04/13/2011 Gerald Tamayo Implement Teledyne All
Controls template and add
appendix
K 09/29/2011 Gerald Tamayo Update Figures to All
correspond with current
software version
L 10/08/2012 Jorge Valdez Corrected phone number. I, 1, 2, 4,33-40
Windows 7 reference
document. Included
Teledyne Controls contact
information. Added 615A-3,
udated section 7.5 AFDX
Network Configuration.

80459 Revision N February 13, 2015 Page I

 615A Dataloader
User Guide

M 6/24/2012 Jorge Valdez Updated Screen shots to All

current current version.
Removed 665 Parts
Manager. Added Appendix
B.

N 2/13/2015 John Cuadra  Updated contact 2, 4,7,10

phone number
 2.1 Reference
Documents
 Figure 3-1 removed
 Section 5.1
reworded
 Figure 5-3 re-done
 Cover image
changed

80459 Revision N February 13, 2015 Page I

 615A Dataloader
User Guide

TABLE OF CONTENTS

1.0 Introduction ........................................................................................................... 1

2.0 REFERENCES ..................................................................................................... 2
2.1 Reference Documents ...................................................................................... 2
2.2 Document Conventions ..................................................................................... 2
3.0 HARDWARE SETUP ........................................................................................... 3
3.1 Install 615A Dataloader on PMAT 2000 ............................................................ 3
3.2 Uninstall 615A Dataloader from PMAT 2000 .................................................... 3
3.3 Install 615A Dataloader on Windows PC .......................................................... 4
3.4 Uninstall 615A Dataloader from Window PC..................................................... 5
3.5 Upgrade to a New Version of 615A Dataloader ................................................ 5
4.0 TRANSFERRING PARTS TO THE INTERNAL HARD DRIVE............................. 5
4.1 LoadStar ........................................................................................................... 5
5.0 615A DATALOADER SOFTWARE ...................................................................... 5
5.1 Start Up ............................................................................................................. 5
5.2 User Information ............................................................................................... 6
5.2.1 User Name ............................................................................................... 6
5.2.2 Date/Time ................................................................................................. 6
5.3 Select Tail Number ........................................................................................... 7
5.4 Select Connection Type .................................................................................... 7
5.4.1 Default Connection Types ........................................................................ 8
5.5 Go Back ............................................................................................................ 8
5.6 Select an Operation .......................................................................................... 9
5.6.1 Available 615A Targets .......................................................................... 10
5.6.2 Session Status Window .......................................................................... 11
5.6.3 Get Information....................................................................................... 11
5.6.4 Operator Defined Download ................................................................... 12
5.6.5 Media Defined Download ....................................................................... 14
5.6.6 Upload .................................................................................................... 15
5.6.7 Batch Operation ..................................................................................... 21
5.7 Multiple Operations ......................................................................................... 23
5.8 Log Window .................................................................................................... 23
5.9 Select an Operation ........................................................................................ 23
5.10 Help ................................................................................................................ 24
5.11 Battery Charge Status ..................................................................................... 24
6.0 615A LOG .......................................................................................................... 25
7.0 ARINC 615A CONFIGURATION OPTIONS GUIDE ........................................... 27
7.1 Overview ......................................................................................................... 27
7.2 Network Configuration XML File ..................................................................... 27
7.3 615A Parameters ............................................................................................ 28
7.3.1 Available 615A Targets .......................................................................... 28
7.3.2 Server Port Override .............................................................................. 29
7.3.3 Client Port Override ................................................................................ 29
7.3.4 615A-3 Port Option................................................................................. 30
7.3.5 TFTP Block Size Overrides .................................................................... 30

80459 Revision N February 13, 2015 Page I

 615A Dataloader
User Guide

7.3.6 FIND Broadcast ...................................................................................... 31

7.3.7 Target Definitions ................................................................................... 31
7.4 Ethernet Network Configuration ...................................................................... 32
7.4.1 Ethernet Specific Parameters ................................................................. 32
7.4.2 Ethernet Configurations .......................................................................... 33
7.5 AFDX Network Configuration .......................................................................... 36
7.5.1 Overview of AFDX dataloading .............................................................. 36
7.5.2 The Network configuration file ................................................................ 37
7.5.3 CFDX configuration file for GE driver V1.2 ............................................. 38
7.5.4 BFDX configuration for GE driver V3.1 ................................................... 41
7.6 CAN Network Configuration ............................................................................ 43
7.6.1 CAN Specific Parameters ....................................................................... 43
7.6.2 CAN Network Configuration Files ........................................................... 44
7.7 BFDX Network Configuration .......................................................................... 46
8.0 GLOSSARY ........................................................................................................ 47
Appendix A .................................................................................................................... 48
Appendix B .................................................................................................................... 49

80459 Revision N February 13, 2015 Page I

 615A Dataloader
User Guide

TABLE OF FIGURES
Figure 5-1. Log-In Screen ............................................................................................. 6
Figure 5-3. Operation Menu .......................................................................................... 9
Figure 5-4. Target List ................................................................................................. 10
Figure 5-5. Target LRU Busy ...................................................................................... 11
Figure 5-6. Get Information ........................................................................................ 12
Figure 5-8. Download Select Window ........................................................................ 13
Figure 5-8. Download SSW ......................................................................................... 13
Figure 5-9. Media Defined Download Selections ...................................................... 14
Figure 5-10. Confirm Media Download Window........................................................ 15
Figure 5-11. Media Defined Download SSW .............................................................. 15
Figure 5-12. Upload From MSD .................................................................................. 16
Figure 5-13. Upload From Select By Attributes ........................................................ 17
Figure 5-14. Upload From Removable Media ............................................................ 17
Figure 5-15. Upload Information Window .................................................................. 18
Figure 5-16. Verify SSW .............................................................................................. 19
Figure 5-17. Upload Confirmation Window ............................................................... 19
Figure 5-17. Upload SSW ............................................................................................ 20
Figure 5-19. Batch Load Information Window .......................................................... 21
Figure 5-20. Batch Upload Warning ........................................................................... 22
Figure 5-21. Confirm Batch Upload ........................................................................... 22
Figure 5-22. Multiple Operations ................................................................................ 23
Figure 5-23. Operation Waiting .................................................................................. 23
Figure 5-24. Go Back Warning Window ..................................................................... 24
Figure 5-25. Battery Status Icons .............................................................................. 24
Figure 6-1. 615A Log ................................................................................................... 25
Figure 6-2. 615A Log Files .......................................................................................... 26
Figure 6-3. No Signature Present ............................................................................... 49
Figure 6-4. Signature Not Valid .................................................................................. 50
Figure 6-5. Signature Valid ......................................................................................... 50

80459 Revision N February 13, 2015 Page I

 615A Dataloader
User Guide

1.0 Introduction
This document describes the functionality and operation of the 615A Dataloading
Software. The 615A Dataloading Software performs the following functions:

 Upload - Transfer of data from the loader to the Target Line Replaceable Unit
(LRU).
 Operator Defined Download - Transfer of data from the Target LRU to the loader.
 Media Defined Download - Transfer of data specified by the download media
from the Target LRU to the loader.
 Get Information - Retrieves hardware and software information from the Target
LRU selected by the user.
 Batch Operation - Allows the user to load a predetermined set of multiple
Loadable Software Parts (LSPs) on multiple Target LRUs.

The software is designed to interoperate with LoadStar Configuration Management

software from Teledyne Controls and be fully integrated into the PMAT 2000® platform
providing a single tool for the maintenance and dataloading of ARINC 615A, 615A-1,
615A-2 and 615A-3 compatible LRU avionics.

This manual covers operation on a PMAT 2000 from Teledyne Controls and operation
on a Windows PC.

If you are running on a PC or laptop, the following are the minimum requirements
Feature Minimum Requirement
Operating Windows XP Pro or greater
Systems
Processor 500MHz, x86 (XP)
RAM 256MB (XP)
Hard Drive 60GB
Size
Media Drive CDROM, DVD
Ethernet port 10/100 BaseT, 1 port
Display 1024 x 768, color, 128MB graphics
memory
Loading over AFDX or BFDX buses requires a GE Fanuc AFDX CNIC card be installed
in the PMAT 2000 or Windows PC.

Loading over the CAN bus is only available on the PMAT 2000.

80459 Revision N February 13, 2015 Page 1

 615A Dataloader
User Guide

2.0 REFERENCES

2.1 Reference Documents

Teledyne Controls Documents:
80010 PMAT 2000(80000-05) User’s Guide
80010-1 PMAT 2000(80000-06) User’s Guide
59721 LoadStar User’s Guide
80697 License Requestor User’s Guide

Others:
ARINC 615A Specification Document; Release Date: November 24, 1999
ARINC 615A-1 Specification Document; Release Date: January 12, 2001
ARINC 615A-2 Specification Document; Release Date: May 10, 2002
ARINC 615A-3 Specification Document; Release Date: June 30, 2007
ARINC 665-1 Specification Document; Release Date: July 12, 2001
ARINC 665-2 Specification Document; Release Date: August 30, 2002
Microsoft® Windows 2000® User’s Manual
Microsoft® Windows XP Professional User’s Manual
Microsoft® Windows Vista Business User’s Manual
Microsoft® Windows 7 User’s Manual

2.2 Document Conventions

The following notational conventions are used in this manual.
Bold Italic Bold italic Arial typeface represents text or buttons displayed on the
screen
Bold Bold courier typeface is used for anything that you must type
KEYCAP Regular courier typeface represents a key on the Keyboard - for
example "Press ENTER to continue".
The mouse is used the majority of the time to position the cursor over a button
displayed on the screen. The following convention is used to activate the displayed
button's function.
select Italics means use the mouse to move the cursor over the displayed button
and press and release the left button of the mouse.

80459 Revision N February 13, 2015 Page 2

 615A Dataloader
User Guide

3.0 HARDWARE SETUP

3.1 Install 615A Dataloader on PMAT 2000

This section provides the general procedures to install the 615A Dataloading Software
onto the PMAT 2000.
Note: The PMAT 2000 user must be logged on as an Administrator to install any
software onto the PMAT 2000.
WARNING: Before you start the installation process, close all open Windows
applications! Make sure your PMAT 2000 has enough hard drive storage space
to install the program (approx. 20MB).
An external CD-ROM Drive is required for CD-ROM installations. Please refer to the
PMAT 2000 User’s Guide (P/N 80010 or 80010-1) for the instructions on how to
connect the PMAT 2000 to a CD-ROM drive.
To install the 615A Dataloading Software (CD) program on the PMAT 2000 Windows
2000 Professional® or Windows XP Professional ® operating system, follow these
steps:

1. Make sure the CD-ROM drive is connected to the PMAT 2000 and turned ON.
2. Put the 615A Dataloading Software Installation CD (P/N 82112) into the
CD-ROM.
3. Exit PMAT 2000 Main Menu to Windows desktop.
4. Select Windows 2000 Professional ® Start button.
5. Select the Run button
6. Select Browse
7. Look in the CDROM drive (example E: )
8. Select the program “Setup.exe”
Follow the 615A Dataloading Software setup instructions that appear on the screen.
The setup process takes approximately 5 minutes. After the installation completes, the
user is asked to reboot the unit. Select Yes to reboot. When the Main Menu is
displayed after the PMAT 2000 is rebooted, an application button labeled ARINC 615A
Dataloader is now included on the Main Menu.

3.2 Uninstall 615A Dataloader from PMAT 2000

To uninstall the 615A Dataloading Software, simply run the setup.exe program on the
615A Dataloader Installation CD once again. The 615A Dataloading Software
Installation program will run but only present the user uninstall options. Follow the
uninstall wizard which guides the user through the removal process. 615A
Dataloading Software can also be removed via the Add/Remove Programs feature
found in the Windows Control Panel.

80459 Revision N February 13, 2015 Page 3

 615A Dataloader
User Guide

3.3 Install 615A Dataloader on Windows PC

You must be logged onto the PC with administrator rights to install the software.

1. Insert the 615A Dataloader Desktop Package CDROM (P/Ns 82121, 82131, or
82141) into a CD-ROM drive.
2. Go to the 615A Dataloader Installer directory and run setup.exe to install the
615A Dataloader application.
3. Go to License Requester Installer directory and run setup.exe to install the
Teledyne Controls License Request application.
4. Go to Start→Programs→Teledyne Controls and select the "License Requester"
shortcut
5. A Teledyne Controls License Requester screen will be displayed.
6. Enter all the user information and select the 615A Dataloader option.
7. Select the Get License button.
8. A message stating the location of the License request file will be displayed.
9. E-mail the license request file to Teledyne Controls Customer Support-Data
Loading Solutions
http://www.teledyne-controls.com/services/airtranspersonnel.asp
10. A license file will be e-mailed by Teledyne Controls to you.
11. After receiving the license file, Go to Start|Programs|Teledyne Controls and
select the "Teledyne Controls License Requester" shortcut.
12. A Teledyne Controls License Requester screen will be displayed.
13. Select the Install License button.
14. An "Install License" screen will be displayed.
15. In the "License File" box type the location of the license file e-mailed by
Teledyne Controls or use the "..." button to browse to the location.
16. Select the License File and select the Install button.
17. A successfully installed license message will be displayed.
18. Select the GO BACK button.
19. Select the Exit button.
The 615A is now licensed for the PC it is installed on. The license is not transferable
to another PC. To transfer the 615A application to another PC, uninstall the 615A
application from the current PC and repeat the installation steps above. You will need
to request a new license for the new PC.

80459 Revision N February 13, 2015 Page 4

 615A Dataloader
User Guide

3.4 Uninstall 615A Dataloader from Window PC

To uninstall 615A Dataloader from a PC, insert the 615A Dataloader Disc into a CD-
ROM and run the setup.exe under the 615A Dataloader installer directory. Follow the
instructions displayed.

3.5 Upgrade to a New Version of 615A Dataloader

WARNING: Before upgrading the 615A Dataloader Application, please save the
NetworkConfiguration.xml file located at c:\datafiles\configuration\615A. The default
Network settings installed by the 615A Dataloader may not be same as the previous
network settings.

To upgrade, first uninstall the 615A Dataloading Software and then install the new
version. After installation, run the 615A software and verify the new version number is
displayed in the title bar.

4.0 TRANSFERRING PARTS TO THE INTERNAL HARD DRIVE

4.1 LoadStar
On a PMAT 2000, the 615A Dataloader Software uses Teledyne Controls Loadstar
Configuration Management software to manage the configuration of the 665 Loadable
Software Parts (LSP) stored on the hard drive. Aircraft model and tail number
information is also obtained from Loadstar. (For more information on Loadstar
operation, refer to the Loadstar User’s Guide P/N 59721.)

5.0 615A DATALOADER SOFTWARE

5.1 Start Up
Power up the PMAT 2000, allow the PMAT 200 to complete its boot sequence and the
PMAT 2000 Main Menu is displayed. Select the ARINC 615A DATALOADER button
to open the application. The 615A Datalaoder Log-In screen shall appear. (See Figure
5-1)

For the Windows PC environment open the ARINC 615A DATALOADER application
by selecting the Start Button on the Windows Taskbar, select All Programs, then
Teledyne Controls Folder and select 615A Dataloader. Log-in screen will be
displayed as shown in Figure 5-1.

80459 Revision N February 13, 2015 Page 5

 615A Dataloader
User Guide

Figure 5-1. Log-In Screen

5.2 User Information

Section 1 of the Log-In Screen, the User Information section, requires the user to
enter a User Name. This user name, along with the Date and Time, will be recorded in
the 615A Log.

NOTE: The Date and Time displayed by the 615A Dataloading Software is obtained
from the internal date and clock settings of the PMAT 2000 or Windows PC. If the
PMAT 2000 or Windows PC has crossed time zones, the date/time information
recorded in the 615A Log may be inaccurate. It is suggested that the user verify the
date/clock settings to ensure accurate 615A Log data.

5.2.1 User Name

The user is required to enter a User Name to begin his dataloading session. (See
Figure 5-2) This User Name is recorded in the 615A Log. The User Name data is
not used as a security measure, but simply to record the activity of each individual
user in case a problem arises. (e.g. It is discovered that user name “Joe B” was
given a bad disk set and all aircraft that “Joe B” loaded need a software update.)

5.2.2 Date/Time
The Date and Time that the user initiates the session is recorded in the 615A Log.
(See Figure 5-2)
Note: An incorrect date and time will not affect 615A operation.

80459 Revision N February 13, 2015 Page 6

 615A Dataloader
User Guide

5.3 Select Tail Number

In section 2 of the Log-In Screen, a list of tail numbers is obtained from Loadstar and
displayed in the SELECT TAIL NUMBER window. The user may select from the list
the tail number of the aircraft he is loading or select OTHER to enter a new tail
number. This information will be recorded in the 615A Log.

5.4 Select Connection Type

In section 3 of the Log-In Screen, a list of connection options appears in the SELECT
CONNECTION TYPE window. This list is not activated until the user enters the
required User Information and Tail Number. (See Figure 5-2) Once the user enters the
required information, he may choose from the list a connection type specific to the
aircraft he is loading. Continue by selecting the CONTINUE button (labeled as number
4).

The software will change the network configuration settings of the PMAT 2000 to the
connection type chosen by the user.

If the 615A Dataloader is installed on a Windows PC the 615A Dataloader application

will ask users to select the Network Adapter used for loading. When the user selects
the network adapter, the software will change the network configuration setting of the
Windows PC. The network adapter information will also be saved in the
NetworkConfiguation.xml file.

Figure 5-2. Log-In Screen

80459 Revision N February 13, 2015 Page 7

 615A Dataloader
User Guide

5.4.1 Default Connection Types

The 615A Dataloader Software offers a default list of connection types. (See
Figure 5-2) This default list can include:
 615A Loader Standard – Changes the Network IP address to 192.168.1.2
 Electronic Flight Bag – Changes the Network IP settings to connect
software to Boeing’s Electronic Flight Bag (EFB)
 747-8/787 Electronic Flight Bag (EFB)
 Network Defined – Obtains IP address automatically from a DHCP Server.
 Use Existing – Uses the Network Configuration settings present on the
PMAT 2000.
 Thales DMC ADIRU
 Honeywell/THALES FMC
 Airbus ATSU
 THALES OANS
 GP7200/GenX
 Boeing NFS Loader
 Teledyne OIT
 Teledyne WGL comm+
 A380 CVMS
 747-8 EIU
 747-8EMU
 747-8 FMC
 747-8 IDMU
 787-8 SDU
 787 CIS

Reference section 7 for help setting up other connection types.

5.5 Go Back
Selecting the GO BACK button at this point will end the dataloading session and exit
the program.

80459 Revision N February 13, 2015 Page 8

 615A Dataloader
User Guide

5.6 Select an Operation

Once the user completes the Log-In screen, the Operations Menu appears. (See
Figure 5-3) The Session Status Window (SSW) will show the status of all sessions
open. If no sessions are open, then it will display NO SESSIONS IN PROGRESS. The
Log Window lists all operations, including a time/date stamp, performed by the user
during his dataloading session. This information is also recorded in the 615A log on
the PMAT 2000 hard drive. (See section 6.0) The operation buttons available to the
user are Get Information, Operator Defined Download, Media Defined Download,
Upload and Batch Operation. When the Get Information, Operator Defined
Download, Media Defined Download or Upload operation has been selected, a
window appears displaying a list of available 615A Target LRU(s). (See Figure 5-4)

Access to this
User’s Guide
through HELP. See
Section 5.10

SSW Listing
References

Next Page
Previous Page
of SSWs
of SSWs

Close Program
and Return to
Figure 5-3. Operation Menu Main Menu

80459 Revision N February 13, 2015 Page 9

 615A Dataloader
User Guide

Figure 5-4. Target List

5.6.1 Available 615A Targets

The Available 615A Targets list displays the entire list of Target LRUs that the
615A Dataloading software can communicate with via the chosen connection type.
This list includes the Target LRU Name, Target ID Position and a colored status
block. This status block indicates the status of the Target LRU. If the status block
shows GREEN, then the Target LRU is powered-on, connected to the same
network as the dataloader and ready to accept a dataload. If the LRU goes off-line,
then the status block will show YELLOW. If the status block shows a GREEN clock
symbol, then the Target LRU is busy with another operation. (See Figure 5-5)
There is a limit of 15 targets to be selected at a time.Once the user selects the
Target LRUs, select Continue to process.

Note: The status block for some LRUs may show yellow when the LRU is actually
ready to accept a dataload.

80459 Revision N February 13, 2015 Page 10

 615A Dataloader
User Guide

Figure 5-5. Target LRU Busy

5.6.2 Session Status Window

Once the user selects an operation and a Target LRU (Figure 5-4), a Session
Status Window (SSW) appears in the Operation Menu. (See Figure 5-6) This SSW
displays to the user the Target LRU Name, the operation selected, the estimated
time of the operation obtained from the LRU, the elapsed time, the status of the
operation, the data transfer speed and a colored progress bar. The progress bar
shows the progression of the load according to information received from the
Target LRU and is not a function of the 615A Dataloading Software. The
progression of a load may vary with different Target LRU types.

During multiple operations when multiple SSWs are shown, the user can choose
how the SSWs are listed. (See Figure 5-3) By selecting Oldest First, the first SSW
started will appear at the top of the list. Any subsequent SSWs started will appear
below in the order they are started. By selecting Newest First, any new SSWs will
appear at the top of the list, moving all previous SSWs down one. NOTE: The
default setting is set to Newest First.

5.6.3 Get Information

Selecting the Get Information button allows the target to display its current
configuration information so that the user can ascertain the software version(s)
installed on the target computer. This may be used to see if a software update is
required.

80459 Revision N February 13, 2015 Page 11

 615A Dataloader
User Guide

After the user selects a Target LRU, a Get Information SSW appears. (See Figure
5-6) When the Get Information operation has been completed successfully, the
progress bar will show GREEN. The progress bar will show RED if the operation
failed or if the user presses the ABORT button halting the operation. To view the
information from the LRU, select the Show Report button. A window will appear
displaying the data. The user may also view the data by viewing the 615A Log.
(See section 6.0) Once the user has viewed the LRU information, a CLOSE button
will appear. Close the SSW by selecting the CLOSE button.

Figure 5-6. Get Information

5.6.4 Operator Defined Download

Selecting the Operator Defined Download button downloads the data from the
Target LRU’s internal memory. When the Operator Defined Download button and
Target LRU is selected, the user is shown the Download List selection window.
(See Figure 5-7) The Download List displays all the available download files from
the Target LRU’s internal memory. The user must choose the files he wishes to
download from the list by highlighting the filenames with the mouse-pointer. To
select all the files listed, press the Select All button. To clear selected files, press
the Clear Selection button. To terminate the Operator Defined Download
operation, press the Go Back button. Once the files are selected, press the Start
button to begin the download. An Operator Defined Download SSW will appear.
(See Figure 5-8)

80459 Revision N February 13, 2015 Page 12

 615A Dataloader
User Guide

Figure 5-8. Download Select Window

Once the Operator Defined Download operation has been completed successfully,
the progress bar will show GREEN. The progress bar will show RED if the
operation failed or if the user presses the ABORT button.

The 615A Dataloading Software records the status of each file transferred during
the download, and also receives a report from the Target LRU at the end of the
download. To view the downloaded data from the LRU, select the Show Report
button. A window will appear displaying the report data. The user may also view
the data by viewing the 615A Log. (See section 6.0) The downloaded data resides
in the C:\datafiles\Downloads\615A\<date and time stamp>\<filename>. To close
the SSW, select the Close button.

Figure 5-8. Download SSW

80459 Revision N February 13, 2015 Page 13

 615A Dataloader
User Guide

5.6.5 Media Defined Download

Selecting the Media Defined Download button downloads the specified data from
the specified Target LRU’s internal memory. When the Media Defined Download
button is selected and the user has selected the Target to download from, the
SELECT DOWNLOAD window (See Figure 5-9) is shown. In the SELECT
SOURCE MEDIA window, the User then selects the Media source that contains
the definition of the target LRU and the data to be downloaded. In the SELECT
DESTINATION MEDIA window, the User then selects the destination for the
download. The STATUS window displays the files from the media that define the
download from each target.

Figure 5-9. Media Defined Download Selections

After selecting CONTINUE, the available download files from each Target LRU are
listed in the CONFIRM MEDIA DOWNLOAD window. (See Figure 5-10) To
terminate the Download operation, press the Go Back button. Select the
CONTINUE button to begin the download. Note: that Internal MSD cannot be used
as the source for a Media Defined Download.

80459 Revision N February 13, 2015 Page 14

 615A Dataloader
User Guide

Figure 5-10. Confirm Media Download Window

A Media Defined Download SSW will appear. (See Figure 5-11)

Figure 5-11. Media Defined Download SSW

5.6.6 Upload
To upload a 665 LSP to a Target LRU, select the Upload button. Once selected
and the user chooses the Target LRU(s) from the Target List, an Upload
information window will appear. This information window will allow the user to

80459 Revision N February 13, 2015 Page 15

 615A Dataloader
User Guide

select the LSP Source, aircraft model, tail number and software part number of the
665 LSP to be loaded. (See Figure 5-12)

5.6.6.1 Select LSP Source

The user starts by selecting the LSP Source drive.

1. If the user selects INTERNAL MSD, the software will retrieve the 665
LSPs from Loadstar. (See Figure 5-12)

Figure 5-12. Upload From MSD

2. If the user selects SELECT BY ATTRIBUTES, then a pre-set model and

tail number will retrieve the 665 LSPs from Loadstar. (See Figure 5-13)

80459 Revision N February 13, 2015 Page 16

 615A Dataloader
User Guide

Figure 5-13. Upload From Select By Attributes

3. If the user selects REMOVABLE MEDIA, then a list of all removable

media appears. (i.e. A:\ and D:\ etc.). The user then selects the
appropriate media source from the list. (See Figure 5-14)

Figure 5-14. Upload From Removable Media

4. If the user selects SELECTED PATH, then a window will come up. The
user then selects appropriate media source from a list of Part folder .
(See Figure 5-15)

80459 Revision N February 13, 2015 Page 17

 615A Dataloader
User Guide

Figure 5-15. Upload Information Window

5.6.6.2 Select Model and Tail Number

Although the user started the session by entering a tail number, he now has the
opportunity to upload to a different aircraft tail number. By selecting ANY TAIL
from the tail number list, the user may choose a different tail number or aircraft
model number listed. The 615A Dataloading Software obtains the aircraft model
and tail number information from Loadstar. (See section 4.0)

5.6.6.3 Select 665 Parts

The user then selects the 665 LSPs from the Select Parts To Upload list. The
user may select one or more LSPs by left clicking on the part number with the
mouse-pointer. The selected part number will show as highlighted. To deselect
a part number from the list, simply left click again on the highlighted part
number.

5.6.6.4 Verify 665 Parts

The user may verify the integrity of an LSP by selecting the VERIFY button.
The 615A Dataloading Software performs a Cyclical Redundancy Check (CRC)
on the LSP chosen and compares the resulting checksum with the checksum
recorded in the software code.

Once the Verify 665 button has been selected, a Verify SSW will appear. (See
Figure 5-16) This Verify activity SSW displays to the user the Target LRU
Name, the operation selected, the elapsed time, the status of the operation and
a colored progress bar. A GREEN status bar indicates the LSP passed
verification. The status bar will cycle multiple times if multiple software parts are
chosen. The user can then start the upload operation by selecting the Start
Upload button, or cancel by selecting the Close button.

80459 Revision N February 13, 2015 Page 18

 615A Dataloader
User Guide

Figure 5-16. Verify SSW

5.6.6.5 Select Software Load and Start

The Upload information window will list all the 665 LSP(s) assigned to the
aircraft model and tail number chosen by the user. To begin the upload, the
user selects an LSP part then selects the CONTINUE button. A confirmation
window will appear. (See Figure 5-17)

Note: For AirBus secure image, please refer to Appendix B regarding signature
validation.

Figure 5-17. Upload Confirmation Window

In the Confirm Upload window, the user will see:

80459 Revision N February 13, 2015 Page 19

 615A Dataloader
User Guide

 The Model, Tail Number and the source of the software part listed at
the top.
 The left column lists all the software parts chosen by the user to be
uploaded.
 Each subsequent column is assigned to a selected Target LRU.
 If a Target LRU is assigned software parts for upload, the Target LRU
name will appear in BLACK text. If no software parts are assigned to a
Target LRU, then the Target LRU name will appear in RED text. The
User can select GO BACK to return to the previous window to select
only targets that have parts to be loaded.
 Software parts assigned to a Target LRU are indicated by a CHECK
MARK below Target LRU name.
 At the bottom of each Target LRU column is a check box labeled Load
Serial. The user may change the manner in which the 615A Dataloader
uploads the software part to the Target LRU. This is an advanced
feature that allows the loading of parts with duplicate file names to a
single target If this is a required operation. The 615A Dataloading
Software automatically sets this based on the configuration file. To
load the software part serially, i.e. each part is loaded completely
before the next part is loaded, check the Load Serial box. To load the
software parts in parallel, i.e. all parts are offered to the Target LRU
simultaneously; do not check the Load Serial box.

NOTE: The 615A Dataloading Software is automatically configured to upload

the software part in the manner set by the Target LRU. It is not recommended
that the user change this default setting.

To continue with the upload, select CONTINUE UPLOAD. Cancel the Upload
and return to the Upload information window by selecting the GO BACK button.
An Upload SSW will appear in the Operation Menu. (See Figure 5-18)

Figure 5-17. Upload SSW

Once the Upload operation has been completed successfully, the progress bar
on the SSW will show GREEN. The progress bar will show RED if the operation
failed or if the user presses the ABORT button.

80459 Revision N February 13, 2015 Page 20

 615A Dataloader
User Guide

The 615A Dataloading Software records the status of each file transferred
during the Upload, and also receives and records the report from the Target
LRU at the end of the transfer. To view this data from the LRU, select the Show
Report button. A window will appear displaying the report data. The user may
also view the data by viewing the 615A Log. (see section 6.0) To close the
SSW, select the Close button.

5.6.7 Batch Operation

A suite of one or more LSP uploads aimed at multiple Target LRUs on a single
aircraft is called a Batch Upload. A user can initiate a Batch Upload by selecting
the Get Information button on the Operation Menu. This Get Information is
necessary to make sure if the Target LRUs are ready. The status block indicates
the status of the Target LRUs. If the status block shows GREEN, then the Target
LRUs are powered-on and ready to accept a dataload. Select the Go Back button
back to the Operations Menu then select Batch Operation button on the
Operation Menu. Once selected, a Batch Load Information window will appear.
(See Figure 5-19) This Batch Load Information window functions similar to the
Upload Information window. (Refer to section 5.6.6 to 5.6.6.5) Note: Only ONE
Batch Operation part can be selected. Once the user has entered the proper
information and selected a Batch Upload part number, he may start the Batch
Upload by selecting the START button. A Confirm Batch Upload Window will
appear. (See Figure 5-21)

Note: For AirBus secure image, please refer to Appendix B regarding signature
validation.

Figure 5-19. Batch Load Information Window

80459 Revision N February 13, 2015 Page 21

 615A Dataloader
User Guide

5.6.7.1 Confirm Batch Upload

If one or more target LRUs is off-line, or if one or more LSP part numbers are
not present in the LSP source drive (internal MSD or removable media), a
warning message will appear. (See Figure 5-20) Continue by selecting the OK
button.

Figure 5-20. Batch Upload Warning

The Confirm Batch Upload window displays the information entered by the user
plus Batch Load Summary. The Batch Load summary is a listing of the Target
LRUs and the LSP part numbers that will be uploaded during the Batch Upload.
(See Figure 5-21) The Batch Load Summary will also indicate the status of the
Target LRU in parentheses next to the LRU name. To start the Batch Upload,
select the START button. To return to the Batch Load Information window,
select the GO BACK button.

Figure 5-21. Confirm Batch Upload

80459 Revision N February 13, 2015 Page 22

 615A Dataloader
User Guide

5.7 Multiple Operations

The 615A Dataloading Software will support multiple operations running at once but is
limited to 15 operations. As the user continues to start operations, multiple SSWs will
appear in the Operation Menu. (See Figure 5-22)

Figure 5-22. Multiple Operations

If the user attempts to perform an operation on a Target LRU that is busy with another
operation, a SSW will appear but show the operation status as WAITING. (See
Figure 5-23) Once the Target LRU has completed the first operation it will
automatically begin the next operation.

Figure 5-23. Operation Waiting

5.8 Log Window

The Log Window lists all operations, including a time/date stamp, performed by the
user during his dataloading session. This information is also recorded in the 615A log
on the PMAT 2000 hard drive. (See section 6.0)

5.9 Select an Operation

Selecting the GO BACK button will end the dataloading session and exit the program. If
an SSW is still open, a window will appear warning the user that exiting the software
might leave the session in an unstable state and recommends that the user close all
sessions before exiting. (See Figure 5-24)

80459 Revision N February 13, 2015 Page 23

 615A Dataloader
User Guide

Figure 5-24. Go Back Warning Window

5.10 Help
A copy of this User’s Manual is available to the user by selecting the HELP icon at the
top of the screen.

5.11 Battery Charge Status

To assist the user monitor the PMAT 2000 battery charge status, a battery status icon
is provided at the top of the screen. This icon will display the charge level of the on
board batteries in GREEN or display the presence of an external power source. (See
Figure 5-25) The software updates these icons every minute to show any change in
battery status.

Figure 5-25. Battery Status Icons

80459 Revision N February 13, 2015 Page 24

 615A Dataloader
User Guide

6.0 615A LOG

The 615A Dataloading Software records all activity by a user during his dataloading
session as a LOG.txt file in the 615A Log. The software also records the Target LRU
information received during a Get Information operation as an INFO.txt file in the 615A
Log. (See Section 5.6.3) To view this information, follow these steps:

1. From the PMAT 2000 Main Menu, select the ARCHIVE DATA button.
2. From the ARCHIVE DATA window, select the 615A LOGS button. A File
Maintenance window will appear.
3. Highlight a log entry and select the VIEW FILE button. A text screen will appear
displaying the log data.

The date and time of each log entry appears next to the file name. The user can transfer
the log file to a floppy disk, or delete the file by selecting the appropriate button. To exit
the 615A Log and return to the ARCHIVE DATA screen, select the GO BACK button.
(See Figure 6-1)

Figure 6-1. 615A Log

The 615A logs are created in the C:\datafiles\Logs\615A path and can be accessed
using My Computer on the Windows PC. Select the desired log file from the directory,
then press ENTER on the keyboard or double-click to open the file. (See Figure 6-2)

80459 Revision N February 13, 2015 Page 25

 615A Dataloader
User Guide

Figure 6-2. 615A Log Files

80459 Revision N February 13, 2015 Page 26

 615A Dataloader
User Guide

7.0 ARINC 615A CONFIGURATION OPTIONS GUIDE

WARNING – THIS SECTION IS FOR ADVANCED USERS ONLY

7.1 Overview
This section provides details on the ARINC 615A loader options and settings. This
document contains configuration information for 615A version 17.0.

The 615A loader reads configuration information from an XML file located at
C:\datafiles\configuration\615A\NetworkConfiguration.xml. AFDX entries also
contain references to AFDX configuration XML files that are also stored in
C:\datafiles\configuration\615A\

Configuration includes network parameters as well as 615A parameters.

7.2 Network Configuration XML File

This XML document represents a series of entries called network configurations.
Each network configuration is laid out between two XML tags. All network
configurations are presented to the user in the order they are found in this file when
615A starts. The loader will not generate an error if two network configurations have
the same name, but the user may not be able to distinguish between them.

<?xml version=”1.0”?>
<NETCONFIG app=”615Adataloader”>

Multiple Network configurations go here

</NETCONFIG>

There are currently four network configuration types:

 IP – for Ethernet configuration information. Used on both PMAT 2000 and PCs.
Each IP entry is written like this:
<IP NAME=”name” ...>
</IP>
 AFDX – for AFDX configuration information. Used with the GE Fanuc AFDX
CNIC card installed in the PMAT 2000 or PC.
Each AFDX entry is written like this:
<AFDX NAME=”name” ...>
</AFDX>
 BFDX – for BFDX configuration information. Used with the GE Fanuc AFDX
CNIC card installed in a PMAT 2000 or PC.
Each BFDX entry is written like this:
<BFDX NAME=”name” ...>
</BFDX>
 CAN – for CAN bus configuration information. Used with the PMAT 2000 CAN
bus interface.

80459 Revision N February 13, 2015 Page 27

 615A Dataloader
User Guide

<CAN NAME=”name” ...>

</CAN>

7.3 615A Parameters

These parameters modify the behavior of the 615A engine and are not network
specific. For placement of the parameter and applicability see the details on the
individual sections below.

7.3.1 Available 615A Targets

The 615A loader always records a log of its actions in c:\datafiles\logs\615A which
provides general details of 615A operations. The filename reflects a date/time
stamp.

To provide more detailed debugging information the Debugging option must be

enabled. This option:
 Creates a 615A engine trace. This trace records what the 615A loader is
trying to do, its reaction to any packets it receives, any problems it has in
parsing data, etc. This trace is initially dumped to the Event log during
loading and automatically stripped from the event log into a text file when
the 615A loader exits. This file is in addition to the 615A log file created
above.
 Creates a network level trace.
- Using Ethernet this feature automatically sets up a trace using the
ethereal application that records all traffic on the Ethernet interface.
- Using AFDX this feature automatically enables the tracing features
built into the GE Fanuc CFDX library that records all traffic on the
AFDX interface. The trace file is stored at C:\datafiles\logs.
- Using CAN this feature automatically enables the tracing features built
into the PMAT 2000 CAN driver which records all traffic on the CAN
interface. The CAN tracing is always on and ignores the IP_DEBUG
parameter. The trace file is stored at C:\program files\Teledyne
Controls\615A Dataloader.
 This is a required option in all network entries. As a default, it is set to
FALSE.

Exit the 615A loader to stop the tracing and allow the 615A loader to collect the
files. The files will be collected in a subdirectory of c:\datafiles\615A\downloads.

Each time the loader is started with IP_DEBUG=”TRUE” a new subdirectory

corresponding to the name format YYYYTTDDHHMMSSNN will be created where
under the downloads directory:
 YYYY is the year
 TT is the month
 DD is the day

80459 Revision N February 13, 2015 Page 28

 615A Dataloader
User Guide

 HH is the hour in 24 hour format

 MM is the minute
 SS is the start second
 NN is a collision number that is set to 00 and incremented if, for any
reason, that directory name should already exist.

Note: Debugging is enabled from the time the 615A loader is on

the main page until the user exits the 615A loader. Due to the
size of the files that can be generated, TDY recommends enabling
this feature in order to record details of problems and not during
general operation.

Example:
IP_DEBUG=”TRUE”
or
IP_DEBUG=”FALSE”

7.3.2 Server Port Override

This value is expressed in decimal and has a range from 1 to 65535. By default
the Loader’s 615A engine binds to port 59 and responds to requests from that port.
Server port override may be used to cause the 615A loader to bind to another port
number. If specified, the 615A engine will no longer respond to requests on the
default port and will use only the port specified.

Note: This option affects the loader’s behavior for all clients (targets) on the
network.

Example:
SERVER_PORT =”69”

7.3.3 Client Port Override

This value is expressed in decimal and has a range from 1 to 65535. By default
the Loader’s 615A engine attempts to contact the target on port 59. Client Port
Override may be used to cause the 615A loader to contact the target on another
port number. If specified the 615A engine will no longer attempt to connect to the
target on the default port and will only open connections to the port specified.

Note: This option affects the loader’s behavior for all clients (targets) on the
network.

Example:
CLIENT_PORT =”69”

80459 Revision N February 13, 2015 Page 29

 615A Dataloader
User Guide

When specifying both target and client port overrides, the XML should be written
as:

Example:
SERVER_PORT =”69” CLIENT_PORT =”69”

7.3.4 615A-3 Port Option

This value is a Boolean value. This option may be specified as TRUE, FALSE or
the entry may be omitted entirely.

If the Port option is set to TRUE then

 The ARINC 615A Dataloader adds the “PORT N” option in the first
ReadRequest sent to the target in accordance with 615A-3 Note: this
option will be sent regardless of the 615A version used during the
operation.
 The port number “N” is the dataloader server port number. By default the
dataloader server port number is 59. To change the default server port
number, refer to the SERVER PORT Override option defined in this
document.
 The ARINC 615A dataloader expects the target to return the “PORT N”
option in the Option Acknowledge. If the target fails to return the “PORT N”
option or the port number is different from the dataloader server port
number, the 615A Dataloader logs an error message but still attempts to
continue loading. However, most likely the operation will fail.

Note: This option affects the loader’s behavior for all clients (targets) on the
network.

Example:
PORT_OPTION="TRUE"

 Example: To send Port Option: 69 define the following values in the

NetworkConfiguration.xml file

Example:
SERVER_PORT =”69” PORT_OPTION="TRUE"

7.3.5 TFTP Block Size Overrides

By default the 615A dataloader sends the first Read Request at block size 512 and
the minimum and maximum allowed block sizes are 8 and 65429 respectively
when using Ethernet. The maximum block size allowed for AFDX is 8192. This
entry allows the user to specify the starting, maximum, and the minimum
blocksizes for a given network configuration.
 MAX_BLK: This field specifies the maximum blocksize allowed. By default
this value is 65429 bytes for an Ethernet or CAN network. The default
Size is 8192 bytes for an AFDX network. If set to a higher value, the

80459 Revision N February 13, 2015 Page 30

 615A Dataloader
User Guide

loader will convert any target request for a blocksize smaller than this
value to the value specified.
 MIN_BLK: This field specifies the minimum blocksize allowed. By default
this value is 8 bytes. If set to a lower value the loader will convert any
target request for a blocksize larger than this value to the value specified.
 START_BLK: This field specifies the starting blocksize for all TFTP
requests initiated by the loader. When specified the loader will specify this
value as a TFTP option on all requests.
Example:
This example shows the maximum blocksize set to 8100 bytes, the minimum
blocksize set to 8 bytes and a starting blocksize of 228 bytes.

<BLK MAX_BLK="8100" MIN_BLK="8" START_BLK="228"/>

7.3.6 FIND Broadcast

By default the 615A engine broadcasts a FIND request only to the local subnet as
defined by the network setup parameters. This entry causes the 615A engine to
also send a request to the given IP address.
 ADDR may be an IP address such as 10.1.44.1 or a broadcast address
such as 255.255.255.255.
 BCAST controls whether the IP broadcast flag is set and may be either
TRUE or FALSE.
 Zero or more FIND entries may be included.

Example:
<FIND ADDR="10.1.44.1" BCAST="FALSE"/>
<FIND ADDR="255.255.0.0" BCAST="TRUE"/>

7.3.7 Target Definitions

By default the 615A engine only displays targets which respond to a FIND
broadcast. This entry causes the 615A engine to display the listed target whether
that target supports the FIND response or not. These fields correspond to a FIND
response.
 TARGET ID (Target Hardware Identifier) is a string of up to 15 characters
corresponding to the first field in the FIND response.
 TYPE (Target Hardware Type Name) is a string of up to 8 characters
corresponding to the second field in the FIND response.
 POSITION (Target Hardware Position) is a string of up to 8 characters
corresponding to the third field in the FIND response.
 NAME (Literal Name) is a string of up to 20 characters corresponding to
the fourth field in the FIND response.
 MANUFACTURER (Manufacturer Code) is a string of 3 characters
corresponding to the fifth field in the FIND response.
 Zero or more Target Definition entries may be included.

80459 Revision N February 13, 2015 Page 31

 615A Dataloader
User Guide

Example:
<TARGET ID= "0200" TYPE="ABC" POSITION="L" NAME="EFB"
MANUFACTURER="DEM" IP="10.0.0.70"/>

7.4 Ethernet Network Configuration

On the PMAT 2000, the ARINC 615A software will only load through the circular
connector (J1), and overrides routing rules and binds all sockets to the J1 Ethernet
interface. This behavior cannot be modified.

On a desktop or laptop PC, the loader is able to operate over multiple Ethernet
networks, binding its sockets to the selected Ethernet interface to perform loading of
an LRU. The loader will restore the original Ethernet settings of the selected loader
interface after the loader exits.

7.4.1 Ethernet Specific Parameters

7.4.1.1 Network Interface Parameters

These network interface parameters are applied to the circular connector on a
PMAT 2000 or the selected Ethernet adapter on a workstation when the 615A
application starts. The original network parameters will be restored when 615A
exits.
 ADDR is either:
- “xxx.xxx.xxx.xxx”to set the IP address of the loader. It is
expressed in IP dotted notation.
- “DHCP” to indicate that the loader should force a DHCP request and
obtain a network address from a DHCP server.
- “”, i.e. blank, to indicate that the 615A loader should use the existing
network settings and not modify the IP address of the loader.
 MASK is the IP netmask of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”. Leave this value blank if specifying DHCP or
when using the existing settings.
 GATEWAY is the IP gateway of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”. When in doubt, or if no Gateway is available,
set this to the address of a target on the network or to any other
address valid based on the netmask. Leave this value blank when
specifying DHCP or when using the existing settings.
 NIC_SPEED sets the desired the speed of the Ethernet that is on the
circular 53-pin connector of the PMAT 2000. The possible values are:
AUTO, 10HALF, 10FULL, 100HALF, 100FULL. The number 10 or 100
indicates the speed of the Ethernet link in megabits per second. HALF
or FULL indicates the duplex capabilities of the channel. This option
should only be used if a target that is to be loaded cannot auto-
negotiate the Ethernet speed with the PMAT 2000 when connected. It
is not supported on standard PCs.

80459 Revision N February 13, 2015 Page 32

 615A Dataloader
User Guide

7.4.1.2 ARP Override

By default the 615A engine uses ARP to match the IP address given to the
MAC address needed to send a packet to a particular target. For targets that
do not support ARP this information may be defined.
 ARP_IP is the IP address of the target in IP dotted notation:
“xxx.xxx.xxx.xxx”. It must match the IP address of the target’s IP
address returned by the FIND packet or FIND Override.
 ARP_MAC is the MAC address of the target expressed as six
hexadecimal octets: “xx-xx-xx-xx-xx-xx”. It must match the MAC
address of the target exactly.
 Zero or more ARP Override entries may be included.

Example:
<ARP ARP_IP= "10.129.0.11" ARP_MAC="02-00-01-6b-00-01"/>

7.4.2 Ethernet Configurations

7.4.2.1 Simple Configuration for PMAT 2000

The simplest entry for Ethernet configurations is one that does not modify the
network settings. This entry will cause the 615A loader to not modify the
network settings from what they currently are:
 NAME is the name of the network configuration. The name does not
need to be USE EXISTING. 615A notes the network parameters are
blank and does not affect the network settings.
 IP_DEBUG enables or disables the debugging option.

Example:
<IP NAME="USE EXISTING" ADDR="" MASK="" GATEWAY=""
IP_DEBUG="FALSE"/>

7.4.2.2 Simple Configuration for PC

The simplest entry for Ethernet configurations is one that does not modify the
network settings. This entry will cause the 615A loader to not modify the
network settings from what they currently are:
 NAME is the name of the network configuration. The name does not
need to be USE EXISTING. 615A notes the network parameters are
blank and does not affect the network settings.
 ADDR and MASK are set to blank to confirm that the 615A loader
should not attempt to modify these settings.
 MAC is the MAC address of the loader station’s Ethernet interface to use
expressed as six hexadecimal octets: “xx-xx-xx-xx-xx-xx”. It must
match the MAC address of one of the local network adapters exactly.
 IP_DEBUG enables or disables the debugging option.

80459 Revision N February 13, 2015 Page 33

 615A Dataloader
User Guide

Example:
<IP NAME="SIMPLE" ADDR="" MASK="" MAC="01-02-03-04-05-06"
IP_DEBUG="FALSE"/>

7.4.2.3 Standard Entry Setting a Static Address

This entry sets the Ethernet network to the settings indicated:
 NAME is the name of the network configuration.
 ADDR is the IP address of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”.
 MASK is the IP netmask of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”.
 GATEWAY is the IP gateway of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”. When in doubt, or if no Gateway is available,
set this to the address of a target on the network or to any other
address valid based on the netmask.
 IP_DEBUG enables or disables the debugging option.

Example:
<IP NAME="ELECTRONIC FLIGHT BAG (EFB)" ADDR="192.168.1.2"
MASK="255.255.255.0" GATEWAY="192.168.1.1"/
IP_DEBUG=”FALSE”>

7.4.2.4 Standard Entry Requesting a DHCP Assigned Address

This entry sets the Ethernet network to the settings indicated:
 NAME is the name of the network configuration. The name does not
need to be DHCP.
 ADDR is the string “DHCP” which indicates to the 615A loader to
obtain an IP address from a DHCP server on the network.
 IP_DEBUG enables or disables the debugging option.

Example:
<IP NAME="DHCP" ADDR="DHCP" IP_DEBUG="FALSE"/>

7.4.2.5 Entry with Overrides for PMAT 2000

This entry shows how a more complex set of address parameters are laid out.
 NAME is the name of the network configuration. The name does not
need to be DHCP.
 ADDR is the IP address of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”.
 MASK is the IP netmask of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”.
 GATEWAY is the IP gateway of the loader in IP dotted notation:
“xxx.xxx.xxx.xxx”. When in doubt, or if no Gateway is available,
set this to the address of a target on the network or to any other
address valid based on the netmask.

80459 Revision N February 13, 2015 Page 34

 615A Dataloader
User Guide

 NIC_SPEED is the desired speed of the Ethernet on the PMAT 2000

53-pin circular connector. The possible values are: AUTO, 10HALF,
10FULL, 100HALF, 100FULL. The number 10 or 100 indicates the
speed of the Ethernet link in megabits per second. HALF or FULL
indicates the duplex capabilities of the channel. This option should
only be used if a target that is to be loaded cannot auto-negotiate the
Ethernet speed with the PMAT 2000 when connected. It is not
supported on standard PCs.
 PORT is the SERVER port and CLIENT port overrides.
 TARGET is the target FIND response override
 ARP is the ARP override.
 IP_DEBUG enables or disables the debugging option.

Example:
<IP NAME="ATSU" ADDR="10.129.0.50" MASK="255.240.0.0"
GATEWAY="10.129.0.12" IP_DEBUG=”FALSE” NIC_SPEED=”10FULL”>
<PORT SERVER_PORT= "69" CLIENT_PORT = "69"/>
<TARGET ID= "0200" TYPE="UPLD" POSITION="1" NAME="ATSU"
MANUFACTURER="" IP="10.129.0.10"/>
<ARP ARP_IP= "10.129.0.10" ARP_MAC="02-00-02-00-00-01"/>
</ IP>

7.4.2.6 Entry with Overrides for PC

This entry shows how a more complex set of address parameters are laid out.
 NAME is the name of the network configuration. The name does not
need to be DHCP.
 ADDR and MASK are set to blank to confirm that the 615A loader
should not attempt to modify these settings.
 MAC is the MAC address of the loader station’s Ethernet interface to
use expressed as six hexadecimal octets: “xx-xx-xx-xx-xx-xx”. It
must match the MAC address of one of the local network adapters
exactly.
 PORT is the SERVER port and CLIENT port overrides.
 TARGET is the target FIND response override
 ARP is the ARP override.
 IP_DEBUG enables or disables the debugging option.

Example:
<IP NAME="ADVANCED" ADDR="" MASK="" MAC="01-02-03-04-05-06"
IP_DEBUG="FALSE"/>
<PORT SERVER_PORT= "69" CLIENT_PORT = "69"/>
<TARGET ID= "0200" TYPE="UPLD" POSITION="1" NAME="ATSU"
MANUFACTURER="" IP="10.129.0.10"/>
<ARP ARP_IP= "10.129.0.10" ARP_MAC="02-00-02-00-00-01"/>
</IP>

80459 Revision N February 13, 2015 Page 35

 615A Dataloader
User Guide

7.5 AFDX Network Configuration

This section describes how to generate the two configuration files required by the
ARINC 615A Dataloader application to load a target using the AFDX protocol.

Reference Documents:
CFDX Users Manual, Document Number 1500-053. This is the GE v1.2 document.
BFDX Users Manual, Document Number 1500-073. This is the GE v3.1 document.

7.5.1 Overview of AFDX dataloading

The ARINC 615A software will only load via the AFDX protocol using a GE Fanuc AFDX
CNIC card. A full description of the AFDX parameters is provided in the GE Fanuc AFDX
User’s Guide. The GE card comes with its own driver software that must be installed using
the GE-provided installer. The 615A Dataloader supports two versions of the GE driver
software: v1.2 and v3.1. The configuration files for the two versions are different, so
therefore the two versions are described separately in this document.

The ARINC 615A Dataloader requires two configuration files to load a target using the
AFDX protocol. Both files are text files and can be edited with any text editor, such as
notepad.

AFDX Network Configuration file --- The AFDX Configuration file describes the
Network setup (IP address, VLINK, Tx/Rx port number) for a specific target.
This file is used to initialize the GE Fanuc AFDX CNIC card. The file is in XML format as
described by the GE Fanuc AFDX Users Guide and takes a .xml extension.
The file name of this file can be anything you decide, and that name should appear in the
NetworkConfiguration.xml file. The Dataloader passes this file name to the GE AFDX
driver, and that driver then reads the file to configure the AFDX end system. This file
contains a reference to the .dtd schema file for the XML. The DTD file is not used in
dataloading, but is used by XML editors and viewers, and therefore the DTD file always
goes along with the xml file. The v1.2 DTD file is of course different from the v3.1 DTD
file.

NetworkConfiguration.xml file -- This file is the configuration file used by the 615A
Dataloader application. When the 615A Dataloader application is launched it parses this
file to get a list of available network setups. For more information on how the
NetworkConfiguration.xml file is defined see previous sections of this document. The
keyword AFDX in this file is used to create an AFDX setup. When an AFDX configuration
is chosen for dataloading, the dataloader looks for the v3.1 driver (i.e. the latest). If it finds
that driver, it uses it. If it does not find the v3.1 driver, it looks for the v1.2 driver. The
reason it does this is that the calls to the v1.2 and v3.1 drivers are different.

80459 Revision N February 13, 2015 Page 36

 615A Dataloader
User Guide

About IP Addresses. Target and loader IP addresses in AFDX are defined as follows. In
AFDX systems, the first byte in an IP address is always 10. Thus, the AFDX IP address is
always 10.x.x.x. In all AFDX systems the IP address is a combination of the Network ID,
Equipment ID and the Partition ID, as follows:

10.NetworkID.EquipmentID.PartitionID

For example, if NetworkID = 46, Equipment ID= 12, PartitionID=0 then the IP address
is 10.46.12.0

About SAP ports. Dataloading uses SAP ports exclusively. In the AFDX xml file, when
you define a TX port, and it is a SAP port (and for dataloading, they are all SAP ports)
you do not have to specify a destination port. You specify the source port (i.e. the port on
the loader that is the source port for the packet being transmitted to the target). The
whole idea of a SAP port is that the dataloader can decide the destination port
dynamically, on the fly, right at the time of sending the packet. Later you will see the
differences between v1.2 and v3.1 on this topic.

7.5.2 The Network configuration file

This section describes the NetworkConfiguration.xml file of the dataloader. This file did
not change format. Here is an example networkconfiguration.xml file. It is the same
example as given for the v3.1 CNIC example below in section 7.5.4.

<?xml version="1.0"?>
<NETCONFIG app="615ADataloader">
<AFDX NAME="AFDX_CACP" CONFIG="CACP_T.xml" IP_DEBUG="FALSE"
LOADER_IP_ADDR="10.2.33.0">
<TARGET IP="10.23.1.0" TX_FIND_PORT="101" RX_FIND_PORT="202"
RX_TFTP_PORT="201" FIND_ADDR="10.23.1.0">
<LOADER_PORT TX_PORT="102" RX_PORT="203"/>
<LOADER_PORT TX_PORT="103" RX_PORT="204"/>
</TARGET>
<BLK MAX_BLK="8192" MIN_BLK="8" START_BLK="1024" />
</AFDX>
</NETCONFIG>

NAME: this field defines the name that the 615A Dataloader application displays in the
“Network Connections” list.

CONFIG: is the name of the AFDX network configuration file.

TARGET: This whole section defines the parameters of the target --- the IP address, FIND, and
TFTP port ID numbers as defined in the AFDX configuration file.

IP: This is the target IP address.

80459 Revision N February 13, 2015 Page 37

 615A Dataloader
User Guide

RX_TFTP_PORT: The “Port ID” number corresponding to the Receive TFTP port number in
the AFDX configuration file. This is the receive port on the loader side for the loader’s TFTP
server. This is the Well known port (WKP) for TFTP, which is almost always port 59. In other
words, this is the port that will be the destination port for a RRQ or WRQ coming from the target
to the loader.

TX_FIND_PORT: The “Port ID” number corresponding to the transmit FIND port number in
the AFDX configuration file. This is the port used for transmitting the FIND query from the
loader to the target. If you remember from the overview section, the destination port of a TX port
in v3.1 is not really used. This TX FIND port is really the source port of a TX port definition. In
other words, it is the source port of a FIND IRQ (query packet) that is sent from the loader to the
target. It is always port 1001.

RX_FIND_PORT: The “Port ID” number corresponding to the receive FIND port number in
the AFDX configuration file. This is the destination port of a FIND IAN (answer packet) that is
sent from the target to loader. This is always port 1001. When we do FIND, the source port and
destination port are both always 1001, and this is true for IRQ packets that the loader sends to the
target, and it is true for the IAN packets that the target sends to the loader.

FIND_ADDR: This is the target IP address for performing the FIND operation. This is mostly
used in the case when the target has a MultiCast FIND IP address. In Ethernet dataloading, most
targets use the the same IP address for FIND and for TFTP, however in AFDX this is not always
true. There are many examples of LRUs that have a different IP address for FIND when AFDX
is used.

LOADER_PORT: defines the dataloading “Port ID” numbers for the transmit (TX_PORT) and
the receive port (RX_PORT) pairs as defined in the AFDX Configuration file. This declaration
defines pairs, and is essentially binding a RX port to a TX port. This makes AFDX look a little
more like an Ethernet socket. In Ethernet socket IO, the dataloader receives on a socket and then
transmits on the socket. In AFDX, there are no sockets, and so this declaration lets you associate
the TX and RX ports as a pair that are almost like a socket. These two ports that you bind
together have the same port number. This makes sense because one of the most common things
that happens in TFTP is that when the loader receives a packet on a local port (i.e. the destination
port of a packet from the target to the loader), the loader then turns it around and sends back
some kind of response to the target with that same port, now as the source. This is the basic idea
of the back and forth motion of packets in TFTP. The big exception to this rule of course is the
WKP, the server port, port 59. The WKP is the crux of TFTP, the port hop, where the server
hops from the WKP to an ephemeral port to start this back and forth flow. Thus, in conclusion,
this section describes the association of RX and TX ports during the back and forth flow of
packets in TFTP.

7.5.3 CFDX configuration file for GE driver V1.2

Below is an example configuration file for this driver.

80459 Revision N February 13, 2015 Page 38

 615A Dataloader
User Guide

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE AFDXConfig SYSTEM "AFDXDTD.dtd">
<AFDXConfig Name="SAP Port Configuration">
<EndSystem Name="Loader" EndSystemUniqueID="545" NetworkID="2"
EquipmentID="33" EndSystemGroupID="0">
<Partition Name="Partition 1" PartitionID="1" />
</EndSystem>
<EndSystem Name="ACP" EndSystemUniqueID="5889" NetworkID="23"
EquipmentID="1" EndSystemGroupID="1">
<Partition Name="Partition 1" PartitionID="0" />
</EndSystem>

<VirtualLink Name="Loader_ACP" VirtualLinkID="2085" NumSubVL="1"

BAG="128" Lmax="1500" IntegrityCheck="ACTIVE"
RedundancyManagement="ACTIVE" NetworkSelector="BOTH" SkewMax="256">
<SrcEndSystem EndSystemUniqueID="545" />
<DstEndSystem EndSystemUniqueID="5889" />
<SAP QueueSize="20" DontFragment="FALSE">
<TxPort Name="FIND Response" PortID="FIND 1" PortUniqueID="101"
PartitionID="1" UDPPortNumber="1001" SubVL="1"/>
</SAP>
<SAP QueueSize="20" DontFragment="FALSE">
<TxPort Name="Channel 21" PortID="Channel 21" PortUniqueID="102"
PartitionID="1" UDPPortNumber="63198" SubVL="1"/>
</SAP>
<SAP QueueSize="20" DontFragment="FALSE">
<TxPort Name="Channel 22" PortID="Channel 22" PortUniqueID="103"
PartitionID="1" UDPPortNumber="63199" SubVL="1"/>
</SAP>
</VirtualLink>

<VirtualLink Name="ACP_Loader" VirtualLinkID="1317" NumSubVL="1"

BAG="128" Lmax="1500" IntegrityCheck="ACTIVE"
RedundancyManagement="ACTIVE" NetworkSelector="BOTH" SkewMax="256">
<SrcEndSystem EndSystemUniqueID="5889" />
<DstEndSystem EndSystemUniqueID="545" />
<SAP QueueSize="20" DontFragment="FALSE">
<RxPort Name="TFTP Service" PortID="TFTP 1" PortUniqueID="201"
EndSystemUniqueID="545" PartitionID="1" UDPPortNumber="59"/>
</SAP>
<SAP QueueSize="20" DontFragment="FALSE">
<RxPort Name="FIND Response" PortID="FIND 1" PortUniqueID="202"
EndSystemUniqueID="545" PartitionID="1" UDPPortNumber="1001"/>
</SAP>
<SAP QueueSize="20" DontFragment="FALSE">

80459 Revision N February 13, 2015 Page 39

 615A Dataloader
User Guide

<RxPort Name="Channel 21" PortID="Channel 21" PortUniqueID="203"

EndSystemUniqueID="545" PartitionID="1" UDPPortNumber="63198"/>
</SAP>
<SAP QueueSize="20" DontFragment="FALSE">
<RxPort Name="Channel 22" PortID="Channel 22" PortUniqueID="204"
EndSystemUniqueID="545" PartitionID="1" UDPPortNumber="63199"/>
</SAP>
</VirtualLink>
</AFDXConfig>

EndSystem – Note that both the loader and target end system are declared here. But this
file is really for the loader, and the loader has one end system. Thus, the definition of the
target end system is just a dummy that allows you to specify the source and destination of
the virtual links. Notice that the virtual links are not specified as RX or TX links, and so
this file uses the source and destination end systems to determine if the VL is RX or TX.

Loader IP Address – This is the IP address of the Dataloader and is required to

communicate with the target being loaded.

Target IP Address - This is the target IP address.

End System Unique ID -- This is a Unique ID defined to specify a loader or a target in the
given network. It is calculated by combining the NetworkID and the EquipmentID as
follows: EndSystemUniqueID = EquipmentID + NetworkID*256

UDP Port Number – In all cases, this is the port on the local machine. Remember the
discussion in the overview about SAP ports. For the TX ports, this represents the source
port on the loader that the transmission is coming from. The reason is that it is a SAP port –
the loader will provide the destination port on the fly later. For RX ports, this is the
destination port, i.e. it is the port on the loader side that is the destination of a packet that is
received. This XML format has a section for declaring SAP ports separately from the non-
SAP ports, and so there is no mention of a destination port here – not needed.

Virtual Link ID – This has to correspond to a VL of the target. Both the loader and the
target have an XML AFDX definition file, and both have an RX VL and a TX VL. Thus,
the RX VL of the loader is the TX VL of the target, and vice versa. This virtual link ID is
actually communicated between the two machines. This is how the machines address each
other – they communicate via ports on the VL.

The corresponding NetworkConfiguration.xml file is:

<?xml version="1.0"?>
<NETCONFIG app="615ADataloader">
<AFDX NAME="AFDX_CACP" CONFIG="CACP_T.xml" IP_DEBUG="FALSE"
LOADER_IP_ADDR="10.2.33.1">

80459 Revision N February 13, 2015 Page 40

 615A Dataloader
User Guide

<TARGET IP="10.23.1.0" TX_FIND_PORT="101" RX_FIND_PORT="202"

RX_TFTP_PORT="201" FIND_ADDR="10.23.1.0">
<LOADER_PORT TX_PORT="102" RX_PORT="203"/>
<LOADER_PORT TX_PORT="103" RX_PORT="204"/>
</TARGET>
<BLK MAX_BLK="8192" MIN_BLK="8" START_BLK="512" />
</AFDX>
</NETCONFIG>

7.5.4 BFDX configuration for GE driver V3.1

There are big differences between the GE v1.2 XML format and the GE v3.1 XML format.

Here is an example v3.1 AFDX configuration file. The file is named CACP_T.xml.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE AFDX_Configuration SYSTEM "AFDX-A.dtd">
<AFDX_Configuration Name="SAP Port Configuration">
<End_System Name="Loader" Network_ID="2"
Equipment_ID="33" End_System_Group_ID="0" Link_Speed="MBPS_100">
<Tx_Virtual_Link Name="Loader_to_ACP" Virtual_Link_ID="2085"
Bag="1000" Max_Frame_Size="1500" Skew_Delay_Max="400"
Physical_Interface="BOTH">
<SubVL>
<Tx_Port Queue_Depth="20" Fragmentation_Enabled="YES"
IP_Destination_Address_Format="UNICAST"
Access_Type="SAP"
Name="FIND Response" Port_ID="101" Destination_Port="1001"
Periodic="NO" Phase="0" Period="0" Payload_Size="0"
Source_Partition="1" Source_Port="1001" />
<Tx_Port Queue_Depth="20" Fragmentation_Enabled="YES"
IP_Destination_Address_Format="UNICAST"
Access_Type="SAP"
Name="Channel 21" Port_ID="102" Destination_Port="63198"
Periodic="NO" Phase="0" Period="0" Payload_Size="0"
Source_Partition="1" Source_Port="53198" />
<Tx_Port Queue_Depth="20" Fragmentation_Enabled="YES"
IP_Destination_Address_Format="UNICAST"
Access_Type="SAP"
Name="Channel 22" Port_ID="103" Destination_Port="63199"
Periodic="NO" Phase="0" Period="0" Payload_Size="0"
Source_Partition="1" Source_Port="53199" />
</SubVL>
</Tx_Virtual_Link>
<Rx_Virtual_Link Name="ACP_to_Loader" Virtual_Link_ID="1317"
MTU="1500" IC_Enabled="YES" RM_Enabled="YES"

80459 Revision N February 13, 2015 Page 41

 615A Dataloader
User Guide

Interface_A_Enable="YES" Interface_B_Enable="YES"
Skew_Max="400" Prev_Seq_Number_Range="20"
Rx_VL_ICMP_Enabled="NO">
<Rx_Port Queue_Depth="20" Sampling_or_Queuing="QUEUING"
Name="TFTP Service" Port_ID="201"
Destination_Partition="1" Destination_UDP_Port_Number="59"/>
<Rx_Port Queue_Depth="20" Sampling_or_Queuing="QUEUING"
Name="FIND Response" Port_ID="202"
Destination_Partition="1" Destination_UDP_Port_Number="1001"/>
<Rx_Port Queue_Depth="20" Sampling_or_Queuing="QUEUING"
Name="Channel 21" Port_ID="203"
Destination_Partition="1" Destination_UDP_Port_Number="53198"/>
<Rx_Port Queue_Depth="20" Sampling_or_Queuing="QUEUING"
Name="Channel 22" Port_ID="204"
Destination_Partition="1" Destination_UDP_Port_Number="53199"/>
</Rx_Virtual_Link>
<ICMP/>
</End_System>
</AFDX_Configuration>

Here are some notes about the fields in this file.

End_System – In this format, only the end system of the loader is declared. The target end
system is never mentioned. The reason is that this format has changed and now there are
separate declarations for the RX VL and the TX VL. There are no end system unique IDs.

Destination_Port – Note that the destination port of the TX port declaration is not used.
The new format has one port declaration format that is used for both SAP and non-SAP
ports. There is an Access_Type tag to indicate that the port is SAP. As mentioned earlier in
the overview, a destination port makes no sense for a SAP port because the loader sets the
destination port on the fly. Thus, this field is required by the XML parser, but it is not used
at all by the end system, because it is a SAP port. You can put anything in this field and it
will be totally ignored.

The corresponding NetworkConfiguration.xml file is:

<?xml version="1.0"?>
<NETCONFIG app="615ADataloader">
<AFDX NAME="AFDX_CACP" CONFIG="CACP_T.xml" IP_DEBUG="FALSE"
LOADER_IP_ADDR="10.2.33.0">
<TARGET IP="10.23.1.0" TX_FIND_PORT="101" RX_FIND_PORT="202"
RX_TFTP_PORT="201" FIND_ADDR="10.23.1.0">
<LOADER_PORT TX_PORT="102" RX_PORT="203"/>
<LOADER_PORT TX_PORT="103" RX_PORT="204"/>
</TARGET>

80459 Revision N February 13, 2015 Page 42

 615A Dataloader
User Guide

<BLK MAX_BLK="8192" MIN_BLK="8" START_BLK="1024" />

</AFDX>
</NETCONFIG>

7.6 CAN Network Configuration

The network configuration entry “CAN” is dedicated to the use of 615A ported onto the
physical CAN bus using the communication protocol identified for use on the Boeing
787 aircraft as identified in the Boeing documents D616Z001-02 and D617Z001-01.

CAN loading is currently available only on a PMAT 2000. The PMAT 2000 provides one
physical CAN interface located within the PMAT 2000’s circular connector J1.

Note: The ARINC 615A software will only load through the circular connector
(J1). This behavior cannot be modified.

7.6.1 CAN Specific Parameters

The following parameters are setting unique to the use of the CAN protocol as
defined for use on the 787 aircraft.

 CAN entry option:

 BAUD_RATE: CAN bus speed expressed in Hertz. There are four valid
quantized entry values: {125000, 250000, 500000, and 1000000}. The
default value is 500000. The specification of an invalid entry will result in
use of the default value. The setting of this value is dependent on the
communication speed that the target supports.
 PROMISCUOUS: Setting this flag allows the loader to operate, monitor
and receive all messages on the CAN Bus. PROMISCUOUS:
TRUE|FALSE, when set to TRUE; the loader will not filter out CAN traffic
based on CAN ID. This setting is used for debugging and test purposes
only and should not be set for normal operation.
 ACCEPTANCE_MASK: Loader CAN mask value: 29 bit Hex value that
indicates the relevant portions of the bits in the received messages. In the
787, the CAN bus extended message identifier (29 bits) is utilized. Some
of the lower order bits are used to identify fragment information while the
upper bits are the true message identifier (see below). The default mask
is 0x1FFFFC00 or (536869888 in decimal). This value is required to
support communication with target identified for use on the 787 aircraft
and this value should normally not be changed.
 LOADER_IP_ADDR: The value used as the Loader’s IP address for use in
the CAN loading protocol on the 787 aircraft. The IP address is used by
the communication protocol above the CAN layers. This IP address is
assigned by the aircraft integrator or target manufacturer. This IP address

80459 Revision N February 13, 2015 Page 43

 615A Dataloader
User Guide

may or may not be the same IP address used in the loader for Ethernet
communication.
 GATEWAY_BIT: The Gateway bit in the CAN Address is configurable in
the 615A Dataloader. Depending on the target requirements the 615A
Dataloader can set the CAN Gateway bit to 1 or 0. If no value is specified
the 615A Dataloader defaults the gateway value to 1.
 TARGET Entry Options
 TARGET: BLOCKTRANSFER_ID is a 10 bit value used in the 787 CAN
communication protocol to identify the communication message. This is
assigned by the target manufacturer. The BLOCKTRANSFER_ID is used
as follows to create the physical 29 bit extended format CAN message
identifier:
o Gateway: 1 Bit -MSB –Defined in this Network Configuration File
o GroupID Base: 3 Bits -Fixed in the 787 CAN protocol as 111 (binary)
o GroupID Offset: 5 bits - Fixed in the 787 CAN protocol as 00001 (binary)
o Block Transfer ID: 10 Bits -Must be specified for the unique target being loaded
o Source : 1 Bit -0 indicates a message from the loader, 1 indicates
o -a message from the target.

7.6.2 CAN Network Configuration Files

7.6.2.1 Sample NetworkConfiguration.XML file for CAN

Below is an example of the contents of the NetworkConfiguration.xml file used

for CAN loading:

Example:

<?xml version="1.0" ?>

<NETCONFIG app="615ADataloader">

<CAN NAME="Lo-Fwd"
LOADER_IP_ADDR="192.1.1.1"
IP_DEBUG="FALSE"
BAUD_RATE="250000"
ACCEPTANCE_MASK="536869888"
GATEWAY_BIT="0">

<TARGET ID="Target 1"

TYPE="OPS"
NAME="Lo-Fwd"
POSITION="LOF"
MANUFACTURER="Sample"
IP="192.1.1.2"
BLOCKTRANSFER_ID="56"
RX_TFTP_PORT="59"
DEFAULT_615A_TIMEOUT="12000"

80459 Revision N February 13, 2015 Page 44

 615A Dataloader
User Guide

TFTP_TIMEOUT="2000">
<LOADER_PORT TX_PORT="1000" RX_PORT="1000" />
<LOADER_PORT TX_PORT="2000" RX_PORT="2000" />
</TARGET>

<TARGET ID="Target 2"

TYPE="OPS"
NAME="Ro-Fwd"
POSITION="ROF"
MANUFACTURER="Sample"
IP="192.1.1.2"
BLOCKTRANSFER_ID="56"
RX_TFTP_PORT="59"
DEFAULT_615A_TIMEOUT="12000"
TFTP_TIMEOUT="2000">
<LOADER_PORT TX_PORT="1000" RX_PORT="1000" />
<LOADER_PORT TX_PORT="2000" RX_PORT="2000" />
</TARGET>

</CAN>

</NETCONFIG>

7.6.2.2 CAN Entry Definitions

 <NETCONFIG app=”615ADataloader”> This is the header to the XML

file and this is the name that the user would select for the loader to
use as the network configuration (see section 5.4 of this document)
 <CAN NAME="Lo-Fwd" This is the display name for the CAN
Target selection in 615A
 LOADER_IP_ADDR="192.1.1.1" This is the IP Address of the PMAT
2000 Loader – This value is used to tell the LRU where to send its
packets in the communication protocol (this is different than the
physical address of the CAN interface).
 IP_DEBUG="FALSE" Enables (=TRUE) or disables (=FALSE) the
debugging option for 615A
 BAUD_RATE="250000" CAN Bus speed in HZ, 250000 = 250Khz
 ACCEPTANCE_MASK="536869888" CAN packet address mask.
The default value is 536869888 in decimal notation. (This
correlates to the default setting of 0x1FFFC00, however the system
requires the input as a decimal string. This value should not be
changed.)
 GATEWAY_BIT="0" Bit is based on the requirements of the target
 <TARGET …> </TARGET> Target information which overrides the
need for a “FIND” operation in 615A.

80459 Revision N February 13, 2015 Page 45

 615A Dataloader
User Guide

 ID=" Target 1" This value should be the same as the LRU name.
 IP="192.1.1.2" This value is the CAN Target IP address.
 RX_PORT="1000" This is the Port the PMAT will receive data.
 TX_PORT="1000" This is the Port the PMAT will transmit from.
 BLOCKTRANSFER_ID="56" Target’s Block Transfer ID. This value
provides the unique message identification. The value is in decimal.

Fill in the appropriate values for each piece of information in this section.
NOTE: The target ID MUST match the target LRU.

7.7 BFDX Network Configuration

The BFDX network configuration is a Boeing proprietary version of the AFDX protocol.
It is currently used on the 787 airplane.

The BFDX configuration entries are similar to the AFDX entries. The XML
configuration files for BFDX and AFDX networks are not interchangeable and follow
different DTDs. See the GE FANUC documentation on the BFDX configuration files
for more details on how to create a BFDX configuration file.

Contact Teledyne Controls Customer Support (www.teledyne-controls.com) for help

creating BFDX configuration files.

80459 Revision N February 13, 2015 Page 46

 615A Dataloader
User Guide

8.0 GLOSSARY

AFDX Avionics Full Duplex Switch Ethernet

BFDX Boeing Version of AFDX Protocol
CFDX GE FANUC Software Library for the CNIC Card
CD Compact Disk
CNIC GE FANUC Network Interface Card
CRC Cyclical Redundancy Check
DHCP Dynamic Host Configuration Protocol
DMC Digital Mapping Computer
EFB Electronic Flight Bag
FMC Flight Management Computer
IP Internet Protocol
LAN Local Area Network
LRU Line Replaceable Unit
LSP Loadable Software Part
PMAT Portable Maintenance Access Terminal
P/N Part Number
RAM Random Access Memory
SSW Session Status Window
TDY Teledyne Controls

80459 Revision N February 13, 2015 Page 47

 615A Dataloader
User Guide

Appendix A

Special cables are required to load the Boeing EFB using the 615A Dataloader
application. The cables listed below are manufactured and available from TDY:

Loading Boeing EFB via Windows Laptop Cable P/N 80088-1

Loading Boeing EFB via PMAT 2000 Cable P/N 80072-4

80459 Revision N February 13, 2015 Page 48

 615A Dataloader
User Guide

Appendix B

The Upload or Batch part number(s) will be validated with AirBus secure image. This signature
validation is to confirm the Batch or Upload part number(s) is accurate and correct. If the
signature is not present, the Signature Status will show No Signature Present in the Status screen
and the results will also be showed below the Status screen. Select Cancel to go back previous
step Upload Confirmation Window section 5.6.6 or Batch Load Information Window section
5.6.7.

Figure 6-3. No Signature Present

If the signature is not correct, the Signature Staus will show in the Stauts screen and the results
will not be valid. (See Figure 6-4) Select Cancel to go back the previous step, follow Upload
Confirmation Window section 5.6.6 or Batch Load Information Window section 5.6.7. to select
the correct software part number.

80459 Revision N February 13, 2015 Page 49

 615A Dataloader
User Guide

Figure 6-4. Signature Not Valid

If the Upload or Batch part number(s) is valid, the Signature Status will show present and the
result will be valid. Select OK to continue and follow previous section 5.6.6 or section 5.6.7

Figure 6-5. Signature Valid

80459 Revision N February 13, 2015 Page 50