evoscan logger release
I'm glad it helps. I'm sure Evo4Mad will do much more with the data later, but it is obviously beta for now and I'm just contributing anything I can since I love the software so much.
Originally Posted by jcsbanks
andenbre, surely you could get different numbers in logs compared with mapped numbers if there are other compensation maps active? What timing do you get at idle? I'm intending to compare to my OBD-II logger later on.
lookin at the map that could fall either way
my map shows 5 deg at 40% and 15 at 60%
Last edited by andenbre; Jun 27, 2006 at 08:17 PM.
Originally Posted by jcsbanks
andenbre, I've tried it now, agree the timing numbers seem about 10 too high - eg 15 degrees at idle. I can log at 12 samples per sec but that is because of my slow laptop. I am getting readings of 1,2,3 on the knock sum, sometimes on very little throttle though, and one 9 and 12 on lift off in another hot zone that I've retarded. I have no idea what is normal for knock sum.
I took the CSV file and sorted it by the item reference then the time stamp, then I copied the blocks so that one row of the sheet showed all the values collected in a short time interval, then I could make sense of the log file a bit better.
There is some weirdness with airflow for example, Hz will read out to say 1600 Hz and then just stick there, not going up or down. The airflow quantity moves around differently still - lots of oscillation with no clear trend. The temperatures are not scaled to suit the IX at present it seems.
Excellent test at this stage really just to establish communication with the ECU and save the requests to file. Excellent job evo4mad
I took the CSV file and sorted it by the item reference then the time stamp, then I copied the blocks so that one row of the sheet showed all the values collected in a short time interval, then I could make sense of the log file a bit better.
There is some weirdness with airflow for example, Hz will read out to say 1600 Hz and then just stick there, not going up or down. The airflow quantity moves around differently still - lots of oscillation with no clear trend. The temperatures are not scaled to suit the IX at present it seems.
Excellent test at this stage really just to establish communication with the ECU and save the requests to file. Excellent job evo4mad
i have only seen knock values in one pull and its value was 2 for 1 second worth of log. since the rest of my logs showed 0 i disregarded it as a fluke rattle or what ever.
the air volume seems pretty erattic at consistant speed/rpm/throttle
sweeping from 8 to 250 earily similar to o2 sensor sweeps
Edit: I beleive that air volume is actualy closed loop front o2 sensor now because in the logs at steady 3k it osolates between 8 and 248 just like o2 until tps goes to basicly 0 (13.3333333 but that is the idle stop reading) decel then air volume goes to 0 until idle rpm is reached then it pops back up to single digit to triple digit sweeps. o2 sensor channel data is a bit slower to respond also. this is on an evo9, 8s may be different
Last edited by andenbre; Jun 29, 2006 at 07:20 PM.
Hmm Im still getting 3 samples per second. I tried plugging in both connectors before the car was started and its still the same. I did minimize the window and it jumped to 80 samples per second. Is there any way I can view the window without it being minimized at this time or am I going to wait till the new release?
Originally Posted by justchil
What are the specs on your computer? Maybe you just have a slow machine? Maybe not.. but just a thought.
Yes, its slow. I think it's only a P2 maybe a 3.
But logging while I had the maftpro in the car it was quick, It logged about 20 different things at once.
Originally Posted by justchil
Every time I try to do a 3rd gear pull I look down and the logger has stopped itself. I need to figure out whats up with that 
I had the exact oposite. I did a 3rd gear pull with the logger off and looked down and it was logging, my mouse had shot off the armrest and landed in the back seat hiting the mouse button right on the start log button
Now that I think about it... I have an IBM which has a shock sensor.. It will "pause" the hard drive but i haven't had problems with any other apps. I guess its possible my tq is just too much for it
