Flight Data Interfaces ALLFlight / NTED / JEDEYE

This document describes the transmission of flight state data within the project ALLFlight and for NTED as well as for the JEDEYE helmet system. In 2008, while starting the project ALLFlight, a message for transmission of flight state data between the FHS experimental system and the so-called sensor co-computer (SCC) was defined. These data are provided by the so-called DMC (Data Management Computer) of the FHS experimental system. The DMC is able to combine different signals from different sources and sensors of the FHS like INS, GPS, Time, ADC, Radio altimeter etc. and transmits these data in a user-defined format via a UDP Ethernet connection. This data stream from the DMC is organized in UDP messages which are transmitted on a multicast port. The structure of this message is described in the first part of this document. In 2011 DLR starts to operate two different HMD systems which are manufactured by Elbit. Both systems require flight state data, as UPD messages via Ethernet connection, which are used to “drive” elements of the so-called “stroke symbology”. These data are provided by the DMC and transmitted in a user-defined format via a UDP Ethernet connection. The different data streams from the DMC to these display systems is organized in different UPD messages, which are described in the second and third part of this document. In September 2011 the integration of the JEDEYE system into the GECO simulator has been conducted in close cooperation between DLR and Elbit. During this integration work, some data elements for controlling the basic HMD symbols (see Figure 1) of the display needed to be modified to comply with Elbit’s frame work.