Megasquirt Support Forum (MSEXTRA)

I was wondering why is there not a lambda AFR table in mega log viewer? Maybe I missed something.

msl

Not sure I understand you correctly but if you want to display the Lambda value instead of AFR that is possible. You have to make sure you have chosen Lambda as a parameter to be logged in your TS logging profile.

Look at the picture. The lower right in the pull down menu. There is Advanced table one, Advanced table 2, Advanced table 3, AFR table 1, AFR table 2, etc.... No lambda table.

Interesting point...

In TS it is still the AFR table, but the values are shown in Lambda if that is selected in project properties. MLV doesn't take note of the LAMBDA setting in project properties.
I'll put that on the todo list.

Okay phil thanks a lot. I talked to one of the younger guys at EFI analytics today and they said to send a screenshot but I'll let him know that you replied.

I'm not sure if it is related to this topic but I have noticed also that if Lambda is chosen in project properties the lambda target gets written to datalogs as AFR and not lambda. There is no logged field Lambda 1 Target.

To be honest I am coming around to the idea that the most robust way of working with Lambda is to tell TS that you are using a standard wideband in project properties but enter Lambda values into the sensor cal and target table and accept that it will still be called "AFR". Not ideal really...

motthomas wrote:I'm not sure if it is related to this topic but I have noticed also that if Lambda is chosen in project properties the lambda target gets written to datalogs as AFR and not lambda. There is no logged field Lambda 1 Target.

To be honest I am coming around to the idea that the most robust way of working with Lambda is to tell TS that you are using a standard wideband in project properties but enter Lambda values into the sensor cal and target table and accept that it will still be called "AFR". Not ideal really...

That is controlled by the ini for your firmware.
What firmware are you using?

You can add your own Lambda Target field to any firmware using the Custom channel editor in TunerStudio Ultra, or work in the custom.ini file.

LT401Vette wrote: That is controlled by the ini for your firmware.
What firmware are you using?

You can add your own Lambda Target field to any firmware using the Custom channel editor in TunerStudio Ultra, or work in the custom.ini file.

Ok I take your point about using a custom .ini file and this would probably sort everything. However I don't just use TS. I also use MSDroid for logging so custom .ini has the potential to have me over when swapping between platforms.

I do currently use a custom field in TS to log Lambda target but it's a calculation based on Target AFR which isn't the point. Having to do that or needing a custom .ini defeats the purpose of having a specific Project Properties choice to deal in Lambda.

The project properties solution is pointless if it doesn't do Everything Exactly the same no matter what you choose. People like me choose Lambda in project properties because we want to use Lambda instead of AFR not as well as.

In my opinion, the Lambda properties option should be removed completely and everyone should have to use the standard linear wideband option and the sensor calibration and stoichiometric AFR entry used to define whether you are working in Lambda or AFR of whatever fuel. However to make this approach robust, a single stoichiometric AFR entry is needed (currently 2 iirc) and any AFR calculations within TS and/or the code should use the single input value. I would need to look at this in detail again but I believe there are currently calculated fields in the .ini file that use 14.7 in the calculation no matter what stoichiometric AFR is input. I found these while I was trying to use a different stoichiometric AFR some time back and noticed some anomalies in the ECU calculations.

BTW I'm using MS2EXTRA 3.4.2 firmware for Microsquirt.

Sent from my GT-I9305 using Tapatalk

Hi Phil,

On a related note to my above posts, I have found that the transformation from lambda target to AFR target appears to be a part of the TS software and uses 14.7 as the multiplier rather than the stoich AFR which the user inputs in the General Settings page. I wondered if you can confirm this? More details in the below linked topic.

http://www.msextra.com/forums/viewtopic ... 91&t=68068

motthomas wrote:Hi Phil,

On a related note to my above posts, I have found that the transformation from lambda target to AFR target appears to be a part of the TS software and uses 14.7 as the multiplier rather than the stoich AFR which the user inputs in the General Settings page. I wondered if you can confirm this? More details in the below linked topic.

http://www.msextra.com/forums/viewtopic ... 91&t=68068

It is done in TS, but based on the ini file.
So what is used for stoich, is based on what ini / firmware you have.

In many cases it is using a hard 14.7 because that is the base AFR used when sending the AFR calibration tables.