Evo 6 Boost Logging - Mitsubishi Lancer Register Forum
 
 

Go Back   Mitsubishi Lancer Register Forum > Technical > ECU / Mapping

Reply
 
Thread Tools Rate Thread Display Modes
Old 13-07-2018, 14:07   #1
jaemess
Registered User
 
Join Date: Apr 2016
Posts: 17
Evo 6 Boost Logging

Hi all,

I have searched and couldn't find any definitive answer/s, so I am posting this thread in the hopes of finding one. Has anyone successfully logged boost on the evo 6 via MAP sensor (using evoscan), and if so, which pin on the E6 Ecu do i need to send the signal from the MAP to?

thanks!
jaemess is offline   Reply With Quote
Sponsored Links
Advertisement
 
Old 19-07-2018, 06:51   #2
rjwkerkhof
Registered User
 
Join Date: Mar 2016
My Car
Posts: 146
Following
rjwkerkhof is offline   Reply With Quote
The Following User Says Thank You to rjwkerkhof For This Useful Post:
jaemess (19-07-2018)
Old 20-08-2018, 00:59   #3
VR-4Squid
Registered User
 
Join Date: May 2003
Location: New Zealand
Car: CP9A Evolution V
Posts: 555
Also searching for this info, if I find out I'll share.
__________________
E39A vr-4 - Project 燃えないゴミ (Unburnable Junk) - Stolen!
VR-4Squid is offline   Reply With Quote
Sponsored Links
Advertisement
 
Old 20-08-2018, 17:17   #4
And
Registered User
 
Join Date: Dec 2005
Location: Bristol
Car: Evo VIII GSR, Black with red leather interior, Do-Luck wide arch kit, Rota GTR rims 265 tyres
My Car
Posts: 2,632
Send a message via MSN to And
If you wire the map sensor up to pin 75 you might be able to log mut 3C, that might work
And is offline   Reply With Quote
The Following User Says Thank You to And For This Useful Post:
rjwkerkhof (21-08-2018)
Old 28-08-2018, 06:06   #5
jaemess
Registered User
 
Join Date: Apr 2016
Posts: 17
i think this is for the evo 7-8 ecu? since their pinouts indicate lambda rear sensor -- in evo 6 ecu pin 75 is blank (not used)....
jaemess is offline   Reply With Quote
Old 28-08-2018, 07:33   #6
rjwkerkhof
Registered User
 
Join Date: Mar 2016
My Car
Posts: 146
Quote:
Originally Posted by jaemess View Post
i think this is for the evo 7-8 ecu? since their pinouts indicate lambda rear sensor -- in evo 6 ecu pin 75 is blank (not used)....
Hi Jeamess,

When going SD the map sensor should be connected to pin 75, the SD rom has rewritten code (my guess) to support the reading of the map sensor signal at pin 75.

There might be a possibility to do this the same for the none SD ceddy rom, there are already some tables defined for SD in this ROM.

In the coming weeks Ill try to hookup my GM 3 bar map sensor to pin 75 hoping my ECU can log the signal.

Kind regards,

Roy
rjwkerkhof is offline   Reply With Quote
Old 28-08-2018, 18:29   #7
And
Registered User
 
Join Date: Dec 2005
Location: Bristol
Car: Evo VIII GSR, Black with red leather interior, Do-Luck wide arch kit, Rota GTR rims 265 tyres
My Car
Posts: 2,632
Send a message via MSN to And
I've checked it this evening and it works on a standard rom with the sensor wired to pin 75. It works because all you are doing is asking the ecu what the value of the adc channel is that is connected to pin 75. To convert from the adc value (0 to 255 which is 0v to 5v) to kpa you'll need to know the conversion for the sensor you are using.
And is offline   Reply With Quote
The Following User Says Thank You to And For This Useful Post:
rjwkerkhof (29-08-2018)
Old 29-08-2018, 06:42   #8
rjwkerkhof
Registered User
 
Join Date: Mar 2016
My Car
Posts: 146
Quote:
Originally Posted by And View Post
I've checked it this evening and it works on a standard rom with the sensor wired to pin 75. It works because all you are doing is asking the ecu what the value of the adc channel is that is connected to pin 75. To convert from the adc value (0 to 255 which is 0v to 5v) to kpa you'll need to know the conversion for the sensor you are using.
Thanks And!

What address/request are you using to read out? Is it the 38 as defined in the evoscan ceddy xml already?
rjwkerkhof is offline   Reply With Quote
Old 29-08-2018, 06:55   #9
And
Registered User
 
Join Date: Dec 2005
Location: Bristol
Car: Evo VIII GSR, Black with red leather interior, Do-Luck wide arch kit, Rota GTR rims 265 tyres
My Car
Posts: 2,632
Send a message via MSN to And
No you'll need to use 3C
And is offline   Reply With Quote
Old 29-08-2018, 07:14   #10
jaemess
Registered User
 
Join Date: Apr 2016
Posts: 17
Thumbs up

Quote:
Originally Posted by rjwkerkhof View Post
Hi Jeamess,

When going SD the map sensor should be connected to pin 75, the SD rom has rewritten code (my guess) to support the reading of the map sensor signal at pin 75.

There might be a possibility to do this the same for the none SD ceddy rom, there are already some tables defined for SD in this ROM.

In the coming weeks Ill try to hookup my GM 3 bar map sensor to pin 75 hoping my ECU can log the signal.

Kind regards,

Roy
Thanks a bunch Roy! Kindly keep us posted once you've tried this.
jaemess is offline   Reply With Quote
Old 29-08-2018, 07:14   #11
jaemess
Registered User
 
Join Date: Apr 2016
Posts: 17
Quote:
Originally Posted by And View Post
I've checked it this evening and it works on a standard rom with the sensor wired to pin 75. It works because all you are doing is asking the ecu what the value of the adc channel is that is connected to pin 75. To convert from the adc value (0 to 255 which is 0v to 5v) to kpa you'll need to know the conversion for the sensor you are using.
Thanks And!! How do you use/request 3c address on ceddy rom once you connect to pin 75? A quick how to on how you set it up would be awesome. thanks and regards!

Last edited by jaemess; 29-08-2018 at 07:19..
jaemess is offline   Reply With Quote
Old 29-08-2018, 07:36   #12
And
Registered User
 
Join Date: Dec 2005
Location: Bristol
Car: Evo VIII GSR, Black with red leather interior, Do-Luck wide arch kit, Rota GTR rims 265 tyres
My Car
Posts: 2,632
Send a message via MSN to And
You request 3c in evoscan, just edit the map sensor that you have i.e. GM 3 BAR then change the MUT request from 38 to 3C that's it. If your map sensor isn't listed you'll need to calibrate it to get the kpa to volts conversion then modify the equation in evoscan to suit
And is offline   Reply With Quote
The Following User Says Thank You to And For This Useful Post:
rjwkerkhof (29-08-2018)
Old 29-08-2018, 10:15   #13
rjwkerkhof
Registered User
 
Join Date: Mar 2016
My Car
Posts: 146
Quote:
Originally Posted by And View Post
You request 3c in evoscan, just edit the map sensor that you have i.e. GM 3 BAR then change the MUT request from 38 to 3C that's it. If your map sensor isn't listed you'll need to calibrate it to get the kpa to volts conversion then modify the equation in evoscan to suit
Good to know that it needs to be 3C instead of 38, any idea why it was set to 38 by ceddy?

Btw do you also know the request for pin 44 on the E6 ECU? My map switch is connected to it but wont log in evoscan.
rjwkerkhof is offline   Reply With Quote
Old 29-08-2018, 11:01   #14
jaemess
Registered User
 
Join Date: Apr 2016
Posts: 17
so if i use omni 4 bar (which is listed) all i have to do is change the request to 3C and thats it? nothing else? thanks!!!
jaemess is offline   Reply With Quote
Old 29-08-2018, 11:31   #15
rjwkerkhof
Registered User
 
Join Date: Mar 2016
My Car
Posts: 146
Quote:
Originally Posted by jaemess View Post
so if i use omni 4 bar (which is listed) all i have to do is change the request to 3C and thats it? nothing else? thanks!!!
According to And yes! Only need to know if he tested it on a E5/6 Ecu or on a E8 ecu
rjwkerkhof is offline   Reply With Quote
Mitsubishi Lancer Register
Sponsored Links
Advertisement
 
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT. The time now is 01:15.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.