Method and Device for Coding a Controller of a Vehicle and for Checking a Controller of a Vehicle

Abstract

A method codes a controller of a vehicle, wherein a set of vehicle parameters is coded into the controller as the coding parameters, and the set of vehicle parameters is additionally coded in another controller of the vehicle.

Claims

1-11. (canceled)

12. A method for coding a controller of a vehicle, comprising: coding a set of vehicle parameters into the controller of the vehicle as coding parameters; and additionally coding the set of vehicle parameters in another controller of the vehicle.

13. The method according to claim 12, wherein 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 coded into the controller as a coding parameter.

14. The method according to claim 13, wherein a set of function-specific parameters is additionally coded into the controller as coding parameters, and the set of function-specific parameters is a subset of function-specific parameters that are coded in the other controller of the vehicle.

15. The method according to claim 14, wherein 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 additionally coded into the controller.

16. A method for checking a controller of a vehicle, comprising: reading, from the controller, a first set of vehicle parameters that have been coded into the controller as coding parameters; providing a second set of vehicle parameters that is coded in another controller of the vehicle; and comparing the first set of vehicle parameters with the second set of vehicle parameters to check the controller.

17. The method according to claim 16, wherein 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 a coding parameter is read from the controller and checked.

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

19. The method according to claim 17, wherein a set of function-specific parameters that have been coded into the controller as coding parameters, and/or 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 additionally read and checked.

20. A device for coding or for checking a controller of a vehicle, wherein (i) for coding the controller, the device is configured to carry out the acts of: coding a set of vehicle parameters into the controller of the vehicle as coding parameters; and additionally coding the set of vehicle parameters in another controller of the vehicle; or (ii) for checking the controller, the device is configured to carry out the acts of: reading from the controller, a first set of vehicle parameters that have been coded into the controller as coding parameters; providing a second set of vehicle parameters that is coded in another controller of the vehicle; and comparing the first set of vehicle parameters with the second set of vehicle parameters to check the controller.

21. A computer product comprising a non-transitory computer readable medium having stored thereon executable program code, wherein (i) for coding a controller, the program code when executed on a computing unit, carries out the acts of: coding a set of vehicle parameters into the controller of the vehicle as coding parameters; and additionally coding the set of vehicle parameters in another controller of the vehicle; or (ii) for checking the controller, the program code when executed on a computing unit, carries out the acts of: reading from the controller, a first set of vehicle parameters that have been coded into the controller as coding parameters; providing a second set of vehicle parameters that is coded in another controller of the vehicle; and comparing the first set of vehicle parameters with the second set of vehicle parameters to check the controller.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG. 1 is a flowchart of a program for coding a controller of a vehicle.

[0037] FIG. 2 is a flowchart of a program for checking a controller of a vehicle.

DETAILED DESCRIPTION OF THE DRAWINGS

[0038] FIG. 1 shows a flowchart of a program for coding a controller of a vehicle.

[0039] 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.

[0040] The device may also be referred to as device for coding a controller of a vehicle.

[0041] To this end, the program is in particular stored on the program and data memory of the device.

[0042] The program is started in a step S1 in which variables may possibly be initialized.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] In a step S5, the program is ended and may possibly be restarted in step S1.

[0048] FIG. 2 shows a flowchart of a program for checking a controller of a vehicle.

[0049] 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.

[0050] 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.

[0051] To this end, the program is in particular stored on the program and data memory of the device.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] If an error has been detected in the check, the program is continued in a step S31.

[0057] If no error has been detected in the check, the program is continued in an optional step S21.

[0058] In step S21, a plausibility test is performed on one or more vehicle parameters of the read set of vehicle parameters.

[0059] If an error has been detected in the plausibility test, the program is continued in step S31.

[0060] If no error has been detected in the plausibility test, the program is continued in an optional step S23.

[0061] 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.

[0062] In an optional step S25, the checksum corresponding to the set is checked.

[0063] If an error has been detected in the check, the program is continued in step S31.

[0064] If no error has been detected in the check, the program is continued in an optional step S27.

[0065] In optional step S27, the identification number corresponding to the set is checked.

[0066] If an error has been detected in the check, the program is continued in step S31.

[0067] If no error has been detected in the check, the program is continued in an optional step S29.

[0068] 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.

[0069] If an error has been detected in the comparison, the program is continued in step S31.

[0070] If no error has been detected in the check, the program is continued in an optional step S30.

[0071] 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.

[0072] 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.