Method for manufacturing vehicle

Abstract

A method of manufacturing a vehicle is disclosed. Provided is a technique for correctly writing individual programs. A method for manufacturing a vehicle disclosed in this specification is provided with: a first step for preparing a vehicle body on which a controller, in which common software common to a plurality of vehicle types is written, is mounted; and a second step in which individual software, which is specific for the vehicle type of the vehicle body, is written to the controller mounted on the vehicle body, identifiers corresponding to different features in the plurality of vehicle types are added to the controller, and before the individual software is written, the identifiers corresponding to different features in the plurality of vehicle types are added to the controller. A match is confirmed between the individual software written to the controller and the identifier after writing the individual software, and a match is confirmed between the individual software written to the controller after writing the individual software.

Description

TECHNICAL FIELD

[0001] The present specification relates to a manufacturing method of a vehicle. BACKGROUND

[0002] In Patent Literature 1, there is disclosed a manufacturing method of a vehicle, which includes a step of preparing a vehicle body on which an ECU is mounted, in which basic software common to a plurality of vehicle models is written, and a step of writing individual software particular to a vehicle model of the vehicle body in the ECU. In the step of writing the individual software, a check using a Check sum or the like is performed.

[0003] PRIOR ART DOCUMENTS

[0004] PATENT LITERATURE

[0005] Patent Literature 1: Japanese Patent Application Laid-Open No. 2005-157637 SUMMARY

[0006] In the manufacturing of a vehicle, it is necessary to write correct individual software for a vehicle model to be manufactured. Therefore, it is considered to check the matching between the basic software and the individual software stored in the ECU after the individual software is written. However, in the case where such a method is adopted, when a change is made in the basic software, it is necessary to modify the individual software and the contents of the check accordingly. In the present specification, a technology for avoiding such a trouble and writing the individual software correctly is provided.

[0007] The manufacturing method of a vehicle disclosed in the present specification includes a first step of preparing a vehicle body on which a controller is mounted, the controller having written therein common software common to a plurality of vehicle models, and a second step of writing individual software particular to a vehicle model of the vehicle body to the controller mounted on the vehicle body, the controller having attached thereto an identifier corresponding to a feature different in the plurality of vehicle models, in the second step, confirming the matching between the individual software written to the controller and the identifier before the individual software is written, and confirming the matching between the individual software written to the controller after the individual software is written.

[0008] According to the above-described structure, by confirming the matching between the individual software and the identifier, it is possible to confirm that the correct individual software is selected for a vehicle model to be manufactured. Further, by confirming the matching between the individual software actually stored in the controller after the individual software is written, it is possible to double-check whether the written individual software is appropriate or not. In this series of checks, the common software is not used. Therefore, even when a change is made in the basic software, it is not necessary to modify the individual software and the contents of the check accordingly, and it is possible to write the individual software correctly.

[0009] The details and further modifications of the technology disclosed in this specification will be explained in the following detailed description and further illustrated by the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0010] Figure 1 is a block diagram of a vehicle manufactured.

[0011] Figure 2 is a flowchart of a confirmation process.

[0012] Figure 3 is a diagram showing a process of manufacturing a vehicle.

[0013] SYMBOL EXPLANATION

[0014] 2: vehicle; 10: vehicle body; 12: central gateway; 20: controller; 30: 1st microcomputer; 32: 1st common software; 34: 1st individual software; 40: 2nd microcomputer; 42: 2nd common software; 44: 2nd individual software; 100: writing device; ID1, ID2: identifier. DETAILED DESCRIPTION

[0015] (Structure of vehicle 2; Figure 1 )

[0016] Figure 1 A vehicle 2 manufactured by the manufacturing method of the present embodiment is shown. The vehicle 2 is provided with a vehicle body 10, a central gateway 12 (hereinafter referred to as "CGW 12"), and a controller 20. The CGW 12 and the controller 20 are mounted on the vehicle body 10. The CGW 12 is a device for performing communication between a device (for example, the controller 20) mounted on the vehicle body 10 and a device outside the vehicle body 10.

[0017] In the vehicle body 10, a motor for running and a motor for power generation (omitted from the drawing) are also mounted. The controller 20 is provided with a 1st microcomputer 30 that controls electric power supplied to the motor for running, and a 2nd microcomputer 40 that controls electric power output from the motor for power generation. In a modified example, two motors for running can also be mounted in the vehicle body 10. One of the motors can be a motor for front-wheel drive, and the other motor can be a motor for rear-wheel drive. Further, the 1st microcomputer 30 can control electric power supplied to the motor for front-wheel drive, and the 2nd microcomputer 40 can control electric power supplied to the motor for rear-wheel drive.

[0018] In the 1st microcomputer 30, the 1st common software 32 and the 1st individual software 34 are written. The 1st common software 32 is software common to a plurality of vehicle models, and the 1st individual software 34 is software peculiar to the vehicle model of the vehicle body 10. In other words, the common software 32 and 42 include programs identical between the 1st vehicle model and the 2nd vehicle model, whereas the individual software 34 and 44 include programs different between the 1st vehicle model and the 2nd vehicle model. In the 2nd microcomputer 40, as with the 1st microcomputer 30, the 2nd common software 42 and the 2nd individual software 44 are also written.

[0019] In addition, the controller 20 is additionally attached with an identifier (e.g., ID1) corresponding to a feature different among a plurality of vehicle models. The feature different among a plurality of vehicle models is, for example, a kind of storage battery, an engine displacement, a drive system, or the like. For example, the controller 20 having the same configuration is used in the 1st vehicle model and a 2nd vehicle model having a feature different from the 1st vehicle model. On the other hand, the controller 20 to be mounted on the 1st vehicle model is attached with the identifier ID1, and the controller 20 to be mounted on the 2nd vehicle model is attached with an identifier ID2 different from the identifier ID1. For example, the identifier is contained in the common software 32 and 42.

[0020] The writing device 100 is a device for writing the individual software 34 and 44 to the controller 20. The writing device 100 is configured to be connectable to the CGW 12.

[0021] (Confirmation processing; Figure 2 )

[0022] The confirmation processing of Figure 2 will be described with reference to FIG. 6. The confirmation processing of confirming whether the individual software 34 and 44 are correctly written to the controller 20 is performed by the controller 20. Figure 2 Figure 2 The confirmation processing of

[0023] In S10, the controller 20 confirms the matching between the 1st individual software 34 received from the writing device 100 and the identifier attached to the controller 20. For example, in the 1st individual software 34, an identifier corresponding to a feature of the vehicle model corresponding to the 1st individual software 34 is contained. The controller 20 determines that the 1st individual software 34 matches the identifier in a case where the identifier in the 1st individual software 34 coincides with the identifier attached to the controller 20. The controller 20 proceeds to S12 in a case where it is determined that the 1st individual software 34 matches the identifier (YES in S10).

[0024] In S12, the controller 20 writes the 1st individual software 34 to the 1st microcomputer 30. When S12 ends, the controller 20 proceeds to S20.​

[0025] In S20, the controller 20 confirms the matching between the 2nd individual software 44 received from the writing device 100 and the identifier attached to the controller 20. The method of confirming the matching is the same as that in S10. The controller 20 proceeds to S22 in the case where the 2nd individual software 44 is judged to match the identifier (YES in S20).

[0026] In S22, the controller 20 writes the 2nd individual software 44 to the 2nd microcomputer 40. When S22 ends, the controller 20 proceeds to S40.

[0027] In S40, the controller 20 calculates an error detection code of the combination of the 1st individual software 34 written in S12 and the 2nd individual software 44 written in S22. Here, the error detection code is, for example, a SUM value used in a checksum.

[0028] In S42, the controller 20 judges whether the error detection code calculated in S40 matches a correct value. The judgment of S42 is, for example, a checksum. The correct value is, for example, included in at least one of the individual software 34 and 44 received from the writing device 100.

[0029] The controller 20 proceeds to S44 in the case where the error detection code calculated in S40 is judged to match the correct value (YES in S42). In S44, the controller 20 sends a normal notification indicating that the individual software 34 and 44 have been normally written to the writing device 100.

[0030] Further, the controller 20 proceeds to S46 in the case where the error detection code calculated in S40 is judged not to match the correct value (YES in S42). In S46, the controller 20 sends an abnormal notification indicating that the individual software 34 and 44 have not been normally written to the writing device 100.

[0031] Further, the controller 20 proceeds to S30 in the case where the 1st individual software 34 is judged not to match the identifier (NO in S10) and in the case where the 2nd individual software 44 is judged not to match the identifier (NO in S20). In S30, the controller 20 sends an NG notification indicating that the received individual software is erroneous to the writing device 100.

[0032] When any of S30, S44, and S46 ends, the controller 20 ends the processing of the flowchart of FIG. 6. Figure 2

[0033] (Method of manufacturing vehicle 2; Figure 3 )

[0034] Referring to Figure 3 ​, and a manufacturing method of the vehicle 2 is explained. In the step (a), in a vehicle factory, the vehicle body 10 is prepared, which is mounted with the controller 20 and the CGW 12 in which the common software 32 and 34 are written.

[0035] For example, the common software 32 and 34 are written to the controller 20 in a factory where the controller 20 is manufactured, and shipped to the vehicle factory. Then, in the vehicle factory, the controller 20 is mounted to the vehicle body 10, and thereby the vehicle body 10 mounted with the controller 20 is prepared. At the stage of the step (a), the individual software 34 and 44 has not been written to the controller 20. That is, the vehicle body 10 prepared in the step (a) is a vehicle body before shipment from the factory.

[0036] Further, in a modification, the vehicle body 10 prepared in the step (a) can also be a vehicle body returned to the factory after shipment from the vehicle factory to the market. In this modification, at the stage of the step (a), the individual software 34 and 44 has been written to the controller 20, and at least one of the individual software 34 and 44 is updated.

[0037] In the step (b), the writing device 100 is connected to the central gateway 12 of the vehicle body 10. In the step (c), the writing device 100 sends a writing request including the individual software 34 and 44 to the controller 20. Thereby, in the controller 20, the confirmation processing of Figure 2 is executed. Then, with the matching of the identifier being confirmed as a condition, the individual software 34 and 44 is written to the microcomputers 30 and 40 Figure 2 (S12 and S22).

[0038] In the step (d), the processing after S40 of Figure 2 is executed. As described above, the error detection code is calculated which combines the first individual software 34 and the second individual software 44. As shown by the dotted line, in S40 of Figure 2 , the error detection code is calculated between the individual software 34 and 44, and the error detection code is not calculated between the first common software 32 and the first individual software 34 and between the second common software 42 and the second individual software 44.

[0039] In the step (d), the matching between the individual software 34 and 44 is confirmed due to the error detection code which is calculated between the individual software 34 and 44 and which coincides with the correct value. Thereby, the manufacturing of the vehicle 2 is completed.

[0040] (EFFECTS OF THE PRESENT EMBODIMENT)

[0041] According to the structure of the present embodiment, by confirming the matching between the individual software and the identifier, it is possible to confirm that the correct individual software is selected for the vehicle model which should be manufactured Figure 2Further, after the individual software is written, the matching is confirmed between the individual software actually stored in the controller 20, so that the appropriateness of the written individual software can be double-checked (S42). Since the common software is changed due to the upgrade based on the data obtained from the market, etc., the common software 32 and 34 are not used in the series of checks in the present embodiment. Therefore, even when the common software 32 and 34 are changed, the individual software 34 and 44, the contents of the check (e.g., the correct value), etc. do not need to be modified accordingly, so that the individual software can be correctly written.

[0042] (Correspondence)

[0043] The vehicle body 10 and the controller 20 are each an example of a "vehicle body" and a "controller". The common software 32 and 42 are each an example of "common software". The individual software 34 and 44 are each an example of "individual software". The identifier ID1 is an example of an "identifier". The process (a) is an example of a "first process", and the processes (c) and (d) are each an example of a "second process".

[0044] Hereinafter, points to be noted in relation to the technology shown in the embodiment will be described. The controller 20 can also have three or more microcomputers. In the present modification, three or more individual software can be written to the controller 20, and in the process (d), the error detection code is calculated between the three or more individual software, and the matching is confirmed between the three or more individual software. In the present modification, the three or more individual software are each an example of "individual software".

[0045] Figure 2 The judgment of S10 and S20 can also be performed not by the controller 20 but by the writing device 100. For example, the writing device 100 can receive the identifier from the controller 20, and send the individual software to the controller 20 when the individual software matches the identifier.

Claims

1. A manufacturing method of a vehicle, comprising: a first step of preparing a vehicle body on which a controller is mounted, the controller having written therein common software common to a plurality of vehicle models; and a second step of writing, to the controller mounted on the vehicle body, individual software specific to a vehicle model of the vehicle body, the controller having attached thereto an identifier corresponding to a feature different among the plurality of vehicle models, in the second step, confirming matching between the individual software written to the controller and the identifier before the individual software is written, and confirming matching between the individual software written to the controller after the individual software is written. ​ ​ ​ ​ ​ ​

Images