What is claimed is:
1. An ignition controller for an internal combustion engine comprising:
a crank angle sensor for generating a plurality of crank angle signals periodically in correspondence with a rotational angle of a crankshaft of an internal combustion engine;
a cam sensor for generating cylinder discrimination information of said internal combustion engine in correspondence with a rotational angle of a camshaft rotating in synchronism with said crankshaft; and
a control unit for controlling the ignition energization of each cylinder of said internal combustion engine on the basis of said crank angle signals and said cylinder information,
wherein said control unit includes:
an engine-speed detecting unit for detecting a change in an engine speed of said internal combustion engine; and
an ignition correcting unit for correcting ignition energization time, an ignition energization start timing, and an ignition timing in correspondence a changed engine speed in a case where the change in the engine speed is equal to a greater than a predetermined level.
2. The ignition controller for an internal combustion engine according to claim 1,
wherein said control unit includes:
an engine-speed detecting unit for detecting a change in the engine speed of the internal combustion engine on the basis of an average period of a crank angle; and
an ignition correcting unit for computing an ignition energization start on the basis of a change in the crank angle average period to correct the ignition energization time in a case where the change in the engine speed has been detected.
3. The ignition controller for an internal combustion engine according to claim 1,
wherein said ignition correcting unit effects correction on the basis of an ensuing estimated crank angle average period or effects correction by adding or subtracting a predetermined amount to or from a present crank angle average period.
4. The ignition controller for an internal combustion engine according to claim 1,
wherein said ignition correcting unit corrects again one of the once-corrected ignition energization start timing and ignition timing at the time of inputting of the crank angle signal prior to effecting that ignition control.
5. The ignition controller for an internal combustion engine according claim 1,
wherein said ignition correcting unit synchronizes the corrected ignition energization start timing and ignition timing with a crank angle signal immediately close thereto.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A system for determining hardware diagnostics during initial program loading, comprising:
a processor;
a storage facility that stores hardware identifications corresponding to hardware to be tested;
a memory having stored thereon a utility which executes on the processor to provide the functions of:
allocating a space for a diagnostics hardware table configured to store hardware identifications corresponding to hardware to be tested during the initial program loading;
detecting new hardware by a hardware monitor function;
adding hardware identifications corresponding to the new hardware detected to the diagnostics hardware table;
detecting defective hardware by the hardware monitor function;
adding hardware identifications corresponding to the defective hardware detected to the diagnostics hardware table;
selecting hardware manually;
adding hardware identifications corresponding to the selected hardware to the diagnostics hardware table;
acquiring the hardware identifications to be tested while hardware objects are built by a system Hardware Object Model (HOM);
setting diagnostics flags within the HOM according to the diagnostics hardware table;
performing diagnostics on the hardware objects having set diagnostics flags during the initial program loading;
clearing the diagnostics hardware table following completion of the diagnostics to prevent testing of hardware associated with the hardware objects having set diagnostics flags during the initial program loading during a subsequent initial program loading; and
running an operating system following completion of the initial program loading.
2. The system of claim 1, said utility further comprising converting a suspected defective subsystem identification detected at runtime to a hardware identification.
3. The system of claim 2, said utility further comprising adding the hardware identification of the suspected defective subsystem identification detected at runtime to the diagnostics hardware table.
4. The system of claim 3, said utility further comprising diagnosing the hardware identification of the suspected defective subsystem identification detected at runtime in the diagnostics hardware table during the subsequent initial program loading.
5. A method for determining hardware diagnostics during initial program loading, comprising:
allocating a space for a diagnostics hardware table configured to store hardware identifications corresponding to hardware to be tested during the initial program loading;
detecting new hardware by a hardware monitor function;
adding hardware identifications corresponding to the new hardware detected to the diagnostics hardware table;
detecting defective hardware by the hardware monitor function;
adding hardware identifications corresponding to the defective hardware detected to the diagnostics hardware table;
selecting hardware manually;
adding hardware identifications corresponding to the selected hardware to the diagnostics hardware table;
acquiring the hardware identifications to be tested while hardware objects are built by a system Hardware Object Model (HOM);
setting diagnostics flags within the HOM according to the diagnostics hardware table;
performing diagnostics on the hardware objects having set diagnostics flags during the initial program loading;
clearing the diagnostics hardware table following completion of the diagnostics to prevent testing of hardware associated with the hardware objects having set diagnostics flags during the initial program loading during a subsequent initial program loading; and
running an operating system following completion of the initial program loading.
6. The method of claim 5, further comprising converting a suspected defective subsystem identification detected at runtime to a hardware identification.
7. The method of claim 6, further comprising adding the hardware identification of the suspected defective subsystem identification detected at runtime to the diagnostics hardware table.
8. The method of claim 7, further comprising diagnosing the hardware identification of the suspected defective subsystem identification detected at runtime in the diagnostics hardware table during the subsequent initial program loading.
9. A computer program product having code recorded on a computer readable storage medium for determining hardware diagnostics during initial program loading, said program product comprising code for:
allocating a space for a diagnostics hardware table configured to store hardware identifications corresponding to hardware to be tested during the initial program loading;
detecting new hardware by a hardware monitor function;
adding hardware identifications corresponding to the new hardware detected to the diagnostics hardware table;
detecting defective hardware by the hardware monitor function;
adding hardware identifications corresponding to the defective hardware detected to the diagnostics hardware table;
selecting hardware manually;
adding hardware identifications corresponding to the selected hardware to the diagnostics hardware table;
acquiring the hardware identifications to be tested while hardware objects are built by a system Hardware Object Model (HOM);
setting diagnostics flags within the HOM according to the diagnostics hardware table;
performing diagnostics on the hardware objects having set diagnostics flags during the initial program loading;
clearing the diagnostics hardware table following completion of the diagnostics to prevent testing of hardware associated with the hardware objects having set diagnostics flags during the initial program loading during a subsequent initial program loading; and
running an operating system following completion of the initial program loading.
10. The computer program product of claim 9, further comprising code for converting a suspected defective subsystem identification detected at runtime to hardware identification.
11. The computer program product of claim 10, further comprising code for adding the hardware identification of the suspected defective subsystem identification detected at runtime to the diagnostics hardware table.
12. The computer program product of claim 11, further comprising code for diagnosing the hardware identification of the suspected defective subsystem identification detected at runtime in the diagnostics hardware table during the subsequent initial program loading.