I finally got sick and tired of trying to log with either Mitsulogger or Logworks2, so I bought a copy of EvoScan last night figuring it would be the best to use with the least amount of issues for my new tuning laptop. ML worked great on my old XP powered laptop, but for some reason doesn't like connecting to my LC-1 on my new Vista powered laptop, and Logworks works just fine but it's a pita to read. Well today I fired up EvoScan for the drive to work (what better time for some good long logs) and for some reason I couldn't get it to connect to my LC-1 either. Same issue on my way home from work, and as soon as I got home I decided to try something. I ran Logworks first (came up as com5) and it connected fine, then closed it and ran EvoScan, selected com5 (before only com3 and com4 would show up) and voila'...it connected to the LC-1 and was logging. Is it normal to have to run Logworks before EvoScan in order to get it to recognize the proper com port?

 

evoscan 2.5 has serious LC1 connection bugs.

at least install the 2.6b6 upgrade (from the thread on here)

for a better solution, permanently wire your LC1 to the ECU (via the rear02 signal wiring)

This reduces the amount of times the serial cable can screw up the LC1...

 

Ok, I'll give it a shot...thanks. It worked flawlessly today so I finally got some decent logs, but I'd hate for it to be a temporary thing.