No problem, YaroRS. Please note my edit 2 posts above. BTW, it's pretty cool that we can share this info across continents on here!

 

I adjusted VE ratio by monitoring fuel trims for iddle (load around 30) and cruise (load around 50). Everything was fine, trims are within 1%. Later on that day my engine went mad. After cruising and switching to neutral AFR falls to 19-20, revs drop to 500, then the engine tries to stabilize it (switched to MAF - no problem at all). Any suggestions how to make it stable (car is stock evo8). Using closed loop for iddle and cruise, ignition and afr maps unchanged

 

I tried SD v7 rom and I am having a bit of trouble. Manifold Air temperature (connected to fuel temp input, pin 77) logs for some reason as 3A request, not 09 as it supposed to be, and 09 request shows some rubish. 3a request doesnt work correctly. It shows -7 when the temperature is +4, when it is +8 it shows in evoscan 0 degrees celcius. Checked the impendace of the sensor and it correct, so the sensor is working. Checked the voltage coming from ECU and it is 4.7 volts instead of 5. (To figure out what sensor shows temperature I disconnected the plug from MAT sensor and the temperature droped immidiately to -65 degrees)

Guys, can you help me with this ? What have I done wrong ? Anyone having the same problem as me ?

 

Check your MAT scaling table, it might be scaled improperly.

 

has anyone got this mod working on 2004 Evo 8 EDM ?

 

I'm having issues logging my GM IAT sensor since converting over to V7; I'm logging via MUT09 and the temps say 17* F in EvoScan and don't really move (ambient is 50*F). Are the V7 SD MAT tables pre-populated w/ the correct scalings and information? There's only a few of us who have tried V7 w/ SD so I'm wondering if all the bugs haven't been worked out yet. The car also idles very rich w/ the same settings I was using w/ 94170015.

 

Bring the issue back up that l2r99gst noticed.

On 96530006, the RPM VE table replaces an old table at 337c and an old axis at 65f6.

I'm not real familiar with the patch, but is there any chance that these tables are actually used under certain conditions and this is where the IPW drop out is coming from?

Seems like moving the table to a known unused area may be at least worth a shot?

 

The table and bit of code associated with it are used to calculate the MAF clip value. jcsbanks used this subroutine and table as a means to hook into the MAF control code. He eliminated the MAF clip code and then forced the MAF control code to always use the MAF value from the modified subroutine.

 

The other option perhaps is to hook in and replace the MAF much earlier.

 

What does the MAF clip value do originally?

I just noticed that the (MAF Clip) table was replaced by a speed density table and wondered if maybe there was a certain condition that may allow the code to jump around that subroutine and it was causing the IPW drop out that has been noticed.

 

The subroutine compares the actual MAF value to a value from the MAF clip table (vs RPM). If the actual MAF value is higher than the value in table, then the value in the table is used. Its discussed in the "maximum load thread". jcsbanks eliminated the code that allows this subroutine to be bypassed.

 

IM trying to doenload these links and they do not work so im having a hard time getting the xml for ecu flash https://www.evolutionm.net/forums/ec...tructions.html

 

My server went down over the weekend due to a power outage. I'll be back online late this evening.

 

thanks you're the best

 

Anyone able to log correct MAT figures w/ V7? If so, give me some advice on what I'm doing incorrectly. I'm using the default Fuel Temp ADC for my GM IAT.