YaroRS

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 ?

phenem

iTrader: (39)

Read through this post and post up there to see if they can help you: https://www.evolutionm.net/forums/ec...y-patches.html

Jack_of_Trades

iTrader: (17)

The 9563 rom works differently than the 9417 roms when it comes to MAP sensors. Since it doesn't use ANY MAP sensor data, we are just scaling input signal to get the proper readings in our tables for THAT particular sensor. The scalings are all correct for the popular map sensors in the new XML, just choose the scalings for your particular MAP sensor (omni 4 bar,omni 3 bar, etc..) in the tables pertaining to PSI based boost control and you are all set to go.

andrewzaragoza

iTrader: (6)

i'm in the same boat. i can't seem to figure out what was added. has someone done this? i have a custom maf scaling and i can't bring it in because of the adder. thanks in advance!

Appauldd

iTrader: (22)

MAF scaling was changed to incorporate the MAF sze in the numbers you see. Simply subtract 357.5 from the numbers you see in the MAF scaling table....you should look like your current table.

I made a quick accel spread sheet that I put all of my current scalings into...then I added to every cell 357.5. The output values then are put into the MAF scaling table. Too easy.

nano

iTrader: (1)

What table is applicable to MAF Scaling in v7? The only one close that I could find is MAF compensation.

Is there a table def I'm missing or am I blind?

Trinievo7

guys which of these can i run ... ? i got an JDM EVO 7 ... running a ralliart rom with some tricks ..to fuel, boost n speed ...

any help would be good ...

kaymin

iTrader: (11)

Uhm. So whenever ecuflash saves my V7 rom it changes it a 9694**** or whatever instead of keeping it in the same 965**** that all the evo 8s are supposed to use. So everytime I save, I lose all my tephra stuff and my maps and everything.. Makes no sense

Creamo3

iTrader: (48)

I'm seeing this same issue; I did a fresh EvoScan install and only added the definitions in the second post (MAT as well) and get the error. I'll see if I can troubleshoot it down to which XML addition is causing the error.

That reminds me; I should check to see if Maptracer works w/ the BigMaps.

andrewzaragoza

iTrader: (6)

thanks. but it still doesn't add up. looking at my stock oem rom it looks like this
19 145
25 152
50 165
75 175
100 182
125 187
150 191
175 195
200 198
225 200
250 203
275 206
300 208
400 217
500 222
600 226
800 233
1000 236
1200 237
1400 235
1600 232
while on v7 it looks like this.
19 357.4
25 366.1
50 382.4
75 395
101 403.8
126 410
151 415
176 420.1
201 423.8
226 426.3
252 430.1
277 433.9
302 436.4
403 447.6
503 453.9
604 458.9
805 467.7
1006 471.5
1208 472.7
1409 470.2
1610 466.5

SoCal Rally

Please post link to video. Thanks.

Slo_crx1

iTrader: (9)

Yeah I actually figured it out last night before I called it a night (was up until 12 digging around for the info only to find out they never had a map sensor...doh!). I didn't realize that the scaling that I added into the xml only changed the way the values looked so I could adjust them back down to match up with the load % values. I adjusted them down last night and flashed it onto the car first thing when I got home from work, went for a few logs and it works great now. So in a sense I was still running on the 3 bar settings, I just didn't realize it lol.

Now to tackle the rest of the VE tables and the asynch enrichment...it's gonna be a long night digging through jcsbanks SD thread lol.

Thanks guys, I appreciate the help!

Jack_of_Trades

iTrader: (17)

The MAF scaling actually has the 'MAF Adder' already added to the numbers( its not the MAF Size)...THEN it's converted to grams/sec. Whenever rescaling the MAF before, you always needed to add 140 (decimal value) to the (decimal)MAF scaling values before you did any calculations. If you wanted to remove 10% of fuel, you couldn't just make the value 10% smaller, you needed the first add the MAF Adder to the decimal value, THEN do the math. Now you can just add/subtract the actual percentage you'd like to change.

Its just like the boost tables. There is a 'Boost Adder' that needs to be added to the values in the boost tables to get the true boost level.


That scaling was actually from my own XML and I didn't mean to have it be added to the default XML

If you change the scaling to 'uint16' for the MAF Scaling instead of mine, it should read like the original ECUFlash XML's were.

D-VO

iTrader: (1)

That's pretty damn sweet though! What I'm still trying to figure out is: What is the difference between changing the settings on the MAF compensation table compared to changing it on the MAF scaling table? It looks like they're the same except for the part of the formula you edited. I would think that if they are in fact the same then both tables would change when one value is edited, but it doesn't.

Appauldd

iTrader: (22)

Guess I was wrong on that one. Funny thing is...whatever way I made the conversion....my MAF scaling is great and fuel trims are spot on.

Personally, I like your method. Saves a lot of adding and subtracting.

EDIT....

Oh I just remembered what I did....

I changed the scaling back to match my old ROM. Inported my numbers, then changed the scaling back.