HPTuner pids refer back to VE #
no Ken, i think he wants to know the RAW VE number, as stored in the PCM.
frankly, i would like to know it too, since i just reread the 've table cracked' thread again and i have some new ideas. or at least how do you calculate the raw value from the 'display' value?
frankly, i would like to know it too, since i just reread the 've table cracked' thread again and i have some new ideas. or at least how do you calculate the raw value from the 'display' value?
Trending Topics
I think he wants the VE table value in play at the time.
Which could always be done tediously by hand, but it
would probably be enlightening to see real vs modeled
tick by tick.
Which could always be done tediously by hand, but it
would probably be enlightening to see real vs modeled
tick by tick.
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
FormerVendor
Joined: May 2004
Posts: 152
Likes: 0
Originally Posted by jimmyblue
I think he wants the VE table value in play at the time.
Which could always be done tediously by hand, but it
would probably be enlightening to see real vs modeled
tick by tick.
Which could always be done tediously by hand, but it
would probably be enlightening to see real vs modeled
tick by tick.
It also does not save the x,y coordinates used to find and interpolate the table values. So the best anybody can do is model it in the scanner as a % error.
Anything else is just "entertainment".
-Ken
Originally Posted by Super Sport X2
The problem with that is the VCM rarely uses a "single" value from the table.
It also does not save the x,y coordinates used to find and interpolate the table values. So the best anybody can do is model it in the scanner as a % error.
Anything else is just "entertainment".
-Ken
It also does not save the x,y coordinates used to find and interpolate the table values. So the best anybody can do is model it in the scanner as a % error.
Anything else is just "entertainment".
-Ken
So you say.
FormerVendor
Joined: May 2004
Posts: 152
Likes: 0
Originally Posted by HumpinSS
So you say.
Will you please go find something else to do Humpinss, I'm trying to get some information from Phil here. Get back to me when you can actually edit a 3D table view instead of just look at it.
FormerVendor
Joined: May 2004
Posts: 152
Likes: 0
Nobody flamed you Humpinss. I responded to Jimmys question and you had to get your 2 cents in.
The VCM does not save the x,y table coordinates, only the result it interpolated which can be up to 4 cells.
You can map it with software, but you will always be at the mercy of the scanner data rate.
The VCM does not save the x,y table coordinates, only the result it interpolated which can be up to 4 cells.
You can map it with software, but you will always be at the mercy of the scanner data rate.
FormerVendor
Joined: May 2004
Posts: 152
Likes: 0
You can guess Humpinss. One must make the assumption that the time the VCM picked the table results is the exact same time it updated the scanner ram PID's. Then you have the delay in data transmission, delay in picking up the error in the exhaust stream, etc.
So the answer to Phil's question is it's not an exact timed science or sequence of events that can be traced back to the original number in the VE table. You can cover an area as % error and call it good. Like I said, anything else is just entertainment to watch the software guess where things came from.
Even the VCM treats all AFR errors as corrections due to "persistent" errors.
Thats why everybody call it a histogram
Without over complicating things, just use the histograms and copy/paste the errors, then smooth the area.
So the answer to Phil's question is it's not an exact timed science or sequence of events that can be traced back to the original number in the VE table. You can cover an area as % error and call it good. Like I said, anything else is just entertainment to watch the software guess where things came from.
Even the VCM treats all AFR errors as corrections due to "persistent" errors.
Thats why everybody call it a histogram
Without over complicating things, just use the histograms and copy/paste the errors, then smooth the area.