This invention relates to diagnostic systems for equipment service vehicles. In particular, this invention relates to an on-board diagnostic system for equipment service vehicles.
Modern vehicles have become increasingly complex and difficult to maintain. In order to enable more efficient vehicle maintenance, it is desirable to be able to accurately diagnose malfunctioning subsystems, such as engine systems, transmission systems, and so on, as well as specific vehicle components. When a malfunction is not properly diagnosed, the result is typically that parts which are fully operational are repaired or replaced, that parts which are repairable are replaced, and/or that parts which are not fully operational are not repaired or replaced. Accurate diagnoses therefore allow more efficient vehicle maintenance by avoiding unnecessary repairs and replacements, and by enabling necessary repairs and replacements to be made.
It is known to provide electronic diagnostic systems to aid in the accurate diagnoses of vehicle malfunctions. Government Report No. CR-82-588-003, entitled “STE/ICE-R Design Guide For Vehicle Diagnostic Connector Assemblies,” February 1988, describes a diagnostic system used in connection with military vehicles. According to the approach described in this document, a military vehicle is provided with numerous sensors that are located throughout the vehicle and each of which obtains information pertaining to the health and operation of a subsystem of the vehicle. The sensors are used to measure typical parameters of interest such as engine RPM, engine temperature, fuel pressure, and so on. The sensors are connected by way of vehicle wiring to a common connector assembly. Diagnostic equipment provided at a maintenance depot is then capable of connecting to the various sensors by way of the connector assembly. At the maintenance depot, the diagnostic equipment can be utilized to perform tests on the vehicle to aid pinpointing the source of vehicle system malfunction.
In this arrangement, the sensors that are used by the diagnostic system are used exclusively by the diagnostic equipment at the maintenance depot, and not by other systems during normal operation of the vehicle. Additionally, in this arrangement, the connector assembly defines a hardwired analog interface between the sensors and the diagnostic equipment, and the diagnostic equipment expects signals appearing at given pins of the connector assembly to have predefined signal characteristics that are unique to the sensor utilized.
This approach suffers several disadvantages. First, this approach is expensive to implement because it requires numerous sensors above and beyond those required for normal operation of the vehicle. Additionally, the required sensors typically have unique signal characteristics that are specifically matched to the diagnostic equipment, and therefore the sensors are specialty items that are more expensive and not commonly available.
Second, this approach results in a diagnostic system with an unduly limited capability to accurately diagnose system faults. The capabilities of the diagnostic system are limited by the fact that the diagnostic system only utilizes information that is available from the diagnostic system sensors and not from other sources of information available on-board the vehicle. Therefore, the number of different types of information that can be obtained is limited to the number of diagnostic system sensors utilized. Further, because the sensors that are utilized tend to be specialty items as previously noted, they often do not incorporate the latest advances in sensor technology that provide performance/durability improvements over earlier sensor technologies. This further limits the accuracy of the diagnostic system as compared to that which could otherwise be achieved.
Finally, this approach is unduly cumbersome to utilize. As previously noted, the diagnostic equipment is provided at a maintenance depot and not on-board the vehicle. Therefore, in order to have a vehicle malfunction diagnosed, the vehicle must be brought to the maintenance depot. This requirement is inconvenient and limits the potential for field servicing of vehicles to minimize the amount of time that the vehicle is out of service for maintenance reasons.
According to a first preferred embodiment, an equipment service vehicle comprises a network communication link, a plurality of vehicle subsystems, a test control module, and an operator interface. Each vehicle subsystem comprises a mechanical system and an electronic control system that controls the mechanical system. Each respective electronic control system is connected to the network communication link and transmits information pertaining to the health and operation of the mechanical system on the network communication link. The test control module is mounted on board the vehicle and is coupled to the plurality of vehicle subsystems by way of the network communication link. The test control module is programmed to acquire at least some of the information pertaining to the health and operation of the mechanical system. The operator interface is mounted on board the vehicle and is coupled to the test control module. The operator interface comprises a display that displays a menu of test options to an operator and an input device that receives an operator input indicative of a menu selection made by the operator. The menu selection indicates a test selected by the operator. At least some of the information pertaining to the health and operation of the mechanical system, including results of the test, are displayed to the operator.
According to a second preferred embodiment, a method of diagnosing a fault on an equipment service vehicle is provided. The method comprises displaying a plurality of test options to an operator using an operator interface that is mounted on the vehicle. The method also comprises receiving an operator input using the operator interface, the input being indicative of a selection made by the operator and indicating a test selected by the operator. The method also comprises performing the selected test on the vehicle in response to the operator input, including communicating information pertaining to the health and operation of a vehicle subsystem from a control system for the vehicle subsystem to the operator interface by way of a network communication link. The method also comprises transmitting information pertaining to health and operation of a vehicle subsystem from an electronic control system for the subsystem to the operator interface by way of a network communication link. The method also comprises displaying results of the test to the operator using the operator interface.
It should be understood that the detailed description and specific examples, while indicating preferred embodiments of the present invention, are given by way of illustration and not limitation. Many modifications and changes within the scope of the present invention may be made without departing from the spirit thereof, and the invention includes all such modifications.
Referring now to
More specifically, the vehicle 10 is a military vehicle and, in particular, a medium tactical vehicle. However, it should be understood that the diagnostic system 12 of
The intelligent display module 14 provides an operator interface to the diagnostic system 12 and also provides intelligence used to conduct diagnostic tests and other services. In particular, the intelligent display module 14 includes a test control module 15 (which further includes a microprocessor 16 and a diagnostic program 17) and an operator interface 18 (which further includes a display 19 and a keypad 20) (see
In the preferred embodiment, the test control module 15 and the operator interface 18 are provided as a single, integrated unit (namely, the intelligent display module 14) and share the same housing as well as at least some of the internal electronics. Other arrangements are possible, however. For example, as can be easily imagined, it would also be possible to provide the test control module 15 and the operator interface 18 in the form of separate physical units, although this arrangement is not preferred for reasons of increased cost and parts count. Both the test control module 15 and the operator interface 18 can be obtained in the form of a single, integrated unit from Advanced Technology, Inc., Elkhart, Ind. 46517. This product provides a generic flat panel 4 line×20 character display 19, four button keypad 20, microprocessor 16, and memory that is capable of being programmed with a program (such as the diagnostic program 17) to customize the intelligent display module for a particular application. Of course, a more (or less) elaborate intelligent display module could also be utilized.
Also in the preferred embodiment, the intelligent display module 14 is semi-permanently mounted within the vehicle 10. By semi-permanently mounted, it is meant that the intelligent display module 14 is mounted within the vehicle 10 in a manner that is sufficiently rugged to withstand normal operation of the vehicle for extended periods of time (at least days or weeks) and still remain operational. However, that is not to say that the intelligent display module 14 is mounted such that it can never be removed (e.g., for servicing of the intelligent display module) without significantly degrading the structural integrity of the mounting structure employed to mount the intelligent display module 14 to the remainder of the vehicle 10. The intelligent display module 14 is preferably mounted in an operator compartment of the vehicle 10, for example, in a storage compartment within the operator compartment or on an operator panel provided on the dashboard.
The operation of the test control module 15, and in particular of the microprocessor 16 to execute the diagnostic program 17, is shown and described in greater detail below in conjunction with the flow chart of
The operator interface 18 includes the display 19 which is used to communicate (and, in particular, to display) information to the operator. For example, the display 19 is used to prompt the operator to enter information into the keypad 20, or to take certain actions with respect to the vehicle during testing (e.g., bring the engine to a specified RPM level). The display 19 is also used to display a menu or series of menus to allow the operator to select a test to be performed or to select another service of the intelligent display module 14 to be utilized. The display 19 is also used to display status information during system startup and during testing, and to display any error messages that arise during system startup or during testing. The display 19 is also used to display input data and fault mode indicators from control systems 24–30, and any other information from additional vehicle subsystems. The display 19 is also used to display information from discrete sensors such as the sensors 22. The display 19 is also used to display the results of diagnostic tests that are performed (e.g., a pass/fail message or other message).
Preferably, the display 19 displays all of this information to the operator in a user-friendly format as opposed to in the form of codes that must be interpreted by reference to a separate test or service manual. This is achieved in straightforward fashion by storing in the memory of the intelligent display module 14 information of the type commonly published in such manuals to facilitate manual interpretation of such codes, and using this information to perform the translation automatically. Likewise, as previously noted, the display 19 is used to prompt the operator to take certain actions with respect to the vehicle during testing and to otherwise step the operator through any test procedures, without reference to a test manual. This allows the amount of operator training to be reduced.
The operator interface 18 also includes the keypad 20 which is used to accept or receive operator inputs. For example, the keypad 20 is used to allow the user to scroll through and otherwise navigate menus displayed by the display 19 (e.g., menus of possible tests to be performed on the vehicle 20), and to select menu items from those menus.
As previously noted, it would also be possible to utilize a more elaborate intelligent display module. For example, a more elaborate keypad 20 could be utilized if more data entry capability is desired. In this regard, however, it is noted that the intelligent display module 14 also preferably includes a communication port that allows the display module to communicate with a personal computer 33 by way of a communication link 36 (see
The test interface module 21 accepts requests from the intelligent display module 14 for information from the sensors 22, retrieves the requested information from the respective sensor 22, converts input signals from the respective sensor 22 into a format that is compatible with the network communication link 32, and transmits the information from the respective sensor 22 to the intelligent display module 14 via the network communication link 32. The test interface module 21 is therefore preferably implemented as a passive unit with no standard broadcasts that burden the communication link 32. As a result, in operation, the test interface module 21 does not regularly transmit data on the network communication link 32. Rather, the test interface module 21 passively monitors the network communication link 32 for information requests directed to the interface module 21. When an information request is received, the test interface module 21 obtains the requested information from the relevant sensor 22, and then transmits the requested information on the network communication link 32 to the intelligent display module 14.
The test interface module 21 may, for example, include as many inputs as there are sensors 22. Each input may include associated switches for configuring the input, an analog-to-digital converter to convert analog signals to a digital format, and any other signal processing circuitry. The number of inputs is not important, since it is possible to use fewer test interface modules each with a larger number of inputs, or more test interface modules each with a smaller number of inputs. The number of inputs is not limited in any particular way and is determined by need.
In practice, the test interface module 21 may be a commercially available unit capable of putting information from discrete sensors onto a network communication link such as SAE (Society of Automotive Engineers) J1708. The test interface module 21 preferably also meets applicable standards for underhood installation, such as SAE J1455, to allow the test interface module to be located in close proximity to the sensors 22 to reduce wiring. The test interface module may, for example, be obtained from Advanced Technology Inc., Elkhart, Ind. 46517 (PN 3246282). Again, however, a wide range of devices of varying construction and complexity could be utilized to implement the test interface module 21.
The test interface module 21 is connected to the plurality of sensors 22 which are each capable of obtaining information pertaining to the health and operation of a vehicle subsystem. “Health” and “operation” are interrelated and information that pertains to one will, at least to some extent, pertain to the other as well. The sensors 22 are discrete sensors in the sense that they are not integrally provided with the control systems 24–30 and associated controlled mechanical systems (e.g., engine, transmission, and so on) 34–40. The sensors are add-on devices that are used only in connection with the intelligent display module 14. In general, discrete sensors are preferably only used when the information provided by the sensor is not otherwise available on the network communication link 32. In
In addition to the intelligent display module 14 and the test interface module 21, the diagnostic system 12 also includes a plurality of additional vehicle control systems 24–30, as previously noted. As shown in
The control systems 24–30 each store information pertaining to the health and operation of a respective controlled system. The control systems 24–30 are capable of being queried and, in response, making the requested information available on the network communication link 32. Because the vast amount of information required for performing most diagnostic tests of interest is available from the control systems 24–30 by way of the network communication link 32, it is possible to drastically reduce the number of discrete sensors 22 that are required. Thus, as just noted, discrete sensors are preferably only used when the information provided by the sensor is not otherwise available on the network communication link 32.
Typically, each of the control systems 24–30 comprises a microprocessor-based electronic control unit (ECU) that is connected to the network communication link 32. When the intelligent display module 14 requires status information pertaining to one of the mechanical systems 34–40, the intelligent display module 14 issues a request for the information to the respective one of the control systems 24–30. The respective control system then responds by making the requested information available on the network communication link 32.
Typical ECUs for transmission and engine control systems are capable of producing fault codes and transmitting the fault codes on the network communication link 32. Depending on the type of fault, the fault codes may be transmitted automatically or alternative only in response to a specific request for fault information. Typical ECUs for central tire inflation systems and anti-lock brake systems also transmit fault codes but, in most commercially available systems, fault codes are transmitted only in response to specific requests for fault information. When a fault code is transmitted on the network communication link 32, the intelligent display module 14 receives the fault codes from the network communication link 32, interprets the fault codes, and displays the interpreted fault codes to a human operator using the display 19.
Referring now to
Referring now to
In general, the specific diagnostic tests that are performed will be selected depending on the application, including the type of equipment utilized by the vehicle 10. Most or all tests may be simple in nature from a data acquisition standpoint, involving primarily bringing the vehicle to a particular operating condition (e.g., engine speed), if necessary, and obtaining information from a suitable transducer constructed and placed to measure the parameter of interest, although more elaborate tests could also be utilized. Any number of different vehicle parameters can be measured, each providing a separate data point regarding the operational health of the vehicle. By providing an operator with enough data points regarding the operational health of the vehicle, the operator can use this information in a known way to determine whether the vehicle is in good working order, or whether some subsystem or component thereof needs to be repaired or replaced.
At step 102, once the vehicle diagnostic option is selected, the display 19 displays a menu of various tests that are available to the operator, and the operator is prompted to select a test from the test menu. Again, the list of options may comprise dozens of options, such as some or all of those listed above, and/or tests other than those listed above, and the operator can scroll through the menu and selected the desired option.
At Step 104, the operator is prompted to perform a vehicle related action. This step, which may or may not be necessary depending on the type of test performed, may be used to prompt the operator to start the engine to develop fuel pressure, oil pressure, and so on, depending on which vehicle parameter is tested. For example, if it is desired to test the operational health of the battery, then the operator may be prompted to engage the starter for a predetermined amount of time to establish a current draw on the battery.
At Step 106, the intelligent display module 14 issues a request for information from the test interface module 21 and/or from one or more of the control systems 24–30. As previously noted, the test interface module 21 does not continually broadcast information on the network communication link 32, because the sensors 22 connected to the test interface module are used only for diagnostic testing and because presumably diagnostic testing will be performed only infrequently. Therefore, when the intelligent display module 14 needs information from one of the sensors 22 pursuant to a test requested to be performed by the operator at the operator interface 18, the intelligent display module 14 requests the test interface module 21 for this information.
Alternatively, the needed information may be of a type that is available from one of the control systems 24–30. The control systems 24–30 are not only able to acquire information from sensors located within the systems 34–40, but are also able to maintain information derived from sensors located within the systems 34–40. For example, the engine control system 30 may maintain information pertaining to the average RPM of the engine, which is a parameter that is not directly measurable but that can be easily calculated based on parameters that are directly measurable. Through the network communication link 32, all of this information is made available to the diagnostic system 12. When the intelligent display module 14 needs information from one of the control systems 24–30 pursuant to a test requested to be performed by the operator at the operator interface 18, the intelligent display module 14 requests the respective control system for this information.
At Step 108, the requested information is retrieved from one of the sensors 22 by the test interface module 21, or from memory or an internal sensor by the respective control system 24–30. At step 109, the information is transmitted from the test interface module 21 or from one of the control systems 24–30 to the intelligent display module 14 by way of the network communication link 32.
At step 112, the input status information is processed at the intelligent display module 14. For example, if fuel supply pressure is measured by one of the sensors 22, then the measured fuel supply pressure may be compared with upper and lower benchmark values to determine whether the fuel pressure is at an acceptable level, or whether it is too high or too low. Finally, at step 114, the results of the test are displayed to the operator.
As has been previously noted, in addition to performing diagnostic tests, the intelligent display module 14 can also be used to provide other services to an operator. For example, the intelligent display module 14 can be used to allow the operator to view engine codes, to view transmission codes, to view ABS codes, and to view CTIS codes. In practice, these services can be implemented simply by allowing acquiring the respective codes from the respective control system 24–30, and displaying the codes to the operator. Additionally, the control systems 24–30 may automatically transmit fault information on the network communication link 32, and the intelligent display module 14 can listen for such fault information and display the fault information to the user when it appears on the network communication link 32.
The intelligent display module 14 also includes sufficient memory to allow maintenance information to be stored therein to implement maintenance jacket functionality. The maintenance log may consist of a table comprising a variety of fields, such as registration numbers, chassis serial number, vehicle codes, and dates and descriptions of maintenance actions performed. This information may be retrieved and manipulated utilizing the computer 33 when the vehicle 10 is taken to a maintenance depot. If the computer 33 is provided with an interactive electronic technical manual (IETM) for the vehicle 10, this allows the IETM to have access to all of the diagnostic data acquired by the intelligent display module 14 as well as all of the maintenance data stored by the intelligent display module 14. This greatly enhances the ability to perform vehicle maintenance and diagnostics on the vehicle 10.
Additionally, sufficient memory capacity is preferably provided so that status information from the test interface module 21 as well as the control systems 24–30 can be sampled and stored at frequent, regular intervals in a circular data queue (i.e., with new data eventually replacing old data in the circular queue). This allows the intelligent display module 14 to provide a data logger service so that input data acquired over a period of time can be viewed to allow an assessment of dynamic conditions leading to a fault to be evaluated. Additionally, the vehicle is preferably provided with one more sensors that indicate whether a severe malfunction (e.g., the vehicle being involved in an accident) has occurred. When inputs from these sensors indicates that a severe malfunction has occurred, data logging is stopped, so that data leading up to the severe malfunction is stored in a manner similar to a so-called “black box recorder.”
Referring now to
Referring now to
Referring now to
Referring now to
Advantageously, due to the utilization of a network architecture in the preferred embodiment, the diagnostic system is able to use sensors and other sources of information that are already provided on the vehicle, because it is able to interact with other vehicle control systems such as the engine control system, the anti-lock brake control system, the central tire inflation control system, and so on, via a network communication link. The fact that the diagnostic system is connected to these other systems, which are all typically capable of providing a vast array of status information, puts this status information at the disposal of the diagnostic system.
Further, due to the utilization of an intelligent display module in the preferred embodiment, it is possible for the intelligent display module to be connected to the network communication link and collect information as necessary for a variety of purposes. Thus, the preferred intelligent display module is microprocessor-based and is capable of executing firmware to provide additional functionality such as data logging, accident reconstruction, and a vehicle maintenance record. Again, this functionality can be achieved by taking advantage of the information available from the vehicle subsystems by way of the network architecture.
Moreover, by mounting the intelligent display module on board the vehicle in the preferred embodiment, for example, in an operator compartment, it is not necessary to bring the vehicle to a maintenance depot to have vehicle malfunctions diagnosed. The services offered by the intelligent display module are available wherever and whenever the vehicle is in operation.
Many other changes and modifications may be made to the present invention without department from the spirit thereof. The scope of these and other changes will become apparent from the appended claims.
This application is a continuation of U.S. Ser. No. 09/500,506, filed Feb. 9, 2000, now U.S. Pat. No. 6,553,290, issued Apr. 22, 2003, hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3720863 | Ringland et al. | Mar 1973 | A |
4041470 | Slane et al. | Aug 1977 | A |
4162714 | Correll | Jul 1979 | A |
4180803 | Wesemeyer et al. | Dec 1979 | A |
4355385 | Hampshire et al. | Oct 1982 | A |
4516121 | Moriyama et al. | May 1985 | A |
4542802 | Garvey et al. | Sep 1985 | A |
RE32140 | Tokuda et al. | May 1986 | E |
4639609 | Floyd et al. | Jan 1987 | A |
4646232 | Chang et al. | Feb 1987 | A |
4744218 | Edwards et al. | May 1988 | A |
4760275 | Sato et al. | Jul 1988 | A |
4809177 | Windle et al. | Feb 1989 | A |
4809803 | Ahern et al. | Mar 1989 | A |
4843557 | Ina et al. | Jun 1989 | A |
4864154 | Copeland et al. | Sep 1989 | A |
4864568 | Sato et al. | Sep 1989 | A |
4894781 | Sato et al. | Jan 1990 | A |
4941546 | Nist et al. | Jul 1990 | A |
4949808 | Garnett | Aug 1990 | A |
5025253 | DiLullo et al. | Jun 1991 | A |
5046007 | McCrery et al. | Sep 1991 | A |
5091856 | Hasegawa et al. | Feb 1992 | A |
5124915 | Krenzel | Jun 1992 | A |
5189617 | Shiraishi | Feb 1993 | A |
5202830 | Tsurumiya et al. | Apr 1993 | A |
5214582 | Gray | May 1993 | A |
5365436 | Schaller et al. | Nov 1994 | A |
5416702 | Kitagawa et al. | May 1995 | A |
5418437 | Couture et al. | May 1995 | A |
5445347 | Ng | Aug 1995 | A |
5463992 | Swenson et al. | Nov 1995 | A |
5493490 | Johnson | Feb 1996 | A |
5508689 | Rado et al. | Apr 1996 | A |
5528496 | Brauer et al. | Jun 1996 | A |
5539869 | Spoto et al. | Jul 1996 | A |
5541840 | Gurne et al. | Jul 1996 | A |
5555171 | Sonehara et al. | Sep 1996 | A |
5557257 | Gieffers | Sep 1996 | A |
5568023 | Grayer et al. | Oct 1996 | A |
5579227 | Simmons et al. | Nov 1996 | A |
5592375 | Salmon et al. | Jan 1997 | A |
5619412 | Hapka | Apr 1997 | A |
5623169 | Sugimoto et al. | Apr 1997 | A |
5636122 | Shah et al. | Jun 1997 | A |
5637933 | Rawlings et al. | Jun 1997 | A |
5638272 | Minowa et al. | Jun 1997 | A |
5657224 | Lonn et al. | Aug 1997 | A |
5670845 | Grant et al. | Sep 1997 | A |
5732074 | Spaur et al. | Mar 1998 | A |
5736925 | Knauff et al. | Apr 1998 | A |
5739592 | Rigsby et al. | Apr 1998 | A |
5754021 | Kojima | May 1998 | A |
5774361 | Colarelli, III et al. | Jun 1998 | A |
5793648 | Nagle et al. | Aug 1998 | A |
5794165 | Minowa et al. | Aug 1998 | A |
5812959 | Froeburg et al. | Sep 1998 | A |
5815126 | Fan et al. | Sep 1998 | A |
5819188 | Vos | Oct 1998 | A |
5819201 | DeGraaf | Oct 1998 | A |
5827957 | Wehinger | Oct 1998 | A |
5838251 | Brinkmeyer et al. | Nov 1998 | A |
5844473 | Kaman | Dec 1998 | A |
5845221 | Hosokawa et al. | Dec 1998 | A |
5848365 | Coverdill | Dec 1998 | A |
5856976 | Hirano | Jan 1999 | A |
5864781 | White | Jan 1999 | A |
5884206 | Kim | Mar 1999 | A |
5890080 | Coverdill et al. | Mar 1999 | A |
5896418 | Hamano et al. | Apr 1999 | A |
5913210 | Call | Jun 1999 | A |
5918180 | Dimino | Jun 1999 | A |
5919237 | Balliet | Jul 1999 | A |
5922040 | Prabhakaran | Jul 1999 | A |
5928291 | Jenkins et al. | Jul 1999 | A |
5930742 | Dodd, Jr. et al. | Jul 1999 | A |
5945919 | Trask | Aug 1999 | A |
5948025 | Sonoda | Sep 1999 | A |
5949330 | Hoffman et al. | Sep 1999 | A |
5950144 | Hall et al. | Sep 1999 | A |
5957985 | Wong et al. | Sep 1999 | A |
5985454 | McMordie et al. | Nov 1999 | A |
5987365 | Okamoto | Nov 1999 | A |
5995898 | Tuttle | Nov 1999 | A |
5997338 | Pohjola | Dec 1999 | A |
5999104 | Symanow et al. | Dec 1999 | A |
6012004 | Sugano et al. | Jan 2000 | A |
6033041 | Koga et al. | Mar 2000 | A |
6038500 | Weiss | Mar 2000 | A |
6041310 | Green et al. | Mar 2000 | A |
6065565 | Puszkiewicz et al. | May 2000 | A |
6070538 | Flamme et al. | Jun 2000 | A |
6088650 | Schipper et al. | Jul 2000 | A |
6096978 | Pohjola | Aug 2000 | A |
6097998 | Lancki | Aug 2000 | A |
6112152 | Tuttle | Aug 2000 | A |
6125356 | Brockman et al. | Sep 2000 | A |
6135806 | Pohjola | Oct 2000 | A |
6141608 | Rother | Oct 2000 | A |
6141610 | Rothert et al. | Oct 2000 | A |
6154122 | Menze | Nov 2000 | A |
6154658 | Caci | Nov 2000 | A |
6157889 | Baker | Dec 2000 | A |
6181994 | Colson et al. | Jan 2001 | B1 |
6182807 | Saito et al. | Feb 2001 | B1 |
6208948 | Klingler et al. | Mar 2001 | B1 |
6212449 | Wellman et al. | Apr 2001 | B1 |
6219626 | Steinmetz et al. | Apr 2001 | B1 |
6223104 | Kamen et al. | Apr 2001 | B1 |
6230496 | Hofmann et al. | May 2001 | B1 |
6232874 | Murphy | May 2001 | B1 |
6240365 | Bunn | May 2001 | B1 |
6241593 | Chen et al. | Jun 2001 | B1 |
6243628 | Bliley et al. | Jun 2001 | B1 |
6244758 | Solymar et al. | Jun 2001 | B1 |
6246320 | Monroe | Jun 2001 | B1 |
6256580 | Meis et al. | Jul 2001 | B1 |
6263268 | Nathanson | Jul 2001 | B1 |
6263269 | Dannenberg | Jul 2001 | B1 |
6281790 | Kimmel et al. | Aug 2001 | B1 |
6285932 | de Bellefeuille et al. | Sep 2001 | B1 |
6331365 | King | Dec 2001 | B1 |
6338010 | Sparks et al. | Jan 2002 | B1 |
6356826 | Pohjola | Mar 2002 | B1 |
6370454 | Moore | Apr 2002 | B1 |
6404607 | Burgess et al. | Jun 2002 | B1 |
6405114 | Priestley et al. | Jun 2002 | B1 |
6411874 | Morgan et al. | Jun 2002 | B2 |
6421593 | Kempen et al. | Jul 2002 | B1 |
6429773 | Schuyler | Aug 2002 | B1 |
6430164 | Jones et al. | Aug 2002 | B1 |
6430488 | Goldman et al. | Aug 2002 | B1 |
6434512 | Discenzo | Aug 2002 | B1 |
6466258 | Mogenis et al. | Oct 2002 | B1 |
6487717 | Brunemann et al. | Nov 2002 | B1 |
6496775 | McDonald, Jr. et al. | Dec 2002 | B2 |
6501368 | Wiebe et al. | Dec 2002 | B1 |
6522955 | Colborn | Feb 2003 | B1 |
6539296 | Diaz et al. | Mar 2003 | B2 |
6542077 | Joao | Apr 2003 | B2 |
6549827 | Yen | Apr 2003 | B1 |
6553290 | Pillar | Apr 2003 | B1 |
6580953 | Wiebe et al. | Jun 2003 | B1 |
6609051 | Fiechter et al. | Aug 2003 | B2 |
6609108 | Pulliam et al. | Aug 2003 | B1 |
6611740 | Lowrey et al. | Aug 2003 | B2 |
6611755 | Coffee et al. | Aug 2003 | B1 |
6615186 | Kolls | Sep 2003 | B1 |
6636790 | Lightner et al. | Oct 2003 | B1 |
6640166 | Liebl et al. | Oct 2003 | B2 |
6643571 | Götvall et al. | Nov 2003 | B2 |
6662087 | Liebl et al. | Dec 2003 | B1 |
6671594 | Miller | Dec 2003 | B2 |
6671646 | Manegold et al. | Dec 2003 | B2 |
6694234 | Lockwood et al. | Feb 2004 | B2 |
6735504 | Katagishi et al. | May 2004 | B2 |
6757597 | Yakes et al. | Jun 2004 | B2 |
6795758 | Sinex | Sep 2004 | B2 |
6798344 | Faulkner et al. | Sep 2004 | B2 |
6804626 | Manegold et al. | Oct 2004 | B2 |
6865460 | Bray et al. | Mar 2005 | B2 |
6882917 | Pillar et al. | Apr 2005 | B2 |
6885920 | Yakes et al. | Apr 2005 | B2 |
6892131 | Coffee et al. | May 2005 | B2 |
6909944 | Pillar et al. | Jun 2005 | B2 |
6912453 | Le Draoullec et al. | Jun 2005 | B2 |
6917288 | Kimmel et al. | Jul 2005 | B2 |
6922615 | Pillar et al. | Jul 2005 | B2 |
6941202 | Wilson et al. | Sep 2005 | B2 |
6959235 | Abdel-Malek et al. | Oct 2005 | B1 |
6993420 | Le Draoullec et al. | Jan 2006 | B2 |
6993421 | Pillar et al. | Jan 2006 | B2 |
7006902 | Archer et al. | Feb 2006 | B2 |
7024296 | Squires et al. | Apr 2006 | B2 |
7034678 | Burkley et al. | Apr 2006 | B2 |
7072745 | Pillar et al. | Jul 2006 | B2 |
7107129 | Rowe et al. | Sep 2006 | B2 |
7127331 | Pillar et al. | Oct 2006 | B2 |
7162332 | Pillar et al. | Jan 2007 | B2 |
7164977 | Yakes et al. | Jan 2007 | B2 |
7184862 | Pillar et al. | Feb 2007 | B2 |
7184866 | Squires et al. | Feb 2007 | B2 |
7209817 | Abdel-Malek et al. | Apr 2007 | B2 |
7254468 | Pillar et al. | Aug 2007 | B2 |
7302320 | Nasr et al. | Nov 2007 | B2 |
7363128 | Dietsch et al. | Apr 2008 | B2 |
20010034573 | Morgan et al. | Oct 2001 | A1 |
20010034656 | Lucas et al. | Oct 2001 | A1 |
20010044769 | Chaves | Nov 2001 | A1 |
20020010643 | Chaves | Jan 2002 | A1 |
20020015354 | Buckelew | Feb 2002 | A1 |
20020049523 | Diaz et al. | Apr 2002 | A1 |
20020065594 | Squires et al. | May 2002 | A1 |
20020065707 | Lancaster et al. | May 2002 | A1 |
20020107833 | Kerkinni | Aug 2002 | A1 |
20020111725 | Burge | Aug 2002 | A1 |
20020123832 | Gotvall et al. | Sep 2002 | A1 |
20020133273 | Lowrey et al. | Sep 2002 | A1 |
20020181405 | Ying | Dec 2002 | A1 |
20030001736 | Lewis | Jan 2003 | A1 |
20030046179 | Anabtawi et al. | Mar 2003 | A1 |
20030080619 | Bray et al. | May 2003 | A1 |
20030081123 | Rupe | May 2003 | A1 |
20030105565 | Loda et al. | Jun 2003 | A1 |
20030105566 | Miller | Jun 2003 | A1 |
20030114965 | Fiechter et al. | Jun 2003 | A1 |
20030130765 | Pillar et al. | Jul 2003 | A1 |
20030158635 | Pillar et al. | Aug 2003 | A1 |
20030158638 | Yakes et al. | Aug 2003 | A1 |
20030158640 | Pillar et al. | Aug 2003 | A1 |
20030163228 | Pillar et al. | Aug 2003 | A1 |
20030163229 | Pillar et al. | Aug 2003 | A1 |
20030163230 | Pillar et al. | Aug 2003 | A1 |
20030163233 | Song et al. | Aug 2003 | A1 |
20030171854 | Pillar et al. | Sep 2003 | A1 |
20030182034 | Katagishi et al. | Sep 2003 | A1 |
20030195680 | Pillar | Oct 2003 | A1 |
20030200015 | Pillar | Oct 2003 | A1 |
20030205422 | Morrow et al. | Nov 2003 | A1 |
20030233178 | Sinex | Dec 2003 | A1 |
20040002794 | Pillar et al. | Jan 2004 | A1 |
20040019414 | Pillar et al. | Jan 2004 | A1 |
20040024502 | Squires et al. | Feb 2004 | A1 |
20040039502 | Wilson et al. | Feb 2004 | A1 |
20040039504 | Coffee et al. | Feb 2004 | A1 |
20040039510 | Archer et al. | Feb 2004 | A1 |
20040055802 | Pillar et al. | Mar 2004 | A1 |
20040069850 | De Wilde | Apr 2004 | A1 |
20040069865 | Rowe et al. | Apr 2004 | A1 |
20040070515 | Burkley et al. | Apr 2004 | A1 |
20040133319 | Pillar et al. | Jul 2004 | A1 |
20040133332 | Yakes et al. | Jul 2004 | A1 |
20040199302 | Pillar et al. | Oct 2004 | A1 |
20040203974 | Seibel | Oct 2004 | A1 |
20050004733 | Pillar et al. | Jan 2005 | A1 |
20050038934 | Gotze et al. | Feb 2005 | A1 |
20050060246 | Lastinger et al. | Mar 2005 | A1 |
20050113988 | Nasr et al. | May 2005 | A1 |
20050113996 | Pillar et al. | May 2005 | A1 |
20050114007 | Pillar et al. | May 2005 | A1 |
20050119806 | Nasr et al. | Jun 2005 | A1 |
20050131600 | Quigley et al. | Jun 2005 | A1 |
20050209747 | Yakes et al. | Sep 2005 | A1 |
20050234622 | Pillar et al. | Oct 2005 | A1 |
Number | Date | Country |
---|---|---|
41 11 865 | Oct 1991 | DE |
624500 | Nov 1994 | DE |
29807561 | Aug 1998 | DE |
199 29 434 | Dec 2000 | DE |
19936352 | Feb 2001 | DE |
DE 101 03 922 | Aug 2002 | DE |
0 266 704 | May 1988 | EP |
0 504 913 | Sep 1992 | EP |
0 564 943 | Oct 1993 | EP |
0 791 506 | Aug 1997 | EP |
0 949 122 | Oct 1999 | EP |
1 087 343 | Mar 2001 | EP |
1 115 264 | Jul 2001 | EP |
1 229 636 | Aug 2002 | EP |
10115232 | May 1998 | JP |
2000-333160 | Nov 2000 | JP |
507 046 | Mar 1998 | SE |
2 263 376 | Jul 1993 | WO |
WO 9515594 | Jun 1995 | WO |
WO 9702965 | Jan 1997 | WO |
WO 9830961 | Jul 1998 | WO |
WO9923783 | May 1999 | WO |
WO 9923783 | May 1999 | WO |
WO 0069662 | Nov 2000 | WO |
WO 0079727 | Dec 2000 | WO |
WO 01015001 | Mar 2001 | WO |
WO 03059455 | Jul 2003 | WO |
WO 03059455 | Jul 2003 | WO |
WO 03060831 | Jul 2003 | WO |
WO 03060831 | Jul 2003 | WO |
WO 03061235 | Jul 2003 | WO |
WO 03061235 | Jul 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20030200015 A1 | Oct 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09500506 | Feb 2000 | US |
Child | 10420187 | US |