Is there anyone using the OpenECU flashing and editing tools?

If so, lets chat on tuning

Yes, I am. I've used Enginuity and flashed my car a few times with some changes.

what kind of methodology do you use when "tuning"? I've figured out the flashing part.. I'm just lost with the whole changing values part...

what kind of methodology do you use when "tuning"? I've figured out the flashing part.. I'm just lost with the whole changing values part...
I saw your post on the Enginuity site. There is something seriously wrong with your flash, as you shouldn't be seeing KC values like -12 over and over again at low loads and in vacuum. I think your map is jacked, but the only thing questionable I saw was that rev ignition limit - I haven't seen that on some of the other XMLs, like XMLwrite, so it might be something you don't want to experiment with. Do you have any logs with your stock map? If I were you, I would only copy over the values that are on the Cobb map and nothing else.

Anyway, I learned a lot from guys on this site - crazymikie, drees, jon ct, riftswrx, I'm sure I'm leaving out someone. Do some searches in this engine management, you'll find a wealth of discussion. What I've learned is that you should get your combo about where you want it and then get a custom tune. Then from there, you can make small changes as needed. Starting from stratch with mods and doing a road tune, you really have to know what you're doing and EGT, wideband, knock light are musts, and even then you can't match a good dyno tune by experienced tuner. Best to at least start out with an off-the-shelf map at a minimum and go from there.

I've only been playing with this stuff for a week or two now so i'm still very early on in the game... I've got a ton of reading to do but it's kinda hard to hear that there's no DIY solution that can't replace a good dyno tune.

hehe.. I'm kinda embarressed being such a n00b at all of this... As for my post on enginuity.org, it was very puzzling... I have lots of logs with the stock maps and i'd only ever see negative knock correction values when I coast around at super low rpms... I like to take 5th at about 60 km/h. I've kinda gotten into a habit of shifting super early and only shifting down when absolutely necessary.

Eitherway, I'd still be able to maintain a high IAM with the stock maps with that driving style so for the 5-10 minutes I ran with the "upgraded" maps, I couldn't believe that it was knocking so much so early (after reading the logs). I wasn't shifting super early but the hesitation got me so scared i didn't try anything risky.

As for the maps I should copy over to use as a base, I basically blindly copied all the maps that differed from the stock maps (about 10 total maps)... Should I only stick with a subset? the big three: timing, fuel, and boost(target and WG-DC) and forget about all those other ones like boost rev limit, or others (damn, i can't remember the names and I'm too lazy to turn on my lappy to check...)?

Another thing is that I wonder if i've got enginuity properly supporting the ECU ROM version i have. The majority of the maps out there are the 02 WRXs and 04 and 05's. i wonder if support for the 03 maps have suffered because of this. I figured since enginuity read an 03 rom properly it should be writing it properly too... but that's something I'm not sure how to check.

Anyways thanks for the feedback! As for my goals... I'm a cheap-ass guy so bang-for-the-buck is the most important to me. so most hardware mods are out of the question. the most I'll probably ever do is open up the exhaust with a up/dp/exhaust... This is why i'm so intrigued at engine management. It's like free power (sorta)!.

I am currently working on an STI In canada. Check openecu.org under my name.

PM your stock map with your new logs.

For the new logs perform the following funtions:-

1) Drive normal
2) Drive aggressive
3) Log 3, 4 & 5 gear pulls from low rpms as possible @ WOT.

It seems you know how to flash.

I will send you a new rom where you can look over and upload.

Send me the rom you are on w/ a detail logs with load, rpm, boost and so on.

I will need that info in the logs above.

I've only been playing with this stuff for a week or two now so i'm still very early on in the game... I've got a ton of reading to do but it's kinda hard to hear that there's no DIY solution that can't replace a good dyno tune.
It's not impossible, but it takes a lot of time, experience and equipment (notably EGT, wideband, knock light). Some guys have even rented out dynos for a few hours so they can tune their own cars. On the street, it is really difficult to quantify incremental gains made by small changes. For example, you might be adding some boost and on the dyno you could see what gains you were getting from x amount of boost. You might reach a point where increasing the boost past a certain point (say 17 psi) would result in very little increase in HP. Maybe increasing to 18 psi nets you less than 1 hp. The same can be done with timing and fuel at different loads/rpm as well, especially with the Protuner stuff, where they can do real time tuning.

hehe.. I'm kinda embarressed being such a n00b at all of this... As for my post on enginuity.org, it was very puzzling... I have lots of logs with the stock maps and i'd only ever see negative knock correction values when I coast around at super low rpms... I like to take 5th at about 60 km/h. I've kinda gotten into a habit of shifting super early and only shifting down when absolutely necessary.

Eitherway, I'd still be able to maintain a high IAM with the stock maps with that driving style so for the 5-10 minutes I ran with the "upgraded" maps, I couldn't believe that it was knocking so much so early (after reading the logs). I wasn't shifting super early but the hesitation got me so scared i didn't try anything risky.
Well, I didn't mean you were knocking. Some negative knock correction is normal off-boost and is occasionally seen in most people's logs, but it shouldn't be real knock. The ECU does not use those negative number to lower your IAM - you have to be under a certain minimum amount of load (like 1.0, IIRC). But you logs were showing -12, -10 over and over again in each row. I've never seen that before. Did you log with your stock map before? If you have, then post them up. If not, revert back to the stock map and log and see if you get the strange KC values.

As for the maps I should copy over to use as a base, I basically blindly copied all the maps that differed from the stock maps (about 10 total maps)... Should I only stick with a subset? the big three: timing, fuel, and boost(target and WG-DC) and forget about all those other ones like boost rev limit, or others (damn, i can't remember the names and I'm too lazy to turn on my lappy to check...)?

I looked at your map and it looked ok. The rev ignition limit thing I wasn't sure about though. It's possible that one of the other tables has something screwy about it in the XML. Which XML are you using? I would copy over the primary maps - WDC, boost, ignition, fuel and also the two turbo dynamics tables. I wouldn't worry about the others like boost limit, egt limit, etc. for now, which wouldn't be an issue for stage 1 anyway.

You do have the right idea, though. Starting with a staged map and tuning from there.

I am using EcuEdit for map editing, now just switched to an XML definition created by XMLWrite, and use Ecuflash to reflash/read. I tend to post on openecu.org a lot.

I had already modified the DBW table to get rid of the throttle plate closing at 7000rpm, raised the outright rev limiter, modified wastegate duties, etc, although I am still using my UTEC for primary tuning.

I just installed new injectors and am going to attempt to run a 100% openecu reflash only, taking the UTEC out of the equation (for now, I still want some UTEC features, but I want the flash to work on its own first off). I'm curious how much just injector scaling will take care of it (Perrin modified injectors).

Good guys,

Keep more of the good stuff coming.

I would really like to see some problems logs w/ custom roms.

Thanks for all the input guys! this is getting very interesting! I'll try to find some time to get the logs for those runs soon..

I literally flashed to ECU only fuel injector scaling between runs at the dragstrip tonight after getting pissed off at the craptastic things that happen when you use UTEC fuel injector scaling. Namely, the ECU wants to run stupid high timing since it thinks very little air is getting in, so on off-throttle, the transition from UTEC to ECU timing goes from something like +20 to +46 while still in nominal load, causing sick nasty knock. I honestly don't know how you could ever run a UTEC with large injectors without this problem and popping huge knock events every time you eased off the throttle and went back to ECU control.

I am going to spend the next few weeks with the UTEC turned off and try to run OpenECU flash only. I'll probably be posting more on openecu.org, though.

I know Freon, but I noticed that there were some noise :) here and I thought that it would be nice to start a thread on that.

Thanks for all the input guys! this is getting very interesting! I'll try to find some time to get the logs for those runs soon..
No prob.

I look forward to them :)

I made the IGN rev limit change back to the stock value and tried it out.

The maps worked! no nasty knock/det. Car was running and ran relatively smooth. I definitely noticed a bigger kick in 1st and 2nd gear when going into boost.

I got a bunch of logs but I don't want to use them since I'm running on a relatively bad tank of gas. Even with the stock maps, my IAM was hovering around 5 with this gas. with the new map (and lots of hard driving), i'm only at 8. I drove hard, easy, and did a few 3rd and 4th gear pulls.

west_minist, If you think you can still use the logs, just let me know.

I PM u.

Send me both Stock and your tune rom.

Rev limiter fix and the drive by wire throttle shut fix I put in definitely work. I just raised it to 7100. I've run it up to 7100 no problem.

Car is running great on Perrin modified STI injectors purely by changing the injector scaling value. Had to try three times to find a good value, but half the problem is figuring out how the ECU stores injector scaling. It is not in CC/min or lbs/min, it is an ontime coefficient, so the value actually needs to go DOWN with larger injector. It is easy enough to invert it, but finding the right coefficient for that is under discussion. I think I've settled on what it is, but some disagree, fair enough. Either way, Perrin modded STI USDM yellowtop sidefeed injectors are just about right on +50% flow of stock.

You guys visit either of these sites today? I can't get to them, just got the cable, need the drivers.

-Jason

http://www.ftdichip.com/Drivers/VCP/Win2000/R2176.zip

The newest Ecuflash (1.27) includes and installs the drivers. Openecu.org had been flaky, but seems to be running better the last few days.

mr_yellow,

How is the tuning going?

I did a rom pull with the new one and it works very nice.

I have a usdm 2005 sti. I have the cobb access port and i installed version 1.27 ecuflash. I connected the green connectors but I can't read the rom. What am I missing? I'm able to use the cable for logging on ecuexplorer just fine.

Found out I have to have a different cable. I ordered one from Tactrix. Can't wait until it gets here :)

Did you get the flash block connector or jumper the flash block?

No I thought I read that I don't need that for a 2005 sti.

Ok. No prob. I have not look @ the doc. So you maybe right.

You have the v1.2 cable?

The 1.2 is what I ordered. Sucks I can't overnight it.

I believe none of the drive-by-wire (all 2.5L turbos?) require the flash block. Just the green test connector.

For the 2.0L turbos, it varies, but the newer models are less likely to need it.

I've had my cable for more than a month. Took me about two weeks of reading and playing with the various software interfaces to decide on one I liked. I'm now using Enginuity and over the past week have reflashed about twice a day :)

I got into it because I was having horrific problems running my new 3.5" blow through MAF. Not to mention all of the other crap in the mix. Today, my map is completely augmented (fuel injectors, MAF table completely re-scaled, AFR maps, base timing, timing correction, many common CEL's disabled, etc). The very last thing I'm working on at the moment is my 'Tip-in Enrichment' and I'll be finished. I've just got to get the tip-in table formatted in the definitions first.

I'm also running UTEC in CL fueling for fine corrections. My UTEC transition used to make large jumps from like 30* in the stock ECU to UTEC fixed timing at maybe 24*. While that may have worked functionally, I never liked that about UTEC. Now, my stock ECU timing is the identical to UTEC timing and is a perfect transition. In fact, my stock ECU timing is almost a mirror of UTEC timing to redline. This is on 93 octane gas.

I'm really happy I got my cable :)

I have a few questions, as I am interested in this option.

1. Can the dealership tell if you have flashed? (Assuming you go back to the original map before taking it in.)

2. Will this type of flash prohibit you from using a AccessPort later on?

No and no. The dealership doesn't read out your ECU or CRC check it AFAIK. No OBD or SSM capability is lost when you flash, you're just messing with tuning maps. The dealership couldn't tell that you've done an Openecuflash any better than if you have done an Ecutek or Cobb AP. Since the Openecu stuff is open, it necessarily changes less code. You only need to change the tuning maps, nothing else needs to be touched. No license, no realtime code changed, etc.

Be careful trying to use both Openecu stuff with either an Ecutek'd or AP'd ECU. You can potentially flash over your license. AP also changes code to make the "real time" map thing happen, so you probably don't want to try to tune a Cobb AP flashed ECU with the openecu stuff.

The Accessport just writes right over what you had when you first marry it and flash it. It can't tell what was there before. If you have an Ecutek, then get an AP, the AP will right over your Ecutek license like it was never there.

IOW, the same general risks exist when mixing any of the three flashes together, except the Openecu you never "lose" your license since there is none. It's all free.

I have a few questions, as I am interested in this option.

1. Can the dealership tell if you have flashed? (Assuming you go back to the original map before taking it in.)

2. Will this type of flash prohibit you from using a AccessPort later on?
No, to both. They are using the stock subaru protocol to do the reflash, just as the ap does. In fact this is less detectable than the ap, as it will correctly reflash _your_ stock map, vs the generic cobb one. This (should) include vin if the ecu includes it from stock. (2005 sti does not, as far as I can tell, from comparing multiple rom copies).

No, to both. They are using the stock subaru protocol to do the reflash, just as the ap does. In fact this is less detectable than the ap, as it will correctly reflash _your_ stock map, vs the generic cobb one. This (should) include vin if the ecu includes it from stock. (2005 sti does not, as far as I can tell, from comparing multiple rom copies).

Thank you. :)
And you too Freon. I just noticed your post. :banana:

Subcribed.

(2005 sti does not, as far as I can tell, from comparing multiple rom copies).

uh yes it does you can read the vin with a generic obd-2 scanner

uh yes it does you can read the vin with a generic obd-2 scanner
I know, but it does not appear to be in the main ECU image-I've compared 3 different copies of the same rom file, and been unable to locate differences. There is a 4 byte field that I have seen 2(not 3) different values in, but I don't believe that is vin, not sure what it is. (at offset ff8)

I don't think you can tell if the data contained in the the tables have changed. Unless there's something within the Subaru Select Tool.

I've heard (and seen screenshots) that in the VW/Audi world, there's something in their hardware that will show the number of flashes. So maybe it could be detected on Subaru I'm not sure. With the hardware that I have, it doesn't tell you that.

I know, but it does not appear to be in the main ECU image-I've compared 3 different copies of the same rom file, and been unable to locate differences. There is a 4 byte field that I have seen 2(not 3) different values in, but I don't believe that is vin, not sure what it is. (at offset ff8)
I've heard that the VIN is at least located in the RAM. Not sure how it gets written there though.

I've heard that the VIN is at least located in the RAM. Not sure how it gets written there though.
Yep, I know it is read from ram. I wonder if on the 05+ sti it might be coming from the immobilizer module, but don't know. Going to re-read my 05 sti map to confirm, too. That would give me 3 different copies of the same revision.

Yep, I know it is read from ram. I wonder if on the 05+ sti it might be coming from the immobilizer module, but don't know. Going to re-read my 05 sti map to confirm, too. That would give me 3 different copies of the same revision.
You can read your RAM using ECUexplorer's "ECU Query" function. You don't even need to connect the green diagnostics connectors. Most of the data is in the first 8kb, which is the default setting.

I have a few questions, as I am interested in this option.

1. Can the dealership tell if you have flashed? (Assuming you go back to the original map before taking it in.)

2. Will this type of flash prohibit you from using a AccessPort later on?

if the dealship checks the date the rom file was flashed compared to
manufacture date you're busted.

i have access to a subaru scan II & factory ecu flash modules.
and when you check rom file the dates will appear.

if the dealship checks the date the rom file was flashed compared to
manufacture date you're busted.

i have access to a subaru scan II & factory ecu flash modules.
and when you check rom file the dates will appear.


great.

if the dealship checks the date the rom file was flashed compared to
manufacture date you're busted.

i have access to a subaru scan II & factory ecu flash modules.
and when you check rom file the dates will appear.
Is that stored in the main rom file or in a separate processor/file?

Most probably in the kernel, since thise deals with uploading.

But it could be a chance that the timestamp could be place in the same rom when it was edited.

The Pro's will have to step in here or go to openecu.org and post there.

Can u change the date/time on the computer back? :D Where does the timestamp come from that gets written to the ecu?

if the dealship checks the date the rom file was flashed compared to
manufacture date you're busted.

i have access to a subaru scan II & factory ecu flash modules.
and when you check rom file the dates will appear.

I appreciate you have access to the Subaru tools, but I don't think that is a feature of the ECU itself, but instead the Subaru tools that explicitly set a date.

Generally there are no automatic triggers. Unless the tools you are using explicitly change something, it doesn't get changed.

I would guess what you describe is irrelevent. I would be interested to see what date you find with your Subaru tools after a recent Openecu or AP flash. I wouldn't believe either situation until actually tested. Do you have regular access to these tools to test?

There is no "date of flash" stored in the ECU/CPU. I think the Subaru tools are simply showing the dates of release of various CALIDs (ROM versions).

im new to the whole openecu flashing methods but im learning slowly. i was wondering if anyone has any direct links to the software i need to dl to flash. im doing this all for my buddy with a stcok 02 wagon so im would like to know where i could maybe load a base tune also. any help is much appreciated.

im new to the whole openecu flashing methods but im learning slowly. i was wondering if anyone has any direct links to the software i need to dl to flash. im doing this all for my buddy with a stcok 02 wagon so im would like to know where i could maybe load a base tune also. any help is much appreciated.
A few things to understand first. You'll need ECUflash, which allows you to read and flash your ROM. Then you will need a tuning program. Ecuflash has a tuning program built-in. Other tuning programs include Ecuedit and Enginuity. In addition, you will need an XML file for your particular revision for each tuning program you want to use. The XML file basically tells the tuning program where to find the tuning data for your particular ECU and how to convert the data to something you can understand. Most people use a program called XMLwrite to write XML definition files for Ecuflash, Enginuity, or Ecuedit. If you use the XML file that came with the tuning program's DL, it is often incomplete.

ECUflash: http://openecu.org/downloads/ecuflash_setup128.rar (you'll need to register at the www.openecu.org site to download).

Enginuity: This is a tuning program I use. Download the latest version here: ( http://www.enginuity.org/viewforum.php?f=2&sid=9c22916b43e6de398d5bf978fc0540c8 ). I've also created a comprehensive XML definition that covers all USDM WRX revisions and some non-USDM ones. Get it here: ( http://www.enginuity.org/viewtopic.php?t=360 ). The nice thing about it, is that it is in english units like psi, whereas your XMLwrite definitions will be in metric, like bar.

XMLwrite: Use this XML generator for Ecuflash and Ecuedit. The link for its DL on its main thread has been removed. I'm sure it is somewhere on the openecu.org site.

Ecuedit: See this thread to download. The latest version is 1.2.0.71. http://forums.openecu.org/viewtopic.php?t=190&start=285

Also, this site: ( http://www.osecuroms.org/ ) has staged maps developed by the community for download. Right now they are in a revision for the 05 WRX only, but you can copy over the tuning values to your friend's 02 map, if you feel comfortable using the tools and you know what you are doing.

What kind of wideband do you recommend that is also affordable?

The stock works good up to 11.25. Get an Innovate LM1 or LC1.

The stock works good up to 11.25. Get an Innovate LM1 or LC1.

Not entirely correct. Someone on here actually did a side by side comparison on what the stock primary O2 sensor can do and what a true wideband can do. The stock one was off by quite a bit. If you're tuning the car with the primary wideband in the car and something like ecuExplorer reading the output you're going to run into major issues down the line.... Just a heads-up.

How far off is the stock o2. Lean or rich?

The stock O2 is actually fairely accurate down to 13.5 or so from what I've seen.

Below that, it starts reading rich, and doesn't read any lower than 11.25:1 or so (you'll know as it will flatline and not read any richer), but by that time it could be a whole point off.

Here's a great thread on IWSTI about it: http://www.iwsti.com/forums/showthread.php?t=36914&highlight=accurate

So if the stock sensor reads 11.25:1, you can be somewhat certain that the motor isn't any leaner than 12.25:1 or so.

How far off is the stock o2. Lean or rich?
The point is it isn't accurate. If it was always off by 0.5 AFR at 11.0 AFR or something, the sensor calibration curve would've already been tuned to compensate for that.

Get a real wideband. Do not tune your car with it. Stop trying.

It would be interesting to log the stock O2 side by side with LM1 or similar. I know it's accurate to a point just not sure how far. Maybe down to 12.8:1 -13:1 AFR. I know anything past that and it definitely seems off.

Freon , Do not worry My car is getting dyno tunned as we speak. Probably next month I'll buy a lc1, just to have it.

Subscribed, to watch this develop.

what are the gains on doing a flash to a basic upgrade tune on a pretty much stock 2005 wrx wagon?

what are the gains on doing a flash to a basic upgrade tune on a pretty much stock 2005 wrx wagon?

I'd have to say that depends on your ability to tune vs an off the shelf remap.

I'd have to say that depends on your ability to tune vs an off the shelf remap.
Im interested in what a basic ecu re-flash(off the shelf) would affect in the ecu. Ie what it would change etc. to produce a little more power.

Im interested in what a basic ecu re-flash(off the shelf) would affect in the ecu. Ie what it would change etc. to produce a little more power.
same basic things that get changed in all tunes: wastegate duty cycle, ignition map(s), ignition advance, fuel maps, desired boost maps. These basic things, plus/minus a few others, are what _EVERY_ reflash, no matter vendor or tuner, change. There are 3 main reflash systems available right now: Ecutek, Cobb AP(also includes hw), and openecu. All work by overwriting subaru's stock rom image with a new rom image. Cobb is currently the most advanced, in that they have a realtime capability that is expected soon to the openecu method. ecutek is probably the worst from the advanced user's POV, as it a: locks your ecu against any reflash. b: is only available from a ecutek dealer. c: impossible for user to modify at all. d: costs as much as the cobb product.
Openecu is the cheapest, but also the most rapidly evolving and has a bit of a learning curve. In addition, people are just starting to share "stage" maps for the openecu product.

I have done some work. Pretty basic is very relative. My baisc is all out :)

All of my roms have ign temp compensation, jdm learning, and many other changes. MY first release of JDM WRX will be soon out. Auto WRX 2002-2003 still need some work because of people schedules, Manuals are the same thing, 2001-2003 JDM STI almost finish.

Just review the software and spend a lot of time ont he open tools forums.

A few things to understand first. You'll need ECUflash, which allows you to read and flash your ROM. Then you will need a tuning program. Ecuflash has a tuning program built-in. Other tuning programs include Ecuedit and Enginuity. In addition, you will need an XML file for your particular revision for each tuning program you want to use. The XML file basically tells the tuning program where to find the tuning data for your particular ECU and how to convert the data to something you can understand. Most people use a program called XMLwrite to write XML definition files for Ecuflash, Enginuity, or Ecuedit. If you use the XML file that came with the tuning program's DL, it is often incomplete.

ECUflash: http://openecu.org/downloads/ecuflash_setup128.rar (you'll need to register at the www.openecu.org site to download).

Enginuity: This is a tuning program I use. Download the latest version here: ( http://www.enginuity.org/viewforum.php?f=2&sid=9c22916b43e6de398d5bf978fc0540c8 ). I've also created a comprehensive XML definition that covers all USDM WRX revisions and some non-USDM ones. Get it here: ( http://www.enginuity.org/viewtopic.php?t=360 ). The nice thing about it, is that it is in english units like psi, whereas your XMLwrite definitions will be in metric, like bar.

XMLwrite: Use this XML generator for Ecuflash and Ecuedit. The link for its DL on its main thread has been removed. I'm sure it is somewhere on the openecu.org site.

Ecuedit: See this thread to download. The latest version is 1.2.0.71. http://forums.openecu.org/viewtopic.php?t=190&start=285

Also, this site: ( http://www.osecuroms.org/ ) has staged maps developed by the community for download. Right now they are in a revision for the 05 WRX only, but you can copy over the tuning values to your friend's 02 map, if you feel comfortable using the tools and you know what you are doing.

Thank you, very informative. :)

What tuning program are most of you using when flashing with ecufash or ecuexplorer and why? Pros and cons of the different software.

What tuning program are most of you using when flashing with ecufash or ecuexplorer and why? Pros and cons of the different software.
ECUexplorer is a logger and does not tune, although it does have an older command-line version of ECUflash that you can use to read/flash the non-drive-by-wire Subarus.

ECUflash lets you read/flash/tune both the non-DBW (02-05 WRX) and DBW roms (STi, FXT, LGT, etc). Ecuedit and Enginuity are tuning programs only. All of the tuning programs use an XML database base file which contains references to different ECU revisions telling the software where to find the data. Because the XML file(s) that comes with Ecuedit and Ecuflash are limited, most people use a program called XMLwrite to write the XML file for their particular revision. Enginuity comes with a full-featured XML file already and this program just added DBW support. Enginuity also is the only program in standard units (psi, F, etc), although they have a metric file available for download.

If your XML file is incomplete, incorrect or missing for your revision, then either you won't be able to open your ROM, or you won't have access to as many tables, or you will be reading (and writing) incorrectly.

Im interested in what a basic ecu re-flash(off the shelf) would affect in the ecu. Ie what it would change etc. to produce a little more power.

Ignition advance/retard, AFR (both low and high det tables), boost, and CL/OL crossover. There are many other tables that go into tuning though but these are the (more) major ones. For driveabilty, that's where a little more tuning skill comes into play. The MAF table is a b%tch when you begin to play with it (if you need it). You may need to adjust idle rpms, injector scaling, rev limit, etc etc etc etc etc........ There are many opportunites to make changes, some good and some not so good as to the produced effects.

You guys know how to turn off CEL codes with EcuFlash?

- Matt

You guys know how to turn off CEL codes with EcuFlash?

- Matt
Enginuity does.

Depends on what codes... You can turn off the CELs for EGT and O2 with ecuEdit.

I haven't run those programs yet... do you have to read the ROM and convert it to XML, or is there a function in ecuEdit or Enginuity that allows you to clear CELs?

Thanks,
Matt

Enginuity does.

Sorry for my newbness.
But where and how?
I just downloaded the latest release Ver 0.3.1b and ordered an openport cable. I can't find anything about CEL's. Does it only have CEL suport for the non-DBW ECU's?

TMS

You have to download your rom and then open it in the editing program. Enginuity has xml (the definitions that tell the respective programs what data is where in the actual ROM file) support already in it. eduEdit, you have to get xmlwrite and create the xml files for whatever respective rom you're editing. Yeah, I know it's cryptic... blame that on the programmers.

So once the ROM is in XML format, are you looking for the CEL code itself (in my case the P0420) or a description? And once you find it, what do you edit to turn it off?

<- Also a newb, but doing lots of reading and keeping this thread alive is good anyway!

- Matt

^^^ You need to read more. You don't convert the ROM to XML format. Think of the XML file more as a translator for what's inside the ROM file itself. I think Enginuity has checkboxes for CEL disable. I user eduEdit, so in that you just change the ranges of the sensor's limitations themselves. For instance for EGT you set the table values to 1000 and for O2 you set the table values to 65535. That's the basics of it anyway.

^^^ You need to read more. You don't convert the ROM to XML format. Think of the XML file more as a translator for what's inside the ROM file itself. I think Enginuity has checkboxes for CEL disable. I user eduEdit, so in that you just change the ranges of the sensor's limitations themselves. For instance for EGT you set the table values to 1000 and for O2 you set the table values to 65535. That's the basics of it anyway.
You can do the same with Enginuity, which has the EGT limit table as well as the 2-3 (depending on revision) cat threshold tables which have been setup up with check boxes to automatically enter the relevant minimum or maximum values. You don't have to disable the CEL directly if you don't want to, but some people still a throw a CEL so that capability is there if you need it.

I like how you don't have to just disable the CEL, and you can adjust it's parameter thresholds instead. This way if you had to get an emissions test, your ECU would not report a condidtion that would cause a failure of your test.

IIRC, the ECU will not go into a "ready state," if you just disable a CEL, which is an automatic fail.

Well any of the tuning programs have the potential to adjust the thresholds. It's all in having an XML setup to do it.

I do not think all the programs have checkbox on/off CEL capabilities.

Well any of the tuning programs have the potential to adjust the thresholds. It's all in having an XML setup to do it.

I do not think all the programs have checkbox on/off CEL capabilities.
The check box feature has been added recently to Enginuity and is editable within the xml. All it is doing is making it easier for the user to set up the thresholds, without having to know the values. So, with one of the cat threshold tables, which is a maximum value, clicking on the check box will automatically put in the maximum value (0xFFFF) which is what tuners use to raise the threshold to such a high value that the CEL will never be tripped. Unchecking the box puts the original stock value back in. These threshold tables might not prevent all CELs, so the cel fixes are in the current ecu definitions that will allow you to disable particular emission CELs (same check box feature), although this may not fix the "not ready" state caused by some CELs.

This is soo interesting, i am lookin into this further because i am in the process of installing a ej257 bottom end in my wrx and know its not gonna run up to par so this would be a good way to help out a little

You can also remove any CEL using just a HEX editor and the ROM file, I removed the EGT and rear o2 CEL by overwriting offsets in the binary.

G.

The stock O2 is actually fairely accurate down to 13.5 or so from what I've seen.

Below that, it starts reading rich, and doesn't read any lower than 11.25:1 or so (you'll know as it will flatline and not read any richer), but by that time it could be a whole point off.

Here's a great thread on IWSTI about it: http://www.iwsti.com/forums/showthread.php?t=36914&highlight=accurate

So if the stock sensor reads 11.25:1, you can be somewhat certain that the motor isn't any leaner than 12.25:1 or so.

Looking at those logs, it's hard to tell if the stock w2 is reading rich or if the wb02 is reading laggy. It's a shame he wasn't logging injector DC too so we could tell which it is.