vephd blues
#1
vephd blues
Been trying to get vephd to work with 7427 $od, frustrating to say the least. Have already modded the vephdat file to corespond with tunerpro rt csv data log. But everytime i try to run the program it stops short of giving me an .out file with an error message overflow in module vephd at line 0568:2231 any one have a solution. Seems to work fine with the sample .in file. could sure use some help cause i'm doing something wrong.. thanks
#2
Member
Join Date: May 2004
Location: Grand Rapids, MI
Posts: 105
Likes: 0
Received 0 Likes
on
0 Posts
Car: '90 Formula
Engine: L98 --> Ramjet
Transmission: Auto
Re: vephd blues
I've used vephd quite a bit, but i've never seen that error message. I'd say double-check your settings...this thread may help?
https://www.thirdgen.org/forums/diy-...ighlight=vephd
https://www.thirdgen.org/forums/diy-...ighlight=vephd
#3
Re: vephd blues
Yes that is an informative thead. What i ended up doing is pasting my rpm kpa, blm ,etc info from my data log into the vephd.in file and the program ran though with no errors. However with $od using one o2 sensor it appears my corrected ve numbers are only half of what they should be, am I reading this corectly?
#4
Member
Join Date: May 2004
Location: Grand Rapids, MI
Posts: 105
Likes: 0
Received 0 Likes
on
0 Posts
Car: '90 Formula
Engine: L98 --> Ramjet
Transmission: Auto
Re: vephd blues
One thing you might do to make sure it's calculating correctly is to note the number of rows that are in your "in" file. Make sure it's basically the same number of rows vephd tells you it crunched after it's done. If not, then something's wrong.
VEPHD is just a number-cruncher. It doesn't care what code/mask you're using, but you have to make sure it's getting its data in the proper format.
HTH
VEPHD is just a number-cruncher. It doesn't care what code/mask you're using, but you have to make sure it's getting its data in the proper format.
HTH
#5
Re: vephd blues
Everthing seems to crunching corectly, however for engines with one o2 sensor should the blm2 and int2 be set at zero or 128? I have it set at zero right now which seems to be why my output values are approx half of what i expect. Thanx for your help.
#6
Member
Join Date: May 2004
Location: Grand Rapids, MI
Posts: 105
Likes: 0
Received 0 Likes
on
0 Posts
Car: '90 Formula
Engine: L98 --> Ramjet
Transmission: Auto
Re: vephd blues
I'm assuming you're referring to the settings in the vephddat.csv file. You need to tell it the column # that the data is located in, in the input file.
Seems like zero should work for you. I'm also using just one blm and int, but my setup is a little different. For both blm1 and blm2 I'm telling it to use the same column # (same for int). So it's crunching two blm's, but they're the same numbers, so in my mind it's the same as just having one. This works for me - you might try this and see if you're output changes.
Seems like zero should work for you. I'm also using just one blm and int, but my setup is a little different. For both blm1 and blm2 I'm telling it to use the same column # (same for int). So it's crunching two blm's, but they're the same numbers, so in my mind it's the same as just having one. This works for me - you might try this and see if you're output changes.
Thread
Thread Starter
Forum
Replies
Last Post