Actually no we don't know where you got it from as according to the post on the beta forum you wouldn't tell the informer who you got it from.

Please lets keep the posts in this thread more towards the more truthful, educational and informative types of posts about EcuFlash.

That said, expect a large update on post #1 soon...

 

i hope w/ all my being is a release date i hate to see a paper weight in my desk

 

Back on topic and yes we got our authorized copy from a heavy poster within this very thread.

 

If you were a member of the beta forum and working with the developer on a daily basis, then it seems reasonable that you would have not made your post about another bricked ECU because you'd know that the developer has engineered a way to recover a bricked Evo X ECU.

The bottom line is that flashing the Evo X will likely never be as forgiving as flashing an Evo 7/8/9 by virtue of the method required to flash an Evo X ECU. People will actually have to watch what is happening during a flash and know what recovery action to take should a flash fail part way through. Its unfortunate, but its not the exception. The Subaru community is in the same boat. Colby has a recovery package for Subarus with bricked ECUs, and he'll likely have a similar recovery package for the X.

 

That is good to hear. Are you speaking of the "attempt another flash until successful" method or something else?

No mention has been made to us that these bricked ECU's have been salvaged, but it would be nice to know if that was the case.

 

i sense a disturbance in the force

 

Its a new method. Colby hasn't said whether it will be a fix that can be distributed to end users or whether a bricked ECU will have to be mailed to Tactrix.

 

ROFL....really u feel that too?

Well this thread got mmm, mmm, mmm, toasty. In the last page alone. Sad news that another ECU got bricked. How is this happening to certain ECU's and not others. Bryan I take it you haven't had this problem with the beta testing on customers cars. So what is going on? Are people not paying attention? And I thought when a flash failed, if you exited programming mode and reflashed you were fine. Are people panicking and making things worse?

 

all i know is, everyone should stop hounding for a release date, if your interested in the software, really truly interested in the software then there are hundreds of posts by guys like MRFred, Razorlab, JohnBradley,MalibuJack, and others in the evo 1-9 ecuflash subforum, dont clutter this thread asking questions like how to force open/closed loop conditions or if you should buy a wideband.

i have a legit question for razorlab or any other beta-testers out there...

i had read in an earlier beta thread that you can keep throwing timing at the X and not get knock (obviously not cause its not registering just cause its a good engine), so its dangerous to road tune since if you continue throwing timing at it past peak torque (dyno needed) youll eventually lead yourself to throwing a rod thru the block

is it true that this car will just keep taking timing without an overly large amount of knock?

is there any truth to what i had heard, or complete BS feel free to flame if it sounds ridiculous

i know the X can run a substantial amount more timing then all previous evos, due to a number of things, including better head design, heat dispersion, dual mivec, etc

 

We actually had a ralliart fail a read from ECU and it would not start. Though reprocessing additional requests it reset the ecu and it was back to normal. Without the program trading info with the ECU at the end of the flash process, the ecu is not in a position to start the car.

I haven't saved the exact exchange of info, however it is at the part where the VIN number is taken from the ECU that needs to go through 100% before the car will start again.

 

The Evo X WILL PULL TIMING, however one of the larger risks of the car are the extreme high EGT's that will deteriorate the turbine blades and turn it into shrapnel. There are a number of both shops and regular members on Blouche Dominators and EvoX Red turbos because of this.

We are currently monitoring EGT's and using water injection to cool the exhaust temps.

 

Funny how you say to not clutter this thread with how to force open/closed loop conditions, which is ECU based and thus relevant in this thread I do believe...when all your question regarding knock are all engine based question that could be asked in an entirely separate thread?

 

Well I heard fail to read is easy to escape and recover from. Simply after the failure command the escape programing mode, correct? But it's writing and fails that I hear are bricking the ECU's. So I'm guessing a write failure is permanent unless Colby can fix it. Where read is temporary until force of exit programing.

 

my question was directly relevant to the X and its tuning, not a subject that has been covered a billion times and if that button we have all known and come to love was used, you might already know the answer too

another directly related question

what program (if available to the general population) is/can be used to log for the X, i know evoscan in its current iteration cant be used (or doesnt say it can) since a few guys around here have modded X's

also since the X comes with the same MAP sensor as the JDM 9 does that mean it is also capable of logging boost?

 

Then why ask your question in a ECUFlash thread? What exactly does your question have to do with ECUFlash? Couldn't you have asked in an AP, ECUtek thread? My questions were asked becuase I plan to self tune. And I ask here becuase Bryan constantly updates us on his progress, and understanding of what the maps in the new X ECUFlash mean and do....

BTW, use the search button. As data logging has been cover many times in regards to the X....