 |
Walkinshaw Racing /font>
| Each team utilises different approaches to tuning the car. However, there is typically a common thread that it involves including a working relationship between the driver and his engineering staff, namely the race engineer and data engineer. A typical approach during a session would involve:
Driver completes a run of 2 – 3 laps before returning to the pit lane
Race engineer speaks with the driver, while the data engineer downloads the data and listens in to the driver /race engineer conversation.
Often a chat with the driver will occur regarding setup direction options, with the race engineer confirming the final decision.
Data engineer will quickly analyse the data for the previous change to ensure it was the right direction or help direct further changes to be made.
This data is transferred to a server computer so that the other engineering staff are able to use it for comparison with their driver and setup direction
Race engineer directs the changes to the mechanics, and another run is completed with the process repeating.
In a multi-car team, such as Walkinshaw Racing, this relationship extends to the wider car crews of driver and two engineers also working together and communicating the effect of changes made. If this is efficient, it enables a team to move two cars forward. Post session, the team will often conduct a debrief session for the engineering staff and drivers to openly discuss what worked and what didn’t.
Data analysis is an important tool used to understand what the car and driver is doing on track. Walkinshaw Racing uses Pi Toolbox for all data analysis and each engineering staff member is trained to use the software. Drivers may also have limited use for understanding their driving style.
|
Away from the race track, there is significant pre and post event analysis completed by the engineering staff. This involves such work as:
Strategy optimisation pre event, detailing all options available.
Tyre management for the event, ensuring tyre grip is maximised at all times.
Potential changes and setup directions
Post event analysis of strategies used and what are teams did that was good and bad
Post event analysis of changes made and work out what was good and what was bad and decide on development areas
Post event debrief with all engineers and drivers to review the event
During every event, whether it be a test or race meeting, the engineering personnel maintain extensive written and electronic records of the cars performance and changes made so that at any point in the future, this can be reviewed with as much accuracy as possible.
SOME INTERESTING FACTS
The Holden VE road car is longer than its predecessor, the VZ. When the VE was introduced the wheelbase was too long to meet the technical regulations of V8 Supercars. The solution was to shorten the car by 70mm. This means that the roof skin and rear doors required re-manufacturing.
The Holden and Ford Chassis is now quite similar, sharing common sheet metal components and rail design. Gone are the days of receiving a bare shell from the manufacturer and the teams welding in a roll cage. The cars are now produced from the ground up, with the roll cage being manufactured first and the panels then welded and pop-riveted on around it. This makes the manufacture process quicker and less expensive, and importantly reduces the time and cost to make repairs after an accident.
|
This web site is supplied strictly on the condition that Glenvale Publications and Auto Parts and Accessories Journal,
its employees, agents, authors, editors and consultants are not responsible for any deficiency, error,
omission or mistake contained in this web site, and Glenvale Publications and Auto Parts and Accessories Journal,
its employees, agents, authors, editors and consultants hereby expressly disclaim all liability of whatsoever nature
to any person who may rely on the contents of this web site in whole or in part. No portion of this web site, in whole
or in part, may be reproduced without the written permission of the publisher.
|
|