Well i'm after a program that will create an Volumetric Efficiency table that is suitable for my engine. I'm not really sure how they work. Even if someone can explain to me it would be great.
I'm in the process of programming an 808 ecu and i'd just like to have everything configured right.
Are there any good sites out there that will teach be about all this? I am very interested in all of it. I'm just a beginner though.
Thanks alot
I'm in the process of programming an 808 ecu and i'd just like to have everything configured right.
Are there any good sites out there that will teach be about all this? I am very interested in all of it. I'm just a beginner though.
Thanks alot
Supreme Member
Desktop Dyno 2000 display volumetric efficiency.
Tim
Tim
Supreme Member
Bringing this back from the dead.... Is the VE table is creates good for anything? Is there any way to determine "optimum" spark information based on engine specs similar to the way Desktop Dyno can create a VE table?
Senior Member
The only drawbacks to this that I can see are:
1.) DD2000 only gives a single dataset for VE vs RPM
2.) There is no way to get it to generate a VE vs MAP table that I can see
3.) You have to take the DD2000 numbers and convert them to numbers that can be put into your VE% tables and then burned to a chip.
Does anyone here know of anyway around this? What about Panalyze? Doesn't it give some sort of VE stuff?
Nevermind...I just looked at Panalyze...the newest version I could find. It just takes the csv file and parses it into a more meaningful form.
Now, if you look at Craig's VEPhD, you can adapt it to just about any ECM. I started doing that but I haven't quite finished it yet. All I am doing is removing the rows and columns that I don't need for my VE tables. When I finish it, I'll let you know how it works.
1.) DD2000 only gives a single dataset for VE vs RPM
2.) There is no way to get it to generate a VE vs MAP table that I can see
3.) You have to take the DD2000 numbers and convert them to numbers that can be put into your VE% tables and then burned to a chip.
Does anyone here know of anyway around this? What about Panalyze? Doesn't it give some sort of VE stuff?
Nevermind...I just looked at Panalyze...the newest version I could find. It just takes the csv file and parses it into a more meaningful form.
Now, if you look at Craig's VEPhD, you can adapt it to just about any ECM. I started doing that but I haven't quite finished it yet. All I am doing is removing the rows and columns that I don't need for my VE tables. When I finish it, I'll let you know how it works.
Supreme Member
Quote:
Originally posted by Scott_92RS
Bringing this back from the dead.... Is the VE table is creates good for anything? Is there any way to determine "optimum" spark information based on engine specs similar to the way Desktop Dyno can create a VE table?
When you get to working in the advanced lab areas at, at least the big two, ie GM, and Ford, they have some simulation stuff that gets close. Other then that nothing, that'd I'd trust. A few years ago I bought some real expensive software, and the results were always based on threshold detonation tuning. And for that you can just tune for 93, dump in some 116, and then add 4* and be close, IMBOriginally posted by Scott_92RS
Bringing this back from the dead.... Is the VE table is creates good for anything? Is there any way to determine "optimum" spark information based on engine specs similar to the way Desktop Dyno can create a VE table?
Senior Member
Quote:
Originally posted by Grumpy
When you get to working in the advanced lab areas at, at least the big two, ie GM, and Ford, they have some simulation stuff that gets close. Other then that nothing, that'd I'd trust. A few years ago I bought some real expensive software, and the results were always based on threshold detonation tuning. And for that you can just tune for 93, dump in some 116, and then add 4* and be close, IMB
Ford uses a program called Mandy. It's really good but what's the point? Give the engine what it wants, not what you think it needs. The only time the software helps is to see trends or to simulate resonance tuning or cam selections. Unless you're designing an engine from the shortblock up I wouldn't bother with software. Just use software like DD2000 to get an idea of where your peak vol eff will be. The power of DD2000 is very limited. It isn't based on scientific evidence but instead, trends, hence errors if you do anything goofy and out if it's "range."Originally posted by Grumpy
When you get to working in the advanced lab areas at, at least the big two, ie GM, and Ford, they have some simulation stuff that gets close. Other then that nothing, that'd I'd trust. A few years ago I bought some real expensive software, and the results were always based on threshold detonation tuning. And for that you can just tune for 93, dump in some 116, and then add 4* and be close, IMB
If you had a buisness I would recommend Virtual 4-stroke. It's not cheap but it'll give you accurate results.
For the money, I'd rather purchase an engine dyno with some good data-aq like NI Labview
. Tags cj7, creating, efficiency, extended, gen, gm, programming, site, table, tbi, volumetric