Speed Density MAT - Page 4 - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community



Speed Density MAT

Reply
 
 
 
Thread Tools Search this Thread
Old Jan 14, 2017, 03:47 AM   #46
Newbie
 
Join Date: May 2010
Location: Canberra, Australia
Posts: 39
Thanked 1 Time in 1 Post

Drives: 2002 Mitsubishi Magna AWD

Quote:
Originally Posted by redSLed View Post
So is what you mean is that MUT 11 should have the address 9a96 from the 139 element table? Without looking I'm almost certain that's not the address that's currently in there because I've looked over that table and nearly everything starts with an '8'. Lemme check and get back here later.
No, the MUT table shouldn't have the address of the map but rather the address of the value to be logged (i.e. the address in RAM where the code stores an actual data value).

The MUT table you show in your follow-up post has the stock 94170015 addresses for MUT 11 (0xFFFF88C1, shortened in the ECUFlash presentation to 88C1) and MUT 3A (0xFFFF88BD, shortened to 88BD), so when you log MUT 11 you are logging the scaled IAT (i.e. output from interpolating the IAT sensor calibration map) and on MUT 3A you are logging the raw IAT sensor ADC input voltage. If you set the eval formula for each MUT appropriately in Evoscan you would then be able to cross check that the IAT calibration map is producing the correct output on MUT 11 given the input from MUT 3A.

I did have a look for fuel temp info as well: the only standard MUT item in 94170015 for this seems to be the raw fuel temperature ADC input voltage on MUT 87. If you were to pick a MUT item that you have never logged and change the address in the MUT table to 8917 (enter as 0x8917, this being the shortened form of the real address which is 0xFFFF8917) you should be able to log the value interpolated from the fuel temperature sensor calibration table with the Evoscan eval formula x*1.8-40 (for F). Looking at your MUT table, I would pick one of MUT BC, MUT BD or MUT BE for this purpose as these are duplicates of MUT BB (NB: you can only select a MUT to change from MUT 00 through MUT BF as these are MUT requests; the higher MUTs are all commands).
Offline
 
Reply With Quote
Old Jan 14, 2017, 06:52 AM   #47
Evolving Member
 
redSLed's Avatar
 
Join Date: Feb 2010
Location: Bethlehem, PA
Posts: 128
Thanked 3 Times in 3 Posts

Drives: 2004 Lancer Evolution RS

Thanks for clarifying, I misunderstood. I'm going to have to cross reference 3a and 11 logged values and see if one is appropriate given the logged value of the other. I've got the correct evaluation formulas for each request. X*1.8+32 for 3a and x*1.8-40 for request 11 for deg F.

I noticed if I use 0x03 I log about 10 degrees under ambient at 3a and if I use 0x0E (preferred for my tune), I log about 10 degrees OVER ambient at 3a. Either setting yields 73-75 degrees at request 11. I'm thinking somehow my table scaling may be off or the ait senor is bad.

I don't know how guys are logging within a degree of ambient/coolant temp on a stone cold car, at request 11. I'll figure this out if it kills me.

You've seen my scaling tables for mat (121 element) and sd mat scaling for iat table(139 element) does anything look glaringly off for a gm ait? The table scalings I've found for temp and volts are few and far between and all the old threads with appropriate scales and patches have DEAD links.

Again, thanks so much for your help and time here. I'm still learning.
Offline
 
Reply With Quote
Old Jan 14, 2017, 04:59 PM   #48
Evolving Member
 
redSLed's Avatar
 
Join Date: Feb 2010
Location: Bethlehem, PA
Posts: 128
Thanked 3 Times in 3 Posts

Drives: 2004 Lancer Evolution RS

Well, I still seem to be logging strange values. I've tried intentionally different settings in the MAT Scaling table (121 element) and 131 element SD MAT scaling for IAT scaling table and obviously logged request 11 changes with adjustments to the SD MAT/IAT table.

What's interesting is that request 09, 87 do not change based on completely different scaling settings for the MAT table with tempscalefuel scaling.

Air temp remains well above ambient by more than 15 degrees and logged fuel temp is logging 221 degrees F? I went with MUTBC with address 8917 to log fuel temperature per your recommendation.

There must be some scaling issue here. I wish there were some definitive and convincing table scaling values that were shared in some of these threads and the old links are all gone.
Attached Thumbnails
Speed Density MAT-screenshot-32-.png  
Offline
 
Reply With Quote
Old Jan 14, 2017, 09:32 PM   #49
Newbie
 
Join Date: May 2010
Location: Canberra, Australia
Posts: 39
Thanked 1 Time in 1 Post

Drives: 2002 Mitsubishi Magna AWD

Quote:
Originally Posted by redSLed View Post
Thanks for clarifying, I misunderstood. I'm going to have to cross reference 3a and 11 logged values and see if one is appropriate given the logged value of the other. I've got the correct evaluation formulas for each request. X*1.8+32 for 3a and x*1.8-40 for request 11 for deg F.
Evoscan and many other sources have the standard usage of MUT 3A incorrect: the correct units are Volts not temperature (F or C). A reasonably accurate Evoscan formula for MUT 3A in stock usage is x*0.01953.

Quote:
Originally Posted by redSLed View Post
I noticed if I use 0x03 I log about 10 degrees under ambient at 3a and if I use 0x0E (preferred for my tune), I log about 10 degrees OVER ambient at 3a. Either setting yields 73-75 degrees at request 11. I'm thinking somehow my table scaling may be off or the ait senor is bad.
I don't know a lot about the inner workings of the Tephra ROMs in this regard but I don't think changing the "source" of IAT info for the SD system via the control value affects the standard MUT logging, it just changes where the SD routines get the IAT value. You still have to log the source input to see what that's doing.

Which input on the ECU do you have your GM AIT wired into? If the GM AIT is wired in place of the stock MAF AIT, then MUT 3A and MUT 11 will tell you about it. If you're setting the SD routines to use the fuel temp rather than AIT then you'll need to log fuel temp related data (as described in my earlier post) to understand what the SD system is doing.
Offline
 
Reply With Quote
Old Jan 15, 2017, 08:30 AM   #50
Evolving Member
 
redSLed's Avatar
 
Join Date: Feb 2010
Location: Bethlehem, PA
Posts: 128
Thanked 3 Times in 3 Posts

Drives: 2004 Lancer Evolution RS

Thanks for the formula for logging volts from the air temps sensor! I was wondering about that and couldn't seem to find it amongst the threads I'd searched. I'll give it a shot and then I can correlate volts in 3a to the temp logged at mut11.

I was under the impression that if I'm logging fuel temp with option 0x0E and still have my GM iat sensor connected to the maf harness via the Spoolinup adapter, the value logged at MUT11 is a simulated fuel temp converted from raw iat? Something along those lines. I think I read that more than once in one of the original MrFred threads on SD logging mat, etc.

I'm still going to attempt to log fuel temp using mutBD using address 8917. I tried address BC yesterday and logged 200 plus deg F which is incredibly off for some reason or another.

I have no explanation as to why my logs for raw iat at 3a change up and down 10-11 deg F from ambient just from changing 0x03 to 0x0E but it does. I tested it back to back with that being the only change to the rom! Strange...
Offline
 
Reply With Quote
Old Oct 8, 2017, 08:16 AM   #51
Newbie
 
400s's Avatar
 
Join Date: Mar 2014
Location: C
Posts: 32
Thanks: 0
Thanked 2 Times in 2 Posts

Drives: Evo IX MR

Deleted

Last edited by 400s; Oct 17, 2017 at 08:14 AM. Reason: Got the answer to my stupid question
Offline
 
Reply With Quote
 
 
Reply

Related Topics
Thread Thread Starter Forum Replies Last Post
MAT scale ? 95630706 EcuFlash 12 Oct 8, 2017 08:12 AM
How To: Speed Density on the evo8 using tephra v7/Phenem pre-patched roms scheides EcuFlash 341 Sep 4, 2017 09:08 PM
Links to jcsbanks' Speed Density patches mrfred EcuFlash 375 Jan 28, 2017 09:58 PM
RAX Patch - ROM patches richardjh Ecuflash 200 Sep 20, 2016 11:31 AM
how-to: control closed loop AFR with your wideband O2 system mrfred EcuFlash 453 May 2, 2016 06:35 PM


Tags
96531706, bmw, cost, density, english, evo, evolution, fuel, mat, mrfred, mrfreds, patch, patych, racing, sd, speed, temp

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -7. The time now is 02:02 PM.


 
  • Ask a Question
    Get answers from community experts
Question Title:
Description:
Your question will be posted in: