Got a few questions again I would like to make sure I'm doing it right and I have the correct source of information.

Is the MUT request list from evowiki still a valid source to match with newer car like the X and the RA?

Assuming 3efc0 is the correct adress for the RA, when I compare the MUT request list, my MUT table and what's in EvoScan using the Mode 23 2009 USDM EVOX RA the value are not right. Logging seems to report good value for some even if the adresse don't match.

Maybe I'm reading the table upside down so here's what I understood based on a post from Acamus.

As an example SFT show 0F so I go to the line 0 row F and the value there should be the SFT adress to put in EvoScan (adding a 23 in front).

Is that correct?

 

yup u got it

 

Thanks tephra.

Well it's bit different then coding in Visual Basic but there's still a logic to it.

I'm just really surprised how incorrect are the value in EvoScan but that they still lead to possible value for some items

At least I found a coulpe of matching value but I just wanted to be sure before going ahead and correcting the Data.xml file.

I really appreciate having a ECU guru saying, yup it's ok

Should I change the Fuction as well when they don't match the formula from the wiki or just changing to the right adress should do the trick?

I feel bad with all those questions when for you it's obvious lol

 

well your only logging, cant really break anything if you get it wrong.

with various memory addresses, a lot of stuff is duplicated so that could be 1 reason.

or your mut table entry is wrong..

simple check would be for TimingAdv = MUT06 - that should match the timing adv in evoscan

 

Yup that was one of those that match so I'm happy to see I got it right I'll fix what doesn't match and give it a shot.

Thanks I really appreciate the help.

 

Oh I see that some values don't match period and they are 1 byte but some are listed in 2 bytes response, I guess there's another trick I have to learn and the value there are right hahah.

I'm actually enjoying that lol. Time to find some 2 bytes instruction and how to.

 

Tephra,

Anyway you can find mode23 addresses for 55580005. Seem to not be the same as 55570005.

Find rom and XML here:

http://norcalmotorsports.org/users/b...ch/2010_evo10/

Thanks!

- Bryan

 

posted + emailed :P

 

You da man!

- Bryan

 

quick 1 off logging question;
the ecu pin payout has 2 intake air temp sensors that cne be logged, is it:
ambient & maf or maf & intake manifold temp?
i forgot my laptop at home and i think it says in evoscan
thanks in advance

 

I had a weird issue today with EvoScan 2.7 Beta 5.

We tried a pull in 3rd gear, and I managed to grab only 5 lines of data.
I was in the mode Mode23 Evo X and data was coming fine.
I don't think I was loggin to much stuff, I had:
TPS, RPM, Load, Timing, ActiveWGC, knock, PSIG, LTFT Idle, LTFT Cruise, MAF Voltage.

Is this way too much or something is wrong with 2.7 Beta 5?

LogEntrySeconds
0.13521
2.24072
5.34561
6.4691
7.58683

It's pretty clear there's big hole in there.
Any help would be greatly appreciated.

EDIT: By searching a bit deeper, I found a post saying you shoul avoid logging CAN data but I was not logging CAN stuff in the Items Data log section. Everything in there is what come by default when you select Mode23 EvoX.

Thanks!

 

The latest and greatest EVOscan software will be out on or near this Monday! It provides basic mode23 logging for the 2010 EVO and Ralliart as well as the ability to read and clear check engine lights!

Currently the software will log the following:

RPM
Load
Timing Advance
PSIG
Knock Sum
External wide band (digital output from gauge)
TPS
Manifold Air Temp
ECT (coolant temp)
IAT (intake air temp)
speed

I have not personally verified all of these yet... just got the software bugs worked out with Hamish, and will be testing the logging out Today.

Later,

Keith

 

I need help...

I enabled mode23 on my car with my old work laptop. I don't have that laptop or the definitions files from it.

I'm now trying to recreate the definition file, but I can't seem to get it right.

I've read the ECU and saved it off to hex. But I can't read it until I get mode23 enabled.

I tried updating the xml file with the information on the front post but that alone doesn't seem to be working or I'm doing it wrong.

Any advice?

 

Yup I can confirm that it's working fine on my 2010, and those DTC function are pretty nice. The only issue I have is with my AEM UEGO, it seems to always read zero. I tried 2.5, 2.6 and 2.7 beta 5 they all work fine.

I'll give a shot at re-installing 2.7 again and hopefully it will work

 

Not sure I follow you.
You can read a ROM (hex file) even if mode23 is not in your xml file.
You just won't see the option for mode23 but since you already enabled it.

The only time you won't be able to read a ROM is if you don't have the definition for that rom ID but not because one item definition is missing from the XML.

Could you clarify a bit your question? What's the rom ID?