i got the email a couple days ago, I am going to try to log tonight, hopefully no connection problems.
so what is the baud rate of this new vesion, previous .98 version I was using was 16425 or something like that.

 

15625 baud I believe. I have my rom set for 62500 so I forget what the default was. I'm pretty sure thats correct though.

 

that was my first problem. plug your comp into your car and search for "device manager" open that and go to "ports" then find the driver and set it to com1. and it should work... thats what i had to do

 

I sent Hamish a message regaurding v 2.1, and by the end of the day, I received my v 2.1! thank you sir!

 

i went back to 2.0 for now until all the lil kinks are resolved.

 

So I logged my fuel consumption and on a 15 minute highway cruise I averaged 25.11MPG(U.S. gallons) from 65-80mph cruising range. This was no boosting at all. The Fuel Consumption feature works well with the new formula, and corrected injector duty cycle formula

Also, I averaged 21.97MPG(U.S) from 20mph-80mph in my trip)

 

Good stuff should we also switch the units from litre/100kms to something else as well?

 

I just changed mine to "MPG(U.S.)". I haven't been able to get the readings to show up on the graph though (I used MS office), it freezes and i have to quit evoscan and restart it. Maybe its because it can go as high on the graph (it can go up to infinity)?

 

awsome, thanks man ill try that next. ive done just about everything else including a rain dance around the car when connecting...

 

Not really possible. It probably just gets big enough that it slows it down. If you leave it alone for a while does it come back?

 

Nope, it actually says "infinity" when you are watching it live. The error says that it can't perfom an axis because its either too big or too small. This is just when you are reviewing the log ina graph AFTER you've saved it, not in any live graphing manner.

Check it out. You can view it in Excel no problem, and you can view all other parameters in the graph until you get to the fuel consumption.

http://dsm-ezine.com/evoscandatalog_...0_17.16.29.zip

 

Damit, i can't get mine to connect. Keeps autoreconnecting and then eventually times out.

Always something... Any Ideas? I have tried switching the Com's and all that stuff too..

 

What is your baudrate set to?

 

The baudrate is set-up in my ECU for 62500, but in EvoScan I thought I remember it said 15625 or whatever it defaults to.

I suppose I should change it to 62500, right? I remember I thought Evoscan would autodetect it..

 

Auto-detect, I think is a feature that has been removed. Type in 62500 and you'll connect just fine ;-)