SD - first test success
You need an Innovate product to do live logging in LW3 according to the manual. Is LW2 different?
The only reason I'm really using it is to do the VE maps as it does a properly centered RPM and MAP axes. Evoscan map tracing so far takes say the 60 load column and dumps everything >=60 and <70 in that cell, whereas it should be >=55 and <65. The errors stack up when you're calculating idle or over-run VE, whereas in LW3 it displays just right.
The only reason I'm really using it is to do the VE maps as it does a properly centered RPM and MAP axes. Evoscan map tracing so far takes say the 60 load column and dumps everything >=60 and <70 in that cell, whereas it should be >=55 and <65. The errors stack up when you're calculating idle or over-run VE, whereas in LW3 it displays just right.
I agree that all the links to the patched ROMs should be in the first post or perhaps start another thread. I was going to leave the option of doing that to jcsbanks since its his baby, but you're killing me if you can't find it in this thread:
https://www.evolutionm.net/forums/ec...ml#post6698077
The MAT sensor patch thread is here:
https://www.evolutionm.net/forums/ec...e-logging.html
https://www.evolutionm.net/forums/ec...ml#post6698077
The MAT sensor patch thread is here:
https://www.evolutionm.net/forums/ec...e-logging.html
Sorry about that.
You need an Innovate product to do live logging in LW3 according to the manual. Is LW2 different?
The only reason I'm really using it is to do the VE maps as it does a properly centered RPM and MAP axes. Evoscan map tracing so far takes say the 60 load column and dumps everything >=60 and <70 in that cell, whereas it should be >=55 and <65. The errors stack up when you're calculating idle or over-run VE, whereas in LW3 it displays just right.
The only reason I'm really using it is to do the VE maps as it does a properly centered RPM and MAP axes. Evoscan map tracing so far takes say the 60 load column and dumps everything >=60 and <70 in that cell, whereas it should be >=55 and <65. The errors stack up when you're calculating idle or over-run VE, whereas in LW3 it displays just right.
I'm glad you took a look at LogWorks though. I think it's a great tool.
live logging works with LW2 and the open port 1.3 patch/plug-in.
i've done it.
in extra devices but you must have at least 1 innovate device
.
i've done it.
in extra devices but you must have at least 1 innovate device
.
Last edited by leecavturbo; Feb 25, 2009 at 01:34 PM.
it really is what you want . you can zoom and scroll to a particular wot run for example
and there are smoothing options too. i love it
the ability to only log wot pulls or load above xxx also saves time looking for pulls
and there are smoothing options too. i love it
the ability to only log wot pulls or load above xxx also saves time looking for pulls
Last edited by leecavturbo; Feb 25, 2009 at 02:06 PM.
I've got a log here setup just like JCSBanks and I'm seeing most of my map above 100% VE.
I'm thinking this has to do with the fact that load is only a function of MAF frequency and MAFscaling? Thus because I'm at 4200' and for any given MAP I will see a higher MAF frequency (because of the lower air density/higher air velocity), it's making my load artificially (relative to sea level) higher?
I'm thinking this has to do with the fact that load is only a function of MAF frequency and MAFscaling? Thus because I'm at 4200' and for any given MAP I will see a higher MAF frequency (because of the lower air density/higher air velocity), it's making my load artificially (relative to sea level) higher?
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I've got a log here setup just like JCSBanks and I'm seeing most of my map above 100% VE.
I'm thinking this has to do with the fact that load is only a function of MAF frequency and MAFscaling? Thus because I'm at 4200' and for any given MAP I will see a higher MAF frequency (because of the lower air density/higher air velocity), it's making my load artificially (relative to sea level) higher?
I'm thinking this has to do with the fact that load is only a function of MAF frequency and MAFscaling? Thus because I'm at 4200' and for any given MAP I will see a higher MAF frequency (because of the lower air density/higher air velocity), it's making my load artificially (relative to sea level) higher?
I'm logging based on the Omni-power 4bar and Tephra's 1 Byte scaled load.
My values look similar to JCSBanks, just higher...

The spots in the map with lots of samples seem to sit right around 1.00.
I'm running 18 PSI and local ambient pressure is 12.4 PSIA. This makes the MAP 30.4 PSIA or 210 kPa, as seen in the chart.
My values look similar to JCSBanks, just higher...

The spots in the map with lots of samples seem to sit right around 1.00.
I'm running 18 PSI and local ambient pressure is 12.4 PSIA. This makes the MAP 30.4 PSIA or 210 kPa, as seen in the chart.
Last edited by 03whitegsr; Feb 25, 2009 at 09:29 PM.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
What formula are you using to log MAP?
For tuning VE, you'll need to log baro+temp corrected load. I think tephra's 1-byte load is the uncompensated load variable.
For tuning VE, you'll need to log baro+temp corrected load. I think tephra's 1-byte load is the uncompensated load variable.
I'm using the formula I came up with for the 4bar based on the data from the sensor. I'm actually logging in PSI, then I convert over to kPa.
My complete scaling is as follows:
PSIG=(x-52)*0.2368 [52 here is the raw count I get from atmospheric pressure]
kPa=(PSIG+12.3136)*6.8948 [12.3136=52*0.2368 the atmospheric offset from above, 6.8948 is a conversion factor to go from PSI to kPa]
I read your thread on all the different loads. Sorry to not search back, but it seemed a little difficult for me to follow last time I read it. What MUT channel should I log for the compensated load then?
EDIT:
Also, just an FYI, I have changed load scaling by a factor of 100. I'm use to DSMLink which seems to use these same values as an airflow/rev measurement. Instead of 200, I would see 2.00, thus the reason my values are 1.00 = JCSBanks 100.
My complete scaling is as follows:
PSIG=(x-52)*0.2368 [52 here is the raw count I get from atmospheric pressure]
kPa=(PSIG+12.3136)*6.8948 [12.3136=52*0.2368 the atmospheric offset from above, 6.8948 is a conversion factor to go from PSI to kPa]
I read your thread on all the different loads. Sorry to not search back, but it seemed a little difficult for me to follow last time I read it. What MUT channel should I log for the compensated load then?
EDIT:
Also, just an FYI, I have changed load scaling by a factor of 100. I'm use to DSMLink which seems to use these same values as an airflow/rev measurement. Instead of 200, I would see 2.00, thus the reason my values are 1.00 = JCSBanks 100.
Last edited by 03whitegsr; Feb 25, 2009 at 10:28 PM.
Ok,
I have the patched Evo 9 0015 rom and its working without the maf, no check engine lights ect. ect.
It drives extreemly well, idels better than it did with the MAF. However Im not getting something, as soon as I try to hit boost or higher than 150 load I instantly go lean 18.8 AFRS, I have adjusted my MAP VE scalings but still wont let me transit over. My STFT ranges in the 25 or so range. I dont know what I am missing.
JDM Map and GM IAT both seem to be working correctly. This is on a 2.3L with 35R turbo fyi.
Any ideas? Im really excited to get this to work, so any help would be great!
Evan Smith
I have the patched Evo 9 0015 rom and its working without the maf, no check engine lights ect. ect.

It drives extreemly well, idels better than it did with the MAF. However Im not getting something, as soon as I try to hit boost or higher than 150 load I instantly go lean 18.8 AFRS, I have adjusted my MAP VE scalings but still wont let me transit over. My STFT ranges in the 25 or so range. I dont know what I am missing.
JDM Map and GM IAT both seem to be working correctly. This is on a 2.3L with 35R turbo fyi.
Any ideas? Im really excited to get this to work, so any help would be great!
Evan Smith
Thanks for 90550001 patch, tried it today but car throw P0110 (Intake air temp malfunction) when I disconnect the maf. I think the air temp I log was built in the maf, now I need to wire up another air temp sensor to my manifold. And some questions here:
a) OEM VII ecu have no fuel temp sensor wire up to ecu, can someone suggest which pin I can use with new air temp sensor?
b) I have existing vipec air temp sensor 1/2 npt with 2 wire and I intend to use it. Do I have to calibrate air temp sensor (just like jdm map)?
Thanks for help!
a) OEM VII ecu have no fuel temp sensor wire up to ecu, can someone suggest which pin I can use with new air temp sensor?
b) I have existing vipec air temp sensor 1/2 npt with 2 wire and I intend to use it. Do I have to calibrate air temp sensor (just like jdm map)?
Thanks for help!
Thanks for 90550001 patch, tried it today but car throw P0110 (Intake air temp malfunction) when I disconnect the maf. I think the air temp I log was built in the maf, now I need to wire up another air temp sensor to my manifold. And some questions here:
a) OEM VII ecu have no fuel temp sensor wire up to ecu, can someone suggest which pin I can use with new air temp sensor?
b) I have existing vipec air temp sensor 1/2 npt with 2 wire and I intend to use it. Do I have to calibrate air temp sensor (just like jdm map)?
Thanks for help!
a) OEM VII ecu have no fuel temp sensor wire up to ecu, can someone suggest which pin I can use with new air temp sensor?
b) I have existing vipec air temp sensor 1/2 npt with 2 wire and I intend to use it. Do I have to calibrate air temp sensor (just like jdm map)?
Thanks for help!
You will need to calibrate the temp sensor you use.


