KR20120112299A - Method for maintenance of a motor vehicle and computer-readable memory media on which a computer program for maintenance of a motor vehicle is stored - Google Patents

Abstract

PURPOSE: An auto repair method and an electronically readable memory medium including a computer program for auto repair are provided to easily check a statement about a vehicle and easily update an ECU(Electronic Control Unit) used for the vehicle. CONSTITUTION: A parameter set is obtained from a vehicle statement file as a parameter setting module is executed. The vehicle statement file stored in a memory is read through a data bus(4) as plural program modules are executed. Electronic devices(3) are programmed through the data bus by the parameter set obtained from the vehicle statement file.

Description

METHOD FOR MAINTENANCE OF A MOTOR VEHICLE AND COMPUTER-READABLE MEMORY MEDIA ON WHICH A COMPUTER PROGRAM FOR MAINTENANCE OF A MOTOR VEHICLE IS STORED}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a vehicle maintenance method for servicing an automobile comprising a communication bus and a computer readable memory medium having stored thereon a computer program for servicing the automobile.

In order to increase efficiency and flexibility, transportation technology has evolved to use more and more network solutions to control various types of devices and processes in vehicles. For example, the Controller Area Network (CAN) standard specifies the means of achieving such networks that are widely used in trucks, buses and other vehicles. A bus device called Keyword 2000 also makes it possible to interconnect different CANs to form a federated network (keyword 2000 network). Thus, a federated network may include multiple CANs that are operated and controlled simultaneously.

So-called on-board diagnostic (OBD) systems can be used to check whether a particular control device connected to CAN is operating properly. Embedded diagnostic facilities, such as dashboard mounted video display devices, provide access to information generated by the embedded diagnostic system.

There may be multiple vehicle control devices installed in each CAN and controlled by the network. It is well known to have vehicle component modules installed to control various vehicle components such as lights, brakes and automatic transmissions. In general, the vehicle component module is programmable, so that the function of the vehicle can be changed somewhat according to the needs of the purchaser. An error code is generally stored in such a vehicle module, and the error code is intended to indicate a case in which a vehicle component malfunctions.

Because of the complexity of modern vehicles and the many features available to consumers, the vehicle module code has become very extensive. When the vehicle is under inspection, a computer may be connected to the vehicle to receive information from the vehicle module. This information may include the aforementioned error code as well as the vehicle module code. However, the vehicle module code is so extensive that it becomes difficult for the inspection staff to outline how the vehicle works.

During the service life of a vehicle, it is common for a vehicle owner to change the vehicle in some fashion, just as a vehicle repairs. If the vehicle has been modified or repaired and the control module has been replaced with a non-standard control module, the technical manual no longer fits the vehicle, making it difficult for the maintenance staff to repair the vehicle.

U.S. Patent No. 6,434,455 discloses a logistic service system that includes a reprogrammable vehicle module. The vehicle module stores an error code indicating when a vehicle component malfunctions. According to US Pat. No. 6,434,455, the vehicle can be connected to the inspection computer and back to a central server. The inspection computer can read the information from the vehicle and send it to the central server. Check information may also be stored at the central server. This inspection information can be used to know the inspection history of the vehicle the next time the vehicle comes to the repair shop. However, the U.S. patent does not address the difficulty of the inspection staff in reading the vehicle module code and the tracking of changes made to the vehicle.

DaimlerChrysler AG, Coventry, 1999. "Exact configuration onboard" of the ERA Conference p. 5.2.1 ff describes the problem of documentation of different models of vehicles. According to the above document, this problem is solved by storing product data in the vehicle itself. Product data may include changes made to the vehicle as well as information on vehicle inspection. However, these data do not solve the problem of technical information readily available to the inspection staff.

In addition, the prior art does not describe how product data or technical information should be stored to enable reprogramming when a control device is replaced with a non-standard control device.

Accordingly, there is a need for a vehicle that solves at least one of the problems noted above and a method for such a vehicle.

The present invention aims to provide an apparatus, a method and a computer program which solve at least one of the above mentioned problems.

It is an object of the present invention to provide a vehicle maintenance apparatus, a method and a computer program which provide means for an uncomplicated modification of the vehicle.

Another object of the present invention is to provide a vehicle maintenance apparatus, a method and a computer program that enable the inspection staff to easily read the specification for the vehicle.

It is yet another object of the present invention to provide an apparatus, a method and a computer program which make it easy to update an electronic control unit (ECU) for use in motor vehicles.

At least one of the above objects is achieved with an apparatus, a computer program and a method according to the appended independent claims.

Other objects and effects are apparent from the dependent claims.

At least one controllable vehicle component, a data bus and at least one electronic control device connected to the data bus and configured to control at least one of the controllable vehicle components, each of which is controlled by its own parameter set An automobile maintenance apparatus for servicing a vehicle comprising a programmable electronic control device and a memory specification file containing information relating to a parameter set of the electronic control device and a memory coupled to the data bus, the vehicle maintenance device comprising: a vehicle; A car maintenance apparatus is provided that includes a device connector for connecting to said data bus. The motor vehicle maintenance apparatus reads a parameter setting module configured to obtain a parameter set from the vehicle specification file, the vehicle specification file stored in the memory via the data bus, and a parameter obtained from the vehicle specification file by the parameter setting module. A plurality of program modules configured to program the electronic control device via the data bus by a set. The vehicle maintenance apparatus includes the vehicle specification file and the at least one electronic control device each including a vehicle identification number, wherein the plurality of program modules also identify the vehicle from the at least one electronic control device via the data bus. Read the number and compare it with the vehicle identification number in the vehicle specification file, and program the electronic control device based on the comparison result.

The vehicle under inspection by the device according to the invention comprises a plurality of electronic control devices for controlling different electrical functions in the vehicle. The vehicle specification file is stored in at least one electronic control device, but may be stored in more than one place in the vehicle. The vehicle specification file may include information about the electronic control apparatus in the vehicle, technical information about the vehicle, and a product specification for the function of the vehicle.

The maintenance device according to the invention provides a powerful solution for the maintenance of a vehicle. By having a vehicle specification file that can derive the parameter set used to program the electronic control unit, the inspection staff who want to work on the vehicle can easily outline vehicle maintenance. In addition, by having a parameter setting module for obtaining the parameters of the vehicle, the use of a new electronic control device that has become popular in the market after the launch of the vehicle only needs to update the parameter setting module. In short, the device according to the invention makes it possible to freely modify the vehicle.

The device may be installed to read information from each of the electronic control devices connected to the data bus via the device connector. This provides the possibility of playing back at least a portion of the vehicle specification file in the event of an error in the vehicle specification file.

Information from the electronic control device may include a vehicle identification number. This information can be used to electronically control the electronic control device to be identical to that specified by the vehicle specification file.

The apparatus of the present invention may also include a communication connector for connecting the apparatus of the present invention to a central server. This can be used to provide an update of the parameter setting module to the device of the present invention.

The maintenance device of the present invention is arranged to read a vehicle specification file from a memory via a device connector and a data bus when an instruction from a user is received, and to transmit the vehicle specification file as an e-mail to a central server via a communication connector. Can be. Sending the vehicle specification file as an email is an effective, fast and reliable way to provide the vehicle specification file to a central server.

The parameter setting module can be executed as a computer program in the maintenance device, the maintenance device is configured to receive an update to the parameter setting module via the communication connector, and the maintenance device is also configured to execute the update to the parameter setting module. As an alternative to implementing the parameter setting module as a computer program, it is of course also possible to implement the parameter setting module as a hard-wired electronic device. However, running in the form of a computer program provides a much more flexible solution.

By installing the maintenance device to receive the update via the communication connector, updating the parameter setting module is not complicated.

The vehicle specification file includes information about the dimensions of the vehicle, information about the chassis of the vehicle, information about the engine of the vehicle, information about the length of the cable in the vehicle, information about the arrangement of the cables in the vehicle, cable layout, and It may include at least one type of information from the group including information about the electrical component, and information about the update of the vehicle. The above list is not exhaustive and other types of information may be included in the vehicle specification file.

The maintenance apparatus of the present invention may include a user input device for inputting information from a user. The user input device may be a normal keyboard, but may also be in the form of another input device known to those skilled in the art, such as a microphone, digitizer board or touch screen, for example.

The maintenance device of the present invention includes a graphical user interface which is installed to control a display device connected to the device. The display device may of course be any type of display device known to those skilled in the art.

After leaving the factory, various structural defects can be found in a series of vehicles. Such structural defects are usually repaired by recalling such a series of vehicles by a so-called campaign alert. However, the owners of vehicles often do not know the campaign notification. As a result, many vehicles cannot be repaired in the required way. Therefore, there is a need for an apparatus that can cope with this problem. To this end, the maintenance device of the present invention is configured to receive alert modifications to be performed on the vehicle type and an alert identifier identifying such vehicle via a communication connector. In the state connected to the vehicle, the maintenance apparatus of the present invention reads the vehicle specification file from the vehicle, compares the notification identifier with the identifier of the vehicle specification file, and confirms the change remaining in the state to be performed if the identifiers match with each other. Compare the notification change with the vehicle specification file and output a notification to the user of such a change to be made. This maintenance device allows most vehicles to be repaired structural defects when inspected regularly, thus reducing the problem of unrepaired structural defects.

When the vehicle is inspected at the workshop, the personnel of the workshop obtain information about the vehicle from the vehicle specification file. Since the information in the vehicle specification file provides guidance as to whether there have been any changes to the vehicle, this can be very valuable to fix the problem of the vehicle. If changes were made at an unauthorized workshop, the vehicle specification file would not have been updated. Therefore, the fact of the change can be found through the mismatch between the vehicle specification file and the actual state of the vehicle. For example, if the electronic control unit (ECU) has been replaced with a non-standard electronic control unit (ECU), this can be found by comparing the information in the vehicle specification file with the actual electronic control unit installed in the vehicle.

If the change of the vehicle was made at an authorized workshop, the vehicle specification file is modified accordingly.

Although only one vehicle specification file version may be stored in the vehicle as described above, it is also possible to have two versions stored at two different points. This has the advantage that it is more likely to reproduce accurate information in the event of an error in the vehicle specification file in any way. For this storage of the vehicle specification file, the maintenance device of the present invention reads the vehicle specification file from two different memories connected to the data bus of the vehicle when it is connected to the vehicle, and determines whether any of the vehicle specification files have been changed. Compare the vehicle specification files and output a signal to the display device indicating a mismatch between the vehicle specification files.

The maintenance device of the present invention may also be configured to verify at least one check sum of each of the vehicle specification files in order to verify which vehicle specification file is correct in case of inconsistency between the vehicle specification files. have. Thereby, the maintenance apparatus of the present invention can check which of the vehicle specification files is correct. Each vehicle specification file may have more than one checksum. According to this, it is possible to control a part of the vehicle specification file, and also to combine the exact part of the first version of the vehicle specification file with the exact part of the second version of the vehicle specification file.

In addition, the maintenance apparatus of the present invention is configured to obtain information on the mileage of the vehicle from the vehicle specification file, to prepare information on the inspection rule by using the mileage of the vehicle and the program module and to output the inspection rule to the display device Can be. Maintenance devices configured in this way can automatically provide inspection rules on the display and allow the maintenance staff to easily obtain information about what has been done to the vehicle. Alternatively, the travel distance may be provided to the maintenance device as an input value through the input device.

According to a second aspect of the invention, there is provided at least one controllable vehicle component, a data bus, and at least one electronic control device connected to the data bus and configured to control at least one of the controllable vehicle components. Maintain an automobile comprising an electronic control device, each of which can be programmed by its own parameter set, and a memory storing a vehicle specification file containing information relating to the parameter set of the electronic control device and connected to the data bus. An automobile maintenance computer program is stored, the computer program being provided with a computer readable memory medium configured to include instructions for causing the computer to communicate with the data bus of the vehicle when operating the computer. The memory medium may be configured such that the computer program executes a parameter setting module to obtain a parameter set from the vehicle specification file, and executes a plurality of program modules to read the vehicle specification file stored in the memory via the data bus. A parameter setting module configured to program the electronic control device via the data bus by a parameter set obtained from the vehicle specification file, wherein the vehicle specification file and the at least one electronic control device each include a vehicle identification number. And the computer program also executes the plurality of program modules to read the vehicle identification number from the at least one electronic control device via the data bus and compare it with the vehicle identification number in the vehicle specification file. Based on the characterized in that it is configured to be programmed to the electronic controller. Such a computer program can be executed on a standard computer for operating the car maintenance apparatus according to the present invention.

The features described above with respect to the maintenance device according to the invention, if applicable, can be implemented in a computer program according to the invention with the same advantages as described with respect to the device of the invention.

According to a third aspect of the invention, there is provided at least one controllable vehicle component, a data bus, and at least one electronic control device connected to the data bus and configured to control at least one of the controllable vehicle components. Maintain an automobile comprising an electronic control device, each of which can be programmed by its own parameter set, and a memory storing a vehicle specification file containing information relating to the parameter set of the electronic control device and connected to the data bus. An automobile maintenance method is provided. The vehicle maintenance method of the present invention includes providing a parameter setting module configured to obtain the parameter set from the vehicle specification file, reading the vehicle detail file from the memory via the data bus of the vehicle; Obtaining a parameter set from the vehicle specification file using a parameter setting module, and programming the electronic control device via the data bus with the obtained parameter set, wherein programming the electronic control device comprises: Reading a vehicle identification number from the at least one electronic control device via the data bus, comparing the vehicle identification number of the electronic control device with the vehicle identification number of the vehicle specification file, and based on the comparison result The electronic control unit Characterized in that it comprises programmed. This vehicle maintenance method is preferably performed using the above-described maintenance apparatus.

The features described above with respect to the maintenance device according to the invention, if applicable, can be carried out in the maintenance method according to the invention with the same advantages as described with respect to the device of the invention.

In prior art vehicles, the electronic control unit (ECU) is programmed with a number of codes to achieve the required function. According to the present invention, the vehicle description file describes the vehicle in a high level language. The vehicle specification file is then converted into code for programming the electronic control device. By defining the vehicle in a high-level language in the vehicle specification file, it becomes much easier for the inspection staff to read and modify the vehicle specification file.

The above forms of the invention can of course be combined in the same embodiment.

The present invention provides a vehicle maintenance apparatus, method and computer program which provides a means for an uncomplicated modification of a vehicle, the maintenance apparatus, method and computer program of which an inspection staff can easily read specifications for the vehicle. It works.

Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

1 illustrates a motor vehicle according to an embodiment of the present invention.
FIG. 2 shows the principal arrangement of the buses of the vehicle of FIG. 1.
3 schematically illustrates a vehicle specification file according to an embodiment of the present invention.
4 is a flowchart illustrating a consistency check of a vehicle according to an embodiment of the present invention.
5 shows the function of the program module when reading the vehicle specification file from the vehicle.
6 shows the function of a program module when programming spare parts.
7 illustrates the functionality of a program module for displaying information from a UFC block.
8 shows the function of a program module for displaying a cable list.
9 shows process steps for investigating the need for change by a campaign.
10 shows the process steps performed when checking the vehicle.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The following description of the preferred embodiments of the present invention refers to the drawings, wherein like elements are designated by like reference numerals.

1 shows a motor vehicle 1 according to an embodiment of the invention. In FIG. 1 a car is shown as a truck, but the car may be any other type of car. The motor vehicle comprises a plurality of controllable vehicle parts 2, each of which is controlled by a programmable electronic control unit (ECU) 3. The electronic control unit ECU is all connected to the data bus 4. In FIG. 1 all electronic control units (ECUs) are connected to a common data bus 4, but as described below, the electronic control units are divided into groups so that each group of electronic control units is connected to a separate data bus. It may be. The number of groups and data buses is not limited. The vehicle part 2 may be, for example, the taillight 13 or the headlight 14 of the motor vehicle 1. Other components that can be controlled by an electronic control device include gearboxes, climate control devices, power windows, and the like. Also shown in FIG. 1 is a vehicle connector 5 which is connected to a data bus 4 and which can be connected to a device 6 for servicing a motor vehicle 1. The data bus 4 is also connected to a central electronic control unit (CECU) comprising a memory 8 for storing the vehicle specification file. Also shown in FIG. 1 is a maintenance device 6 for a motor vehicle 1 and a central server 21 connected to the maintenance device via a communication connector 18. By the connection with the central server 21, data related to the automobile 1 can be transmitted to the central server 21, and data related to the automobile 1 in the central server 21 can be transmitted to the automobile. . The connection between the maintenance device 6 and the central server 21 and the connection between the vehicle connector 5 and the maintenance device 6 can be made wireless. Such a wireless connection may be provided in any manner known to those skilled in the art.

2 shows the main arrangement of the data network 12 in the motor vehicle 1. The data network comprises a first data bus 9, a second data bus 10, and a third data bus 11, all three of the data buses 9, 10, and 11 having a central electronic control unit (CECU). 7, the central electronic control device 7 is again connected to a vehicle connector 5 installed in the vehicle for connecting the maintenance device 6 to the data buses 9, 10, 11. A memory 8 in which various data can be stored is installed in the central electronic control device 7. According to the invention the vehicle specification file is stored in the memory 8.

Car maintenance

The main configuration of the motor vehicle maintenance device 6 is shown in FIG. 1. The maintenance device 6 comprises a device connector 17 for connecting the maintenance device 6 to the vehicle connector 5 of the vehicle. The maintenance device 6 comprises a number of modules 23 and 24 which are executed as computer programs in the maintenance device. The display device 16 is connected to the maintenance device 6 for displaying information to the maintenance staff using the maintenance device 6. The maintenance device 6 also includes a communication connector 18 for connecting the maintenance device 6 to a network such as the Internet or other network. The maintenance device 6 can communicate with the central server via the communication connector 18. [ The maintenance device 6 also includes an input device 19, such as a keyboard, for inputting information from a maintenance staff using the maintenance device 6.

The maintenance device 6 has an input 20 for a dongle 22 used to access a module of the maintenance device, which module can be executed by a computer program. Depending on the code included in the dongle 22, access to the maintenance device may be granted at different privilege levels. The coding system used in the dongle 22 and the maintenance device 6 may be any type of coding system known to those skilled in the art. Coding of the dongle 22 may be implemented in hardware or software.

When the inspection staff puts his personal dongle into the maintenance device 6, the maintenance device 6 reads the code of the dongle and allows the inspection staff access to a level of authority corresponding to the code of the dongle. For example, the first permission level may allow the inspector only to read information from the car, and the second permission level may allow the inspector to change a limited amount of information of the car. Finally, the third level of authority may authorize the inspector to change all possible information on the vehicle.

Of course, there is no limit to the number of levels of authority to access the maintenance unit.

Vehicle specification file

The vehicle specification file 25 is schematically shown in FIG. 3 and divided into a number of blocks for programming. Each block of the vehicle specification has its own checksum, its own identification and version, so that each block can be processed separately.

In addition to the information common to all the blocks as described above, the head portion 26 of the vehicle specification file 25 also includes pointers to other blocks in the vehicle specification file 25 and thus to all blocks. Easy access The head portion also includes an identification name and a version number identifying the vehicle specification file 25. If further blocks are included in the vehicle specification file 25 in the future, the version number is updated. The head unit may further include a digital fingerprint having information on the creator of the vehicle specification file 25 and the generation time of the vehicle specification file by date entry, and an application program that generates the vehicle specification file 25. ), Identifying the item, the version of the application, and the serial number of the USB-key used for authorization purposes.

In the vehicle specification file 25, the ECU-block 27, the FPC-block 28, the XPC-block 29, the UFC-block 30, and the CABL-block 31, which are described in detail below in detail, are described. And version-block 32.

The ECU-block 27 contains a list of ECUs of the vehicle. This list contains the address of each ECU, the identification number for each ECU, the function parameters indicating the possible functions for each ECU, the part number of each ECU, the configuration checksum and the adjustments. Within each ECU a vehicle identification number (VIN) is programmed. The data in the ECU block and the VIN ensure that the ECUs are properly programmed. When an ECU is moved from one vehicle to another, this movement can be detected because the VIN in the ECU is incorrect. If the ECU is programmed with an incompatibility program, this can also be detected as the checksum becomes incorrect. In addition, if the ECU is lost or inoperative, relevant information about the ECU can be collected from the ECU-block. When the ECU is replaced with a new ECU, it can be easily replaced and programmed by using the information from the vehicle specification file 25.

The FPC-block 28 contains the product specification of the vehicle. This product specification contains information about the type of vehicle and includes the functional product characteristics of the vehicle. The product specification is used during vehicle production and contains information about the vehicle from a functional point of view, although schematic in that it does not include an item number for the part. Examples of such functional product features are the wheel base of the vehicle, the wheel arrangement, ie the number and size of the wheels of each axle, the size of the fuel tank, the shape of the gear box and the vehicle color. Due to the design of the FPC-block 28, the values of the various functional product characteristics cannot be stored in the FPC-block 28. Within the FPC-block 28 only codes that represent different values are stored. The main function of the FPC-block 28 is to serve as embedded data when programming spare parts or adjusting ECUs. Programming of the spare ECU refers to the complete configuration of all the functions that can be built into the ECU. In a typical vehicle, about 1000 parameters are configured in the ECU from about 100 functional product characteristics. The functional product characteristic is converted into programming parameters by the device for programming the vehicle.

The XPC-block 29 contains vehicle related information that cannot be included in the FPC-block 28, ie values for various product characteristics. Thus information about the values corresponding to the various codes in the FPC-block 28 is stored in the XPC-block 29. The XPC-block 29 can be used to store various new information when it is necessary to store new information. The information in the XPC-block 29 may be used for programming the spare ECU. Examples of information in the XPC-block 29 are information on the gear ratio of the final drive and the volume of the left and right fuel tanks. In addition to the information that can be used to program the spare ECU, the XPC block 29 also contains information about the administrative character.

The UFC-block 30 contains information about functions experienced by the vehicle user such as the function of the automatic gear box, the function of the ventilation system and the function of the drive control. UFC-block 30 also includes information regarding the performance of each of the functions for the vehicle. Information about performance means information about how the ECU has been programmed to provide functionality. When the vehicle is connected to the maintenance device, the information in the UFC block is displayed to the inspector. The UFC block 30 contains all the electrical system functions and information about the functioning in the vehicle. Personalized information makes it easier to fault-tracing. The information in the UFC-block 30 only relates to the information in the form of visual drawings and descriptive documents implemented in the maintenance unit.

The CABL-block 31 contains all the information about the vehicle cable. This information includes data on cable lengths and cable connections. As in the case of the UFC-block 30, this is individualized information in the form of a list of cables embedded in the vehicle. The information in the CABL-block 31, together with the information in the maintenance device, provides the maintenance worker with sufficient information for quick and reliable error tracking.

The version-block 32 contains information about changes made to the vehicle. This information makes it possible to verify the initial specification of the vehicle, so it is worth having change information. When the vehicle is modified at an authorized workshop, with a new fingerprint with information about the application used to update the version block 32, the version of the application, the update date and the serial number of the USB-key A new version-block 32 is created that indicates what changes have been made to the vehicle.

Finally, the vehicle specification file 25 also includes a campaign-block 33 similar to the version-block 32 but containing information about an implementation campaign to be executed instead of the modification. The information in campaign-block 33 represents the change made to the vehicle.

Of vehicle specification file update

The vehicle specification file 25 is updated for various reasons. One such reason is the failure of the ECU. If there is no inventory of a failed ECU's item, it must be replaced with another one that is compatible with the existing one. However, among many ECUs, the parameter set is often different from the parameter set used to program the failed ECU. Therefore, when replacing a failed ECU with a new, compatible ECU, the parameter set must be updated. However, in order to be able to replace the ECU with a new ECU, the new ECU must be supported by a parameter setting module in the maintenance device. Such support is provided by a parameter setting module that contains information about a large number of different ECUs and how to arrange parameter sets to provide various functions.

In some cases, the new version of the ECU provides more functionality than the original version of the ECU. In such a case, the parameters are set such that the initial function is achieved. Alternatively, if the hardware allows for new functionality, it can be set as such.

As a first embodiment, the replacement of the failed ECU 3 that controls the automatic gearbox will be described. The automobile is connected to the maintenance apparatus 6 of the automobile 1 at the workshop. The maintenance apparatus reads the vehicle specification file 25 from the vehicle and checks the identification number of all ECUs in the vehicle from the vehicle specification file 25. The identification number is shown on the display connected to the maintenance unit.

In various ways known to those skilled in the art, it is possible to identify a failed ECU 3. For example, it is possible to confirm by comparing the description of the error provided by the car user with the possibility of error. If the ECU 3 itself does not respond, this means that the ECU 3 has failed. In addition, the failed ECU 3 may be identified by an error code that may be recorded in an error detection system that is separate from or integrated with the network 12 of the ECU 3.

Once the ECU 3 to be replaced is identified, the mechanic using the maintenance device 6 can select the ECU 3 to be replaced in the maintenance device 6 using the input device 19 and the display device. When a particular ECU 3 is selected, the maintenance device 6 presents a replacement ECU 3 which can be used in place of the failed ECU 3 and displays the information on the display describing the function to the ECU 3. After replacing the ECU 3, the mechanic can input the information that the ECU 3 has been replaced by the input device 19 to the maintenance device 6. Thereafter, updating of the parameter set for the replaced ECU 3 is started. The maintenance device 6 thus obtains a new set of parameters using the vehicle specification file 25 from the vehicle 1 and the information about the ECU 3. The obtained parameter set is then transmitted from the maintenance device 6 to the motor vehicle 1.

As a second embodiment of the time point when the vehicle specification file 25 needs to be updated, the modification of the vehicle will be described. First, the owner of the vehicle 1 adapts the vehicle 1 by adding a second rear axle. After retrofitting the motor vehicle 1, the motor vehicle 1 can be connected to the maintenance device 6 which reads the vehicle specification file 25 from the memory 8 of the central ECU 7. The maintenance device then updates the version block of the specification file. There are two ways to update the vehicle specification file 25. According to the first approach in the case of small and frequent retrofitting, the vehicle specification file 25 is read from the vehicle and sent to the reconstruction database. Accordingly, a list of modifiable items that are presented to the owner who is attempting to retrofit the vehicle is displayed. After retrofitting the vehicle and programming the required ECU, the updated vehicle specification file 25 is stored back in the vehicle. According to the second approach, the vehicle specification file 25 is sent to the inspection center with a request for a particular modification of the vehicle. At the inspection center, a new vehicle specification file 25 is provided, sent to the owner who modifies the vehicle and stored in the vehicle.

Vehicle inspection

The vehicle specification file 25 is also very important when checking the vehicle 1. When the vehicle is inspected at the garage, the inspector connects the vehicle maintenance device 6 to the vehicle 1. In step 1001 of FIG. 10, the maintenance apparatus 6 reads the vehicle specification file 25 from the memory 8 of the central ECU 7. In step 1002, the traveling distance of the vehicle is input by the inspector to the maintenance apparatus 6 through the input apparatus or automatically read from the vehicle 1. The travel distance may be stored in the memory 8 of the central ECU 7. In step 1003, from the version block of the vehicle specification file 25, the maintenance apparatus 6 extracts information concerning the identification number identifying the inspection performed on the automobile 1 and the person who inspected the automobile 1. In step 1004, the maintenance apparatus 6 determines the inspection to be performed on the vehicle 1 based on the identification number and the traveling distance of the vehicle 1. Thereafter, in step 1005, the maintenance apparatus 6 compares the inspection to be performed on the vehicle 1 with the inspection already performed, and displays the difference on the display device 16. After the check is performed, in step 1006, the vehicle specification file 25 is updated and stored in the memory 8.

Campaign notifications ( Campaign alert )

After selling the vehicle 1, different structural defects can be found for the series of vehicles 1. Often these structural defects are repaired during a so-called campaign, when the vehicle owner of a particular series of cars is informed that the structural defects need to be repaired. Even after receiving such a campaign notification, only a few vehicle owners visit the workshop with the car 1. According to one embodiment of the invention, the execution of such a campaign is checked when the motor vehicle 1 is in a workshop for inspection or maintenance.

Thus, if for some reason the vehicle is connected to the maintenance device 6, it is checked whether the tasks specified in the different campaigns have been performed. In more detail, the vehicle specification file 25 is read from the memory 8 of the central ECU 7 and compared with the information about the campaign related to the vehicle 1.

Referring to FIG. 9, a method of investigating whether a campaign needs to be changed is shown. In a first step 901 a campaign block is read from the vehicle 1. In a second step 902, the campaign block is compared with information of all campaigns that have already been issued to determine which campaigns have not been executed for the car. In a third step 903, the display device 16 indicates which campaign should be executed for the vehicle. The campaign information is received by the maintenance apparatus 6 from the central server 21.

Consistency Check ( consistency check )

In order to inspect the electrical system of the vehicle, which is composed of suitably programmed electronic control devices, a consistency check can be performed. This consistency check involves several steps, which will be described later in conjunction with the diagram of FIG. 4.

In some situations, the vehicles 1 may be in different states, at which time there is a risk that an error may occur in the vehicle specification file 25. This means that the contents of the vehicle specification file 25 cannot be trusted. According to one embodiment of the invention, this problem can be solved by providing two copies of the vehicle specification file 25 in the vehicle and storing them in different places. The first version of the vehicle specification file 25 may be stored in the memory 8 of the central electronic control device 7. The second version of the vehicle specification file 25 may be stored in any of the other electronic control devices.

In the first step 401, the vehicle specification file 25 is obtained from the central electronic control apparatus 7 and another electronic control apparatus in which the vehicle specification file 25 is stored. The consistency of two versions of the vehicle specification file can be checked by comparing them. After doing so, if there is a difference between two different versions of the vehicle specification file 25, it is possible to determine that at least one of them is wrong. If so, the checksum of the vehicle specification file 25 is checked. Since the vehicle specification file 25 has one checksum for each block, it is possible to inspect each block separately.

Naturally, it is also possible to verify the checksum before comparing the vehicle specification file 25, but if the vehicle specification file 25 does not have a checksum for all blocks, the work takes more time.

In the event of an error in the two versions of the vehicle specification file 25, the maintenance device 6 receives some information from each electronic control device in order to be able to reproduce at least part of the vehicle specification file 25. May be arranged to recover. Thus, blocks with the correct checksum can be retrieved from one of the vehicle specification files 25 and other blocks can be retrieved from the other vehicle specification file 25 provided they have the correct checksum. The information read from each one electronic control device may be, for example, identification numbers of the electronic control devices.

In a second step 402, it is controlled whether it is possible to connect all the electronic control devices defined in the vehicle specification file 25. If one electronic control device is missing, it means that the electronic control device cannot function in any other way.

In a third step 403, it is checked whether all electronic control devices have the same vehicle identification number as the vehicle specification file 25. If an electronic control device has a different vehicle identification number, it means that the source may be another vehicle. Therefore, to function properly it must be reprogrammed. If the vehicle identification number is missing, this means that a spare electronic control device that is not programmed may be inserted. This information is displayed to the vehicle maintenance staff.

In a fourth step 404, it is checked whether the electronic control devices have a product number defined in the vehicle specification file 25. The vehicle identification number is correct, but the product number may be inaccurate. However, the reason for having the product number stored in the vehicle specification file 25 is to easily order the components when the components are to be replaced.

In a fifth step 405, the verification of the checksum is performed. Based on the parameters of the programmed electronic control devices, a checksum is generated and stored in each electronic control device. This checksum is accurate only if the electronic control units are programmed with a certified service unit.

Although the steps are shown in a certain order in the flowchart, it will be apparent to one skilled in the art that the steps may be executed in any order.

Transmission of vehicle specification file

In some cases, a mechanic alone cannot repair a car. In order to cope with such a situation, the maintenance device 6 may include a communication connector 18 connected to the Internet. The device can then be connected to the central server 21 via a communication connector 18.

Information may be transmitted from the maintenance apparatus to the central server 21, and may also be transmitted in the opposite direction. Such a transfer is performed, for example, when a computer program of a maintenance device needs to be updated. This is the case when new versions of the electronic control devices 3 are released or when a new function is added to the vehicle 1. The program update can be transmitted from the central server 21 to the maintenance device 6 via the communication connector 18 via the Internet.

If the mechanic wishes to transmit some information to the central server 21, the information can be transmitted via the communication connector 18. For example, the vehicle specification file 25 may be sent to the central server 21 by email.

As described above, the vehicle specification file 25 is read from the vehicle by the maintenance apparatus. This maintenance device is controlled by a number of program modules. The function of these different program modules will be described later.

5, a reading operation of the vehicle specification file is shown. The first program module 503 reads the vehicle specification file 505 from the vehicle 501. In order to be able to read the vehicle specification file from the vehicle 501, an electronic key 502 must be provided in the first program module 503. The second program module 504 is equipped with an electronic library used to interpret the vehicle specification file and display the readable version to the computer operator.

Referring to Figure 6, the programming of the spare parts is illustrated. The first program module 602 reads the vehicle specification file 603 from the vehicle 601. The second program module 604 converts the vehicle specification file 603 into a readable format. The first program module 602 also reads an identification number for the new electronic control device from the vehicle 601 and transmits the identification number to the third program module 605. The third program module 605 is connected to the database 606. By means of the information about the identity of the electronic control device, the vehicle specification file and the database 606, the third program module 605 obtains program data to be used for programming the electronic control device.

Referring to Fig. 7, the information display operation of the UFC block 30 is shown. The UFC block 30 of the vehicle specification file 704 is read by the first program module 701 and transmitted to the second program module 702, which is then operated by a computer operator using the database 703. Will be given text and graphics.

8, a cable list display process is shown. The first program module 801 is used to read the CABL block 31 from the vehicle specification file 802. The CABL block 31 is transmitted to the second program module 803, which collects the characters and graphics connected to the CABL block 31 using the database 804. The graphic output is then displayed to the operator of the computer.

Although the use of the electronic key has not been described with reference to FIGS. 6 to 8, it will be apparent to those skilled in the art that the electronic key may also be used in those cases.

The present invention is not limited to the above-described preferred embodiments, and can be modified in various ways without departing from the scope and spirit of the present invention. The invention is only limited by the claims appended hereto.

The quantity of wheels of the automobile 1 may be less than six, for example the quantity of wheels of the automobile 1 shown in FIG. 1.

Storing two copies of the vehicle specification file 25 has been described only with respect to the consistency check, but one of ordinary skill in the art will appreciate that this approach can be applied to the other embodiments described above.

1: car 2: vehicle parts
3: electronic control unit 4: data bus
6: car maintenance device 8: memory
16: display device 17: device connector
18: communication connector 19: user input device
23: parameter setting module 25: vehicle specification file

Claims (11)

At least one electronic component connected to the at least one controllable vehicle component 2, the data bus 4 and the data bus 4 and configured to control at least one of the controllable vehicle components 2. The control device 3 stores an electronic control device 3, each of which can be programmed by its own parameter set, and a vehicle specification file containing information relating to the parameter set of the electronic control device, An automobile maintenance computer program for servicing an automobile 1 comprising a memory 8 connected to 4) is stored, which computer program stores the data bus (1) of the automobile 1 when the computer is operated. A computer readable memory medium configured to include instructions for communicating with 4) comprising:
The computer program executes a parameter setting module to obtain a parameter set from the vehicle specification file, and executes a plurality of program modules to read the vehicle specification file stored in the memory via the data bus 4 and to set the parameter. Configured to program the electronic control device 3 via the data bus 4 by means of a parameter set obtained from the vehicle specification file by a module,
The vehicle specification file 25 and the at least one electronic control device 3 each include a vehicle identification number,
The computer program also executes the plurality of program modules to read the vehicle identification number from the at least one electronic control device 3 via the data bus 4 so that the vehicle identification number of the vehicle specification file 25 can be read. And a computer program for storing the automobile maintenance computer, wherein the electronic control device is programmed based on the comparison result. The method of claim 1,
The computer program causes the computer 6 to read the vehicle specification file 25 from the memory 8 via the data bus 4 when receiving a command from the user and the vehicle specification file as e-mail. And (25) for transmitting to the central server (21). The method according to claim 1 or 2,
The computer is configured to receive, by the computer program, an update for the parameter setting module 23 from the central server 21 and to perform the update for the parameter setting module 23. Readable memory media. The method of claim 1,
The vehicle specification file 25 includes information about the dimensions of the vehicle, information about the chassis of the vehicle, information about the engine of the vehicle, information about the length of the cable in the vehicle, information about the layout of the cable in the vehicle, And at least one type of information from the group comprising information about the layout of the cable, the information about the electrical components in the vehicle, and the update of the vehicle. The method of claim 1,
And the computer is arranged to output a signal for controlling a display device (16) connected to the computer by the computer program. The method of claim 5,
The computer 6,
Receive alert modifications to be performed on the vehicle type when the computer is connected to the vehicle and an alert identifier identifying the vehicle,
Read the vehicle specification file 25 from the vehicle,
Compare the notification identifier with an identifier of the vehicle specification file 25,
If the identifiers for identifying the notification change to be performed correspond to each other, compare the notification change with the vehicle specification file 25,
And a signal for outputting a signal for notifying a user about such a notification change to be performed. The method of claim 5,
When connected to the motor vehicle 1, is installed to read the vehicle specification file 25 from two different memories connected to the data bus 4 of the motor vehicle,
A signal that compares the vehicle specification files 25 to determine whether any of the vehicle specification files 25 have been changed, and indicates a mismatch between the vehicle specification files 25 on the display device 16. And a computer readable memory medium. The method of claim 5,
The computer, when there is a mismatch between the vehicle specification files 25, by the computer program, the computer program controls each of the vehicle specification files 25 to control which vehicle specification file 25 is correct. A computer readable memory medium arranged to control a check sum. The method of claim 5,
The computer 6 acquires information on the mileage of the vehicle 1 from the vehicle specification file 25 by the computer program, and uses the mileage of the vehicle and the information on the inspection rule by using a programming module. And output a check rule as a signal to the display device (16). At least one electronic component connected to the at least one controllable vehicle component 2, the data bus 4 and the data bus 4 and configured to control at least one of the controllable vehicle components 2. The control device 3 stores an electronic control device 3, each of which can be programmed by its own parameter set, and a vehicle specification file containing information relating to the parameter set of the electronic control device, In a vehicle maintenance method for servicing a motor vehicle 1 comprising a memory 8 connected to 4),
Providing a parameter setting module configured to obtain the parameter set from the vehicle specification file 25;
Reading the vehicle detail file from the memory 8 via the data bus 4 of the vehicle;
Obtaining a parameter set from the vehicle specification file using the parameter setting module;
Programming said electronic control device 3 via said data bus 4 by means of said obtained parameter set,
Programming the electronic control device 3,
Reading a vehicle identification number from the at least one electronic control device 3 via the data bus 4;
Comparing the vehicle identification number of the electronic control device 3 with the vehicle identification number of the vehicle specification file;
And programming said electronic control device based on said comparison result. The method of claim 10,
Connecting the maintenance device 6 to the data bus of the motor vehicle 1, wherein the step of obtaining the parameter set from the vehicle specification file 25 is performed in the maintenance device 6. Car maintenance method.

Images