Evo9isLife

If you are logging AFR in evoscan, what values are you using for the "RequestID" and "ScalingFactor" in your evoscan data.xml? Im using a AEM UEGO if that matters.
In this example, the OP is using RequestID: 12 and ScalingFactor: 1 https://www.evolutionm.net/forums/ec...ial-cable.html
In this example, the OP is using RequestID: 3C and ScalingFactor: 10 https://www.evolutionm.net/forums/la...o-evoscan.html
What should I be using?

Evo9_Dubai

You should be logging directly from the uego output.
Logging AFR via rear o2 or alt map is not accurate. No matter what formula you will use.

Evo9isLife

I dont know what you mean, my question has nothing to do with a formula. Wideband will be wired directly to the 73 pin in the ecu.

taylorvw

He is suggesting you use the output signal from the gauge itself to measure AFR vs taping into a pre-used output and altering the formula to get "somewhat" accurate results. Directly from the source via serial/usb and you will be getting fast, accurate results.

Evo9isLife

Obviously I dont want to do that, I want to log afr directly in evoscan. And yes you can make it very accurate.
Seriously? Nobody will take 2 min out of their day to see what RequestID and ScalingFactor they are using in evoscan?

pisyakot

RequestID: id mut table cell
ScalingFactor: for display value in evoscan logger (to match axis)

Evo9isLife

Bruh.... Im not asking what their function is.. Im asking what specific value you are using for each. Please read the first post

XxOLIVERxX

You need to log "External Wideband o2" in evoscan.
It will display live actual afr to the laptop only.
select COM port, make the USB to serial cable adaptor (local electronics/hobby store) to connect directly to the gauge serial output..

This way the ecu doesnt know the actual AFR, only the laptop.
Actual AFR is not needed by the ecu anyway as it works based off calculated load and is pre programmed via MAF scaling. adding the wideband reading to the ecu and then messing with it to attempt and make it read accurately and on time is the stupid way around it in my opinion. as the guys above suggested.

Evo9isLife

FFS, idk why i need to say this again but let me repeat... 1) I do not want to use the serial cable method. 2) It can easily be made very accurate.