JP2009214614A - Software writing method and writing system into ecu - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software writing method and a writing system into ECUs that achieve tact shortening and the improvement of degree of process freedom. <P>SOLUTION: The software writing method includes: a vehicle information input step, in which vehicle information identifying a vehicle 120 is input into the writing system; an assembling state detection step, in which an assembling state detection means 100 periodically detects the assembling states of a plurality of ECUs 110 etc.; a vehicle information transmission step, in which, when the assembling state of either one of the ECUs satisfies a certain condition inherent in that ECU, the transmission means 100 transmits the vehicle information to a host system 130; a software specific information receiving step, in which a receiving means 100 receives software specific information corresponding to the vehicle information transmitted by the host system; and a writing step, in which a software writing means 100 transmits the software stored by a storage means 100 in advance to the ECUs and writes it into the ECUs from the software specific information. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a software writing method and writing system to an ECU (Electric Control Unit), and more particularly to a software writing method and writing system for writing software to an ECU assembled in a vehicle.

  A plurality of ECUs for controlling the vehicle are mounted on the vehicle. Usually, ECUs use common hardware that can be applied to multiple vehicles to reduce costs, and write multiple software that is appropriate for each vehicle type to each ECU before and after assembly to the vehicle on the production line. Has been done.

As a software writing method in a production line, techniques described in the following documents are known. That is, the software writing terminal is connected to the network of the corresponding vehicle, the information for identifying the vehicle acquired by communication with the vehicle is wirelessly transmitted to the host system, and the software instruction to be written to the ECU is received from the host system. And the method of writing in the applicable ECU what received the instruction | indication which should be written in ECU among the some software previously hold | maintained at the software writing terminal is known.
JP 2005-202594 A

  However, each ECU usually has a unique write condition such that another ECU is already assembled in order to write software to the ECU. On the other hand, in the above-described known technology, after a plurality of ECUs to be assembled to the vehicle are assembled to the vehicle, it is necessary to collectively write to the ECU. A dedicated writing process must be arranged. As described above, when writing to the ECU is performed by arranging a dedicated writing process, there is a problem that the tact time becomes long and the degree of freedom of the process decreases.

  The present invention has been made to solve such problems. In other words, the software writing device monitors the mounting state of the ECU in the ECU in the ECU mounting process, and when any ECU detects that the writing conditions specific to the ECU are satisfied, an instruction from the host system Based on the above, software is written in the ECU each time. This makes it possible to perform software writing to each ECU in a distributed manner in the ECU assembling process, thereby realizing a reduction in tact time and an improvement in process flexibility.

  In order to solve the above problems, a software writing method to an ECU according to the present invention is a software writing method to an ECU by a software writing system that writes software to each of a plurality of ECUs assembled to the vehicle, and identifies the vehicle. Vehicle information input stage in which an operator inputs vehicle information to the system, an assembly state detection stage in which the system periodically detects a state in which a plurality of ECUs and other parts are assembled in the vehicle, and detection The vehicle information transmission stage for transmitting the input vehicle information to the host system when the assembled state satisfies a certain condition inherent to each ECU for any ECU, and the host system Software specifying information for specifying software to be written to the ECU corresponding to the vehicle information to be transmitted Receiving software specifying information and a writing step of transmitting to the ECU and writing to the ECU software to be written to each of a plurality of ECUs based on the received software specifying information. It is characterized by.

  Further, a software writing system to the ECU according to the present invention is a software writing system to the ECU for writing software to each of a plurality of ECUs assembled to the vehicle, and input means for inputting vehicle information for identifying the vehicle. And an assembly state detection means for periodically detecting an assembly state in which a plurality of ECUs and other parts are assembled to the vehicle, and an assembly state detected by the assembly state detection means, An ECU corresponding to the vehicle information transmitted by the host system, and a transmission unit that transmits the vehicle information input to the input unit to the host system when a certain condition inherent to the ECU is satisfied for any ECU Receiving means for receiving software specifying information for specifying the software to be written in, and writing to each of the plurality of ECUs A storage unit that stores software to be stored in advance; and a software writing unit that transmits the software stored in the storage unit and writes the software into the ECU based on the software identification information acquired by the software identification information acquisition unit. .

  According to the software writing method and the writing system for the ECU according to the present invention, a dedicated writing process is not required, so that tact time can be reduced.

  Further, the degree of freedom in the process can be improved, and it is possible to easily cope with a shift in production order or reorganization.

  BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the best embodiment of a software writing method and writing system to an ECU according to the present invention will be described in detail with reference to the drawings.

  FIG. 1 is an explanatory diagram for explaining an embodiment of a software writing method according to the present invention. FIG. 2 is a diagram showing a state in which the software writing device according to the embodiment of the present invention is connected to a network in the vehicle.

  An embodiment of a software writing method and a writing system according to the present invention will be schematically described with reference to FIG. The process of assembling the ECU to the vehicle 120 includes process 1, process 2, process 3, process 4, and subsequent processes, and the process of assembling the ECU is sequentially performed in this order. The vehicle 120 is equipped with a large number of ECUs for controlling the vehicle. The ECU is usually made up of hardware with a certain degree of versatility that can be applied to a plurality of uses and a plurality of vehicles for cost reduction, and is suitable for each use and each vehicle type in the vehicle production line. Writing software. In the software writing method and the writing system according to the embodiment of the present invention, the writing of software to each ECU by the software writing device (software writing system) 100 is distributed in the assembly process of the ECU.

  As will be described later, the software writing device 100 may include a CPU, an input unit, an antenna unit, a transmission / reception unit, a memory, an interface, and a display unit. The software writing device 100 is configured to be capable of wireless information communication with the host system 130.

  The host system 130 can include a computer 132, a data transmission / reception device 131, and a server 133. These components are connected to a common network. The data transmission / reception device 131 can perform wireless information communication with at least the software writing device 100 existing in the assembly process line of the ECU. The computer 132 controls the data transmission / reception device 131 and the server 133. The server 133 stores data transmitted from the software writing device 100 as needed, and stores necessary data related to software writing to the ECU in advance.

  In step 1, vehicle information of the target vehicle is input to a software writing device 100, which is a device for writing software to the ECU, and connected to a network in the vehicle (hereinafter referred to as "vehicle network"). The in-vehicle network may be a CAN (Controller Area Network) network. The vehicle information is information including the vehicle type and identification information of the target vehicle.

  In step 2, the first ECU 110 to be assembled first is assembled. At this time, the software writing device 100 detects that the first ECU 110 has been assembled through the in-vehicle network. Here, the plurality of ECUs assembled to the vehicle can be written only when other ECUs and components are assembled to the vehicle (hereinafter referred to as “assembled state”) in a certain assembled state. There are those having specific conditions for the purpose (hereinafter referred to as “write conditions”). Therefore, the software writing device 100 determines whether or not the first ECU 110 has a writing condition, and if it does not have the writing condition, transmits the vehicle information to the host system 130. Then, the software writing device 100 receives information (hereinafter referred to as “software specifying information”) that specifies software to be written to the ECU corresponding to the vehicle information from the host system 130. The software writing device 100 stores software to be written in each ECU in advance. The software writing device 100 writes software in the first ECU 110 by transmitting software specified by the software specifying information from the stored software to the first ECU 110 through the in-vehicle network. When the first ECU 110 has the write condition, the software writing device 100 periodically detects whether the write condition is satisfied, and when the write condition is satisfied, the same processing as that when the write condition is not satisfied is described above. I do.

  The same process as the process 2 mentioned above is performed also in the assembly process of ECU after the process 3, the process 4, and the following.

  Next, with reference to FIG. 2, an embodiment of a software writing method and writing system to the ECU according to the present invention will be described in detail. As shown in FIG. 2, a software writing device (software writing system, assembly state detection means, transmission means, reception means, storage means, software writing means, write verification means) 200 is a CPU (Central Processing Unit) 201, input Unit (input unit) 202, antenna unit (transmission unit, reception unit) 203, transmission / reception unit (transmission unit, reception unit) 204, memory (storage unit) 205, interface 206, and display unit 207.

  The CPU 202 is a device that executes a program stored in the memory 205, receives data from the memory 205 or the input unit 202, calculates and processes the data, and outputs the data to the memory 205 or the display unit 207.

  The input unit 202 includes a barcode reader, and has a function of reading vehicle information from a barcode attached to the vehicle. The input unit 202 may be a keyboard. In this case, the operator needs to input vehicle information from the keyboard.

  The antenna unit 203 transmits information by radiating a high-frequency current including information as an electromagnetic wave to the space, and receives the information by converting the electromagnetic wave including the spatial information into a high-frequency current.

  The transmission / reception unit 204 converts the information to be transmitted into a high-frequency current to be supplied to the antenna unit 203 at the time of transmission, and can be processed in the CPU 201 or the memory 205 upon receiving a high-frequency current including information from the antenna unit 203 at the time of reception To correct data.

  The memory 205 includes a main storage device and an auxiliary storage device. The main storage device performs data processing mainly in cooperation with the CPU 202. The auxiliary storage device mainly stores data to be saved. The main storage device may be a DRAM (Dynamic Random Access Memory) or an SRAM (Static Random Access Memory). The auxiliary storage device may be a hard disk device or a flash memory.

  The interface 206 stands between the two and mediates the exchange of information. By connecting the interface 206 to the in-vehicle network, the software writing device 200 is connected to the in-vehicle network 220.

  The display unit 207 is a display device such as a CRT display, a liquid crystal display, a plasma display, or an LED.

  The configuration of the software writing device 200 has been described above. As an example of a device having such a function, there is a PDA (Personal Digital Assistant) with a built-in wireless LAN card, and even if the PDA is used as the software writing device 200, Good.

  The ECUs 210, 211, and 212 are connected to the in-vehicle network 220 by being assembled in the vehicle. The software writing device 200 and the ECUs 210, 211, and 212 assembled in the vehicle can transmit and receive data to and from each other through the in-vehicle network 220. The in-vehicle network is a wired network, but may be a wireless network.

  FIG. 3 is a view showing a flowchart of the software writing method to the ECU according to the first embodiment of the present invention. Hereinafter, this embodiment will be described in detail for each step.

[S300]
Enter vehicle information. That is, the operator inputs vehicle information to the software writing device by reading a barcode attached to the vehicle with a barcode reader. The input of vehicle information may be performed by an operator typing vehicle information from a keyboard. As described above, the vehicle information is information including the vehicle type and identification information of the target vehicle. Since the information for identifying the target vehicle is included, the vehicle information is different even for the same vehicle type.

[S301]
A software writing device is installed in the vehicle. That is, the operator connects the software writing device to the in-vehicle network by mounting the software writing device on the vehicle. When the software writing device is mounted on a vehicle, it can transmit / receive data to / from an ECU connected to the in-vehicle network.

[S302]
Detect assembly status. That is, the software writing device periodically detects whether any ECU (and a part associated therewith) is assembled. The detection can be performed by the software writing device transmitting a test signal to the in-vehicle network and detecting a response signal to the test signal from the ECU connected to the in-vehicle network. The software writing device may transmit the detected assembly state to the host system. The steps after this step are automatically performed by the software writing device.

[S303]
Determine if there is a write condition. That is, the software writing device determines whether or not an ECU (hereinafter referred to as “target ECU”) that has been detected as being assembled to the vehicle in step S302 has a writing condition. Here, as described above, the write condition is a condition unique to the ECU that can be written only when the assembly state of the other ECUs and components is in a certain assembly state. For example, if the target ECU is an inter-vehicle distance control unit, software may be written to the target ECU only after the vehicle behavior control unit is assembled. In this case, the target ECU sets the write condition. Will have.

  FIG. 4 is a diagram showing the ECU assembled to the vehicle and the presence or absence of the write condition. This means that the part indicated by a circle in the figure has a write condition. For example, the second ECU (ECU2) can write software only after the first ECU (ECU1) is assembled. Write condition data is stored in advance in a software writing device.

  Here, although it has been described that the software writing device determines the writing condition, the host system may determine the writing condition based on the vehicle information. In this case, it is necessary to store write condition data in the host system in advance.

[S304]
When the target ECU has a write condition, the software writing device detects the assembled state. That is, the assembly state is read in order to determine whether the current assembly state satisfies the writing condition of the target ECU in the next step S305. The software writing device may transmit the detected assembly state to the host system.

[S305]
It is determined whether the target ECU satisfies the write condition. That is, the software writing device determines whether or not the assembled state detected in step S304 satisfies the writing condition of the target ECU. If it is determined that the write condition is not satisfied, the process returns to step S304, and the assembly state is detected again. That is, the assembly state is periodically detected until the assembly process of the ECU proceeds and the assembly state satisfies the writing condition of the target ECU.

[S306]
Send vehicle information to the host system. That is, the software writing device transmits vehicle information to the host system in order to receive a software instruction to be written to the target ECU from the host system.

[S307]
Send software specific information. That is, based on the vehicle information transmitted to the host system by the software writing device in step S306, the host system transmits software specifying information that is information for specifying software to be written to the ECU assembled to the vehicle to the software writing device. To do. Data on the relationship between the software specifying information and the vehicle information is stored in advance in a server of the host system. Here, the host system can identify the software writing device that has transmitted the vehicle information by its IP address or MAC address. Therefore, the host system can specify the software writing device by adding the IP address or MAC address of the software writing device to be transmitted to the software specifying information, and transmit the software specifying information. The software writing device receives software writing information to which its own IP address or MAC address is added.

[S308]
Write software to the ECU. That is, the software writing device writes software to the target ECU by transmitting to the target ECU software specified by the software specifying information received from the host system among the software stored in advance. The software is transmitted to the target ECU through the in-vehicle network.

[S309]
Check whether the writing of the software to the target ECU has been completed normally. In other words, the software writing device reads out the written software from the target ECU and compares it with the stored software, thereby confirming whether the writing of the software has been completed normally.

[S310]
In step S309, when it is confirmed that the writing of the software to the target ECU is not completed normally, the software writing device warns the operator of the writing abnormality. The warning is performed by displaying on the display unit of the software writing device. For example, the operator can be warned by LED display. The operator who receives the warning can take measures such as rewriting. Since the operator is immediately warned of the writing abnormality, the software writing in each process can be independently guaranteed.

[S311]
Sends the completion of writing to the host system. In other words, the software writing device transmits the software to one of the ECUs normally and then transmits to the host system that the writing has been completed normally each time. By notifying the host system that writing to the target ECU has been completed normally and leaving a log in the host system, it is possible to carry out a software writing check on the ECU in the process simultaneously with the ECU assembly process. The inspection process time can be shortened.

[S312]
The assembly state after writing is detected and transmitted to the host system. That is, the software writing device periodically detects the assembly state and transmits it to the host system. By notifying the host system of the assembly state after writing and leaving a log in the host system, it is possible to inspect the parts assembly to the vehicle in the process at the same time as the ECU assembly process. It can be shortened.

  The flowchart of the software writing method to the ECU shown in FIG. 3 is continuously repeated until the ECU assembly process is completed and the software writing to all ECUs assembled to the vehicle is completed. As described above, since the writing of software to each ECU is performed in a distributed manner in the ECU assembling process, a dedicated writing process is not required, and the tact can be shortened. Further, the degree of freedom in the process can be improved, and it is possible to easily cope with a shift in production order or reorganization.

  After the writing of software to all ECUs is completed, the operator removes the software writing device from the vehicle.

  Step S300 in the present embodiment corresponds to the vehicle information input stage of the present invention, step S302 corresponds to the assembly state detection stage, and steps S303 to S306 correspond to the vehicle information transmission stage. Step S307 corresponds to software specifying information receiving means, and S308 corresponds to a writing stage. S309 and S310 correspond to the write verification stage, S311 corresponds to the write verification result transmission stage, and S312 corresponds to the assembly state transmission stage.

As mentioned above, although the software writing method and writing system to ECU which concern on 1st Embodiment of this invention were demonstrated in detail, this 1st Embodiment has the following effects.
・ Tact can be shortened because a dedicated writing process is not required.
-The process flexibility can be improved, and it is possible to easily cope with production order shifts and rearrangements.
-Since the software writing inspection to the ECU in the process can be performed simultaneously with the ECU assembly process, the time of the inspection process can be shortened.
・ Since the operator is immediately warned of the writing abnormality, the software writing of each process can be independently guaranteed.

  FIG. 5 is a view showing a flowchart of a software writing method to the ECU according to the second embodiment of the present invention. Hereinafter, this embodiment will be described in detail for each step.

[S500]
The host system receives the assembly status. That is, the upper system receives the assembly state periodically transmitted by the software writing device to the upper system in step S312 of the first embodiment. Here, the second embodiment can be implemented by being incorporated into the first embodiment by being connected to step S312 of the first embodiment. However, the step of the first embodiment to which this step can be connected is not limited to step S312, and may be connected to any step as long as the software writing device transmits the assembly state to the host system.

[S501]
Compare the assembly status with the component assembly information table. That is, the host system compares the component information table stored in advance in the server with the assembly state received from the software writing device.

  FIG. 6 is a diagram showing a component assembly information table. The host system compares this table with the assembly state received from the software writing device.

[S502]
The host system (assembly state verification means) determines whether the assembly state matches the component assembly information table.

[S503]
In step S502, when it is determined that the assembly state does not match the component assembly information table, the host system notifies the software writing device that there is an error in component assembly.

[S504]
An operator is warned of an error in assembling parts by LED display of the software writing device. In other words, the software writing device receives a notification from the host system that there is an error in component assembly, and warns with an LED display in order to inform the operator of this. The operator takes measures such as changing parts based on the warning.

  Steps S500 to S504 in the present embodiment correspond to the assembly state verification stage of the present invention.

As mentioned above, although the software writing method and writing system to ECU which concern on 2nd Embodiment of this invention were demonstrated in detail, this 2nd Embodiment has the following effects other than the effect which 1st Embodiment has.
-Since the part assembly inspection in the process can be performed simultaneously with the assembly process of the ECU, the time of the inspection process can be shortened.
-Since the operator is immediately warned of an abnormality in the assembly of the parts, self-assurance of the assembly of the parts for each process can be performed.

It is explanatory drawing for demonstrating embodiment of the software writing method which concerns on this invention. It is a figure showing the state where the software writing device concerning the embodiment of the present invention is connected to the network in vehicles. It is the figure which showed the flowchart of the software writing method to ECU which concerns on 1st Embodiment of this invention. It is a figure which shows the presence or absence of ECU and writing conditions assembled | attached to a vehicle. It is a figure which shows the flowchart of the software writing method to ECU which concerns on 2nd Embodiment of this invention. It is a figure which shows a components assembly | attachment information table.

Explanation of symbols

100, 200 Software writing device (software writing system, assembly state detection means, transmission means, reception means, storage means, software writing means, write verification means),
110, 210 1st ECU,
111, 211 second ECU,
112 3rd ECU,
120 vehicles,
130 Host system (assembly state verification means),
131 data transmission / reception device,
132 computers,
133 servers,
201 CPU,
202 input unit (input means),
203 Antenna part (transmission means, reception means),
204 transceiver unit (transmitting means, receiving means),
205 memory (storage means),
206 interface,
207 display,
212 nECU,
220 In-car network.

Claims (7)

A software writing method to the ECU by a software writing system that writes software to each of a plurality of ECUs assembled in a vehicle,
A vehicle information input stage in which an operator inputs vehicle information for identifying the vehicle into the system;
An assembly state detection stage in which the system periodically detects a state in which the plurality of ECUs and other components are assembled to the vehicle;
Vehicle information for transmitting the inputted vehicle information to a host system when the detected assembly state satisfies a certain condition inherent to each ECU for any of the ECUs The transmission phase;
A software specifying information receiving step for receiving software specifying information for specifying software to be written in the ECU corresponding to the vehicle information transmitted by the host system;
Based on the received software specifying information, the software to be written to each of the plurality of ECUs among the software stored in advance, the writing step of transmitting to the ECU and writing to the ECU,
A method of writing software to the ECU, comprising: A write verification step for verifying whether the software written in the ECU is normal;
A write verification result transmission stage for transmitting the verified verification result to the host system;
An assembly state transmission step of transmitting the detected assembly state to the host system;
The host system verifies whether or not the assembly state is normal;
The method for writing software to the ECU according to claim 1, further comprising: The assembly state transmission step and the assembly state verification step are performed periodically,
The method for writing software to an ECU according to claim 2, wherein the write verification step and the write verification result transmission step are performed when software is written in any of the ECUs.   The input vehicle information is wirelessly transmitted to a host system, and the software specifying information transmitted by the host system is wirelessly received from the host system. To write software to the ECU. A software writing system to the ECU for writing software to each of a plurality of ECUs assembled in a vehicle,
Input means for inputting vehicle information for identifying the vehicle;
Assembly state detection means for periodically detecting an assembly state in which the plurality of ECUs and other components are assembled to the vehicle;
When the assembly state detected by the assembly state detection unit satisfies a certain condition inherent to each ECU, the vehicle information input to the input unit is A transmission means for transmitting to the host system;
Receiving means for receiving software specifying information for specifying software to be written in the ECU corresponding to the vehicle information, transmitted by the host system;
Storage means for storing in advance software to be written in each of the plurality of ECUs;
Based on the software identification information acquired by the software identification information acquisition unit, software writing unit that transmits the software stored in the storage unit and writes the software in the ECU;
A system for writing software to an ECU, comprising: The software writing means further has write verification means for verifying whether the software written in the ECU is normal,
An assembly state verification means for verifying whether the assembly state is normal;
The transmission unit further transmits the assembly state detected by the assembly state detection unit and the verification result verified by the write verification unit to the host system,
6. The system for writing software to an ECU according to claim 5, wherein the assembly state verification unit forms part of the host system.   7. The system for writing software to an ECU according to claim 5 or 6, wherein the transmission means is information transmission means to the host system wirelessly, and the reception means is information reception means from the host system wirelessly. .

Images