Hey guys, I have a 1.3u cable and the latest Evoscan on my eeePC, and it seems like whatever settings I put it on, Evoscan just wont work and it keeps going "Disengaged".


Anybody here have experience with Evoscan?? What settings/tricks do you use?

Big thanks guys,

Ben

Is the USB cable driver installed? Its in C:\Program Files\Evoscan... somewhere. Pretty easy to spot.

after that... restart your nerdbox and try again.

Only works with the ignition in the ON position.

OH! and check the cable setting in Evoscan is the right one for the cable you're using. I dont have evoscan on this computer, but its in the main screen. Options are; 2.0 or 1.3.

Then, check you've got your ECU set right...

Damn. I'd be more help if I had it with me.

Hey guys, I have a 1.3u cable and the latest Evoscan on my eeePC, and it seems like whatever settings I put it on, Evoscan just wont work and it keeps going "Disengaged".


Anybody here have experience with Evoscan?? What settings/tricks do you use?


You need to make sure that Openport 1.3 is selected, the MUT-III protocol is selected (the baud rate should automatically be set to 15625, leave timeout as 1000ms) and select the "EFI" ECU as the source (should be the default as I recall).

Evoscan will only connect once the ignition is switched to ON (so only "start datalogger" once that's done) and will disconnect when the ignition is switched to ACC or OFF. You should be able to log through the engine starting, but the log will only show zeros in all selected columns until the engine is running.

http://i.imgur.com/OVlW2.png

Marked some areas to check.

Correct path to USB drivers is; C:\Program Files\Evoscan\Evoscan v2.8\USB Drivers\openport 1.3\

As for tips and tricks; don't select sensors that return zero data or unusable data. It loads your PC up. Don't bother with the gauges for logging, playback maybe. The graphs will be enough. There were a few other things I tweaked using trial and error. Things like getting the fuel consumption to output data that was closer to real-world data. Use the alarms feature, set a sound, to get feed back while driving... its a lot safer.

Get an adapter to run your laptop from the accessory socket. I have an EEEPC, the adapter was $8 from china.

All of this is only for logging. Its interesting to see some changes, if any, after each mod. And spotting dead sensors and the like. I've used the set idle feature to set my idle.

Cheers boys, I'll give this a go tonight :D

Hey guys,

Done everything above and it still wont connect...

I've loaded up all of the evoscan versions i could find, and the only one that would connect (but not pick up any information) is the Chrysler setting...

Bummer. I'll have a look tonight when I get home. In the "Logging" pull down menu, I think there may be something in there that needs selecting.

Drivers were installed correctly for the cable?

Sometimes old winDOS needs a reboot when things get too hard for it.

Hey guys,

Done everything above and it still wont connect...

I've loaded up all of the evoscan versions i could find, and the only one that would connect (but not pick up any information) is the Chrysler setting...

Chrysler? Where are you selecting that? I'm using the same version of Evoscan as Skapper (see pic above) and don't ever recall seeing a setting for Chrysler...

I downloaded evoscan 2.5,2.6,2.7 and 2.8 to see if any of them would work. 2.5 has the option for Chrysler.

Everything I tried above was on evoscan 2.8.

I really dunno why it's not working... It keeps going "disengaged" for every setting I try to use.

I think if it keeps disengaging it cant see the cable or the ECU. Reinstall the drivers for the cable - my PC drops the drivers at random, so its not uncommon - then try turning te ignition to ON (or start the engine) then try reconnecting.

I've had this issue before. Cable drivers I'm sure.

I've checked my "Logging" pull down menu and I cant see anything that will stop it connecting.

In the Logging menu I have the following selected;
- Logger superspeed
- Disable Mitsubishi Dashboard Flashing Lights
- Apply CPU timer fix
- Log data to file
- Log data to screen
- Autoreconnect on timeout
- Metric Units

Like I said, I doubt anything in the Logging menu will stop you from connecting. If anything its the cable and/or a setting in the main screen.

stick with the latest version of Evoscan to.

I've formatted my evoscan laptop and its working now :D

I'm not exactly sure how to use it now, I've had a play at logging and I was wondering if anybody could show/tell me how to use the torque/power function? The times I've done it, its calculated that my car has 1000kW+ and while its fast, its not that fast haha...

Does it only work if you start logging in gear, just before you put your foot down, or are you able to log a journey, do 10+ WOT runs and then disect each WOT run's power/torque calculation?

Glad to hear you got this sorted!

If you haven't changed the injector scaling (in Evoscan), that needs to be done for a start. Unless of course you are actually using Evo injectors... :badgrin:

I've never bothered with the "derivative" functions, because I don't completely trust Evoscan's scaling of some values. In any case, I'm more interested in what the ECU is actually doing with the engine...

I've got this to work, but it appeared very random as every other time it just plain wouldn't.

Set your data for torque and power, then open a data log. Select a section of data and then calculate torque.

From there it can be very generous of an estimate depending on the option you have set for correction.

I'm on the iPhone on a couch a few klicks from home so I can only relay all this from memory. Some of what I've said might be vaguely correct.

Injector scaling as in what their flow rate is or their latency?

Injector scaling I've changed, to what am I'm not sure - still got to make it home from work yet - I did have a reason for the change, like I just didn't pluck a number out if the air or anything. I think the change I made was based on something I'd read in a help file somewhere.

Sorry, mate, my memory is pretty bad. I need my laptop in front of me to jog my memory.

Injector scaling as in what their flow rate is or their latency?

Flow rate. Evoscan's default value is (as best I recall) 513cc/min which is the stock Evo 7/8 scaling.

Hi
Ive noticed something a bit strange with my car using Evo scan. when i plug in the cable without connecting it to the USB port the the ABS light starts to flash as does the "P" and "N" lamps in the transmission display. The car is a 2001 Verada. I am not using it to tune the car but im chaasing a pesky problem where the "TCL Off" light and the engine light keeps coming on. Anyone struck this at all.? I can connect with the ECU but i had to increase the timeout default from 1000ms to 12000ms.
Thanks