http://forums.plastikracing.net/view...?p=52097#52097
Go here and scroll down to just under half the page. No more converting volts to AFR. YAYYY
I'm still not sure if this is for the 32-4200 or 4100 as I have the 4100 and previously i had to convert my volts up .5 a AFR point because the MLV values were were not equal to what came in my manual.

 

This looks like it should work for the NGK AFX too!

Gratzie.

 

if it ouputs 0-5v 10-20:1 AFR, then you coulda just selected LC-1

 

I tried this with the 9-16afr and 255-0 ref of my NGK AFK. It got me reading in AFR on the table... but it wouldn't retain the leaner cells. Doesn't appear to play nicely with mine sadly.

 

thanks for the info. edited my files and looking forward to hooking up to the car and tuning.

 

It worked for me thus far. Going to it out later today.

 

Found this old thread searching for the cure for the "AEM shows volts not AFR" (on the VE table)

I have the 30-4100 AEM UEGO & from the posts I've found so far it looks like I can either set the LC-1 in the configurator, or edit my msns-extra.ini file.
How will I know if it's reading correctly though? Is it simply "get the AEM gauge & Megatune to agree on a value"?

 

when i set it to LC-1 in the configurator it was completely off. i used the described method instead. only way i found to see if they agree was to hold the laptop near the gauge. snap some pics. then look at the pics.

 

So the object is to get the gauge & laptop display to match.
That's how we know the wideband is setup correctly in the MS?

 

sorry, i thought there was a link to this thread somewhere in here http://forums.plastikhosting.net/viewtopic.php?t=2221

that describes how to get your gauge in MT to match your AEM gauge display

while the author had better results changing the 9.72 to 10.02 I had better results using 9.48. experiment a bit. back up the original lambdaSensors.ini file just in case.

 

Sorry my question wasn't clear.
I was trying to ask, "How will I know if it's reading correctly? Is it simply "get the AEM gauge & Megatune to agree on a value"? "

I think you are saying "yes" get the 2 to agree on a value & they are set correctly.

Thanks for that link though. I hadn't seen mention of the lambdaSensors.ini file in the threads I'd found. And I see what you mean about needing a camera to look at both gauges at the same time. Good Idea!

 

The AEM UEGO is calibrated from the factory using a calibration resistor. There should be zero difference between the outputs from one UEGO to the next but there is for some reason.

What the gauge reads should be correct but we will never really know if it is exact unless you compare it to multiple other widebands such as a dyno's wideband and a few more and then come up with an average difference.

All this method does is change the slope of the AFR curve so that around 14.7 the two gauge read the same. Go by what your gauge says, do what you can to make megatune read the same.

 

i have never had a reading difference on my ugeo and MS using the "aem liner" in the conf

 

We're talking .1-.5 AFR difference. You have to be fast to notice. I guess..

 

Thanks for the clarification.

 

From what I understand it doesn't matter really if the gauge matches in Megatune because:

1. your MS is reading the voltage from the gauge directly so EGO correction would have no dependence on what MT is showing.

2. MLV VE Analyzer reads the voltage values from the log, not an AFR value.

However, that leads me to believe that the same calibration correction should be done somewhere in MLV but when I posted on the MSI forums nobody was able to help. Anyone?