A trouble diagnosing device connectable to an ECU mounted on a vehicle and equipped with a memory to store current trouble information and past trouble information, and the trouble diagnosing device includes a display screen to display a diagnosed trouble state, and a simultaneous display unit to call trouble information stored in the memory and make both of the current trouble information and past trouble information displayed at a same time on the display screen.
|
9. A trouble diagnosing device connectable to an electronic control unit mounted on a vehicle, the trouble diagnosing device comprising:
a trouble storing unit for storing current trouble information and past trouble information;
a display screen for displaying a diagnosed trouble state;
a simultaneous display unit for displaying both the current trouble information and the past trouble information at a same time on the display screen; and
a trouble information erasing unit for instructing erasing of certain trouble information of at least one group of the current trouble information or the past trouble information stored in the trouble storage unit while the current trouble information and past trouble information are being displayed on the display screen.
1. A trouble diagnosing device connectable to an electronic control unit mounted on a vehicle and equipped with a trouble storing unit configured to store current trouble information and past trouble information, the trouble diagnosing device comprising:
a display screen configured to display a diagnosed trouble state, the display screen including a current trouble information display section and a past trouble information display section; and
a simultaneous display unit configured to call trouble information stored in the trouble storing unit and make both of the current trouble information and past trouble information displayed at a same time on the current trouble information display section and the past trouble information display section of the display screen,
wherein the simultaneous display unit displays at the same time the current and past trouble information including the same trouble information and the current and past trouble information display sections, respectively.
2. The trouble diagnosing device according to
3. The trouble diagnosing device according to
a trouble information erasing unit configured to instruct erasing of certain trouble information of at least one group of the current trouble information or the past trouble information stored in the trouble storage unit while the current trouble information and past trouble information are being displayed on the display screen.
4. The trouble diagnosing device according to
5. The trouble diagnosing device according to
6. The trouble diagnosing device according to
7. The trouble diagnosing device according to
8. The trouble diagnosing device according to
|
This application is based upon and claims the benefit of priority from prior Japanese Patent Application No. 2003-290196, filed Aug. 8, 2003, the entire contents of which are incorporated herein by reference.
1. Field of the Invention
The present invention relates to a trouble diagnosing device that diagnoses a trouble of a vehicle such as a track or a bus, as the device is coupled with an ECU (electronic control unit) mounted on the vehicle.
2. Description of the Related Art
As shown in
The trouble diagnosis device 1 includes a display unit 5, an “S” key 6a, a “C” key 6b, a cursor key 7, an “YES” key 8a, a “NO” key 8b and function keys 9.
The trouble diagnosing device 1 can display a diagnosis code generated while the vehicle is running, on a display unit 5.
For example, when a self-diagnostic mode is set by manipulating a particular key, the trouble diagnosing device 1 transmits to the ECU 3 a command instructing to read the current diagnosis codes stored in the current trouble information region of the memory 4. Consequently, the current diagnosis codes are displayed on the display unit 5 as shown in
For maintenance, it is necessary to know the past diagnosis codes. To display the past codes, for example, the “S” key 6a was assigned for this operation. As the “S” key 6a is operated, the trouble diagnosing device 1 transmits to the ECU 3 a command of reading out the past diagnosis codes stored in the past trouble information region of the memory 4 of the ECU 3. Consequently, the past diagnosis codes are displayed on the display unit 5.
As described above, in order to display past diagnosis codes on the display unit 5, the key operation described above must be performed, but this operation is laborious and therefore it makes the maintenance work more complicated.
Further, for the repair of a broken-down vehicle, not only current diagnosis codes but also past diagnosis codes are important data. Nevertheless, if one mechanic takes a memo of the information of the diagnosis codes displayed on the display unit 5, and passes it to another mechanic, there results in some cases such confusion that it is not clear as to whether a diagnosis code on the memo indicates a current diagnosis code or a past diagnosis code. When such confusion occurs, it is very difficult to investigate the cause for the trouble.
The present invention has been proposed in consideration of the above-described points, and the object thereof is to provide a trouble diagnosing device with an improved ease of maintenance and repair using diagnosis codes stored in an electronic control device equipped with a diagnostic function and capable of easily investigating the cause for a trouble.
According to an aspect of the present invention, there is provided a trouble diagnosing device connectable to an electronic control unit mounted on a vehicle and equipped with a trouble storing unit configured to store current trouble information and past trouble information, the trouble diagnosing device comprising: a display screen configured to display a diagnosed trouble state; and a simultaneous display unit configured to call trouble information stored in the trouble storing unit and make both of the current trouble information and past trouble information at a same time on the display screen.
Additional objects and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be leaned by practice of the invention. The objects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out hereinafter.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate presently preferred embodiments of the invention, and together with the general description given above and the detailed description of the preferred embodiments given below, serve to explain the principles of the invention.
An embodiment of the present invention will now be described with reference to accompanying drawings.
The VCI 12 has a function of converting a communication specification used for the ECU 13 into a communication specification used for the PC 11. The VCI 12 has a built-in microprocessor and has a memory 12m inside.
As described above, the trouble diagnosing device itself is pre-equipped with the interface equipment serving as an interface with the electronic control unit mounted on the vehicle. Thus, it is not necessary to particularly prepare a separate interface equipment. Therefore, the operation for matching the specifications with each other can be omitted and therefore the increase in production cost can be suppressed.
The ECU 13 has a diagnostic function. The diagnostic function means a self-diagnostic function. That is, the ECU 13 monitors input signals from various types of sensors, an actuator and switch, and when some abnormality occurs in anyone of the input signals, the ECU 3 stores the contents of the abnormality (diagnosis code) or the data at the time the abnormality occurred in the memory 13m as maintenance and repair data.
A predetermined area of the memory 13m further includes a current trouble information region 13a for storing current diagnosis codes, as shown in
As described above, the current trouble information region 13a is capable of storing eight current diagnosis codes at the maximum. For example, in the case where three current diagnosis codes are already stored in the current trouble information region 13a, and additional diagnosis codes that are the same as any of these three already stored codes are generated, the three already stored diagnosis codes are maintained as they are.
In the case where eight current diagnosis codes are already stored in the current trouble information region 13a, and a new current diagnosis code is generated, the oldest one of the already stored eight current diagnosis codes is deleted, and then the new current diagnosis code is stored in the current trouble information region 13a.
Next, the structure of the PC 11 will now be described with reference to
The HDD 26 stores a trouble diagnostic program for executing the diagnostic functions.
The trouble diagnostic program includes the following programs:
(1) A main program as illustrated in
(2) A program for displaying an image corresponding to a touch button displayed on the display 25 when an operator touches the button, and a program for executing a process designated by the button.
The details of these programs are as follows. For example, one of these corresponds to simultaneous display unit for displaying current diagnosis codes, past diagnosis codes, and a total number of each type of codes simultaneously on the display screen 31. These data are displayed as a command for reading the current diagnosis codes and past diagnosis codes stored in the current trouble information region 13a and past trouble information region 13b, respectively, a command for reading the total number of the current diagnosis codes and past diagnosis codes, etc., are output to the ECU 13 with the touch of a “self-diagnosis” button of the function menu, which will be described later. Another program corresponds to a trouble information erasing unit for instructing the ECU 13 to erase certain diagnosis codes of at least one type of the current diagnosis codes and past diagnosis codes stored in the current trouble information region 13a and past trouble information region 13b, respectively, with the touch of an “eraser” button 43. Still another program corresponds to a printing unit for printing a presently displayed image by transmitting the data corresponding to an image presently shown on the display screen 31 to a printer (not shown) via the printer I/F 28. Still another program corresponds to a dialog-type trouble diagnosing unit for performing a dialog-type troubleshooting with the touch of a “code-by-code troubleshooting” button 42.
It should be noted here that the RAM 23 has various work areas.
Next, the operation will now be described. The members are connected to each other as shown in
First, a startup image as shown in
This function selection image presents buttons for the “self-diagnosis”, . . . , “calibration”, . . . .
When the “self-diagnosis” is selected from this image, what is shown in
The display screen 31 illustrated in
On the left-hand side of the display screen 31, a current trouble information display section 32 which is capable of five displaying current diagnosis codes at the maximum is provided, whereas a past trouble information display section 33 which is capable of five displaying past diagnosis codes at the maximum is provided.
More specifically, the current trouble information display section 32 is provided with five independent cells 32a to 32e in which trouble information are indicated, and similarly, the past trouble information display section 33 is provided with five independent cells 33a to 33e. A width a of each of the cells 32a to 32e and cells 33a to 33e is about 0.39 inch (=1 cm) to 0.79 inch (=2 cm) when the display screen has a size of 12.1 inches.
As described above, when the display screen has a size of 12.1 inches (the length of a diagonal line of the screen image is about 31 cm), each of the cells 32a to 32e is displayed to have such a large width of about 0.39 inch (=1 cm) to 0.79 inch (=2 cm). With this size, if each cell of the trouble diagnosing device is manipulated by an operator in a maintenance and repair shop with work gloves on, the possibility of the operating error can be significantly reduced.
In the case where the display screen 31 has a size of 15 inches, it is preferable that the width of each of the cells 32a to 32e should be set to about 0.49 inch (=1.24 cm) to 0.98 inch (=2.48 cm).
In the case where the display screen 31 has a size of 17 inches, it is preferable that the width of each of the cells 32a to 32e should be set to about 0.56 inch (=1.41 cm) to 1.11 inches (=2.82 cm). Thus, the width of each cell should preferably be set to about 1/30 to 1/15 of the length of a diagonal line of the screen image.
DCT indicated at the top section of the current trouble information display section 32 is the abbreviation of diagnosis trouble code, which means current diagnosis node.
The contents shown in
As described above, when the “self diagnosis” button of the function display image is manipulated, current diagnosis codes and past diagnosis codes are indicated in the current trouble information display section 32 and the past trouble information display section 33, respectively, at the same time on the display screen 31 so that they can be compared and contrasted with each other. In this manner, troubles that occurred in the past and those occurred this time can be easily compared with each other. Thus, it is possible to recognize the past troubles and current troubles at a glance without switching the images during the repair. Therefore, the ease of repair can be improved.
Further, the current trouble information display section 32 includes in its lower portion a total trouble count indicating section 34a that indicates the total number of current diagnosis codes. Similarly, the past trouble information display section 33 includes in its lower portion a total trouble count indicating section 34b that indicates the total number of past diagnosis codes. The total number of current diagnosis codes indicated in the total trouble count indicating section 34a and the total number of past diagnosis codes indicated in the total trouble count indicating section 34b can be obtained by counting, on the PC 11 side, the number of current diagnosis codes and the number of past diagnosis codes, respectively, which have been transmitted from the ECU 13.
According to the embodiment, the total number of each group of the present and past diagnosis codes is indicated, and therefore it is possible to know whether there are more data present that cannot be displayed in the current trouble information display section 32 and past trouble information display section 33. Thus, it is very hard to miss even those diagnosis codes that are not displayed in the image screen.
Further, the total number of each of the current and past diagnosis codes is displayed, and therefore it is possible to know how serious is a trouble at a glance, and to know the frequency of troubles of the ECU 13.
For example, in the example shown in the figure, three current diagnosis codes are indicated in the current trouble information display section 32, and the count indicated in the total trouble count indicating section 34a is “3”. Therefore, in this case, it is possible to understand that all of the current diagnosis codes are presently indicated in the current trouble information display section 32.
Suppose here the case where five current diagnosis codes are indicated in the current trouble information display section 32 and the count indicated in the total trouble count indicating section 34a is “8”. In this case, three current diagnosis codes remain not displayed. In order to display these three remaining current diagnosis codes on the current trouble information display section 32, the data can be scrolled on the screen by appropriately manipulating the cursor buttons 35 and 36 provided on the right-hand side of the current trouble information display section 32.
Cursor buttons 37 and 38 designed to scroll displayed data are displayed on the right-hand side of the past trouble information display section 33.
Thus, with the total number of each group of the current and past diagnosis codes displayed, it is possible to know how serious is a trouble at a glance, and to know the frequency of troubles of the ECU 13 as a whole.
Further, the section of the menu bar provided in the lowermost section of the display screen 31 displays the display button 41 for printing the contents presently shown on the display screen 31, the “code-by-code troubleshooting” button 42 for performing a dialog-type troubleshooting, and the “eraser” button 43 for erasing certain diagnosis codes of at least one group of the current diagnosis codes and past diagnosis codes stored in the current trouble information display section 32 and past trouble information display section 33, respectively.
For example, when the printing button 41 is manipulated by touching it, the contents of the current display screen 31 are printed and output from a printer (not shown) connected the printer I/F 28.
Thus, the current diagnosis codes and past diagnosis codes are printed at the same time on the same sheet, the record of maintenance and repair can be easily and accurately formed. Further, for printing, it suffices only if the printing button 41 is touched, and thus the printing order can be easily made. Furthermore, by having the current trouble data and past trouble data on a print, the data can be accurately passed on to another mechanic who next takes case of the vehicle, thereby making it possible to improve the efficiency of the maintenance and repair.
Moreover, when one of the cells 32a to 32e in which current diagnosis codes or past diagnosis codes are displayed is selected by touching it, and then the “code-by-code troubleshooting” button 42 is touched, the dialog-type trouble diagnosis corresponding to the selected diagnosis code is started. In other words, under what conditions the selected diagnosis code occurred is indicated on the displayed image 31, and the maintenance and repair data stored in the memory 13m of the ECU 13 are displayed. Thus, with these displayed data, the inspection procedure can be carried out in a dialog manner.
As described above, an operator can easily take care of the trouble without referring to the maintenance and repair guidebook.
On the other hand, when at least one of the current trouble information display section 32 and past trouble information display section 33 is selected by touching it, and then the “eraser” button 43 is touched, the data of the selected one of the current diagnosis codes and past diagnosis codes are erased from the memory 13m.
In this manner, for example, when the cause for a trouble is investigated and the troubled part is repaired in a maintenance and repair shop, the current diagnosis codes and past diagnosis codes can then be erased to start a new self-diagnosis.
In case where a vehicle with a trouble is brought in a maintenance and repair shop, but the trouble is not detected as current trouble information, such a conduct that easily causes a trouble as shaking a part to be inspected is performed. If trouble information corresponding to the inspected part is detected as current trouble information after this conduct, it can be judged that the inspected part is broken. Thus, it is possible to carry out the investigation of the cause for a trouble.
It should be noted here that it is alternatively possible to print out those current diagnosis codes and past diagnosis codes that are not displayed in the display screen 31 when the printing button 41 is touched, as well if there are any.
In the above-described embodiment, the total number of each group of the current diagnosis codes and past diagnosis codes transmitted from the ECU 13 is counted on the PC 11 side; however it is alternatively possible to count the total number on the ECU 13 side, and transmit it to the PC 11.
The renewal manner of the current diagnosis codes stored in the current trouble information region 13a of the memory 13m and the past diagnosis codes stored in the past trouble information region 13b, which was described with reference to
It should be noted that in the above-described embodiment, the programs that correspond to various units are stored in the HDD 26; however the present invention is not limited to this, but it is alternatively possible to store these programs in an external storage means such as a CD-ROM or FD, and download them to the HDD 26 of the PC 11 as needed.
Further, in the above-described embodiment, a touch panel-type display is used; however in the case of a PC that does not equipped with a touch panel-type display, each operation can be assigned with use of a mouse.
Additional advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described herein. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents.
Kawauchi, Hiroshi, Kitajima, Akihisa
Patent | Priority | Assignee | Title |
7634337, | Dec 29 2004 | Snap-On Incorporated | Vehicle or engine diagnostic systems with advanced non-volatile memory |
7937198, | Dec 29 2004 | Snap-On Incorporated | Vehicle or engine diagnostic systems supporting fast boot and reprogramming |
9951705, | Apr 23 2008 | Denso Corporation | Control unit and program for same |
Patent | Priority | Assignee | Title |
5648902, | Jul 27 1994 | HND Co., Ltd. | Method for measuring a damping force of a shock absorber in a suspension system for a motor vehicle and a measuring system thereof |
5774361, | Jul 14 1995 | Hunter Engineering Company | Context sensitive vehicle alignment and inspection system |
5909379, | Oct 19 1995 | SNAP-ON TECHNOLOGIES, INC | Custom vehicle wheel aligner |
5968108, | Jul 18 1997 | Honda Giken Kogyo Kabushiki Kaisha | Vehicle diagnosing apparatus |
6141608, | Oct 28 1997 | Snap-On Tools Company | System for dynamic diagnosis of apparatus operating conditions |
6181992, | Jun 25 1993 | FCA US LLC | Automotive diagnostic service tool with hand held tool and master controller |
6327525, | Aug 10 2000 | Ford Global Technologies, Inc. | Vehicle suspension ride control diagnostic testing |
6370455, | Sep 05 2000 | Hunter Engineering Company | Method and apparatus for networked wheel alignment communications and service |
6411874, | Aug 18 1997 | Texas A&M University Systems | Advanced law enforcement and response technology |
6542794, | Jan 28 1997 | TALKING QUICK TIPS, INC | Technique for effectively communicating information concerning vehicle service providers to a user |
6615120, | Oct 28 1997 | Snap-on Technologies, Inc. | System for dynamic diagnosis of apparatus operating conditions |
6714846, | Mar 20 2001 | SNAP-ON TECHNOLOGIES, INC | Diagnostic director |
6845307, | Oct 28 1997 | Snap-On Incorporated | System for dynamic diagnosis of apparatus operating conditions |
20010029410, | |||
20030187556, | |||
20050065680, | |||
20050137762, | |||
DE19712924, | |||
EP922952, | |||
JP11144042, | |||
JP2000146766, | |||
JP2000240495, | |||
JP2002091545, | |||
JP200291545, | |||
JP2110337, | |||
JP2308951, | |||
JP4304589, | |||
KR20000028587, | |||
KR20000059333, | |||
WO39556, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Aug 04 2004 | Mitsubishi Fuso Truck and Bus Corporation | (assignment on the face of the patent) | / | |||
Sep 03 2004 | KAWAUCHI, HIROSHI | Mitsubishi Fuso Truck and Bus Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016039 | /0145 | |
Sep 03 2004 | KITAJIMA, AKIHISA | Mitsubishi Fuso Truck and Bus Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 016039 | /0145 |
Date | Maintenance Fee Events |
Aug 04 2008 | ASPN: Payor Number Assigned. |
Dec 12 2011 | REM: Maintenance Fee Reminder Mailed. |
Apr 29 2012 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
Date | Maintenance Schedule |
Apr 29 2011 | 4 years fee payment window open |
Oct 29 2011 | 6 months grace period start (w surcharge) |
Apr 29 2012 | patent expiry (for year 4) |
Apr 29 2014 | 2 years to revive unintentionally abandoned end. (for year 4) |
Apr 29 2015 | 8 years fee payment window open |
Oct 29 2015 | 6 months grace period start (w surcharge) |
Apr 29 2016 | patent expiry (for year 8) |
Apr 29 2018 | 2 years to revive unintentionally abandoned end. (for year 8) |
Apr 29 2019 | 12 years fee payment window open |
Oct 29 2019 | 6 months grace period start (w surcharge) |
Apr 29 2020 | patent expiry (for year 12) |
Apr 29 2022 | 2 years to revive unintentionally abandoned end. (for year 12) |