Can I auto populate Lambda readings?

[TurboTito]

I just purchased my first Motec ECM, about to begin using the I2 standard software to begin tuning cruising. I recently watched a youtube video posted by MOTEC Global about tuning based on logged data. It is said that I have to write down each Lambda reading for each plot for my MAP vs RPM table, then to perform the changes for each plot using the Lambda Was feature. Is this still the only option, or can the MAP vs RPM table be done using a quicker method now?

Thanks,
Terry

[NathanB]

Hey Terry,

There is no quick or auto populate method for doing this. The best method to achieve what you want to do will also depend on what specific MoTeC ECM you are using.

[TurboTito]

I am currently running the PNP M150 that was built by John Reed Racing.

[Stephen Dean]

The "Lambda Was" function accessed through the L key is used here, this allows for you to find the matching data point in the efficiency table, press the L key and enter the actual and expected Lambda values for that point from the logging. You will need to have the Lambda Normalised channel logged as this is the Lambda value without Closed Loop compensation. If you do not have Closed Loop activated, then the normal Lambda channel can be used.

[NathanB]

Ok, so with the M1 ecus, you will want to log the following channels at the following recommended rates:

Engine Speed - 50hz
Exhaust lambda (as required, and depending on what sensors are fitted) - 50hz
Exhaust lambda normalised (the calculated lambda before any closed loop trimming is applied) - 50hz
Fuel mixture aim - 20hz
ambient pressure - 1hz (5 or 10hz if you have a sensor and the ambient isn't derived by the estimate)
Inlet manifold pressure - 50hz
inlet manifold pressure estimate - 20hz
throttle position - 20hz
closed loop bank n trim (bank 1 and bank 2 if a v engine/ if fitted)
closed loop bank n trim average (this channel only works if logging was done whilst no pc connection was active. It will tell you what the average closed loop trim was in the active load site)
closed loop trim min / max - 10hz
closed loop period - 10hz
closed loop state - 10hz

for your workspace in i2, you can also do a simple maths channel to work out how far away the lambda was from the fuel mixture aim, however this will not take into account the closed loop period (the delay between the combustion leaving the chamber and being read by the sensor.

Maths example: ( 'Fuel Mix Aim' [LA] - 'Exh Lambda Bank 1 Normalised' [LA] ) * 100

Otherwise, where possible, having a laptop plugged in and connected to the ECU with M1 tune open, going for a drive, and then reviewing the paused data in tuned and making alterations with the "Q" function on the efficiency table is quite effective, as you have the benefit of the crosshairs to tell how well you were lined up with a load site.

fuelling data from logging.png (101.01 KiB) Viewed 5735 times

[TurboTito]

Thank you both very much. The information provided was very helpful and I will give it a shot this evening. Thank you both again.