First off let me say, I did indeed do a search.

I am going to be installing a HSR and new cam this summer. I am wondering about some PROM tuning advice for the initial startup. I have been working with my TPI for a while and I figure that should be good enough to get started with.

Does anyone that runs a HSR or even a MiniRam have any suggestions for a new PROM? I have read that at the upper rpm range they, HSR, want more fuel and little less timing. What about idle and low RPMs?

I am open to any and all suggestions. Thanks in advance.

 

Capture lots of data, use VEPhD (which you'll find by doing a search) and you'll get the midrange tuned right.

 

I did a search like you suggested but I still have some questions if you don't mind. What is VEphD? How does it work? What will it do for me? And how do I get it if I need it?

One of the posts in the search leads me to believe it is a program that helps to evaluate how the VE table needs to be modified. Am I correct?

Thanks...

 

First off let me say, do another search.

But seriously, I did a quick search on the DIY_PROM forum for 'vephd' and this article has a good description.

https://www.thirdgen.org/techbb2/sho...ighlight=vephd

You might also download DataMaster from TTS, and VEMaster from Joe Georger's site (find info on both by searching)...DataMaster gives you 20 runs free before the demo expires, and that should be enough to run data thru VEMaster and get a decently-tuned bin cut.

 

Yeah, I did a quick search. Will do more through today since I have more time.

I have Datamaster already. Using the PP2 and Tuner Cat as well. I have heard of the VEMaster you mentioned as well. I just don't know what they are or do. I will try to find out. THanks for you leads.

 

VEMaster is pretty slick. You drive around w/ Datamaster capturing data, save the data, then feed your saved data and the .bin you were running thru VEMaster...it spits out a modified .bin with the VE tables recalculated based on the BLMs you logged at the various RPM/KPa coordinates.

To really make use of VEMaster, get a good sampling of driving conditions....hold the gears to higher revs a few times, pull a hill or two both at steady cruise and accelerating, etc. The more variety you get saved, the more VEMaster (and VEPhD for that matter) can do to your VE tables.

 

Thats it!!!

Isn't that a little too easy...

How good is it at correcting the VE? I read in the webpage for VEMaster that it only was designed for working at part throttle VEs. It said it only works to about 3000. What do ya think?

 

It's very good, and goes as high in the RPM range as you tell it to go. I've actually held gears @ part throttle up to 5K on flat road and hills just to get data, and VEMaster uses it.

About the only anomaly I'm tracking now is Datamaster's use of some field other than BLM to report long-term fueling compensation...it's not the same field that Moates uses. I drive a stretch of road with a fresh bin and Datamaster running, the histogram shows various cells in slightly rich/lean states...same stretch w/ Moates and I'm nearly dead on @ 128 +/- 2.

Datamaster reports both BLM and some "Cross Counts" value, but it uses the cross counts to measure & report fueling compensation. Probably OK, just not straight BLM like I'm expecting.

 

Well I am glad to hear that VEMaster works at higher RPMs. I typically cruise at about 2500+ RPM and sometimes cruise at 3500 to keep up with my friends. No overdrive kinda sucks.

I will download the VEMaster tonight and test it out some time next week. Thanks for you input.