Evo X Logging
#496
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
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
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.
#498
Evolved Member
Join Date: Mar 2008
Location: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Posts: 730
Likes: 0
Received 3 Likes
on
2 Posts
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.
#499
Former Sponsor
iTrader: (4)
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)
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)
#501
Evolving Member
iTrader: (11)
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.
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.
#502
EvoM Guru
iTrader: (50)
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?
IDC probably is a 10-15% overestimate like on previous Evos.
#504
Evolving Member
iTrader: (11)
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.
#505
Evolving Member
iTrader: (3)
Join Date: May 2008
Location: Utah
Posts: 472
Likes: 0
Received 0 Likes
on
0 Posts
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)
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
#506
Newbie
Join Date: Oct 2008
Location: French Polynesia
Posts: 52
Likes: 0
Received 0 Likes
on
0 Posts
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
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
#507
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
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
#509
Evolved Member
iTrader: (6)
You should get a wideband installed to see what your AFR is.
#510
Newbie
Join Date: Oct 2008
Location: French Polynesia
Posts: 52
Likes: 0
Received 0 Likes
on
0 Posts
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
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