Evoscan 2.3 released.
Jul 5, 2008, 06:04 AM
#92
Evolved Member
iTrader: (5)
Join Date: Jul 2004
Location: ORLANDO
Posts: 974
Likes: 0
Received 0 Likes
on
0 Posts
Anyone know what mandatory variables we need to log so Evoscan can come up with power and torque? For example I need to display power & torque on 3rd gear pull, but under "acceleration runs found" is not displaying anything (while sometimes it does).
Is it mandatory to log estimated g/rev, horsepower and torque so I can get power & torque?
Is it mandatory to log estimated g/rev, horsepower and torque so I can get power & torque?
Jul 5, 2008, 04:30 PM
#95
I'm back to 2.1, personally. 2.2 was stillborn for me because of the loss of LC-1 logging functionality, and 2.3 is completely unusable because of the logging jitters. Plus, it's amazing how much bloat has set in; 2.1 worked fine on my win2k tablet with 256MB of memory, but 2.3 is absolutely choking if I have the poor luck of having anything else open at the same time (like, say, ecuflash). 
If logging with LogWorks didn't feel like such a hack, I'd be there in a heartbeat. I need to finish writing my own damn logger already.
If logging with LogWorks didn't feel like such a hack, I'd be there in a heartbeat. I need to finish writing my own damn logger already.
Jul 5, 2008, 07:14 PM
#98
wow. I only had one report of this problem on my support desk, I didn't realise it was such a big deal. I'll release a new version today.
I spent hundreds of hours in v2.3 to make it faster with multithreading etc. I'm guessing multithreading is actually made everything slightly bloated but it definately makes things more responsive, i.e you can actually controll the interface while its logging now. I may change it so that you have the option of using the multithreading or not.
I spent hundreds of hours in v2.3 to make it faster with multithreading etc. I'm guessing multithreading is actually made everything slightly bloated but it definately makes things more responsive, i.e you can actually controll the interface while its logging now. I may change it so that you have the option of using the multithreading or not.
Jul 5, 2008, 08:22 PM
#99
At some point, I'll probably plunk down for an Eee and add a touchscreen to it, but for now, this does the job.
(Honestly, my workflow probably lends itself better to something else anyway; a small-footprint logging component like Mitsulogger, with a detailed log analyzer/visualizer like DataLogLab, perhaps. Gauges and real-time display aren't something I find very useful except for very rare circumstances; I have real physical gauges and other full-time alerting for that, and a text editor lets me see the numbers just as well as an on-screen display.)
Jul 5, 2008, 11:02 PM
#100
...
I spent hundreds of hours in v2.3 to make it faster with multithreading etc. I'm guessing multithreading is actually made everything slightly bloated but it definately makes things more responsive, i.e you can actually controll the interface while its logging now. I may change it so that you have the option of using the multithreading or not.
I spent hundreds of hours in v2.3 to make it faster with multithreading etc. I'm guessing multithreading is actually made everything slightly bloated but it definately makes things more responsive, i.e you can actually controll the interface while its logging now. I may change it so that you have the option of using the multithreading or not.
Jul 6, 2008, 12:22 AM
#101
Yeah I'm gonna make a seperate .exe that has a small footprint for those who don't need the xtra features. that will just do the bear minimum features for logging to csv. and it will use the same settings data.xml so you can set it up in the full evoscan, and run it in the tiny footprint exe for maximum dyno logging performance.
Jul 6, 2008, 06:53 AM
#105
lol, not much gets past you lot 
I am making one more change for v2.4
In v2.1 onwards I changed the AFRMap to match the ecuflash AFRMap values...
in v2.0 AFRMAP = x
LOADCALC = 5*513*((0.256*x)-(-0.1026*[Battery]+1.8741))/[AFRMAP]
in v2.3 AFRMAP = (14.7*128)/x
LOADCALC = 5*513*((0.256*x)-(-0.1026*[Battery]+1.8741))/[AFRMAP]
in EvoScan v2.4 I will leave the AFRMAP as (14.7*128)/x and I'll change the
LoadCalc to match correctly with =5*[InjectorScalingTextBox]*((0.256*x)-(-0.1026*[Battery]+1.8741))/(14.7*128/[AFRMAP]) and I'll add a box to the form for you to easily change the Injector Scaling (cc/min) value.
I am making one more change for v2.4
In v2.1 onwards I changed the AFRMap to match the ecuflash AFRMap values...
in v2.0 AFRMAP = x
LOADCALC = 5*513*((0.256*x)-(-0.1026*[Battery]+1.8741))/[AFRMAP]
in v2.3 AFRMAP = (14.7*128)/x
LOADCALC = 5*513*((0.256*x)-(-0.1026*[Battery]+1.8741))/[AFRMAP]
in EvoScan v2.4 I will leave the AFRMAP as (14.7*128)/x and I'll change the
LoadCalc to match correctly with =5*[InjectorScalingTextBox]*((0.256*x)-(-0.1026*[Battery]+1.8741))/(14.7*128/[AFRMAP]) and I'll add a box to the form for you to easily change the Injector Scaling (cc/min) value.