Evo X Logging
#692
On Sunday I logged mode23 boost and the ZT2 boost with the medical grade Kavlico 3.5 bar MAP sensor I could not log the rpm with the ZT2 since the wire is not connected. I ran Evoscan and the ZT2 logger at the same time and logged the boost for the same 4th gear run. I compared the peaks and valleys of both boost curves and can confirm an almost exact overlap between the two.
I have compared the JDM MAP sensor to the GM 3-bar MAP sensor on my Evo 9 and they were very close.
Good to know that mode 23 boost is accurate
I have compared the JDM MAP sensor to the GM 3-bar MAP sensor on my Evo 9 and they were very close.
Good to know that mode 23 boost is accurate
#695
Evoscan Mode23 XML for EDM
Hi there!
I am new to using evoscan, bought the license a couple of weeks ago and I am ready to give it a go.
However I could not find Mode23 for EDM in evoscan.
Someone was mentioning that I can use the Mode23 for JDM, is this ok for my Evo X EDM MR?
I know I have to get some help in another thread on enabling Mode23 for my (ROMID=53050006).
/L-O
I am new to using evoscan, bought the license a couple of weeks ago and I am ready to give it a go.
However I could not find Mode23 for EDM in evoscan.
Someone was mentioning that I can use the Mode23 for JDM, is this ok for my Evo X EDM MR?
I know I have to get some help in another thread on enabling Mode23 for my (ROMID=53050006).
/L-O
#696
Evolved Member
iTrader: (2)
Join Date: Nov 2003
Location: Mtz, CA
Posts: 606
Likes: 0
Received 0 Likes
on
0 Posts
Also when logging the LTFT should I be watching the Idel or Cruise one?
#699
Evolved Member
iTrader: (4)
Join Date: Sep 2004
Location: so cal
Posts: 636
Likes: 0
Received 0 Likes
on
0 Posts
xbox4414 - what power setting are you running in vista? i had the same problem when i had it set to balanced was getting 1 per every 3 seconds, changed it to high performance and i get 4 per second now
#702
Newbie
Join Date: Oct 2008
Location: French Polynesia
Posts: 52
Likes: 0
Received 0 Likes
on
0 Posts
AEM UEGO problem
Hi all,
Please can you explain why i cannot get my aem uego to log through evoscan, what is weird is that it's working on hyper terminal? here is the error log:
Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.07.259
Info: Battery 11,807V
Info: Initialize Vehicle ECU...
Info: Initializing CAN...
Info: CAN Connected...
Info: Connection successful...
Error: Object reference not set to an instance of an object.
at System.Windows.Forms.Control.MarshaledInvoke(Contr ol caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at #=qH7E777JbeJrjOu0kHLKN8Q98wfszgezClMV$M2PGzeY=.#= q1vj0lpDnMD4d_9YwRU5NPwySpukLfbVxNBTNI6snjNI=(Obje ct #=qwtDeWGdPkC36daAvQEXuzA==, #=qVj$jOrHYArnvB$OJMIYcOM$Pk6$hePTM0u2EoKqSopW1a4a TspxR6Dz_wKVSlwuJ #=qgG1vqHp4db0mQOrlqnLfeA==)
at #=q$$OQeW4kUpJYVxFyTXkRXG$BAuRXabx9nMWi2ih1wXo=.#= q8IoYZB_ghSq7TgoActyFjARG_0fBsESECeJ$0gGrfQ0=(Obje ct #=qxnXczwSEWJSwmXUTuAuvXg==, #=qVj$jOrHYArnvB$OJMIYcOM$Pk6$hePTM0u2EoKqSopW1a4a TspxR6Dz_wKVSlwuJ #=q_1Xk5vt6yXPPQ7CBz0$33g==)
at #=q$$OQeW4kUpJYVxFyTXkRXG$BAuRXabx9nMWi2ih1wXo=.#= qbb_IWhExjSwnrKcDsWcqTg==(Double& #=qBClifrCnW3XIMxS4sq_TMA==)
at #=q$$OQeW4kUpJYVxFyTXkRXG$BAuRXabx9nMWi2ih1wXo=.#= qFJn4mhLQUsnW9xKyzSgkag==()
Info: Datalogger Ended.
Please can you explain why i cannot get my aem uego to log through evoscan, what is weird is that it's working on hyper terminal? here is the error log:
Info: OpenPort 2.0 Found.
Info: OpenPort Firmware v1.07.259
Info: Battery 11,807V
Info: Initialize Vehicle ECU...
Info: Initializing CAN...
Info: CAN Connected...
Info: Connection successful...
Error: Object reference not set to an instance of an object.
at System.Windows.Forms.Control.MarshaledInvoke(Contr ol caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at #=qH7E777JbeJrjOu0kHLKN8Q98wfszgezClMV$M2PGzeY=.#= q1vj0lpDnMD4d_9YwRU5NPwySpukLfbVxNBTNI6snjNI=(Obje ct #=qwtDeWGdPkC36daAvQEXuzA==, #=qVj$jOrHYArnvB$OJMIYcOM$Pk6$hePTM0u2EoKqSopW1a4a TspxR6Dz_wKVSlwuJ #=qgG1vqHp4db0mQOrlqnLfeA==)
at #=q$$OQeW4kUpJYVxFyTXkRXG$BAuRXabx9nMWi2ih1wXo=.#= q8IoYZB_ghSq7TgoActyFjARG_0fBsESECeJ$0gGrfQ0=(Obje ct #=qxnXczwSEWJSwmXUTuAuvXg==, #=qVj$jOrHYArnvB$OJMIYcOM$Pk6$hePTM0u2EoKqSopW1a4a TspxR6Dz_wKVSlwuJ #=q_1Xk5vt6yXPPQ7CBz0$33g==)
at #=q$$OQeW4kUpJYVxFyTXkRXG$BAuRXabx9nMWi2ih1wXo=.#= qbb_IWhExjSwnrKcDsWcqTg==(Double& #=qBClifrCnW3XIMxS4sq_TMA==)
at #=q$$OQeW4kUpJYVxFyTXkRXG$BAuRXabx9nMWi2ih1wXo=.#= qFJn4mhLQUsnW9xKyzSgkag==()
Info: Datalogger Ended.
#704
Evolving Member
iTrader: (3)
Join Date: Sep 2005
Location: MIA
Posts: 367
Likes: 0
Received 0 Likes
on
0 Posts
bumping my earlier post for an answer (especially for the trims)
Is there a reason the LC-1 AFR option is not available for the JDM RS EVO X? Is the address unknown? There is a post catalytic OEM sensor in place. Also what about the trims since I'd like to have that in order to scale the injectors correctly rather than just plugging in the most common settings used for the Deatschwerks 800cc. EvoScan 2.6 Beta 19 Mode23 only has the trim parameters defined for the USA EVOX and not the JDM RS EVO X.
Is there a reason the LC-1 AFR option is not available for the JDM RS EVO X? Is the address unknown? There is a post catalytic OEM sensor in place. Also what about the trims since I'd like to have that in order to scale the injectors correctly rather than just plugging in the most common settings used for the Deatschwerks 800cc. EvoScan 2.6 Beta 19 Mode23 only has the trim parameters defined for the USA EVOX and not the JDM RS EVO X.
Last edited by nitz; Aug 4, 2009 at 11:27 AM.
#705
Evolved Member
iTrader: (1)
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 1,018
Likes: 0
Received 0 Likes
on
0 Posts
bumping my earlier post for an answer (especially for the trims)
Also what about the trims since I'd like to have that in order to scale the injectors correctly rather than just plugging in the most common settings used for the Deatschwerks 800cc. EvoScan 2.6 Beta 19 Mode23 only has the trim parameters defined for the USA EVOX and not the JDM RS EVO X.
Also what about the trims since I'd like to have that in order to scale the injectors correctly rather than just plugging in the most common settings used for the Deatschwerks 800cc. EvoScan 2.6 Beta 19 Mode23 only has the trim parameters defined for the USA EVOX and not the JDM RS EVO X.
Code:
<DataListItem DataLog="Y" Color="" Display="STFT" LogReference="STFT" RequestID="23808864" Eval="(0.1953125*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> <DataListItem DataLog="Y" Color="" Display="FuelTrim_Idle" LogReference="FuelTrim_Idle" RequestID="23804573" Eval="(0.1953125*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> <DataListItem DataLog="Y" Color="" Display="FuelTrim_Cruise" LogReference="FuelTrim_Cruise" RequestID="23804575" Eval="(0.1953125*x)-25" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="False" />