USPatent applicationPatented

Device, method and computer program product for altimetry system

Granted 24 Jun 2003 · 2 office actions

Life of the application

11 dated events
⤢ drag to zoom200020022004200620082010201220142016201820202022ProsecutionOwnershipTerm & fees
ProsecutionOwnershipTerm & feeshover for detail · click to open

Abstract

An apparatus, system, method and computer program product to verify proper operation of an aircraft altimetry system. Aural and visual alerts may optionally be provided when a fault in the altimetry is detected.

Description

8 parts
›CROSS-REFERENCES TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional Application No. 60/180,629 filed Feb. 3, 2000 titled: “Gillham Altitude Monitoring Algorithm.” which is incorporated herein by reference for all purposes. This application is additionally related to U.S. application Ser. No. 09/255,670, which is now U.S. Pat. No. 6,216,064, filed Feb. 23, 1999 and titled: “Method and Apparatus for Determining Altitude” which is also hereby incorporated by reference.

›BACKGROUND OF THE INVENTION

This invention relates to altimetry systems for aircraft and more particularly to encoding of altimetry data.

All aircraft carry an altimeter to sense aircraft altitude. In most modern aircraft, such equipment includes an encoding altimeter; a barometric altimeter coupled to an altimeter digitizer; and/or an air data computer. The altimetry data output from such devices is digitally encoded for use by other aircraft systems, including, for example: the aircraft transponder; traffic collision and avoidance system (TCAS); ground proximity warning systems (GPWS and EGPWS); flight data recorders; various navigation systems; and in some cases a cockpit display of pressure altitude.

Digital representation of the altimetry data is electronically accomplished through the use of Gray code. Unlike other number systems, in which more than one bit may change when the measured parameter increments in value, the Gray code is a number system designed such that only one bit changes at a time. For example, in the system of counting numbers, a change in value from 79 to 80 changes both the “7” to an “8” and the “9” to a “0.” Simultaneously changing the value of more than one bit increases the probability of an error in the encoding process. Such errors are reduced through the use of the Gray code. A particular form of Gray code, called Gillham code, is used in aviation to encode the altimetry data. Table 1 lists the Gillham code.

Errors in altimetry can also occur due to a blocked static port. Barometric altimeters sense changes in ambient air pressure and correlate these pressure changes to changes in altitude. Blockage of the static port disrupts the altimeter's source of pressure data, thereby introducing altimetry errors. Additional errors can also arise when the altitude sensing equipment has a fault that causes the data, or a bit in the digital representation of the data, to freeze at a certain value. Errors may also occur due to an altimeter malfunction that results in a completely erroneous determination of altitude.

Any errors in the altitude data used by aircraft systems may lead to hazardous conditions or catastrophic accidents. Air traffic controllers often maintain aircraft separation through use of vertical spacing. Without accurate altitude data as relayed by the aircraft transponder, the controller cannot be assured that aircraft are separated vertically. The TCAS system is a safety device that also seeks to prevent inadvertent collisions between aircraft by exchanging altitude data between aircraft in close proximity. Errors in the altitude data used by this system may exacerbate rather than mitigate the risk of collision.

Aircraft systems therefore utilize various systems to verify the accuracy of the altitude data. In many cases, a redundant altitude data source/computing system is used to independently calculate the altitude information. In the event the two calculations do not agree, this information is used to indicate a system fault. Use of redundant computations, however, slows processing time and increases the overall system cost through use of duplicative circuits and components. Furthermore, this redundancy reduces but does not necessarily eliminate errors. For example, a scenario can occur where neither altimeter calculation appears to be obviously in error, yet neither is in agreement with the other.

To reduce the expense associated with a completely duplicative system, in many aircraft configurations, a single Gillham encoder is used to encode the altimetry data, or a single source of raw altimetry data is provided to the redundant computing systems for encoding. Thus, if the single encoder or single raw data source suffers a fault, even the redundant computing systems may not detect the error. A Wall Street Journal article titled “Flawed Safety Device in Jets Causes a Near Miss,” published Oct. 20, 1999 documents one example of this latter type of failure.

Alternative means of measuring altitude do not completely solve the above identified problems. Use of radio altimetry measures height above ground and unlike pressure altitude data or data referenced to sea level, does not provide information relative to a reference in use among all participating aircraft. Use of satellite based navigation tools such as the global positioning system, GPS, provide only a partial solution. Reliable GPS navigation requires that a minimum number of operational satellites be visible. In addition, errors in GPS computed position have their greatest magnitude in the calculation of altitude.

›SUMMARY OF THE INVENTION

The present invention provides a system, apparatus, method and computer program product for enhancing the robustness of altimetry data using Gillham, or other Grey code encoding. In addition, the present invention provides a system, apparatus, method and computer program product for verifying the reasonableness of aircraft altimetry data and may optionally include an alert when the altimetry appears suspect.

According to one aspect of the invention, the invention compares two independent sources of altitude data to obtain two independent measures of altitude rate. In a preferred embodiment, the invention compares inputs from both the pneumatic altimetry data and the global positioning (GPS) altitude data. The altitude rate of change between the two sources is then compared and if the two values are not within a specified tolerance, a possible fault in the altimetry is indicated. The system faults detected by this aspect of the invention thus include a blocked static port, or “stuck” altitude source or encoder.

According to another aspect of the present invention, the invention verifies that the measure of pressure altitude as indicated by the altimetry system is a reasonable value. In a preferred embodiment, pressure altitude is compared with geometric altitude provided by an independent source, such as for example, GPS. An error budget is established to account for errors due to, for example, the known difference between pressure altitude and geometric altitude in the standard atmosphere, errors in GPS position measurement and deviations from standard atmospheric conditions. If the pressure altitude differs from the geometric altitude by an amount greater than this error budget, a possible fault is likely in the pressure altitude sensing/reporting system.

According to yet another embodiment of the present invention, the Gillham code is itself checked for errors. In one embodiment of the invention, the current Gillham value is compared to the last sampled Gillham value to ascertain if the Gillham bits have toggled between samples in an invalid sequence. The invention additionally checks for invalid bit values in certain code positions. The present invention is thus able to detect a fault in the Gillham logic such as a broken encoder, a stuck bit or faulty wiring connection.

According to another aspect of the invention, the invention alerts the cockpit crew of discrepancies in the altimetry data. The invention may also be used to signal other aircraft systems that the altimetry data is suspect. Systems requiring such data may then elect to disregard or otherwise process the altimetry data in accordance with the criticality of altitude data to the operation of that system.

Further features and advantages of the present invention will be described in greater detail below with reference to the drawings.

›BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a top level diagram illustrating operation of the present invention;

FIG. 2 is a transfer diagram for identifying an error in Gillham altitude transition according to a preferred embodiment of the present invention;

FIG. 3 is a transfer diagram for identifying an error in the rate of change in pressure altitude according to a preferred embodiment of the present invention;

FIG. 4 is a chart illustrating the spatial relationship between FIGS. 5A-5D;

FIGS. 5A-5D are top level diagrams illustrating a device for obtaining a geometric altitude according to a preferred embodiment of the present invention;

FIG. 6 is a transfer diagram for identifying an error in pressure altitude absolute altitude according to a preferred embodiment of the present invention; and

FIG. 7 is a block diagram of a GPWS system for hosting the present invention.

›DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS · 1 of 4

The present invention provides a system, method, apparatus and computer program product for detecting possible faults in the altimetry sensing and reporting systems, and is particularly useful for aircraft.

System Overview

FIG. 1 is top level diagram illustrating operation of a preferred embodiment of the present invention. A first portion 2 of FIG. 1 includes logic that asserts a signal when a probable error is detected in the altimetry data operations. According to a preferred embodiment of the invention, FIG. 1 optionally includes a second portion 4 that includes logic to drive an aural and/or visual alert. The alerting and annunciating functions of the present invention are optionally activated by the aircraft operator or flight crew via a signal 6 . Altitude monitor enable signal 6 may comprise a cockpit switch or a pin enable that is activated at time of installation.

When the altitude monitor of the present invention is enabled by signal 6 , the present invention asserts a signal if a possible error is detected in either the Gillham code transition, the pressure altitude rate of change, or in the pressure altitude measurement. According to one possible embodiment of the present invention, three independent logic circuits, to be described in detail below, ascertain if an error is possible in the Gillham code transition, the altitude rate of change and the pressure altitude measurement respectively. If any of these logic circuits detect a possible error in the aforementioned parameters, the appropriate circuit asserts a signal on one of lines 12 , 14 or 16 . When the present invention is enabled by signal 6 , the presence of an asserted signal on any of lines 12 , 14 and 16 will cause the output 18 of logical OR 19 to be asserted, thereby indicating a possible fault in the altitude data supplied to the aircraft systems.

Logic circuit 2 further includes logic that outputs a signal to indicate that the altimetry data appears valid. Logical AND function 30 receives the inverted output 32 of OR function 19 , and the pressure altitude input valid signal 34 . Pressure altitude input valid signal 34 comprises a signal currently available on the aircraft and output by the encoding altimeter, air data computer, or altitude digitizer as appropriate that indicates that the respective equipment is powered on and has satisfactorily performed all self checks. Signal 32 comprises the output of inverter 36 , which inverts signal 18 output from OR function 19 . Signal 32 is asserted whenever each of signals 12 , 14 and 16 are deasserted and thus when asserted signal 32 indicates that no fault has been detected in the altimetry. When both signals 32 and 34 are asserted, the pressure altitude output by the altimetry system is therefore presumed valid, and AND function 30 asserts a pressure altitude valid signal 38 . Signal 38 is subsequently supplied to those aircraft systems that utilize altimetry in their operations. These systems can be programmed to cease operations requiring the altimetry, to otherwise process the altimetry or to execute some other action as appropriate to the task performed by that system.

In a preferred embodiment of the invention, signal 18 may be additionally coupled to annunciation circuit 4 . When signal 18 is asserted, annunciation circuit 4 provides notification to the crew of a possible altitude data fault. The annunciation may be either aural and/or visual and is preferably user configurable. In the embodiment of FIG. 1, the aural annunciation circuit includes an enable signal 40 which is input to a logical AND function 42 . Also coupled to AND gate 42 is the output 44 of an AND function 46 . AND gate 44 receives signal 18 and a second signal, 48 that indicates whether the aircraft is below 18,000 feet. According to the embodiment of FIG. 1, when the aircraft is both below 18,000 feet and an altimetry fault is indicated by signal 18 of circuit 2 , the output 48 of AND gate 44 is asserted thereby activating annunciation of the altimetry fault.

The use of AND gate 44 and signal 48 comprises an optional portion of the invention. The floor of class A controlled airspace begins at 18,000 feet. All aircraft in class A airspace must be on an instrument flight plan and carry certain specified equipment. Aircraft in class A airspace also set their altimeter reference to 29.92 inches of mercury regardless of the actual sea level pressure. Typically, general aviation aircraft do not fly at or above this altitude. For this reason, in certain general aviation aircraft applications, it may be desirable to enable the annunciation circuit only when the on board navigation systems indicate that the aircraft is below 18,000 feet. In the embodiment shown, this information is provided from the aircraft global positioning system as signal 48 . The comparison between the GPS altitude and the specified value of 18,000 feet may be modulated, or incorporate a hysteresis, to prevent oscillations about the 18,000 foot mark that alternatively activate and deactivate the annunciation system. Modulation in the manner described is well known to those of skill in the art.

In the embodiment of FIG. 1, the aural annunciation activates when circuit 2 asserts signal 18 , the aircraft is below 18,000 feet, and both the altitude monitor enable and aural alert enable signals are asserted. The aural announcement may comprise, for example, the phrase “Check Altitude.” or other acceptable voice alert stored in a WAV file or similar device as is known to those of skill in the art.

The AND gate 50 of FIG. 1 operates in a similar manner to AND gate 42 to activate a visual annunciation of a possible altitude data fault. As diagrammed in FIG. 2, AND gate 50 asserts a signal to activate the visual annunciation when circuit 2 asserts signal 18 , the aircraft is below 18,000 feet, and both the altitude monitor enable signal 6 and the visual alert enable signal 52 are asserted. The visual alert may comprise a cockpit lamp or a graphical or textual alert appearing on a cockpit display. In FIG. 1, a set of user configurable values 54 are stored in a memory device or display driver. These configurable parameters identify placement of the visual annunciation on a display 56 . The phrase “CHK ALT” appears in the upper left corner of example display 56 . Other appropriate phraseology may be used. The visual annunciation may optionally comprise a graphical symbol.

›DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS · 2 of 4

Displays and display drivers suitable for use with the present invention are located throughout the flight deck and avionics subsystems. The flight management system (FMS), weather radar, Enhanced Ground Proximity Warning System (EGPWS), Traffic Collision and Avoidance System (TCAS), and cockpit navigation displays are examples of systems which contain hardware/software useful for driving an associated cockpit display. Techniques for driving these displays to display the alerting graphics and text of the present invention are well known to those of skill in the art.

Gillham Altitude Transition Error Detection Logic

FIG. 2 contains a logic diagram illustrating a device and method for detecting errors in the Gillham altitude data and for asserting signal 12 of FIG. 1 . Specifically, the logic of FIG. 2 can detect when there exists a stuck bit in the Gillham encoder, or a broken wire lead, or faulty connection in the circuits supplying the Gillham altitude data.

One subsection, 201 , of FIG. 2 checks for stuck bits in the Gillham code. Region 201 of FIG. 3 receives the Gillham altitude value at input 204 . A comparator 206 compares the current Gillham altitude, signal A, with the last Gillham altitude value, B, which has been retained in the 1 sample delay latch 208 . For the condition when the current Gillham value, A, does not equal the previous value, B, stored in the latch, comparator 206 asserts a signal on line 210 . Signal 210 when asserted indicates that the altitude as reported by the Gillham code has changed.

A junction 212 obtains the difference between the current value A and previous value B. The difference value output from junction 212 is provided to an absolute value function 214 that ensures the reported difference, C, between the current and previous samples is always greater than zero. A second comparator circuit 216 compares this difference to a set of predefined error codes 218 . If the difference signal C equals one of the values D stored in table 218 , one bit of the Gillham code is likely in error due to either a stuck bit or other fault in the system electrical connection. Specifically, a 7900 foot difference between the present altitude as represented by Gillham encoded signal A and the previously encoded altitude, B, indicates that bit B 1 of the Gillham encoded altitude is in error. In a similar manner, a difference of 3900 feet indicates an error in bit B 2 of the code and a 1900 foot difference indicates an error in bit B 4 of the Gillham encoded altitude. When the difference signal C equals one of these error values, D; comparator 216 asserts an error signal 220 .

When the current and previously reported Gillham altitude have changed as indicated by signal 218 , and the difference between the codes indicates a bit error as indicated by error signal 220 , a fault in the Gillham reported data is likely. A logical AND function 222 asserts a signal 224 when these conditions exist and the Gillham circuit is operational. A Gillham altitude valid signal 226 indicates the operational status of the Gillham encoding circuit. In a preferred embodiment of the invention, signal 226 comprises a signal output from the Gillham encoder that indicates the encoder is receiving power and has satisfactorily performed all of its self checks.

The logic of FIG. 2 also checks for invalid bit patterns in the Gillham code. Bits C 1 , C 2 and C 4 should not, when read in sequence, equal the binary representations of the Arabic numbers 0, 5, or 7. In other words, the combination of bits 000, 101, and 111 should not appear in bit positions C 1 , C 2 and C 4 . Such a combination indicates an invalid Gillham encoded altitude has been output by the system. Block 230 of FIG. 2 reads these bit positions and asserts a signal 232 when these invalid bit patterns are detected.

When either an invalid bit pattern exists or circuit 201 indicates a stuck or faulty bit, logical OR function 236 asserts a signal indicating the presence of an error. The logic of FIG. 2 additionally includes, however, circuitry to minimize false alerts and ensure that an actual error has been detected. False alerts have been shown to reduce the likelihood that the crew will treat an actual alert as a true alert condition and thereby have the effect of counteracting the safety benefits the present invention. For this reason, region 240 of FIG. 2 includes a counter 242 and a comparator 246 that causes Gillham transition error signal 12 to be asserted only when an error condition is detected twice in sequence. In a preferred embodiment of the invention, the sample rate of FIG. 2 is 20 times per second. The exact sample rate chosen is not critical, but is preferably fast enough such that no more than a 100 foot increase in altitude is likely to occur in the sample period. A logical OR 248 may optionally be used to initialize or reset the counter. Logical OR function 248 resets counter 242 when the aircraft is airborne as indicated by INAIR signal 250 , at powerup as indicated by POWERUP signal 252 or optionally when the aircraft altitude exceeds 18,000 feet as indicated by signal 256 . Signal 250 may come from a weight on wheels sensor, a radio altitude signal indicating a predetermined height above ground, or an airspeed signal showing an airspeed in excess of a specified value.

Pressure Altitude Rate of Change Error Logic

FIG. 3 contains a logic diagram illustrating a device and method useful for detecting a condition in which changes in altitude are not reported. Such a condition can occur when the aircraft static port becomes blocked and/or the altitude encoder “freezes” and continues to output a single value.

In the diagram of FIG. 3, both the pressure altitude 300 as measured in feet and the geometric altitude 302 read from a global positioning unit or other non barometric altitude source are first processed by junctions 310 and 312 , and sample and hold devices 314 and 316 respectively to obtain a change in altitude rate value. In a preferred embodiment of the invention, the altitude rates are represented as feet per second. These altitude rate values are then filtered by filters 320 and 322 . Filters 320 and 322 introduce a lag into the altitude rate of change data to obtain a steady state value and to smooth out transient information. The specific time constant of 60 seconds chosen for filters 320 and 322 of FIG. 3 is but one of numerous possible values and the invention is not limited to the time constant as shown in FIG. 3 .

›DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS · 3 of 4

The filtered rate of change information is compared at junction 324 and the absolute value of the difference between the two rates taken by function generator 326 . If the absolute value of the difference, signal C, exceeds some predefined value, D, a comparator 328 asserts a signal 330 indicating a possible problem with the aircraft's altimetry. In the embodiment of FIG. 3, this predetermined value is shown as 20 feet per second, however, any value reasonably chosen to identify a significant discrepancy in the rate values obtained from the two sensors may be used. Preferably, this predetermined value also accounts for pneumatic lags in the collection of the barometric altitude data.

The logic of FIG. 3 also includes elements designed to prevent false alerts. The AND logic 332 only asserts a signal indicating an altitude rate of change error when various signals 334 indicate that the aircraft is airborne and the equipment used to sense altitude is operational. In FIG. 3, signals 334 include INAIR signal 250 and POWERUP signal 252 previously described. Signals 334 additionally include a Pressure Altitude Input Valid signal 336 and a Geometric Altitude High Integrity signal 338 . Signals 336 and 338 are signals to indicate that the sensors used to sense altitude are functioning. Signal 336 may comprise a signal from, for example, the air data computer, or the encoding altimeter, that indicates that the system is powered and performed its self checks. Signal 338 is a signal to indicate integrity of the global positioning system altitude signal when a global positioning unit supplies altitude data to junction 312 . Signal 338 , however, may comprise any other appropriate signal to indicate that the associated sensor is active. Signal 338 may, for example, comprise a signal indicating the sensor is powered and performed self checks.

Geometric Altitude High Integrity signal 338 of the present embodiment, however, is obtained from a separate logic application designed to accurately fix geometric altitude using both barometric and global positioning system inputs. Such a system is fully described in copending U.S. application Ser. No. 09/255,670 titled: “Method and Apparatus for Determining Altitude,” filed Feb. 23, 1999 and incorporated herein by reference. FIGS. 4 and 5 A- 5 D collectively depict a block diagram of a geometric altitude measurement system.

The geometric altitude determination of FIGS. 4 and 5 A- 5 D preferably uses a first altitude 380 based on hydrostatic calculations, including local pressure and temperature, as well as a second altitude 385 which is preferably a GPS altitude. Radio altimetry 387 can also be used instead of, or to complement the GPS altitude. Other sources of altitude data, for example barometric altitude data 390 , can be used in the equation for the calculation of the final altitude when available. Each of the sources of altitude data is provided with an estimated error. In the final determination of the probable geometric altitude, each source of altitude data is weighted according to the estimated error of the altitude source. For global positioning altitude, the final combination of the altitude sources uses a complementary filter which takes into account the selective availability of the GPS altitude. This filter accounts for the long-term accuracy but short-term inaccuracy of GPS altitude. Corrections may be additionally provided to account for horizontal changes in pressure gradient as the aircraft moves through weather patterns between origin and destination as well as corrections based on non-standard atmospheric temperature variations.

The blended geometric altitude provided by the system of FIGS. 4-5 may be compared with the GPS altitude or other geometric altitude source input to FIG. 3 . If the compared values are within reasonable agreement, the geometric altitude input of FIG. 3 may be assumed valid as indicated by signal 338 and the altitude checks performed by the logic of FIG. 3 may be reasonably relied upon.

A track hold device 345 is additionally provided in FIG. 3 to further reduce nuisance alerts. Track hold device 345 ensures that any signal output by AND function 332 remains in either the asserted or deasserted state for at least 15 seconds before changing the status of Pressure Altitude rate of change error signal 14 . Track hold device 345 thus inhibits the toggling of annunciation circuit 4 until a steady state condition is established.

Pressure Altitude Absolute Error Logic

The pressure altitude absolute error logic of FIG. 6 examines the difference between pressure altitude, and geometric altitude as measured by another source. Geometric altitude corresponds to the true “tape measure” altitude above sea level. Pressure altitude corresponds to what the barometric altimeter reads when the sea level reference barometric pressure is set to 29.92 inches of mercury. A standard model of the atmosphere exists in which the changes in pressure, temperature and density are described as a function of height above sea level. The standard sea level pressure assumed by the model is 29.92 inches of mercury. Therefore, on a day when the actual air conditions approximate the values assumed in the standard model atmosphere, the pressure altitude will equal the geometric altitude. On days where conditions deviate from standard, the error between pressure altitude geometric altitude can be computed or at least bounded. The present invention makes use of these properties to check whether the pressure altitude as measured by the aircraft pneumatic systems is within reasonable limits of the geometric altitude, as measured by an independent sensor. In a preferred embodiment of the invention, this independent sensor comprises a global positioning device.

In the logic diagram of FIG. 6, pressure altitude is compared to one of a runway calibrated altitude 412 or GPS altitude 302 . Runway calibrated altitude 412 may be obtained from a terrain data base such as that used with, for example, an Enhanced Ground Proximity Warning System. Optionally, runway calibrated altitude 412 is a conditioned value obtained using the “Method and Apparatus for Determining Altitude” as described in the aforesaid patent application. Use of runway calibrated altitude 412 when the aircraft is not airborne is optional. The GPS altitude 302 may be used for all cases.

›DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS · 4 of 4

When available, use of runway calibrated altitude 412 and GPS altitude 302 when airborne is toggled by a switch 416 . Switch 416 is toggled by a logical AND function which asserts a signal when both INAIR signal 250 indicates the aircraft is on the ground and when signal 420 indicates the system for calibrating the runway altitude is operational. When the aircraft is airborne, AND function 418 is deasserted and switch 416 toggles to the lower position, thereby coupling GPS altitude signal 302 to junction 430 . Junction 430 obtains the difference between the geometric altitude as measured by GPS signal 302 or runway altitude signal 412 and the pressure altitude 300 . Function generator 432 obtains the absolute value of this difference and outputs this value as signal C on line 433 .

The geometric altitude value switched at switch 416 is additionally provided to a second function generator 440 . Function generator 440 models the theoretical difference 441 between pressure altitude and geometric altitude as a function of the observed geometric altitude. For example, according to the function graphed in function generator 440 , a probable error of 6400 feet exists in the pressure altitude measurement when the geometric altitude measurement reads 6000 feet. The difference signal 441 is multiplied by a gain 442 to obtain an AERROR estimate signal. In the embodiment of FIG. 6, gain 442 equals 2. The gain chosen may be any value, however, the gain is preferably chosen to provide a tolerance value, or confidence margin in the error, such that one may be assured that the maximum error would reasonably fall within the value represented by signal AERROR.

A figure of merit value, or FOM, value is also switched according to AND function 418 . The FOM value is an estimate of the error associated with the sensor used to sense geometric altitude. The particular FOM latched by the switch 450 depends upon whether the aircraft is airborne as explained above in connection with the operation of AND function 418 . Most GPS units in use today provide a FOM value directly. If the runway calibrated altitude is used, the FOM may be provided by that system in the manner described in U.S. patent application Ser. No. 09/255,670. The FOM value latched by switch 450 is also multiplied by a gain 452 to obtain a geometric error signal GERROR.

A third source of error may occur if the actual sea level pressure differs significantly from standard. Such conditions occur infrequently, but have been known to result in serious altimetry errors. The possibility of such an error being present is accounted for by box 458 of FIG. 6 . It is unlikely that an extreme deviation from standard pressure would result in an error of more than 1000 feet. For this reason, box 458 includes a constant, K, equal to 1000 feet, and which represents the error due to extreme deviations from standard pressure, PERROR. Other values for the constant K may be chosen while still keeping with the principles of the present invention.

Each of the three possible errors: AERROR, GERROR and PERROR are input to a third function generator 460 . Generator 460 takes the square root of the sum of the squares (RSS) of the three error values to obtain a probable error budget value, signal D. The RSS method of quantifying errors is well known to those of skill in the art. Other techniques, also known to those of skill in the art may also be used.

The amount of acceptable error in the discrepancy between the pressure altitude and geometric altitude measurements is therefore represented by signal D. Signal D is then compared with signal C which represents the actual difference between the two measures. If signal C exceeds the error budget represented by signal D, comparator 462 asserts a signal 464 to indicate a possible error in the pressure altitude measurement.

Signal 464 is supplied to an AND function 468 , which operates in a manner similar to AND function 332 of FIG. 3 . Thus, AND function 468 will assert a signal 470 indicating a possible pressure altitude error when the sensors have been powered for a sufficient time so as to be thermally stable and both the geometric altitude sensor system and pressure altitude sensor appear to be operational.

To prevent nuisance alerts, the logic diagrammed in FIG. 6 also includes a track hold device 472 . Track hold device 472 ensures that signal 470 output by AND function 468 remains either deasserted or asserted for at least 15 seconds before changing the status of pressure altitude absolute error signal 16 .

Implementation

The invention as herein described may be implemented in a variety of fashions. For example, the invention may be implemented as a sequence of computer program instructions or in firmware as electronic microcircuitry. In a preferred embodiment, the invention is hosted on a device having a general purpose processor. Such an implementation saves weight and power. Numerous aircraft systems contain a processor and receive those inputs, or can be readily wired to receive, those inputs used by the present invention. The aircraft flight management system (FMS), the TCAS, and the transponder are examples of existing aircraft systems on which the present invention may be hosted. In a preferred embodiment of the invention, the aircraft EGPWS is used to host the present invention and to drive the alerting display and aural alerts. FIG. 7 illustrates an embodiment in which an EGPWS 700 hosts the present invention and drives a display 56 . Display 56 may be the combination terrain awareness/weather radar/TCAS display typically coupled to the EGPWS device. Optionally display 56 may comprise any other available cockpit display.

Preferred embodiments of the invention have now been described. Variations and modifications will be readily apparent to those of skill in the art. The invention is therefore to be interpreted in light of the claims.

›Tables in the description — 1
TABLE 1 — Gillham Grey Code Chart
AttitudeD4A1A2A4B1B2B4C1C2C4
−10000000000010
−9000000000110
−8000000000100
−7000000001100
−6000000001110
−5000000001010
−4000000001011
−3000000001001
−2000000011001
−1000000011011
00000011010
1000000011110
2000000011100
3000000010100
4000000010110
5000000010010
6000000010011
7000000010001
8000000110001
9000000110011
10000000110010
11000000110110
12000000110100
13000000111100
14000000111110
15000000111010
16000000111011
17000000111001
18000000101001
19000000101011
20000000101010
21000000101110
22000000101100
23000000100100
24000000100110
25000000100010
26000000100011
27000000100001
28000001100001
29000001100011
30000001100010
31000001100110
32000001100100
33000001101100
34000001101110
35000001101010
36000001101011
37000001101001
38000001111001
39000001111011
40000001111010
41000001111110
42000001111100
43000001110100
44000001110110
45000001110010
46000001110011
47000001110001
48000001010001
49000001010011
50000001010010
51000001010110
52000001010100
53000001011100
54000001011110
55000001011010
56000001011011
57000001011001
58000001001001
59000001001011
60000001001010
61000001001110
62000001001100
63000001000100
64000001000110
65000001000010
66000001000011
67000001000001
68000011000001
69000011000011
70000011000010
71000011000110
72000011000100
73000011001100
74000011001110
75000011001010
76000011001011
77000011001001
78000011011001
79000011011011
80000011011010
81000011011110
82000011011100
83000011010100
84000011010110
85000011010010
86000011010011
87000011010001
88000011110001
89000011110011
90000011110010
91000011110110
92000011110100
93000011111100
94000011111110
95000011111010
96000011111011
97000011111001
98000011101001
99000011101011
100000011101010
101000011101110
102000011101100
103000011100100
104000011100110
105000011100010
106000011100011
107000011100001
108000010100001
109000010100011
110000010100010
111000010100110
112000010100100
113000010101100
114000010101110
115000010101010
116000010101011
117000010101001
118000010111001
119000010111011
120000010111010
121000010111110
122000010111100
123000010110100
124000010110110
125000010110010
126000010110011
127000010110001
128000010010001
129000010010011
130000010010010
131000010010110
132000010010100
133000010011100
134000010011110
135000010011010
136000010011011
137000010011001
138000010001001
139000010001011
140000010001010
141000010001110
142000010001100
143000010000100
144000010000110
145000010000010
146000010000011
147000010000001
148000110000001
149000110000011
150000110000010
151000110000110
152000110000100
153000110001100
154000110001110
155000110001010
156000110001011
157000110001001
158000110011001
159000110011011
160000110011010
161000110011110
162000110011100
163000110010100
164000110010110
165000110010010
166000110010011
167000110010001
168000110110001
169000110110011
170000110110010
171000110110110
172000110110100
173000110111100
174000110111110
175000110111010
176000110111011
177000110111001
178000110101001
179000110101011
180000110101010
181000110101110
182000110101100
183000110100100
184000110100110
185000110100010
186000110100011
187000110100001
188000111100001
189000111100011
190000111100010
191000111100110
192000111100100
193000111101100
194000111101110
195000111101010
196000111101011
197000111101001
198000111111001
199000111111011
200000111111010
201000111111110
202000111111100
203000111110100
204000111110110
205000111110010
206000111110011
207000111110001
208000111010001
209000111010011
210000111010010
211000111010110
212000111010100
213000111011100
214000111011110
215000111011010
216000111011011
217000111011001
218000111001001
219000111001011
220000111001010
221000111001110
222000111001100
223000111000100
224000111000110
225000111000010
226000111000011
227000111000001
228000101000001
229000101000011
230000101000010
231000101000110
232000101000100
233000101001100
234000101001110
235000101001010
236000101001011
237000101001001
238000101011001
239000101011011
240000101011010
241000101011110
242000101011100
243000101010100
244000101010110
245000101010010
246000101010011
247000101010001
248000101110001
249000101110011
250000101110010
251000101110110
252000101110100
253000101111100
254000101111110
255000101111010
256000101111011
257000101111001
258000101101001
259000101101011
260000101101010
261000101101110
262000101101100
262000101100100
264000101100110
265000101100010
266000101100011
267000101100001
268000100100001
269000100100011
270000100100010
271000100100110
272000100100100
273000100101100
274000100101110
275000100101010
276000100101011
277000100101001
278000100111001
279000100111011
280000100111010
281000100111110
282000100111100
283000100110100
284000100110110
285000100110010
286000100110011
287000100110001
288000100010001
289000100010011
290000100010010
291000100010110
292000100010100
293000100011100
294000100011110
295000100011010
296000100011011
297000100011001
298000100001001
299000100001011
300000100001010
301000100001110
302000100001100
303000100000100
304000100000110
305000100000010
306000100000011
307000100000001
308001100000001
309001100000011
310001100000010
311001100000110
312001100000100
313001100001100
314001100001110
315001100001010
316001100001011
317001100001001
318001100011001
319001100011011
320001100011010
321001100011110
322001100011100
323001100010100
324001100010110
325001100010010
326001100010011
327001100010001
328001100110001
329001100110011
330001100110010
331001100110110
332001100110100
333001100111100
334001100111110
335001100111010
336001100111011
337001100111001
338001100101001
339001100101011
340001100101010
341001100101110
342001100101100
343001100100100
344001100100110
345001100100010
346001100100011
347001100100001
348001101100001
349001101100011
350001101100010

Claims as granted

76 claims

Log in to read the claims of this application.

Log in to unlock

Classifications

10 codes
IPC · International Patent Classification
Section G — Physics
  • G01C25/00
  • G01C5/00
USPC · US Patent Classification
701/4701/4701/301340/963342/462340/945340/977340/961

Claim changes

Soon
Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this application are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoomJan 2001Apr 2001Jul 2001Oct 2001Jan 2002Apr 2002Jul 2002Oct 2002Jan 2003Apr 2003Jul 2003USPTOApplicantNon-final rejectionResponse after non-finalNon-final rejectionResponse after non-finalNotice of allowance
USPTOApplicanthover for detail · click to open
Pendency
2.4 y
872 days filing → grant
Office actions
2
non-final + final
Responses
2
no RCE
Examiner
Thomas G. Black
art unit 3663 · TC 3600
Citations: 20 back · 14 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Documents

Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.

Log in to unlock

Chain of title

⤢ drag to zoom2002200420062008201020122014201620182020Owner 1
Titlehover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.

Log in to unlock