First, I am using a Macbook Pro running bootcamp.

Using Evoscan 2.3 Beta and final 2.3 release, logging my afrs will work for a little while then abruptly cut out when letting off the throttle. It seems like any lean condition 70:1 and up, the logging for wideband stops. Rarely will I see the logging for wideband turn back on.

I had addressed this issue with Hamish during the Beta version but it seems like it's still an issue, at least for me. It seemed less sensitive on the beta version.

Does anyone else have this problem or know of a solution?

 

Likely due to the same sampling rate issues we are all having

 

im getting the same thing with my lc-1...i ended up going back to evoscan 2.1 until the bugs are worked out of 2.3

 

Interesting.

Does 2.1 have 2byteload/rpm?

 

I'm having the same problem with evoscan 2.5. It'll read the LM-1 for a minute or two but then cut off. Still no reply from support @ limitless.

 

Crap. I haven't even tried 2.5 yet.
Does it cut when you hit lean conditions or is it just a time thing?

 

Yeah that happends too. It'll go upto 100:1 then cut it sometimes.

 

Any fix on that bug? I'm having the same issue on Win XP Sp3 / Evoscan 2.5 / LM1.
Going over 80:1 and get error.

 

When I mentioned it to Hamish, this was his reply:

"must be the status flags switching to O2% (Oxygen %)"

and that he'll check it out.

 

I made a .net program to read to log and fill in the blanks with the last value. Here it is.

https://www.evolutionm.net/forums/sh...d.php?t=361521

... use the search...

 

I'll give your solution a try.

However, I could tell you to search as well. I posted this question a whole month before your Log Fixer post. You could've replied here.

 

Happened a few times with me. Just had to restart Evoscan a couple of times and it went away.

 

even after restarting, still bugging when going over 100:1.
The only fix i found is not let over 99:1 ....

So get a co-pilot with you when logging, so he can stop de logs

 

Does anyone have a copy of .99 or any other evoscan versions that don't have this issue? I'm still having an issue with 2.5.