GB2543852A

GB2543852A - Method for end of line testing of a vehicle with a work implement

Info

Publication number: GB2543852A
Application number: GB1519343.6A
Authority: GB
Inventors: Cornillon Bruno; Piquer Estelle; Arfa Samir; Meunier Christophe; A Rolland Eric; Dequier Jerome; Ponnet Franck; Rodriques Patrick; J Kieser Andrew
Original assignee: Caterpillar Inc
Current assignee: Caterpillar Inc
Priority date: 2015-11-02
Filing date: 2015-11-02
Publication date: 2017-05-03
Also published as: GB201519343D0

Abstract

A method for end of line (EOL) testing of a vehicle (for example a track type tractor or loader or digging machine, etc) with a work implement (job, arm, a harvesters, a shovel, hammer, etc) is disclosed. The method comprises the steps of: connecting 100 the vehicle to a control system for command of vehicle operations and acquisition of operational data; initiating 102 a vehicle operation by the control system; acquiring operational data 106 relating to the vehicle operation; and terminating the vehicle operation 108. Another method also includes initiating a plurality of vehicle operations and wherein one of the operations comprises implement operations, such as moving the implement. The method can further include the steps of initial machine state checks 104 and intermittent machine state checks. It may also include the step of verifying synchronicity between the vehicle and control system. The disclosed method allows testing of a completed vehicle to not require an operator being present.

Description

METHOD FOR END OF LINE TESTING OF A VEHICLE WITH A WORK

IMPLEMENT

Technical Field

This disclosure relates to the field of testing vehicles on a test bench, in particular to end of line testing of a newly assembled vehicle. More particularly, the disclosure relates to end of line testing of newly assembled work vehicles.

Background

Vehicles (e.g. track type tractor or loader) may be tested and verified for operation upon completion of assembly. Testing a manufactured vehicle at the end of the assembly line may be an important aspect of the production process. Such testing may serve to identify defective vehicles prior to shipment to a customer. End-of-line testing may serve to analyse not only the quality of the product, but also the stability and yield of the production process.

Generally, a human operator is required to run through the operations of the vehicle during testing. The operator may be required to sit in the vehicle cabin and manually carry out different operation testing whilst monitoring the results of such testing. The operator may be required to run through each test sequentially until the testing is complete to the operator’s satisfaction.

Each vehicle may require a separate operator to physically perform the testing. Further, the operator may need to monitor the machine and wait for each test to complete before starting the next test. This is time consuming and requires multiple operators for multiple machines. The testing environment may be noisy, dirty and involve significant machine movement and so a high operator awareness may be required when being present in such an environment. US6076030 discloses a motion planning algorithm to control an autonomous machine. The motion planning algorithm consists of a script which captures the general trends of the motion and parameters in the script are filled in with the kinematic details for a specific machine and set of movements. The new parameters are evaluated by the learning algorithm using a predictive function approximator to test various performance criteria such as the time required to perform a task and the accuracy with which the task was performed. The performance criteria are weighted using local regression techniques so that the prediction of the outcome of alternate motions places emphasis on the performance criteria that is considered most important. As data from repeated motions accumulates, the algorithm uses the history of the results of various motions to re-compute and refine the parameters to improve performance.

Brief Summary of the Invention

In a first aspect, the present disclosure describes a method for end of line testing of a vehicle with a work implement is disclosed. The method may comprise the steps of: connecting the vehicle to a control system for command of vehicle operations and acquisition of operational data; initiating a vehicle operation by the control system; acquiring operational data relating to the vehicle operation; and terminating the vehicle operation.

In a second aspect, the present disclosure describes a method for end of line testing of a vehicle with a work implement. The method comprise the steps of: connecting the vehicle to a control system for command of vehicle operations and acquisition of operational data; initiating a plurality of vehicle operations by the control system; acquiring operational data relating to the vehicle operations; and terminating the vehicle operations, wherein at least one of the vehicle operations comprises measurements involving the work implement.

Brief Description of the Drawings

The foregoing and other features and advantages of the present disclosure will be more fully understood from the following description of various embodiments, when read together with the accompanying drawings, in which:

Fig. 1 is a block diagram exemplifying a method and an apparatus for end of line testing of a vehicle with an implement according to the present disclosure;

Fig. 2 is general flow chart exemplifying the method for the end of line testing of a vehicle with an implement according to the present disclosure;

Fig. 3A is a first part of a sequential functional chart (SFC) exemplifying details of the method for end of line testing of a vehicle with an implement according to the present disclosure; and

Fig. 3B is a second part of a sequential functional chart (SFC) exemplifying details of the method for end of line testing of a vehicle with an implement according to the present disclosure.

Detailed Description

This disclosure generally relates to a method for testing of vehicles at the end of an assembly line. The vehicle may be equipped with a work implement. The work implement may be for example a jib, an arm a rope shove or a dragline. The jib or arm may be fitted with a harvester, a loader, a shovel, a bucket, a multiprocessor, a rake, a pulveriser, a shear, a ripper, a backhoe, a blade, a cold planner, a hammer or a grapple.

With reference to Fig. 1, the block diagram illustrates an exemplifying architecture 10 of the method. The architecture 10 may have a control system 12 that interfaces with a vehicle (not shown). Control system 12 may be provided as a part of test bench equipment at the end of the assembly line.

The control system 12 may be connected to an I/O (Input/Output) system 14. The I/O system 14 may be provided as part of the control system 12. The I/O system 14 may electronically control the operations of the vehicle. The I/O system 14 may be provided with a datalink 50. The datalink 50 may enable communication/exchange of data with the vehicle and/or sensors connected to the machine. The datalink 50 may be configured through a configuration editor interface 34.

The control system 12 may communicate with an on board system 15. The on board system 15 may be predisposed in the vehicle for required operation control thereof. The vehicle may be equipped with an electronic command. The vehicle may be commanded electronically through the electronic command.

The control system 12 may communicate with the on board system 15 through the I/O system 14. In an embodiment, the I/O system 14 may communicate with the on board system 15 through a communication adapter 36. The communication adapter 36 may connected to the datalink 50. In a further embodiment, the I/O system 14 may send commands to the on board system 15 through the communication adapter 36. In yet a further embodiment, the I/O system 14 may acquire test data from the on board system 15 through the communication adapter 36.

In an embodiment, the I/O system 14 may communicate with the on board system 15 through a data acquisition unit 48. The data acquisition unit 48 may connected to the datalink 50. In a further embodiment, the I/O system 14 may acquire test data from the on board system 15 through the data acquisition unit 48. The data acquisition unit 48 may acquire measurements from the sensors on the vehicle.

The I/O system 14 may have an analog input acquisition port 38. The analog input acquisition port 38 may be connected to sensors 17 in the vehicle through physical connections 19. The I/O system 14 may be connected to pressure sensors and speed sensors through the analog input acquisition port 38. The I/O system 14 may be connected to the sensors through capillaries which are formed as small hoses that are connected to vehicle and enable collection of data from sensors connected at their endpoint

The vehicle may be connected to the control system 12 through respective I/O (input and output) terminals provided on the vehicle and the control system 12. The sensors and bus connection of the vehicle may be connected to the respective I/O terminal of the control system 12. The control system 12 may be programmed to command operations of the vehicle and to acquire data regarding the operations from the vehicle though an I/O link 16. The I/O link 16 may be linked to a microprocessor 18. I/O terminals on the vehicle and the control system 12 may enable dialog between the respective computers in the vehicle and the control system 12. The I/O link 16 may enable dialog between the respective computers in the vehicle and the control system 12 through the I/O system 14.

The microprocessor 18 may be configured to run a programme suitable for testing the vehicle based on a test script 20. The I/O link 16 may be linked to a microprocessor 18 through the test script 20. The vehicle may be commanded to perform operations without input from an operator by the test programme 22. The vehicle may be commanded to perform operations as required by the test programme 22.

The required test programme 22 may be loaded onto the microprocessor 18. The selection of the test programme 22 may be determined by the vehicle to be tested. The control system 12 may be provided with the required test programme 22 from a programme database 24. The programme database 24 may provide commands that are included in the test programme 22. The programme database 24 may be provided as a database group 40 that may be required for the testing of the vehicle. The commands may be adapted for different vehicles. The test programme 22 may be generic for a class of vehicles. Initiation, progression and termination of the test may be controlled by the test programme 22.

The test may comprise at least a single vehicle operation. The vehicle operation may be selected from the group consisting of implement activity, command activity, switch control, transmission activity, engine activity, fan regulation and machine options (blade, ripper, reversible fan, lift arm, winch). Implement activity may comprise movement of the implement. The movement of the implement may be along forward and rearward directions and/ or upwards and downwards directions, and/or other types of movement in accordance with typical movements of the relevant implement. In an embodiment, the test may comprise a plurality of vehicle operations. The plurality of vehicle operations may be run sequentially.

With respect to the implement, the test programme 22 may require testing of the vehicle engine speed in conjunction with the lift cylinder position. In addition, the pressure may be measured in the implement line. The transmission speed and pressure in the forward and rearward position of the implement may also be measured. Initiation, progression and termination of the vehicle operations may be controlled by the test programme 22.

The control system 12 may perform checks on the state of the vehicle (machine state check). In an embodiment, test programme 22 may perform the machine state checks. Machine state checks may be performed to assess the state of the vehicle in order to obtain accurate data in relation to the vehicle operations that are tested. A machine state check may be performed at the initiation of a test. The initial machine state check may provide an overall assessment of the vehicle. The initial machine state check may provide a base level assessment for the test to be performed.

Ongoing machine state checks may be performed during the test. Intermittent machine state checks may be performed during the test between the vehicle operations. Intermittent machine state checks may provide an assessment of the vehicle state prior to a vehicle operation being initiated. The intermittent machine state checks may provide a base level assessment for the testing of the specific vehicle operation.

The machine state check may comprise an assessment of a single parameter. In an alternative embodiment, the machine state check may comprise an assessment of a plurality of parameters. The machine state check may comprise one or more of the machine states selected from the group consisting of engine speed, implement lockout position and park brake position. In an embodiment, the machine state check may further comprise as neutral position of the implement, machine and engine temperatures.

Control system 12 may further comprise a command or a user interface. The microprocessor 18 may be connected to the command or a user interface (not shown). The user may modify the test programme 22 to adapt to specific requirements or conditions, with command or user interface. The command or user interface may be based on available systems such as typed commands, graphical icons or visual indicators. The command or user interface may be connected to the microprocessor 18 through wired or wireless connections.

Data generated by the vehicle operations commanded by the test programme 22 may be acquired by the control system 12. Acquisition of the generated data may be under the control of the test programme 22. Data generated may be acquired by the control system 12 through the I/O link 16. The acquired data 30 may be stored in a result bench database 32. The stored data may be analysed as to whether the values related to the operations performed during the test fall within required parameters the stored data may be analysed through the results server consultation.

The control system 12 may be provided with a control protocol to command the vehicle operations that are required for the testing of the vehicle. The acquisition of the data resulting from the vehicle operations may be obtained through the control protocol as provided in Figs. 2, 3A and 3B.

With reference to Fig. 1, the on board system 15 may be provided with an on-board microprocessor (not shown). The command of the vehicle operations and acquisition of data related to the operations performed through the on board microprocessor. In an embodiment, the on board system 15 may be subordinate/ slave to the control system 12 which serves as a master. The command of a vehicle operation and the acquisition of data through the on board system may be performed upon command from the control system 12.

On board system 15 may interface with the control system 12 through the control protocol in the control system. The command of the vehicle operations and acquisition of data related to the operations performed through the plurality of component protocols for each of the vehicle component. The control protocol may interact and communicate with the plurality of component protocols for each of the vehicle component in a predetermined form of dialogue.

The control system 12 may be provided with modules of general configuration. In an embodiment, the control system 12 may be provided with an operator editor interface 42. In a further embodiment, the control system 12 may be provided with a Programmable logic controller (‘PLC’) editor interface 46. The operator editor interface 42 and PLC editor interface 46 may be connected to the I/O link 16.

In an embodiment, the control system 12 may be connected to a plurality of vehicles. A single operator may initiate the testing process of several vehicles in the test zone, such as a testing tunnel. A remote control system may be used to supervise the running of the machine tests.

The method for end of line testing of the vehicle with a work implement may comprise the steps of: connecting the vehicle to a control system 12 for command of vehicle operations and acquisition of operational data; initiating a vehicle operation cycle by the control system; acquiring operational data relating to the vehicle operation; and terminating the vehicle operation cycle.

The control system 12 may initiate the procedure for testing of the vehicle based on a determination of a connection. The control system 12 may initiate a vehicle operation cycle based on a positive determination of command of the vehicle operations and data acquisition. The control system 12 may initiate acquisition of operational data based on a determination of the vehicle operation. The control system 12 may terminate the vehicle operation based on a determination that test steps required for the vehicle operation cycle is concluded.

In an embodiment, the method for end of line testing of a vehicle with a work implement may comprise the steps of connecting the vehicle to a control system for command of vehicle operations and acquisition of operational data; initiating a plurality of vehicle operation cycles by the control system; acquiring operational data relating to the vehicle operations; and terminating the vehicle operation cycles, wherein at least one of the vehicle operations comprises implement activity.

The control system 12 may initiate the procedure for testing of the vehicle based on a determination of a connection. The control system 12 may initiate a plurality of vehicle operation cycles based on a positive determination of command of the vehicle operations and data acquisition. The control system 12 may acquire operational data based on determination of each vehicle operation of a vehicle operation cycle. The control system 12 may terminate each vehicle operation cycles based on a determination that test steps required for each vehicle operation cycle is concluded.

The method may be directed to an automated testing system in a production environment. The method may involve the testing of a plurality of vehicle through the control system 12. The control system 12 may enable simultaneous testing of a plurality of vehicles. A newly assembled vehicle may arrive at the end of the assembly or production line. The control system 12 may be set up at a test bench at the test zone located either at the end of the assembly line or adjacent thereto.

With reference to Fig. 2, the vehicle with the implement may be electronically connected to the control system 12 at the test zone at step 100. Electronically connecting the vehicle to the control system 12 may comprise connecting the respective I/O terminals of the vehicle to the control system 12. In an embodiment, electronically connecting the vehicle to the control system 12 may comprise wirelessly connecting the control system 12 to the on board system 15.

The electronic connection may enable the control system 12 to command vehicle operations. The electronic connection may enable the control system 12 to acquire data from the vehicle. The vehicle operations may be controlled through on board system 15.

In a further embodiment, the vehicle may be physically connected to the control system 12 at the test zone at step 100. The vehicle may be physically connected through capillary tubes thereon. If the vehicle and the control system 12 are connected the control system may initiate the test procedure for the vehicle operation at step 102.

At step 104, based on the determination of connection of the vehicle to the control system 12, the control system 12 may initiate a vehicle operation cycle for a specific vehicle operation. A vehicle operation cycle may comprise all the steps and/ or conditions that the vehicle operation is required to undergo as required by the test programme 22.

The specific vehicle operation that is selected may be a required element for the test for the specific vehicle undergoing the test. The vehicle operation may be subject to testing over a required period and under required conditions at the command of the control system 12 during the vehicle operation cycle. The required period and/ or the required conditions may vary for each vehicle operation.

In an embodiment, the method may further comprise performing an initial machine state check at initiation of the test in step 102. The control system 12 may perform the initial machine state check based on the determination of connection between the vehicle and the control system 12. Step 102 may be performed prior to initiation of the vehicle operation at step 104. In an embodiment, an initial machine state check may be performed prior to initiation of the first vehicle operation at step 104 when a plurality of vehicle operations are required.

Operational data may be generated as the vehicle is commanded to perform the required steps involving the selected vehicle operation. Based on a determination of data being generated during the vehicle operation, the control system 12 may proceed with the acquisition of the datarat step 106. Data acquisition may be carried out during the progression of the vehicle operation cycle.

At step 108 the control system 12 may terminate the vehicle operation cycle based on a determination that the required steps for testing of the vehicle operation is concluded. In an embodiment, data acquisition step 106 may be carried out at the termination of the vehicle operation cycle.

In an embodiment, the method may further comprise the step of verifying synchronicity between the vehicle and the control system 12. The control system 12 may check for a periodic heartbeat signal. The periodic signal may be sent between the vehicle and the control system 12. In particular, the control system 12 may send a signal to the on board system 15 to which a return signal is sent in response from the on board system 15 to the control system 12. The test procedure may be paused if a return signal is not received by the control system 12.

In an embodiment, the on board system 15 may send a signal to the control system 12 to which a return signal is sent in response from the control system 12 to the on board system 15. The test procedure may be paused if a return signal is not received by the on board system 15.

The periodic signal may be extraneous to the test of vehicle operation. The periodic signal may be used in the assessment of safety when using the automated testing system.

The method may further comprise performing the steps of initiating a vehicle operation, acquiring operational data relating to each vehicle operation and terminating the vehicle operation for a plurality of vehicle operations cycle. From step 108 the method may return to step 104 for initiating the next vehicle operation cycle.

Each vehicle operation cycle may comprise initiation of the vehicle operation, progression of the vehicle operation and termination of the vehicle operation. Step 104, step 106 and step 108 may be repeated for each vehicle operation. The sequence of the vehicle operations to be tested may be selected by the test programme 22. The sequence of the vehicle operation cycles may be selected by the test programme 22.

In an embodiment, the method may comprise the step of performing intermittent machine state checks during the test (e.g. a plurality of regular, irregular and/or event-triggered checks). Intermittent machine state checks may be performed between each vehicle operation cycle at step 114. In an embodiment, the intermittent test machine state checks may be performed during the vehicle operation.

At the end of the final vehicle operation cycle the test may be terminated at step 110. The vehicle may be disconnected from the control system 12 at step 110.

The method may further comprise the step 112 of analysing the acquired data. The analysis of the acquired data may be performed after the termination of the test. In an embodiment, the analysis of the acquired data may be performed at the termination of the vehicle operation cycle at step 108. In yet a further embodiment, the analysis of the acquired data may be performed at during the progression of the vehicle operation cycle.

With reference to Figs. 3A and 3B a sequential functional chart (SFC) exemplifying details of the method is described. The vehicle with an implement may be connected to the control system 12 at step 100.

The test programme 22 for the vehicle to be tested may be selected through the control system 12 at step 120. The relevant test programme 22 may be selected at 122. If the required test programme 22 is available and selected, the specific I/O configuration for the vehicle may then be loaded into the control system 12 at step 124. If the specific I/O configuration is loaded into the control system 12 then, at step 126 the protocol for dialogue between the specific vehicle and the control system 12 may be initialised. If the protocol for dialogue is initialised then, at step 128 the logical I/O mapping between the specific vehicle and the control system 12 may be performed.

At step 130 the control system 12 may seek authorisation for command control of the test procedure. If authorisation is not provided to the control system 12, the test and calibration may be performed in manual mode at step 132. In manual mode, the automated test procedure is stopped and the required steps for the test procedure are then performed by an operator.

If authorisation is provided to the control system 12 then a step 102 of performing an initial machine state check may be performed. The conditions checked may be the engine speed, parking brake lock out condition and the implement lock out condition.

At step 102a, the machine condition is assessed. If the machine condition is negative then remedial actions are performed to bring the conditions to the required criteria at step 102b. If a positive assessment of the machine condition is determined by the control system 12, then the method may proceed to step 104 to initiate a vehicle operation cycle. Testing of the selected vehicle operation may initiate at step 104a.

In an embodiment, the vehicle operation cycle may be require calibration of the respective vehicle operation to be tested at step 104b. The calibration procedure may be performed prior to the procedure for testing of the selected vehicle operation at step 104a. In an embodiment, the calibration procedure may be performed simultaneously with the procedure testing of the selected vehicle operation at step 104a.

The calibration procedure may be required for the type of vehicle selected. The calibration procedure may be performed at least once for each vehicle. For each vehicle, depending on vehicle configuration, several calibrations may be required.

The calibration procedure may initiate with an initial calibration step at step 120. The initial calibration step may involve selection of the calibration criteria required for the selected vehicle. If the calibration step is completed then the control system 12 may command the vehicle to set the initial conditions for the calibration at step 122. If the initial conditions are set in the vehicle the control system 12 may command the start of the calibration at step 124. Upon completion of the calibration the control system 12 may acquire the results of the calibration at step 126. If the results are acquired then the control system 12 may store the results in the calibration results database at step 128. The control system 12 may then end the calibration procedure at step 130 if the results are stored in the datarabase.

Data may be acquired from the calibration procedure. At the end of a calibration procedure, the method may return to the next calibration procedure at step 104b. The programme database 24, depending on the type of vehicle and configuration, may list all calibration procedures to perform.

If the required calibration procedure is completed, the control system 12 may then proceed with the procedure for testing of the selected vehicle operation at step 104a. The required calibration may be the calibration required for the testing of the selected vehicle operation. In an embodiment, the control system 12 may perform an intermittent machine state check at step 114. The engine speed, engine temperature and fan speed may be checked during the intermittent machine state check.

At step 114a, the machine condition is assessed. If the machine condition is negative then remedial actions are performed to bring the conditions to the required criteria at step 114b. If a positive machine condition is assessed by the control system 12, then the method may proceed to the next step 116.

At step 116, the control system 12 may send the command to initiate the testing of the vehicle operation. The required vehicle operation may proceed trough a series of required procedures if the command to initiate testing is received by the on board system 15.

Data generated during the vehicle operation cycle may be acquired by the control system at step 106. The data acquisition may be carried out during the progression of the vehicle operation. The acquired data may be stored in the results database 32 at step 118. Data acquired from the calibration may also be stored in the results database 32 at step 118. The method may further comprise the step 112 of analysing the acquired data.

At step 108 the control system 12 may terminate the vehicle operation cycle if the testing procedure is completed. In an embodiment, analysis 112 and/ or storing 118 of the acquired data may be performed at the termination of the vehicle operation at step 108.

The method may proceed to a further vehicle operation cycle at step 104a if a plurality of vehicle operations are required by the test programme 22. Upon completion of the test the vehicle is disconnected at step 110.

The skilled person would appreciate that foregoing embodiments may be modified or combined to obtain the method of end of line testing for a vehicle of the present disclosure. Industrial Applicability

This disclosure describes a method for end of line testing of a vehicle. The method may enable testing of the vehicle for operations that are required on-site. The method may enable each operation to be performed and the data related to the operations to be acquired for storage in a database.

The method may assess the state of vehicle operational readiness. The method may assess if the acquired data is within predefined parameters. The data acquired may be operational values of a part of a system in the vehicle required for on-site work. The data operational values may be measured at various conditions, e.g. at different load conditions such as at low load, medium load and high load. The operational values for the different load conditions may be acquired and stored in database at the test bench.

The method may enable productive and efficient testing of the vehicle in safe environment and with higher accuracy than a testing method that is dependent on an operator. All required operations may be performed under the control of the control system. These vehicle operations may be performed without operator input. The vehicle may therefore be tested without the need for continuous human operator input - a human operator does not need to wait for a test mode to complete in order to initiate the next test mode.

Accordingly, this disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein.

Where technical features mentioned in any claim are followed by reference signs, the reference signs have been included for the sole purpose of increasing the intelligibility of the claims and accordingly, neither the reference signs nor their absence have any limiting effect on the technical features as described above or on the scope of any claim elements.

One skilled in the art will realise the disclosure may be embodied in other specific forms without departing from the disclosure or essential characteristics thereof. The foregoing embodiments are therefore to be considered in all respects illustrative rather than limiting of the disclosure described herein. Scope of the invention is thus indicated by the appended claims, rather than the foregoing description, and all changes that come within the meaning and range of equivalence of the claims are therefore intended to be embraced therein.

Claims

1. A method for end of line testing of a vehicle with a work implement, the method comprising the steps of: connecting the vehicle to a control system (12) for command of vehicle operations and acquisition of operational data; initiating a vehicle operation cycle by the control system (12); acquiring operational data relating to the vehicle operation by the control system (12); and terminating the vehicle operation cycle by the control system (12).

2. The method of claim 1 further comprising the step of performing an initial machine state check at initiation the test.

3. The method of claim 1 or 2 further comprising the step of performing intermittent machine state check during the test.

4. The method of claims 2 or 3 wherein the machine state check comprises one or more of the machine states selected from the group consisting of engine speed, implement lockout position and park brake position.

5. The method of any one of preceding cl aims wherein connecting the vehicle to the control system comprises connecting sensors and BUS of the vehicle to respective I/O of the control system (12).

6. The method of any one of preceding claims wherein the command of vehicle operations and acquisition of operational data is performed by a control protocol in the control system communicating with a plurality of component protocols for each of the vehicle component.

7. The method of any one of preceding claims further comprising the step of verifying synchronicity between the vehicle and the control system (12).

8. The method of any one of preceding claims further comprising performing the steps of initiating a vehicle operation, acquiring operational data relating to each vehicle operation and terminating the vehicle operation for a plurality of vehicle operations.

9. The method of claim 8 wherein the plurality of vehicle operations is performed in a sequence controlled by the control system (12).

10. The method of any one of preceding claims wherein the vehicle operation is selected from the group consisting of implement activity, command activity, switch control, transmission activity, engine activity, machine activity.

11. The method of any one of preceding claims further comprising the step of analysing the acquired data.

12. A method for end of line testing of a vehicle with a work implement, the method comprising the steps of: connecting the vehicle to a control system (12) for command of vehicle operations and acquisition of operational data; initiating a plurality of vehicle operation cycles by the control system (12); acquiring operational data relating to the vehicle operations by the control system (12); and terminating the vehicle operation cycles by the control system (12), wherein at least one of the vehicle operations comprises implement activity.

13. The method of claim 12 wherein the implement activity comprises movement of the work implement.