Evo X Logging - Page 3

SiC · Jun 2, 2009, 06:26 PM

The 53040007 addresses didn't match up on the JDM

tephra · Jun 2, 2009, 06:34 PM

send me the rom dude - ill work them out for you.

myforumname @ gmail.com

SiC · Jun 2, 2009, 06:42 PM

Quote:

Originally Posted by tephra

send me the rom dude - ill work them out for you.

myforumname @ gmail.com

Sent from hotmail!

Thanks

tephra · Jun 2, 2009, 07:03 PM

first post updated with XML's for some ROMID's.

You can use the zip in the 2nd page - but you will have to update the Hex Address's...

SiC · Jun 2, 2009, 07:04 PM

You ROCK!!

tephra · Jun 2, 2009, 07:07 PM

that 52360018 rom is a bit screwy SiC - the XML should work - but just be a bit cautious when you after you flash...

SiC · Jun 2, 2009, 07:12 PM

Quote:

Originally Posted by tephra

that 52360018 rom is a bit screwy SiC - the XML should work - but just be a bit cautious when you after you flash...

Yeah, I noticed I sent you an old ROM that we used in the old ECUFlash beta before it supported the correct checksum on the EvoX. I tested the address out with another ROM and it seems to work fine.

BTW, can I send you one more: JDM 52370024 (SST), this one didn't seem to all line up either.

Thanks again!

Deepseadiver · Jun 2, 2009, 07:14 PM

This is great news! When will I be able to use EVOscan with no problems? Or a "how to" log an evo X thread?

LaXGSR · Jun 2, 2009, 07:49 PM

Tephra, this worked great on a stock USDM GSR with 52680018. Looks like it's pulling a degree or two of timing up top above 6500 rpm's. How do I interpret the knock sum value - I see a few 1's and 2's up top. Is this a count like the evo 8/9 where 3 counts equals 1 degree, or does 1 count equal 1 degree roughly?

I've attached my log. Any chance of getting TPS and wastegate duty cycle? Thanks again

Hiboost · Jun 2, 2009, 08:13 PM

I'm pretty sure it's normally 3 counts = 1 degree but I think even 1 or 2 counts can pull 1 degree of timing. I'll let Tephra confirm that of course!

1-3 counts = 1 degree (minor knock, may not always occur in the same spot)
4-6 counts = 2 degrees
7-9 counts = 3 degrees
10+ counts = correct the knock ASAP!

I think usually 1-2 counts occasionally is livable, especially if pulling 1 degree of timing doesn't seem to clear it up at all. I have a TurboXS Knocklite and on it's most sensitive setting it won't trigger unless I hit 7+ counts. I can make it more sensitive by not revving it as high when I calibrate it for my base engine noise but I would rather only see it when it is definite knock.

tephra · Jun 2, 2009, 08:39 PM

yeah same is IX, so 3 KS = -1*

So 1KS = 0.35 timing retard.

You might see -1* with 2KS because of rounding etc..

Bob_tm · Jun 2, 2009, 08:56 PM

I will test log on 53040007 in two days.

SiC · Jun 2, 2009, 10:09 PM

Tephra, is the program you uploaded strictly for the 52680015 or can it be used with other ROM IDs too?

tephra · Jun 2, 2009, 10:40 PM

Any ROMID...

The XML changes allow the program to execute Mode23 commands.

The config file tells the program which memory addresses to retrieve.

tephra · Jun 2, 2009, 10:54 PM

updated post #1 with some details.

still need to test the new version of the app on my car b4 posting (you can still use the zip off page#2 if you want)

new version just has some minor enhancements.. (like waiting for you to plug the OP2.0 cable in etc etc)