Patent Grant
11257307
The present invention is directed to a vehicle diagnostic system, and in particular to an adaptive vehicle scan selection with a vehicle diagnostic device.
Vehicle diagnostic systems employing diagnostic scan devices or tools are used in automotive repair facilities to diagnose and repair computer-based vehicle systems, where vehicles may have differing computer-based systems depending on the configuration and options installed on the vehicle. Vehicle diagnostic scan systems may include or use one or more diagnostic software scanning programs or applications, such as applications developed by an original equipment automotive manufacturer (“OEM”), or an aftermarket diagnostic company. OEM diagnostic applications may include proprietary diagnostic application software exclusive to a particular OEM, and may be required for particular computer-based vehicle systems of a vehicle, such as for Adaptive Driver Assistance Systems (“ADAS”) of a vehicle.
The present invention provides a vehicle diagnostic system, and in particular a diagnostic system that queries/scans a vehicle for vehicle data information that is read and evaluated to determine whether or not the vehicle includes, or the presence or absence, of particular vehicle systems, such as ADAS systems, or other such safety systems, and based thereon selectively controls the diagnostic scanning of the vehicle. Based on a determination of the presence or absence of particular vehicle systems, such as safety systems and/or what specific safety systems are included in the vehicle, the diagnostic system determines and controls the depth of diagnostic scanning required for the vehicle, including the diagnostic scanning programs to be used.
In one embodiment the diagnostic system reads a vehicle identification number (VIN) of the vehicle under evaluation, with the VIN being analyzed or parsed to determine the safety systems residing on the vehicle, and with the diagnostic system then utilizing an appropriate diagnostic scanning program for the given vehicle. Alternatively, the vehicle data information read by the diagnostic system comprises part numbers of electronic control units (ECUs) contained on the vehicle, with the ECU part numbers analyzed or parsed to determine which if any pertain to particular vehicle systems, such as vehicle ADAS safety systems, and with the diagnostic system then utilizing an appropriate diagnostic scanning program for the given vehicle. Less invasive diagnostic scanning programs may be utilized in instance in which it is determined that the vehicle is not equipped with particular vehicle systems, such as ADAS systems. In contrast, upon determination of the presence of safety systems, appropriate diagnostic scanning programs may be utilized that provide more in-depth scanning of the vehicle ECUs, such as to locate relevant fault or error codes.
According to an aspect of the present invention, a method of diagnosing a vehicle electrical system includes connecting a vehicle interface device with a diagnostic port of a vehicle so as to be in communication with an electrical system of the vehicle, reading vehicle data information of the vehicle with the vehicle interface device, determining whether particular electrical vehicle systems are present on the vehicle based on the vehicle data information, and selecting a diagnostic scanning program from a plurality of available diagnostic scanning programs based on said determining whether particular electrical vehicle systems are present, wherein the selected diagnostic scanning program is configured to determine fault codes in the electrical system of the vehicle. In particular this includes determining whether the vehicle includes Advanced Driver Assistance Systems (ADAS) electrical vehicle systems.
In particular embodiments reading vehicle data information of the vehicle comprises reading a vehicle identification number (VIN) of the vehicle, and determining whether particular electrical vehicle systems are present on the vehicle occurs via a database to analyze the VIN of the vehicle, where the database comprises a VIN database that includes information regarding the electrical vehicle systems present on the vehicle based on the VIN of the vehicle.
In alternative embodiments reading vehicle data information of the vehicle comprises reading electronic control unit (ECU) part numbers of the vehicle, and determining whether particular electrical vehicle systems are present on the vehicle comprises using a database to analyze the ECU part numbers of the vehicle, where the database comprises an ECU part number database that includes ECU part numbers for ADAS system ECUs.
A vehicle diagnostic system in accordance with the present invention includes a vehicle interface device configured to be operatively connected with a vehicle in order to diagnose an electrical system of the vehicle, a diagnostic evaluation program configured to query the electrical system of the vehicle when the vehicle interface device is connected with the vehicle, with the diagnostic evaluation program operative to read vehicle data information from the electrical system of the vehicle. The vehicle diagnostic system further includes a computer device communicatively connected with the vehicle interface device and operable to obtain the vehicle data information from the diagnostic evaluation program. The computer device is configured to access a database to determine whether the vehicle includes particular vehicle systems based on the vehicle data information to designate which diagnostic scanning program from a plurality of diagnostic scanning programs is to be used to diagnose the electrical system of the vehicle.
In a particular embodiment the vehicle interface device and computer device are separate devices connected by a cable or a wireless connection, with the computer device including the diagnostic evaluation program and a plurality of diagnostic scanning programs. In accordance with the invention the database may reside on the computer device, or may reside on a remote computer device.
The vehicle diagnostic system of the present invention enables repair facilities to accurately and efficiently scan/query a vehicle for fault codes by using the diagnostic scanning program that is most efficient and least expensive with respect to monetary cost and test duration for the given vehicle by scanning the vehicle electrical system based on the vehicle systems present on the vehicle, including any ADAS systems and associated ECUs on the vehicle. The ability to determine whether the vehicle under test is equipped with particular vehicle systems, such as ADAS ECUs, allows the system to selectively use a proprietary manufacturer supplied scanning program as needed, or use an alternative third-party supplied scanning program when the vehicle under test is not equipped with ADAS ECUs. These and other objects, advantages, purposes and features of this invention will become apparent upon review of the following specification in conjunction with the drawings.
The present invention will now be described with reference to the accompanying figures, wherein the numbered elements in the following written description correspond to like-numbered elements in the figures. A vehicle diagnostic system 20 for use with a vehicle 22 is shown for use by a mechanic or operator 24, such as in an automotive repair facility. System 20 is illustrated in
Vehicle diagnostic system 20 may be configured to be selectively operable in one of a plurality of different modes, whereby a technician may use the interface device for vehicle maintenance, diagnosis, programming and repair as needed. In accordance with an embodiment of the present invention, system 20 includes diagnostic applications 50a, including a diagnostic evaluation program application 51 (
In the illustrated embodiment computer 30 is operatively connected with vehicle interface device 28, with computer 30 including one or more commercially available diagnostic application scanning programs 53a, 53b that are configured for use with the specific vehicle 22 and may be used depending on the vehicle systems present on vehicle 22. Although shown as having two diagnostic application programs 53a, 53b, it should be appreciated that system 20 may include more than two such programs available for use with a given vehicle 22. Interface device 28 may be configured as an SAE standard J2534 device, such as a device compliant with the J2534-2 standard, or as an ISO compliant or other standard compliant device for supporting and enabling communication with the electronic systems of a vehicle.
As illustrated in
It should be appreciated that different vehicles may be equipped with different ECUs, including that some vehicles of the same make/model may have different or additional ECUs when compared to other vehicles of the same make/model. For example, a given vehicle may be sold with or without advanced driver-assistance systems (ADAS), such as adaptive cruise control, lane departure warning, parking assistance, blind spot detection, and other driver assistance systems. Each ADAS subsystem may include its own additional ECUs, or an ECU may be shared for more than one ADAS feature, where such additional ECUs must be queried/scanned, accessed, and then assessed. It should be appreciated that vehicles with the additional ADAS subsystems and corresponding additional ECUs will require a more extensive scanning program that is capable of interfacing with the additional ECUs of the equipped ADAS subsystems. Correspondingly, the same vehicle make and model without additional ADAS subsystems will not have the additional ECUs.
Interfacing and interrogation with every ECU of a vehicle allows all fault codes to be ascertained. An OEM supplied diagnostic scanning program may operate to perform an in-depth scan regardless of the vehicle configuration, including whether or not the vehicle includes ADAS systems, whereby all possible ECUs for a particular model of a vehicle are routinely queried by the vehicle diagnostic system 20 whether they are actually in the vehicle 22 or not. While a proprietary manufacturer supplied scanning program may provide an assurance that all ECUs on a vehicle under test have been queried/scanned and assessed, such scanning programs are often costly, including in terms of requiring a significant length of time to operate as the scanning program methodically queries/scans for each ECU the vehicle may be equipped with, whether or not the vehicle is in fact equipped with any given ECU, as well as having a substantial financial cost as there are monetary charges associated with utilizing the proprietary scanning program, including such as costs for each use or running of the proprietary scanning program. In accordance with aspects of the present invention, therefore, prior to running a diagnostic scanning program, an evaluation may be performed to determine the vehicle systems present on the subject vehicle and whereby a diagnostic scanning program may be selected that is suited to use with the vehicle, including to expedite the vehicle scanning and avoid unnecessary time and expense associated with running a diagnostic scanning program that is not required for the vehicle. Rather, a diagnostic scanning program may be run that is not configured to query all possible ECUs that a vehicle may possibly be equipped with, such as for example not querying ECUs associated with ADAS systems that are not present on the vehicle.
Accordingly, prior to selecting a diagnostic scanning program 53a, 53b for use with a given vehicle, a diagnostic evaluation program 51 may initially be run to read or obtain vehicle data information related to the equipped vehicle systems on the vehicle. In one embodiment the diagnostic evaluation program 51 obtains the vehicle VIN upon connection of system 20 with vehicle 22. As a first step, system 20 via the vehicle interface device 28 may initially acquire a vehicle identification number (VIN) associated with a vehicle under test. In an aspect of the present invention, the vehicle interface device 28 is operable to read the VIN from the vehicle 22 via its connection through the OBD2 diagnostic port 32. The vehicle VIN is then used to determine the vehicle systems equipped on the vehicle. For example, computer 30 may include a database 50b that is operatively used to determine the vehicle systems on the vehicle based on the determined VIN, such as via a VIN database. This may include an algorithmic lookup table based on the identified VIN, such as for example where certain alphanumeric characters of the VIN identify the presence or absence of particular vehicle systems present on the vehicle, such as ADAS systems or other vehicle or safety systems. In response to the identification of the vehicle systems an appropriate diagnostic scanning program 53a, 53b may be selected for use in scanning the electrical system of the vehicle. Alternatively, the VIN for the vehicle 22 may be acquired through alternative means and directly input by the operator 24, such as by being visually examined and input via interface 66, such as by way of a keyboard or touch screen. Moreover, rather than a lookup VIN database, the system 20 may operatively algorithmically analyze selected alphanumerical characters, such as by position number in the VIN, with the system 20 recognizing based on the particular character and location the presence or absence of particular vehicle systems present on the vehicle, such as being preprogrammed. This may include, for example, an operator initially entering a make and model of a vehicle via interface 66 whereby the system 20 is preconfigured to read particular characters in particular locations of the VIN in order to determine the presence or absence of particular vehicle systems present on the vehicle.
An exemplary embodiment of a database 50b configured as a VIN database is illustrated in
In a further alternative embodiment, system 20 may query the electronic system 23 of the vehicle 22 to obtain the part numbers of all ECUs resident on vehicle 22, where the ECU part numbers are readable via interface tool 28 and the connection with OBD diagnostic port 32. The ECU part numbers are then usable to determine which vehicle scanning program 53a, 53b to run. For example, database 50b may additionally or alternatively include an ECU part number database, where a comparison of ECU part numbers obtained via interface tool 28 with ECU part numbers in database 50b provides a decision as to which vehicle scanning program 53a, 53b to run. For example, upon a determination of the presence of one or more ECU part numbers associated with ADAS systems, a proprietary OEM vehicle scanning program application may be run. Alternatively, upon a determination that no ADAS systems are present on the vehicle, an aftermarket vehicle scanning program application may be run. Still further, it should be appreciated that yet other alternative vehicle scanning programs may be run depending on the specific ECUs present on the vehicle 22 under test. For example, programs may be available for vehicle configurations having particular ADAS systems that do not include other ADAS systems, whereby particular known ECUs present can be scanned while avoiding use of a diagnostic scanning program having superfluous capability and functionality.
An exemplary embodiment of a database 50b configured as an ECU database is illustrated in
The vehicle database 50b may further comprise a VIN/ECU part number database that includes a listing of ECU part numbers associated with a given VIN. Therefore, based upon a review of the VIN database and a review of the ECU part numbers associated with the current vehicle's VIN, a selection may be made between a third party supplied scanning program or a manufacturer supplied scanning program. For example, if the VIN database reveals that a given vehicle contains one or more ECU part numbers associated with ADAS ECUs, a decision can be made to select the more comprehensive manufacturer supplied scanning program. In the alternative, if a review of the VIN database reveals that the vehicle is not equipped with ADAS ECUs, the faster and less costly third-party supplied scanning program may be utilized. Such a decision may be aided if the VIN entry in the VIN database for an ADAS equipped vehicle includes at least one part number of an ADAS ECU associated with the VIN. Alternatively, the VIN entry in the VIN database for an ADAS equipped vehicle may include some other indication in the VIN database that the VIN is associated with an ADAS equipped vehicle. Therefore, if a vehicle's VIN entry in the VIN database does not include an ADAS ECU part number or some other indication that the VIN is for an ADAS equipped vehicle, the third-party supplied scanning program may be selected.
Still further, system 20 may be configured to accept operator input to obtain vehicle data information used to select a desired diagnostic evaluation program 53a, 53b appropriate to a particular vehicle 22 under test. For example, system 20 may prompt an operator 24 to enter vehicle make and model information, such as via interface 66. System 20 may then provide step-by-step inquiries to operator 24 regarding systems installed on vehicle 22, such as whether vehicle 22 includes particular cameras at particular locations, or specifically whether vehicle 22 has particular ADAS systems. Upon entering this information into system 20, system 20 may then selectively activate an appropriate diagnostic evaluation program 53a, 53b for the vehicle 22.
Although database 50b is disclosed above as residing in local computer 30, such a database may additionally or alternatively reside in a memory 44 of vehicle interface device 28 and/or in the memory of a remote computer, such as a remote server 64. If the database is located in a remote server 64, the vehicle interface device 28 and/or the computer 30 may access the database via their respective Internet interfaces 68, 52. Optionally, the database, such as a database found on the remote computer or server 64, may be a compiled database of VINs and/or ECUs provided by a third party. Still further, the database found in either of the memories 44, 50 of the vehicle interface device 28 or the computer 30, respectively, may be a local database that comprises a portion of the information, where the database found on the remote computer or server 64 is remote and contains additional or alternative information. For example, the database may be progressively expanded to include those VINs and/or associated ECU part numbers for vehicles previously serviced at a particular service station or automotive repair business. Optionally, the database may be updated, such that an operator may add a new vehicle VIN and associated ECU part numbers. The database may thus be a tool for identifying which vehicles are equipped with ADAS subsystems and therefore need to be queried/scanned with a more in-depth scanning program, such as a manufacturer supplied scanning program.
Computer 30 may, either in addition to the above noted various loaded diagnostic applications or in place thereof, be used to access remotely located diagnostic applications, such as that may reside on remotely located servers 64. This may be done, for example, to avoid the need for obtaining and locally storing and maintaining diagnostic applications on computer 30. In the illustrated embodiment, computer 30 includes an input/output (I/O) interface 66 for coupling to peripheral devices, such as one or more of a monitor, keyboard, mouse, and the like. In a further illustrated embodiment, the computer 30 is implemented as a laptop computer with integrated monitor, keyboard, and mouse. Still further, interface device 28 and computer 30 may be structurally integrated.
A method for selecting a scanning program in accordance with aspects of the present invention is illustrated in
In step 210 of
When the vehicle's VIN and/or ECU part numbers are not associated with information within a compared database, in an aspect of the present invention, the VIN and ECU part numbers may be separately investigated for updating of the databases. Alternatively, the vehicle 22 may be physically inspected for the presence or absence of particular vehicle systems, such as ADAS systems, with the appropriate diagnostic evaluation program being run based thereon.
As noted, a user interface on either of the vehicle interface device 28 and the computer 30 allows for the operator 24 to directly enter information into system 20. The same user interface may also be used to enter notations regarding the presence or absence of ADAS subsystems in the vehicle 22. It is also understood that the controller 29 of the vehicle interface device 28 may alternatively be configured to perform the database searching and the scanning program selection discussed above. Alternatively, the computer 30 is operable to perform the database searching and the scanning program selection discussed above.
System 20, in addition to performing scanning operations, may also be used for reprogramming of vehicle 22, such as reprogramming selected ECUs, including reprogramming ECUs based on a determination of particular fault codes.
In the above discussed embodiments, the vehicle interface device 28 and the computer 30 are shown as separate components that are linked together, such as by way of a cable 72. In an alternative embodiment, however, the vehicle interface device 28 and the computer 30 may be integrated together to operate as a vehicle maintenance computer system, as indicated by reference number 76 in
Although vehicle interface device 28 is discussed above as conforming with the SAE J2534 standard, it should be appreciated that alternatively configured vehicle diagnostic and programming tools may be employed within the scope of the present invention, including alternatively configured tools for alternative types of vehicles, such as alternative classes of vehicles. Accordingly, an interface tool may conform with the ISO 22900 standard, or RP1210 standard, or may operate under the ELM327 command protocol.
As noted, the software and/or hardware of diagnostic and programming tools may be required to be updated to operate with new vehicles and/or enable programming and diagnosing of existing vehicles. In the above noted embodiments the vehicle interface device 28 may be periodically updated via an Internet connection, such as via computer 30, or may be returned to the supplier for updating, including with regard to hardware updates. This may be done by the supplier of the vehicle interface device 28 whereby the local operator 24 need not spend time attempting to maintain the equipment.
In the illustrated embodiment local computer 30 is disclosed as including both the diagnostic evaluation program 51 as well as multiple diagnostic scanning programs 53a, 53b. It should be appreciated that alternative arrangements may be employed within the scope of the present invention. For example, program 51 and/or programs 53a, 53b may reside on different devices. In one alternative diagnostic evaluation program may reside on a vehicle scan device 28. Likewise, diagnostic scanning programs 53a, 53b may reside on different computer devices from each other. For example, an operator 24 may first utilize one device with a diagnostic evaluation program 51 to determine which diagnostic evaluation program is appropriate for the vehicle 22, and then select from alternative computer devices to run the determined diagnostic evaluation program. Still further, although diagnostic evaluation program 51 and diagnostic scanning programs 53a, 53b are illustrated and discussed herein as being separate programs, one or more of such programs may be combined together and operate as subroutines.
The vehicle interface device 28, with or without the computer 30, may be used to scan ECUs of a vehicle under test for error codes while using a scanning program that performs a minimum number of ECU queries possible, while also querying any ADAS ECUs in the vehicle. Less costly and faster scanning programs, such as third-party supplied scanning programs may be used instead of a manufacturer supplied scanning program when, for example, there are no ADAS ECUs in the vehicle under test. A manufacturer supplied scanning program may be used, however, when the vehicle under test includes ADAS ECUs to insure an in-depth scanning of the electrical system 23 of the vehicle 22. Thus, when appropriate, a vehicle under test may be scanned for ECU error codes using a more efficient and minimally expensive with respect to monetary cost and test duration scanning program that queries/scans a substantial majority of the vehicle's ECUs.
Changes and modifications in the specifically described embodiments can be carried out without departing from the principles of the present invention which is intended to be limited only by the scope of the appended claims, as interpreted according to the principles of patent law including the doctrine of equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6154658 | Caci | Nov 2000 | A |
| 6728603 | Pruzan et al. | Apr 2004 | B2 |
| 6879894 | Lightner et al. | Apr 2005 | B1 |
| 6956501 | Kitson | Oct 2005 | B2 |
| 7092803 | Kapolka et al. | Aug 2006 | B2 |
| 7373226 | Cancilla et al. | May 2008 | B1 |
| 7502672 | Kolls | Mar 2009 | B1 |
| 7519458 | Buckley | Apr 2009 | B2 |
| 7532962 | Lowrey et al. | May 2009 | B1 |
| 7584030 | Graham | Sep 2009 | B1 |
| 7786851 | Drew et al. | Aug 2010 | B2 |
| 7840812 | Levenberg | Nov 2010 | B1 |
| 7928837 | Drew et al. | Apr 2011 | B2 |
| 8190322 | Lin et al. | May 2012 | B2 |
| 8259936 | Mahalingaiah | Sep 2012 | B2 |
| 8306687 | Chen | Nov 2012 | B2 |
| 8339254 | Drew et al. | Dec 2012 | B2 |
| 8352577 | Martone | Jan 2013 | B2 |
| 8638207 | Drew et al. | Jan 2014 | B2 |
| 8688313 | Margol et al. | Apr 2014 | B2 |
| 8909416 | Chen et al. | Dec 2014 | B2 |
| 8918245 | Dewhurst et al. | Dec 2014 | B2 |
| 9430884 | Drew et al. | Aug 2016 | B2 |
| 9530255 | Drew et al. | Dec 2016 | B2 |
| 9563988 | Drew et al. | Feb 2017 | B2 |
| 9646130 | Drew et al. | May 2017 | B2 |
| 10013816 | Nassar et al. | Jul 2018 | B2 |
| 10146521 | West et al. | Dec 2018 | B2 |
| 10181225 | Liebl et al. | Jan 2019 | B2 |
| 10282924 | Drew et al. | May 2019 | B2 |
| 10414277 | Herron et al. | Sep 2019 | B1 |
| 10445953 | Herron et al. | Oct 2019 | B1 |
| 10706645 | Herron et al. | Jul 2020 | B1 |
| 10719813 | Beckmann et al. | Jul 2020 | B1 |
| 10748356 | Herron et al. | Aug 2020 | B1 |
| 11062534 | Jingle et al. | Jul 2021 | B2 |
| 20010056544 | Walker | Dec 2001 | A1 |
| 20030001720 | Wade et al. | Jan 2003 | A1 |
| 20030020759 | Cancilla et al. | Jan 2003 | A1 |
| 20040044454 | Ross et al. | Mar 2004 | A1 |
| 20040167689 | Bromley et al. | Aug 2004 | A1 |
| 20050021294 | Trsar et al. | Jan 2005 | A1 |
| 20050038581 | Kapolka et al. | Feb 2005 | A1 |
| 20050060070 | Kapolka et al. | Mar 2005 | A1 |
| 20050182537 | Tefft et al. | Aug 2005 | A1 |
| 20050240555 | Wilde et al. | Oct 2005 | A1 |
| 20050251304 | Cancellara et al. | Nov 2005 | A1 |
| 20060052921 | Bodin et al. | Mar 2006 | A1 |
| 20060106508 | Liebl et al. | May 2006 | A1 |
| 20060211446 | Wittmann et al. | Sep 2006 | A1 |
| 20070005201 | Chenn | Jan 2007 | A1 |
| 20070043488 | Avery et al. | Feb 2007 | A1 |
| 20070050105 | Chinnadurai et al. | Mar 2007 | A1 |
| 20070055420 | Krzystofczyk et al. | Mar 2007 | A1 |
| 20070073460 | Bertosa et al. | Mar 2007 | A1 |
| 20070185624 | Duddles et al. | Aug 2007 | A1 |
| 20070204215 | Mueller et al. | Aug 2007 | A1 |
| 20070233340 | Raichle et al. | Oct 2007 | A1 |
| 20080177438 | Chen et al. | Jul 2008 | A1 |
| 20080269975 | Bertosa | Oct 2008 | A1 |
| 20080280602 | Ban | Nov 2008 | A1 |
| 20080306645 | Dewhurst | Dec 2008 | A1 |
| 20090062978 | Picard | Mar 2009 | A1 |
| 20090118899 | Carlson | May 2009 | A1 |
| 20090119657 | Link, II | May 2009 | A1 |
| 20090187976 | Perroud et al. | Jul 2009 | A1 |
| 20090265055 | Gillies | Oct 2009 | A1 |
| 20090276115 | Chen | Nov 2009 | A1 |
| 20100042287 | Zhang | Feb 2010 | A1 |
| 20100174446 | Andreasen et al. | Jul 2010 | A1 |
| 20100204878 | Drew et al. | Aug 2010 | A1 |
| 20100205450 | Sarnacke | Aug 2010 | A1 |
| 20100262335 | Brozovich | Oct 2010 | A1 |
| 20110071709 | Damiani et al. | Mar 2011 | A1 |
| 20110112718 | Claus | May 2011 | A1 |
| 20110153150 | Drew et al. | Jun 2011 | A1 |
| 20110276218 | Dwan | Nov 2011 | A1 |
| 20110313593 | Cohen et al. | Dec 2011 | A1 |
| 20120046826 | Panko | Feb 2012 | A1 |
| 20120254345 | Montoya | Oct 2012 | A1 |
| 20140279230 | Bertosa et al. | Sep 2014 | A1 |
| 20150121275 | Marshall et al. | Apr 2015 | A1 |
| 20170301154 | Rozint | Oct 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2004092857 | Oct 2004 | WO |
| Entry |
|---|
| Article entitled “Remote Vehicle Diagnostic System Using Mobile Handsets” by Doo-Hee Jung, Gu-Min Jeong, and Hyun-Sik Ahn, understood to be from the proceedings of the Jun. 2006 International Conference on Wireless Networks, ICWN 2006, Las Vegas, Nevada. |
| Thesis by Alexander Ellery, entitled, “Systems Design & Control of a Freeflying Space Robotic Manipulation System (ATLAS) for In-Orbit Satellite Servicing Operations”, Published 1996, Cranfield University, College of Aeronautics. |
