Teaser Pics of the Definition:

 

UGH... Im excited... I hope Merlin gets mine done before his vacation... lol

 

Update. Received my definition file from Merlin over the weekend. Got them into ECUflash and opened up my current ROM. Holy Mother of Tuning!!! There are so many options. I have even more options than Brent's shows. Mainly because of all the Automatic Transmission controls. This is intense. Oh and what Brent's screenshot shows is only the tip of the iceburg there are so many options within each of those headings. I can only hope to be able to understand everything in this some day. Merlin is a genius...

More updates to come. I am going to log my current rom soon. Then I'll get the word on when to try the new tune. Im so excited!

 

Good Day all, I'm not sure if this is the correct forum but, here goes. I have an evo 5 rs and had someone assist me some years ago to tune it using an evo 8 ecu and patch cable. It worked ok. However I am attempting to do some tuning for myself and noticed that my ROM ID is 99270000 and I am not able to find the MUT load 2 byte address for this rom.

I read that some people replaced this ROM with 96530006, unfortunately the car does not start. Is there a step by step guide to assist me with this ROM change?

Thanks

 

For the Evo 1-9 you can check in These Boards and see if they can help you out. This section is actually for the Ralliart. So the guys in that section will probably be much better suited to answer your question.

I hope you get it sorted out! I would love to own an Evo 5 some day... Its my dream car. lol

 

Thanks Bakuro117

 

Transmission tuning for the AT very NICE!!!!!!

 

Yea its awesome. I cant wait to play around with it more. I attached a screenshot of my ROM metadata and all the fields it contains. It shows all the transmission options near the bottom. But within all of those fields is MORE THAN 170 tables of information that can be edited however you see fit. This is full control. I am absolutely stoked to get cracking on this now. This totally blows the top off of what I was expecting to see when I got my definition file.

 

I made the same post on another Forum that is Eclipse Specific. I feel you all should know as I am working with a couple of members from EVOM to fix this issue:


I have been working with 4 members form this form and EVOM (names not being published for privacy reasons) to help them fix their ECU. Based on the above information that is NOT accurate these members have tried to read and write to their ECU using ECUFLASH and it has not gone well.

Here is what has been happening:

1. Read the ECU save the File as a 512K of 768K (whatever your ecu happens to be)
2. The customer sends the file to me I get Merlin or Acamus to build a definition.
3. I send the tuned file and definition back to the customer.
4. Customer writes the file to the ECU tries to start the car and the car won't start.
5. After some diagnostic time (free of charge) I find out the customer is using ECUFLASH.
6. Customer reads the ECU and sends the file. After looking at it in HEX we (myself and the local person helping me out) find the same section missing that does not get written, thus bricking the ECU.

The local person helping me out will be re-testing the bench procedure, double check for accuracy. (I do not have a bench set up to test)

*Ecuflash will read the ECU no problems. I have confirmed this*
*Ecuflash will leave out a section when a file is written to the ECU. Again I have confirmed this (OBDII port only for now, bench test to be confirmed)*
*ALL FILES WILL WRITE TO THE ECU AND APPEAR THAT THE WRITE WAS GOOD BUT THERE WILL BE A SECTION LEFT OUT*


*PLEASE DO NOT LISTEN TO HACK THE INFORMATION HE PROVIDED IS NOT CORRECT*

If you have any questions please email me I will be glad to help. No question is a stupid question PLEASE just ask.

Here is the Exhaust and Performance Company Email I am now working with:

XxxclusivemotorsportsxxX@gmail.com

Again if you have ANY question please just email.

I would love for ECUFLASH to fix this issue then the tuning process would be much cheaper. I am not out here as a honk for mmcflash I am only using it as it is the only method that works properly.

 

"*PLEASE DO NOT LISTEN TO HACK THE INFORMATION HE PROVIDED IS NOT CORRECT*"

What information is he providing?

 

You can then read the ECU using the profile for Colt 768k. If you have a MT car and you're positive it should be a 512k file then just lop the end off in a hex editor. I have used ecuflash many times on the bench to read and write ECUs so I know it works reliably.

I don't have much time at the moment but I'll try to make a video to detail exactly how to do it.

-Michael

Post #39. Here is a follow up I posted on Clug4G:

Update:

My imaginary friend did the bench test last night and here are the results. Using ECUFLASH

8303(768K) Lancer Read with ecuflash write not complete
8202(512k) Lancer Read with ecuflash write not complete
8302(512K) Eclipse Read with ecuflash write not complete.

The result was the same VIA the bench or OBDII the same section left out.

Both ECU are from a Lancer 2005 RA 8202 MT and 2006 RA 8303 AT. There is are some consistencies 512K are MT and 768K are AT.

All Eclipse 2009+are full CAN-BUS and are 768K processor should be 8304. All of this is very consistent with mmcflash.

The more ECU we acquire the more testing we can do. I would like to test ECUFLASH on a 2009+ Eclipse Anyone with a 2009+ that has a Tactrix Cable shoot me a PM or Email I just need you to read the ECU.

Conclusion: 2006-2008 There are too many inconsistencies to use ECUFLASH Safely. Testing needed to be done on a 2009+(Eclipse)

I had a few ask me what tech support needed for mmcflash and uvtune/fastworks. I can't comment on fastworks i never used it nor will I but I am pretty sure the recovery process will be the same or close. From using both systems this is what I know:

uvtune/fastworks: the file being flashed is aprox 186k. I believe this was done to speed up the write process (actually a very good idea flash time less than 2 mins). Issue now is you need a recovery file/tech support if something goes wrong. Bigger issue tech support time is inconsistent. When tech support is there it is fast and very good. (I can be objective and give credit where credit is due) if tech support is not available wait times are unknown, I waited to 2 weeks at one point other times less than an hour, regardless it was inconsistent. If this recovery process has been reworked in the new upcoming release i do not know I am just stating it as it is now from my experience with uvtune. Disconnecting the battery or the ECU may be required.

mmcflash: Flash time is about 5-6 mins, the program does a complete erase and a full 512k or 768k write what ever your ecu is. Tech support not needed for recovery you just need to know how to do it. If after a write and the car wont start (it does happen from time to time
) unplug the ecu (if that is nightmare on the Eclipse) then disconnect the battery and pull the ECU relay (may not be needed but I did it anyways just kills ECU power faster) reconnect battery and ECU relay write the file car will start. So far this has worked every time, again no tech support needed. Time to fix this approx 10 mins with no tech support needed.

 

@Mike - The quote from Ott's post. Michael/Hack told a few people that they dont need MMCflash (or FastWorks for that matter) to reflash the car. Which right now is untrue unless he used a tweak/mod/diagnostic mode when he was using it on the bench. But in the car only MMCflash will fully write the rom/hex files back into the ECU.

And sorry for not updating this on my progress. Ive been consumed with finishing the Eclipse. We had been dialing in the tune to get rid of some knock. Now we are trying to fix a low spot in the powerband right around 4000rpm. I have a file ready to test, if all goes well I plan to attempt to rebuild my stock rom then do a before an after of the improvements.

 

@Josh & @Ott: hey guys, thanks so much for the updates! i really appreciate all the work that you have all been putting towards our RA community. also want to say that i am looking forward to the results that your fruitful research will be bringing to our tables. i am amazed at the contributions that everyone is able to put in to further advance our knowledge on the first gen RA. it's just mind-boggling! i just hope someday i'll be able to give back to this community. i try to help by giving some basic advice but that's about it for now. i'd love to be part of some kind of test! that would be amazing!

 

Brent you surprised the crap outa me !! Not only are you bashing your competion to try upsell yourself.now your telling everyone not to listen to him ? Wtf man ! Does he come and start bashing you ? Or telling people to stay away ? That's bad biz !! Maybe you should close the thread and start a new one when you actually have something that works. I know the people who are doing all your work will figure it out and get it working. Just please stop bashing hackish not only here but also in club4g.org. Get your stuff together and come back when it works

 

Actually, it sounds more like he's trying to warn people that it's incorrect to use ECUFlash with the RA and certain models of 4G, and that they'll brick their ecus. Hackish is telling people it's possible, but it is not. How is that bashing?