Evo X Logging
Evolving Member
Joined: Jun 2007
Posts: 109
Likes: 0
From: New Zealand
Looking for some addresses for JDM 52360018.
- APP & TPS
- The 2 other loads (Mivec & timing)
- Manifold air temp (Charged air temp)
I think I have the AFR map which is 238088f0
Also, these should be the mivec on the JDM
- APP & TPS
- The 2 other loads (Mivec & timing)
- Manifold air temp (Charged air temp)
I think I have the AFR map which is 238088f0
Also, these should be the mivec on the JDM
Code:
<DataListItem DataLog="N" Color="" Display="InVVT" LogReference="InVVT" RequestID="23809450" Eval="(x-3552)/48.64+10" Unit="Deg" MetricEval="" MetricUnit="" ResponseBytes="2" GaugeMin="-40" GaugeMax="50" ChartMin="-40" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="ExVVT" LogReference="ExVVT" RequestID="23809452" Eval="(x-4096)*-0.01953" Unit="Deg" MetricEval="" MetricUnit="" ResponseBytes="2" GaugeMin="-40" GaugeMax="50" ChartMin="-40" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
Hahaha.
JK.
Are you serious? U were doing ECUtek before EcuFlash right? I'm guessing you guys had to pay for a licensing fee and program fee for those, ranging in the thousands? LOL. Dam I feel a bit better but I'm not made of money and was happy to finally buy PCM and now no support, I so don't feel the love any more.
Hahaha.
Hahaha.
No we did not purchase EcuTek. I knew better.
Hahaha, I knew it was a generic logger. But I'm just trying to figure out why boost is capped. I find it so odd. Obviously it's in the Evo's hardware. Should be a quick'ish fix or no?
Really? I thought u were flashing X's before EcuFlash....oh wait u had the very first beta's didn't you? LOL! That's why you were flashing X's so early, hahaha.
Really? I thought u were flashing X's before EcuFlash....oh wait u had the very first beta's didn't you? LOL! That's why you were flashing X's so early, hahaha.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Not a quick fix, and to be honest, PCMScan does not have the flexibility that EvoScan has, so its not worth the effort to accommodate PCMScan.
Newbie
Joined: Jun 2004
Posts: 83
Likes: 0
From: UK
i was ok up to about page 22 a couple of days ago now i have got lost again
if i take the code from page 1 of this thread, add to xml file for 5236 jdm gsr rom, reopen my rom, change the value of the new options in ecuflash as per this thread, then reflash.
will i be able to log boost/timing/load/rpm/knock ?? on evoscan
thanks for all the hard work got a bit confused on the last few pages though
if i take the code from page 1 of this thread, add to xml file for 5236 jdm gsr rom, reopen my rom, change the value of the new options in ecuflash as per this thread, then reflash.
will i be able to log boost/timing/load/rpm/knock ?? on evoscan
thanks for all the hard work got a bit confused on the last few pages though
Evolving Member
Joined: Jun 2008
Posts: 146
Likes: 0
From: Romania
I have made the mode23 mod to ecu but evoscan 2.6b14 with the latest USDM data.xml file cannot connect. Evoscan is blocked completly when I start the logger, I have tried to select only the RPM, but the same thing happens.
I have tactrix 2.0 with CAN/Evo X connection setting in evoscan.
what I am missing?
...I have unchecked the disable multithreading option and now connects, but no data is received
I have tactrix 2.0 with CAN/Evo X connection setting in evoscan.
what I am missing?
...I have unchecked the disable multithreading option and now connects, but no data is received
Last edited by GTR2009; Jun 19, 2009 at 03:28 PM.