LM-1 Logging Issue
LM-1 Logging Issue
Guys, I thought I'd start here for help since there is knowledge of EvoScan in this forum.
Basically, my LM-1 just decided to stop logging to EvoScan. I'm still using .99, but have also tried other, newer versions of the software with the same results.
The COM port is correct, the PC sees the device connected. I've tried selecting LM-1 and LC-1 from the menu in EvoScan.
Basically, I can select Wideband to log and EvoScan logs perfectly, just with blank cells for the WB. I get no errors. the LM-1 displays the AFR and lambda correctly on the screen and records correctly as well.
This is a portable kit, so I'm using the 12v adapter in the cigarette lighter and the Innovate exhaust clamp for the sensor itself.
Any input would be awesome. Thanks.
Basically, my LM-1 just decided to stop logging to EvoScan. I'm still using .99, but have also tried other, newer versions of the software with the same results.
The COM port is correct, the PC sees the device connected. I've tried selecting LM-1 and LC-1 from the menu in EvoScan.
Basically, I can select Wideband to log and EvoScan logs perfectly, just with blank cells for the WB. I get no errors. the LM-1 displays the AFR and lambda correctly on the screen and records correctly as well.
This is a portable kit, so I'm using the 12v adapter in the cigarette lighter and the Innovate exhaust clamp for the sensor itself.
Any input would be awesome. Thanks.
Go into the LM programmer and see what the fuel setting is and make sure it is set for gasoline 14.7 and not custom. For some reason the innovate stuff will just go random and haywire every now and then and do its own thing...
There are no 1/8" connections on the LM-1. This one has the box that controls everything. So, the sensor and power go to the box and then I go from the box to the computer.
But, since you've mentioned the LC-1 ... the LC-1 installed int he car still logs fine, so i don't think it's a EvoScan issue, but an LM-1 issue.
But, since you've mentioned the LC-1 ... the LC-1 installed int he car still logs fine, so i don't think it's a EvoScan issue, but an LM-1 issue.
Logging via LogWorks, and via the analog output through the ECU, has and continues to work just fine. In fact, with DMA logging, it's far superior.

I suspect something's not quite cooked with EvoScan's Innovate bus support, for some reason, but since I have a workable solution, I didn't really spend any time on it. My results were with whatever the latest beta of 2.6 Hamish posted recently was.
Trending Topics
I have pretty much the same setup as you and it works. EvoScan .99 and an old LM-1. However, I'm using a Serial to USB converter. All this works fine for me.
I wish I could be more helpful in debugging your problem. I don't really have any ideas though.
So it was working before and then now it doesn't work?
I wish I could be more helpful in debugging your problem. I don't really have any ideas though.

So it was working before and then now it doesn't work?
Yeah. It worked fine before and now it doesn't. I'm leaning toward a damaged serial cable. I still haven't tried to verify the fuel setting though.
I just think it's very strange that I don't get an EvoScan error with this thing not functioning. Just a blank column.
I just think it's very strange that I don't get an EvoScan error with this thing not functioning. Just a blank column.
Thread
Thread Starter
Forum
Replies
Last Post





