I know that .98 still has some bugs in it but I wanted to share this to see if anyone else has experienced anything like this. So I just hook up my uego to log with evoscan, I make sure the afr's are indeed logging, and they are. evoscan .97 works same as always, but when I go to verify everythings cool with .98 something very strange happens. I am idling, at a stop, go to start the log and as soon as it initializes the rpm's rocket to 3k and the cel comes on, the rpm's hold around 3k, I am confused so I stop the log and the cel goes away and rpm's drop.

So to sum it up I repeat the process a couple of times to the same effect, version .97 does not have the same problem. Any thoughts?

 

free bump.....


i emailed the guy 10 times now for the link so i can download the program, but captain douch bag hasn't responded yet.

 

Try taking out the second plug from under the dash.

 

The white connector?

 

why whats that one do?

 

The weirdo log that was created

 

Grounds pin 1 for ECU flashing...I think

 

Unplug the white connector, its possible thats causing the problem. Its also possible the RequestID's are polling a test request causing it. But it will be clearer after you unplut the white connector while logging.

When I updated Mitsulogger, I found a glitch in the new FTDI drivers that I had spent a few days trying to fix, It might be how the driver is initialized in his application, but again, unplugging the white connector will be a dead giveaway.

Early versions of some of the loggers did trigger similar symptoms when it glitched the FTDI port (toggled the circuits that would trigger bootstrap mode)

 

Thanks for he suggestion MJ. .97 still runs fine so I think it may be just a .98 thing? I'll let you know what happens.

 

It probably is, some of the FTDI api changed recently and this might be the result.

 

I don't know why so many people plug the white connector in to log.

When I bought the cable I thought it was pretty clear the only purpose of that was for flashing.

 

Yeah, I have a habit of leaving it plugged in, however it has never caused the symptoms that this person is describing. But if I did get them, I'd disconnect it.

 

Well, The problem sorta went away... the cel still comes on when loggling, and the idle is a little rough, the log still gave me aroneous values....but the skyrocketing idle is gone.

 

I myself have reinstalled .97 and am going to wait. I have found though that LogWorks 2.04 from Innovative (my wideband) is one majorly badass application since they now support the OpenPort cable.

The Math and Graphing functions are also fantastic.

 

That's "Captain Douchbag Sir" - there sarge

AFR little high

Thats exactly what it is, I think only one of the 3 pins on the connector plug is actually making contact with any of the sockets of the car's connector jack.

I also never thought that hooking it up while real timing would cause any interferrence