I just tried a couple other things. I relocated the gauge grounds better. No change. In Evoscan, I changed the Eval to "x" to see what would log. It logged values of between 9 and 16 at idle. That's strange as I should read the same volts being output by the gauge analog output wire of something like 2.8V to 3.2V at idle. I then tested the gauge analog output wire directly with a volt meter. It read 2.8V to 3.2V at idle just like it should. So, there is definitely some type of factor being applied to the voltage signal by the ECU as it goes through the O2 signal pin or by Evoscan before it goes to the Eval formula in Evoscan.

Please, can anybody help me?

 

Bump for help

 

I'm going that method as well. Can you please explain how you set up Evoscan for this? What is your eval formula, request ID, Min, Max, scaling... ?

 

your eval formula will vary car to car. the best thing to do is create it yourself.
you just need 3 data points. with that you can make a parabolic function.

i read this post and followed it. my readings in evoscan match my gauge damn near perfectly.
https://www.evolutionm.net/forums/9933717-post119.html

give that a read and try figuring that out. i can help guide you in the right direction if you need help. i'll post when i get home because that is where my spreadsheet with my calculations are.

 

That's an interesting method. Maybe I didn't follow, but how do you determine the exact AFR with the corresponding volts and Evoscan "X" values at a given point in time with the engine running? It would be easy documenting the free air test, but I am not sure how it can be done with three constantly changing values. How did you do that.

 

yea, that's what i need to go home and double check for you.

i know i logged the rear o2 address which is o2 voltage as seen by the ecu. the other thing i may have logged was actual AFR via usb cable from my aem uego controller. i understand you might not be able to do that due to no serial/usb out.

there are alternatives however:

0.00 8.43 1.40 10.64 2.81 13.99 4.21 17.31
0.16 8.43 1.56 11.02 2.96 14.34 4.37 17.69
0.31 8.43 1.72 11.40 3.12 14.72 4.52 18.05
0.47 8.43 1.87 11.75 3.28 15.10 4.68 18.05
0.62 8.79 2.03 12.13 3.43 15.46 4.84 18.05
0.78 9.17 2.18 12.49 3.59 15.84 4.99 18.05
0.94 9.55 2.34 12.87 3.74 16.20 NA NA
1.09 9.90 2.50 13.25 3.90 16.58 NA NA

1.25 10.28 2.65 13.61 4.06 16.96 NA NA

that is the calibration for your aem 30-5130. you might check your voltage at free air as reported by evoscan by logging your rear o2 address.

http://www.aemelectronics.com/Images...%2030-5130.pdf

 

Yes, I recognize that graph - been staring at it for weeks lol. If there was a way to log actual volts in Evoscan from the gauge output wire, that could be directly compared with the Evoscan "X" value. Together with this graph, all three variables would be known in any point in time and then the conversion could be calculated.

In a more primitive way, I could video record the windband gauge, the Evoscan "X" value and a volt meter all at the same time while driving .

 

yea... you might need to! or atleast have someone watch the gauge and have them record the minimum AFR and place that with your lowest voltage.

i checked my notes. here is what i did:

point #1. my free air AFR was 19.7 which was 4.45 volts on evoscan. the x value was 228. (x=V/0.01952 using my formula in evoscan)

point #2. 14.7 at idle was 2.59616 volts. x value was 133.

point #3. this was where i used my usb out. my third value was 9.8 which was .507252 v, an x value of 26.

went to wolframalpha. typed in:
'parabola (26,9.8196), (133,14.7), (228,19.6686)'

got:
y = 0.000033118x^2 + 0.0403445x + 8.74823

which formatted for evoscan is:
x*((0.000033118*x) + 0.0403455)+8.74823


this matches my phone (aem xwifi gauge) and my usb perfectly.

 

I'm logged thru the ecu via the rear o2 sensor. Works well after you get the scaling correct.

WBO2: Request “3C”, Function “8.43+(18.05-8.43)*x/255”

 

can you not do this:
http://highboostforum.com/forum/show...r-AEM-wideband)

 

I tried that formula this morning and it is very close. Idle is about 0.3 AFR lower than what the gauge reads, but it seems right on in the richer (11.0) AFRs. Thanks!

Last night I did numerous trial and error tests at idle and at partial WOT and came up with a formula of 7.95+(18.05-8.43)*x/215. This seemed to read the same as the gauge at idle and at richer AFRs.

 

No. My gauge does not have a digital output signal wire that can use the serial port connection method. That was my first try, but then I found out the analog face AEM wideband gauge does not have it. That left me with only one option.

 

Hi Fantrman,
im having the same nightmare and im using the aem eugo digital wb.
Ive gone thru the whole process according to the forums & aem manual but yet i still cant link my wb to evoscan!

What happening???

Ive link my blue wire (serial output) to pin 2 & grounded pin 5.
Done all the setting on evoscan, aem eugo 9600, selected COM 3 and still cant get it link on my evoscan external; wideband!

Help!!!!

 

Hi anyone to help?

 

I'll help, but I don't really understand what you are saying.

First, do you have a digital face wideband or an analog face wideband? The wiring is a little different for each. Second, are you trying to log through the ECU or through a serial port directly into the laptop?