Any idea?

 

Its software issue, cna be fixed with edit.

The computer does sanity checks of TPS vs predicted airflow/load (my guess is MAP, but may be MAF)

Big cam cars have values closer to atmospheric and throws the code sometimes, and id assume 422 blower cars that consume a lot of air and would make man pressure earlier would too

 

Not tryin' to pull teeth or anything, here , but, do you know what needs to be adjusted in LS1Edit, or where I may get a sample table that may help me overcome this?

Thanks!

 

Since i have the old *** version of edit to use, on cars ive had to toggle the sytem perf codes off on the offending codes, not the hi/los. on new edit there is a window table for the 121 code a few say to just raise values 10 each.

now were trying tochase dowwn a car that just doesnt want to shift 2-3.. period lol. Needs like 600 rpm lead time

 

Someone asked about this on another forum, and I thought I'd check if anyone has solved a problem like this yet. {hopeful}

 

Thanks Black LS1

My problem is at WOT, I do not have the power necesary to feather... I would assume he would get the same if it would hook up.
Here is what I am seing now :

I have been having an intermittent problem at WOT at the track lately. The car will fall right on its face 'sometimes' at WOT.

http://j.cz28.com/wotupshift.jpg

Graph here. If you look at it, it seems the cpu is commanding the shift for some reason..... The previous 6 runs that day had no problems. I did change the tune before the 3rd run, otherwise it stayed the same for 4th to the 7th run. Log shows rpm, tps and mph (which is the parameters the cpu looks for i believe) Running in SD mode if that makes any difference. Trans is converted to vacuum mod. Of course this problem occured in the Final round.

Is there more than 1 place the computer 'sees' vehicle speed ? The only thing I can think of is another intermittent problem : In the burnout box 'sometimes' the mph gauge will be lazy for 1-1.5 sec then jump up real fast.... It is not tied to the upshift problem 100%, (IE when this problem occurs, it does not indicate the other problem will on that particular run) but thought something might be connected there ?

I have the .tun file if anybody wants to take a look. Seems like there is some parameter that is causing this.... BTW: I am not getting the TPS code.

Thanks for any input here.
'J

 

I believe I get the short-shift whether I feather or not, as well. There is just so much torque, I can hardly tell it short-shifted without looking back at the logs. Perhaps I should let torque reduction kick in just to see what happens.