Why are my STIT's staying at zero?
08-20-2010, 01:48 PM
#1
Why are my STIT's staying at zero? HPT Support says it's either mechanical or in the tune. Frost is helping me with the tune and it's the first time he's seen this.
I'm going to try scanning with the 2.22 release instead of the beta in case it's a scanner bug. If it's not that, how do I resolve this?
I'm going to try scanning with the 2.22 release instead of the beta in case it's a scanner bug. If it's not that, how do I resolve this?
08-20-2010, 04:15 PM
#5
Moderator
iTrader: (11)
Join Date: Mar 2002
Location: East Central Florida
Posts: 12,605
Likes: 0
Received 6 Likes
on
6 Posts
There are some enable fields for adaptive idle RPM, like
off temperature. And if your TPS reads out of idle range
then it won't even try to trim. Any of this sound likely?
If IAC counts are moving around and RPM is being held,
I'd be thinking a PID screwup of some sort (what it thinks
is your STIT PID, returns zeroes). There seem to be some
occasional issues of that sort, though you'd think a '98
F-body ought to be a pretty known quantity. Then again
there's that (how many?) multiple-OSes deal....
off temperature. And if your TPS reads out of idle range
then it won't even try to trim. Any of this sound likely?
If IAC counts are moving around and RPM is being held,
I'd be thinking a PID screwup of some sort (what it thinks
is your STIT PID, returns zeroes). There seem to be some
occasional issues of that sort, though you'd think a '98
F-body ought to be a pretty known quantity. Then again
there's that (how many?) multiple-OSes deal....
08-20-2010, 07:05 PM
#7
I'll try that this weekend. My opinion is the software should notify the user if you're trying to log more than the supported number of bytes when you connect to the vehicle. I'm also curious how the software determines which bytes to ignore?
