Is anyone using this combination on vista with sucess, when i use logworks 2, my idle afr are averaging out at 14.79, over several minutes and it logs fine, when i try and log with evoscan 2.0 it connects and shows its reading the lc-1 with com port 7, but the reading under wideband afr is 4.8-4.9? Then when i try and review the file it says no entry for wideband afr? Any suggestions, looks like tuning with logworks will be a major PITA?

 

I don't run Vista and had the exact same readings on the new Evoscan I simply went back and i am currently running the old version. Let me know if anyone has any ideas as well

Subscribed

 

I went out and logged/tund but its a pain, my afrs are decent on logworks but there really is no reference other than time. I tried mitsulogger and it started throwing codes(its beta so expected) so i uninstalled and used maptracer on 2.0 to at least see what cells i was hitting, but its very very difficult to tune this way. I may reinstall old evoscan for now to at least get my tune down but this was why I went with 2.0 was LC-1 and maptracing?

 

I use Logworks 2 to log from my LC-1, LMA-3 and my ecu.
The folks at innovate have written a plugin for the openport (tactrix) cable.

 

My afrs with my LC-1 and evoscan 2 are fine.

My issues with evoscan 2.o are with the maptracer.

It sounds like your com port is wrong? I always verify the com port by looking at it in devce manager.

 

What exact settings are you using, I am clicking on LC1, and my com port was set up as 7. I used 7 since logworks installed a new driver for this when i had to get the radioshack serial to usb cable, when the driver was installed it even went so far as to say you have installed a new driver for following: radioshack usb adapter. But my afr's log fine in logworks with exact same port, 7, I plug it in side by side with my tactrix cable right in back of laptop.

 

I am using Vista. Logworks is working fine and so is evoscan a/f along with the map tracer. I am not sure what everyones problem is with the map tracer

 

For some reason the IX roms work in evoscan 2 but not others...

 

So I went into device manager, reconfigured the com ports as 3(tactrix) 4(lc-1) and logged again, same thing, shows 4.8-4.9 at idle, i reinstalled evoscan .99, same figure 4.8-4.9, so somethings up? Anyone care to chime in, my laptop has no setting for a virtual com port or at least not one i can find? I really need to tune this thing were doing a track day, and logworks is way to hard to use since theres not even an rpm reference let alone load. ????

 

My com port for the LC-1 is 3. It changes periodically. You need to do the following:

Start/Control panel/system/hardware tab/device manager/com ports

You should have two ports one for the tactrix cable and another for the serial to USB which is your WB.

If it is correct you may have another issue. I used to get readings like you are getting when I checked LM-1 by mistake before Hamish wrote different code for the LC-1 and before evoscan remembered the WB choice.

 

Logging my LC-1 through evoscan is hit or miss, lately it has been a straight up strikeout. Have you tried using the openport add-on that is included with LW2? Apparently it is slow logging from the ecu, but you can log essential parameters (ign, rpm, knock, load). For 2byte load you need the definitions (high bit, low bit) to add to LW's protocols xml, then add a formula to calculate the final load with the formula calculator, under "tools" on the taskbar. Search for it, it's here in a few threads. The guys from Innovate have posted it as well, I believe. You could tune with logworks to set AFR, then switch to evoscan to clean up the rest. Evoscan is great for convienence, but Logworks has great presentation. In my experience you have to utilize the advantages of the available dataloggers and try to minimize the effects of their weaknesses.

 

Try copying your saved logs to a different location and uninstall evoscan. I have a feeling that something is corrupted.

 

So i have a theory, on the evoscan edit data screen I look at the eval and all it has is an x as opposed to a formula, i believe evoscan is reading the voltage(lambda ) and not converting to afr? Does anyone have the formula from voltage to afr, i can plug that in and try before uninstalling. I used your advice above to log from ecu to logworks2 and is very helpful but rpm logs every 400 or so. Thanks for the tip on that one.

 

you should be able to read rpm in 30 increments in logworks. something along the line of 2300, 2330, 2360, 2390,etc.

 

I may have been logging too many parameters at once, was doing rpm, load, map, and timing, but it was def about every 400 rpm. I am uninstalling evoscan and downloading as we speak, and will try again, so noone has the conversion form lambda to afr, i believe its around 2.9-3.0, which would be about right.