Notices

Evo X Logging

Thread Tools
 
Search this Thread
 
Old Jul 1, 2009 | 01:23 AM
  #496  
acamus's Avatar
Evolved Member
 
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
53040010 found some good stuff to log maybe something is already known:

808C94 Number of trouble codes
808774 Calculated engine load value: X*100/255 [0 - 100%]
80863A Engine coolant temperature : X-40 [-40C - 215C]
808890 Short Fuel Trim: (X-128) * 100/128 [-100% - 99.22%]
8088A2 Long term fuel: (X-128) * 100/128 [-100% - 99.22%]
808714 MAP: X [0kPA-255kPa]
8087D8 MAF air flow rate: ((256*A)+B) / 100
8086F0 Throttle position: [0-100%]
808660 Front O2 Voltage
808664 Rear O2 Voltage
804C8E Distance travelled on CEL


MUT commands sub 40400 - unk_808C4C = 0
OBDII routine is sub 95788 - unk_808C4C = 1
0x10 init routine - unk 808C4C = 2
So you were close tephra to get MUT communication

Moreover there is MUT over OBDII (Hybrid mode via Mode A0) at 0x95AB8
0x93FA4 is Freeze DTC Array
and 808C41 & 0x3 clears trouble codes
ECU_OPTIONS_2 & 0x6 - rearO2 test

Hope it helps

Last edited by acamus; Nov 4, 2009 at 10:14 PM.
Reply
Old Jul 1, 2009 | 05:43 AM
  #497  
tephra's Avatar
Thread Starter
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yeah I am looking into the rear02 stuff.

I should send you my lattest disasm..

I got a fair bit of the DTC stuff sort of figured out

SO MUCH code goddammit
Reply
Old Jul 1, 2009 | 06:41 AM
  #498  
acamus's Avatar
Evolved Member
 
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
I hope Hamish will read it as actuators are somewhere in MUT commands (sub 40400) and CAN30, CAN31 references same routines

Last edited by acamus; Nov 4, 2009 at 10:14 PM.
Reply
Old Jul 1, 2009 | 11:33 AM
  #499  
evo4mad's Avatar
Former Sponsor
iTrader: (4)
 
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
yep I read it with great interest I have added DTC and Actuator support for Openport 2.0 and Evo7/8/9

I already know about that MUT over OBDII, It is already implemented in EvoScan.. select "Hybrid" option, since about EvoScan version 2.0

EvoScan v2.6 Beta16
- FULL support for evo7/8/9 and openport2 USB cables.
- MUTII DTC support for op2
- OBDII DTC support for op2
- MUTII Actuator Support for op2
- Fixed openport2 freeze when vehicle was not plugged in.
- Minor Map Tracer enhancements.
- Minor Power graphing enhancement.
- Faster op2 datalogging
- Disabled multithreading by default, it is faster. (enable this from the logging menu if you want a more responsive UI)
Reply
Old Jul 1, 2009 | 11:50 AM
  #500  
evo4mad's Avatar
Former Sponsor
iTrader: (4)
 
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
Originally Posted by mrfred
it looks like EvoScan is not liking the "CALC" command in the Mode23 zone. The "&HLC" indicates that EvoScan is trying to convert "CALC".
oh yeah, I didn't add CALC support to the CAN protocol. I have now updated EvoScan v2.6 beta16 to include CALC requestid support, you can redownload beta16 now to get this supported.
Reply
Old Jul 1, 2009 | 12:15 PM
  #501  
MR. Tim's Avatar
Evolving Member
iTrader: (11)
 
Joined: Sep 2007
Posts: 432
Likes: 1
From: Greensburg, PA
Originally Posted by mrfred
What values do you get for APP and TPS when the car is stationary and idling? If you let me know this, I can fine-tune the APP and TPS conversion formulas a little more.

ok, it looks like EvoScan is not liking the "CALC" command in the Mode23 zone. The "&HLC" indicates that EvoScan is trying to convert "CALC" into an address, e.g. &HCALC. After thinking about it for a second, I've come up with a possible workaround. Try the attached Data.xml file when you get a chance.
Here is a 3rd gear pull from my way to work this morning using the last xml you posted yesterday. Getting closer on APP and TPS. IPW and IDC along with 2byte RPM now log also. Is IDC just about spot on or is there still a bit of overhead "buffer" like there traditionally was?
Attached Files
File Type: zip
3rd.zip (7.0 KB, 0 views)
Reply
Old Jul 1, 2009 | 07:37 PM
  #502  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by MR. Tim
Here is a 3rd gear pull from my way to work this morning using the last xml you posted yesterday. Getting closer on APP and TPS. IPW and IDC along with 2byte RPM now log also. Is IDC just about spot on or is there still a bit of overhead "buffer" like there traditionally was?
Could you let me know what values you get for APP and TPS when the car is idling?

IDC probably is a 10-15% overestimate like on previous Evos.
Reply
Old Jul 1, 2009 | 09:51 PM
  #503  
acamus's Avatar
Evolved Member
 
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Originally Posted by evo4mad
I already know about that MUT over OBDII, It is already implemented in EvoScan.. select "Hybrid" option, since about EvoScan version 2.0
Are you saying it is already working for CAN ECU's?
Reply
Old Jul 2, 2009 | 02:06 PM
  #504  
MR. Tim's Avatar
Evolving Member
iTrader: (11)
 
Joined: Sep 2007
Posts: 432
Likes: 1
From: Greensburg, PA
Originally Posted by mrfred
Could you let me know what values you get for APP and TPS when the car is idling?

IDC probably is a 10-15% overestimate like on previous Evos.
Here is a log of some idle time. It is a cold start from after work today. The gap in the middle was my ride home so i deleted it. The small portion at the end was some idle time before i shut the car off. I didnt know if the cold start idle would skew the numbers so thats why i did it like that.
Attached Files
File Type: zip
Idle.zip (69.6 KB, 0 views)
Reply
Old Jul 2, 2009 | 08:02 PM
  #505  
criptballer's Avatar
Evolving Member
iTrader: (3)
 
Joined: May 2008
Posts: 472
Likes: 0
From: Utah
Originally Posted by evo4mad
yep I read it with great interest I have added DTC and Actuator support for Openport 2.0 and Evo7/8/9

I already know about that MUT over OBDII, It is already implemented in EvoScan.. select "Hybrid" option, since about EvoScan version 2.0

EvoScan v2.6 Beta16
- FULL support for evo7/8/9 and openport2 USB cables.
- MUTII DTC support for op2
- OBDII DTC support for op2
- MUTII Actuator Support for op2
- Fixed openport2 freeze when vehicle was not plugged in.
- Minor Map Tracer enhancements.
- Minor Power graphing enhancement.
- Faster op2 datalogging
- Disabled multithreading by default, it is faster. (enable this from the logging menu if you want a more responsive UI)

hey hamish, for those of us that are logging the X, do we need to change the BAUD rate or anything? why did we lose so many parameters? there was a lot more on the previous one. thanks
Reply
Old Jul 3, 2009 | 03:37 PM
  #506  
EVOXSILVER's Avatar
Newbie
 
Joined: Oct 2008
Posts: 52
Likes: 0
From: French Polynesia
Hi,
I have 3 questions:

First: In evoscan when i try to playback in real time one of my log, i have an error message "Input string was not in a correct format. Couldn't store <2281,25> in USAMode23RPM Column. Expected type is Double."
How can i solve this?

Second: When i open my log file in Graph it works fine but when i click map tracer it won't show anything in the cells. I've noticed that load is scaled improperly 0 to 100 and i believe it should be 0 to 320.
How can i make map tracer to work?

Third: I have bad knock (6 knock counts at 6500+) how should i prevent from knock?
I have attached the log.

Thanks
Attached Files
File Type: pdf
Log EVOX.pdf (15.7 KB, 0 views)
Reply
Old Jul 3, 2009 | 05:30 PM
  #507  
LaXGSR's Avatar
Evolved Member
 
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
Originally Posted by EVOXSILVER
Hi,
I have 3 questions:

First: In evoscan when i try to playback in real time one of my log, i have an error message "Input string was not in a correct format. Couldn't store <2281,25> in USAMode23RPM Column. Expected type is Double."
How can i solve this?

Second: When i open my log file in Graph it works fine but when i click map tracer it won't show anything in the cells. I've noticed that load is scaled improperly 0 to 100 and i believe it should be 0 to 320.
How can i make map tracer to work?

Third: I have bad knock (6 knock counts at 6500+) how should i prevent from knock?
I have attached the log.

Thanks
Not sure about questions 1 and 2, but to reduce your knock, try lowering your timing a bit in that rpm/load range. It looks like your car only wants to run 15-16 degrees of timing there. You could also try lowering the boost a bit by lowering the passive WGDC at high rpm.
Reply
Old Jul 3, 2009 | 07:47 PM
  #508  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
Originally Posted by EVOXSILVER
Third: I have bad knock (6 knock counts at 6500+) how should i prevent from knock?
I have attached the log.

Thanks
What gear was that log? Also, what does your AFR look like and what gas are you running? Your IGN timing already looks pretty low to me.
Reply
Old Jul 3, 2009 | 08:00 PM
  #509  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Originally Posted by EVOXSILVER
Hi,

Third: I have bad knock (6 knock counts at 6500+) how should i prevent from knock?
I have attached the log.

Thanks
Since we do not know your AFR, then your best off if you pull a degree from 6500 rpm to redline from load cell 200 to 320. That should lower your knock to about 1-2 counts. If it does not, then pull another degree.

You should get a wideband installed to see what your AFR is.
Reply
Old Jul 3, 2009 | 10:19 PM
  #510  
EVOXSILVER's Avatar
Newbie
 
Joined: Oct 2008
Posts: 52
Likes: 0
From: French Polynesia
Thank you very much for your answers.
My pull was in 3rd gear.
About the gas i don't really know (small island should be equivalent to 91.
I have the AEM wideband but honestly i'm waiting for tephra to finish with his O2 sensor mod that way i won't have to drill to install a new bung for the extra sensor.
I've been trying to lower the timing in the load range which knock occurs and it worked for about 2 counts of knock.
I have a EBC so would it make any changes to reduce passive WGDC?
What do you guys think about the log (Boost, Load, IPW etc...)
Thanks
Reply



All times are GMT -7. The time now is 07:50 PM.