Method and device for coding a controller of a vehicle and for checking a controller of a vehicle

Abstract

Methods and devices for writing or for checking a controller of a vehicle are provided. A first set of vehicle parameters are written into the controller of the vehicle as coding parameters. A second set of vehicle parameters are written in another controller of the vehicle coupled to the controller via a vehicle bus of the vehicle. The first set of vehicle parameters are compared with the second set of vehicle parameters. An error is detected based on the comparing. The vehicle is not started in response to the detected error.

Claims

1. A method for writing a controller of a vehicle, comprising: writing a first set of vehicle parameters into the controller of the vehicle as coding parameters; writing a second set of vehicle parameters in another controller of the vehicle coupled to the controller via a vehicle bus of the vehicle; comparing the first set of vehicle parameters with the second set of vehicle parameters; detecting an error based on the comparing; and not starting the vehicle in response to the detecting of the error.

2. The method according to claim 1, wherein a corresponding checksum of a cyclic redundancy check is written into the controller as a coding parameter.

3. The method according to claim 2, wherein a set of function-specific parameters is additionally written into the controller as coding parameters, and the set of function-specific parameters is a subset of function-specific parameters that are written in the another controller of the vehicle.

4. The method according to claim 3, wherein one or more of the following are additionally coded into the controller: a checksum, corresponding to the first set or the second set, of a cyclic redundancy check, an identification number corresponding to the first set or the second set, or a checksum, corresponding to the identification number, of a cyclic redundancy check.

5. A method for checking a controller of a vehicle, comprising: reading, from the controller, a first set of vehicle parameters that have been written into the controller as coding parameters; providing a second set of vehicle parameters that is written in another controller coupled to the controller via a vehicle bus of the vehicle; comparing the first set of vehicle parameters with the second set of vehicle parameters to check the controller; and starting the vehicle by using the another controller to send a message containing the second set of vehicle parameters to the controller in response to the comparing.

6. The method according to claim 5, wherein a corresponding checksum of a cyclic redundancy check that has been written into the controller as a coding parameter is read from the controller and checked.

7. The method according to claim 6, wherein a plausibility test is additionally performed on one or more vehicle parameters of the read first set of vehicle parameters.

8. The method according to claim 6, wherein one or more of the following are additionally read and checked: a set of function-specific parameters that have been written into the controller as coding parameters, a checksum, corresponding to the set of function-specific parameters, of a cyclic redundancy check, an identification number corresponding to the set of function-specific parameters, or a checksum, corresponding to the identification number, of a cyclic redundancy check.

9. A device for writing or for checking a controller of a vehicle, wherein the device is configured to carry out the acts of: writing a set of vehicle parameters into the controller of the vehicle as coding parameters; additionally writing the set of vehicle parameters in another controller of the vehicle; reading from the controller, a first set of vehicle parameters that have been written into the controller as coding parameters; providing a second set of vehicle parameters that is written in another controller coupled to the controller via a vehicle bus of the vehicle; comparing the first set of vehicle parameters with the second set of vehicle parameters to check the controller; and starting the vehicle by using the another controller to send a message containing the second set of vehicle parameters to the controller in response to the comparing.

10. A computer product comprising a non-transitory computer readable medium having stored thereon executable program code, wherein the program code when executed on a computing unit, carries out the acts of claim 1.

11. The method according to claim 1, wherein the first and second set of vehicle parameters comprise: the vehicle height or the vehicle width.

12. The method according to claim 1, wherein the first and second set of vehicle parameters comprise: a length of a hood of the vehicle.

13. The method according to claim 1, wherein the first and second set of vehicle parameters comprise: a steering wheel side of the vehicle.

14. The method according to claim 5, wherein the first and second set of vehicle parameters comprise: the vehicle height or the vehicle width.

15. The method according to claim 5, wherein the first and second set of vehicle parameters comprise: a length of a hood of the vehicle.

16. The method according to claim 5, wherein the first and second set of vehicle parameters comprise: a steering wheel side of the vehicle.

17. The method according to claim 7, wherein the plausibility test comprises a limit value comparison with a respective upper and/or lower limit value.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a flowchart of a program for coding a controller of a vehicle.

(2) FIG. 2 is a flowchart of a program for checking a controller of a vehicle.

DETAILED DESCRIPTION OF THE DRAWINGS

(3) FIG. 1 shows a flowchart of a program for coding a controller of a vehicle.

(4) The program may be run for example by a device. To this end, the device has in particular a computing unit, a program and data memory, and for example one or more communication interfaces. The program and data memory and/or the computing unit and/or the communication interfaces may be formed in one module and/or distributed over a plurality of modules.

(5) The device may also be referred to as device for coding a controller of a vehicle.

(6) To this end, the program is in particular stored on the program and data memory of the device.

(7) The program is started in a step S1 in which variables may possibly be initialized.

(8) In a step S3, a set of vehicle parameters is coded into the controller as coding parameters, wherein the set of vehicle parameters is additionally coded in another controller of the vehicle.

(9) In addition to one or more vehicle parameters and/or to a subset of vehicle parameters of the set of vehicle parameters, a corresponding checksum of a cyclic redundancy check is optionally coded into the controller as a coding parameter.

(10) A set of function-specific parameters is optionally additionally coded into the controller as coding parameters, wherein the set is a subset of function-specific parameters that are coded in the other controller of the vehicle.

(11) A checksum, corresponding to the set, of a cyclic redundancy check and/or an identification number corresponding to the set and/or a checksum, corresponding to the identification number, of a cyclic redundancy check, is optionally additionally coded into the controller.

(12) In a step S5, the program is ended and may possibly be restarted in step S1.

(13) FIG. 2 shows a flowchart of a program for checking a controller of a vehicle.

(14) The program may be run for example by a device. To this end, the device has in particular a computing unit, a program and data memory, and for example one or more communication interfaces. The program and data memory and/or the computing unit and/or the communication interfaces may be formed in one module and/or distributed over a plurality of modules.

(15) The device may also be referred to as device for checking a controller of a vehicle. The device may be implemented for example in the controller to be checked.

(16) To this end, the program is in particular stored on the program and data memory of the device.

(17) The program is started in a step S11 in which variables may possibly be initialized. The program is started for example when the vehicle is started by virtue of another controller sending a message designed for this purpose to the controller to be checked.

(18) In a step S13, a first set of vehicle parameters, which have been coded into the controller as coding parameters, is read from the controller.

(19) In an optional step S15, in addition to one or more vehicle parameters and/or to a subset of vehicle parameters of the read set of vehicle parameters, a corresponding checksum of a cyclic redundancy check that has been coded into the controller as coding parameter is read from the controller.

(20) In an optional step S17, the checksums corresponding to one or more vehicle parameters and/or to a subset of vehicle parameters of the read set of vehicle parameters are checked.

(21) If an error has been detected in the check, the program is continued in a step S31.

(22) If no error has been detected in the check, the program is continued in an optional step S21.

(23) In step S21, a plausibility test is performed on one or more vehicle parameters of the read set of vehicle parameters.

(24) If an error has been detected in the plausibility test, the program is continued in step S31.

(25) If no error has been detected in the plausibility test, the program is continued in an optional step S23.

(26) In step S23, a set of function-specific parameters, which have been coded into the controller as coding parameters, a checksum, corresponding to the set, of a cyclic redundancy check and an identification number corresponding to the set are read.

(27) In an optional step S25, the checksum corresponding to the set is checked.

(28) If an error has been detected in the check, the program is continued in step S31.

(29) If no error has been detected in the check, the program is continued in an optional step S27.

(30) In optional step S27, the identification number corresponding to the set is checked.

(31) If an error has been detected in the check, the program is continued in step S31.

(32) If no error has been detected in the check, the program is continued in an optional step S29.

(33) In step S29, the first set of vehicle parameters is compared with a second set of vehicle parameters that has been provided and that is coded in another controller of the vehicle. By way of example, a vehicle type, a country code and a steering wheel side are compared.

(34) If an error has been detected in the comparison, the program is continued in step S31.

(35) If no error has been detected in the check, the program is continued in an optional step S30.

(36) In step S30, all of the checks have been performed successfully. The controller is thus able for example to send a confirmation message and start its normal operating mode. The program is then ended in a step S33.

(37) If an error has been established in step S31, then a suitable measure may be taken depending on the safety relevance of the controller/error, such as not starting the vehicle, displaying that it is necessary to visit a garage, deactivating a function of the controller and/or activating an emergency operating mode. The program is then ended in step S33.