UEGO 30-2310 Evoscan scaling

[Chris@Rvengeperformance]

Not sure what their product is but the equation can't possibly be correct for the 30-2310. It would indicate 8.5 AFR for 0V and 18 AFR for 5V which is not what the sensor does.

that is the formula an aem rep sent me for the inline wideband and it works 100% perfect.

[Chris@Rvengeperformance]

You don't want to change the scaling for logging the wideband in chrome. That formula is setup to read the output of the scaling tables. Using that formula will only show some odd readings.

I would also shy away from using the ECU ground for some of these aftermarket sensors as I've run into issues with it offsetting all the other sensors readings.

it worked perfect, i logged wideband all the time. I think I actually used chassis ground just out of laziness.

[Chris@Rvengeperformance]

didnt you say your wideband is reading 12.9 at idle Jim?

[Greg E]

it worked perfect, i logged wideband all the time. I think I actually used chassis ground just out of laziness.

You use the fuel tank sensor request and not the wideband scaled request?

Both AEM and LC1 instruct the sensor to be hooked to chassis ground. I'm starting to understand why.

[Chris@Rvengeperformance]

You use the fuel tank sensor request and not the wideband scaled request?

probably, I think I had issues with the rom based scaling table giving me good numbers. i'm skeptical of the published info for the inline aem wideband. using the info in their docs was way off, the formula the aem guy sent me worked better.

[Greg E]

probably, I think I had issues with the rom based scaling table giving me good numbers. i'm skeptical of the published info for the inline aem wideband. using the info in their docs was way off, the formula the aem guy sent me worked better.

As long as you have an accurate voltage vs AFR chart, the ROM based scaling should be dead nuts on.

Based on the formula you got from the AEM tech, 5V = 19.14 and 0V = 7.13. Enter those numbers into the table and interpolate in between.

[Jimvr4]

I'm sorry Chris, I should have checked your formula more carefully. It is exactly the same as mine when you do the math!!

I do have 12.9 AFR at idle but that's another issue

[Greg E]

Just curious: how come you two don't use the wideband scaled option in chrome?

[Jimvr4]

I thought I was

I have the sensor wired to pin 93 and I have the equation from post #1 programmed for the scaling for request BF.

What other way is there and why would I use it?

I also want this to work using the standalone tactrix 2.0 module with the SD card, and it DOES!!

I'm trying to use a gauge layout now when I use Evoscan for logging and found one that uses the External Wideband so I changed it to use Wideband Scaled but I don't get any readings on the gauge even though the logging works fine. Any light on that?

[Greg E]

I thought I was

I was afraid of that... Who told you to edit the request formula for that request?

In chrome, the AFR scaling is done in the ROM, not in EVOScan. There's a few reasons why I did this but let's just say without getting into detail that it has to do with future versions of Chrome.

http://www.3sgto.org/tuning-engine-e...tml#post211632

All you do is setup the table and log the wideband request. Changing the formula will only cause it to spit out erroneous numbers. This maybe why you're seeing 12.6 AFR at idle. It may not necessarily be that the engine is running rich.

The correct formula for wideband scaled is x*.0627+7

To answer your question about the gauges, it doesn't work because that parameter is looking for a serial input not a MUT request. You have to make a new gauge for wideband scaled.