I'm still having com1 port problem.
I already have it set at com1 in device manager.

How do you know what the ECU baud rate is set to?
I tried various numbers and still get the "link disengaged" and com1 cannot be found error.

 

Did you get it to log with an older version before? The default ECU baudrate setting in the ROMs is 15625 and 95% of the guys on here will keep it that way.

 

Jack,

This is my fist time to use Evoscan. I just registered last night so I get the latest 2.1 version.

In another thread, Kreonic suggested to turn off the Wideband feature as I don't have a wideband. I tried to disable the "Innovate...", first row under the wideband tab by checking the two bottom row items under the same Wideband tab and it worked. But everytime I open Evoscan, that first row under wideband keeps getting enabled but I don't get the COM1 Error anymore.

Thanks,
Richard

 

If you don't have a WB hooked up, it just won't log anything. Nothing to worry about.

 

What I was talking about if you have wideband checked under the display items. If the wideband is checked and you dont have a wideband hooked up to the PC it will timeout as soon as it starts

 

Ah, yes that is true and has caught me off guard a few times.

 

Hi Guys,

Need advice on the loadcal formula.

For example, if you have the following parameters what are the steps you should take?

Injector Scaling: 780
14v Latency: 1.035

Below is the existing formula for the evoscan2.1:
<DataListItem DataLog="N" Color="" Display="Load Calculated" LogReference="LoadCalc" RequestID="29" Eval="5*513*((0.256*x)-(-0.1026*[Battery]+1.8741))/[AFRMAP]" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="5*InjScaling*([InjPulseWidth]-(-0.1026*[Battery]+1.8741))/[AFRMAP]" Priority="1" Visible="False"></DataListItem>

 

Eval="5*780*((0.256*x)-(-0.1026*[Battery]+1.8741))/[AFRMAP]"

 

so i do not it to change the rest of the figures ".....-(-0.1026*[Battery]
+1.8741))/[AFRMAP]..." in-accordance to the new latency values?

 

As far as I know, no.

 

Just a quick question. I have the 1.3 Mitsubishi Open Port Tactix cable. My buddy has an '05 STI which is a drive by wire vehicle.

From my understanding, with this version of EvoScan and my Tactrix cable, I should be able to log his car since it doesn't need the test connectors to log/flash like the WRX, correct?

 

So my laptop died right after downloading 2.1, then I got it back and my LC-1 was out of whack, innovate got me running again, and i finally get evoscan 2.1 going only to realise it still does not support LC-1, it says in progress? WTF, thats the only reason I upgraded.

 

my lc-1 worked fine in 2.0 but it's not working with 2.1... bleh, rolling back to 2.0

 

edit your rom for 2byte load and log 2byte load via evoscan, make it easy on your self bro. If you have trouble editing your rom for it either pm me or search Jack of Trades name. He made thread to make it easier for ppl to search there rom for 2byte load mod.

 

Hamish is already working on version 2.2 to correct all of the little bugs that turned up. I'd expect to see an email sent out for this very very soon.