So I've finally made the switch to EVOScan from Mitsulogger mostly just to check its capabilities out but, I'm running into an issue logging my LC-1. The logging keeps spitting the readings out in volts? I've also selected the "AFR map" box which appears like it should, using the equation list of 14.7 * 128/x, calculate the a/f ratio, however, when I log that it only shows 14.7, almost like its not calculating properly?

Any suggestions? I'm using the latest version of EVOScan (2.5).

 

Bump for some help.

 

I can help you out, I picked up your post from googling evoscan

what is your msn messenger address? I can get it set up for you how you like it.

 

I don't have a msn messenger account. I would be willing to create one so long as its free. I really would like to get EVOScan straightened out.

Have you had expierence or know of anyone using it on a MAC via Parallels on XP? I've been running ECUFlash, Logworks2 and Mitsulogger that way. Mitsulogger doesn't seem to happy with it though as I keep getting error messages.

 

I also need my serial number :-) I need to switch EVOScan to my MAC from my PC and I can't seem to find the serial #.

 

I set a MSN account. My address is afuhs@comcast.net. I'll be waiting I also need my serial number.

 

did you ever get a fix for this. my lc-1 is logging values like 3.xxx,4.xxx,5.xxx in evoscan although it works fine via the same serial connection in logworks. let me know thanks.

 

AFR MAP is not for wideband data, it's for reading the Fuel Map values from your ROM (ie. target AFR). There should be a separate checkbox for Wideband

As far as logging the wrong values in EvoScan, connect to the LC-1 using LM Programmer and make sure it's calibrated to output lambda in Gasoline scale (14.7:1).

 

uhhh.. i think everyone realised this already. this thread was about lc-1/evoscan logging incorrect values. ie voltage like instead of afr

 

nevermind i found your other thread and checked the output programming of the lc1 and was indeed set to custom instead of gasoline. afr output in evoscan is reading correctly now.