Sale ends todayGet 30% off any course (excluding packages)

Ends in --- --- ---

MoTeC M1 Software Tutorial: Lambda Input

Watch This Course

$229 USD $114.50 USD

Or 8 easy payments of only $14.31 Instant access. Easy checkout. No fees. Learn more
Course Access for Life
60 day money back guarantee

Lambda Input


00:00 To get the most out of your M1 ECU, it is preferable to add a lambda input so that the ECU can monitor the exhaust lambda.
00:08 With a valid lambda input, we can then use the ‘Quick Lambda’ function to speed up calibrating the engine efficiency table.
00:15 This also gives us the option to use the closed loop fuel control system we have already looked at and data log the air fuel ratio.
00:24 There are a few options when it comes to adding a lambda sensor to your M1 and we will look at them in this module.
00:31 The M1 can receive lambda data from either a MoTeC LTC or ‘Lambda To CAN’ module or from a MoTeC PLM or ‘Professional Lambda Meter’.
00:42 Regardless what product you are using, the lambda data is sent via CAN and we need to configure the ECU so it knows what to look for and where to look for it.
00:52 We can also configure multiple lambda measurement devices and the M1 can accept a single lambda input from the collector, one lambda input per bank or even an individual sensor for each cylinder. We will look at setting up each of these options.
01:09 Let’s start by looking at a single lambda input located in the exhaust collector as this is probably one of the most typical installations.
01:18 We need to head to the ‘Initial Setup 2’ workbook and then the ‘Lambda Single’ worksheet.
01:24 We need to change the ‘Exhaust Lambda Collector Mode’ to ‘Enabled’ first.
01:29 Now we can select the ‘Exhaust Lambda Collector LTC Index’ which defines which LTC unit is providing this information.
01:38 Each LTC can be configured with its own index - For example the CAN Address for a single LTC is normally four sixty.
01:46 This becomes important when you are dealing with multiple sensors.
01:50 Next we have the LTC type which will depend on what you are using.
01:55 Options include LTC, PLM or LTC N which is suitable for the NTK version of the LTC.
02:04 We also need to define which CAN bus the LTC is connected to.
02:09 This should be sufficient to make the lambda data available and if we press the squiggle icon, you will be able to see all the channel data related to the LTC input being displayed.
02:20 Before we move on we have a few more settings to discuss.
02:24 At the bottom of this worksheet you can see we have the parameter ‘Exhaust Lambda Filter’ and this can be used to filter the input from the lambda sensor.
02:33 If this is set to zero it is unfiltered and you may find the channel is quite erratic while obviously if the filter value is too high the response of the sensor will be compromised.
02:44 A filter value of twenty milliseconds gives a good compromise here.
02:49 The last two parameters on this worksheet control how the LTC heater is used.
02:55 ‘Exhaust Lambda Power Save Delay’ can be used to keep the LTC heater powered up after engine shutdown.
03:02 This function can be used to provide a lambda measurement during a subsequent engine startup if desired.
03:08 Normally the LTC operation is paused during startup and the heater operation is delayed by the ‘Exhaust Lambda Engine Run Time’ value to protect the lambda sensor from moisture.
03:20 If you want to monitor lambda values during engine start up, this value should be set to zero.
03:26 That covers configuring a single lambda input, but let’s see what is involved in configuring two inputs for individual bank lambda measurement by heading to the ‘Lambda Bank’ worksheet.
03:37 There shouldn’t be any real surprises here and the settings should be relatively intuitive.
03:42 If you want to use individual bank lambda, you will need to enable the ‘Bank One’ and ‘Bank Two’ modes and then select the appropriate LTC index to correspond to the LTC fitted to each bank.
03:55 The CAN Address for a second LTC is normally four sixty one.
04:00 If you are wondering which bank corresponds to what cylinders, remember that this is one of the first parameters we set up in the ‘Initial Setup’ workbook, under the ‘Engine Details’ worksheet.
04:12 This is where the M1 defines which cylinder is on which bank and this same bank reference is used by the lambda configuration.
04:20 While it isn’t common, the M1 also supports individual cylinder lambda measurement with multiple LTCs.
04:26 This feature can be used to monitor and adjust any lambda discrepancies between different cylinders.
04:33 Setting this feature up is really a repeat of what we have already looked at, but this time we will go to the ‘Engine Systems’ workbook, and then the ‘Multi Exhaust Lambda’ worksheet.
04:43 The adjustments here should be pretty familiar by now and if you want to use this feature you will need to enable the mode for each cylinder and then define the LTC CAN Address, LTC type and which CAN bus each LTC can be found on.
04:58 When you are calibrating the efficiency table, you will be referencing the ‘Exhaust Lambda’ channel, and how this is derived will depend on how the lambda input is configured.
05:08 If a single lambda sensor is mounted in the exhaust collector, then this becomes the Exhaust Lambda channel.
05:14 If you have a lambda sensor in each bank of an engine, the Exhaust Lambda will be the bank average, and if you are utilising individual cylinder lambda the exhaust lambda reading will be the average of all the cylinders.

We usually reply within 12hrs (often sooner)

Need Help?

Need help choosing a course?

Experiencing website difficulties?

Or need to contact us for any other reason?