Evo X Logging
Jun 15, 2009 | 08:12 PM
#346
Thread Starter
EvoM Guru
iTrader: (6)
Joined: Mar 2007
Posts: 9,486
Likes: 66
From: Melbourne, Australia
Please do - although as I said I am not sure how quickly the sensor reacts because of the heat soaking nature of the I/M.
Code:
RPM PSIG I* KS LOAD VSS IAT CAT 4566 18.58 15 0 224 60 14 31 4781 20.76 14 1 242 60 14 31 4863 21.58 12 1 246 60 13 31 5023 21.63 13 0 245 60 13 31 5140 21.49 14 0 241 60 13 31 5320 21.34 15 0 236 60 13 31 5394 20.76 17 0 232 60 13 31 5589 20.23 18 0 226 60 13 31 5691 19.65 18 0 223 60 13 30 5843 19.41 18 0 222 60 13 30 5957 19.12 18 0 221 60 13 30 6097 18.78 18 0 219 60 13 30 6183 18.44 18 0 216 74 13 30 6355 17.52 18 2 212 74 13 30 6394 12.39 21 1 155 74 13 30
Jun 15, 2009 | 08:34 PM
#347
Evolved Member
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
Thanks guys! I'll try out the updated Data.xml tomorrow night. Tephra, in the log you posted, which one is manifold temperature, so I can compare my results. Thanks!
HiBoost, it would be great if you could take logs too for reference. I'll post up my results as well.
HiBoost, it would be great if you could take logs too for reference. I'll post up my results as well.
Jun 16, 2009 | 12:20 AM
#349
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 130
From: Tri-Cities, WA // Portland, OR
Updated mode 23 Data.xml file attached for 52680015-20 USDM GSRs. WGDC values have been verified, and have added entries to log all the different loads.
Last edited by mrfred; Jun 16, 2009 at 04:50 AM.
Jun 16, 2009 | 10:40 AM
#354
dont mind the stupid question but, whats the target AFR table for?
also, has anyone made their own RS232 cable to log with evoscan, i'm attempting to do that today, but my comport on my laptop doesnt work, so now i have to buy a USB to comport cable.anyone done this yet?
also, has anyone made their own RS232 cable to log with evoscan, i'm attempting to do that today, but my comport on my laptop doesnt work, so now i have to buy a USB to comport cable.anyone done this yet?
Jun 16, 2009 | 10:49 AM
#355
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 130
From: Tri-Cities, WA // Portland, OR
Its the target AFR that the ECU uses to set IPW. When the car is in open loop, it comes from the fuel tables. When the car is in closed loop, its set at 14.7:1. Its not the actual AFR though. A wideband is needed to measure actual AFR. AFRMAP is just a tool to see how the target AFR is comparing to actual AFR.
Jun 16, 2009 | 11:01 AM
#356
can you put the wideband back in the data.xml file? 
Its the target AFR that the ECU uses to set IPW. When the car is in open loop, it comes from the fuel tables. When the car is in closed loop, its set at 14.7:1. Its not the actual AFR though. A wideband is needed to measure actual AFR. AFRMAP is just a tool to see how the target AFR is comparing to actual AFR.
Jun 16, 2009 | 01:24 PM
#359
Evolved Member
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
All you need is a good USB to serial converter. I'm assuming this is to hook up your serial wideband o2 input? Look in the evo 9 ecuflash subforum for a thread discussing serial converters that work. I got mine off Amazon (it got pretty good reviews) and it seems to work fine. Radio shack also has some that will work.
Jun 16, 2009 | 02:40 PM
#360
Evolved Member
Joined: Oct 2002
Posts: 2,788
Likes: 1
Sorry to report but I tried logging a few days ago with my friends X again and had no luck. I was able to connect with EvoScan but the logging rate was like incredible slow. Also the values logged were innacurate it seems. Here is a little screen grab of the Excel output:
Everything else looks a mess. This is from the 52360016 rom. I tried to upgrade to the 52360018 rom but when I opened this rom in EcuFlash I seemed to be missing the rom meta data for the inherited rom id. I got this message:
[16:38:05.666] Unable to find parent metadata 52370024
So does someone have the meta data for the above inherited rom id?
And in terms of the data.xml, can anyone confirm the data.xml that comes with beta14 actually has the correct data.xml definitions for the 52360016 or 52360018 roms? As in did someone actually do it and it worked?
Also logging rate is one per second which is obviously practically unusable. Is there any effect com port settings or anything can make? I have log to file, no log to screen, disable mutli-threading, etc...
Does the baud rate in the OP 2.0 settings have any effect?
Everything else looks a mess. This is from the 52360016 rom. I tried to upgrade to the 52360018 rom but when I opened this rom in EcuFlash I seemed to be missing the rom meta data for the inherited rom id. I got this message:
[16:38:05.666] Unable to find parent metadata 52370024
So does someone have the meta data for the above inherited rom id?
And in terms of the data.xml, can anyone confirm the data.xml that comes with beta14 actually has the correct data.xml definitions for the 52360016 or 52360018 roms? As in did someone actually do it and it worked?
Also logging rate is one per second which is obviously practically unusable. Is there any effect com port settings or anything can make? I have log to file, no log to screen, disable mutli-threading, etc...
Does the baud rate in the OP 2.0 settings have any effect?