Jack_of_Trades

iTrader: (17)

Ahh, well I'm pretty sure someone said that the 1 byte RPM can only go to 8000rpm. If thats so, 8000rpm/256(1 byte)=31.25 per increment. What does the 2 byte RPM max out at? 2 byte would be 65536 I believe so it'd be [max rpm]/65536(2 byte)= ? per increment.

Jack_of_Trades

iTrader: (17)

Another thing. For MUT 2byte RPM the formula is 31.25*x but isn't it supposed to be 1000*x/256? I'm pretty sure I came across this before and also that is you didn't put the * in the formula, it doesn't work right.

tkklemann

iTrader: (6)

What about the fuel trims? (Fuel Trim Low/Mid/High)



The current formula is => 0.78125*x


Isn't the correct formula => (.1961*x)-25 ??

Jack_of_Trades

iTrader: (17)

That is correct as well. Man, whoever wants to use 2.1 has a good list of things to edit before logging for the first time,lol. Its all a one time change though, after its all said and done you won't have to do it again. Until the next upgrade,lol.

rish197

iTrader: (34)

How is this formula different from the IDC=IPW*RPM/1200? I've always used the other one to calculate IDC%?

Sorry for the n00bie question.
-Jason

rish197

iTrader: (34)

Nevermind, I got it. Haven't had my coffee yet.

rpm = 31.25*x
rpm RequestID =21

mrfred

iTrader: (50)

I looked back at my notes, and the scaling factor for 2-byte rpm is 3.906.

cladden

What is the RequestID for [InjPulseWidth] ?

Thanks in advance.

rish197

iTrader: (34)

29

Jack_of_Trades

iTrader: (17)

The "corrected" formula I posted is technically the exact same as the one you use. Instead of referencing off of the RPM chart they just reference off of the 'x' value directly. Same outcome either way. In v2.1 he just accidentally added the ".256*" part.

Honestly, the best way to do this would be to do the MUT_2byte_RPM mod and use this formula:

IDC= [InjPulseWidth]*[RPMMUT2Byte]/1200

By doing so, you're making the Fuel Consumption rreadings far more accurate too since it will calculate off of the improved IDC readings.

kreionic

iTrader: (14)

I am not using the MUT tables. Can someone post up the formula for 2 byte rpm and what the numbers are that need to be changed. I added 2 byte load and 2 byte airflow this way with just the formula and then changed my numbers in ecuflash. Or is 2 byte rpm a MUT table thing only?

xpro

iTrader: (2)

does anyone know why i cant change com port numbers in evoscan.It stays in com number 1,so its telling me access denied,im trying to switch to port com2,cause i have it set up so in device manager,but evoscan stays in com1.im gona burst this laptop

kreionic

iTrader: (14)

what issues are you having. In all the evoscan I never had to change any com ports besides the wideband one. What issue are you having with v2.1? Does it time out when you start logging?

xpro

iTrader: (2)

i never had any issues with previous version,but with this one its telling me unable to open port com1.access denied.Then i changed open port com to number 2,but evoscan is not allowing me to change com ports even tho there is an option for this.
Someone here mentioned that if you getting message "unable to open port com1"
to try changeing ports in device manager.
thanks

kreionic

iTrader: (14)

Fair enough. its just odd that some are having issues and others aren't