2009+ Ralliart Evoscan addresses / info
 

This will evolve into a central thread where people can find correct Evoscan address's to properly log their 2009+ Ralliarts.

-------------------------------------------------------------------------------------------------------------------------------------------

First, check this first post for your ROM ID and check for the *known working* address's for your ROM ID / Model Year and Market.

If what you are seeking is not listed then:

Second, post what ROM ID / Model Year and Market you have and then what you are trying to log and with what current address.

Example:

ID 55590342
2010
USDM

Looking for:

Manifold Air Temp
Currently logging request address: 23808632
Does not log correctly

-------------------------------------------------------------------------------------------------------------------------------------------

ID 55590007
2010
USDM

Currently logging correctly:

RPM
Load
TimingAdv
Barometer
PSI
Knock Sum
Accel Pedal Position
TPS
Active WGDC
IPW
IDC
Corrected Timing Advance
Manifold Air Temp
Coolant Temp
Intake Air Temp
Speed
STFT
LTFT idle
LTFT Cruise
LTFT In Use
Boost Error (for psi-target, needs rom mods)
Front Oxygen Sensor
Rear 02
Knock Voltage
Battery Level
Injector Latency
InVVT (target)
ExVVT (target)
InVVT (actual)
ExVVT (actual
MAF Volts
MAF Airflow
Altmap Status (for Tephra map switching, needs rom mods)
SST Transmission Temp
External Wideband A/F Ratio

XML:

-------------------------------------------------------------------------------------------------------------------------------------------

ID 53600010
2009
USDM

Currently logging correctly:

RPM
Load
TimingAdv
PSI
Knock Sum
Accel Pedal Position
TPS
Active WGDC
IPW
Coolant Temp
Intake Air Temp
Speed
MAF Volts
External Wideband A/F Ratio

XML

Saved for overflow if needed

Saved for overflow if needed

I'm going to need some help from you guys for 2009 as I don't have a 2009 I can log whenever I want and I can't remember what works correctly and what doesn't

- Bryan

Awesome, Thanks again Bryan!

Nub ? though. My stock internal id was 53600010 and after I flashed to the GST V2 basemap it was changed to 53600009. Does this matter now for logging purposes, since every rom id has its own address for data?

ID 53600010
2009
USDM

Intake Air Temperature
Currently logging request address: 23808659, eval - 1.8*x-40

May not be wrong but this is what I have been logging for IAT and I was seeing 188F. I will be more help on this once I have the stock air box out.

Manifold Air Temp
Currently logging request address: 23808661, eval - 1.8*x-40

With ambient air temp at 66F, MAT was 75F @ cruise/normal driving. Seems correct.

Knock Sum
Currently logging request address: 23808A53, eval x

2 Byte RPM
Currently logging request address: 23808743, eval 3.90625*x

correct

Bryan, I have a 2009 and am pretty local to you. Let me know if you want to take a look.

I just got my Tactrix cable today and was playing with Evoscan. So does this mean that the 09 RA doesn't log properly in the latest version?

53600009 same as 53600010

usually same year, same model, address's are the same. I just wanted to include Rom ID's as well

- Bryan

We are not 1000% sure on some. If at all possible magnus, log some data for IAT and any other you may want to log and let's compare and contrast.

This would be awesome!

So i did a little logging on the way to work today. Traffic was bad so it was really fairly useless. But I'll report what does not seem to be right. I am logging using the default address in evoscan 2.7 for USA RA EVO X. I had done a bunch of searching and had most of this stuff working correctly, but had some laptop issues and lost the addresses :mad:

53600010

ExVVT 23809462
Seems to be InVVT as it follows my intake map almost exactly. Not sure if this is target or actual.

InVVT 23809444
Return -63 constantly

IPW 2380A94C
Returns 0 constantly

IDC 2380874E
Returns 0 constantly (IPW is not working)

IAT 23808659
146 to 167 degree. Seems strange

LTFT cruise 2380457D
Returns -21 constantly

Ill post more stuff when I get a chance.

55590006 2010 Ralliart

Trans temp isn't reading correctly in F anyway. What EVAL should be used in there for correct temps in F? Currently it has X-50 in there.

I put 1.8*x-40 in there for Fahrenheit reading. Just making sure this is correct.

I believe all temps (IAT, MAT...etc) should have the Eval at 1.8*x-40.

If someone else can assure me and Colt on this?

I have been logging this address for IAT and I can defiantly confirm that this is wrong. How do we figure what is right? MUT Tables? So then this would be the xml code to access the MUT tables?

<table name="MUT Table" address="???"> (not sure of the address)
<table name="X"/>
<table name="Y"/>

Piper, it seems that you may have a lot of knowledge regarding this topic. I am just starting to learn this so if at all possible any of your help would be completely appreciated.

All I have is experience logging and tinkering with my own car, and a lot of reading. As far as rom disassembly and finding the correct address, I unfortunately have no insight. I got my hands on IDA Pro, but really need some guidance to begin looking at the rom, or a partial disassembly would help. I'm not a programmer, but I do have experience with assembly language.

Ok no problem. I am in the same boat as you then. I have experience with x86 assembly and am pretty much fluent in C++. But I program video games...lol I do not know how to read MUT tables yet or even no where to start. I have read tephras EvoX logging and have so much more reading to do!

Here is the mut table for 53600010

<table name="MUT Table" address="3efc0">
<table name="X" elements="16"/>
<table name="Y" elements="30"/>
</table>

Here is what I was trying to use to find stuff in the MUT table. Not sure if this is the most current. I actually kinda forgot about that important table. That is how I actually cleared up some of those addresses before losing them. Except that damn IAT :lol:

http://evoecu.logic.net/wiki/MUT_Requests
https://www.evolutionm.net/forums/7075360-post10.html

Awesome! Thanks a lot for the links and the MUT table. I will have the opportunity to reflash, with the MUT table added to my 53600010 xml tomorrow morning.

If those links are correct then, MUT 11 is our IAT address...

Yes it seems that way. But that's the address for MAT in evoscan, so what would that one be 3A on the mut? In that case they are just flipped. But 180 degree doesn't seem right does it? Thats a pretty inefficient IC.

Evoscan update! if you didn't get the email. Maybe some of our logging issues are fixed....:)

The update didn't help me - still no logging for Mode 23 on AUSDM RAs. I've asked Tephra to take a look a few weeks back, but he never got back to me.

I'm headed out to try some address from referencing the MUT table. I am confused because I tried to cross reference Bryan's list of working address for the 2010 model with the MUT table from 55590006 and they don't correspond to the MUT id listed in the wiki page. Unless 55590006 and 55590007 have different mut tables. Maybe the address for the MUT table I have for that rom is not right. Maybe Bryan can confirm if this is the way to go about finding proper address? I think there is more to it...

Ok so I think I have corrected a few address.

ROM 53600010

LTFT Idle 23804573
LTFT Cruise 23804575
IPW 2380A974

Maybe someone else can try and see.

Bump!

Did anyone confirm these addresses?

sorry piper, i did not have a chance to log those addresses yet. I have been crazy busy. As of right now my front bumper, intake and cat is off my car. I have a appointment to get tuned tom so I have to get the ams intake, testpipe and bumper back on tonight. And it was my b day weekend :) so i was not in any state to log data. So wenesday i should be able to.

Happy late B-day! Sounds like you got some fun Birthday parts. Good luck with the tune let us know how it goes.

Thanks!!! I will post as much as i can on my build thread tomorrow night.

"I program video games.."

What kind of video games? Ever get any free copies ;)

Looking forward to it {thumbup}

Could use some help getting Mode 23 to work with EvoScan with AusDM 2009 RA. I have same issue as BobCrusader......

Bryan you are the man!! Thank you for all the help you are giving to the Ralliart community!

what tools are people using to try and work out the addresses? I'm pretty good with computing thingies, but need a bit of help getting started.

I believe they're using EvoScan software and the Tactrix Open Port 2.0 to find addresses and map them

Is there an easy way to load all of the EvoScan addresses without going 1 by 1? Sorry still trying to lear this program

I've got that stuff. But 'understanding' hex and translating that into something useful is the hard part.

Ok, I have not had the chance to check and recheck addresses yet. I will have time today. But I want to start at the beginning to make sure I and others wanting to log are doing this correct.

I have updated EVOscan to the latest version and have noticed things are moved and a couple request addresses are changed. If someone can confirm I have the correct code to enable Mode23 for my ROM, I will start doing some logs ASAP.

2009 Lancer Ralliart
Rom ID: 53600010

1. Enable mode23 logging ( There is a thread dedicated to this )

What I have in my xml is

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

Can anyone confirm this is correct the correct XML code for my Rom ID?

After adding these few lines of code into the XML for 53600010, Flash your RA again with the ROM your are wanting to log.

Plug in your tactrix cable, Select Mode23 USA RA EVOX and start datalogger.

Thats it!

Thanks!

That's the xml I'm using.

Same address here. You forgot to mention to actually change the values in the new tables after adding to your xml. If they don't match, you got the wrong address.

Ya forgot to mention that too. That's kinda why I added the mode 23 logging thread. But to be sure you mean changing the new tables in ecuflash to match the values. 0x23....etc.

Yup. I figured you obviously knew or you wouldn't be logging anything. I should have kept quiet :p

Haha, its all good! {thumbup}

Ok some weird serious S*** happened last night when I added the mode23 logging xml code to my 53600010 xml.

I reflashed, started the car ( idled like normal, seemed perfectly fine ) But when I clicked start data logger in EVOscan my car STARTED GOING CRAZY! The triangle exclamation point popped, idle started fluctuating like CAARRRAAAZY! I turned the car off immediately and deleted the mode23 code in my xml and reflashed. No problems.

Weird because I have logged numerous times before with GST base maps, my stock map and I am for sure certain that I added the right code. I double checked like 3x to make sure, wasn't missing any syntax. Somethings not right and I can not figure out what I did. Spent all day searching and thinking...nothing!

Any help here would be awesome!

^^^ Did you ever resolve your problem?

Also, can anyone point me to the right address to log MIVEC timing (actual) for intake and exhaust? It would be nice to see if and how much it lags behind the target, and it might also help to relate MIVEC patterns with torque production.

No not yet. I am waiting for Chris @ AMS to allow for evoscan to work with the base map. He did not say what could cause the issue, only that a couple settings in the rom will do that. So until he can get back to me I wont be able to log.

Hi all.

ID 53610010
2009
AUDM

Looking for:

Basic logging of any sort!

I've just applied the glorious GST Base Map ROM "2009 AUS / EDM - 93 oct - StockPill - V2" to my bone-stock RA Sportback via OpenPort 2.0. Got OpenPort 2.0 standalone mode23 logging to mini-SD card "functional" (ie. recording values to file). But the values aren't sensible.

I've searched high and low for valid 53610010 logging addresses, but to no avail. I was hoping to review some basic RPM/Knock/TimingAdv items before driving it hard - it seemed the sensible approach.

Not sure what to do next, apart from just cross my fingers and drive! :)

If anyone knows of sensible "basic" logging addresses for this particular ROM, I'd be delighted to hear 'em...

Cheers,

Rich

Second that, Richard. BTW - get the boost pill from GST (or AMS) and try the Boost Pill tune. Best $30 you will ever spend.

Rom ID 53600010

I can log now!

Here is a 3rd - 4th gear pull.

Request ID for IAT = 23808659
MAT = 23808661

http://img214.imageshack.us/img214/4...liatmat68f.png

I still think IAT is way too high? Ambient Temp was 68F today.

How do I figure out what address is correct to log proper IAT?

And here is the same pull logging Rpm, boost and knock.

http://img257.imageshack.us/img257/9...lrpmboostk.png

2011 Ralliart Addresses for EvoScan:

Any chance of finding the MIVEC logging for 2009 RA?

55590006
USDM
2010 RASB
Need the info for logging boost.
Thanks

On first page, use 55590007 addresses

I did, have it set-up as directed:
(x/4*0.1953125)-[Baro]
And Baro seems to be correct, logging 14.6 - 14.8 (I'm at see level)
But here is a sample from my log from last night:
2ByteRPM Load O2Sensor2 KnockSum TimingAdv Boost TPS Speed Baro
2,492 45 13.9 - 37.0 9.2 20.0 19 14.8
2,500 43 13.6 - 38.0 9.2 20.0 19 14.8
2,512 43 13.3 - 38.0 9.1 20.0 19 14.8
2,523 42 13.0 - 38.0 9.2 20.4 19 14.8
2,543 42 13.0 - 38.0 9.1 20.4 19 14.8
2,566 42 13.2 - 38.0 9.1 20.4 19 14.8
2,586 42 13.9 - 38.0 9.0 20.4 19 14.8
2,609 42 13.9 - 38.0 8.9 20.0 19 14.8
2,621 41 13.9 - 39.0 8.8 20.4 20 14.8
2,633 41 13.8 - 39.0 8.7 20.4 20 14.8
2,645 41 13.8 - 40.0 8.6 20.4 20 14.8
2,660 41 13.6 - 40.0 8.6 20.4 20 14.8
2,668 41 13.2 - 40.0 8.6 20.8 20 14.8
2,684 41 13.2 - 39.0 8.7 20.8 20 14.8
2,707 42 13.5 - 39.0 8.7 20.4 20 14.8
2,723 41 13.8 - 40.0 8.6 20.4 20 14.8
2,742 41 13.8 - 40.0 8.6 21.2 21 14.8
2,781 41 13.7 - 4.0 8.9 22.0 21 14.8
2,707 45 13.6 - 4.0 9.9 23.1 21 14.8
2,543 52 13.4 - 3.0 11.1 23.9 21 14.8
2,363 58 13.5 - 17.0 12.5 25.9 21 14.8
2,238 66 13.7 - 28.0 13.6 25.9 21 14.8
2,113 70 13.7 - 27.0 14.0 27.8 21 14.8
2,156 72 13.5 - 28.0 14.6 32.5 21 14.8
2,195 75 13.2 - 27.0 16.2 38.0 22 14.8
2,230 79 13.2 - 25.0 16.5 38.0 22 14.8
2,250 82 13.2 - 23.0 16.8 40.8 22 14.8
2,258 85 13.5 - 20.0 17.4 47.8 22 14.8
2,293 90 13.8 - 19.0 17.8 50.6 22 14.8
2,336 93 14.4 - 17.0 18.2 53.3 22 14.8
2,348 97 14.4 - 16.0 18.6 57.6 22 14.8
2,383 103 13.9 - 15.0 19.2 61.2 22 14.8
2,422 107 13.8 - 14.0 19.8 62.0 25 14.8
2,461 112 13.8 - 13.0 20.5 61.6 25 14.8
2,496 117 13.8 - 12.0 21.1 61.6 25 14.8
2,527 123 13.8 - 10.0 22.1 62.0 25 14.8
2,590 130 13.7 - 9.0 23.0 61.6 25 14.8
2,633 136 13.5 - 10.0 23.9 61.6 25 14.8
2,676 141 13.5 - 9.0 25.0 61.6 25 14.8
2,723 148 13.5 - 8.0 26.1 61.6 25 14.8
2,797 156 13.5 - 8.0 27.4 61.2 25 14.8
2,852 165 13.5 - 8.0 28.9 61.2 29 14.8
2,922 174 13.3 - 7.0 30.8 61.6 29 14.8
2,984 189 13.2 - 6.0 32.6 61.2 29 14.8
3,059 198 12.9 - 5.0 34.0 61.2 29 14.8
3,129 207 12.2 - 6.0 35.2 61.2 29 14.8
3,234 209 12.2 - 6.0 35.1 61.2 29 14.8
3,297 208 12.2 - 7.0 34.5 61.2 29 14.8
3,391 206 12.2 - 7.0 34.0 61.2 35 14.8
3,508 199 11.4 - 8.0 33.0 61.2 35 14.8
3,582 197 11.4 - 8.0 32.3 61.6 35 14.8
3,598 197 11.4 - 8.0 31.8 62.0 35 14.8
3,641 198 11.4 - 9.0 31.7 64.3 35 14.8
3,727 197 11.4 - 9.0 31.7 67.1 35 14.8
3,770 199 11.2 - 9.0 31.8 69.0 35 14.8
3,863 201 11.1 - 10.0 32.4 71.0 35 14.8
3,949 205 11.1 - 10.0 32.9 72.2 35 14.8
4,043 209 11.0 - 10.0 33.7 72.9 41 14.8
4,129 214 11.0 - 9.0 34.3 74.1 41 14.8
4,199 218 11.1 - 9.0 34.9 75.3 41 14.8
4,250 220 11.0 - 10.0 35.0 76.1 41 14.8
4,309 222 10.7 - 10.0 35.1 76.5 41 14.8
4,379 222 10.7 - 10.0 35.0 76.5 41 14.8
4,453 223 10.7 - 10.0 35.1 76.9 41 14.8
4,504 223 10.7 - 10.0 35.4 77.3 41 14.8
4,574 223 10.7 - 10.0 35.4 77.6 47 14.8
4,648 223 10.0 - 11.0 35.3 78.8 47 14.8
4,719 224 10.0 - 11.0 35.4 80.8 47 14.8
4,789 224 10.0 - 11.0 35.5 83.1 47 14.8
4,844 224 10.0 - 12.0 35.8 85.1 47 14.8
4,953 224 10.0 - 12.0 35.8 85.9 47 14.8
5,027 224 10.0 - 12.0 35.9 86.7 47 14.8
5,090 224 10.0 - 12.0 35.7 86.7 47 14.8
5,160 223 10.0 - 12.0 35.6 86.7 53 14.8
5,215 222 10.0 - 12.0 35.5 86.3 53 14.8
5,289 221 10.0 - 13.0 35.1 86.3 53 14.8
5,363 219 10.0 - 13.0 34.8 86.3 53 14.8
5,410 217 10.0 - 13.0 34.7 86.3 53 14.8
5,496 216 10.0 - 13.0 34.4 86.7 53 14.8
There is no way that boost reading is correct. I'm using PSIG from page one; I notice you often label these items by their units rather than common names, and that was the unit from EvoScan for Boost. So is this the correct address and eval for boost, or should I be using something else?
Sorry I'm having issues getting the raw data to be in a presentable format on here. Boost is 4 from right (hitting values of 34.4 for last line item)

OK here we go, got it in a viewable format {thumbup}

Wait I just thought of something, -[Baro] for the eval, is that actual item typed in... Because if I subtract Baro from the logged amount, then I get what it "should be".

Baro needs to come before PSIG in the logging.

^haha really?!? its that simple... based on order of logging items.
Sorry for the redundancy, thanks much!

Heres a new question, how do I edit the range for RPM (rows)? For instance in the Timing map its in increments of 250, but in Fuel its increments of 500. Can I change the Fueling map RPM ranges to 250??

Any have the address for 53610010 2009 AUSDM WGDC Error Correction Interval for EcuFlash? I want to run a 3 port boost solenoid and reduce the interval time.

Hi Bob.

Believe this is what you're looking for...



There is apparently a "low gear range" one too, but I don't know its address for sure. I found a similar ROM to ours that had an XML address of "54688" specified for it, and the value at that address in our ROM is 7 (the expected value)... but I'm not game to poke at it!

I'd also read somewhere that these weren't really "high vs. low" timers at all, but were instead "normal vs. limit-exceeded". So for now I'm ignoring the "other" interval address completely... :)

If you find a real winner of an EC configuration, let me know. I've been messing about with this for a week now, and would love to see other peoples' findings on the RA.

Rich

Merlin's guide reckons on 3 (=300ms). Default is supposed to be 10 (=1000ms), but mine was 7 as well.

I would like to log my wideband via the rear o2 ADC. I wired it in, I just need the address to log for 53600010. Can someone help me out?

I was just going over my data logs, and since updating my EvoScan logging information with the data for 55590006 on page one, I noticed my boost levels appear to be higher than before...

I looked over the XML data and confirmed I have the same entries as page 1 from this thread:

I know it's been said that the above is the "proper" way to log boost levels. I read the OP of this information on the EvoX thread, but did not read the entire thread to see if my observations became a topic of discussion. With these settings I noticed the PSIG readings in my logs to be directly proportional to my altitude. or to put in another way, my logged PSIG readings were inversely proportional to the environmental air pressure...

For example, I was doing some pulls at about 2750 ft altitude (Baro logged 13.3), as a result my logged boost levels were about 23 PSI peak. Using the old method of calculating PSIG ( - 14.7 instead of - Baro ), I would consistently have around 21 PSI...

With the calculation for PSIG being based on the Baro reading, I would have 1.3 PSI less boost at sea level (Baro reading of 14.7), which would be about 21.7PSI peak boost. That is assuming the pressure in the intake manifold was identical regardless of environment air pressure.

This is kind of confusing me, because with the calculation for PSIG the logs would (and do) indicate I have increasing boost levels as I increase in altitude. Relative to the environmental air pressure this makes sense, but at the same time, it seems a bit counter intuitive?

I guess, the part that's confusing me most is why I would want my logged boost levels to indicate higher numbers when I'm at higher altitudes?

Ok, I've read more of the thread that I think first brought this method of calculating boost levels up. It seems that it's thought that this method is better for people at altitude. However, I still don't really understand why you would want to do it this way for your logs. If you're tuned on PSI based maps, then wouldn't logging your PSI relative to the atmospheric pressure cause your logs to show artificially high PSIG readings if you were to drive into the mountains?

I mean, if I log PSIG relative to sea level, then my boost levels while driving through the mountains would be relatively consistent when reaching peak boost levels (e.g. 21 psi). If I log PSIG relative to atmospheric pressure, then when I reach 6000ft of altitude (altitude changes for me in the mountains range from 2500 to 6200 ft), my logged peak boost readings would be 2.9PSI higher (e.g. ~24psi), which would give the appearance of over boosting.

In that comparison above, the absolute pressure inside the manifold is the same. The only thing that changed is the atmospheric pressure.

In the interest of properly detecting over boost conditions, shouldn't I want to log my PSIG as a function of a constant, like air pressure at sea level (14.7)? I mean, isn't knowing the "absolute pressure" in the manifold more important than knowing the pressure in the manifold relative to the environment?

If I'm missing something major here please do enlighten me...

I did much more reading, and decided to have EvoScan log my PSIG as a function of air pressure at sea level, because with a PSI based tune made for sea level the pressures inside the manifold that you want to keep track of will be relative to sea level, regardless of your altitude. The car will adjust the AFR trim based on the PSI inside the manifold relative to the altitude it was tuned for. This means at 6000ft of altitude and logging PSIG relative to atmospheric pressure, the PSIG will read 2.9 PSI higher than sea level, which would give the appearance of over boosting. However, in reality it isn't because the car is making its boost corrections based on the targets set for sea level, and a manifold pressure of 22.9 PSI at 6000 ft of altitude is the same as 20 PSI at sea level.

The only point that this ~might~ be a problem is with soft lines that have to hold positive pressure inside them, for example the OEM UICP and the couplers on after market UICPs. However, in the case of after market UICPs the soft couplers should be rated to hold much much higher pressure differentials than we can achieve w/ the stock turbo. I'm not sure what the OEM UICP is rated to be able to handle, but I imagine it should be able to handle pressure differentials much higher than we can achieve with the stock turbo as well.

Most importantly, IIRC, the GST base map v2.5 ROMs are PSI target tunes that target 22.4 PSI @ sea level...

The GST 2.5 ROM version I use (AUDM) still uses "traditional" load-based boost control...

Rich

Yea the basemaps are target-load based.

ah, my bad ... didn't mean to mis-inform anyone :\

Has anyone figured out how to log and/or alter the radiator activation temp yet?

I'd like to set mine to about 195, under 35 - 45MPH. I've been logging my commutes between work and home, and during LA evening rush hour, I'm seeing the coolant temps go up past 205. Today it got up to 208, and I don't recall hearing the fan kick on at all. :\

hey everyone i'm currently on the hunt for some addresses for 2010 ralliart. currently cannot find load timing and ignition timing. if anyone can help it would be much appreciated. thanks

they should be in there plain as day, assuming you have the right definitions. Well, the ignition timing is. You have high octane timing, low octane timing, upper and lower timing boundaries, warm up timing retard, etc... I assume by "load timing" you mean the cam timing, or are you referring to egr?

also the data in this thread is all EvoScan/ECUFlash centric...

09
53600010
evoscan 2.9

I'm getting weird number logging baro(2380A911), snap-on scanner is showing 30inHG/correct for my area, while evoscan is showing 0 or 60+ bar.

This is the default evoscan xml file. The table in the first post doesn't list baro at all.

<DataListItem DataLog="Y" Color="" Display="Barometer" LogReference="Baro" RequestID="2380A939" Eval="x*0.07251887" Unit="psi" MetricEval="x/2" MetricUnit="kPa" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="50" Visible="False" />

Thanks, is there an updated list of addresses for my particular rom? I'm also curious as to how x is defined in the eval portion, I assume it's just an integer and then some math to hit what unit you're trying to describe it as?

x is the raw logged unit

Here is the list I have for your ROM:

23808776 Load
2380874E 2ByteRPM
23808722 PSIG / Boost
23808A53 Knock Sum
238088A0 STFT
23804573 LFTF Idle
23804575 LTFT Cruise
238088B1 LTFT in use
2380877C Load (MIVEC) and (Timing if IAT GT 75F)
23808701 TPS
2380951D Accel Pedel Position
23808A0F TimingAdv
23808B5B ActiveWGDC
23808661 Intake Air Temp
23808647 Coolant Temp
23808667 Manifold Air Temp
2380A974 IPW
23808F64 MAF Volts
23809446 INVVT (Target)
23809452 EXVVT (Target)
2380947E INVVT (Actual)
2380948A EXVVT (Actual)
238087EF Speed
238086F7 Battery
2380A939 Barometer
23808A59 knock_adc_processed
2380A96B knock_base
2380A967 knock_var
2380A96D knock_change
23808A67 knock_dynamics
2380812D knock_flag
23808671 Front O2
23808675 Rear O2
238045C5 Cruise Light
23808B59 WGDC Correction
238087E3 MAF Hz
238088FD AFR Map

Any chance we can get the info for logging maf_calcs and map_calcs???? In particular for 555900006 :)

Can this be updated for the 2011 USDM addresses?

Yes, also I have been trying to log with evoscan and apperantly I have the wrong address for TPS, will not open up any logs for me. Anyone know the different address for TPS.. 2011 USDM,

2011

V1

2011

V2

2012

So I tried V1 and V2 for TPS, changed it in evoscan then tried to load my logs that I had done. I keep getting the error "Power/Torque graph warning: throttle position sensor(TPS)>80 or missing Accelerator Pedal Position(APP) >80." Then it looks like it loads but there is no data displayed.... Cant seem to figure this out?

Go direct to the .csv and read it. Chances are, you'll spot what's going on in there.

Post up an excerpt if you're stuck. {thumbup}

Rich

Here is the log file, just rename to .csv extension. I looked in there but honestly even with all the reading I have been doing about logging on the forum I still dont understand all of this especially what I am looking at inside the excel file. Thanks

Bryan, what's the difference between the two versions?

Thanks for posting these up!

Well looks like you are logging nothing correctly, none of your values make sense. Think you are using the wrong drop down vehicle in evoscan. Did you copy what razor posted and put it in your evoscan data file xml? I posted my file, just put it in your evoscan datasettings folder and pick 2011 RA from the dropdown menu....just rename to xml.....also for further reference, if your speed is reading 320...you might have a logging issue.

I did this, so do I have to go out and log again or should I be able to load the existing logs that I did before doing this.

You have to go out and log again... although you can probably just switch ignition to ON, log, press the throttle a few times, then switch off. No need to even start the car. :)

It'll tell you if your TPS is right. If that's right, the rest should have come along for the ride too.

Rich

OK went out and did a log with the car not even on, as I was pressing on gas pedal I could see TPS changing from 15 to 87, so seems to be working, but when trying to open up the log in graphs/logs I got that same error again. Opened up log in excel and looks better.

Yep, looks good from a data perspective.

My Evoscan doesn't whinge like that though.

Once it loads, do you have check boxes on the left hand side? Can you tick them and see graphs?

Rich

Yeah i have the boxes, but on the grid tab if check any of them nothing comes up on any of the graphs. On the chart tab if i scroll all the way to the bottom it will show some stats on a graph when tick some of the items on left hand side. Shouldnt everything populate once loaded. I am kind of going off the sample logs that were provided in evoscan, mine doesnt have any of that data?

Well first from your sample log, you didn't turn the car on, so you have no real data, just baro, psig, and tps, everything else is just 0. Evoscan will only make graphs on what you select. Try to find the how to's online, or go to the evoscan website, you will find a lot of good information on how to log your car and analyze the logs.

Noob question... but how would I add the 2011 addresses to EvoScan? Or do I need to edit them one by one?

Just use the file I posted few posts ago and put it in the datasettings folder.....and bobs your uncle.

First off thanks Bryan for the addresses, now my evoscan works correctly{thumbup}
Second, I'm having some trouble getting my wideband (AEM) to log correctly. I've been trying for the last 4 hours or so to figure out the eval to place in to get my WB dialed in.

So far I know my analog voltage reads
0.00v = 10afr.
.125v = 10.25afr
2.262v = 14.7afr
4v = 18afr

Now these are from the AEM manual that is for my gauge. I haven't yet read them with a multimeter but I'm confidant I have a good ground.

I'm sorry if this has been covered before, I've read the the how-to by expirmnt and followed the best I could. Now I'm asking for help.

Could someone break down the equation for me so I can figure this out please.

Cheers

That just looks like...

AFR = ( volts * 2 ) + 10


You mentioned Evoscan. The only way I know that can log analogue voltage is if you patched in to the rear o2 sensor (ie. an ECU pin). Not sure about that, as I've never used it.



Tactrix standalone logging can do it via "pin 8" input, direct into the OP2.0. If you use that, the OP2.0 ADC scales to millivolts (so the value ranges from 0 to 5000). You'd therefore use...

Rich

There are two different AEM UEGO formulas that you may use, depending on the gauge. I'm not sure if there was a difference based on production date, or what, but there it is all the same. If the one Rich posted doesn't work for you, this is the one I'm running, the AEM analog 30-5130 gauge to pin8, and logging correctly with this:

type=adc
paramname=AFR
paramid=8
scalingrpn=x,0.002375,*,7.31,+

Forgot to mention that I did connect my analog signal wire from the gauge to the rear o2 sensor. Then I disabled the rear o2 in ecuflash. My rom has the DTC disables in them. But when in evoscan I need to enter a formula in the eval... I dont have that formula.

Chi-town are you spliced into a obd2 extension cable.. Pin 8. or are you connected through the rear 02 sensor?

Rich, if I get the obd2 extention cable as you have and splice into pin 8.. can you still log through evoscan with the computer, or only the standalone option with the mini SD?

I prefer to have my computer in the car and log that way. THats why I choose to go through the rear 02. I will try the fromula rich gave me and see what happens.

Thanks guys

Rich your formula is right when I work it out on paper. But when I plug it into the eval : (x*2)+10 then logging only shows 10. and the decimal places are moving but thats it.

Address: 23808675 -- this address is the one I use for the rear o2 sensor as described in Razolabs addresses... Not sure if this is the correct one, but the numbers are moving in sync with my throttle.. so that tells me the address is probably correct and the formula is off.

Note I also tried a few different formulas from other threads like 2*(x/1023)+10 with now success.

Just log x.... then review the results. Forget the formula to start with. :)

Also, make sure you're logging as 1-byte, not 2-byte. It's an odd address...

Rich

Thanks Rich,

I got the evoscan part of it working now. I just have to get points for my slope and I'll be in business. Thanks for your help.

Yeah, once you've logged raw "x", you can add an extra column in Excel with a formula. That means you can try it all out in your log results spreadsheet first. Once your Excel formula looks exactly right, you'll know what you have to do in the logging setup.

Glad it's coming good!

Rich