Hi guys,

Interesting reading. It's good to see the conversations start after a thread I started, maybe my question was so dumb after all

Here is what has happened in the last day or so. I had a customers car that when started "cold" was lean. Ran like crap for a few minutes. I needed the cold start tables for the 0008 rom. I found them, patched them into my xml. Now, I am stupid when it comes to this stuff but thought I was getting the hang of it.

I then opened his ROM in Ecuflash and NOTHING. No cold start enrichment tables. So I go back and look and sure enough they are there. What is interesting is so are the Tephra mods and the MUT tables and some other things. None of them showed up. Nothing after the 4th periphery table showed up. So I cut and pasted it up further in the rom, instead of the end, still nothing. Then I took my non computer brain and tried to see if something wasn't written write in the xml, nothing. I then sent it to my secret helper, who I am quite confident is one of the best in the industry, and he said the xml worked for him. He modified and it and sent it back, same thing, I can see nothing. Well after investing about 4 miserable hours in this project I was so pissed off I was going to refund the customers money in full and tell him to find a real tuner.

This morning I asked this helper of mine if he had one last suggestion for me. He suggested I take Evoflash out of my computer completely and do a fresh install on it. I figured that wasn't going to work. I then just gave up and put my fully modified 0015 ROM into the customers car and fixed it, done deal. I should have done that in the first place.

Then tonight I was laying on the floor at my house and I remembered that since I have been using my new laptop, occasionally I get an error telling me an inproper address or something has been found and wants to know if I want to correct it, I click yes and continue. It hit me then that my helper was right. I copied my EVO romdata file to save my modified xml files, deleted the rest of Evoflash and then did a fresh download. I then cut and pasted my modified xml's back into the new rom directory and HOLY CRAP!!!!! It all worked perfectly.

Something must have gotten corrupted when I first downloaded V1.41.

I am HOPING that from now on things will go much smoother.

BTW, I had asked about the "universal" roms before. I am using basically three roms now for 03-06 cars. I have not had a change to build a good complete 2005 rom yet but have the others.

I know I am a low guy on the totem pole but if it would help I'd give up the stuff I have worked on.

Who's the big dog in all this, Tephra? Mr Fred? GST? Mr Turco? Why don't one of you just make the call to which ROMs become universal and post those 3 roms up with as many mods as you can get in them. Then the rest of us can start trying to use them and give you guys feedback. Eventually if no other support is provided for all the other ROMs nobody will bother with them It makes absolute perfect sense to me.

Thank you all for your help. If someone posts up the ROM's post the link and I'll give them a shot. Hell I'd make a donation for it, it will save me hours upon hours.

Thanks again.

 

This place is more like a herd of cats than something resembling a hierarchy. :-) Here's my take on the universal ROM discussion (probably the same was what I said a month ago or whenver it was)

USDM Evo 9: 88590015 has been the standard, but I'm a little curious about whether a JDM ROM can be used. There are a few nice things about the JDM ROM. First is that there is less OBD-II crap. Second is that it has support for antilag control. However, I don't know how well the JDM ROM will get along with all the USDM emissions hardware, and I don't know whether it could pass emissions testing.

'05 USDM Evo 8: 96530006 seems to be the popular choice because it has room for all of tephra's mods. It lacks antilag support though. Perhaps there is a better choice?

'03-'04 USDM Evo 8: There is a push to find a universal ROM for these cars. The final ROM for these cars is the 96420011. It should work with all the USDM Evo 8s. There is some interest getting the 96530006 working with the '03-'04 Evo 8s, but I wonder whether the 96530006 needs to be talking to an ACD controller (that the '03-'04 Evo 8 does not have). I know there is a communication wire that goes between the ACD controller and the ECU, and the FSM wiring diagram indicates that the information flow goes from the ACD controller to the ECU. So the ECU does take some input from the ACD controller. One other possibility is to use a non-USDM ROM. The benefit again would be less emissions crap and having antilag support.

 

I thought the ACD/ECU wire was for TPS?

jcsbanks and myself were hoping 8857008 was going to work over 88590015... no one has tried it yet...

 

TPS feeds into the ACD controller, but there is a signal that goes from the ACD controller to the ECU. (The FSM wiring diagram definitely shows signal flow from the ACD controller to the ECU.) There's no info that I found about its purpose, but at the end of the ACD section of the FSM, I found a pinout table where its called an "Idle Switch". It apparently depends at least on TPS, and may depend on other ACD parameters. Would be nice to know if it connects to an ADC input on the ECU. There is one unaccounted ADC input, ADC_4D. Its used by the ECU, but not sure yet how. The subroutine where its called is pretty long, and I haven't had time to look at it in detail.

 

I thought a while back people who were logging and switching the ACD to the different settings were noticing it pulled timing etc. So that would be fed to the ECU somehow right (which setting the ACD was on)? Or am I way off-base?

 

On 2G DSMs this Ecu pin, is the "Idle Switch". Just an additional signal from the tps sensor when throttle is fully closed. Evos don't have them, they use the tps ADC Signal to calculate if the throttle is closed.
When using an evo ecu in a 2g, you just cut tis wire.

 

The information that I posted about the Idle Switch is straight from the Evo 9 factory service manual. No guesswork here. The Evo 9 FSM says that the "Idle Switch" output signal from the ACD controller will vary with TPS, and this signal feeds into the ECU.

 

Yeah sorry to ***** up your thread Dave.



Looks like you had a similar problem as me with an ecuflash install getting buggy, and things on the computer just not playing well in the sand box.

I don't moonlight as a technical / computer genius either. Which is why I normally back everything I NEED up, and then just wipe things out. Then start over fresh.

 

asmodeus6, no apology needed. I was serious. I'm glad there is a conversation about this stuff going on in this thread.

I am using the 94170015 for 03-04 roms and 88590015 for EVO9's. I have not built a good modded ROM for the 2005 yet because I haven't needed it yet. I'm using those two ROM's because so far they seem to have the best support. Both working very-very well.

I appreciate your input Mrfred.

 

David,

Eventually with the Tephra edits you will only need one ROM for any EVO8. The one that has been working on all EVO8's that we have been testing is 96530006. Tephra version 7 edit changes that ROM to 96530706, the 7 for version 7. I have run this on many 8's from 03 to 05 without any problems. Check out the thread towards the end and you can see we are just about done testing v7 and it will be released.

https://www.evolutionm.net/forums/ec...6-testing.html

Tephra releases the 9653 ROM, I take it and make it work for USDM EVO's that wish to run his edits. Go to the last page for updates.

~Zach

 

Dave I'm an 05 VIII. And I initially had my doubts, but coming back to this since I posted what I did, I already have 96530006 on the car. (Actually 96530706 which is the newest patched 96530006 rom Version 7.6)

As Phenem said, this is moving to be THE VIII rom. I would duck into that thread, grab the rom, and the xml he was nice enough to supply with Mrfreds ecu based boost control tables already in it.

You can literally point the immobilizer at the right address, (switch it to the correct one from the previous rom.) Paste your stuff in and go. This guy has really put in most of the hard work for everyone.

He saved me a hell of a long time fiddling with xml files.

I jumped on the evo wiki, and if you look up 96530006 it will show you all the MUT addresses for 2 byte (4 load, rpm, airflow) Punch it in, and bang your up and logging now too.

 

As far as logging goes 2 byte load is no longer, Tephra has incorporated that into his 1 byte load calculation and uses a multiplyer to reduce the size of load below 255 so it fits into 1 byte then he multiplies it by the multiplier once you log it.

Below is the EVOScan data you need to add in order to log on the v7t6 ROM:

Notice on the 1 byte load value the EVAL is 1.3x, this will allow you to log 2 byte load up to 331.5 (1.3 * 255), so if you need to log load higher than this just increase this value in the 2byte to 1byte load factor in your ROM and in your EVAL statement to 1.4 or 1.5 (357 or 382.5) respectively. Just remember the higher the factor the less resolution you get because of squeezing all of that into 1 byte. This will help logging speed as well cause you are doing the processing outside of the ECU and less requests go to it.

That's really all you need to log, 2 byte RPM is really not needed. It just slows down your logger anyway.

You do not need to edit the v7t6 MUT table at all! Just plug in the important data and use the data above to plug into your EVOScan data.xml file and you are set!

 

Maybe I missed the answer, but how do I convert my 94170008 to the 94170015?

Can I get a walk through? Thanks.

 

for this rom, all you need to do is copy/paste the Immob. over, along w/ the important maps, of course.

ALL roms tht start w/ the same first 4 digits, can be swapped out for a newer version of the same rom...
(ex.) 94170008, can be upgraded to 94170015,
(ex.) 88590014, can be upgraded to 88590015