tephra

iTrader: (6)

ok - are your calculated values (ie IDC and EVOLC1) configured BEFORE this new one?

dan l

iTrader: (3)

My LBS/Min is the very first thing I log. Are you saying that I have to move it down the screen a bit?

tephra

iTrader: (6)

yeah - you need to log your pre-requisites first. So put that new definition after EVOLC1 and IDC...

evo4mad

iTrader: (4)

you can just use the word CALC in the request Id, but you dont want the the car ecu to timeout, so yeah sending a dummy requestid is probably the best way to go anyway.

evo4mad

iTrader: (4)

Yeah WickedE i'm frustrated by it too, trying to fix minority issues causes other issues lol. I added the "disable multithreading" to the logging menu new in v2.5 so give it a go to get any lost speed, by the extra thread, back. I seriously think v2.5 is now better than v.99, and you're right I can't say that for some of the releases in between. But I now get less support calls for v2.4/2.5 than I did for v0.99 so v2.5 is definately much better. Now I think more testing needs to be done around Maptracer and Wideband logging, so thats next on my list, a lot more LC1s are now supported in v2.5 than v0.99.

magyar86

iTrader: (10)

sorry if this has already been discussed but how about making log ids that use the 2-byte pre-requisites. like idc, whp, torque, etc. so ppl dont have to change the existing evals back and forth for when they are logging cars that dont have the 2-byte rom mods. sorry if i dont have the right terms but hopefully your understand what i mean...

fryedchikin

Please fix the Enable Start/Stop by Alarm Triggers.

dan l

iTrader: (3)

V2.4 is working good for me. Its one of the better versions. One bug that I've noticed when clicking on things like MUT2Byte RPM or in this instance Fuel Consumption when graphing. Here is a picture of the error and evoscan locks up:

fryedchikin

I have encountered numerous errors with the graphing too, I thought it was just something with my setup. When those errors do occur I have to use task manager to quit the application and restart, the error handling really needs to be improved.

dan l

iTrader: (3)

Yes it locks it up good, real good. You can kill the boxes but it won't do you any good. You need to cntl-alt-del to kill it.

Thoe99

iTrader: (25)

Anyone find a fix for this?

Jack_of_Trades

iTrader: (17)

I'm pretty sure the reason the fuel consumption wont graph is because when you let off the gas and coast its an infinite value, which it cant log.

evo4mad

iTrader: (4)

I fixed the Innovate LC1 logging on the weekend, and also added a LC1 recalibration feature to the EvoScan menu. I will release it later this week.

I was thinking about capping the Wideband results to "20" so that the graph doesn't go out of scale so easily. Do any of you run AFRs greater than 20 that I should know about?

Jack_of_Trades

iTrader: (17)

21:1 AFR is usually the highest any of the WB setups read. What about the fuel consumption graphing? Can you make a cap on that too?

Asmodeus6

iTrader: (7)

Definitely need to cap the WB at 20. Most don't read below 8 or 9 either. One of the problems I encountered when trying to build a gauge panel was reconfiguring the scale after I assigned an input. Even after you had it up and running, if you saved it. Reloaded ES, it would error its a** off and dump all my gauges back to th originals. IE useless.

Honestly this is the FIRST version of ES that has even WORKED for me AT ALL since I picked it up almost a year ago. Its only version that will log without disconnecting every 2 seconds. So I'm not complaining. I gave up on it and used logworks up until maybe 3 days ago. Wiped every trace of ES off the computer, and gave 2.4 a shot. And it finally works. None of the others did.

Could be me, or my laptop... but this one works. ? So, yay!