1. Field of Invention
Embodiments of the invention relate, in general, to engine testing and more specifically, the embodiments of the invention relate to methods and systems for managing automation during testing of engine test unit.
[1] An engine needs to be tested to ensure its safety and sustainability while it is running on actual road conditions. The engine is tested for inspecting engine characteristics such as amount of exhaust gases, engine noises, power of engine, fuel leakages etc. These engine characteristics are inspected based on tests that are conducted on the engine using the actual road conditions. The actual road conditions refer to load conditions for the engine that are experienced by the engine while it is in use on a road. For example, a load that is experienced by an engine of a vehicle, when the vehicle runs on a road.
[2] Further, the tests on the engine are performed using testing equipments. For example, a test for measuring a smoke content is performed using a test equipment such as a smoke meter. Moreover, the tests on the engine can be performed in engine test labs so as to avoid practical difficulties that arise with the tests. The practical difficulties can be accuracy in collection of test data during a movement of the engine. The test data provides information regarding results of the tests on the engine. For example, the test data can be data pertaining to gasses that are emitted from an exhaust system of a vehicle engine.
[3] Typically, the tests are performed on the engine using simulated conditions. The simulated conditions are the simulation of on-road conditions for the engine. The simulated conditions can simulate actual service conditions for the engine using the testing equipments. For example, a simulation of road resistance for a vehicle is created by the simulation of a torque moment to the vehicle. Moreover, the test data is recorded during the testing of the engine under the simulated conditions. [4] According to one conventional technique, test data is captured by separately configuring testing equipments for various tests. Each test is performed using various simulated conditions. Further, these simulated conditions are manually configured every time for the each test. This requires operator assistance for manually configuring the simulated conditions.

BRIEF DESCRIPTION OF THE DRAWINGS
The present invention is illustrated by way of an example and is not limited by the example
and / or in the accompanying drawings, in which like references indicate similar elements
and in which:
Fig. 1 illustrates a network environment wherein an exemplary embodiment of the
invention can be practiced.
Fig. 2a and 2b shows a flowchart depicting the requisite steps taken to manage the
automation for controlling a test setup for an engine test unit, in accordance with an
exemplary embodiment of the invention.
DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION
[5] The preferred embodiments of the invention have been described in the following description and it will be clear that the invention is not limited to these embodiments only. Numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present invention. It will be evident that modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art without departing from the spirit and scope of the invention as described in the appended claims. [6] The embodiments of the invention provide a method and a system to manage testing of an engine test unit. The various embodiments of the invention provide a method for managing automation for controlling a test setup for the engine test unit. The test setup is associated with a procedure for the testing of the engine test unit. Moreover, the test setup is used for defining simulated conditions for the testing of the engine test unit. Further, the engine test unit is tested using an engine testing system under simulated conditions. A test setup device is used to define the test setup for the engine test unit. The test set-up device configures the test set-up using engine test parameters for the testing of the engine test unit. The test setup device configures the engine test parameters in an offline mode for the engine test unit. These engine test parameters are provided by an operator. Further, the engine test parameters are used to define the simulated conditions for the test setup. Moreover, the engine test parameters are stored in test parameter libraries. These test parameter libraries can be re-used for the testing of various engine test units. The libraries can contain information regarding testing parameters for various types of tests. [7] Further, the engine test parameters are provided to the engine testing system for testing the engine test unit. The testing of the engine test unit is performed in an online mode for the engine test unit using the engine test parameters. Further, test data for the

engine test unit is acquired during the online mode for the engine test unit. The test data provides information regarding results of the testing of the engine test unit. This test data is acquired using a data acquisition device in an online mode for the engine test unit. Thereafter, the test data is used to generate reports in a post-processing mode for the engine test unit. These reports provide information regarding the results of the testing of the engine test unit using the engine testing system. These reports are made available to the operator using a display device such as a Graphical User Interface (GUI). [8] Fig. 1 illustrates a network environment 100 wherein an exemplary embodiment of the invention can be practiced. Network environment 100 includes an engine test unit 102, an engine testing system 104, a test setup device 106, a data acquisition device 108 and a report generation device 110. According to various embodiments of the invention, engine test unit 102 is an automobile engine that is mounted on engine testing system 104. Examples of engine include, but are not limited to a two stroke engine, a four stroke engine and the like. Engine test unit 102 is mounted on an engine test bed of the engine testing system 104.
[9] According to various embodiments of the invention, engine testing system 104 is used for testing of engine test unit 102 under simulated conditions. According to various embodiments of the invention, the simulated conditions refer to simulation of on-road conditions for engine test unit 102. The simulated conditions simulate actual service conditions for engine test unit 102. For example, road resistance for a vehicle is created by simulation of an additional moment or torque moment to the vehicle. The simulated conditions are utilized for examining mechanical characteristics and other behavioral characteristics associated with engine test unit 102. Further, engine test unit 102 can be a sample engine that is taken from a set of manufactured engines. Engine test unit 102 can also be a prototype of an engine, which is to be used for manufacturing of similar engines. [10] Further, engine test unit 102 is subjected to a series of tests and inspections during simulated motion of engine test unit 102. Example of the series of the tests include but are not limited to, checking thrust on engine test unit 102, verifying gas consumption for engine test unit 102, inspecting plugs on engine test unit 102, testing safety circuits for on engine test unit 102 and the like. Further, the simulated conditions are applied on engine test unit 102 using engine testing system 104.
[11] According to various embodiments of the invention, engine testing system 104 is used for testing of engine test unit 102. Typically, engine testing system 104 has a driving arrangement for applying simulation of the on-road conditions on engine test unit 102. Engine testing system 104 is used for executing the simulated conditions on engine test unit 102. For example, engine testing system 104 has a driving arrangement such as a

pair of parallel rollers for inspecting power or torque characteristics against speed for engine test unit 102. Further, the pair of parallel rollers can be connected to a brake. Moreover, the pair of parallel rollers can have a rough surface to simulate the roughness associated with a road.
[12] Further, engine testing system 104 includes an engine test bed and test measurement devices. Engine test unit 102 is mounted on the engine test bed. Further, the test measurement devices execute various engine tests using the simulated conditions on engine test unit 102. Examples of the test measurement devices include, but are not limited to a smoke meter, fuel meter, gaseous emission analyzer and the like. Typical test measurement devices can be AVL 415S from AVL, MEXA 7000 from Horiba, AMA4000 from Pierburg, Fuel Meter from Benz, AVL 735 from AVL etc.
[13] Further, engine testing system 104 executes the simulated conditions based on engine test parameters. The engine test parameters are used to define the simulated conditions for the testing of engine test unit 102. For example, the engine test parameters are values such as mass of the vehicle, force applied by the vehicle, throttle for the engine and the like. These conditions can create the simulated conditions for road resistance that occurs when the vehicle runs on road. Further, the engine test parameters are provided by an operator. According to various embodiments of the invention, the operator configures the engine test parameters using test setup device 106.
[14] Test setup device 106 is a programmable device comprising a processing means and a memory. According to various embodiments of the invention, test setup device 106 is programmed for controlling a test setup for engine test unit 102. According to various embodiments of the invention, the test setup is a data set of the engine test parameters. Moreover, the test setup provides a procedure for the testing of engine test unit 102. Further, according to various embodiments of the invention, test setup device 106 is used for configuring the test setup in an offline mode for engine test unit 102. The offline mode for engine test cell indicates the mode before testing of engine test cell 102. The operator can define the procedure such as an order of tests that can be performed for the testing of engine test unit 102. For example, the operator uses a computer to define the test setup for an endurance testing of engine test unit 102.
[15] According to various embodiments of the invention, test setup device 106 comprises an authentication module for validating the operator. The authentication module verifies a username and a password that are associated with the operator. Further, according to various embodiments of the invention, the authentication module allows the operator for access to test setup device 106 based on a profile associated with the username and the password. The profile defines a level of authorization to access applications that are

associated with test setup device 106. For example, if the profile is a supervisor profile,
then operator can run the applications in a read-write mode. The authentication module
provides access for configuration rights to the supervisor profile.
[16] Test setup device 106 is used for creating test parameter libraries for the engine test
parameters. According to various embodiments of the invention, test setup device 106
includes a parameter administration module for creating the test parameter libraries. The
test parameter libraries are sets of data that are provided by the operator in the offline
mode for engine test unit 102. The test parameter libraries provide information associated
with the test parameters, formulae to be calculated during the testing, details pertaining to
engine test unit 102, storage details that are associated with the testing. For example, the
test parameter libraries are online formula libraries, test script log libraries, average log
libraries etc.
[17] The online formula libraries contain sets of formulae and each formula corresponds
to a specific test. For example, the online formula libraries are programmed for full throttle
performance tests can contain the formula required to calculate the full throttle of engine
test unit 102. Moreover, the online formula libraries may also contain the sets of general
formula needed for most of the standard tests. The required online formula libraries can
be called while conducting the corresponding test of engine test unit 102.
[18] The test script log libraries contain test run sequences for a specific test. The test
script log libraries can also contain general purpose test run sequence like warm-up for
engine test unit 102.
[19] The average log libraries contain a set of parameters to be averaged for testing
measurements. The average log libraries can be specific to a test or a standard for the
test.
[20] Further, these test parameter libraries can be reused for the configuration of the
engine test parameters associated with various tests for engine test unit 102. For
example, test parameter libraries created for a European Stationary Cycle (ESC) test can
be reused for configuring a European Load Response (ELR) test.
[21] In addition, test setup device 106 is used for creating a test run sequence for the
testing. According to various embodiments of the invention, the test run sequence
determines an order for executing the engine test parameters. The test run sequence is
program that contains instructions that define steps that are to be performed for the
testing. For example, the test run sequence has an instruction set that contain loop
commands for repeating a certain test procedure. A typical example for loop commands
can be,
Reg1=1

Labell
Stepl
Reg1=reg1+1
Ifregl >=10
Exit
Else
Gotol
Endif
In this example engine runs at stepi repeatedly for 10 times.
[22] According to various embodiments of the invention, the test run sequence is a
sequence of operating points or steps on engine test unit 102 such as controlling,
measuring and monitoring, from one step of the testing to a next step of the testing.
Further, a step of the testing is characterized by a demand value for engine test unit 102.
The demand value determines corresponding parameters for engine test unit 102. For
example, the demand value of 2 Volt can correspond to 30 Revolution per Minute (RPM)
of engine test unit 102.
[23] In addition, test setup device 106 can select a start for the test run sequence. For
example a test run sequence has five steps:
Stepl - 4500 RPM and 100% throttle
Step2 - 3500 RPM and 120 Newton Meter (NM) of load
StepS - 100 RPM and 50% throttle
Step4 - 3000 RPM and 100 NM of load
Step5 - 2000 RPM and 75 NM of load
The five steps have five different set points. The set point for the Step 1 is that engine test
unit 102 will be run at 4500 RPM and 100% throttle. The set point for the Step 2 is that
engine test unit 102 will be run at 3500 RPM and 120 NM of load, etc. The operator may
select to start the automatic execution from Step 2 instead of step 1.
[24] According to various embodiments of the invention, test set-up device 106 includes
an operation mode manager. The operation mode manager can switch operation modes
for engine test unit 102. The operation modes for engine test unit 102 can be offline mode,
online mode and post-processing mode. According to various embodiments of the
invention, test set-up device 106 configures the test set-up for engine test unit 102 in the
offline mode for engine test unit 102. The offline mode represents the mode before the
testing for engine test unit 102. Further, offline mode indicates that the control for
acquiring the test data is disabled.

[25] According to various embodiments of the invention the online state for engine test unit 102 indicates that the control for acquiring the test data is activated. Further, the postprocessing mode for engine test unit 102 indicates the state in which reporting and analysis of the acquired test data is done.
[26] According to various embodiments of the invention, test set-up device 106 comprises an operation state manager. In an alternative embodiment, the operation state manager is a separate device from test set-up device 106. The operation state manager is used for switching the operation states for engine test unit 102. The operation states indicate the testing state and control state that are associated with engine test unit 102. The operation states are selected when engine test unit 102 is in the online mode. Further, the operation states for the testing of engine test unit 102 in the online mode can be a monitoring state, a manual state and an automatic state. According to various embodiments of the invention, the monitoring state indicates the state where only the acquisition of the test data takes place and no control function is activated. Moreover, the monitoring state indicates that test set up 106 is initialized for the testing. The operator switches to the manual state or automatic state after the monitoring state for engine test unit 102. [27] Further, the manual state indicates the state where the control functions like engine start/stop etc. are available but these control functions can be operated only manually. Moreover, the operator can take manual measurements for the testing using manual measurement screens. According to various embodiments of the invention, the automatic state indicates the state where the control functions like engine start/stop etc. are available and can be operated automatically as per a test run sequence. Accordingly, control steps define the running of engine test unit 102. The test run sequence determines an order for executing the engine test parameters during the testing. [28] According to various embodiments of the invention, the operation state manager is used for switching engine test unit 102 between the monitoring state for engine test unit 102 and the manual state for engine test unit 102. Further, according to various embodiments of the invention, the operation state manager is used for switching engine test unit 102 between the monitoring state for engine test unit 102 and the automatic state for engine test unit 102. Moreover, according to various embodiments of the invention, the operation state manager first switches to manual state before during the switching of the state from the monitoring state to the automatic state. In an embodiment of the invention, the operation state manager can switch engine test unit 102 between the monitoring state and the automatic state for engine test unit 102 without switching to manual state. [29] Further, test setup device 106 is used for configuring the test measurement devices. According to various embodiments of the invention, the test measurement devices are

used for providing the engine test parameters. Moreover, the test measurement devices can also be used for conducting additional tests for the testing of engine test unit 102. Examples of the additional tests can be engine performance tests, engine emission tests etc.
[30] According to various embodiments of the invention, test setup device 106 can configure channels for acquiring test data. An example of the channel can be a hardware channel. Test setup device 106 selects the channels based on the test parameter libraries, which store information regarding a type of the test or type of engine test unit 102.
[31] According to various embodiments of the invention, the channels are configured for acquiring the test data using data acquisition device 108. The test data can provide information associated with results of the testing of engine test unit 102. For example, the test data provides information on emission of Hydrocarbon levels, Nitrogen oxide (NOa) levels, Carbon monoxide (CO) levels, Carbon dioxide (COa) etc. based on an emission test of engine test unit 102.
[32] According to various embodiments of the invention, data acquisition device 108 is a peripheral device that can gather the test data in an automated fashion using analog and digital measurement units such as sensors that are associated with engine testing system 104. Further, data acquisition device 108 uses a combination of measurement hardware and software for acquiring the test data in an operator-defined manner. An example of data acquisition device 108 can be a Data Acquisition (DAQ) device from National Instruments Corporation, Austin.
[33] According to various embodiments of the invention, data acquisition device 108 gathers signals from the measurement hardware such as the test measurement devices. Thereafter, data acquisition device 108 digitizes the signal for storage and analysis. According to various embodiments of the invention, data acquisition device 108 has channels to gather the signals. Further these channels are configured for specifying the parameters. Accordingly, the test data for the specified parameters are gathered. Further, the test data acquired using data acquisition device 108 can be stored in a file that is associated with the test. Further, data acquisition device 108 can be used to acquire the additional test data from the test measurement devices. According to various embodiments of the invention, the test data acquired using data acquisition device 108 is used for generating reports.
[34] According to various embodiments of the invention, report generation device 110 is provided for generating the reports. The reports are associated with results of the testing of engine test unit 102. According to various embodiments of the invention, report

[38] At step 208, the operator configures the channels for acquiring the test data. Details pertaining to the channels have been explained in reference to Fig.1. According to various embodiments of the invention, the operator selects the channels using test setup device 106. The channels are selected based on the test parameter libraries. The channels are configured in the offline mode for engine test unit 102.
[39] At step 210, test setup device 106 provides the engine test parameters to engine testing system 104. Thereafter, engine testing system 104 defines the simulated conditions for the testing of engine test unit 102.
[40] Further, at step 212, the operation mode manager changes the offline mode for engine test unit 102 to the online mode for engine test unit 102. According to various embodiments of the invention, the operation state manager switches engine test unit 102 in the monitoring state when engine test unit 102 gets into the online mode from the offline mode. Details pertaining to the operation mode manager and the operation state manager have been explained in reference to Fig.1.
[41] Further, at step 214, engine testing system 104 executes the simulated conditions on engine test unit 102 for the testing of engine test unit 102. According to various embodiments of the invention, the operator has an option for selecting the manual state or the automatic state for engine test unit 102. Accordingly, engine testing system 104 is configured for the testing. For example, the operator switches to automatic state and selects a specific test for engine testing unit 102. Thereafter, required parameters for the specific test are automatically selected. According to various embodiments of the invention, engine testing system 104 mounts engine test unit 102 on the engine test bed. Thereafter, the test measurement devices execute the simulated conditions for the testing of engine test unit 102. According to various embodiments of the invention, engine testing system 104 executes the simulated conditions on engine test unit 102 in the online mode for engine test unit 102.
[42] Moreover, at step 216, data acquisition device 108 acquires the test data. Details pertaining to the data acquisition device 108 have been explained in reference to Fig.1. The test data can provide information associated with the results of the testing of engine test unit 102. The test data is acquired based on the channels that are configured by the operator. Details pertaining to the test data have been explained in reference to Fig.1. Further, at step 218, data acquisition device 108 stores the test data in the database that is associated with data acquisition device 108.
[43] At step 220, report generation device 110 generates the report using the test data. Details pertaining to report generation device 110 have been explained in reference to Fig.1. These reports are associated with results of the testing of engine test unit 102.

generation device 110 includes a software program that is capable of generating the reports based on the test data. Typically, the reports provide various graphs such as multiple Y axes graphs with single X-axis, comparator graphs etc. Further, the reports that contain these graphs can be tabular reports, cross-tab reports etc. In addition, report generation device 110 compares the test data using standard test data for generating the comparator graphs. The standard test data is data that is acquired during the testing of engine test unit 102 under pre-defined standard conditions.
[35] According to various embodiments of the invention, report generation device 110 is integrated with test setup device 106. In another embodiment of the invention, report generation device 110 is a separate device from test setup device 106. Further, report generation device 110 includes a display device that provides visual display to the operator for viewing the reports. For example, report generation device 110 provides a Graphical User Interface (GUI) to the operator.
[36] Fig.2 is a flowchart depicting the requisite steps taken to manage automation for controlling the test setup for the engine test unit, in accordance with an exemplary embodiment of the invention. At step 202, test setup device 106 authenticates the operator. Details pertaining to test setup device 106 have been explained in reference to Fig.1. Further, the operator accesses test setup device 106 for configuring the engine test parameters. According to various embodiments of the invention, the authentication module authenticates the operator and provides access rights to configure the engine test parameters. Details pertaining to the authentication module have been explained in reference to Fig.1.
[37] At step 204, the operator configures the engine test parameters. According to various embodiments of the invention, the operator configures the engine test parameters using test setup device 106. Details pertaining to the engine test parameters have been explained in reference to Fig.1. According to various embodiments of the invention, the operator configures the engine test parameters in the offline mode for engine test unit 102. Further, the offline mode for engine test unit 102 indicates a before testing state for the engine test unit 102. Further, at step 206, the operator creates the test parameter libraries for the engine test parameters using a parameter administration module. Details pertaining to the test parameter libraries have been explained in reference to Fig.1. Further, these test parameter libraries can be reused for configuring the engine test parameters for various tests of engine test unit 102. Further, the operator can also add details pertaining to vehicles that are associated with engine test unit 102 with the test parameter libraries.

According to various embodiments of the invention, report generation device 110 generates the reports in the post-processing mode for engine test unit 102. Further, details pertaining to the reports have been explained in reference to Fig.1. [44] Further, at step 222, the operator views the reports using a display device that provides visual display for viewing the reports.
[45] Embodiments of the present invention have the advantage that the need of separately configuring engine test parameters for test measurement devices is minimized. The present invention provides a common platform for configuring the engine test parameters for test measurement devices. Moreover, the test measurement devices are configured in an offline mode for an engine test unit. Further, test parameter libraries that are associated with the engine test parameters can be re-used for performing other tests on the engine test unit. This brings down total testing time for the testing of engine test unit. Further, automation for control of a test setup increases synchronization in control and measurement that is associated with the testing of the engine test unit. [46] Although the invention has been described using a few embodiments herein, it is understood that these embodiments are merely illustrative, and not restrictive, of the present invention. Numerous changes and modifications in the invention as known to those skilled in the art could be made to the embodiment of the present invention without departing from the scope and spirit of the invention as set forth. Therefore, it will be appreciated that the present invention is not to be limited to the details shown and described herein, but the present invention is intend to cover all such changes and modifications as encompassed by the scope of the appended claims.

I/We claim:
1. A method for managing automation for controlling a test setup for an engine test unit,
the test setup being associated with a procedure for testing of the engine test unit in an
engine testing system, wherein the engine testing system executes simulated conditions
for the testing of the engine test unit, the method comprising the steps of:
a. configuring engine test parameters for the testing of the engine test unit in an offline
mode for the engine test unit, wherein the engine test parameters are configured by an
operator, wherein the engine test parameters define the simulated conditions for the test
setup, wherein the offline mode for the engine test unit indicates before testing state for
the engine test unit, wherein the step of configuring the engine test parameters comprises
the step of:
i. creating test parameter libraries for the engine test parameters, wherein the test parameter libraries store information associated with the engine test parameters;
b. providing the engine test parameters to the engine testing system, wherein the
engine testing system performs the testing of the engine test unit under the simulated
conditions;
c. acquiring test data during the testing of the engine test unit using a data acquisition
device in an online mode for the engine test unit, wherein the test data provides
information regarding results of the testing of the engine test unit, wherein the online mode
for the engine test unit indicates the testing state for the engine test unit, wherein the step
of acquiring the test data comprises the step of:
i. storing the test data in the data acquisition device; and
d. generating reports based on the test data in an post-processing mode for the
engine test unit, wherein the reports are associated with the results of the testing of the
engine test unit, wherein the post-processing mode for the engine test unit indicates after
testing state for the engine test unit.
2. The method of claim 1, wherein the step of configuring the engine test parameters
comprises the step of:
a. configuring channels of the data acquisition device, wherein the channels are used for acquiring the test data.
3. The method of claim 1, wherein the step of configuring the engine test parameters
further comprises the step of:

a. creating a test run sequence for the engine test unit, wherein the test run sequence determines an order for executing the engine test parameters for the testing of the engine test unit.
4. The method of claim 1, wherein the step of configuring the engine test parameters
further comprises the step of:
a. authenticating the operator.
5. The method of claim 1, wherein the step of configuring the engine test parameters
further comprises the step of:
a. configuring test measurement devices associated with the engine testing system, wherein the test measurement devices being used for executing the engine test parameters for the testing of the engine test unit.
6. The method of claim 1, wherein the step of creating test parameter libraries further
comprises the step of:
a. creating logs associated with the testing of the engine test unit, wherein the logs are stored in the test parameter libraries.
7. The method of claim 1, wherein the step of providing the engine test parameters further
comprises the step of:
a. selecting a start for a test run sequence, wherein the test run sequence determines an order of execution of the engine test parameters for the testing of the engine test unit.
8. The method of claim 1, wherein the step of acquiring the test data further comprises the
step of:
a. acquiring additional test data from the test measurement devices associated with the engine testing system, wherein the test measurement devices being used for performing additional tests for the testing of the engine test unit, wherein the additional test data is associated with the results of the additional tests.
9. The method of claim 1, wherein the step of generating the reports comprises the step
of:
a. analyzing the test data using standard test data, wherein the standard test data provides information regarding testing of the engine test unit using per-defined standard conditions.

10. The method of claim 1, wherein the step of generating the reports comprises the step
of:
a. displaying the reports using a display device to the operator.
11. A system for managing automation for controlling a test setup for an engine test unit,
the test setup being associated with simulated conditions for testing of the engine test unit
in an engine testing system, the system comprising:
a. a test setup device for controlling the test setup for the engine test unit, wherein
the test setup device comprises
i. a configuration module for configuring engine test parameters in an offline mode for the engine test unit, wherein the engine test parameters define the simulated conditions for the test setup, wherein the offline mode for the engine test unit indicates before testing state for the engine test unit;
ii. a parameter administration module for creating test parameter libraries for the engine test parameters, wherein the test parameter libraries store information for the engine test parameters;
iii. an operation mode manager for switching between operation modes for engine test unit; and
iv. an operation state manager for switching operation states for engine test unit;
b. the engine testing system for performing the testing of the engine test unit under
the simulated conditions;
c. a data acquisition device for acquiring test data during the testing of the engine
test unit in the online mode for the engine test unit, wherein the test data provides
information regarding results of the testing of the engine test unit, wherein the online mode
for the engine test unit indicates testing state for the engine test unit; and
d. a report generation device for generating reports based on the test data, wherein
the reports are associated with results of the testing of the engine test unit.
12. The system of claim 11, wherein the test setup device comprises:
a. an authentication module for authenticating an operator, wherein the operator configures the engine test parameters.
13. The system of claim 11, wherein the test setup device creates a test run sequence for
the engine test unit, wherein the test run sequence determines an order for executing the
engine test parameters for the testing of the engine test unit.

13. The system of claim 11, wherein the test setup device creates a test run sequence for
the engine test unit, wherein the test run sequence determines an order for executing the
engine test parameters for the testing of the engine test unit.
14. The system of claim 11, wherein the report generation device comprises:
a. a display device for displaying the reports.