Evo8 ECU in a 1G DSM in the works!
Jul 30, 2009, 06:37 PM
#76
Also, if you email a mod over there, tell em you have a lot of EVO ECU experience and tell them your EVom name, you can get cleared to go into the tech sections.
so I will refrain since its not the members I hate, just the site rules.
Jul 31, 2009, 09:42 AM
#80
Evolving Member
iTrader: (2)
Join Date: Feb 2009
Location: State College, PA
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
Is the Maf Adder a hex or decimal value? We now have 40 thrown in as another possible MAF adder for the 2g?!? Great.
I'm running the MAF scaling that is basicaly the 2g values -76 and that has me at good fuel trims.
I'm running the MAF scaling that is basicaly the 2g values -76 and that has me at good fuel trims.
Jul 31, 2009, 10:49 AM
#84
Evolving Member
iTrader: (2)
Join Date: Feb 2009
Location: State College, PA
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
Ok. That's what I've been thinking. I don't have my computer near me since I'm traveling this weekend, so I couldn't look it up in ecuflash. Since I made that last post, I've done some digging around.
------------------------------------------------------------------------------
In regards to the link posted saying the 2g MAF size is 40...
From: http://www.hwnd.org/#maf%20compensation
First of all, this calls the adder a multiplier. We'll overlook that.
Maybe the 1g has a decimal MAF adder of 100 and the 2g has one of 64? So me thinks. It makes sense. With those values, the 2g MAF will flow 20-30% more at any given Hz than the 1g MAF, which is widely known.
I think the confusion is between what is hex and what is decimal.
Hex ---> Dec
40 - 64
64 - 100
8C - 140
140 - 320
So if you're running a 1g MAF (why would you still?), use the 1g values, but subtract 40. If you're using a 2g MAF, use the 2g values but subtract 76.
Now is this referring to the MAF size (size*100)?
Hex --> Dec
5E86 - 24198 (214.98)
62B9 - 25273 (252.73)
7A03 - 31235 (312.35)
I'm curious where the 286.0 value I'm using for the MAF size came from if these are indeed refering to MAF sizes.
I wish I knew how to disassemble ROMs and read all this stuff for myself. Maybe once school starts up I'll dive into that some more.
On a side note,
I'm running the MAF scaling that is basicaly the 2g values minus 76 and that has me at good fuel trims. I've put more than 1000 miles on my car in the last 2 weeks. (I got 27mpg highway while drivingthrough the mountains
) I'm driving from Pittsburgh to Philly next weekend.
------------------------------------------------------------------------------
In regards to the link posted saying the 2g MAF size is 40...
From: http://www.hwnd.org/#maf%20compensation
NEXT, you need to change another byte the serves as a multiplier. This byte is located at the address 5669, and the stock value at this point is "64" hex. For a 2g MAS, change that to "40" hex.
Maybe the 1g has a decimal MAF adder of 100 and the 2g has one of 64? So me thinks. It makes sense. With those values, the 2g MAF will flow 20-30% more at any given Hz than the 1g MAF, which is widely known.
I think the confusion is between what is hex and what is decimal.
Hex ---> Dec
40 - 64
64 - 100
8C - 140
140 - 320
So if you're running a 1g MAF (why would you still?), use the 1g values, but subtract 40. If you're using a 2g MAF, use the 2g values but subtract 76.
In addition, in order to make sure the timing and fuel maps still line up, you need to change the value at 549A from "5E86" (1g) or "62B9" (GVR-4), to the 2g value which is "7A03."
Hex --> Dec
5E86 - 24198 (214.98)
62B9 - 25273 (252.73)
7A03 - 31235 (312.35)
I'm curious where the 286.0 value I'm using for the MAF size came from if these are indeed refering to MAF sizes.
I wish I knew how to disassemble ROMs and read all this stuff for myself. Maybe once school starts up I'll dive into that some more.
On a side note,
I'm running the MAF scaling that is basicaly the 2g values minus 76 and that has me at good fuel trims. I've put more than 1000 miles on my car in the last 2 weeks. (I got 27mpg highway while drivingthrough the mountains
) I'm driving from Pittsburgh to Philly next weekend.
Jul 31, 2009, 02:04 PM
#87
.
Now is this referring to the MAF size (size*100)?
Hex --> Dec
5E86 - 24198 (214.98)
62B9 - 25273 (252.73)
7A03 - 31235 (312.35)
I'm curious where the 286.0 value I'm using for the MAF size came from if these are indeed refering to MAF sizes.
I wish I knew how to disassemble ROMs and read all this stuff for myself. Maybe once school starts up I'll dive into that some more.
On a side note,
I'm running the MAF scaling that is basicaly the 2g values minus 76 and that has me at good fuel trims. I've put more than 1000 miles on my car in the last 2 weeks. (I got 27mpg highway while drivingthrough the mountains) I'm driving from Pittsburgh to Philly next weekend.
Now is this referring to the MAF size (size*100)?
Hex --> Dec
5E86 - 24198 (214.98)
62B9 - 25273 (252.73)
7A03 - 31235 (312.35)
I'm curious where the 286.0 value I'm using for the MAF size came from if these are indeed refering to MAF sizes.
I wish I knew how to disassemble ROMs and read all this stuff for myself. Maybe once school starts up I'll dive into that some more.
On a side note,
I'm running the MAF scaling that is basicaly the 2g values minus 76 and that has me at good fuel trims. I've put more than 1000 miles on my car in the last 2 weeks. (I got 27mpg highway while drivingthrough the mountains
) I'm driving from Pittsburgh to Philly next weekend.The scalling for MAF size in ECU Flash is x*600/65536. 7A03 in dec is 31235. 31235*600/65536 = 286
Jul 31, 2009, 02:09 PM
#88
so we're adding a hex adder to a scaled "g/s" MAF scaling value when people rescale their MAF's? Seems like we should be using the same scaling for both to do that properly,no? This is referring to the Evo-m 'how to rescale your MAF' thread.