As posted in the other thread:

MAF airflow in g/s:

530400xx: 0x8087d8 (2byte)
526800xx: 0x8087e0 (2byte)

Formula is x * 2 / 100

 

I have discovered about 20 new requestIDs, and their formulas. I am adding them to evoscan this weekend. please PM me any others you find so I can keep EvoScan up to date weekly, thanks.

 

messing around with an X this past weekend, I noticed TPS was always logged at 100% and RPM logged correctly but didn't work with the evoscan gauge...other items made the needle on the gauge work but RPM doesn't. Also decimal points still don't work when you make a WB02 evoscan gauge, it just rounds up/down

 

man you signature is huge. anyway, you need to set the dataitem scale to 0.1 if you want to use RPM with the gauges.

 

hmm it works fine without doing that on the 8/9 ..I'm not sure what that is but I'll try to remember it next time.

 

when logging the evo do i need to use the values that say USARPM USA TIMING USA KNOCKSUM or are the first ones fine i used the knocksum and timing that are at the top for logging is this ok?
whats mode23 for when you log the car what does it tell you?

i logged my car and used dataloglab here is the thread:

https://www.evolutionm.net/forums/ev...ml#post7266808

 

so i went and logged the usarpm timing everthing that says usa and it gives some strange values.
still using the first things the timing it seems that at peakboost the car hit 11* of timing is this normal and at 7000rpms i see 24*degrees of timing is all this normal?
coming from an evo8 this seems high.
thanks guys

and why in the world my throttle opening 95%?can you adjust this?

 

nevermind it was on the second page..

https://www.evolutionm.net/forums/7127262-post26.html

<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7F145" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8AA59" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8AA5E" scaling="Hex16"/>
>>>>>

ok.. so i see posts of people confirming this working with 53040007 early on when using the app and the config file (non as of late since evoscan integrated mode23). however, i don't see any xml listed on the first page for the rom id, 53040007. anyone know xml i should be using for this rom id?

 

anyone have a better xml definition for 53040007? For one the MUT table in mine doesn't quite look correct. below are links to the xml and rom i'm working with..thanks!

http://65.18.174.69/e6/tuning/53040007.xml

http://65.18.174.69/e6/tuning/EDM10RS.zip

 

<table name="MUT Table" address="3e320">
<table name="X"/>
<table name="Y"/>
</table>

 

So I have read all 535 posts twice now. I just want to make sure this is right as it looks nothinglike my 94170015 rom.
<rom>
<romid>
<xmlid>52690019</xmlid>
<internalidaddress>5002A</internalidaddress>
<internalidhex>52690019</internalidhex>
<make>Mitsubishi</make>
<market>USDM</market>
<model>Lancer</model>
<submodel>Evolution X</submodel>
<transmission>6MT</transmission>
<year>2008</year>
<flashmethod>mitsucan</flashmethod>
<checksummodule>mitsucan</checksummodule>
<memmodel>M32186F8</memmodel>

<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f121" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8aafd" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8ab02" scaling="Hex16"/>



</romid>

<include>52680015</include> After posting I add the bold to the 52680015 rom right?
</rom>

This is the rom I pull of the ecuflash. Do I just do this. Add the bold?

 

You can also just dump it into the 52680015.xml file. Then it will show up for 52680015 thru 52680020.

 

thank you sir!

 

I had just downloaded evoscan and it installed v2.6 beta16 automatically which I assume is good. Everything seems to be working okay, but this is my first time using evoscan and I have a couple questions:

1. Would downloading and using a data.xml file (such as one mrfred posted) do anything different for me or is it not necessary in the newest beta16 version?

2. Why does the maptracer function not seem to do anything, nothing happens when I right click the lower graph to load a hex/bin file. Any suggestions pointed on how to get that working?

If it makes any difference I am using a map I downloaded from gunzo which I believe had mode23 support changes already made. I did not have to make any changes to anything else just installed evoscan selected the USA values to log (USA RPM, USA PSIG etc) and it worked fine. Anything I should be doing differently?

-Thanks in advance.

 

Hey all,

I apologize if this topic has already been covered, but I couldn't find anything through searching. I thought I'd check to see if anyone has run into this problem before I posted a support ticket.

I've been trying to log some pulls the last few days and have been noticing that my curves looked off. While trying to figure out why there have been strange bumps, I realized that they may not be strange at all. Instead, my EvoScan logs are "skipping" data points, missing sometimes around 3 seconds of data! Now, while doing a pull, those three seconds of information are pretty darn important...

So, I've attached a log (and I'll paste a clip for people that don't care enough to download an attachment) for the gurus to take a quick peek at to see if I'm doing anything obviously wrong, or if I just don't know about something I was supposed to do. It seems to happen shortly after I go WOT. I originally thought it might be a skip right after starting the log so I started the logging a bit before I did the pull. It didn't work.


Here are the stats:
Windows Vista 32bit
Tactrix OpenPort 2.0rC with latest drivers
AEM UEGO with USB>Serial Adapter
Mode23 Enabled
Canadian (=USDM?) GSR


Clip of Log
LogID LogEntryDate LogEntryTime LogEntrySeconds
...
55 07/14/09 36:29.7 4.97711
56 07/14/09 36:29.8 5.06713
57 07/14/09 36:29.9 5.15735
58 07/14/09 36:30.0 5.24714
59 07/14/09 36:30.1 5.33713
60 07/14/09 36:30.4 5.61617
61 07/14/09 36:30.5 5.7061
62 07/14/09 36:30.5 5.79628
63 07/14/09 36:30.6 5.88612
64 07/14/09 36:30.7 5.9762
65 07/14/09 36:30.8 6.06615
66 07/14/09 36:30.9 6.15514
67 07/14/09 36:34.7 9.9361
68 07/14/09 36:34.8 10.02523
69 07/14/09 36:34.9 10.11525
70 07/14/09 36:35.0 10.20545
71 07/14/09 36:35.0 10.29421
72 07/14/09 36:35.1 10.38417
73 07/14/09 36:35.2 10.47424
74 07/14/09 36:35.3 10.56316
75 07/14/09 36:35.4 10.65336
76 07/14/09 36:35.5 10.74325
77 07/14/09 36:35.6 10.83316
78 07/14/09 36:35.7 10.92335
79 07/14/09 36:35.8 11.01316
80 07/14/09 36:35.8 11.10335
81 07/14/09 36:35.9 11.19215
82 07/14/09 36:36.0 11.28223
83 07/14/09 36:36.1 11.37231
84 07/14/09 36:36.2 11.46217
85 07/14/09 36:36.3 11.55222
86 07/14/09 36:36.4 11.6423
87 07/14/09 36:36.5 11.73226
88 07/14/09 36:36.6 11.82117
89 07/14/09 36:36.7 11.91136
90 07/14/09 36:36.7 12.00119
91 07/14/09 36:36.8 12.09137
92 07/14/09 36:36.9 12.18121
93 07/14/09 36:37.0 12.27212
94 07/14/09 36:37.1 12.36134
95 07/14/09 36:37.2 12.45018
96 07/14/09 36:37.3 12.54018
97 07/14/09 36:37.4 12.6302
98 07/14/09 36:37.5 12.72037
99 07/14/09 36:37.6 12.81029
100 07/14/09 36:37.6 12.90039
101 07/14/09 36:37.7 12.98914
102 07/14/09 36:37.8 13.07939
103 07/14/09 36:38.0 13.29821
....