This application is related to the field of vehicle control systems and, more particularly, to a remote start system and related methods for vehicles.
Vehicle security systems are widely used to deter vehicle theft, prevent theft of valuables from a vehicle, deter vandalism, and to protect vehicle owners and occupants. A typical automobile security system, for example, includes a central processor or controller connected to a plurality of vehicle sensors. The sensors, for example, may detect opening of the trunk, hood, doors, windows, and also movement of the vehicle or within the vehicle. Ultrasonic and microwave motion detectors, vibration sensors, sound discriminators, differential pressure sensors, and switches may be used as sensors. In addition, radar sensors may be used to monitor the area proximate the vehicle.
The controller typically operates to give an alarm indication in the event of triggering of a vehicle sensor. The alarm indication may typically be a flashing of the lights and/or the sounding of the vehicle horn or a siren. In addition, the vehicle fuel supply and/or ignition power may be selectively disabled based upon an alarm condition.
A typical security system also includes a receiver associated with the controller that cooperates with one or more remote transmitters typically carried by the user as disclosed, for example, in U.S. Pat. No. 4,383,242 to Sassover et al. and U.S. Pat. No. 5,146,215 to Drori. The remote transmitter may be used to arm and disarm the vehicle security system or provide other remote control features from a predetermined range away from the vehicle. Also related to remote control of a vehicle function U.S. Pat. No. 5,252,966 to Lambropoulous et al. discloses a remote keyless entry system for a vehicle. The keyless entry system permits the user to remotely open the vehicle doors or open the vehicle trunk using a small handheld transmitter.
Unfortunately, the majority of vehicle security systems need to be directly connected by wires to individual vehicle devices, such as the vehicle horn or door switches of the vehicle. In other words, a conventional vehicle security system is hardwired to various vehicle components, typically by splicing into vehicle wiring harnesses or via interposing T-harnesses and connectors. The number of electrical devices in a vehicle has increased so that the size and complexity of wiring harnesses has also increased. For example, the steering wheel may include horn switches, an airbag, turn-signal and headlight switches, wiper controls, cruise control switches, ignition wiring, an emergency flasher switch, and/or radio controls. Likewise, a door of a vehicle, for example, may include window controls, locks, outside mirror switches, and/or door-panel light switches.
In response to the increased wiring complexity and costs, vehicle manufacturers have begun attempts to reduce the amount of wiring within vehicles to reduce weight, reduce wire routing problems, decrease costs, and reduce complications which may arise when troubleshooting the electrical system. For example, some manufacturers have adopted multiplexing schemes to reduce cables to three or four wires and to simplify the exchange of data among the various onboard electronic systems as disclosed, for example, in “The Thick and Thin of Car Cabling” by Thompson appearing in the IEEE Spectrum, February 1996, pp. 42-45.
Implementing multiplexing concepts in vehicles in a cost-effective and reliable manner may not be easy. Successful implementation, for example, may require the development of low or error-free communications in what can be harsh vehicle environments. With multiplexing technology, the various electronic modules or devices may be linked by a single signal wire in a bus also containing a power wire, and one or more ground wires. Digital messages are communicated to all modules over the data communications bus. Each message may have one or more addresses associated with it so that the devices can recognize which messages to ignore and which messages to respond to or read.
The Thompson article describes a number of multiplexed networks for vehicles. In particular, the Grand Cherokee made by Chrysler is described as having five multiplex nodes or controllers: the engine controller, the temperature controller, the airbag controller, the theft alarm, and the overhead console. Other nodes for different vehicles may include a transmission controller, a trip computer, an instrument cluster controller, an antilock braking controller, an active suspension controller, and a body controller for devices in the passenger compartment.
A number of patent references are also directed to digital or multiplex communications networks or circuits, such as may be used in a vehicle. For example, U.S. Pat. No. 4,538,262 Sinniger et al. discloses a multiplex bus system including a master control unit and a plurality of receiver-transmitter units connected thereto. Similarly, U.S. Pat. No. 4,055,772 to Leung discloses a power bus in a vehicle controlled by a low current digitally coded communications system. Other references disclosing various vehicle multiplex control systems include, for example, U.S. Pat. No. 4,760,275 to Sato et al.; U.S. Pat. No. 4,697,092 to Roggendorf et al.; and U.S. Pat. No. 4,792,783 to Burgess et al.
Several standards have been proposed for vehicle multiplex networks including, for example, the Society of Automotive Engineers “Surface Vehicle Standard, Class B Data Communications Network Interface”, SAE J1850, July 1995. Another report by the SAE is the “Surface Vehicle Information Report, Chrysler Sensor and Control (CSC) Bus Multiplexing Network for Class ‘A’ Applications”, SAE J2058, July 1990. Many other networks are also being implemented or proposed for communications between vehicle devices and nodes or controllers.
In addition, to vehicle security and remote keyless entry functions, another type of desirable vehicle remote control function is remotely starting the vehicle engine when the owner is away from the vehicle. Such remote starting can be used in cold climates to warm the engine and/or run the passenger compartment heater, to thereby prevent freezing or for the user's comfort. Conversely, remote engine starting can enable the air conditioning to run to cool the vehicle's interior before the vehicle user enters the vehicle.
Unfortunately, conventional vehicle control systems, such as aftermarket remote engine starting systems, are for hardwired connection to vehicle devices and are not readily adaptable to a vehicle including a data communications bus. Moreover, remote starting of the engine presents additional difficulties compared to some other vehicle control applications. This is so because starting the engine may require certain vehicle conditions are correct prior to starting the engine and while the engine is running with the vehicle unattended. It may also be necessary for a remote starter system to bypass an immobilizer device which is part of the security system of some vehicles. For example, U.S. Pat. No. 5,612,578 to Drew entitled “Vehicle Engine Start Control Apparatus Including Interface Device Facilitating Installation and Related Methods” discloses a remote start system which is hardwire connected via mating plugs for more conveniently bypassing an immobilizer circuit based upon a coded resistance of the ignition key.
A remote starter system may also desirably be able to interface with one or more vehicle controllers, such as for engine management and transmission control, for example. In addition, a remote starter system, even if it were adapted for a communications bus and devices for one particular model, model year, and manufacturer, may not be compatible with any other models, model years, or manufacturers.
In view of the foregoing background it is therefore an object of the invention to provide a remote start control system and related method for a vehicle comprising a data communications bus and at least one vehicle device connected to the data communications bus.
It is another object of the invention to provide such a remote starter system and associated method wherein the system is adapted to operate with different vehicles.
These and other objects, features and advantages in accordance with the present invention are provided by a vehicle remote start control system including at least one vehicle device associated with starting an engine of the vehicle, a remote start transmitter, and a vehicle remote start controller. The vehicle remote start controller is connected to the data communications bus for communicating with the at least one vehicle device. The remote start controller is also responsive to signals from the remote start transmitter to cause starting of the vehicle.
The at least one vehicle device associated with starting the engine of the vehicle may comprise at least one controller, such as the engine management controller or the transmission controller, for example. Alternately, or additionally, the at least one vehicle device associated with starting the engine of the vehicle may comprise at least one vehicle sensor. For example, the vehicle sensor may be one or more of a brake sensor, a transmission sensor, a hood sensor, or an engine speed sensor.
In some embodiments, the vehicle may also include an engine starter circuit, and a security immobilizer circuit connected to the engine starter circuit. The security immobilizer circuit is for selectively enabling the engine starter, such as in response to a coded key or transponder. In such embodiments, the remote start controller may bypass the security immobilizer circuit to enable remote starting.
The remote start transmitter may be a remote handheld transmitter to be carried by a user when away from the vehicle, for example. The remote start signal may also be supplied via a communications network, such as including at least a central station transmitter.
Another aspect of the invention relates to providing compatibility with different vehicle types. The remote start controller may comprise a multi-vehicle compatible remote start controller. The multi-vehicle compatible remote start controller may generate at least one set of command signals on the data communications bus for the at least one vehicle device. The at least one set of command signals may comprise at least one working command signal and at least one non-working command signal for a given vehicle to thereby provide command compatibility with a plurality of different vehicles.
In addition, for reading communications from the vehicle devices, the multi-vehicle compatible remote start controller may store a set of device codes for a given vehicle device for a plurality of different vehicles, read a device code from the data communications bus, and determine a match between a read device code and the stored device codes to thereby provide compatibility with a plurality of different vehicles.
In another embodiment, the multi-vehicle compatibility may be provided by equipping the remote start controller with a desired signal enabling function. This function or feature is for enabling operation using a desired set of signals for a corresponding desired vehicle from a plurality of sets of signals for different vehicles to thereby provide compatibility with a plurality of different vehicles.
A method aspect of the invention is for remotely starting a vehicle engine in a vehicle comprising a data communications bus and at least one vehicle device associated with starting the vehicle engine. The method preferably comprises connecting a vehicle remote start controller to the data communications bus for communicating with the at least one vehicle device, and using the vehicle remote start controller to start the vehicle engine based upon signals received from a remote start transmitter and based upon communication over the data communications bus with the at least one vehicle device.
The present invention will now be described more fully hereinafter with reference to the accompanying drawings in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the illustrated embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. Prime and multiple prime notation are used in alternate embodiments to indicate similar elements.
Referring initially to
By remote starting is meant initially starting the vehicle engine 38 and allowing it to idle while unattended by the vehicle owner as will be readily appreciated by those skilled in the art. As will also be appreciated by those skilled in the art, whether the remote start controller 25 will allow the engine 38 to be started and continue to idle may be based upon any of a number of conditions at the vehicle, some representatives examples of which are described in greater detail below.
The at least one vehicle device associated with starting the engine 38 of the vehicle 21 may comprise at least one controller, such as the engine management controller 45a or the transmission controller 45c, for example. One or more other controllers 45b may also be communicated with by the remote start controller 25. Alternately, or additionally, the at least one vehicle device associated with starting the engine 38 of the vehicle 21 may comprise at least one vehicle sensor 44a-44d. For example, the vehicle sensor may be one or more of a brake sensor 44b, a transmission sensor 44c, a hood sensor 44a, and an engine speed sensor 44d. Other similar sensors are also contemplated by the present invention.
The remote start controller 25 includes a central processing unit (CPU) 36 which may perform the necessary signal processing and logic functions to control starting and subsequent running or shut-down of the engine 38 as will be appreciated by those of skill in the art. For example, the engine 38 may be prevented from starting or shut down if the gear shift lever is in or moved to a position other than Park. Similarly, the engine may be shut down if the engine RPM exceeds a predetermined value. In addition, the engine starter 29 may only need be operated until the engine RPM indicates that the engine is running. The engine 38 may be prevented from running or shut down if the vehicle hood is open. Many other vehicle conditions may also be taken into account by the remote start controller 25 as will be appreciated by those skilled in the art. Further details regarding logical operation of the remote start controller 25 based upon exemplary vehicle device conditions may be found in the abovementioned U.S. Pat. No. 5,612,578 to Drew, the entire disclosure of which is hereby incorporated herein by reference.
Of course, the vehicle 21 would typically include an engine starter circuit 26 as illustrated in the lower righthand portion of
The vehicle 21 may also include the illustrated security immobilizer circuit connected to the engine starter circuit 26. The security immobilizer circuit illustratively includes a passive transponder 47 carried adjacent the ignition key 48, and reader 46 for powering and reading the coded signal from the transponder as will be appreciated by those skilled in the art. Such an immobilizer circuit may be of a conventional type and needs no further description herein. The remote start controller 25 includes a hardwired interface 42 connected to the immobilizer to bypass this circuit when remote starting is desired. Thus, the engine starter circuit 26 may be enabled in response to presentation of the properly coded passive transponder 47 in proximity to the reader 46.
Of course, in other embodiments other types of immobilizer circuits can be used. The engine ignition could be disabled by the engine management controller 45a unless a predetermined code from a transponder reader was generated on the data bus 30, for example. In such a system, a code could be generated on the data communications bus by the bus interface 41 of the remote start controller 25 to effectively bypass such a transponder immobilizer operating over the data communications bus 30 as would be readily appreciated by those skilled in the art. The bus interface 41 includes circuitry for interfacing to the proper signal levels and formats on the data communications bus 30 as will be appreciated by those skilled in the art without further discussion herein.
In another example, the coded resistor key approach described in the Drew patent may also be selectively bypassed by the remote start controller 25 to enable remote starting as will be appreciated by those skilled in the art. Other immobilizer circuits and devices may also be readily bypassed to enable starting.
The remote start transmitter 34 may be a small portable unit including a housing, function control switches carried by the housing, a battery within the housing, and the associated transmitter circuitry. This type of remote handheld transmitter is commonly used in conventional vehicle remote start systems. The communications from the remote start transmitter 34 to the receiver 32 at the vehicle is typically a direct radio frequency link, that is, there is no intervening communications links. However, in other embodiments, the remote start transmitter 34 may indirectly communicate with the receiver 32 via other communications infrastructure, such as via satellite, or cellular communications, via the public switched telephone network (PSTN) and/or over the world wide web or Internet, as will be appreciated by those skilled in the art.
The remote start transmitter 34 may also include one or more central station transmitters, such as may be provided by a satellite transmitter or cellular telephone transmitter, for example. Such a central station transmitter may also be connected to other communications infrastructure.
In some embodiments, the system 20 may optionally include a remote receiver (not shown) in the form of a small handheld device to be carried by the user or at least one central station receiver cooperating with a transmitter (not shown) at the vehicle, such as to provide status information to the user relating to the remote starting.
In the illustrated system 20, various sensors 44a-44d are shown connected to the data bus 30 and which are communicated to and from via the bus interface 41. However, in other embodiments, one or more of these sensors could be directly connected to the hardwire interface 42. This also applies to the various controllers 45a-45c which may also have hardwire interfaces themselves for certain signals or functions as will be readily appreciated by those skilled in the art.
The remote start controller 25 also includes one or more memories 40a, 40b connected to the CPU 36. Although the memories 40a, 40b are illustrated as separate devices, those of skill in the art will recognize that the memories may be combined in a single device or embedded on the same integrated circuit as the processing circuitry of the CPU.
Another aspect of the invention relates to providing compatibility with different vehicle types. As will now be described, the remote start controller 25 may include features such that it can be considered a multi-vehicle compatible remote start controller. The remote start controller 25 incorporating these optional features may generate at least one set of command signals on the data communications bus 30 for at least one vehicle device. The at least one set of command signals may comprise at least one working command signal and at least one non-working command signal for a given vehicle to thereby provide command compatibility with a plurality of different vehicles.
In addition, for reading communications from the vehicle devices, the remote start controller 25 may store a set of device codes for a given vehicle device for a plurality of different vehicles, read a device code from the data communications bus 30, and determine a match between a read device code and the stored device codes to thereby provide compatibility with a plurality of different vehicles.
The vehicle 21 includes a number of electrical/electronic devices 44a-44d and 45a-45c that can be controlled and/or the status thereof read via the data communications bus 30. The remote start controller 25 may provide its multi-vehicle compatibility in one or both directions of communications via the data communications bus 30. Referring now additionally to
In accordance with this aspect of the invention, the remote start controller 25 preferably generates at least one set of command signals on the data communications bus 30 for the at least one vehicle device. The at least one set of command signals preferably comprises at least one working command signal and at least one non-working command signal for a given vehicle to thereby provide compatibility with the plurality of different vehicles. In other words, multiple signals or codes can be generated on the data communications bus 30, and only that code for the given vehicle and device will cause an operation or response from the vehicle device. This provides for a relatively simple and straightforward approach to interface or cooperate with a vehicle having a data communications bus 30, and wherein the remote start controller 25 is advantageously compatible with a number of different vehicles. Since typically it may be desired to interface to a plurality of vehicle devices, the remote start controller 25 may generate a respective set of command signals for each of the vehicle devices.
Such multi-vehicle compatibility provided by the remote start controller 25 is especially advantageous in after-market remote start systems. The ability to interface through the data communications bus 30 also significantly reduces the wiring complexity needed to interface to the associated vehicle devices.
The remote start controller 25 may sequentially generate the different command signals (working and non-working) for an intended vehicle device. To ensure effective communications even in the presence of noise, for example, the remote start controller 25 may generate the set of command signals a plurality of times, such as, for example, two to five times. The need to effectively communicate should be balanced against possible traffic congestion on the data bus 30 as will be appreciated by those skilled in the art.
Referring now more specifically to the diagram of
The actual coded signals would be compatible with the particular data communications bus 30 as will be appreciated by those skilled in the art. The codes may be binary codes, which for convenience can be represented more simply by corresponding hexadecimal codes as would also be appreciated by those skilled in the art. For example, for an unlock all vehicle doors to be commanded in a 1995 Jeep Grand Cherokee, the code may be 03868004, for a 2000 Jeep Grand Cherokee, the code may be 0422A00400. As will be readily appreciated by those skilled in the art, such codes can be obtained from the manufacturers directly, or may be read from the data bus 30 using any one of a number of commercially available diagnostic tools for reading the data bus 30, for example.
The set of command signals may be repeated as mentioned above, and as schematically illustrated at the lower portion of the table 50. Of course, the memory 40a may store the actual codes, but may also store data enabling generation of the set of command signals by the CPU 36. This may be particularly so where certain portions of the code, e.g. preamble, or some other portion, are common across either multiple vehicles, and/or over multiple vehicle devices.
The number of vehicles and number of devices to be controlled using the multi-vehicle compatibility of the remote start controller 25 can both be relatively large to cover a substantial portion of the vehicle marketplace. Alternatively, the multiple command signal concept may also be advantageously used to provide compatibility for as few as two vehicles, and even a single vehicle device.
Turning now to
The compatibility to read a code and determine the message or content thereof for a vehicle device from among a plurality of vehicles can be used alone or in combination with the compatibility for writing or generating signals on the bus described above. More particularly, the remote start controller 25″ is for storing a set of device codes for a given vehicle device for a plurality of different vehicles, for reading a device code from the data communications bus 30, and for determining a match between a read device code and the stored device codes to thereby provide compatibility with a plurality of different vehicles. Such an arrangement provides for a relatively simple and straightforward approach to interface with a vehicle having a data communications bus 30.
The remote start controller 25 may comprise the code look-up memory 40b for the stored device codes, and the processor or CPU 36 cooperating with the memory for determining the match between the read device code and the stored device codes. The at least one vehicle device may include a plurality of vehicle devices, and, accordingly, the memory 40b of the multi-vehicle compatible controller 25 preferably stores a respective set of device codes for each of the plurality of vehicle devices.
Referring now more specifically to
The last or rightmost column in the illustrated table 60 is the device data or message corresponding to the associated vehicle and code. These device messages extend from a first message, DM1A, to a last device message, DMNZ. The messages may be of many different types, such as driver door open or closed, hood open or closed, shock sensor triggered, brake pressure indicated, gearshift selector in Park, etc. as will be appreciated by those skilled in the art.
By way of example, the common table 60 includes a blocked row schematically illustrating a match for a Code 572. This code is for a Ford Taurus and indicates that the driver's door is open. This type of data may be useful for remote starting. The CPU 36 would read the code on the data bus 30 and compare the code against the stored codes to determine a match. The CPU 36 is likely to buffer some or all of a code when received to subsequently be compared using the table 60 as will be understood by those skilled in the art. In other embodiments, individual bits or blocks thereof may be compared as they are received.
An alternate embodiment of the common table 60 is now explained with reference to
Those of skill in the art will recognize that the tables 60 and 60′ of
Since it may also be desirable to re-install remote start controller 25 in another vehicle, the controller may be reset and another vehicle learned or configured during an initial set-up. This concept is generally described as an embodiment of a desired signal enabling function or feature in related parent U.S. patent application Ser. No. 09/382,245 filed Aug. 25, 1999, which in turn, is a continuation of U.S. Pat. No. 6,011,460, which in turn, is a continuation-in-part of U.S. Pat. No. 5,719,551, and the disclosure of each of which are incorporated herein by reference in its entirety.
This desired signal enabling is further described below with reference to
The remote start system 55 does not show or necessarily include the hardwire interface described above. Rather, in this embodiment, the remote start function is implemented by the remote start controller 55 via communication with the engine management controller 45a which, in turn, is directly connected to the starter relay 27.
Turning now additionally to
As illustrated in
In the illustrated embodiment of
Referring now additionally to
Yet another embodiment of the security system 55″ according to the invention is explained with reference to
Still another embodiment of the desired signal enabling means 57′″ is explained with reference to
Turning now additionally to
Returning now again to
Similar concepts can also be extended to a multi-vehicle compatible adaptor for the other direction of communication, that is, from the data communications bus 30 to one or more vehicle devices. Such an adaptor would include the code look-up memory 40b as described above. Moreover, the operation of such a multi-vehicle compatible adaptor will be readily understood by those of skill in the art based upon the above provided descriptions relating to
A method aspect of the invention is for remotely starting a vehicle engine 38 in a vehicle 21 comprising a data communications bus 30 and at least one vehicle device 44a-44d and 45a-45c associated with starting the vehicle engine. The method preferably comprises receiving signals at the vehicle from a remote start transmitter 34, connecting a vehicle remote start controller 25 to the data communications bus 30 for communicating with the at least one vehicle device, and using the vehicle remote start controller to start the vehicle engine 38 based upon signals received from the remote start transmitter and based upon communication over the data communications bus with the at least one vehicle device.
Other features relating to vehicle control systems are disclosed in copending patent applications entitled “MULTI-VEHICLE COMPATIBLE CONTROL SYSTEM GENERATING COMMAND SIGNALS ON A DATA BUS AND ASSOCIATED METHODS”, Ser. No. 09/533,332 filed May 31, 2000, now U.S. Pat. No. 6,346,376 and “MULTI-VEHICLE COMPATIBLE CONTROL SYSTEM FOR READING FROM A DATA BUS AND ASSOCIATED METHODS”, Ser. No. 09/583,257 filed May 31, 2000, now U.S. Pat. No. 6,713,835, the entire disclosures of which are incorporated herein by reference.
Many modifications and other embodiments of the invention will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Accordingly, it is understood that the invention is not to be limited to the embodiments disclosed, and that other modifications and embodiments are intended to be included within the spirit and scope of the appended claims.
The present application is a continuation of U.S. patent application Ser. No. 10/413,047 filed Apr. 14, 2003 now U.S. Pat. No. 7,031,826, which is a continuation of U.S. patent application Ser. No. 09/583,333 filed May 31, 2000, now U.S. Pat. No. 6,812,829, which is a continuation-in-part of U.S. patent application Ser. No. 09/382,245 filed Aug. 25, 1999, now U.S. Pat. No. 6,275,147, which in turn, is a continuation of Ser. No. 09/023,838 filed Feb. 13, 1998, now U.S. Pat. No. 6,011,460, which in turn, is a continuation-in-part of Ser. No. 08/701,356 filed Aug. 22, 1996, now U.S. Pat. No. 5,719,551, the entire contents of each of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4055772 | Leung | Oct 1977 | A |
4236594 | Ramsperger | Dec 1980 | A |
4288778 | Zucker | Sep 1981 | A |
4446460 | Tholl et al. | May 1984 | A |
4538262 | Sinniger et al. | Aug 1985 | A |
4697092 | Roggendorf et al. | Sep 1987 | A |
4754255 | Saunders et al. | Jun 1988 | A |
4760275 | Sato et al. | Jul 1988 | A |
4761645 | Mochida | Aug 1988 | A |
4792783 | Burgess et al. | Dec 1988 | A |
4794368 | Grossheim et al. | Dec 1988 | A |
4841159 | Evans et al. | Jun 1989 | A |
4897630 | Nykerk | Jan 1990 | A |
4926332 | Komuro et al. | May 1990 | A |
4940964 | Dao | Jul 1990 | A |
5006843 | Hauer | Apr 1991 | A |
5024186 | Long et al. | Jun 1991 | A |
5040990 | Suman et al. | Aug 1991 | A |
5046041 | Lecocq et al. | Sep 1991 | A |
5049867 | Stouffer | Sep 1991 | A |
5054569 | Scott et al. | Oct 1991 | A |
5081667 | Drori et al. | Jan 1992 | A |
5142278 | Moallemi et al. | Aug 1992 | A |
5146215 | Drori | Sep 1992 | A |
5243322 | Thompson et al. | Sep 1993 | A |
5252966 | Lambropoulos et al. | Oct 1993 | A |
5406270 | Van Lente | Apr 1995 | A |
5473540 | Schmitz | Dec 1995 | A |
5475818 | Molyneaux et al. | Dec 1995 | A |
5506562 | Weisner | Apr 1996 | A |
5521588 | Kuhner et al. | May 1996 | A |
5523948 | Adrain | Jun 1996 | A |
5555498 | Berra et al. | Sep 1996 | A |
5606306 | Mutoh et al. | Feb 1997 | A |
5612578 | Drew | Mar 1997 | A |
5619412 | Hapka | Apr 1997 | A |
5646457 | Vakavtchiev | Jul 1997 | A |
5673017 | Dery et al. | Sep 1997 | A |
5689142 | Liu | Nov 1997 | A |
5719551 | Flick | Feb 1998 | A |
5721550 | Lopez | Feb 1998 | A |
5739748 | Flick | Apr 1998 | A |
5757086 | Nagashima | May 1998 | A |
5793283 | Davis | Aug 1998 | A |
5811886 | Majmudar | Sep 1998 | A |
5818330 | Schweiger | Oct 1998 | A |
5832397 | Yoshida et al. | Nov 1998 | A |
5838255 | DiCroce | Nov 1998 | A |
5912512 | Hayashi et al. | Jun 1999 | A |
6812829 | Flick | Nov 2004 | B1 |
Number | Date | Country |
---|---|---|
195 30 721 | Feb 1997 | DE |
0 699 562 | Jul 1995 | EP |
WO 9728988 | Aug 1997 | WO |
Number | Date | Country | |
---|---|---|---|
20050179321 A1 | Aug 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10413047 | Apr 2003 | US |
Child | 11095868 | US | |
Parent | 09583333 | May 2000 | US |
Child | 10413047 | US | |
Parent | 09023838 | Feb 1998 | US |
Child | 09382245 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09382245 | Aug 1999 | US |
Child | 09583333 | US | |
Parent | 08701356 | Aug 1996 | US |
Child | 09023838 | US |