I have a WB on my car but it is sending the pcm a narrowband signal but when I try to load the 98 2 bar VE-Afr error % it says that the histogram is supported in the current loaded parameters... Is this user error on my part or is there something else that I have to do??? I'm just trying to tune my VE tables because I'm running in OLSD and moved from Cali to Oklahoma so I want my commanded AFR to be correct... Thanks and please help me..
Sounds like you aren't logging one of the necessary PID's to allow the histogram to work properly.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
I'm using the one that's already configured for the 98 2 bar...
Yeah then you definitely aren't logging the correct pid's.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Post a scan and config.
Bill Winters
Former owner/builder/tuner of the FarmVette
Out of the LSx tuning game
I'm assuming he's using the default imp config which doesn't log commanded afr which is why the afr error histogram wouldn't work.Originally Posted by 5_Liter_Eater
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Bill I believe that you are correct.. I'm about to go log and would like to be able to use the afr error histogram... Is there something that I'm doing wrong that you can help me with??
Add the "commanded AFR" PID yo your table.
Bill Winters
Former owner/builder/tuner of the FarmVette
Out of the LSx tuning game
Hmmm... makes sense.. hahaha..
Yeah, AFR error is a calculation of the difference between commanded afr & actual(wideband) afr. If you aren't logging either one of those the custom PID that is AFR error will be broken & non functional.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Okay, I got it now guys... Sorry, just haven't really used my software much lately because of new baby, moving from California to Oklahoma, and searching for a job... Thanks guys and I'll let you know if it works (I'm sure it will)....
Here's my log from tonight... I tried to put in the afr error in the table but it never actually logged them... I'm in OLSD so I don't know if that matters...
Also here's my tune...
http://www.hptuners.com/forum/showpo...42&postcount=8
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Ok Bill, I've tried to add the commanded AFR pid (both low and hi res)... i was not able to even see the low res until I cleared last vehicle scanned and then I found it... I added it to my table and then when i started scanning it seemed to not be supported...I understand I need to learn but I just need a little guidance... Thanks for the support so far....
Make sure you are logging 24 bytes of information or less, no need to log both high & low resolution. One or the other is fine. You might need to delete a pid or 2 to keep you under the 24 bytes, but if you know what your ECT usually is thats an easy one to rid yourself of.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Ok I got it... So things that aren't going to need to be monitored like STFT, LTFT, things like that get rid of for the time being to make it be able to log??? Thanks, I feel I'm getting closer...
Just an FYI, I got it Bill!!! thank you so much...
Reply With Quote