A664-FTSIU Users Manual Rev C
A664-FTSIU ARINC 664 / AFDX Flight Test & Simulator Interface Unit
Users Manual REV C March 23, 2012
For further information or questions contact:
Innovative Control Systems, Inc. 10801 N. 24th Ave Suite 103 Phoenix, Arizona 85029 U.S.A.
+01-602-861-6984 Voice +01-602-588-9440 FAX
www.icsaero.com
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 1
A664-FTSIU Users Manual Rev C
TABLE OF CONTENTS
1.1. FIGURES ...... 3 2. QUICK START INFO ...... 4 2.1. FTSIU AFDX CONSUMED DATA DISPLAY PAGE (PAGE 2) ...... 5 2.2. FTSIU AFDX RECORDING DETAILS DISPLAY PAGE (PAGE 3) ...... 6 2.3. FTSIU APIC MEMORY DISPLAY PAGE (PAGE 4) ...... 7 2.4. FTSIU INTERNAL STATISTICS DISPLAY PAGE (PAGE 5) ...... 8 3. SCOPE ...... 9 3.1. REFERENCES ...... 9 3.2. ABBREVIATIONS ...... 10 3.3. COPYRIGHTS AND TRADEMARKS ...... 10 4. A664 FLIGHT TEST / SIMULATOR INTERFACE UNIT (A664-FTSIU) FUNCTIONAL OVERVIEW ...... 11
5. A664-FTSIU FLIGHT TEST / SIMULATOR INTERFACE UNIT OPERATIONAL OVERVIEW ...... 12 5.1. SYSTEM OVERVIEW AND INTRODUCTION ...... 12 5.2. SYSTEM POWER UP AND SHUTDOWN ...... 12 5.3. SYSTEM FILE REQUIREMENTS ...... 14 5.4. LOADING SYSTEM FILES ...... 15 5.4.1. FTSIU Configuration File ...... 15 5.5. LOADING SOFTWARE UPDATE FILES ...... 16 5.6. COMMAND-LINE OPERATION ...... 17 5.7. PLAYBACK MODE ...... 17 5.7.1. Fast Forward ...... 17 6. SYSTEM ELECTRICAL INTERFACE CONNECTORS ...... 18 6.1. SYSTEM ELECTRICAL CONNECTORS A664-TIS ...... 18 7. UDP DATAGRAM FORMAT ...... 19 7.1. STATUS BYTE FORMAT (OUTPUT BY A664-FTSIU VIA UDP LINK) ...... 21 7.2. A664-FTSIU OUTPUT DATA TYPES ...... 21 7.3. IEEE 745 SINGLE PRECISION FLOAT ...... 22 7.4. CRC32 USED TO VERIFY CONTENTS OF UDP DATAGRAM ...... 23 8. WINDOWS BASED CONFIGURATION UTILITY ...... 25 8.1. RECOMMENDED MINIMUM COMPUTER REQUIREMENTS ...... 25 8.2. FEATURES ...... 25 8.3. INSTALLATION ...... 26 8.4. CONFIGURATION TOOL BASIC OPERATION ...... 27 8.5. CONFIGURATION TOOL OPERATION ...... 28 8.5.1. New or Existing Map File ...... 29 8.5.2. Loading a Harvest Database ...... 31 8.5.3. Network Applications Tree View ...... 33 8.5.4. Network Application NDO Tree Expansion ...... 34 8.5.5. ARINC-NDO Field Expansion ...... 35 8.5.6. IDL-NDO Field Expansion ...... 36 8.5.7. Possible User Prompts during parameter selection: ...... 37 8.5.8. NDO Field Channel MAP Placement and Display ...... 38 8.5.9. Changing the assigned channel number ...... 39
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 2
A664-FTSIU Users Manual Rev C
9. WINDOWS BASED CONFIGURATION UTILITY OUTPUT DATA STRUCTURES ...... 40 9.1. TIS .CFG FILE FORMAT ...... 40
1.1. Figures
Figure 1 Opening Screen TIS Configuration Tool 26 Figure 2 Opening Screen 28 Figure 3 Selecting a NEW or Existing MAP File 29 Figure 4 Load Map File Dialog 30 Figure 5 NEW Map Initialization 30 Figure 6 Loading an ARINC-664 Database 31 Figure 7 ARINC 664 / AFDX Database Open Dialog 32 Figure 8 Expanded Tree View of Network Applications 33 Figure 9 Network Application Expansion View 34 Figure 10 Expanded ARINC-429 NDO 35 Figure 11 Expanded IDL-NDO types showing fields 36 Figure 12 Multiple Source Selection Dialog 37 Figure 13 Multiple Byte IDL field Selection Dialog 38 Figure 14 Example of placed single channel parameter 38 Figure 15 Mixed Single and Multi Channel Data Selected 39 Figure 16 Channel Change Dialog 39 Figure 17 Channel Overlap Warning Dialog 39
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 3
A664-FTSIU Users Manual Rev C
2. QUICK START INFO A664 TIU Quickstart Information:
This FTSIU computer system is running SuSE Linux Distribution Version 11.0 or later
See: http://www.novell.com/products/opensuse/ for more information if desired. Extensive on-machine help is installed as well as online-help is available.
There are two accounts on this machine. These are:
Account “tisuser” with password “tisuser” Account “root” with password “root”
This machine has an FTP server active as well as a SAMBA file server to allow windows based network machines to transfer files to and from the SIU. The workgroup is presently defined as: ICS
Files may be loaded to the program directory for the FTSIU TIS software by connecting as “tisuser” with password “tisuser”. Configuration Files should be transferred to the home directory of the “tisuser” account which will be the default if logging in with the tisuser account information.
Remote login by the “root” user has been allowed on this machine. This would normally be a security risk, but this machine is a dedicated purpose machine and will not normally be connected to the Internet.
This machine will boot up automatically as an ARINC 664 FTSIU running in a console window on console 1 and begin recording. Recording files are created on the dedicated internal recording media with a path of “/media/TISDATA/”. The filenames contain the extension .01 and are automatically chosen by the FTSIU using the current IRIG time to ensure uniqueness.
There are terminal options associated with the A664-FTSIU which set the names of the configuration file and the LIVE / Playback mode. It also sets the IP address of the UDP data broadcasts and the base UDP port numbers for data to the attached equipment and from the attached equipment.
Below are screen shots of the FTSIU software starting with page 2, which is the Consumed Data page. 35 decoded AFDX parameters of the 8192 possible are displayed on this page. The Windows-based ARINC-664 FTSIU Configuration Tool software (installed on a Windows- based platform) is used to configure the parameters to be consumed from the AFDX bus and subsequently transmitted to the connected Simulation / Data Acquisition equipment via UDP Ethernet. There are 5 pages that may be displayed. Pressing the number keys 1-5 will take you to the associated page number. Page 1 is the default base page.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 4
A664-FTSIU Users Manual Rev C
2.1. FTSIU AFDX Consumed Data Display Page (PAGE 2)
This page shows the decoded AFDX parameters which are specified in the configuration file. Pressing ‘h’ will toggle the data being shown in hex format or as decoded data. The channel numbers can be scrolled through by pressing the ‘a’ (forward) and ‘b’ (backward) keys.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 5
A664-FTSIU Users Manual Rev C
2.2. FTSIU AFDX Recording Details Display Page (PAGE 3)
This page shows the beginning of the Recording Disk Frame Block and is useful to verify data is being received from the attached AFDX bus.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 6
A664-FTSIU Users Manual Rev C
2.3. FTSIU APIC Memory Display Page (PAGE 4)
This page shows the data currently residing in the APIC memory. The memory can be scrolled through using the ‘a’ (forward) and ‘b’ (backward) keys. This functionality is only valid if an APIC card is installed and specified as such with the Interface Control Word parameter on the command line.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 7
A664-FTSIU Users Manual Rev C
2.4. FTSIU Internal Statistics Display Page (PAGE 5)
This page shows the FTSIU statistics, such as the number of AFDX packets received.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 8
A664-FTSIU Users Manual Rev C
3. SCOPE
This document defines the Setup, Installation, and Use of the UDP and Parallel Interface versions of the ARINC-664 Flight Test and Simulator Interface Unit (A664-FTSIU) to the Rockwell Collins AFDX bus. This includes electrical, mechanical, and software interface requirements of the A664-FTSIU platform. This system was developed by Innovative Control Systems, Inc. to provide an ARINC-664 / AFDX Bus to Flight Test and Simulator I/O Interface.
3.1. References
IBM Technical Reference Personal Computer AT (6280070, S229-9611-00)
IBM, P.O. Box 10659, Riverton, New Jersey 08076-0659 U.S. 1-800-IBM-JOURnals (1-800-426-5687) or U.S. 1-609-786-1714,
Personal Computer Bus Standard P996, Draft 2.00, Jan. 18, 1990 IEEE
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 9
A664-FTSIU Users Manual Rev C
3.2. Abbreviations
BIOS Basic Input/Output Operating System COTS Commercial Off-The-Shelf CSA Canadian Standards Association DMA Direct Memory Address EIA Electronic Industry Association EMI Electromagnetic Interference HSD High-Speed Serial Data Interface Hz Hertz IEC International Electrotechnical Commission ISA Industry Standard Architecture PCI Peripheral Component Interconnect TCP/IP Transmission Control Protocol/Internet Protocol TIU Test Interface Unit (Honyewell) TIS Telemetry Interface System UDP User Datagram Protocol
3.3. Copyrights and Trademarks
AMD Advanced Micro Devices Corporation. ARINC Aeronautical Radio, Inc. Honeywell Honeywell Corporation, Business & Commuter Aviation Systems IBM International Business Machines Intel Intel Corporation Microsoft Microsoft Corporation MSDOS Microsoft Corporation
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 10
A664-FTSIU Users Manual Rev C
4. A664 Flight Test / Simulator Interface Unit (A664-FTSIU) Functional Overview
SIU Conversion Platform Block Diagram
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 11
A664-FTSIU Users Manual Rev C
5. A664-FTSIU Flight Test / Simulator Interface Unit Operational Overview
The FTSIU Simulator Interface Unit has two separate and distinct software packages that are provided with the platform, and requires a Rockwell Collins Harvest database for operation. This database is not included with this equipment. Refer to the Rockwell Collins documentation for details regarding the Harvest database.
5.1. System Overview and Introduction
The FTSIU platform is designed to be a stand-alone conversion unit to read and decode parameters from the AFDX bus and to make these available to the end user’s equipment in a format more easily interfaced to than the AFDX bus.
The unit is an Intel processor based computing platform running a modified version of SuSE Linux. The FTSIU is designed to be turned on and to come up converting data. The power-on operation is automatic. The unit will boot up and automatically log into the ‘tisuser’ account and start the FTSIU software. Power off may be accomplished by simply turning off the power to the unit, however we recommend performing an orderly shutdown where practical. The Linux operating system is generally shutdown by issuing a shutdown command. This may be done from the connected keyboard and monitor or remotely over the network through TELNET. The FTSIU unit uses the Rieser journaling file system, and is therefore tolerant of power off shutdowns, the Rieser system allows the file system to avoid corrupted files that would otherwise occur.
As a Linux based machine, the FTSIU may have its configuration file transferred via network FTP, Floppy, or USB FLASH memory devices to the proper user directory.
5.2. System Power Up and Shutdown
The FTSIU unit may simply be turned on for power up operation. The unit will come up running the FTSIU software automatically and will use the last configuration files that were loaded to direct it operation. There is more on the configuration files later in this section.
For shutdown, the process varies. There are three ways to shutdown the system.
1. Power Off. Power off may be accomplished by simply turning off the power to the unit, however we recommend performing an orderly shutdown where practical. The FTSIU unit uses the Rieser journaling file system, and is therefore tolerant of power off shutdowns, this does still have some risk of file corruption, but the chances of this are exceedingly small.
2. CTL + ALT + DEL from the connected keyboard. Issuing a CLT + ALT + DEL from the connected keyboard will send a termination signal to all running processes and restart the machine. This is not a shut down, but can be used to restart the FTSIU unit after new configuration files have been loaded. Also, since this must be done from the connected keyboard, the user can watch the monitor and shut off the power after the screen has gone blank or during the initial stages of the reboot before the operating system is loaded.
3. Shutdown Command from a console of Telnet session. Issuing the command “shutdown –h now” will shutdown and halt the machine without delay. This can be done from a console window, but not from TTY1 where the FTSIU software is running. Switch to console 2 by typing CTL + ATL + F2, log in as user ‘root’ with password ‘root’. Issue the command “shutdown –h now” and wait for the system to indicate that “run level 0 has been reached”. This is the safest form of shutdown, but it also requires the most interactions.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 12
A664-FTSIU Users Manual Rev C
Alternately, this can be done from a Telnet session. The following is a log of a sample shutdown from a telnet session.
From a TELNET session to the assigned IP address on the Corporate LAN connection:
Welcome to OpenSUSE 10.3 login: root Password: root You have new mail in /var/spool/mail/root. Last login: Tue Mar 16 00:58:01 from 192.168.1.17 Have a lot of fun... FTSIU:~ # FTSIU:~ # shutdown -h now
Broadcast message from root (pts/0) Tue Mar 16 01:22:35 1999...
The system is going down for system halt NOW !!
Broadcast Message from root@FTSIU (/dev/tty1) at 1:22 ...
Network is going down now!
Approximately 15 seconds after the last message “Network is going down now!”, the system may be shut off as Run Level 0 will have been reached.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 13
A664-FTSIU Users Manual Rev C
5.3. System File Requirements
The FTSIU platform must be directed which AFDX parameters to read and what to do with this data. A Windows based configuration utility (ARINC-664 FTSIU Configuration Tool) is used to define what AFDX data is to be read and placed onto a 64-bit word parallel interface to Gulfstream Telemetry Equipment. This tool is described in the section entitled “Windows Based Configuration Utility”.
The ARINC-664 FTSIU Configuration Tool requires the use of a Harvest Database in order to extract AFDX parameters. The utility is then able to generate a system configuration file. This file can be named whatever you wish, but must match the name specified on the command line of the FTSIU program when it is started and must be loaded onto the FTSIU system before data conversion can take place.
The FTSIU supports loading of files via FTP or alternately the files may be transferred through a Microsoft style mapped drive transfer. The FTSIU platform is both an FTP server and an SMB server.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 14
A664-FTSIU Users Manual Rev C
5.4. Loading System Files
The FTSIU platform must have a single configuration file loaded. This may be loaded via FTP or through the FTSIU USB interface.
5.4.1. FTSIU Configuration File
The FTSIU unit looks for a configuration file in the startup directory of the FTSIU software. The FTSIU platform is designed to boot up, automatically run the FTSIU software, and look for the file “afdx.cfg” from the home directory of the user ‘tisuser’. If the file is not found on the hard drive, the FTSIU software will not continue and conversion of data will not take place.
The FTSIU configuration file produced by the Windows-based ARINC-664 FTSIU Configuration Tool will not be produced with a filename suitable for use with the FTSIU. It is necessary to rename the file from its original name to “afdx.cfg” before copying it to tisuser directory. The Windows based configuration tool creates a files called “yourname.cfg” where
The correct files may be transferred to the FTSIU using the FTP protocol and connecting to the FTSIU with an FTP client program. When connecting to the FTSIU, the username ‘tisuser’ and password ‘tisuser’ should be used. If you connect using this account, you will by default be in the proper directory for the file transfer. Simply use the FTP “put” command to transfer the file. This newly loaded file will not be used until the FTSIU unit is restarted or at a minimum the FTSIU application running on Linux console TTY1 is restarted. This application is designed to start at power up, so unless you have made changes, the application is already running by the time you FTP to new file. Since this file is only ready at FTSIU program start, we recommend restarting the FTSIU unit.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 15
A664-FTSIU Users Manual Rev C
5.5. Loading Software Update Files
The FTSIU platform can have system software update files loaded. These may be loaded over the 1000/100 Mb/s LAN connection to the users equipment. These may also be loaded through the FTSIU USB interface. The 10/100/1000 LAN connection is at IP address 10.1.1.1 by default. This may be changed in Linux, but it is recommended that the connected users equipment be given an IP address of 10.1.1.X on the same network, but of course not 10.1.1.0, 10.1.1.255, or 10.1.1.1 as these are used or have special meaning.
To load the Version 2.00 software update to the FTSIU follow these steps:
· Start up the FTSIU · FTP the updated tisupdate_Vxxx.tar file to the tisuser directory just like you would an afdx.cfg file. · Switch to an alternate console window with CTRL + ALT + F2 · Log in as "root" · change to the tisuser home directory with cd ~tisuser or cd /home/tisuser. Either one will work. · type "tar xvf tisupdate_Vxxx.tar" to extract the install files. These will be placed in the directory /home/tisuser/tis_version_xxx · change to the tis_version_xxx directory · type “./install” (This will return immediately, it is very quick).
This command will create a backup directory called old_tis_software_xxx (where xxx is the previous version) and write your current tis and afdfx.cfg files to it so that you will have a backup. It will then copy the new tis executable to the /home/tisuser directory and set the permissions and ownership so that the software may run correctly.
Reboot the machine (Ctrl + Alt + Del to shut down) and you will be using the new version when you restart the machine. Note that it is OK to do all of this while the old FTSIU software is running.
The following commands (similar only) are executed by the install batch file. (For reference only)
cd /home/tisuser mkdir old_tis_software_110 cp tis /home/tisuser/old_tis_software_110/tis cp afdx.cfg /home/tisuser/old_tis_software_110/afdx.cfg rm tis cp /home/tisuser/tisdt1_version_200/tis /home/tisuser/tis cp /home/tisuser/tisdt1_version_200/.bashrc /home/tisuser/.bashrc chmod 777 tis chown root:root tis chmod +s tis
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 16
A664-FTSIU Users Manual Rev C
5.6. Command-Line Operation
The FTSIU may be run in a command-line mode of operation from a console. This allows the user to change parameters such as the IP address and UDP output port for the outgoing UDP packets. It also allows the user to run the application in playback mode rather than in live recording mode. The command-line usage is as follows:
Usage: ftsiu
Where:
Options: -c = Continuous Playback mode. Indicates playback will occur continuously when in Playback mode. The specified playback file will continuously loop back to the beginning of the file once the end is reached. Execution must be stopped using Control-C in this mode.
5.7. Playback Mode
The FTSIU may be used in a playback mode of operation which allows playing back of any previously recorded files. The timing of the data written to the APIC memory as well as the timing of the UDP output datagrams will resemble the timing of the data when it was recorded. Recorded files may be played back by specifying the full path of the file on the command-line. The following is an example command-line for playback mode:
./ftsiu -c afdx.cfg /media/TISDATA/
5.7.1. Fast Forward
While a file is being played back, the letter ‘f’ (case insensitive) may be pressed at any time to enter fast forward mode. This significantly increases the playback speed and allows the user to fast forward to a certain position or time within the file. Pressing the letter ‘p’ (case insensitive) will exit fast forward mode and returns the playback speed to normal.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 17
A664-FTSIU Users Manual Rev C
6. System Electrical Interface Connectors
6.1. System Electrical Connectors A664-TIS
The FTSIU platform has electrical connections to the AFDX data bus and to the Simulator / Telemetry / Acquisition System. The connection points are as shown:
PS/2 Keyboard and VIDEO AFDX Bus UDP IRIG APIC Ch1 APIC Ch0 Mouse Inputs Input Output Input I/O I/O
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 18
A664-FTSIU Users Manual Rev C
7. UDP Datagram Format
Data to and from the FTSIU consists of from 1 to 8192 pieces of data (32-bits each) called “channels”. The AFDX parameter that occurs in a particular channel is definable using the ICS provided Windows based configuration tool. This tool produces a file which is loaded into the FTSIU.
The generated configuration file defines which AFDX parameters will be converted and transmitted to the users connected simulator, and in what “channels” they will appear. This configuration file does not need to change from aircraft load to aircraft load unless a parameter is deleted from the new aircraft load, or changes data type.
The format of transmission to and from the FTSIU and the user’s platform is via UDP datagrams. UDP is a well defined protocol that is essentially a subset of TCP of the well defined TCP/IP protocol. Definition of UDP datagrams will not be discussed here except to define the payload of the individual datagrams as they pertain to the FTSIU data flow.
The FTSIU will transmit one to 32 datagrams of length 1334 bytes at a specific rate. This rate may be defined on the command line, or the FTSIU can be instructed to use the fastest parameter rate found in the configuration file. Each Datagram contain 256 “channels” or 32-bit words of data from the ASCB D bus as well as 256 bytes of parameter status and some packet overhead.
By sending up to 32 datagrams each containing 256 “channels”, a maximum of 8192 channels may be sent. This is the maximum possible on a single FTSIU platform and is processing power dependent.
If the user configures the FTSIU for fewer than 256 channels of data (in positions 1-256), then only 1 datagram will be sent at the specified rate. If more data is defined, then more datagrams will be sent as needed. Datagrams will be padded with 0 if channels are undefined.
Datagram 0 will contain channels [1..256] and will be sent as a broadcast UDP datagram on UDP port 4096 Datagram 1 will contain channels [257..512] and will be sent as a broadcast UDP datagram on UDP port 4097 Datagram 2 will contain channels [513..768] and will be sent as a broadcast UDP datagram on UDP port 4098 : : : Datagram 31 will contain channels [7937..8192] and will be sent as a broadcast UDP datagram on UDP port 4127
As each UDP datagram is on a different port, it is possible to know that data received on that port is always data from the channels associated with that datagram.
Data Structure of UDP Datagrams sent to and from ICS FTSIU:
typedef struct FTSIUADI_DATAGRM { unsigned long LENGTH; unsigned long RESERVED; unsigned long CHANNEL[256] ; unsigned char STATUS[256] ; unsigned long CRC32 ; } DATAGRAM ;
Where:
LENGTH 32-Bit value indicating the length of the UDP payload this includes the not only the 256 parameters, but also the LENGTH, RESERVED, and CRC32 fields. ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 19
A664-FTSIU Users Manual Rev C
RESERVED 32-Bit value which is reserved and always specified as 0.
CHANNEL[256] 256 32-Bit values for the channels represented by the UDP datagram.
STATUS[256] 256 8-Bit status values for the channels represented by the UDP datagram. (see section 8.1 Status Byte Format for further definition)
CRC32 32-Bit CRC value of the UDP payload this includes the not only the 256 parameters, but also the LENGTH, and RESERVED fields, but not the CRC itself.
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 20
A664-FTSIU Users Manual Rev C
7.1. Status Byte Format (Output by A664-FTSIU via UDP link)
These bytes always contain a value of 0 for the FTSIU.
7.2. A664-FTSIU Output Data Types
All data that is read and converted from the AFDX Bus by the FTSIU is produced and placed into 32-bit data blocks to the user data acquisition equipment. The available data types are as follows:
Table 1. FTSIU Parameter Data Types
ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 21
A664-FTSIU Users Manual Rev C
7.3. IEEE 745 Single Precision Float
(For more detailed information, see specification ANSI/IEEE Standard 754-1985)
The IEEE single precision floating point standard representation requires a 32 bit word, which may be represented as numbered from 31to 0, left to right. The first bit is the sign bit, S, the next eight bits are the exponent bits, 'E', and the final 23 bits are the fraction 'F':
S EEEEEEEE FFFFFFFFFFFFFFFFFFFFFFF 31 30 23 22 0
The value V represented by the word may be determined as follows:
If E=255 and F is nonzero, then V=NaN ("Not a number") If E=255 and F is zero and S is 1, then V=-Infinity If E=255 and F is zero and S is 0, then V=Infinity If 0 In particular, 0 00000000 00000000000000000000000 = 0 1 00000000 00000000000000000000000 = -0 0 11111111 00000000000000000000000 = Infinity 1 11111111 00000000000000000000000 = -Infinity 0 11111111 00000100000000000000000 = NaN 1 11111111 00100010001001010101010 = NaN 0 10000000 00000000000000000000000 = +1 * 2**(128-127) * 1.0 = 2 0 10000001 10100000000000000000000 = +1 * 2**(129-127) * 1.101 = 6.5 1 10000001 10100000000000000000000 = -1 * 2**(129-127) * 1.101 = -6.5 0 00000001 00000000000000000000000 = +1 * 2**(1-127) * 1.0 = 2**(-126) 0 00000000 10000000000000000000000 = +1 * 2**(-126) * 0.1 = 2**(-127) 0 00000000 00000000000000000000001 = +1 * 2**(-126) * 0.00000000000000000000001 = 2**(-149) (Smallest positive value) ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 22 A664-FTSIU Users Manual Rev C 7.4. CRC32 used to verify contents of UDP datagram The following software is the actual CRC32 algorithm used to produce the CRC of the UDP datagram. The CRC itself is not a part of the CRC data in the datagram. /**********************************************************************/ /* */ /* Demonstration program to compute the 32-bit CRC used as the frame */ /* check sequence in ADCCP (ANSI X3.66, also known as FIPS PUB 71 */ /* and FED-STD-1003, the U.S. versions of CCITT's X.25 link-level */ /* protocol). The 32-bit FCS was added via the Federal Register, */ /* 1 June 1982, p.23798. I presume but don't know for certain that */ /* this polynomial is or will be included in CCITT V.41, which */ /* defines the 16-bit CRC (often called CRC-CCITT) polynomial. FIPS */ /* PUB 78 says that the 32-bit FCS reduces otherwise undetected */ /* errors by a factor of 10^-5 over 16-bit FCS. */ /* */ /**********************************************************************/ /* Need an unsigned type capable of holding 32 bits; */ typedef unsigned long int UNS_32_BITS; /*------*/ /* Copyright (C) 1986 Gary S. Brown. You may use this program, or */ /* code or tables extracted from it, as desired without restriction. */ /*------*/ /* First, the polynomial itself and its table of feedback terms. The */ /* polynomial is */ /* X^32+X^26+X^23+X^22+X^16+X^12+X^11+X^10+X^8+X^7+X^5+X^4+X^2+X^1+X^0 */ /* Note that we take it "backwards" and put the highest-order term in */ /* the lowest-order bit. The X^32 term is "implied"; the LSB is the */ /* X^31 term, etc. The X^0 term (usually shown as "+1") results in */ /* the MSB being 1. */ /* */ /* Note that the usual hardware shift register implementation, which */ /* is what we're using (we're merely optimizing it by doing eight-bit */ /* chunks at a time) shifts bits into the lowest-order term. In our */ /* implementation, that means shifting towards the right. Why do we */ /* do it this way? Because the calculated CRC must be transmitted in */ /* order from highest-order term to lowest-order term. UARTs transmit */ /* characters in order from LSB to MSB. By storing the CRC this way, */ /* we hand it to the UART in the order low-byte to high-byte; the UART */ /* sends each low-bit to hight-bit; and the result is transmission bit */ /* by bit from highest- to lowest-order term without requiring any bit */ /* shuffling on our part. Reception works similarly. */ /* */ /* The feedback terms table consists of 256, 32-bit entries. Notes: */ /* */ /* 1. The table can be generated at runtime if desired; code to do so */ /* is shown later. It might not be obvious, but the feedback */ /* terms simply represent the results of eight shift/xor opera- */ /* tions for all combinations of data and CRC register values. */ /* */ /* 2. The CRC accumulation logic is the same for all CRC polynomials, */ /* be they sixteen or thirty-two bits wide. You simply choose the */ /* appropriate table. Alternatively, because the table can be */ /* generated at runtime, you can start by generating the table for */ /* the polynomial in question and use exactly the same "updcrc", */ /* if your application needn't simultaneously handle two CRC */ /* polynomials. (Note, however, that XMODEM is strange.) */ /* */ /* 3. For 16-bit CRCs, the table entries need be only 16 bits wide; */ /* of course, 32-bit entries work OK if the high 16 bits are zero. */ /* */ /* 4. The values must be right-shifted by eight bits by the "updcrc" */ /* logic; the shift must be unsigned (bring in zeroes). On some */ /* hardware you could probably optimize the shift in assembler by */ /* using byte-swap instructions. */ /*------*/ ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 23 A664-FTSIU Users Manual Rev C static UNS_32_BITS crc_32_tab[] = { /* CRC polynomial 0xedb88320 */ 0x00000000L, 0x77073096L, 0xee0e612cL, 0x990951baL, 0x076dc419L, 0x706af48fL, 0xe963a535L, 0x9e6495a3L, 0x0edb8832L, 0x79dcb8a4L, 0xe0d5e91eL, 0x97d2d988L, 0x09b64c2bL, 0x7eb17cbdL, 0xe7b82d07L, 0x90bf1d91L, 0x1db71064L, 0x6ab020f2L, 0xf3b97148L, 0x84be41deL, 0x1adad47dL, 0x6ddde4ebL, 0xf4d4b551L, 0x83d385c7L, 0x136c9856L, 0x646ba8c0L, 0xfd62f97aL, 0x8a65c9ecL, 0x14015c4fL, 0x63066cd9L, 0xfa0f3d63L, 0x8d080df5L, 0x3b6e20c8L, 0x4c69105eL, 0xd56041e4L, 0xa2677172L, 0x3c03e4d1L, 0x4b04d447L, 0xd20d85fdL, 0xa50ab56bL, 0x35b5a8faL, 0x42b2986cL, 0xdbbbc9d6L, 0xacbcf940L, 0x32d86ce3L, 0x45df5c75L, 0xdcd60dcfL, 0xabd13d59L, 0x26d930acL, 0x51de003aL, 0xc8d75180L, 0xbfd06116L, 0x21b4f4b5L, 0x56b3c423L, 0xcfba9599L, 0xb8bda50fL, 0x2802b89eL, 0x5f058808L, 0xc60cd9b2L, 0xb10be924L, 0x2f6f7c87L, 0x58684c11L, 0xc1611dabL, 0xb6662d3dL, 0x76dc4190L, 0x01db7106L, 0x98d220bcL, 0xefd5102aL, 0x71b18589L, 0x06b6b51fL, 0x9fbfe4a5L, 0xe8b8d433L, 0x7807c9a2L, 0x0f00f934L, 0x9609a88eL, 0xe10e9818L, 0x7f6a0dbbL, 0x086d3d2dL, 0x91646c97L, 0xe6635c01L, 0x6b6b51f4L, 0x1c6c6162L, 0x856530d8L, 0xf262004eL, 0x6c0695edL, 0x1b01a57bL, 0x8208f4c1L, 0xf50fc457L, 0x65b0d9c6L, 0x12b7e950L, 0x8bbeb8eaL, 0xfcb9887cL, 0x62dd1ddfL, 0x15da2d49L, 0x8cd37cf3L, 0xfbd44c65L, 0x4db26158L, 0x3ab551ceL, 0xa3bc0074L, 0xd4bb30e2L, 0x4adfa541L, 0x3dd895d7L, 0xa4d1c46dL, 0xd3d6f4fbL, 0x4369e96aL, 0x346ed9fcL, 0xad678846L, 0xda60b8d0L, 0x44042d73L, 0x33031de5L, 0xaa0a4c5fL, 0xdd0d7cc9L, 0x5005713cL, 0x270241aaL, 0xbe0b1010L, 0xc90c2086L, 0x5768b525L, 0x206f85b3L, 0xb966d409L, 0xce61e49fL, 0x5edef90eL, 0x29d9c998L, 0xb0d09822L, 0xc7d7a8b4L, 0x59b33d17L, 0x2eb40d81L, 0xb7bd5c3bL, 0xc0ba6cadL, 0xedb88320L, 0x9abfb3b6L, 0x03b6e20cL, 0x74b1d29aL, 0xead54739L, 0x9dd277afL, 0x04db2615L, 0x73dc1683L, 0xe3630b12L, 0x94643b84L, 0x0d6d6a3eL, 0x7a6a5aa8L, 0xe40ecf0bL, 0x9309ff9dL, 0x0a00ae27L, 0x7d079eb1L, 0xf00f9344L, 0x8708a3d2L, 0x1e01f268L, 0x6906c2feL, 0xf762575dL, 0x806567cbL, 0x196c3671L, 0x6e6b06e7L, 0xfed41b76L, 0x89d32be0L, 0x10da7a5aL, 0x67dd4accL, 0xf9b9df6fL, 0x8ebeeff9L, 0x17b7be43L, 0x60b08ed5L, 0xd6d6a3e8L, 0xa1d1937eL, 0x38d8c2c4L, 0x4fdff252L, 0xd1bb67f1L, 0xa6bc5767L, 0x3fb506ddL, 0x48b2364bL, 0xd80d2bdaL, 0xaf0a1b4cL, 0x36034af6L, 0x41047a60L, 0xdf60efc3L, 0xa867df55L, 0x316e8eefL, 0x4669be79L, 0xcb61b38cL, 0xbc66831aL, 0x256fd2a0L, 0x5268e236L, 0xcc0c7795L, 0xbb0b4703L, 0x220216b9L, 0x5505262fL, 0xc5ba3bbeL, 0xb2bd0b28L, 0x2bb45a92L, 0x5cb36a04L, 0xc2d7ffa7L, 0xb5d0cf31L, 0x2cd99e8bL, 0x5bdeae1dL, 0x9b64c2b0L, 0xec63f226L, 0x756aa39cL, 0x026d930aL, 0x9c0906a9L, 0xeb0e363fL, 0x72076785L, 0x05005713L, 0x95bf4a82L, 0xe2b87a14L, 0x7bb12baeL, 0x0cb61b38L, 0x92d28e9bL, 0xe5d5be0dL, 0x7cdcefb7L, 0x0bdbdf21L, 0x86d3d2d4L, 0xf1d4e242L, 0x68ddb3f8L, 0x1fda836eL, 0x81be16cdL, 0xf6b9265bL, 0x6fb077e1L, 0x18b74777L, 0x88085ae6L, 0xff0f6a70L, 0x66063bcaL, 0x11010b5cL, 0x8f659effL, 0xf862ae69L, 0x616bffd3L, 0x166ccf45L, 0xa00ae278L, 0xd70dd2eeL, 0x4e048354L, 0x3903b3c2L, 0xa7672661L, 0xd06016f7L, 0x4969474dL, 0x3e6e77dbL, 0xaed16a4aL, 0xd9d65adcL, 0x40df0b66L, 0x37d83bf0L, 0xa9bcae53L, 0xdebb9ec5L, 0x47b2cf7fL, 0x30b5ffe9L, 0xbdbdf21cL, 0xcabac28aL, 0x53b39330L, 0x24b4a3a6L, 0xbad03605L, 0xcdd70693L, 0x54de5729L, 0x23d967bfL, 0xb3667a2eL, 0xc4614ab8L, 0x5d681b02L, 0x2a6f2b94L, 0xb40bbe37L, 0xc30c8ea1L, 0x5a05df1bL, 0x2d02ef8dL }; /*------*/ /* Define the CRC macro */ /*------*/ #define UPDC32(octet, crc) (crc_32_tab[((crc) ^ (octet)) & 0xff] ^ ((crc) >> 8)) /*------*/ /* Function: CRC32 */ /* */ /* This function is used to perform a 32-bit ANSI 3.66 CRC on the */ /* buffer specified a byte at a time for length bytes. */ /*------*/ long crc32(char buffer[], int length) { register unsigned long oldcrc32 ; register unsigned long oldcrc ; int index ; /*------*/ /* Initialize the OLD CRC and the character count */ /*------*/ oldcrc32 = 0xFFFFFFFFL ; /*------*/ /* CRC the file a byte at a time until EOF. */ /*------*/ for (index=0; index < length; index++) { oldcrc32 = UPDC32(buffer[index], oldcrc32) ; } /*------*/ /* Update the final CRC of the Data. */ /*------*/ oldcrc = oldcrc32 = ~oldcrc32 ; return oldcrc ; } ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 24 A664-FTSIU Users Manual Rev C 8. Windows Based Configuration Utility The ARINC-664 / AFDX Flight Test and Simulator Interface Unit is a highly configurable complex data translator. The platform itself executes software that picks up ARINC-664 / AFDX data from the Pilots or Co- Pilots side of the aircraft and makes this data available in engineering units format to Flight Test Data Acquisition Systems or Simulators over a UDP Ethernet interface or through an ICS APIC Parallel Interface Card. The platform must be directed which ARINC-664 parameters to read and what to do with this data (where to place it in the UDP stream or APIC memory. A Microsoft Windows based configuration utility is used to pick the ARINC-664 parameters from a database of available parameters and to define where in the APIC memory or UDP data stream to place this data. The following sections deal with the installation and operation of this configuration utility. 8.1. Recommended Minimum Computer Requirements Windows XP, Windows Vista, or Windows 7 (32-bit or 64-bit) 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor 1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit) 16 GB available hard disk space (32-bit) or 20 GB (64-bit) DirectX 9 graphics device with WDDM 1.0 or higher driver Recommended Minimum Screen Resolution 1440 x 900 8.2. Features Windows XP/Vista/Windows 7 32-bit or 64-bit compatible Self contained executable requires no libraries or install procedure. Reads Rockwell Collins Harvest database directly Allows selection of ARINC-664 parameters in an easy to use tree view Displays a channel map of what ARINC-664 data is selected for which output channels. Uses Rockwell Collins HARVEST Tool Database for parameter names, descriptions, and types. Produces configuration file for the ARINC-664/AFDX Flight Test / Simulator interface Platform. Allows save and restore of user named channel data maps Checks for changes and prompts for save on Exit. Point and Click to set a parameter in the Channel map. Has Delete Function that will delete a parameter completely from the channel MAP. ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 25 A664-FTSIU Users Manual Rev C 8.3. Installation The ARINC-664 FTSIU TIS Configuration utility does not require an install procedure. The executable is built to be self contained with all required run time libraries included. Simply drop the executable on your desktop and click to start. When the tool starts you should see the following main screen: Figure 1 Opening Screen FTSIU TIS Configuration Tool ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 26 A664-FTSIU Users Manual Rev C 8.4. Configuration Tool Basic Operation Create a NEW channel map file or Load an existing Channel Map File Load a HARVEST Database for the Aircraft Application Select an ARINC-664 parameter to place in the map from the tree view of the HARVEST ARINC-NDO and IDL-NDOs available. Double click the parameter to place it at the next available channel in the map. Repeat until you have selected all data that you wish to monitor and convert Save the Channel Map Generates a Configuration File for the Flight Test / Simulator Interface ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 27 A664-FTSIU Users Manual Rev C 8.5. Configuration Tool Operation Opening screen when program is started Figure 2 Opening Screen ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 28 A664-FTSIU Users Manual Rev C 8.5.1. New or Existing Map File From the file menu or the main screen, you must first either load a pre-existing map, or create a new map. Figure 3 Selecting a NEW or Existing MAP File ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 29 A664-FTSIU Users Manual Rev C Select “Load Map File” and a file selection dialog will appear: Figure 4 Load Map File Dialog OR Select NEW MAP to clear the MAP display and initialize the map to a fresh and empty state. Figure 5 NEW Map Initialization ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 30 A664-FTSIU Users Manual Rev C 8.5.2. Loading a Harvest Database Now you must select a Rockwell / Collins HARVEST Database to select parameters from. Select the File “Load Database” Figure 6 Loading an ARINC-664 Database A File Open Dialog will open next (see next page). ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 31 A664-FTSIU Users Manual Rev C From the Open Access AFDX / 664 Database Dialog, select a directory and database file. Present supported databases are of the Rockwell / Collins Harvest Database format. Figure 7 ARINC 664 / AFDX Database Open Dialog Once the database has been selected, The Tree view of the Database Data will fill in and automatically open the top level tree for the aircraft application will open. See Figure 8 Expanded Tree View of Network Applications. ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 32 A664-FTSIU Users Manual Rev C 8.5.3. Network Applications Tree View The tree view is now filled in with the individual Network Applications if the proper format database is loaded. This database will be available from Rockwell / Collins for your aircraft application. Innovative Control Systems, Inc. does not supply this database. Figure 8 Expanded Tree View of Network Applications ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 33 A664-FTSIU Users Manual Rev C 8.5.4. Network Application NDO Tree Expansion By Clicking on one of the Network Applications, the Application tree node will open up displaying all of the available Network Data Objects (NDOs) for that application. Figure 9 Network Application Expansion View ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 34 A664-FTSIU Users Manual Rev C 8.5.5. ARINC-NDO Field Expansion At the Network Application NDO level of the tree, there are two primary types of Network Data Objects supported by the present version of the ARINC-664 TIS software. These are ARINC-429 NDOs and IDL NDOs. ARINC-429 NDOs are all 32-bits long and fit into one TIS Channel. IDL-NDOs are usually larger than one TIS channel (32-bits) and need to be drilled down into to open the individual IDL-NDO fields (the next tree level). You may however at this level double click an ARINC-429 NDO and have the entire ARINC-429 word (all 32-bits) set into the next available TIS channel. You are required to expand all IDL NDO types before selecting any of the IDL-NDO fields for placement into a TIS Channel. You may alternately expand the ARINC-429 NDO and select individual fields from the ARINC-429 NDO to be pulled from the ARINC-429 word, masked, shifted, and normalized in the LS bits of a TIS channel for easier decoding of only a part of an ARINC-429 NDO. Any part of the ARINC-429 NDO can be selected to be placed into a single TIS Channel Figure 10 Expanded ARINC-429 NDO ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 35 A664-FTSIU Users Manual Rev C 8.5.6. IDL-NDO Field Expansion Below, examples of expanded IDL type NDOs that have been expanded to allow selection and placement into TIS channels. Types that are 64-bits (8 bytes) or less will automatically be placed in one or two consecutive TIS channels if selected. Some IDL-NDO types are larger than 64-bits and in these cases, a pop-up window will open asking you for how many bytes to actually copy to the TIS channels. (4 bytes per TIS channel word) Figure 11 Expanded IDL-NDO types showing fields ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 36 A664-FTSIU Users Manual Rev C 8.5.7. Possible User Prompts during parameter selection: When selecting an ARINC-429 NDO or an IDL-NDO, there are sometimes multiple possible sources of the data. The TIS / FTSIU configuration tool will prompt you for which source you wish to place into which TIS channel. This is necessary when multiple sources of the same NDO ID are available on a network application. In the example below, values are available of 32, 64, and 96. These values undoubtedly translate to one of three possible cabinets or racks, but the information to decode these to cabinet names is application specific and not contained in the Harvest database. Figure 12 Multiple Source Selection Dialog When an IDL-NDO is expanded and a field selected that is larger than 64-bits, then the TIS/FTSIU configuration tool prompts you to enter the number of bytes you actually wish to assign to consecutive TIS channels. The field will be automatically filled in with the total number of bytes in the field, but this can sometimes be large such as the example below that is 384 bytes or 96 consecutive TIS channels. ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 37 A664-FTSIU Users Manual Rev C Figure 13 Multiple Byte IDL field Selection Dialog 8.5.8. NDO Field Channel MAP Placement and Display Once a parameter is selected, it is placed into the next available open channel in the channel map as shown below. The NDO Identification number, the parameter Name and Path, The Data Type, the Source, and the Rate in Hz are displayed in the channel map. The TIS Channel number is the first column of the table in light green. If you wish to assign a different channel number to the parameter you can click on the channel number and it will allow you to change the assigned number. Figure 14 Example of placed single channel parameter In some cases, a parameter may occupy more than one channel, the following is an example of both single and multiple channel placements and how they are displayed. ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 38 A664-FTSIU Users Manual Rev C Figure 15 Mixed Single and Multi Channel Data Selected 8.5.9. Changing the assigned channel number The channel number is automatically assigned as the next available empty channel, however, you can reassign a parameter to a new TIS / FTSIU channel by left clicking on the channel number of a set parameter. Figure 16 Channel Change Dialog If you select a new channel number that will cause a single or multi channel parameter to overlap another already placed parameter, you will receive a warning and the parameter number will not be changed. Figure 17 Channel Overlap Warning Dialog ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 39 A664-FTSIU Users Manual Rev C 9. Windows Based Configuration Utility Output Data Structures 9.1. TIS .CFG File Format The Telemetry Interface Configuration file that is produced by the Windows based configuration tool is a binary file of 96 byte records that contain information about each parameter placed in the channel map. The first entry in the .CFG file is a single 32-bit signed int value indicating the total number of records in the file. /*------*/ /*------*/ /* ARINC 664 / AFDX TIS Configuration First Record Structure (Rockwell/Collins Version)*/ /*------*/ /*------*/ typedef struct AFDXTIS_FirstRecStruct_Def { unsigned long int NumberOfRecords ; // Number of "TISConfigStruc" records to follow unsigned long int MIN_NDO_RATE_MicroSec ; // Rate in Microseconds time_t CfgCreatedTime ; // Windows / Linux time_t format unsigned long int CfgVersion ; // Configuration File Version / Format Information } TISConfigHeaderStruc ; /*------*/ /*------*/ /* ARINC 664 / AFDX TIS Configuration Record Structure (Rockwell/Collins Version)*/ /*------*/ /*------*/ typedef struct AFDXTIS_Struct_Def { unsigned long int TISChannel ; // Channel Number 0..8192 (Mult by 8 for APIC DPRAM Address unsigned long int NDO_ID ; // NDO Identification MS .. LS with NDO SRC byte 4 unsigned long int NDO_TYPE ; // 1 = IDL-NDO, 2 = ARINC-NDO, unsigned long int NDO_RATE_MicroSec ; // Rate in Microseconds float NDO_RATE_HZ ; // Rate in Hertz unsigned char WKSN[50] ; // 50 Character Well Known Name or Service String in Harvest unsigned char DataName[150] ; // 150 Character String in Harvest unsigned long int A429BitStart ; // Only ARINC-NDO Field Start and Stop unsigned long int A429BitStop ; // Only ARINC-NDO Field Start and Stop unsigned char A429TypeString[20]; // Only ARINC-NDO Field 20 Character String in Harvest unsigned long int IDLStartByte ; // Only IDL-NDO Field Start Byte unsigned long int IDLByteCount ; // Only IDL-NDO Field Length Bytes unsigned char IDLTypeString[20] ; // Only IDL-NDO Field 20 Character String in Harvest } TISConfigStruc ; See Definitions on following pages. ICS, Inc. 10801 N. 24th Ave. Suite 103 Phoenix, AZ. 85029 U.S.A. Voice +01-602-861-6984 FAX +01-602-588-9440 40