Abstract

The US Army has a requirement for a highly accurate inertial/TACAN hybrid navigation system. This paper describes the navigation system architecture developed to meet this requirement, the specific hardware selected and the development status. At the beginning of the Integrated Inertial Navigation System (IINS) development program it was anticipated that significant technological advances would take place in its life cycle. In addition, mission requirements were expected to change as the system evolved. Particular attention was therefore given to the IINS system architecture, specifically the partitioning of hardware and software functions as well as the means of data transmittal between the subsystem elements. The paper describes in detail the design trade-offs made as well as hardware selections. The system is configured using several different manufacturers' equipment making the data interface and its configuration control of great importance. The above considerations lead to the conclusion that the appropriate data bus interface standard would be MIL-STD-1553. This interface standard not only facilitates configuration control during system development, but will allow rapid integration with future aircraft systems that will use it as a primary means of data transmittal. The paper describes in detail the signal interface between the subsystem element, onboard mission equipment and flight instruments. The most significant change anticipated in the course of the IINS life cycle is the substitution of Global Positioning System User Equipment for the external update function currently provided by TACAN. Another area where technology insertion may be deemed appropriate is the substitution of a strapdown inertial navigation unit (INU) employing ring laser gyros (RLG) for the currently employed conventional gimballed INU. The INU employed in the IINS is built to a form, fit and function specification, which will allow substitution of a RLG INU when such a unit is qualified and in production. The system hardware and software is structured so that these changes can be accomplished with a minimum of effort. The paper also describes the federated processing structure which allows this flexibility with particular attention to the inertial/TACAN update algorithm and data bus control functions. The paper concludes with a brief summary of the development status of the IINS, currently in full scale engineering development.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call