94170715 V7 Issues
Feb 7, 2010, 10:22 AM
#1
Evolved Member
Thread Starter
iTrader: (19)
Join Date: Oct 2004
Location: CT
Posts: 885
Likes: 0
Received 0 Likes
on
0 Posts
94170715 V7 Issues
I am pleased that this rom is available so no bad kharma.
But...Ha
The MUT requests that were in the 9653 rom are not working.
In particular I am interested in the following.
MUT40 = 1byte gear
MUT42+MUT43 = 2byte SPEED/RPM ratio (to get your gear ratios correct - if you need to)
I also think that the following are not correctly configured in the MUT table
MUT00+MUT01 = 2byte airflow (ie MrFreds mod in g/s or lb/min)
MUT02+MUT03 = 2byte airflow (ie MAFHz)
I put the following addresses to get the 2byte arflow MAFHz to work correctly
MUT02=89BA and MUT03=89BB
I also noticed that the Max WGDC vs coolant temp address is off in appauldd's xml. Anyone know the correct address? It is currently 56D2.
But...Ha
The MUT requests that were in the 9653 rom are not working.
In particular I am interested in the following.
MUT40 = 1byte gear
MUT42+MUT43 = 2byte SPEED/RPM ratio (to get your gear ratios correct - if you need to)
I also think that the following are not correctly configured in the MUT table
MUT00+MUT01 = 2byte airflow (ie MrFreds mod in g/s or lb/min)
MUT02+MUT03 = 2byte airflow (ie MAFHz)
I put the following addresses to get the 2byte arflow MAFHz to work correctly
MUT02=89BA and MUT03=89BB
I also noticed that the Max WGDC vs coolant temp address is off in appauldd's xml. Anyone know the correct address? It is currently 56D2.
Feb 7, 2010, 10:53 AM
#2
Evolved Member
Thread Starter
iTrader: (19)
Join Date: Oct 2004
Location: CT
Posts: 885
Likes: 0
Received 0 Likes
on
0 Posts
For those who want to log 2 byte loads
2byte load raw = 895C and 895D
2byte load + baro compensated = 8960 and 8961
2byte load + baro and IAT compensated = 8962 and 8963
The load for afr is raw and timing is baro-iat compensated
2byte load raw = 895C and 895D
2byte load + baro compensated = 8960 and 8961
2byte load + baro and IAT compensated = 8962 and 8963
The load for afr is raw and timing is baro-iat compensated
Feb 8, 2010, 10:53 AM
#6
Frankly, I need a good 9417 base file (that is 94170015 and evo_7_base). From what I can tell from tuning the first 03 I've been in this weekend the evo_7 base and evo_7_base_new are both junk in v1.42.
Does anyone have a well compiled and clean set of those two XMLs?
Does anyone have a well compiled and clean set of those two XMLs?
Trending Topics
Feb 8, 2010, 02:52 PM
#8
Replied back with a little note 
Has anyone gotten this rom to work with the map tracer?
I get an "object reference not set to an instance of object" every time I try to do anything with the 94170715 V7 rom, but thats the only one. My 88590715 rom and the 94170008 rom work great, as well as the 94170015 v5.10 rom.
For some reason I can't even get evoscan to try to open it. I've tried the usual
-cutting it down to the scalings and the maps
-setting to unix file type
-copying my working 88590715 xml that is cut down and changing the map addresses.
The error seems to happen even when there is no xml for that romID in the directory (when it would normally allow you to select where the xml is) so I think it may be some incompatibility with the ROM. I even went as far as to verify the romID in a hex editor at 0x0f52 !
Working in evoscan v2.6. Any help would be appreciated....
Has anyone gotten this rom to work with the map tracer?
I get an "object reference not set to an instance of object" every time I try to do anything with the 94170715 V7 rom, but thats the only one. My 88590715 rom and the 94170008 rom work great, as well as the 94170015 v5.10 rom.
For some reason I can't even get evoscan to try to open it. I've tried the usual
-cutting it down to the scalings and the maps
-setting to unix file type
-copying my working 88590715 xml that is cut down and changing the map addresses.
The error seems to happen even when there is no xml for that romID in the directory (when it would normally allow you to select where the xml is) so I think it may be some incompatibility with the ROM. I even went as far as to verify the romID in a hex editor at 0x0f52 !
Working in evoscan v2.6. Any help would be appreciated....
Feb 8, 2010, 03:12 PM
#9
Replied back with a little note
Has anyone gotten this rom to work with the map tracer?
I get an "object reference not set to an instance of object" every time I try to do anything with the 94170715 V7 rom, but thats the only one. My 88590715 rom and the 94170008 rom work great, as well as the 94170015 v5.10 rom.
For some reason I can't even get evoscan to try to open it. I've tried the usual
-cutting it down to the scalings and the maps
-setting to unix file type
-copying my working 88590715 xml that is cut down and changing the map addresses.
The error seems to happen even when there is no xml for that romID in the directory (when it would normally allow you to select where the xml is) so I think it may be some incompatibility with the ROM. I even went as far as to verify the romID in a hex editor at 0x0f52 !
Working in evoscan v2.6. Any help would be appreciated....
Has anyone gotten this rom to work with the map tracer?
I get an "object reference not set to an instance of object" every time I try to do anything with the 94170715 V7 rom, but thats the only one. My 88590715 rom and the 94170008 rom work great, as well as the 94170015 v5.10 rom.
For some reason I can't even get evoscan to try to open it. I've tried the usual
-cutting it down to the scalings and the maps
-setting to unix file type
-copying my working 88590715 xml that is cut down and changing the map addresses.
The error seems to happen even when there is no xml for that romID in the directory (when it would normally allow you to select where the xml is) so I think it may be some incompatibility with the ROM. I even went as far as to verify the romID in a hex editor at 0x0f52 !
Working in evoscan v2.6. Any help would be appreciated....
Feb 8, 2010, 06:57 PM
#10
Evolved Member
Thread Starter
iTrader: (19)
Join Date: Oct 2004
Location: CT
Posts: 885
Likes: 0
Received 0 Likes
on
0 Posts
After fighting with evoscan maptracer--using the above tricks--one of which I helped identify, I have given up on the POS. I do not give up easily either. I also use the excel maptracer...
Feb 9, 2010, 10:01 AM
#14
Evolved Member
iTrader: (26)
Join Date: Oct 2005
Location: Pittsburgh
Posts: 1,712
Likes: 0
Received 0 Likes
on
0 Posts
Replied back with a little note
Has anyone gotten this rom to work with the map tracer?
I get an "object reference not set to an instance of object" every time I try to do anything with the 94170715 V7 rom, but thats the only one. My 88590715 rom and the 94170008 rom work great, as well as the 94170015 v5.10 rom.
For some reason I can't even get evoscan to try to open it. I've tried the usual
-cutting it down to the scalings and the maps
-setting to unix file type
-copying my working 88590715 xml that is cut down and changing the map addresses.
The error seems to happen even when there is no xml for that romID in the directory (when it would normally allow you to select where the xml is) so I think it may be some incompatibility with the ROM. I even went as far as to verify the romID in a hex editor at 0x0f52 !
Working in evoscan v2.6. Any help would be appreciated....
Has anyone gotten this rom to work with the map tracer?
I get an "object reference not set to an instance of object" every time I try to do anything with the 94170715 V7 rom, but thats the only one. My 88590715 rom and the 94170008 rom work great, as well as the 94170015 v5.10 rom.
For some reason I can't even get evoscan to try to open it. I've tried the usual
-cutting it down to the scalings and the maps
-setting to unix file type
-copying my working 88590715 xml that is cut down and changing the map addresses.
The error seems to happen even when there is no xml for that romID in the directory (when it would normally allow you to select where the xml is) so I think it may be some incompatibility with the ROM. I even went as far as to verify the romID in a hex editor at 0x0f52 !
Working in evoscan v2.6. Any help would be appreciated....
I ported the evo7base xml into the 94170015 xml (taskes some time) and just linked the tephra rom with 94170015 and eliminated the link to the evo7base. Perhaps the 3 links were throwing it off in evoscan?
