Evo X Logging
Mar 21, 2012, 04:06 PM
#1096
Evolved Member
Golden very kindly sent me the following... for...
53610013 - 2009/2010 ADM/EDM Ralliart
Cheers,
Rich
53610013 - 2009/2010 ADM/EDM Ralliart
Code:
23808778 Load 23808750 2ByteRPM 23808722 PSIG / Boost 23808A57 Knock Sum 238088A4 STFT 23804573 LFTF Idle 23804575 LTFT Cruise 238088B5 LTFT in use 2380877E Load (MIVEC) and (Timing if IAT GT 75F) 23808701 TPS 238095ED Accel Pedel Position 23808A13 TimingAdv 23808B61 ActiveWGDC 23808661 Intake Air Temp 23808647 Coolant Temp 23808667 Manifold Air Temp 2380AA74 IPW 23808F6C MAF Volts 23809516 INVVT (Target) 23809522 EXVVT (Target) 2380954E INVVT (Actual) 2380955A EXVVT (Actual) 238087F3 Speed 238086F7 Battery 2380AA39 Barometer 23808A5D knock_adc_processed 2380AA6B knock_base 2380AA67 knock_var 2380AA6D knock_change 23808A6B knock_dynamics 2380812D knock_flag 23808671 Front O2 23808675 Rear O2 238045C5 Cruise Light 23808B5F WGDC Correction 238087E7 MAF Hz 23808901 AFR Map
Rich
Apr 23, 2012, 04:28 AM
#1097
Evolved Member
Golden also sent me these...
58030005 - 2012 USDM Ralliart
Rich
58030005 - 2012 USDM Ralliart
Code:
238087BC Load 23808794 2ByteRPM 23808766 PSIG / Boost 23808A9B Knock Sum 238088E8 STFT 23804573 LFTF Idle 23804575 LTFT Cruise 238088F9 LTFT in use 238087C2 Load (MIVEC) and (Timing if IAT GT 75F) 23808745 TPS 23809645 Accel Pedel Position 23808A57 TimingAdv 23808BB1 ActiveWGDC 238086A3 Intake Air Temp 23808687 Coolant Temp 238086A9 Manifold Air Temp 2380AB6C IPW 23808FC4 MAF Volts 23809566 INVVT (Target) 23809572 EXVVT (Target) 2380959E INVVT (Actual) 238095AA EXVVT (Actual) 23808837 Speed 2380873B Battery 2380AB31 Barometer 23808AA1 knock_adc_processed 2380AB63 knock_base 2380AB5F knock_var 2380AB65 knock_change 23808AAF knock_dynamics 23808137 knock_flag 238086B5 Front O2 238086B9 Rear O2 238045C5 Cruise Light 23808BAF WGDC Correction 2380882B MAF Hz 23808945 AFR Map
Apr 24, 2012, 06:04 PM
#1099
Evolved Member
...and the 2012 SST (MR) too, from the looks of it.
For 2012, Mitsubishi has done a bang-up job of aligning all their ROM versions. Someone in there likes us!
Rich
For 2012, Mitsubishi has done a bang-up job of aligning all their ROM versions. Someone in there likes us!
Rich
Aug 27, 2012, 09:11 PM
#1104
Are you sure that these IDs are accurate. Some of them do not match to the location IDs in this table.
http://evoecu.logic.net/wiki/MUT_Requests
For example, the Golden's TPS location is 23808745, but if you look at the MUT request table it says it is 17 (1 for the row and 7 for the column). Looking up 17 in the 2012 ROM MUT table give us 23808851. Are the MUT_Requests in the wiki table off?
TIA
http://evoecu.logic.net/wiki/MUT_Requests
For example, the Golden's TPS location is 23808745, but if you look at the MUT request table it says it is 17 (1 for the row and 7 for the column). Looking up 17 in the 2012 ROM MUT table give us 23808851. Are the MUT_Requests in the wiki table off?
TIA
Aug 28, 2012, 01:56 PM
#1106
Newbie
Join Date: Jan 2012
Location: HELL
Posts: 97
Likes: 0
Received 0 Likes
on
0 Posts
I came with the same conclusion on some ID and I wasnt able to end with a logic conclusion...
Mart
Mart
Are you sure that these IDs are accurate. Some of them do not match to the location IDs in this table.
http://evoecu.logic.net/wiki/MUT_Requests
For example, the Golden's TPS location is 23808745, but if you look at the MUT request table it says it is 17 (1 for the row and 7 for the column). Looking up 17 in the 2012 ROM MUT table give us 23808851. Are the MUT_Requests in the wiki table off?
TIA
http://evoecu.logic.net/wiki/MUT_Requests
For example, the Golden's TPS location is 23808745, but if you look at the MUT request table it says it is 17 (1 for the row and 7 for the column). Looking up 17 in the 2012 ROM MUT table give us 23808851. Are the MUT_Requests in the wiki table off?
TIA
Dec 21, 2012, 06:06 PM
#1107
Newbie
Join Date: Apr 2011
Location: Vic Australia
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
Guys I am learning to use IDa pro version 6.1.
Can you point me in the right direction to find the addresses for Evoscan to log?
My processor is very similar to the EvoX,
M32r Renesas, rom id is B3500005
Any hints appreciated
Can you point me in the right direction to find the addresses for Evoscan to log?
My processor is very similar to the EvoX,
M32r Renesas, rom id is B3500005
Any hints appreciated
Dec 23, 2012, 12:04 PM
#1108
Newbie
Join Date: Apr 2011
Location: Vic Australia
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
OK I am using the self help method and have no idea what I am doing
I have managed to get the fuel trims to log and coolant temp.
Still can't get the rpm to log though.......
EDIT;
Well I tried logging with EvoX CAN MUT111 and surprise, most things now log !
Am still trying to get the MAF and TPS working now to tune and display on Evoscan's power chart........
Knock sum is logging correctly so I can tune anyway
I have managed to get the fuel trims to log and coolant temp.
Still can't get the rpm to log though.......
EDIT;
Well I tried logging with EvoX CAN MUT111 and surprise, most things now log !
Am still trying to get the MAF and TPS working now to tune and display on Evoscan's power chart........
Knock sum is logging correctly so I can tune anyway
Last edited by salt36; Dec 23, 2012 at 04:38 PM.