Evoscan 99 and DLL with AEM WBAF
Thread Starter
Evolved Member
Joined: Aug 2006
Posts: 1,427
Likes: 4
From: Sag-Nasty, MI
Evoscan 99 and DLL with AEM WBAF
I'm trying to work all the bugs out of my setup, the new Evoscan is great, remembers my settings and such, I've got the USB configured as com2, and now it never "times out" while logging. So I'm happy.
However, when I try to look at my logs in Data log labs, my aem wideband data doesn't show up... it's there in Evoscan, but not in DLL.
I didn't have this trouble with the .97 Evoscan, in fact I went back to 97 and it still works. re-installed 99, and the logs I take with it don't show the WBAF data in DLL.
Anyone else see this happening??
However, when I try to look at my logs in Data log labs, my aem wideband data doesn't show up... it's there in Evoscan, but not in DLL.
I didn't have this trouble with the .97 Evoscan, in fact I went back to 97 and it still works. re-installed 99, and the logs I take with it don't show the WBAF data in DLL.
Anyone else see this happening??
there were some changes in how evoscan .99 saves the data that made it not work with dll I modified somebody else's def file for the new evoscan and added some other defs also like 2 bite load jdm map and some other changes.
also you can check the evoscan text file in the universal data log formats folder and make sure the channel is exactly the same as in your datalog. if I remember there was a space delete in the column name or something like that. like WB Airflow vs WBAirflow
also you can check the evoscan text file in the universal data log formats folder and make sure the channel is exactly the same as in your datalog. if I remember there was a space delete in the column name or something like that. like WB Airflow vs WBAirflow
Last edited by andenbre; May 7, 2007 at 08:35 PM.
Newbie
Joined: May 2006
Posts: 20
Likes: 1
From: Perris CA
there were some changes in how evoscan .99 saves the data that made it not work with dll I modified somebody else's def file for the new evoscan and added some other defs also like 2 bite load jdm map and some other changes.
also you can check the evoscan text file in the universal data log formats folder and make sure the channel is exactly the same as in your datalog. if I remember there was a space delete in the column name or something like that. like WB Airflow vs WBAirflow
also you can check the evoscan text file in the universal data log formats folder and make sure the channel is exactly the same as in your datalog. if I remember there was a space delete in the column name or something like that. like WB Airflow vs WBAirflow
Thread Starter
Evolved Member
Joined: Aug 2006
Posts: 1,427
Likes: 4
From: Sag-Nasty, MI
Hey thanks, that data file worked... it just scared the **** out of me though because the knock shows up differently on the graph... I have a 3-count on a highways pull but it looked for a minute like a 30!!
Thread
Thread Starter
Forum
Replies
Last Post
phrequenc
General Engine Management / Tuning Forum
15
Feb 17, 2013 01:38 PM
divine_evo
General Engine Management / Tuning Forum
2
Feb 2, 2009 03:09 PM
Nvr2old32
Evo X Engine Management / Tuning Forums
4
Sep 29, 2008 07:51 PM
