Method for configuring a control device for a vehicle

Abstract

The disclosure comprises a method (100) for configuring a control device (50) for a vehicle (60), having the following steps: - querying (102) whether a fault parameter (10) is stored in the control device (50); - determining (104) to which fault type (12, 13, 14) the detected fault parameter (10) is to be assigned; - configuring (106) the control device (50) on the basis of the detected fault type (12) in the control device (50).

Description

[0001] Description

[0002] Title:

[0003] Method for configuring a control unit for a vehicle

[0004] The present invention relates to a method for configuring a control unit for a vehicle.

[0005] State of the art

[0006] Today's control units use microcontrollers or processors that can be updated or reprogrammed for maintenance or service purposes. The update can be installed using a reprogramming tool during routine service or through over-the-air (OTA) updates.

[0007] However, detected and stored errors in the control unit can impair the possibility of software reprogramming or updating. Basically, two scenarios can occur.

[0008] In the first scenario, errors are simply ignored and the control unit is updated to a newer software version. This procedure typically results in the control unit's error log being erased, resulting in the loss of the internal error information stored in the control unit before the control unit was reprogrammed.

[0009] However, deleting stored errors means that subsequent error analysis is no longer possible. Valuable error information for improving the control unit is thus lost. Furthermore, deleting an error results in normal start-up of the control unit and potential failure reactions. The error is no longer executed. If, for example, the control unit was previously in a safe state, the control unit returns to normal operation. This may require a previously detected error to be re-qualified. In the meantime, the malfunction is not under control and, in rare cases, can lead to a dangerous event.

[0010] In the second scenario, updating the control unit to a new software version is not possible if a specific error is detected or stored in the control unit. Therefore, before reprogramming, the control unit must be checked to see if an internal error is stored. If so, any reprogramming attempt will be rejected. For this reason, no further software updates are possible for such a control unit.

[0011] If a fault prevents reprogramming of an ECU, the ECU must be replaced. If the fault is caused by system / software errors (bugs), design weaknesses, specification errors, etc., which can be resolved with a software update, a software update would be more advantageous than replacing the ECU. This is not possible if the locking fault, i.e., a fault that blocks reprogramming, is qualified.

[0012] It is therefore the object of the present invention to provide a solution by means of which a control unit can be configured in an efficient manner when an error is detected.

[0013] Disclosure of the invention

[0014] This object is achieved by a method for configuring a control unit for a vehicle having the features of the independent claim.

[0015] According to a first aspect, the disclosure relates to a method for configuring a control unit for a vehicle, comprising the following steps: In a first step, a query is carried out as to whether an error parameter is stored in the control unit

[0016] In a second step, it is determined to which error type the detected error parameter can be assigned

[0017] In a third step, the control unit is configured depending on the detected error type in the control unit

[0018] A fundamental idea of ​​the present invention is that reprogramming or a software update of a faulty control unit is only permitted or performed under the premise that the identified internal error in the control unit can be assigned to a defined error classification. This avoids replacing the faulty control unit. Compared to the prior art, the present invention does not fundamentally prevent reprogramming of the control unit in the event of a qualified, recognized, and / or stored error in the control unit.

[0019] This results in the following advantages:

[0020] Ensuring that the control unit can be operated in a safe operating mode

[0021] Avoidance of having to replace the control unit Reduction of warranty costs for the control unit Avoidance of costly recalls for vehicles with defective control units

[0022] Increase customer satisfaction

[0023] One embodiment of the method provides that the determination of the error type determines whether the error parameter is to be assigned to a first error type or a second error type. In the case of an error parameter of the first error type, the control unit may be overwritten by a new software version of the control unit program. In the case of an error parameter of the second error type, a software update of the control unit is prevented in order to prevent the corresponding stored error parameter of the second error type from being deleted in the control unit. This enables efficient configuration of the control unit depending on the identified error.

[0024] One embodiment of the method provides that the determination of the error type involves comparing the detected error parameter with a list of error parameters, wherein the list can be retrieved at least partially from an internal vehicle data source and / or by accessing an external vehicle data source. This allows an error in the control unit to be identified efficiently.

[0025] One embodiment of the method provides that the configuration involves comparing a first identification parameter of the software version on the control unit with a second ID parameter of the software version to be transferred to the control unit. Following the comparison, a decision is made that if the software version to be installed is newer than the software version already installed, then the control unit may be configured. Otherwise, a change to the current software version on the control unit is prevented. This prevents errors during the software update of the control unit, and stored data on the control unit is thus not lost.

[0026] According to a second aspect, the disclosure relates to a control unit with a computing unit for a vehicle, wherein the control unit is designed to carry out the method according to the first aspect.

[0027] According to a third aspect, the disclosure relates to a computer program containing machine-readable instructions which, when executed on one or more computers and / or computer instances, cause the computer or computer instances to carry out the method according to the invention.

[0028] According to a fourth aspect, the disclosure relates to a machine-readable data carrier and / or downloadable product with the computer program. According to a fifth aspect, the disclosure relates to one or more computers and / or computer instances with the computer program, and / or with the machine-readable data carrier and / or the downloadable product.

[0029] Further measures improving the invention are described in more detail below together with the description of the preferred embodiments of the invention with reference to figures

[0030] Examples of implementation

[0031] It shows:

[0032] Figure 1 Schematic flow diagram of the method 100 for configuring a control unit 50 for a vehicle 60.

[0033] Figure 1 shows a schematic flow diagram of the method 100 for configuring a control unit 50 for a vehicle 60.

[0034] In step 102, a query is performed to determine whether an error parameter 10 is stored in the control unit 50. Alternatively, the error parameter 10 can also be referred to as error information. The query can also include, or alternatively, mean, determining the error state of the control unit 50.

[0035] In step 104, it is determined to which error type 12, 13, 14 the detected error parameter 10 is to be assigned.

[0036] Optionally, determining the error type 12 determines whether the error parameter or the error information 10 stored or stored in the control unit 50 can be assigned to a first error type 13 or a second error type 14. Error classification with respect to error type can also consist of distinguishing permissible errors from non-permissible errors and adjusting the configuration of the control unit 50 accordingly. If the identified error parameter 10 corresponds to a first error type 13, the control unit 50 may be overwritten with a new software version of the control unit program.

[0037] If, however, the identified error parameter 10 corresponds to a second error type 14, a software update of the control unit 50 is prevented or blocked in order to prevent the corresponding stored error parameter 10 of the second error type 14 in the control unit 50 from being deleted or overwritten. The software version on the control unit 50 is then retained to enable error analysis and to prevent the control unit 50 from leaving its safe operating state.

[0038] In step 106, the control unit 50 is configured depending on the detected error type 12 in the control unit 50.

[0039] Optionally, the configuration of the control unit 50, for example, overwriting an older software version with a newer software version, can be made dependent on how often the control unit 50 has already been configured. A counter can be used for this purpose. This counter indicates how often the control unit 50 has already been configured, e.g., flashed.

[0040] Optionally, determining the error type 12, 13, 14 involves comparing the detected error parameter 10 with a list 20 of error parameters or error information. This list 20, which lists current and defined error parameters or error information for recognized or defined problems, can be retrieved at least partially from an in-vehicle data source 22 of the vehicle 60, such as a control unit or a storage device, and / or by accessing an external data source 24, such as a cloud-based database.

[0041] Optionally, step 106 of configuring provides that a first identification parameter 15 of the software version on the control unit 50 is compared with a second identification ID parameter 16 of the software version to be transferred to the control unit 50, and wherein a decision is then made after the comparison that if the software version to be installed is newer than the software version already installed on the control unit 50, then the control unit 50 may be configured, otherwise a change to the current software version on the control unit 50 is prevented.

[0042] This is preferably done before updating the control unit 50 to a new software version.

[0043] The control unit 50 for a vehicle 60 can be equipped with a computing unit to carry out the method according to the invention. However, the control unit 50 can also be used for any other applications, such as data processing systems or means of transportation.

Claims

Claims 1. Method (100) for configuring a control unit (50) for a vehicle (60), comprising the following steps: Querying (102) whether an error parameter (10) is stored in the control unit (50); Determining (104) to which error type (12, 13, 14) the detected error parameter (10) is to be assigned, configuring (106) the control unit (50) depending on the detected error type (12) in the control unit (50).

2. Method (100) according to claim 1, wherein the determination of the error type (12) provides whether the error parameter (10) is to be assigned to a first error type (13) or a second error type (14), wherein in the case of an error parameter (10) of the first error type (13) the control unit (50) may be overwritten by a new software version of the control unit program, and wherein in the case of an error parameter (10) of the second error type (14) a software update of the control unit (50) is prevented in order not to delete the corresponding stored error parameter (10) of the second error type (14) in the control unit (50).

3. Method (100) according to one of the preceding claims, wherein the determination (104) of the error type (12, 13, 14) provides for comparing the detected error parameter (10) with a list (20) of error parameters, wherein the list (20) is at least partially retrievable from an internal vehicle data source (22) of the vehicle (60) and / or by accessing a vehicle-external data source (24).

4. Method (100) according to one of the preceding claims, wherein the configuration (106) provides that a first identification parameter (15) of the software version located on the control unit (50) is compared with a second ID parameter (16) of the software version to be transferred to the control unit (50), and wherein a decision is then made after the comparison that if the software version to be installed is newer than the software version already installed, then the control unit (50) may be configured, otherwise a change to the current software version on the control unit (50) is prevented.

5. Control unit (50) with a computing unit for a vehicle (60), wherein the control unit (50) is designed to carry out the method according to one of the preceding claims.

6. A computer program containing machine-readable instructions which, when executed on one or more computers and / or compute instances, cause the computer or computers or compute instances to carry out the method according to any one of claims 1 to 4.

7. Machine-readable data carrier and / or download product with the computer program according to claim 6.

8. One or more computers and / or compute instances with the computer program according to claim 6, and / or with the machine-readable data carrier and / or download product according to claim 7.

Images