So basically, one just locates the appropriate scalings in the "scaling_20091012.xml" file and replaces them with the ones here that correspond to his MAP sensor?

 

Launch mode is disabled
Valet Mode is disabled
Map switching is disabled (for now)

Will flash the car now with this and do a log while idling and then try to rev it up.

 

nice job chief!

 

Not so sure this will help....

AS the car revs up and the misfire starts/relay chattering, Evoscan losses connection and then it re-connects.

anyway file attached

 

Good work everyone.

 

WTF - why is evoscan restarting???!?!?

Sean send me the ROM

@gmail.com

 

All of the MAP sensor scalings will eventually be preloaded in the v7 XML's for you. I will make a thread on what to switch in which tables for anyone switching from the factory LOAD based boost control over to the PSI based boost control. It will be as easy as 1,2,3 when I'm done.

I am working on re-arranging the boost control tables and also graying out the unused tables that are no longer used with v7 so no one accidentally adjusts some of the 'old' tables (to prevent people from pulling their hair out and looking like this ).

Does anyone know the address for "Max Total Downward WGDC Correction" for 96530006??

 

Jamie - yeh im doing the greyed out thingy for the next ROM I post up.

But I still want to keep all the new/modified maps in the tephramod menu...

 

Sent

 

With the separate v7 XML I don't see the need. That section is REDICULOUSLY over filled now and needs some separation IMO. I'll show you my 'idea' before we do anything with it.


Also, is there a separate FUEL CUT LOAD for the standard maps and the alt maps or is there just one? It wouldn't make sense to have just one since one maps will generally have higher loads than the other. Maybe I missed something but it looked like they used the same address?

 

Good boy. I prefer pressure (psi) based control, and I'll bet many others will as well.

I vote for graying out or removing anything we don't need to see or alter, for the sake of simplicity and avoiding confusion.

 

I don't know of a trick on how to have a table not show up AT ALL thats inherited from the base or original ROM ID xml but I do know that if I were to add the SAME table to the v7 XML and leave out certain ifo, it will see it as incomplete and gray it out. I'd prefer to hide them completely but IDK of any trick to do that. Anyone else know of a way?

Also, whats te best way to gray them out?

 

Any possibilities of adding the adjustable closed loop AFR cruise in to a prepackaged tephra mod?

 

There are posts about this all over. You want to disable the CEL, but leave the periphery bit for the system enabled. MrFred has posted a different bit to disable the system.

Did you try removing power from your ECU to make sure there was nothing latent in memory that could be causing your problem? I believe it is recommended to remove power after a major reflash, especially when switching major rom IDs.

I will try to make a version of each of the ROMs when V7 final is released for the IX (as I have with v5.10, etc). I'm not sure that patch is even available for the VIII

 

I haven't looked at any of the XML files posted in this thread, but since I have been working on porting over the DMA/LiveMap to this ROM, I have started organizing the tephramod definitions into the following categories:

TephraMod-V7 (for options and config)
TephraMod-V7 AltMaps
TephraMod-V7 LaunchMaps
TephraMod-V7 Stock Map Replacements

Not sure if this is basically what has already been done, but it helps 'clean up' the organization when viewing in ECUFlash. It separates all of the config/setup tables from the tuning maps.


Eric