ECUFlash / Evoscan / Mitsulogger Questions
Aug 5, 2014, 08:42 PM
#1576
Evolved Member
Anyone know if Evoscan will run on a Windows CE6.2 device?
Aug 7, 2014, 12:49 PM
#1578
Newbie
Join Date: Nov 2011
Location: Serbia
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
Aug 8, 2014, 03:58 AM
#1579
Newbie
Join Date: Jun 2014
Location: greece
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
hello , could anyone confirm this?
i have an openport cable 1.3 , and the white reflash connector is different in the outlander , it wont fit , it has two wires one green/yellow and one purple , which one should i splice and connect to the openport cable?
in this thread one guy said its the green wire
https://www.evolutionm.net/forums/ot...l#post11275212
my outlander has an evo 8 ecu and evo 8 motor , which ecu pin corresponds to the white/reflash connector single cable in an evo 8 ecu , so i can trace it back to the ecu if my connector is wrong?
thanx
i have an openport cable 1.3 , and the white reflash connector is different in the outlander , it wont fit , it has two wires one green/yellow and one purple , which one should i splice and connect to the openport cable?
in this thread one guy said its the green wire
https://www.evolutionm.net/forums/ot...l#post11275212
my outlander has an evo 8 ecu and evo 8 motor , which ecu pin corresponds to the white/reflash connector single cable in an evo 8 ecu , so i can trace it back to the ecu if my connector is wrong?
thanx
Aug 12, 2014, 09:37 PM
#1580
Evolved Member
https://docs.google.com/file/d/0B0k8...9uXzk3MGM/edit
I just got my Tactrix cable in the mail and so far works perfectly.
I read my rom. Does this look stock? Reason I ask is the speed limiter. Thought it was supposed to be lower than 510. Makes me wonder if my car is less than the stock I was led to believe. I hope this link works.
Thanks for any input.
I just got my Tactrix cable in the mail and so far works perfectly.
I read my rom. Does this look stock? Reason I ask is the speed limiter. Thought it was supposed to be lower than 510. Makes me wonder if my car is less than the stock I was led to believe. I hope this link works.
Thanks for any input.
Aug 17, 2014, 10:24 PM
#1581
Newbie
Join Date: Nov 2011
Location: Serbia
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
Aug 19, 2014, 01:09 AM
#1583
Newbie
Join Date: Nov 2011
Location: Serbia
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
Give me your email and I will send you my ROM, you will see better than me definitely. Only what I know it seems that function doesn't work anyone
Oct 15, 2014, 01:21 AM
#1585
Newbie
Join Date: May 2012
Location: Glendale, AZ
Posts: 2
Likes: 0
Received 0 Likes
on
0 Posts
having problem with evoscan starts loggin then stops v2.9.0092 Evo 8 2003
what could it be?
uninstall evo sacn and installed it already....
I was told not to take pin 9
anyhelp
what could it be?
uninstall evo sacn and installed it already....
I was told not to take pin 9
anyhelp
Oct 25, 2014, 11:46 AM
#1586
Evolved Member
iTrader: (31)
Join Date: Jan 2007
Location: Under my car
Posts: 766
Likes: 0
Received 0 Likes
on
0 Posts
I need help, I tried to get my Omni 4 Bar to start logging on EvoScan and I have the setting all correct from what the tuner said but I have not got it to start logging. I am using the 4 bar and have the gauge reading -30 and max is 50 as I am using a AEM 50psi Boost gauge. Can someone help me with what I could be doing wrong. I am using EvoScan 2.8 as I was having issues with 2.9
RequestId-38
Eval-0.2369*-14.7
Unit-psig
Response bytes-1
Gauge Min=-30
Gauge Max=50
Chart Min=-30
Chart Max=50
Scaling Factor=1
RequestId-38
Eval-0.2369*-14.7
Unit-psig
Response bytes-1
Gauge Min=-30
Gauge Max=50
Chart Min=-30
Chart Max=50
Scaling Factor=1
Oct 25, 2014, 12:40 PM
#1587
I need help, I tried to get my Omni 4 Bar to start logging on EvoScan and I have the setting all correct from what the tuner said but I have not got it to start logging. I am using the 4 bar and have the gauge reading -30 and max is 50 as I am using a AEM 50psi Boost gauge. Can someone help me with what I could be doing wrong. I am using EvoScan 2.8 as I was having issues with 2.9
RequestId-38
Eval-0.2369*-14.7
Unit-psig
Response bytes-1
Gauge Min=-30
Gauge Max=50
Chart Min=-30
Chart Max=50
Scaling Factor=1
RequestId-38
Eval-0.2369*-14.7
Unit-psig
Response bytes-1
Gauge Min=-30
Gauge Max=50
Chart Min=-30
Chart Max=50
Scaling Factor=1
These settings look good for Omni4 and Evoscan.
Have you checked:
(a) MUT38 table entry in your ROM - The address may be wrong. Go to Google and search for the following: evom (your rom id #) mut table
That should get you the address you need in MUT 38. If not, post your rom id and we can help you find the right address. If the MUT38 address is wrong correct in ECUFlash and flash it back to your ECU.
(b) If the MUT38 address is correct for your ROM it means you are not getting a signal from sensor to the ECU.
Throw a volt meter across the sensor plug to see if you are getting 5V to the sensor. Check the continuity of the signal cable back to the ECU input pin.
Check the voltage at the ECU pin from the sensor - should be around 2V.
(c) If the signal is good at the ECU input pin, then it means the ADC input circuit is fried on your ECU. Find an alternate ADC input on a different pin that is not being used. Rewire sendor, change MUT address to read that ADC input and you are done.
Oct 25, 2014, 12:45 PM
#1588
Evolved Member
iTrader: (31)
Join Date: Jan 2007
Location: Under my car
Posts: 766
Likes: 0
Received 0 Likes
on
0 Posts
These settings look good for Omni4 and Evoscan.
Have you checked:
(a) MUT38 table entry in your ROM - The address may be wrong. Go to Google and search for the following: evom (your rom id #) mut table
That should get you the address you need in MUT 38. If not, post your rom id and we can help you find the right address. If the MUT38 address is wrong correct in ECUFlash and flash it back to your ECU.
(b) If the MUT38 address is correct for your ROM it means you are not getting a signal from sensor to the ECU.
Throw a volt meter across the sensor plug to see if you are getting 5V to the sensor. Check the continuity of the signal cable back to the ECU input pin.
Check the voltage at the ECU pin from the sensor - should be around 2V.
(c) If the signal is good at the ECU input pin, then it means the ADC input circuit is fried on your ECU. Find an alternate ADC input on a different pin that is not being used. Rewire sendor, change MUT address to read that ADC input and you are done.
Have you checked:
(a) MUT38 table entry in your ROM - The address may be wrong. Go to Google and search for the following: evom (your rom id #) mut table
That should get you the address you need in MUT 38. If not, post your rom id and we can help you find the right address. If the MUT38 address is wrong correct in ECUFlash and flash it back to your ECU.
(b) If the MUT38 address is correct for your ROM it means you are not getting a signal from sensor to the ECU.
Throw a volt meter across the sensor plug to see if you are getting 5V to the sensor. Check the continuity of the signal cable back to the ECU input pin.
Check the voltage at the ECU pin from the sensor - should be around 2V.
(c) If the signal is good at the ECU input pin, then it means the ADC input circuit is fried on your ECU. Find an alternate ADC input on a different pin that is not being used. Rewire sendor, change MUT address to read that ADC input and you are done.
Oct 25, 2014, 01:20 PM
#1590
Evolved Member
iTrader: (31)
Join Date: Jan 2007
Location: Under my car
Posts: 766
Likes: 0
Received 0 Likes
on
0 Posts
That correct, when I was reading I was missing one part to the Equation from what I can see. My code currently is 0.2369*-14.7 and it needs to be 0.2369*x-14.7 if I am reading everything correctly.