speed density with ceddy mods

[chronicvex]

I have 3-bar and iat wired in and was wondering what settings should be enabled. I tried before and it wouldnt start. Im using a 3-bar so its already calibrated.
AAny help is appreciated.

Thanks.

 

[Tiki2777]

You can't just use his regular ceddymods, so make sure that you bought his sd version or sd/bigmaps version. I seriously don't understand how so many people make this mistake. If this isn't your problem, I would make sure your battery cable is not corroded and on tight. Also, make sure that you have a good VE table that is tuned at least somewhat closely to your setup. Did you log the needed info with the sensors and tried to use the iat and map with the MAF still plugged.

http://ceddy.us/ceddymods/speed-density/

 

[chronicvex]

I purchased full version. VE tables are already made for 3 bar I thought? My understanding is that you only need to log if youre using something else. I am running 3 bar map with maf right now and mdp unplugged which works fine without SD enabled. I am having issues going to full SD though.

Ps I have read that page about 100 times now. Lol

 

[MY1GDSM]

You need to build a VE map for your Setup and no motors VE is 100% the same... . Cars don't tune themselves and SD is a lot more involved then just plugging in the Right map Sensor.

IIRC, it comes set all across the board at 100... .

 

[chronicvex]

Ok. So I guess I just log with 3 bar and maf plugged in with SD disabled? Thanks

 

[Tiki2777]

I purchased full version. VE tables are already made for 3 bar I thought? My understanding is that you only need to log if youre using something else. I am running 3 bar map with maf right now and mdp unplugged which works fine without SD enabled. I am having issues going to full SD though.

Ps I have read that page about 100 times now. Lol

Also, make sure you have changed the map scaling for the map sensor to your specific brand and make. I am going to have to change mine to omni 4 bar, just make sure you change yours if you have a different one than the stock setting (i think you just right click the map).

 

[chronicvex]

Also, make sure you have changed the map scaling for the map sensor to your specific brand and make. I am going to have to change mine to omni 4 bar, just make sure you change yours if you have a different one than the stock setting (i think you just right click the map).

Im using gm 3 bar so its correct by default. So can anyone confirm that I havr SD disabled while im logging?

Why does ceddy already have a ve table set up if its not usable?

 

[Tiki2777]

Im using gm 3 bar so its correct by default. So can anyone confirm that I havr SD disabled while im logging?

Why does ceddy already have a ve table set up if its not usable?

Because its a nice base to go off of. I believe its the same the evos start with (after all thats where he got his base coding from).

 

[bjmauck]

I'm about to start the same process. Good luck. Hope it goes smooth.

 

[knochgoon24]

Log the MAF airflow counts vs. SD airflow counts. The values that goes in the VE table should then be approx:

New VE = Old VE * (MAF-SD)/SD + Old VE

Ex.
MAF: 150 counts
SD: 68 counts
VE: 100 %

New VE = 100 * (150-68)/68 + 100 = 221


Since you can log all these parameters, you can actually set up a loggable parameter that automatically calculates this for you. Then you can pull it up in the Map Tracer in EvoScan.

And like that link to Ceddy's page says:

If there is a discrepancy that varies with pressure the MAP Sensor VE and Calibration would be changed.
Or if there is a difference that varies with engine speed RPM VE would be changed.

Also beware that you may have to add a little fuel through the startup enrichment table if your car struggles on cold starts.

 

[chronicvex]

Thank you for the input!

 

[chronicvex]

Ok I logged those two items but I don't know what to do from here? How do I open it up in map tracer?

 

[TsiJohn333]

Hes done all the necasarry logs now to build his ve tables, but hes having trouble graphing them. He cant get evoscans maptracer to load his log so he could copy and paste his ve tables over to ecuflash/ceddymods. He logged 2byte aircounts sd and 2byte aircounts maf and aircount ve% change. How does he graph these items to the correct percentages so he can input them into ecuflashs ve table. Any help would be appreciated.

 

[Tiki2777]

Hes done all the necasarry logs now to build his ve tables, but hes having trouble graphing them. He cant get evoscans maptracer to load his log so he could copy and paste his ve tables over to ecuflash/ceddymods. He logged 2byte aircounts sd and 2byte aircounts maf and aircount ve% change. How does he graph these items to the correct percentages so he can input them into ecuflashs ve table. Any help would be appreciated.

That may be a problem with evoscan. Lately, for some reason, updates for evoscan have been causing problems instead of fixing things. I'm not sure why, but i think there is a wiseman out there who has discovered more about this...

 

[chronicvex]

Using evoscan 2.7.

 

[TsiJohn333]

That may be a problem with evoscan. Lately, for some reason, updates for evoscan have been causing problems instead of fixing things. I'm not sure why, but i think there is a wiseman out there who has discovered more about this...

The only other way i can thought of is open up his log in microsoft excel and campare his ve change and rpm. Then factor the numbers in myself but it looks like there could be to many variables to get an accurate result. I'm stumped. Is there any other program that can make this graph? We are using evoscan 2.7 with ceddy's xml files to log sd aircounts and maf aircounts. We cant use evoscan 2.9 because ceddys xml files to log SD will not work with it.

 

[chronicvex]

Log the MAF airflow counts vs. SD airflow counts. The values that goes in the VE table should then be approx:

New VE = Old VE * (MAF-SD)/SD + Old VE

Ex.
MAF: 150 counts
SD: 68 counts
VE: 100 %

New VE = 100 * (150-68)/68 + 100 = 221


Since you can log all these parameters, you can actually set up a loggable parameter that automatically calculates this for you. Then you can pull it up in the Map Tracer in EvoScan.

And like that link to Ceddy's page says:



Also beware that you may have to add a little fuel through the startup enrichment table if your car struggles on cold starts.

Where am I getting my old VE?

Let me give you an example of what is going on here.
My 2Byte Aircounts Maf at 1k RPM and 10 Load= 107.6
My 2Byte Aircounts SD at 1k RPM and 10 Load = 1931.2
My SD VE% as is is showing as 100.
So the equation comes out to 5.6 rounded up.
From what I understand the 5.6 is going in my VE table. Please correct me if I'm wrong.
If i'm correct... is there an easier way to fill this whole table? Lol. My log doesnt cover it all. Although, I guess the areas I'm not covering arent really something to worry about because I probably wont come across them often.

 

[knochgoon24]

Yes, it would be something like that.

But you probably don't want 5.6 %VE in a 10 load cell. You probably won't hit it unless you're under a lot of vacuum (hard decel). While your injectors will normally be off for decel fuel cut, if you crack the throttle slightly, I guarantee that number won't work.

The easiest way I've found is to add that formula to EvoScan AFTER the other 3 parts (VE %, MAF counts, SD counts) and just log it a bunch.

You want to hit as many cells as you can while tuning with the MAF, then take the best educated guess you can at the cells you didn't hit.

 

[chronicvex]

http://img3.imageshack.us/img3/8010/dsmve.png

This is a 30 minute log.... All my 10 load cells are like 5-6. Btw the table shown is the variable that Ceddy added with the formula already built in. I took the three variables and put them into an equation to make sure that they came out the same. I don't know what to do if 6 wont work there. . What should it be more around? When I get this running good I need to do a write up on this because it isnt explained all that well Haha. Speed Density for idiots.

 

[knochgoon24]

That doesn't look right at all.

 

[Tiki2777]

i would redo that evoscan formula for the new VE because just like Knoch said, it doesn't look even close. Also, log the regular values and try to use the formula by hand to compare that stuff.

 

[chronicvex]

i would redo that evoscan formula for the new VE because just like Knoch said, it doesn't look even close. Also, log the regular values and try to use the formula by hand to compare that stuff.

I tried doing it by hand and it came out the same. Is old VE supposed to = 100? Is my SD Aircounts supposed to be in the thousands?

Also, could boost leaks cause something like this? I suspect i'm leaking...

I'm logging using MAF Big Maps with 10 bit map enabled, sd calculations enabled and airflow calculations enabled. Jesus this is a pain in the ass. I'v been trying to get SD running for weeks now. Only reason why I bought the damn software.

 

[Tiki2777]

I tried doing it by hand and it came out the same. Is old VE supposed to = 100? Is my SD Aircounts supposed to be in the thousands?

Also, could boost leaks cause something like this? I suspect i'm leaking...

I'm logging using MAF Big Maps with 10 bit map enabled, sd calculations enabled and airflow calculations enabled. Jesus this is a pain in the ass. I'v been trying to get SD running for weeks now. Only reason why I bought the damn software.

Dude... . Old VE= base map Ceddy gives you. (at that specific load, rpm etc...) Sometimes its just one of those days, and it must be one for you .

 

[chronicvex]

That brings me to 3.6 at 1k RPM 10 Load...

 

[Tiki2777]

I hope i don't have this many probs as you when i got my fuel system up and make the switch. I hope you get this running soon. You should definitely make a tech article or guide for all ecuflash peeps.