Well, it seems like there are quite a few bugs with the new Evoscan v2.1 so I figured I'd make a thread to accumulate any inaccuracies or issues people have already found.

I'll start.

"Hi my name is Jamie and I'm an alcoho...." Woops...wrong place,wrong time


Injector Duty Cycle Formula:

Incorrect = .256*[InjPulseWidth]*31.25*x/1200

Correct = [InjPulseWidth]*31.25*x/1200

The only thing incorrect about the original formula is the accidental addition of.256*

(Edited note) you can also use this formula which has the same results:

[InjPulseWidth]*[RPM]/1200




Formula for RPM MUT 2 byte Mod:
The formula for RPM 2 byte mod is wrong (31.25*x) you need to use this formula:

1000*x/256





Injector Duty Cycle Formula (2 byte mod):
If you have done the RPM_MUT_2byte Mod, use this formula for more accurate readings for your IDC:

[InjPulseWidth]*[RPMMUT2Byte]/1200




Converting Fuel Consumption from litre/100 Kms to MPG (U.S. Gallons):

You must first correct the Injector Duty Cycle formula for this to work.

[Speed]/(513*4*[InjDutyCycle]/100*0.015873)

Note: Replace the 513 value with whatever injector scaling you happen to be using in ECUFLash






Converting Fuel Consumption from litre/100 Kms to MPG (Imperial Gallons):
(Australia, United Kingdom, etc...)
You must first correct the Injector Duty Cycle formula for this to work.

1.201*([Speed]/(513*4*[InjDutyCycle]/100*0.015873))


Note: Replace the 513 value with whatever injector scaling you happen to be using in ECUFLash





.

 

are the bits in red the correct values to enter ?

Also with JDM cars in the loadcalc do I need to change from 513 (for injectors) to 542 (as ecuflash see's the injectors) or 560 which is what they actually are ??

 

good thread...can we use this to post some concerns regarding EvoScan?

 

I changed the colors for clarity here. Blue is bad, red is good.

I'm not sure is the load calc is off of scaled parameters or not. If it IS off of scaled parameters you need to edit that value to your scaled #(which appears to be how it was intended to be calculated). Good question though.

You can post any ERRORS you find in evoscan v2.1 or the solutions to errors. Keep anything else in the regular 2.1 evoscan thread.

 

LoadCalc

5*InjScaling*([InjPulseWidth]-(-0.1026*[Battery]+1.8741))/[AFRMAP]

So as it is when you install 5*513*([InjPulseWidth]-(-0.1026*[Battery]+1.8741))/[AFRMAP] is wrong for my car.


I'm sorry but I don't know what the true size is of the usdm injectors, if they are 513cc true value, then that matches what ecuflash has them listed as, and therefore I have no idea what the correct value is that I need to input.

However if they are approx 530cc true value then I know that I need to use 542cc to give the correct loadcalc figures for my car.

Sorry if I have gone on abit there, just want to get it right

 

Ahh, I totally mis-read exactly what you were asking the first time. Yes, you change that value to whatever your injector scaling is. USDM cars use 560cc/min(560ml/min) injectors and are scaled to 513 in ECUFlash. So if you have a JDM car and the scaling is 542, alter the 513 in the formula to 542 and you should be all set.

 

good stuff, cheers for the reply

 

Correction for those estimated power and torque to give more reasonable numbers and using 2-bye load:

Estimated g/rev : Eval => [LoadMUT2Byte]/95
Estimated Lbs/min: Eval => ([gRev]*[rpm])/454
Estimated Horsepower: Eval => [LbsMin]*9.15
Estimated Torque: Eval => ([WHP]*5252/[rpm])

 

I just delete normal RPM/LOAD and rename my 2bytes..

 

Yeah, to get the best results overall its best to do the 2byte RPM, 2byte LOAD (and 2byte airflow I believe) and then go through EVERY formula and replace the basic RPM, LOADCALC values(and whichever other 2byte upgrades you did) with the new 2byte tags.

A lot of people upgrade to 2byte data but forget (or don't realize) that some of the other parameters still use the 1byte data for their calculations.

 

mine reads:
"Error: USB Cable Device Not Responding
Info: Datalogger Ended."

anybody else have this problem? i asked at the help desk on the site and they replied with "you need to use the cable" wth? how dumb am i?

 

The one thing that I believe is different is the BaudRate "auto-detect" feature which sees what baudrate setting is set in ECUFlash (I think lol). If you edited your baudrate to anything than the default for Mitsubishi of 15625 (mine is set to 62500 and wont connect unless I physically enter this value into the baudrate window) your computer won't connect.

 

what is the advantage of 2-byte rpm?

 

In a nutshell, its more accurate because it checks what the actual RPM values are more times per second. So instead of being in stepped incriments its more linear.

 

Right about the increments but wrong about how its accomplished. ;-) Both are checked with the same frequency. 2-byte RPM provides a more precise RPM measurement. The 1-byte RPM gradation is 31.25 RPM. 2-byte RPM gradation is something like 1 RPM (haven't checked exactly). The finer gradation is useful for HP and TQ calculations.