Results 1 to 15 of 15

Thread: LT1 : Random Trq management pulling 12deg of timing : TCS ?

  1. #1

    LT1 : Random Trq management pulling 12deg of timing : TCS ?

    Hello guys,

    I finalized my tuning (CAI/MSD Intake manifold/ARH Headers/Ported TB) in January. Pulled 460WHP/430WTQ on a Mustang dyno.

    Today, just doing a random pull with datalogging to check everything was fine before doing a Roadcourse event, I caught something I noticed a 2-3 times in the past...

    TRQ MGNT.jpg

    Torque Mgt Advance pulling10-12deg of timing from 5100 to 5600 rpm, then from 5800 to 6000, then from 6100 to redline... With advance back to normal values in between...

    First time I catch it with datalogging as it doesn't happen often... Of course you feel it, 10-12deg of timing is huge, so I know it doesn't happen often...

    Here is my tune

    Last tune 01052019 .hpt

    Here is the full log

    011020192.hpl

    My question to you guys is : exceptionally I was driving in Tour with everything on, as opposed to usual Sport/Race with everything off... Could this be TCS messing around (Strange at this speed in 3rd gear...) ? Or is this real Torque management, and if yes why ? I can't see anything wrong in the torque management values I'm datalogging but I'm very inexperienced...

    Thanks for your help !

    PS : Car is a 2017 Corvette C7 GrandSport, manual 7 speed transmission, with Z07 setup and I'm at around 3000Ft elevation where I live
    Last edited by Sachs; 10-01-2019 at 09:36 PM.

  2. #2
    Lots of areas in the torque management section need work....

    Watch logs and play in that area till you fix it

  3. #3
    There is nothing useful to modify in my opinion in the torque management section for a manual NA LT1 ....I increased sightly the values in the virtual torque menu (Edit) by something like 5% for the different sparks if I recall. In my logs I don't see gaps between actual torque and predicted torque etc...Nothing that could explain that.

    I did 40 logs since I tuned the car, and this is the first time I see that...

  4. #4
    Senior Tuner
    Join Date
    May 2003
    Location
    South FL
    Posts
    1,359
    Traction control kicking in will also trigger Torque Management Advance. Are you sure you're not just spinning? I don't really see anything out of line with torque limiters and throttle isn't closing.
    [email protected]
    Owner/GM Calibrator
    Gen V Specialist - C7 Corvette, Gen6 Camaro & CTS-V3

  5. #5
    Quote Originally Posted by TriPinTaZ View Post
    Traction control kicking in will also trigger Torque Management Advance. Are you sure you're not just spinning? I don't really see anything out of line with torque limiters and throttle isn't closing.
    This is what I think...Normally I do all my pulls with TCS off, but this time I forgot...

  6. #6
    Advanced Tuner
    Join Date
    Aug 2014
    Location
    Central, LA
    Posts
    737
    I doubt it was spinning, but that doesn't mean tcs isn't doing it. I would possibly try to get a little separation between your max and engine torque, but just do the pulls with tcs off and see if it ever happens.

  7. #7
    Quote Originally Posted by sevinn View Post
    I doubt it was spinning, but that doesn't mean tcs isn't doing it. I would possibly try to get a little separation between your max and engine torque, but just do the pulls with tcs off and see if it ever happens.
    This. Which is under the torque management section.

    But what do I know

  8. #8
    Senior Tuner
    Join Date
    May 2003
    Location
    South FL
    Posts
    1,359
    You should increase your Peak Torque Table about 15%. Your PE table logic is a bit odd, you should have your PE table set to target the actual AFR/Lambda you want and then use the MAF/VVE to reach that target. Set your Virtual Torque back to stock values.
    [email protected]
    Owner/GM Calibrator
    Gen V Specialist - C7 Corvette, Gen6 Camaro & CTS-V3

  9. #9
    Quote Originally Posted by TriPinTaZ View Post
    You should increase your Peak Torque Table about 15%. Your PE table logic is a bit odd, you should have your PE table set to target the actual AFR/Lambda you want and then use the MAF/VVE to reach that target. Set your Virtual Torque back to stock values.
    Ok I'll take a look at that

  10. #10
    Senior Tuner SultanHassanMasTuning's Avatar
    Join Date
    Nov 2009
    Location
    All Around
    Posts
    3,149
    Last tune 01052019 VTT.hpt

    there was adjustments needs to your virtual torque to help eliminate your issue
    Follow @MASTUNING visit www.mastuned.com
    Remote Tuning [email protected]
    Contact/Whatsapp +966555366161

  11. #11
    Tuner in Training
    Join Date
    Aug 2019
    Posts
    22
    Did you solve the problem? My Camaros doing basically the same thing.

  12. #12
    Tuner in Training
    Join Date
    Aug 2019
    Posts
    22
    Got mine to stop pulling timing by raising the vtts 5% and driver demand 5% above 95% throttle

  13. #13
    It helps to log engine torque in a histogram matching the vt table and dd table. If one is exceeded you should raise those areas. I'm new at this but that's my opinion. It's not as specific in adjustment as the vve table but more of a general guidance

  14. #14
    Quote Originally Posted by SultanHassanMasTuning View Post
    Last tune 01052019 VTT.hpt

    there was adjustments needs to your virtual torque to help eliminate your issue
    Thanks I'll take a look. Sorry I forgot to come back there since I did not drive the car a lot since october because of the weather.

  15. #15
    Quote Originally Posted by SultanHassanMasTuning View Post
    Last tune 01052019 VTT.hpt

    there was adjustments needs to your virtual torque to help eliminate your issue
    So I tried your modifications on the torque management. It does not work at all. My throttle closes above 5300 rpm. TPS goes from 91.8% (normal value when full throttle) to 64% with yours.

    log.jpg


    I tried my own program with TCS off today no loss of timing and my throttle position stays at 91.8% all the way. Probably was TCS issue