OBD Logging speed
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
so I FINALLY got around to doing a 4th gear log.
hopefully this attaches ok!
yes - finally I can see the compressor surge
yes - I know we are missing some log entries, I need to test out some other combination of the "tuning knobs" in the new op20 beta
hopefully this attaches ok!
yes - finally I can see the compressor surge

yes - I know we are missing some log entries, I need to test out some other combination of the "tuning knobs" in the new op20 beta
How fast can a serial port (AFR) log? Around 30 per second? If we are going to be able to log faster than the serial port, would we have to run the AFR through the rear o2 sensor to maximize the setup?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
hamish is working on optimising the code a bit

)
You truely are the man Tephra!
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
aww that sux...
on my ecu bench I get 150 ROWS a second..
I am logging 18 things, which equates to 2700 individual samples per second..
But in my car (ie real life) - I only get 110 rows a second.. So only ~2000 individual samples per second...
You know it's fast, when you get 5 rows of data just turning the key from OFF to ON...
You know its REALLY fast when you get 100 rows JUST FOR CRANKING...
on my ecu bench I get 150 ROWS a second..
I am logging 18 things, which equates to 2700 individual samples per second..
But in my car (ie real life) - I only get 110 rows a second.. So only ~2000 individual samples per second...
You know it's fast, when you get 5 rows of data just turning the key from OFF to ON...
You know its REALLY fast when you get 100 rows JUST FOR CRANKING...
Are these figures with or without the logging to screen enabled?
I started turning off the logging to screen and the log resolution is much better... I'm fairly new to EvoScan so maybe this is standard practice already but I stumbled upon it about 2 weeks ago and what an improvement that made.
I started turning off the logging to screen and the log resolution is much better... I'm fairly new to EvoScan so maybe this is standard practice already but I stumbled upon it about 2 weeks ago and what an improvement that made.
On my Acer Aspire One netbook I have seen a best of 188/samples sec on EvoScan when the logging to screen is off. With it on I typically see 62~75/samples sec. Thats logging roughly 8~10 items.
I haven't looked with my powerful laptop yet but I've read 200/sec is max for current EvoScan anyway, is that true?




