Laserfiche WebLink
<br />1.2 <br /> <br />When the inertial platform software and the interfaces between the <br />computer and the pressure transducer, plotter and the SF6 analyzer were <br />completed they were then installed in the aircraft. The equipment began <br />operation with a flight on 25 March 1985. All the devices operated and we <br />were able to detect SF6. Various software changes were then added to the <br />computer to make the graphical output clearer. The aircraft operated well, <br />with the expected minor problems. <br /> <br />The data system was driven by an Intel iSBC 86/330A microprocessor with <br />a 35 Mbyte Winchester disk and an 88/40 secondary computer board. This sys- <br />tem was interfaced with an inertial platform (or IMU, inertial measurement <br />unit). The hardware and software were originally an inertial navigation <br />system developed for the NASA Doppler Lidar project. The IMU data included <br />. longitude, latitude, heading of the aircraft, pitch, roll and drift angles. <br />The IMU data were computed by the program GYRO. ~RO is the central part <br />of the software for the data system. Its primary function is to compute <br />positions, keep the platform level at all times and to calibrate the plat- <br />form's performance. The IMU data are then sent to the graphics program to <br />be plotted. The graphics program also receives data from a pressure tran- <br />ducer and the SF6 instrument. It then plots data on the Zeta plotter in <br />a fixed format. <br /> <br />The data transmission from the instruments and Zeta plotter was handled <br />by a direct memory access controller and it was scheduled by the MANAGER <br />program. MANAGER takes plotter commands from a specially-modified version <br />of the Zeta library and sends them to the plotter as the plotter can accom- <br />moda te them. <br /> <br />The plotter, the pressure transducer and the SF6 instrument are on a <br />daisy chain connected by optical fiber cable. Each is activated when it <br />recognizes its number in a transmitted byte. <br /> <br />A heavy demand was placed on the data system because of the need to <br />service the inertial platform every 0.1 seconds. Consequently, all tasks <br />had to be squeezed in this narrow time interval and some had to be segmented. <br />The iRMX86 operating system of the Intel computer had proved to be too slow <br />to use with the inertial platform. During the operation of the navigation <br />program iRMX86 was disabled and hand-coded device drivers were used. Thus <br />the program had to schedule its own operations. Also, some of the plotter <br />routines had to be rewritten so that they could be interleaved with the <br />navigation program without affecting its rate of 10 Hz. <br /> <br />The tasks in the 1985 data system were: <br /> <br />1. servicing the platform and getting the IMU data: <br />2. obtaining data from the instruments: <br />3. plotting positions and instrument data: and <br />4 displaying position and instrument data on CRT (terminal <br />screen) every 10 seconds and printing data every 30 seconds. <br /> <br />I <br />I <br /> <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />I <br />