Last night I went to the track, and did as I usually do.. I hit the TC button 1 time, TC OFF then I use my line lock and do my burn out..

After my burnout (it went sideways just a "little" I got message "Active Handling Recalibrating" then for the rest of the night, the little yellow light on the dash showing TC would remain ON no matter what I did...

I got a message something about "Active Handling... I tried everything from 1 click or 2 clicks, then I held the button down for 5-10 sec.. but was unable to clear the message... when I finished racing, I left for home and about 2-3 miles later the light went off, & all seems normal..

I do not have a high HP car, and can run it with or without Active Handling, I have been just shutting off TC...

In the future would I be better off to hold the TC button for 10 sec to have EVERYTHING OFF TC & AH OFF..

The car hooks up and after it was tuned, it got very consistant... made 5 runs last night 12.14 - 12.17 all night... 60' times were ALL 1.855 - 1.861

I just want to avoid the warning light & don't know why it came on... Also I'm not using any air pressure sensors in my rear tires, and usually get a message NO Signal Rear Left, Rear Right Tire.. which is no prob, because when I put my regular tires back on its fine...

I don't think the tire pressure sensor has anything to do with the AH warning... Would I be better off just holding the button down for the full 10 sec to have EVERYTHING OFF during the run ?

thanks...

 

What tires are you running; are they stock sized? Often times Corvette owners install tires with a different aspect ratio and this causes all sorts of issues with Active Handling and Traction Control...

 

did you hit the reset button, plus they have a tsb problem with the steering sensor wire the way its hooked

 

No I never tried the "Reset" button... it did reset itself after 2 miles..

The tires I'm running are the exact same height as the originals 26.5"
so I don't think that is affecting it, and I've had these tires on for a few races w/ no problems..

I think next race I'm going to try to hold the traction button for 10 sec so it reads ALL OFF before I do any burnout...then the active handling won't be trying to correct it IF it does go a little sideways on the burnout..

 

John when you did the first burn out..... you most likely did not hit the button long enough. I did the same thing last year.

I pressed the button but apparently did not hold it long enough too. If you kept your time slips you should notice a quicker 60 foot resulted in a slower ET when you compare it to the next run. The message eventually went away.....

Good to hear the car is running consistent

 

This happened on Oct 31 (Fri Night) I'll just post my 60' and final ET.. The problem occurred after the 2nd run... the first 4 runs I drove, and Jeanne drove on the 5th

1. 1.866 ET 12.143

2. 1.870 ET 12.172

3. 1.885 ET 12.30 elimination on the breaks 1000' said it = 12.168

4. 1.862 ET 12.157

5. 1.868 ET 12.158 Jeanne Driving (Hot Lapped)

So I don't think the Active Handling light had any affect on my ET's But I WILL and I'll also make sure Jeanne is sure to HOLD the button down until the DIC says TC and Active Handling OFF !

 

Yup it looks like it may have been something else, not the button

However, you can see that torque management is doing its thing on launch Notice:

1.862 = 12.157 quicker 60 slower ET (TQ did its thing)
1.866 = 12.143

The spread is .014 if you can live with that then you should be fine as no tuner has been able to tune out TQ on the launch Good luck

 

I think the difference may be due to two things...

#1 She is 80 lb lighter than me..

#2 When she made her run the car was hot, she ran immediately after my run NO cool down time at all!

 

John,

A lower sixty foot should always result in a quicker Elapsed time........ EXCEPT in the wonderful world of C6 torque management.

The weight is constant for the entire run and hot lapping usually results in a better time.

Please check out page 90 post 1786 of the 1/4 mile sticky. There are three runs by Frank "Evilways" Notice the 60 ft time in relation to the elapsed times. A quicker 60 foot resulted in a slower ET.

This is what Dennis and I were trying to explain to you about torque management on launch at the track rental. Unfortunately, it can not be tuned out upon launch.

As I already stated if you can live with a spread of .014 then you will be fine. That is why we have so many runs, you have to watch the launch to minimize TQ. You seen to be doing fine as the car is runing consistent and any C6 you come up against will have the same problem and more so if it does not have a tune.

 

I'm very HAPPY with the consistency it is showing now. .014 in 2 runs is as close as I expect to get, in over 20 runs since its been tunes, it has only had 1 run that wasn't "in the Ballpark' it was .07 off of what the TAG Weather station predicted.. like you say.. its probably the TM.. but its not doing it enough to screw me or Jeanne up completely.. I think we'll be able to deal with it..

We'll know for sure next Sat..

 

John, mine did the same thing, I used to keep the AH on just in case. However mine went off relatively quickly. It may be due to it not seeing tire pressures. I know that it reads off the ABS sensors but pressure also plays a small part I think. When my tire went flat I got reduced power and AH messages. These things are gremlins.

Congrats on the consistent times. Seems like you got it pretty much down. Are they close enough to win in your class?

 

Thanks, I hope its all worked out, and YES if the car can run that consistent on Sat. and Jeanne is "On Her Game" she will be tough to beat..

But you know what they say, we don't race on paper , the "TRACK" results will tell the final story

 

Dennis has the answer - the TSB on the steering sensor wire. Have this looked at as it is the most likely culprit of the message. If your car is a 3LT car, I am willing to bet this is the only reason for the service active handling message. I had my car fixed last month and, before the fix, I would get the message intermittently. Really annoying but an easy fix.

 

pull the code it should be a history

 

John,

Good luck on Saturday