A cool feature of 2.0 HPT
FormerVendor
Joined: Jan 2003
Posts: 525
Likes: 0
From: Melbourne, Australia
v1.7 already does AFR % error histogram, has done for more than 6 months... 
2.0 includes fully customizable 2D and 3D histograms with auto axis selection based on the editor tables. It also includes custom PIDs that can be created by the user. Common ones like AFR% error, calculated g/cyl etc. are included in the defaults.
Chris...
2.0 includes fully customizable 2D and 3D histograms with auto axis selection based on the editor tables. It also includes custom PIDs that can be created by the user. Common ones like AFR% error, calculated g/cyl etc. are included in the defaults.
Chris...
Originally Posted by gameover
v1.7 already does AFR % error histogram, has done for more than 6 months...
Chris...
Chris...
FormerVendor
Joined: Jan 2003
Posts: 525
Likes: 0
From: Melbourne, Australia
Originally Posted by Black02SS
He was refering to MAF AFR % error histogram. For calibrating the MAF table with ease and not using excel.
Nope. VCM Suite 2.0 just picks up where 1.7 left off.
The 2.0 interface is a lot more graphical than the 1.7 interface.. but the layout is still similar enough that learning 1.7 will only help you with 2.0.
The 2.0 interface is a lot more graphical than the 1.7 interface.. but the layout is still similar enough that learning 1.7 will only help you with 2.0.
Nope, you will not have to relearn the entire tool, but there will be other features that will enhance what you have learned. 
EFI's Auto VE tune = HPTuners EIO AFR% Error
HPTuners will have the ability to tune the MAF table without the need of excel.
The #D histogram (I would think) looks much like the 3D surface display.
EFI's Auto VE tune = HPTuners EIO AFR% Error
HPTuners will have the ability to tune the MAF table without the need of excel.
The #D histogram (I would think) looks much like the 3D surface display.
LS1 Tech Stories
The Best V8 Stories One Small Block at Time
6 Common C5 Corvette Failures and What's Involved In Repairing Them
Pouria Savadkouei
Retro Modern Bandit Pontiac Trans AM Comes With Burt Reynolds' Autograph
Verdad Gallardo
Top 10 Greatest Cadillac V Series Performance Models Ever, Ranked
Pouria Savadkouei
Top 10 Most Powerful Chevy Trucks Ever Made!
Hennessey's New Supercharged Silverado ZR2 Has 700 HP
Verdad Gallardo
Coachbuilt N2A Anteros Is an LS2-Powered C6 Corvette In Italian Clothes
Verdad Gallardo
Awesome K5 Blazer Restomod Comes With C7 Corvette Power
Verdad Gallardo
10 Camaros You Should Never Buy
10 LS Engine Myths That Refuse to Die
Verdad Gallardo
Originally Posted by Jimmyz
I'm just now scratching the surface of 1.7...does this mean I have to re-learn the entire tool?
i never saw 2.0 before yesterday afternoon.. and by the evening, i was using it faster then i was using 1.7... its the same things... and its pretty well laid out... learning 1.7 now can only help.
Originally Posted by Phoenix57
i will be tuning with a WB and the EIO. can the program use that data to properly calibrate the MAF instead of the narrowband trims? this will make a lot of people really happy instead of just guessing on the MAF settings
Originally Posted by Black02SS
He was refering to MAF AFR % error histogram. For calibrating the MAF table with ease and not using excel.
In the past DAY.... I have tuned 2 MAF's...out to 5 decimals
made my own histogram with the MAF table and LTFT's..
was able to tune the MAF in both cases in 3 passes to get it within -2 to +2 everwhere........and I did a few more to get it really accurate.....
I had to buid my own excell spreadsheet(which is still available for download) to do MAF calibration before 2.0......
the only problem I see is that no matter what you have fopr mods..the narrow o2's will still pull the LTFT's to 0 anyways....adn you need your PE multiplier for WOT...so might as well tune the MAF to LTFT's and then use the PE table to get WOT right with the wideband...
The thing to remember is that you are tuning a vehicle that is always trying to tune itself....so get everthing in line with what the car is going to do anyways....and then tune the values that dont ever change after that
Last edited by soundengineer; Aug 24, 2005 at 10:16 AM.
oh...forgot to mention.... I also was able to show a buddy his injectors were maxing out because of the ability to plot injector duty cycle vs map vs rpm...
he didnt believe me when I told him before that his injectors needed to be biger....
now he can see it on my screen..LOL
he didnt believe me when I told him before that his injectors needed to be biger....
now he can see it on my screen..LOL
Originally Posted by soundengineer
oh...forgot to mention.... I also was able to show a buddy his injectors were maxing out because of the ability to plot injector duty cycle vs map vs rpm...
he didnt believe me when I told him before that his injectors needed to be biger....
now he can see it on my screen..LOL
he didnt believe me when I told him before that his injectors needed to be biger....
now he can see it on my screen..LOL
hey, cant you save/share histogram files now?? that one sounds intresting...
Yeah...I'm still not sold on tuning the MAF this way. My headers really play tricks on the O2 sensors, which is where the trims are coming from...
That injector duty cycle vs map vs rpm sounds quite intriguing though...I've never checked to see how my injectors are handling my light mods.
That injector duty cycle vs map vs rpm sounds quite intriguing though...I've never checked to see how my injectors are handling my light mods.
TECH Fanatic
Joined: Mar 2003
Posts: 1,946
Likes: 1
Originally Posted by MeentSS02
Yeah...I'm still not sold on tuning the MAF this way. My headers really play tricks on the O2 sensors, which is where the trims are coming from....
This may have already been mentioned (Phoenix57) but...
Just like the way you tune your VE table using AFR% error could you not use a WB O2 sensor and the AFR% error (vs. commander AFR) to calibrate the MAF??? This would require a VERY accurate VE table I would think though... AND it may only be pertinent to steady state driving, when MAF and MAP are most likely to agree????
Last edited by SideStep; Aug 24, 2005 at 10:43 AM.
Originally Posted by MeentSS02
Yeah...I'm still not sold on tuning the MAF this way. My headers really play tricks on the O2 sensors, which is where the trims are coming from...
That injector duty cycle vs map vs rpm sounds quite intriguing though...I've never checked to see how my injectors are handling my light mods.
That injector duty cycle vs map vs rpm sounds quite intriguing though...I've never checked to see how my injectors are handling my light mods.
you really need to explain these "tricks" since you seem to talk about them enough.
Originally Posted by SideStep
This may have already been mentioned but...
Just like the way you tune your VE table using AFR% error could you not use a WB O2 sensor and the AFR% error (vs. commander AFR) to calibrate the MAF??? This would require a VERY accurate VE table I would think though...
Just like the way you tune your VE table using AFR% error could you not use a WB O2 sensor and the AFR% error (vs. commander AFR) to calibrate the MAF??? This would require a VERY accurate VE table I would think though...
The VE table would have to be spot on as well...and from what I've found, even that has to be a compromise. From what I've seen, part throttle/cruising needs to be tuned open loop to a multiplier of 1.0, but WOT needs to be tuned to what you are shooting for (which for me is 1.13). So you have to find a good middle ground and blend the results...there is some sort of calculation based on the commanded AFR that I don't fully understand.
Originally Posted by MrDude_1
you really need to explain these "tricks" since you seem to talk about them enough.
Originally Posted by Magnus
Yes, you can load and save histograms..
Its in the program files/hp tuners/vcm suite 2/histograms.
You can save them to your desktop as well and then e-mail them.
Its in the program files/hp tuners/vcm suite 2/histograms.
You can save them to your desktop as well and then e-mail them.
yea, i know.. i was just hinting he should post it.. lol
Originally Posted by MeentSS02
With long tube headers, the O2 sensors are moved further down the exhaust stream. This means the gases have more time to cool, not to mention the fact that the gases cool even more because there is a great deal more surface area than the manifolds provided for the cooling of the exhaust gases. O2 sensors need heat to work well, and when they are moved downstream, they aren't getting this heat anymore. This causes lazy O2 sensors (meaning they don't switch as fast as they would have in the stock location), and will eventually kill them. Therefore, the feedback loop is corrupted.
but they're modern HEATED O2s.... and when you use the recommended Bosch 13111 sensors, they even have a higher wattage element.... why the hotter element? because modern cars sometimes have O2s so far back, they're behind the cats!!! (lol just messin with ya.. lil sarcasm there..)
seriously though, they're heated O2 sensors, and you can WATCH them switch in the scanner..
