ECUflash CeddyMod v1 (EcuFlash)

[VETTE_50_TH]

I cant wait to get my car running and get SD going. Will be so awesome!

 

[GSXeclipsePSI]

Going to install 1.97b tonight updated one on ceddys page and test n tune tomorrow.

 

[VETTE_50_TH]

How many logs did it take to get your car up to speed with SD? Because im starting with the car not having any type of tune at all with bigger turbo, cams, fuel pump, injectors, what should be my main focus in my case?

 

[GSXeclipsePSI]

The SD map I setup so far was easy I just hit + on the values before 120 4x each for mine and they came close. I haven't done anymore tuning for the load above 120 in the RPM table.

You have to start with your injectors and then do some timing get it a little higher or not then work over to SD. That's the path I took. I'm adding a few more parts in the next few days I will have to re-tune again anyways. More boost with my wg on the way.

If you mean logs since I started with ECU I can't count. But if your talking about SD settings, I did about 5 revving at home.

Ooo yeah I been meaning to ask, under Speed Density on ecuflash is says to Lock Baro Pressure (set to 1)

and Speed Density Remove IPW Jitter (set to 255)

Do I have to do that? I figured it would be set to that if it needed to be. But it does say to set to those values.

 

[Ceddy]

You are using a 1g fuel pressure in your ecu then using an afpr to make it 43.5?

The ecu only sees injector size, it has no idea what fuel pressure is.

For example my 1150s:
At 43.5 psi you size at 1150.
At 38.0 psi you size at 1070

Ooo yeah I been meaning to ask, under Speed Density on ecuflash is says to Lock Baro Pressure (set to 1)

and Speed Density Remove IPW Jitter (set to 255)

Do I have to do that? I figured it would be set to that if it needed to be. But it does say to set to those values.

Those settings should be left as is. When you switch to the full SD rom they will be already changed to the appropriate values.

The only value that might need changing is Locked Barometric Pressure. It is set to 100 kPa (Sea Level) by default, if you live more then a couple thousand feet above sea you should change it to your local pressure.




I have started on a 3D SD table. Those considering switching to SD may want to wait til its done. Should be finished in a week or two.

Besides higher resolution and more control, another feature is made possible. A sort of Auto-Tune VE. By setting the VE table to 100%, then logging AirCntMAF / AirCntSD it gives you VE%. Put this log in MapTracer and you have your fully tuned VE table. This makes it possible to make your VE table with one good log, the old way the Evo guys did it could take days and a lot of logs and editing the VE tables.

 

[jrohner]

i have started on a 3d sd table. Those considering switching to sd may want to wait til its done. Should be finished in a week or two.

Besides higher resolution and more control, another feature is made possible. A sort of auto-tune ve. By setting the ve table to 100%, then logging aircntmaf / aircntsd it gives you ve%. Put this log in maptracer and you have your fully tuned ve table. This makes it possible to make your ve table with one good log, the old way the evo guys did it could take days and a lot of logs and editing the ve tables.

awesome!


BTW, did you change something that may have gotten rid of my constant nagging P0120? I haven't seen it since I switched to the version you sent me; I even drove 50-60 miles away and back today with no CEL!

 

[motomattxxx]

What about the inverted cas signal changeover? dont see it in the new version or in the last few versions? I thought that there was a mod for it?

 

[GSXeclipsePSI]

Yea Im going to wait til you get that all set up then. Like I said I got things I can work on in the mean time.

OK I was on openecu.org webpage noticed a new ECUFLASH beta wanted to post it here to anyone that doesn't check out the page often.

ECUFlash 1.43.3000b
The following beta is only available as a full install download due to the fact that it uses a new custom Openport 2.0 driver that is not backwards-compatible with previous versions of EcuFlash, or the J2534 DLL.

MUTII logging is now much more robust - it will re-initialize if there is a break in communications
Plus more check out openecu.org link below for full list of updates since 1.42 release.
MORE INFO

Don't forget to update the OP2.0 cable by clicking on Licensing

 

[Ceddy]

BTW, did you change something that may have gotten rid of my constant nagging P0120? I haven't seen it since I switched to the version you sent me; I even drove 50-60 miles away and back today with no CEL!

No, the P0120 is being a real bi*** to find. I have asked one of the Evo ecu OBD2 experts for some help. Hope to find it soon.


GSXeclipsePSI, the new EcuFlash beta uses a new driver, that will require you to completely uninstall EcuFlash and EvoScan, then reinstall, to get EvoScan working. I recommend people hold off installing this because the reinstall is a pain and you lose all your .xmls if you don't remember to back them up. And once you update the OP2.0 firmware you can't go back. The only reason I installed the new beta is I also do work on the Evo ACD/AYC ecu and the new version is required to flash it.



I've upload a new guide for using LogWorks to view EvoScan log files. LogWorks has a lot of nice advanced graphing and charting functions for displaying log data.

It can be viewed here -> http://ceddy.us/?page_id=507
(I may need to start putting FAQs and Guides on my website, because of policy changes on Tuners you can't edit old posts. This makes updating FAQs problematic.)


I have also started on Speed Density 2.0.
Because the of lack of space to fit a big 3D VE table in, we will probably have to lose the 2nd WarmUp Retard map, and the WarmUp Retard map will only be available as stock size when using BigMaps. This shouldn't be a problem because the WarmUp maps have no performance use, and the lower resolution stock size one will work fine. The upside is, this will allow for a 18 x 16 3D VE table.

 

[jrohner]

18x16 should be about perfect for VE, as long as 18 is for RPM.

Isn't the warmup retard just to heat up the Cat faster anyways? I zero mine out.

 

[jeffo]

Still no 7203 support??

 

[Ceddy]

Still no 7203 support??

The new beta version of EcuFlash is suppose to fix all 7203 flashing.

I know it works on the Evo ACD/AYC and Evo 6.5, both of which have MH7203 cpus.

I have been working on the Evo8 ACD DisAsm, the one strange thing is the 7203 has different flash REGs and Blocks. So I'm not sure how some of the ecus that changed cpus mid-year (2000-2001) work. From what I've seen the images are the same, but that shouldn't work if they have different REGs.
(I think flashing a 7202 image to a 7203 ecu and vice versa will brick the ecu)

CheckSum support for the Mitsu has also been added, the ACD/AYC and EvoX ecu are the only ones that use a checksum so far.

 

[Ceddy]

I finished coding "Speed Density 2.0" yesterday, and everything tested good today.

The one issue I did run into is I'm getting some really strange VE% numbers. I think the reason for this is I have a hacked MAF and 4" intake pipe (I need to compensate +25% at low Hz in MAF Smoothing because of my abnormal intake).

The Auto VE% Logging seems to work very well. If someone with a "normal" MAF and intake could get a VE% log it would help things a lot.

I have started on Boost Axis for the Timing and Fuel maps also. This replaces the Load axis with Boost, for Speed Density setups.

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

I have also found Fan Temps table. But I have one aftermarket single speed fan. If someone with the two stock fans, or two dual speed aftermarkets, could test this table it would help.

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

If would like to help out testing, send me a PM or email.

 

[GSXeclipsePSI]

O man I was just starting to understand the old way... I have a FP 4" intake so I don't think I can be any help on this one. Plus the turbo is off and the new FP race manifold are off getting coated.

 

[Hubbard 0]

I am happy to see the fan control stuff. I have a bit of a over heating problem and I'm hoping just a new thermostat and rad. cap will help. The new thermostat is a 170* too so I'm hoping to keep coolant below 200* at all times.

 

[Ceddy]

O man I was just starting to understand the old way... I have a FP 4" intake so I don't think I can be any help on this one. Plus the turbo is off and the new FP race manifold are off getting coated.

The new way is a lot easier to start out, as now you can log actual VE%. And you don't need to decide if a VE change should go in the MAP or RPM table. You can actually make the VE table with one log now, just need to hit every point on the VE map: Idle, Cruise, Spoolup, Boost, Engine Braking, Decel, etc.

I am working on an Excel MapTracer for SD, that you can cut and paste to EcuFlash. EvoScan will only MapTrace Fuel and Timing maps, and LogWorks doesn't allow custom axis divisions.

I don't think 4" intakes effect the 2G MAFs, as much as they do the Evo MAF. The Evo MAFs are very sensitive to intake changes. I think my hacked MAF is the main cause for issues, I had the same problem with a Injen intake and 16G setup.

 

[GSXeclipsePSI]

Sounds good, I wish we had another set of videos to learn from I'm really a visual learner.

 

[Hubbard 0]

On the Evo forum, a user named "Recompile" made 6 videos going from the very basics of evoscan and ecuflash, up to advanced techniques and editing .xmls.

They apply specificaly to the Evo's, but it's still very similar. When I get home I can link you there.

 

[logic]

recompile's videos.

 

[Hubbard 0]

recompile's videos.

What he said...

 

[Scientist]

Any chance you gonna port this over to the Evo 5/6 ecu and 8G Galant VR4?

 

[GSXeclipsePSI]

I have seen them I have them on my computer saved

 

[Ceddy]

Any chance you gonna port this over to the Evo 5/6 ecu and 8G Galant VR4?

I plan to make a version for the Evo5/6 and 3000GT. Someday...

I finishing up SD 2.0 now, and will work on Boost Control next. So still a long ways off.

 

[Scientist]

I know the VR4 board would gladly donate towards this for the Galant ECU which is H8 Based also

 

[GSXeclipsePSI]

I lost my old xmls whats the WB02 info for evoscan. I deleted the old xmls that still had WB02 for the rear mounted 02 wideband input.

thanks