Abstract: A fuel injection controller controls a fuel injector which injects a fuel directly into a cylinder of an engine. The fuel injection controller conducts a correction to increase a fuel injection quantity injected from the fuel injector according to a fuel-adhered quantity which is an amount of the fuel adhered to an opened intake valve. Thus, even when the fuel is adhered to the intake valve, an appropriate amount of the fuel can be injected into the cylinder.

Abstract: In a fuel injection controller that controls a fuel injection device that injects fuel directly into cylinders of an engine, a unit that detects an interference period gradually shifts an injection period of fuel from the fuel injector from a first period during which the injection period does not overlap with an initial value of the interference period, and is distant from the initial value by a given value or larger toward a second period during which the injection period overlaps with the initial value of the interference period. Then, the fuel injection controller detects an actual interference period according to a variation of an air-fuel ratio (A/F value) detected by an air-fuel ratio sensor toward lean.

Abstract: An in-vehicle electronic control unit (ECU), stores behavior information, when a specific vehicle behavior (i.e. a vehicle behavior that does not correspond to the driver's driving operation) is detected. The in-vehicle electronic control unit (ECU) stores, as the behavior information, vehicle travel information, a storage time of the vehicle travel information, and storage execution information that indicates that the vehicle travel information is stored. When the engine of the vehicle stops, the ECU first executes an abnormality check of a CPU operation, when, based on the storage execution information of the behavior information, the vehicle travel information is stored. The ECU stores, as abnormality check information, an abnormality check result, an execution time of the abnormality check, and check execution information indicating that the abnormality check has been executed, and after the storage of the abnormality check information, the ECU stops power supply to the CPU.

Abstract: In a fuel injection controller that controls a fuel injection device that injects fuel directly into cylinders of an engine, a unit that detects an interference period gradually shifts an injection period of fuel from the fuel injector from a first period during which the injection period does not overlap with an initial value of the interference period, and is distant from the initial value by a given value or larger toward a second period during which the injection period overlaps with the initial value of the interference period. Then, the fuel injection controller detects an actual interference period according to a variation of an air-fuel ratio (A/F value) detected by an air-fuel ratio sensor toward lean.

Abstract: A fuel injection controller controls a fuel injector which injects a fuel directly into a cylinder of an engine. The fuel injection controller conducts a correction to increase a fuel injection quantity injected from the fuel injector according to a fuel-adhered quantity which is an amount of the fuel adhered to an opened intake valve. Thus, even when the fuel is adhered to the intake valve, an appropriate amount of the fuel can be injected into the cylinder.

Abstract: A first microcomputer in an ECU outputs a CID of the ECU in response to a request from a scan tool when the ECU has multiple microcomputers implemented therein. Each of the multiple microcomputers has an additive value stored therein for counting an update of the software. The additive values from the multiple microcomputers are added as a sum total of the ECU that is further added to a CID base value. The sum total of the ECU added to the CID base value is then output as the CID of the ECU from the first microcomputer to the scan tool. Therefore, information stored in the first microcomputer is not necessarily changed for outputting an updated CID (e.g., software product number information) from the ECU.

Abstract: An in-vehicle electronic control unit (ECU), stores behavior information, when a specific vehicle behavior (i.e. a vehicle behavior that does not correspond to the driver's driving operation) is detected. The in-vehicle electronic control unit (ECU) stores, as the behavior information, vehicle travel information, a storage time of the vehicle travel information, and storage execution information that indicates that the vehicle travel information is stored. When the engine of the vehicle stops, the ECU first executes an abnormality check of a CPU operation, when, based on the storage execution information of the behavior information, the vehicle travel information is stored. The ECU stores, as abnormality check information, an abnormality check result, an execution time of the abnormality check, and check execution information indicating that the abnormality check has been executed, and after the storage of the abnormality check information, the ECU stops power supply to the CPU.

Abstract: A first microcomputer in an ECU outputs a CID of the ECU in response to a request from a scan tool when the ECU has multiple microcomputers implemented therein. Each of the multiple microcomputers has an additive value stored therein for counting an update of the software. The additive values from the multiple microcomputers are added as a sum total of the ECU that is further added to a CID base value. The sum total of the ECU added to the CID base value is then output as the CID of the ECU from the first microcomputer to the scan tool. Therefore, information stored in the first microcomputer is not necessarily changed for outputting an updated CID (e.g., software product number information) from the ECU.

Abstract: Disclosed is an electronic control apparatus for a vehicle which includes: 1) first storage means for storing vehicle identification information unique to the vehicle; 2) second storage means for storing immobilizer identification information unique to the vehicle; 3) command receiving means for receiving, from an external control apparatus, an update command that commands the electronic control apparatus to update the vehicle identification information stored in the first storage means; and 4) information handling means for handling all the information stored in the first and second storage means. Moreover, in the electronic control apparatus, upon receipt of the update command by the command receiving means, the information handling means updates the immobilizer identification information stored in the second storage means as well as the vehicle identification information stored in the first storage means.

Abstract: An electronic control unit installed in a vehicle performs diagnosis of plural diagnosis objects based on sensor signals, and stores diagnosis results that indicate abnormality of the diagnosis objects in a DTC storage area only when the DTC storage area does not store data having an initial value. The data in the DTC storage area is, in other words, rewritten to different values from the initial value for allowing storage of DTCs when the electronic control unit determines that all of the diagnosis objects are in a normal condition with no indication of abnormality after performing diagnosis, thereby making it possible to exclusively prevent useless abnormality information detected during a vehicle manufacturing process from being stored in an rewritable non-volatile memory.

Abstract: A first microcomputer in an ECU outputs a CID of the ECU in response to a request from a scan tool when the ECU has multiple microcomputers implemented therein. Each of the multiple microcomputers has an additive value stored therein for counting an update of the software. The additive values from the multiple microcomputers are added as a sum total of the ECU that is further added to a CID base value. The sum total of the ECU added to the CID base value is then output as the CID of the ECU from the first microcomputer to the scan tool. Therefore, information stored in the first microcomputer is not necessarily changed for outputting an updated CID (e.g., software product number information) from the ECU.

Abstract: An electronic control unit (ECU) for a vehicle is disclosed. The subject ECU stores: vehicle ID; and first cross-check information different from the vehicle ID. The subject ECU acquires second cross-check information different from the vehicle ID. The second cross-check information is stored in an external ECU that is mounted in a same vehicle as the subject ECU is mounted. The subject ECU determines whether the first cross-check information matches the second cross-check information. Upon receiving an instruction for changing the vehicle ID, the subject ECU prohibits a change the vehicle ID if the first cross-check information matches the second cross-check information, and the subject ECU changes the vehicle ID if the first cross-check information does not match the second cross-check information.

Abstract: Disclosed is an electronic control apparatus for a vehicle which includes: 1) first storage means for storing vehicle identification information unique to the vehicle; 2) second storage means for storing immobilizer identification information unique to the vehicle; 3) command receiving means for receiving, from an external control apparatus, an update command that commands the electronic control apparatus to update the vehicle identification information stored in the first storage means; and 4) information handling means for handling all the information stored in the first and second storage means. Moreover, in the electronic control apparatus, upon receipt of the update command by the command receiving means, the information handling means updates the immobilizer identification information stored in the second storage means as well as the vehicle identification information stored in the first storage means.

Abstract: An electronic control unit (ECU) for a vehicle is disclosed. The subject ECU stores: vehicle ID; and first cross-check information different from the vehicle ID. The subject ECU acquires second cross-check information different from the vehicle ID. The second cross-check information is stored in an external ECU that is mounted in a same vehicle as the subject ECU is mounted. The subject ECU determines whether the first cross-check information matches the second cross-check information. Upon receiving an instruction for changing the vehicle ID, the subject ECU prohibits a change the vehicle ID if the first cross-check information matches the second cross-check information, and the subject ECU changes the vehicle ID if the first cross-check information does not match the second cross-check information.

Abstract: A first microcomputer in an ECU outputs a CID of the ECU in response to a request from a scan tool when the ECU has multiple microcomputers implemented therein. Each of the multiple microcomputers has an additive value stored therein for counting an update of the software. The additive values from the multiple microcomputers are added as a sum total of the ECU that is further added to a CID base value. The sum total of the ECU added to the CID base value is then output as the CID of the ECU from the first microcomputer to the scan tool. Therefore, information stored in the first microcomputer is not necessarily changed for outputting an updated CID (e.g., software product number information) from the ECU.

Abstract: An electronic control unit installed in a vehicle performs diagnosis of plural diagnosis objects based on sensor signals and the like, and stores diagnosis results that indicate abnormality of the diagnosis objects in a DTC storage area only when the DTC storage area does not store data having an initial value. The data in the DTC storage area is, in other words, rewritten to different values from the initial value for allowing storage of DTC when the electronic control unit determines that all of the diagnosis objects are in a normal condition with no indication of abnormality after performing diagnosis, thereby making it possible to exclusively preventing useless abnormality information detected during a vehicle manufacturing process from being stored in an rewritable non-volatile memory.