Expression code needed for AEM 30-0333 to make my math param work

[benf]

I have a LC1 on drivers side and just added a AEM 30-0333 on the pass side. Both reading in Lambda. I have them setup and read fine. Now I want to do a math parameter to add the 2 Lambda together and divide by 2 to give me an avg. I have everything I need for the expression except I cannot find the code for the AEM. I tried using the ones built in to HP, but the expression didn't work.

thanks

[schpenxel]

How is the AEM connected? What about the LC1?

[benf]

lc1 uses the analog input, the aem uses obd

[Keith@HPTuners]

Just log the parent lambda sensor and it will do the averaging for you of all child lambda sensors.

[schpenxel]

So, use the EQ Ratio "sensor" parameter and it will average them?

For some reason I thought it was setup to now switch between whatever sources it had for that parameter instead of averaging them

Easy enough to check---make a chart with the AEM data (say no to using the generic sensor), also add the LC1 (again say no to generic sensor) then add one of them again an DO use the generic EQ Ratio sensor when prompted.

Should be simple enough to check the math.

[Keith@HPTuners]

The Chart vs Time is the easiest way to test/check how all the maths/sensors work in VCM Scanner.

[benf]

Just log the parent lambda sensor and it will do the averaging for you of all child lambda sensors.

think you lost me...this is my current scan layout and u can see where I attempted to make an avg lambda

[schpenxel]

Post log that has both wB's being logged and I'll try something real quick

[benf]

here is one from this morning ...first log on e85 and nitrous...

[schpenxel]

Make a math parameter with this formula and it should work. I tried using the built in EQ Ratio (sensor) parameter but it didn't work as expected. See screenshot--it was just following the exact same reading as the AEM WB. It's possible the LC1 isn't setup to use the right parameter when you did the transform but I can't really tell for sure.

I also attached the math parameter I made. Load this (or create your own with the formula below) and then use it in a chart/graph/etc. as desired and it should average them together.

Math Parameter:
([40152.238]+[36.238])/2


WB_AVG.MathParameter.xml


WB_AVG.PNG

[benf]

I will give it a shot. The problem you had was nearly the same as mine except my avg was just a duplicate of the LC1. Will load your math and see what happens...thanks for helping

[benf]

just loaded your math formula and my avg is duplicating my LC1 again.

[schpenxel]

Save the layout/post it one more time with that parameter used somewhere and I'll take a look

It worked for me.. I was using it in that screenshot

What version of HPT are you running? Shouldn't really matter as long as it's recent but just checking

[benf]

I'm using 3.2

[Keith@HPTuners]

Like I said, you don't need a math. "EQ Ratio [Sensor]" will do the average for you.

[schpenxel]

That's what I used. It didn't work. "EQ Sensor" in the chart I posted is the EQ Ratio [sensor] parameter and it's just matching the AEM WB reading

I know it should work.. but it isn't for whatever reason

I'm wondering if the parameter used in the transform isn't done correctly--not sure what else it could be

[benf]

did I need to put anything the channels list?

[benf]

this is the file with your math included

[Keith@HPTuners]

This is how it looks in the beta. The chart avg bug fix may not have made it into the 3.2 release.

The "EQ Ratio [Sensor]" is the white line, which is the average of the two inputs (averaging done automatically).

[schpenxel]

To op:

You're using the wrong parameter for the LC1 in that chart--the one you were using is the generic "sensor" one, which is already averaged, which is exactly what Keith was saying it should do. That's why the one you were using and the "averaged" math parameter were matching... they both actually are working properly.

Change the LC-1 chart to the LC-1 parameter and select NO when it asks about using a generic sensor. Selecting no will give you ONLY the LC-1 data. Selecting yes will give you an averaged value of the lambda values it has available.. both from the AEM and LC-1.

If you want an averaged one then you can either use the math parameter or just use the generic sensor like you're already using for the LC-1 chart

This is how it looks in the beta. The chart avg bug fix may not have made it into the 3.2 release.

The "EQ Ratio [Sensor]" is the white line, which is the average of the two inputs (averaging done automatically).

Seems to be working now? I dunno.. I switched back to the regular release and it's working there too. Not sure if I just looked at it wrong earlier or what.