Scanner issue with VE Histo

[0352goat]

My VE STFT error histo is showing 105 kPA at part throttle/idle, while the chart display is showing the proper kPA. Even using the stock Imperial scanner config the same thing happens, any ideas?

Side note, I am glad I caught this as I was using this data for STFTs.

[Bill@HPTuners]

Very hard to troubleshoot without the scanner log and config file you are using.

[0352goat]

Hey Bill,
Couldn't upload it at the time, i'll post it once I get home tonight. Thanks

[0352goat]

Here is the config i'm using.
After all this time I still have this issue, I haven't noticed is as i've been MAF only. I am now wanting to go SD and this is preventing any progress!

[edcmat-l1]

Post a log to go with the config.

[0352goat]

A brief log is attached, just a drive from work to home.

[0352goat]

I'll give a quarter for anyone who helps!

Haha

[edcmat-l1]

When I replay your data log, it plots the VE vs STFT just fine. The only one that doesn't, is number 11.

BTW, why so many pids? I'd get rid of most of them. Alot of them are pretty useless. Not to mention they might slow down the scanner.

[0352goat]

I might try and reinstall the scanner then, not sure why it's doing this to me! Haha

What do you suggest I drop? I haven't really visited the PID's in some time.

Thanks Ed, your help is always appreciated and generally comes when I need it most.

[edcmat-l1]

I might try and reinstall the scanner then, not sure why it's doing this to me! Haha

What do you suggest I drop? I haven't really visited the PID's in some time.

Thanks Ed, you're help is always appreciated and generally comes when I need it most.

Awww, I'm all gushy now LOL

I usually setup scanner configs by order of importance for what I'm doing at the time. One would have basic airflow parameters, with minimal additional pids. Something like MAF, MAP, dyn air, RPM, TPS, advance, KR, STFT, commanded A/F pids, WB, something like that. Maybe a few others but not near what you have.

Then I usually have a separate one for trans tuning, where I'll have all my trans pids and torque pids, and less of everything else.

For dyno tuning, I'll have my ignition pids, injector PW and DC %, timing, KR, dyn air, and for autos, TCC slip.

[0352goat]

Awesome thanks for the input. I'll work on cleaning those up later tonight.

Here is a screen shot of what I am seeing. I just uninstalled and installed the suite and I am still seeing this:


Here you can see in the histogram that my MAP is being read at 94 kPa while the chart reads the proper 36 kPa

[edcmat-l1]

Don't know if it's the cause or not, but I don't run with all those windows open, and all those pids. I only use the line graph for reviewing data logs. While logging, I only use the primary table, the histograms, and rarely, the dash. I only use the dash if there's something I want to keep an eye on at a quick glance. Otherwise, I don't even use it.

I would try minimizing your pids, and try just logging with the primary table, and your histograms. Then see how it works.

[0352goat]

I remember having an issue with the chart display when it was doing the same, to fix that I had to change it to the MAP (SAE), for the histogram I have no such option as it uses the Primary VE vs RPM vs MAP..

*grumble*
lol

[Bill@HPTuners]

works fine for me, I have a feeling he has a custom pid or two that is skewing his numbers. Thats where I would start looking at least. If I were to remotely connect to his pc the first thing I would do is delete his VCM Scanner.cfg file(which is where all custom pids are stored) then reopen the scanner and try again. Considering it works for Ed & myself I would tend to believe its a custom pid being the variable here.

[0352goat]

Bill,
Where is this .cfg file located? I'll drop that and try again.

[planethax]

I am wondering if there is something wrong with your vcmscanner config.

Using the config you posted and that log file I see the map working correctly for both.

Edit: Very slow today, need to remember to refresh page before me posting again lol

[0352goat]

That fixed it, thanks everyone. Now to get these PIDs in right.