ECUflash evoscan shuts off in drive

[1Gina2G]

You should be able to just take logs, as you drive right? I'm quite new to even logging, I can't use evoscan for any actual tuning/adjusting just logging from what I read, since I have an EPROM ECU.

I just finished getting the car put together after a cupple years so I don't know what to think. Just noticed the program stopped logging, and while stopped, I tried to restart the program and it didn't want to start, mentioned 'try openport 2.0 if you have that' but I knew it wouldnt work. Then my computer was acting like it couldn't reconize the USB cable 'device' at all.

Also..the baudrate HAS been lowered, to 10400, to be able to actually log on the eprom. Not sure what made it cut off, but on idle it holds all day long, and stops/restarts just fine, even after the drive.

thanks in advance!

 

[MY1GDSM]

What version of Evoscan are you using?

Here are some NOTES I'd read about logging the Pre MUTIII (IE 95/96) Ecu's that are MUToverOBDII

 

[marcman804]

I had this same problem while I was running the 99 flashable ecu. It just stopped working so then I went back to my eprom ecu and it still wouldnt connect. I have yet to find a solution to this problem.

 

[MY1GDSM]

Everyone is always so vague when they have issues like this...

It's a big help to explain exactly what version of Evoscan software you are using, What cable you are using to log and any other details like a error message before or after the laptop stops logging. If you want to actually resolve the issue anyway.

 

[1Gina2G]

Evoscan version 2.9

1.3R USB datalogging and reflashing cable.

at the time I thought I was going to be able to use evoscan to actually tune, but then I read more on it.

I would've also added that I read those note above^ but I forgot they were listed on the evosvan website. I made all the adjustments in the settings, including the mentioned baudrate adjustment along with knowing how to change the TPS setting from voltage to actual postion percent.

 

[MY1GDSM]

Oh I see... 1.3D or even a Vag cable would have been a better Idea for the logging speeds you can only get with the early Ecu's.

What you have now works with Evoscan to reflash Evo Ecu's Just FYI... .

Sounds like a Driver Issue more then anything. Even though you don't have a Cable that will work with ECUflash did you install it for the Drivers or them from ftdi? When you hook up your cable do you get a prompt for it installing any drivers? what about if you look in you device manager? What about ASP Net 2.0? Do you have the 2.0 net framework installed for windows?

 

[1Gina2G]

Oh I see... 1.3D or even a Vag cable would have been a better Idea for the logging speeds you can only get with the early Ecu's.

What you have now works with Evoscan to reflash Evo Ecu's Just FYI... .

Sounds like a Driver Issue more then anything. Even though you don't have a Cable that will work with ECUflash did you install it for the Drivers or them from ftdi? When you hook up your cable do you get a prompt for it installing any drivers? what about if you look in you device manager? What about ASP Net 2.0? Do you have the 2.0 net framework installed for windows?

I honestly thought that I read, that the cable I bought from the evoscan website, did basically everything the 1.3D cable did PLUS reflash as it has the reflash connector that I have not used, pigtailed in the wiring.

Have not received any prompt to install any drivers, or anything in the device manager.

how would I know if I had the 2.0 net framework installed? this is a fairly new laptop, that uses windows 7 if that matters.

The cable I have, should be just fine for only logging right? just not possibly while driving for some reason....thanks for all the advice, I know evoscan isnt the simplest thing in the world.

 

[1Gina2G]

Surprised no one had anything to say by now.

I never got this issue solved, and now im falling even further behind because now evoscan will not allow me to log anything! I think the problem is my lap top actually which still would be surprisingbecause its new and good quality.

Anyways, with the cable plugged into the obd2 connector, the laptop only accepts the USB cable off one side, as in the sound it makes when you plug something usb capable in. On that side, right away a small bubble pops up mentioning again how the USB device cannot be reconized!

Baudrate is still at 1040, DSM box checked in. Not sure what else to do, laptop doesn't give me the slightest clue of what to check out

 

[MY1GDSM]

If you have done what I said in my old post.

Download Evoscan 2.5 and try that... .

 

[PieEyedPiper]

Surprised no one had anything to say by now.

I never got this issue solved, and now im falling even further behind because now evoscan will not allow me to log anything! I think the problem is my lap top actually which still would be surprisingbecause its new and good quality.

Anyways, with the cable plugged into the obd2 connector, the laptop only accepts the USB cable off one side, as in the sound it makes when you plug something usb capable in. On that side, right away a small bubble pops up mentioning again how the USB device cannot be reconized!

Baudrate is still at 1040, DSM box checked in. Not sure what else to do, laptop doesn't give me the slightest clue of what to check out

Start>ControlPanel>Programs and Features>Turn Windows features on or off
This will let you know if you have the correct framework installed. Honestly, the FM's are such a pain in the ass these days I just make sure I have all of 'em.

Also of importance is a driver installation so that your USB device will be recognized. As I recall mine auto installed on win7 ultimate 64bit when I was dicking around with ecuflash and the openport cable.

P.S. I got Evoscan 2.8 to pull codes today. I'm feeling pretty awesome. but I'd feel even awesom-er if I could log 1byteload in 2.9 so I can use the map tracer. Evoscan is a bi***.