SM0133 - 2007 DEFENDER - System Help file
Version 1.29
SM133 - 2007 DEFENDER - System Overview
This vehicle is a revamp of the old TD5 Defender and still includes the same Wabco ABS and Lucas 10AS alarm as covered by software modules SM033 and SM031 respectively. It does however include a new engine complete with its management ECU and the matching instrument pack which are connected to together and to the diagnostic socket by a high speed CAN BUS.This engine is infamous in its original fitment in the Ford Transit Van.

System Name Group Name Communication Type
Diesel Engine Management Diesel EMS HS CAN BUS
Instrument Pack Instrumentation HS CAN BUS

SM133 - 2007 DEFENDER - Known Fitments
Vehicle makes, models and variants known or believed to be using this vehicle system, required diagnostic lead and degree of known compatibility.

Vehicle Make Vehicle Model Vehicle Variant Diagnostic Lead
Land Rover New Defender 2007 on LD020/LD021

SM133 - 2007 DEFENDER - Physical Details

SM133 - 2007 DEFENDER - Diagnostic Capabilities (Read Fault Codes)

The functionality of this ECU in respect of its strategy for detecting faults follows a new standard known as ISO 14229 which far more sophisticated than any previous method.

The standard defines 2 byte usage for storing code values a third byte for a lookup of the nearly 100 fault causes (Sub Type information), open circuit, etc, another byte is broken into bits used to indicate the fault status, Intermittent, Lamp on etc. There are also a number of counters for each code to count fails and passes for each code, tests for the code, fails since code detected Etc. This Count keeping allows for faults or their status & request to be removed or downgraded after pre set passes first caused then to exists.

Finally there is the option and ability of each code test to store multiple sets of freeze frame data at 4 different points during the count up and fail procedure. The freeze frame data includes new and very useful items such as a distance (odometer) and time stamp in milliseconds.

One of the new status bits allocated to each possible code is a test state bit. This bit defines if the test allocated to any given code has been performed or not since the last time the fault memory was cleared. Technically, this means that after clearing the memory every single possible fault code is instantly listed with a status of not tested. Many will disappear straight away though as the tests are made, however some tests may require the vehicle to be driven or warmed up before their conditions for testing are valid.

This helps validate any fixes greatly because you can see that the state of the actual test for the fault. And rather than waiting to see if the fault re logs i.e. the test fails you actually get to see that the test passed.

To reduce the amount of text on the screen we have put buttons that only show any stored snap shot data for each fault on pressing and to more easily see the difference between Tested and Untested faults we have separated them into two distinct groups.

  • Tested fault codes: This function is like the traditional fault code memory in that any faults shown here have been tested and have failed.
  • Not tested fault codes: This function lists all the fault codes for the vehicle system that are related to self diagnostic tests which have not yet been ran. Unlike traditional fault code systems, where validating that a particular fault was no longer present in the system meant clearing the fault and then running the system in such a way as to hope that the conditions had been met sufficiently to have caused the system to run the relevant test to re log the fault if it was still present. This function actually lists those fault codes that have not been tested due to the conditions for the system to run the test and asses if that fault code should be logged due to a problem existing or passed and therefore not logging nor remaining on the untested list due to the fact that the fault has ran and the test passed.

SM133 - 2007 DEFENDER - Diagnostic Capabilities (Clear Fault Codes)
This function Clears all faults from the ECU memory and resets all counters. If a bus error has occurred or an ECU has been removed, it may be required to clear the fault memory of all ECU's on the vehicle.

SM133 - 2007 DEFENDER - Diagnostic Capabilities (Settings)

Standard Settings
The provided settings for both of the Defenders CAN BUS ECU's, comprise of about a dozen pieces of numerical information related to hardware and software versions, various manufacturers part numbers, the Vehicles VIN number and the Current Network status.

Flash Programming
Both of the ECU's on the Defender are flash programmable so they can be debugged and updated in the vehicle. To achieve this a seperate database utility called Flash File Loader can be called up from within the settings menu. This application helps select the files to be programmed into the respective vehicle ECU and also transfers them onto the Vehicle server ready for programming. The application has its own built in help file.

Instrument Pack Settings

  • Car Configuration File (CCF)
    The Instrument Pack contains a very special block of Data called a Car Configuration File (CCF). This centralized block of data actually defines and sets the current configuration settings for all of the on board CAN BUS systems. The Data block is broken down into hundreds of individual settings which are then shared across the vehicles CAN network in real time so the vehicles on board systems can know their own configuration and that of all other ECU's on the vehicles network.
    By using this single source of configuration setting data, there is no requirement to have any configuration settings held in each ECU, making replacement far simpler. The Manufacturers IDS system also has a back up copy of the original "as Built" CCF data for every single vehicle manufactured by Ford / Land Rover etc, supplied on each DVD ROM update.

    The CCF is read only, although some parameters can be changed using the modify Car Configuration function

    Modify Car Configuration
    Provides the ability to program the Vehicles VIN into the ECU when new only, as well as change the parameters for the Tyre size, Fuel Tank Volume, Speed Limit setting and the Saudi overspeed setting.

    Engine Management Settings

    Injector Grades
    Reads and provides editing and writing capabilities for each of the four groups of 16 Hex injector grade characters as stamped on the injectors.

    The Duratorq Engine ECU can now be programmed with Vehicle Explorer

SM133 - 2007 DEFENDER - Diagnostic Capabilities (Other)

  • Fuel Pump Replacement : The fuel pressure supplied by the high pressure pump is regulated by the suction control valve. Each suction control valve has its own unique electric current/fuel quantity characteristics and these vary across the current range. The differences in pump characteristics are seen in new pumps and the change in pump characteristics over time is regarded as negligible. Hence the engine control module uses the 'pump learning procedure' to calibrate itself for any given pump. This routine must be carried out if the pump, suction control valve and/or module are replaced. Note that pump learning is only carried out on key-on. This function is to clear previously-stored pump learning values, not to re-learn immediately. .
  • Pilot Correction Learn reset: Each injector connected to the engine management has different characteristics e.g. opening times, shutting times and these injector characteristics vary with fuel rail pressure. Normal Pilot correction learning functionality is designed to learn changes to injectors over time, so only allows incremental changes from previously-learned values. If injectors are changed, or cleaned etc, the difference may be substantial. Pilot correction learning may not be able to go immediately to the appropriate values - it may take several engine cycles to reach the correct values. This will adversely affect emissions. This function clears previously-learned values. The next time normal learning is done, pilot correction learning will go immediately to the appropriate value.
    start the engine and run at idle while using.
  • Speed Limitation 82mph (131kph) : Sets the vehicles EMS speed limiter to 82mph.
  • Speed Limitation 87mph (140kph): Sets the vehicles EMS speed limiter to 87mph.