Crazy KR under light load.

[mowton]

Yea... I never understood the "use generic sensor instead". Well for now on it's always "DO AS I SAID". 3.2 is good, but also bad. They need to fix this.

It initially made sense because MAP, RPM IPW etc., no matter what platform/year would automatically be "linked" to the generic sensor so you didn't need to have multiple Charts and Graphs. In 2.24 as well as 3.X it really was for the WB and Commanded EQ/AFR to work with the internally calculated error so we didn't have to develop User Defined equations.

Now I will be a bit more careful in my answers like you said and go back to my library and see what else may be lurking in the unknown.....

Ed M

[Jggregory99]

Crap..... ME TOO!!!!! Dropped like 5* of spark for the KR Histo...... Well at least I didn't get to far in... I guess I'll just load stock and start over....!!!

[MADWHIP]

Dang. Back to school for me also. Client has picked up the HSV so I'll have to get back to you guys in the future.
Cheers

[jschemen]

crap. I just wasted a pile of time because I'm stupid... Thanks for this thread and that great catch by ss.

[GHuggins]

OK now I'm confused after reading this thread... Just checked my scanner config - it's set to spark retard as well - which should = ect timing pulls, iat timing pulls, torque timing pulls and on and on added together - right? Definitely not knock! Well at least I haven't been tuning anything off of knock alone I guess??? Going to have to fix my scanner now........ Also explains why it was making power on a few of them even though it was supposedly knocking and I thought I was just getting false knock from the sensors... Well - teaches me to pay better attention...

Only one thing I like about the generic sensors - works best for remote tuning just because it's a sensor parameter that all vehicles of that generation should have, so you can have one scanner config to use on multiple chasis...

[10_SS]

Only one thing I like about the generic sensors - works best for remote tuning just because it's a sensor parameter that all vehicles of that generation should have, so you can have one scanner config to use on multiple chasis...

So with this example I've decided never to use Generic Sensor ever again since I dont remote tune. I figure this way if I use my LS3 config on say the GenV stuff then worse case I wont get data for certain channels and will know right away what is not working rather than thinking it's working and have it be all wrong, in my opinion the way it should be regardless.