Control system, and program product employing an embedded mechanism for testing a system's fault-handling capability

1. A control system for a target system to be controlled, said control system comprising:

an embedded control-data table and an embedded inject-fault-data table within a control system for a hardware target system, the control-data table facilitating operation of the target system and the inject-fault-data table facilitating testing of the target system, wherein testing of the target system is facilitated by selectively substituting for the target system one or more inject-fault-data entries of the inject-fault-data table for one or more entries of the control data table;

a security mechanism to restrict utilization of the inject-fault-data table by the control system, wherein a security check by the security mechanism is to be satisfied for the control system to access the inject-fault-data table for testing of the target system using one or more inject-fault-data entries thereof;

wherein the control-data table comprises at least one control-data entry for facilitating control of at least one component of the target system, and the inject-fault-data table comprises at least one inject-fault-data entry for facilitating testing of the least one component of the target system; and

wherein means for utilization of the inject-fault-data table by the control system comprises means for substituting an entry of the at least one inject-fault entry for an entry of the at least one control-data entry as input for use in testing the target system wherein the entry of the at least one control-data entry comprises at least one of a currently-buffered command signal entry or actual sensor data for operation of the target system.

2. The control system of claim 1 , wherein the one or more entries of the control-data table comprise at least one of sensor data or a command parameter.

3. The control system of claim 2 , wherein:

the sensor data of the control-data table is used for at least one of determining at least one command parameter of the control system or monitoring the target system; and

the command parameter of the control-data table facilitates control of at least one component of the target system.

4. The control system of claim 1 , wherein the means for testing of the target system comprises means for verifying a response of the target system to an injected fault, wherein the injected fault within the target system results from employing at least one inject-fault-data entry of the inject-fault-data table during testing of the target system.

5. The control system of claim 1 , wherein the security mechanism comprises means for comparing at least one of a password or a test-mode security bit to at least one defined value.

6. The control system of claim 1 , wherein the security mechanism comprises:

means for comparing a password to an accepted password; and

means for comparing a test-mode security bit to a defined test-mode security bit value.

7. A control system for a target system to be controlled, said control system comprising:

an embedded control-data table and an embedded inject-fault-data table within a control system for a hardware target system, the control-data table facilitating operation of the target system and the inject-fault-data table facilitating testing of the target system, wherein testing of the target system is facilitated by selectively substituting for the target system one or more inject-fault-data entries of the inject-fault-data table for one or more entries of the control data table;

a security mechanism to restrict utilization of the inject-fault-data table by the control system, wherein a security check by the security mechanism is to be satisfied for the control system to access the inject-fault-data table for testing of the target system using one or more inject-fault-data entries thereof;

wherein the control-data table comprises at least one control-data entry for facilitating control of at least one component of the target system, and the inject-fault-data table comprises at least one inject-fault-data entry for facilitating testing of the least one component of the target system; and

wherein the at least one inject-fault-data entry comprises one of a valid fault value and an invalid fault value, and the control system further comprises:

means for comparing the at least one inject-fault-data entry to the invalid fault value to determine whether the at least one inject-fault-data entry is to be used in testing the target system;

means for substituting the at least one inject-fault-data entry for the at least one control-data entry as input for use in testing the target system if the comparing indicates that the at least one inject-fault-data entry does not comprise the invalid fault value; and

means for employing the at least one control-data entry as input to the control system if the comparing indicates that the at least one inject-fault-data entry equals the invalid fault value.

8. At least one program storage device readable by a machine embodying at least one program of instructions executable by the machine to perform a method of controlling a system, said method comprising:

providing an embedded control-data table and an embedded inject-fault-data table for a hardware system, the control-data table facilitating operation of the system and the inject-fault-data table facilitating testing of the system, wherein testing of the system is facilitated by selectively substituting for the system one or more inject-fault-data entries of the inject-fault-data table for one or more entries of the control-data table;

providing a security mechanism to restrict utilization of the inject-fault-data table by the system, wherein a security check by the security mechanism is to be satisfied for the system to access the inject-fault-data table for testing of the system using one or more inject-fault-data entries thereof;

wherein the control-data table comprises at least one control-data entry for facilitating control of at least one component of the system, and the inject-fault-data table comprises at least one inject-fault-data entry for facilitating testing of the least one component of the system; and

wherein utilization of the inject-fault-data table by the system comprises substituting an entry of the at least one inject-fault entry for an entry of the at least one control-data entry as input to the at least one component of the system for use in testing the system, wherein the entry of the at least one control-data entry comprises at least one of a currently-buffered command signal entry or actual sensor data for operation of the system.

9. The at least one program storage device of claim 8 , wherein the at least one inject-fault-data entry comprises one of a valid fault value and an invalid fault value, and the method further comprises:

comparing the at least one inject-fault-data entry to the invalid fault value to determine whether the at least one inject-fault-data entry is to be used in testing the system;

substituting the at least one inject-fault-data entry for the at least one control-data entry as input for use in testing the system if the comparing indicates that the at least one inject-fault-data entry does not comprise the invalid fault value; and

employing the at least one control-data entry as input to the system if the comparing indicates that the at least one inject-fault-data entry equals the invalid fault value.

10. The at least one program storage device of claim 8 , wherein the one or more entries of the control-data table comprise at least one of sensor data or a command parameter.

11. The at least one program storage device of claim 10 , wherein:

the sensor data of the control-data table is used for at least one of determining at least one command parameter of the system or monitoring the system; and

the command parameter of the control-data table facilitates control of at least one component of the system.

12. The at least one program storage device of claim 8 , wherein the testing of the system comprises verifying a response of the system to an injected fault, wherein the injected fault within the system results from employing at least one inject-fault-data entry of the inject-fault-data table during testing of the system.

13. The at least one program storage device of claim 8 , wherein the security check comprises comparing at least one of a password or a test-mode security bit to at least one defined value.

14. The at least one program storage device of claim 8 , wherein the security check comprises:

comparing a password to an accepted password; and

comparing a test-mode security bit to a defined test-mode security bit value.