What are the codes you you all getting for the O2? I decided to not put a bung in my test pipe for the O2....so it's under the car covered up, taped up and protected but not in the test pipe. I don't get any CEL's except when tracking the car and going ***** out and it's just a no activity CEL....so I don't have to deal with annoying CEl's all the time.

 

the o2 CEL is for low voltage in the secondary o2 sensor. I have a test pipe with a built in CEL fix from ultimate racing. The only time I seem to get these CELs is if I either downshift and stomp on it in 3rd gear and above. But I've only noticed this since the weather got significantly cooler as well. I dunno...

 

Ok, this is something I am interested in. I just want to be clear.

Are we , for the most part, able to operate the vehicle with the stock secondary O2 sensor out, and possibly a wb02 sensor in it's place without receiving CEL's?

I would love a way to monitor a:f with a Wb02 and not resort to a drilling and welding a bung onto the exhaust or test pipe.

Do we have the capability to disable this check in Ecuflash yet?

 

^^^ was wondering the same thing, I was planning just going with a test pipe and getting 3 bungs put into it.

 

Not sure if you are ale to use a WB over a NB....but because the WB would be further down the exhaust system it may not be as accurate as welding a bung to the DP for the WB. The closer to the engine the more accurate.

 

Assuming there is no cat on the car, then placing the sensor further down the exhaust is less accurate only in the sense that there is a longer time delay between the ignition event and when the exhaust pulse reaches the sensor.

 

So... if we could put a percentage on how far along ECUflash is to completion, what might that be??????

 

The only thing holding up release is that some people who have gotten their hands on the betas have bricked their ECU. Tactrix wants to find a solution to this issue before its released.

 

Sorry all. I believe he's talking about me.

 

^ rofl!

 

Here's a few ways to prevent ECUFlash from bricking ECUs:
1. Have ECUFlash disable screensavers, sleep mode, etc. when the program is in use.
2. Have ECUFlash check if the cable is connected to USB 1.1 or 2.0, disable the use of USB 1.1.
3. Have ECUFlash force Exit Programmng State whenever there is an error while flashing.

 

It doesn't help that you (who shouldn't have had it anyway) keep giving it out to unqualified people that in turn brick more Ecu's......

 

I do not understand this statement. The whole point of open source is to have ordinary people flash and tune their cars. The point is not for ONLY professional tuners to use it to make a buck.

A lot of Subaru owners are using the 2.0 cable and the 1.40 release to tune their CAN based STis and WRXs.

The problem is in the implementation of the software for the Evo X and not with the user. I do understand that the software is not ready for release. And I commend Colby for not releasing it until the ordinary person can flash their car w/o bricking the ECU.

 

And it wasn't released to RIcer X1, by colby.
Ecuflash 1.41 isnt public yet because of these issues.
Ricer happen to get a copy and has proceeded to brick his ecu and give it out to more people who have in turn bricked more ecu.....

What dont you get?

 

From what I was told was that the version I used to flash my Evo X MR is not compatible for MR ECU. So its probally just a few minor details to work out so the software can be happy with MR and GSR.