ECUflash CeddyMod v1 (EcuFlash)

[delta448]

It's difficult to do without very adversely affecting other parts of the tune. If you have an adjustable BOV, you could try setting it to a harder cracking pressure, but that can also cause some compressor surge.

I've not seen anyone successfully tune out all the ill effects of venting while the ECU is still dependant on the stock karmen sensor to measure airflow.

 

[Ceddy]

Anyone know of a good way to tune out the bov vent to atm without going to SD? I am going to transition sometime shortly, but for now after i get my car running, it will be running the maf. Unless someone has a good flash for a 20g on e85.

If you can tighten the BOV spring so its not open during vacuum, its not that bad to tune. It will only go rich between shifts.

The 1G BOV and others that are open during vacuum, will suck a large amount of unmetered during idle, cruise, etc. And shouldn't be run that way. You can get away with it, but if you are going for performance, it should be recirculated.

 

[VETTE_50_TH]

Ok. The tial i have has the 12 pound spring i believe so we will see. Hopefully i can remove most of it.

 

[GSXeclipsePSI]

Found these on evolutionm.com

Omni4Bar Settings
0.51 25
0.90 49
1.29 70
1.68 96
2.07 120
2.46 144
2.85 170
3.24 195
3.63 255


And these

Omni4BarSettings

0.61 31
0.90 46
1.09 56
1.80 92
1.99 102
2.40 122
3.01 153
3.59 183
4.98 255

Which should I use. Each has a different voltage. I figured I would want to use the 2nd set of number since the scaling goes to 5v

 

[Ahnubus_29]

Man ricers and having to vent there bov for the cool sound. Its not worth the hassle just run it the right way until you can go speed density, I mean honestly is really that inmportant to have have that noise when it effects the vehicles drivability.

 

[Ceddy]

Found these on evolutionm.com

Omni4Bar Settings
0.51 25
0.90 49
1.29 70
1.68 96
2.07 120
2.46 144
2.85 170
3.24 195
3.63 255


And these

Omni4BarSettings

0.61 31
0.90 46
1.09 56
1.80 92
1.99 102
2.40 122
3.01 153
3.59 183
4.98 255

Which should I use. Each has a different voltage. I figured I would want to use the 2nd set of number since the scaling goes to 5v

No, you need the formulas like: 0.2369*x-14.5

I'll dig them up tonight.

 

[GSXeclipsePSI]

I believe this is it, it was on the one link i posted

"EvoScan Boost logging- 0.238683*x-14.7"

 

[VETTE_50_TH]

Man ricers and having to vent there bov for the cool sound. Its not worth the hassle just run it the right way until you can go speed density, I mean honestly is really that inmportant to have have that noise when it effects the vehicles drivability.

WTF are you talking about. Sorry, but i cant vent my bov since its a standard tial and i have a standard FP intake. Please dont assume. Its not worth buying two sets of setups.

 

[GSXeclipsePSI]

I can't get the items needed to setup SD to log because they are not on the Evoscan list. Is this because I am using the 2.7beta?

You must be logged in to view this image or video.

I added them in anyways, but when I load/over write the data.xml it doesn't change.

I setup the Evoscan scaling for the 4bar I think.

Ceddy please tell me if this is correct. I just modified the GM3Bar item. (attached photo)

Changed also:
Gauge max 44
Chart max 44

Left other settings alone.

 

[Ceddy]

CeddyMods 1.94 beta is now ready for release.

Info, new features, and download link can be found here -> http://ceddy.us/?page_id=16

 

[GSXeclipsePSI]

To anyone else have problems updating there Evoscan xml in Vista I had to uninstall Evoscan 2.6.

Then enable hidden folders. Then go to my computers user file, select my user name.

Go under APP DATA - Then Local - Then Program Files - Then go to virtual store and delete the evoscan files in there for the xml files to be overwritten (evoscan items to be logged).

Then reinstall evoscan and put the xml file in the correct folder.

 

[VETTE_50_TH]

Quick question now that my gsx is getting ever closer to completion. To get the SD working, Leigh (turboking15) has done most of the wiring and wired the gm map sensor into place. To get the SD working, all i need to do, is log in evoscan the maf and map aircounts and then what do i do. I read the file on your website, but im unsure what to do after i log. I also still need to buy the iat. I know that has to be wired in after i log with the maf.

Please let me know. Thank YOU!!

 

[Ceddy]

Quick question now that my gsx is getting ever closer to completion. To get the SD working, Leigh (turboking15) has done most of the wiring and wired the gm map sensor into place. To get the SD working, all i need to do, is log in evoscan the maf and map aircounts and then what do i do. I read the file on your website, but im unsure what to do after i log. I also still need to buy the iat. I know that has to be wired in after i log with the maf.

Please let me know. Thank YOU!!

You should use version 1.94 if you plan to go SD.

You need to log AirCnts MAF and AirCnts SD. The goal is to get them to always match.

AirCnts SD is calculated using the VE% Tables.

You must be logged in to view this image or video.

RPM VE uses a simple percentage.

MAP VE uses a load lookup. If the numbers are equal , its 100% VE.


So simply look at AirCnts SD and AirCnts MAF.

If SD is 10% lower then MAF, whenever you are at 5000 rpms, you would raise RPM VE, 10% at 5000 rpms. (5000 rpms at multiple loads)

If SD is 10% lower then MAF, whenever you are at 40 kpa, you would raise MAP VE, 10% at 40 kpa. (40 kpa at different rpms)


Most of your tuning is going to be in the MAP VE table, the RPM VE table is more for adjusting for huge cams, and even then it only going to change a few percent.


Because the VE tables are 2D and only have 26 items to edit between the both of them, it doesn't take that long make your VE tables.


CeddyMods is setup to use a GM 3 BAR by default, if you are using a different MAP, you need to change settings in EcuFlash.

 

[VETTE_50_TH]

Yea, i have the 3 bar. So when do i plug in the iat then? Any reason for using the 1.94 rather than what 1.8x

 

[GSXeclipsePSI]

I believe the newer version has 10bit rather then 8bit SD and it has more resolution also support for different MAP sensors plus the other listed NEW ITEMS on Ceddy's webpage.

 

[Ceddy]

Yea, i have the 3 bar. So when do i plug in the iat then? Any reason for using the 1.94 rather than what 1.8x

You plug the IAT in when you fully switch to SD and ditch the MAF.

SD has been completely redone. Old maps are not compatible with new ones.

 

[VETTE_50_TH]

Gotcha. Thank you.

 

[_Madman_]

I have an opportunity to get an AEM wideband for acceptable price, but I have no idea if I'll be able to use it.

From what I understand AEM emits analog signal in range 0-0.5v through regular wire, and therefore I cannot use it through USB on laptop.

But I've heard thet EVO guys can feed this analog signal into their ECUs through unused port and get the result through logger.

Do DSM ECUs have free ADCs that can be repurposed for wideband inputs? Maybe rear narrow band input can be used for this?

 

[Ceddy]

I have an opportunity to get an AEM wideband for acceptable price, but I have no idea if I'll be able to use it.

From what I understand AEM emits analog signal in range 0-0.5v through regular wire, and therefore I cannot use it through USB on laptop.

But I've heard thet EVO guys can feed this analog signal into their ECUs through unused port and get the result through logger.

Do DSM ECUs have free ADCs that can be repurposed for wideband inputs? Maybe rear narrow band input can be used for this?

You can use the Rear O2.

But you will get a much more accurate signal if you make a serial cable for it.

evolutionm.net - View Single Post - AEM UEGO Serial Cable Instructions

Costs about $5 to make.

 

[Hubbard 0]

I have an opportunity to get an AEM wideband for acceptable price, but I have no idea if I'll be able to use it.

From what I understand AEM emits analog signal in range 0-0.5v through regular wire, and therefore I cannot use it through USB on laptop.

But I've heard thet EVO guys can feed this analog signal into their ECUs through unused port and get the result through logger.

Do DSM ECUs have free ADCs that can be repurposed for wideband inputs? Maybe rear narrow band input can be used for this?

The AEM has a serial output that you can connect to an RS232 cable and run to your laptop. You'll have two USB cables running to your computer, but it will work.

Evoscan is setup to read the AEM too.

 

[_Madman_]

Ceddy, do you have any information about the EvoScan definition results with other ECUs?

Because of the CAS problem, I'm still running the old "Enginnering Sample" ECU I had in my car originally, and I was wondering if I can use the 2.6 definition to log this ECU. That is, if the scaling values and requests match the definition.

The ECU is weird, EvoScan 2.5 didn't logged it at all, but 2.6 with MUTII EFI option I can log it just fine, with a very good sample rate, but there are some questions.

The coolant temp scaled floats in -10C to -17C range, MAF Air temp is also in range +40C to +80C, Octane level is sitting at 80ish, but jumps to 100 or 0 on knocking, very sharp spikes. And finally, the speed seems to run all over the place from 0 to 400, with it being 200 when car is idling.

So I'm wondering if those logging requests are MUTII specific or ECU specific? I'm still little bit unsure about which EvoScan logged data I can trust on which ECUs, for example NA 2Gs.

It's not very important or anything, but if you know the answer, it would be great to know what's compatible across ECUs and what's not.

 

[Ceddy]

Ceddy, do you have any information about the EvoScan definition results with other ECUs?

Because of the CAS problem, I'm still running the old "Enginnering Sample" ECU I had in my car originally, and I was wondering if I can use the 2.6 definition to log this ECU. That is, if the scaling values and requests match the definition.

The ECU is weird, EvoScan 2.5 didn't logged it at all, but 2.6 with MUTII EFI option I can log it just fine, with a very good sample rate, but there are some questions.

The coolant temp scaled floats in -10C to -17C range, MAF Air temp is also in range +40C to +80C, Octane level is sitting at 80ish, but jumps to 100 or 0 on knocking, very sharp spikes. And finally, the speed seems to run all over the place from 0 to 400, with it being 200 when car is idling.

So I'm wondering if those logging requests are MUTII specific or ECU specific? I'm still little bit unsure about which EvoScan logged data I can trust on which ECUs, for example NA 2Gs.

It's not very important or anything, but if you know the answer, it would be great to know what's compatible across ECUs and what's not.

Mitsu changed things around in the MUT Table a lot in the MID 90s. After 98 they seem to keep things in the same place. The scalings should be correct, but many of the RequestIds may be wrong. Only way to really tell is to see if the data looks good.

 

[GSXeclipsePSI]

I'm about to go out and log some data. I noticed my PSIG for my omni sensor was reading 7000.xxxx-8000.xxxx at idle is that normal?

and my MAF raw was around 198-205 (very jumpy) and SD was 328-335 (not as jumpy) So what changes should I try to make there? I just need a better idea of what to do. I may not be the only one.

Fuel trims are working good I am at -9 on current which isn't bad for guessing settings now logging yet. But I have 1200cc down to 739cc.

 

[Ceddy]

I'm about to go out and log some data. I noticed my PSIG for my omni sensor was reading 7000.xxxx-8000.xxxx at idle is that normal?

and my MAF raw was around 198-205 (very jumpy) and SD was 328-335 (not as jumpy) So what changes should I try to make there? I just need a better idea of what to do. I may not be the only one.

Fuel trims are working good I am at -9 on current which isn't bad for guessing settings now logging yet. But I have 1200cc down to 741cc I think.

PSIG should read 0 with the car off, around -12 at idle.
kPa should read 100 with car off, around 30 at idle.

(I see problem, Omni 4 BAR PSIG function should be: 0.2369*x-14.5, not x0.2369*x-14.5)

The MAF signal is kinda choppy at low airflow, SD makes the car run much smoother.

You should log:
AirCnt MAF
AirCnt SD
RPM
Omni 4 BAR kPa

If:
AirCnt MAF = 200
AirCnt SD = 330
kPa = 40
Then:
You would lower MAP VE load to 60% current value at 40 kPa. (200 / 330 = 60%)
So if current value is 40.5, new value would be 24.3. (40.5 x 60% = 24.3)

You need to free rev the car and get readings for 10, 20, 30, 40, 60, 100, 120 kPa and repeat the above calculations.


Above 120 kPa MAP VE should be 1:1 (kPa = Load), so now you will use the RPM VE table.

If:
AirCnt MAF = 500
AirCnt SD = 550
kPa = greater then 120
RPM = 5000
Then:
500 / 550 = 91%, so in the RPM VE table you would enter 91% at 5000 rpm.


The hardest part is deciding if a VE change should go in the MAP VE or RPM VE table. But if you use MAP VE for less then 120 kPa and RPM VE for greater then 120 kPa, you will get things fairly close.


Last time I did my VE tables I got AirCnt MAF and SD to match within 2% at all points. ( Except during BOV release they won't match.)


If you are not familiar with kPa (Kilo-Pascals), 100 kPa = 1 atmosphere.
0 kPa = absolute vacuum, 100 kPa = 0 psi, 200 kPa = 14.5 psi, 300 kPa = 29 psi, etc.

 

[Hubbard 0]

I finally got my 2.0 cable after ordering it over 3 weeks ago.

Gonna jump right into 1.9 too.

Question regarding Evoscan and the AEM wideband. I currently have v2.6, is that the one with issues logging the wideband? Last time I went out tuning we had problems with that.