SM0132 - FREELANDER 2 (LR2) - System Help file
Version 1.23/1.27 (Dependant on the ECU)
SM132 - FREELANDER 2 (LR2) - System Overview
The electronics of the Freelander 2, also known as LR2 in the USA and code named L359 are comprised of around 25 separate ECU’s (nodes) which are all interconnected by a number of communication busses. This allows them to interact with each other at high levels of interdependency, sharing information vital to their operation. A fault in any one ECU or its removal often has knock on affects in the others, with them storing bus error or missing node fault codes. Most of the ECU’s use either a High speed (500K) or Medium speed (125K) CAN BUS, which are both wired to the Diagnostic socket. These are also interconnected by the instrument pack which acts as a built in gateway between the two busses. However the ECU’s related to information or entertainment that might additionally have to exchange video or audio data use a special fiber optic bus called the MOST BUS. This BUS is not connected to the diagnostic socket but is connected to the Medium speed CAN BUS through the Combined Integrated Control / Head Unit on vehicles fitted with Low Line Audio equipment and through the Integrated Control Unit on those vehicles fitted with High Line Audio equipment.

High line or Low Line Audio
As mentioned the Freelander 2 has 2 options for Audio equipment most noted by the head unit in the centre of the dash board. The High Line Audio head unit has a Slot for a CD above the LCD display panel and the Low Line audio head unit has a slot for the CD below it's LCD display panel.

The following table shows the ECU’s that may be fitted to this vehicle model.

System Name System Acronym Group Name Communication Type
I6 Petrol Engine Management PCM Petrol EMS HS CAN BUS
TD4 Diesel Engine Management PCM Diesel EMS HS CAN BUS
Central Junction Box BCM Body Control HS CAN BUS / MS CAN BUS
Drivers Door Module DDM Body Control MS CAN BUS
Passenger Door Module PDM Body Control MS CAN BUS
Drivers Seat Module DSM Body Control MS CAN BUS
ABS VDM ABS / ETC HS CAN BUS
Restraints Control Module RCM Safety Restraint HS CAN BUS
Occupant Classification System OCS Safety Restraint HS CAN BUS
Transmission Control Module TCM Transmission HS CAN BUS
Rear Differential Control Module RDCM Transmission HS CAN BUS
Automatic Temperature Control HEVAC Climate Control MS CAN BUS
Fuel Burning Heater FBH Climate Control LS CAN BUS
Instrument Pack IPAC Instrumentation HS CAN BUS
Headlamp Control Module HCM Lighting HS CAN BUS
Audio Amplifier Module AAM Audio and Video MOST BUS
Integrated Head / Control Unit (Low Line) IHU Audio and Video MS CAN BUS / MOST BUS
Integrated Head Unit (High Line) IHU Audio and Video MOST BUS
Integrated Control Unit (High Line) icu Audio and Video MS CAN BUS / MOST BUS
High Level Front Display Module HLD Audio and Video MOST BUS
Digital audio Broadcast Module DABS Audio and Video MOST BUS
Satellite Radio Module SDARS Audio and Video MOST BUS
Satellite Navigation Module SATNAV Audio and Video MOST BUS
Telephone TEL Audio and Video MOST BUS
Steering Angle Sensor STANGLE Steering HS CAN BUS
Parking Distance Control PDM Driver Aid LS CAN BUS
All Terrain Control Module ATCM Driver Aid HS CAN BUS
Trailer Control Module TCM Other Systems MS CAN BUS


SM132 - FREELANDER 2 (LR2) - 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 Freelander 2 2007-2012 LD020/LD021

SM132 - FREELANDER 2 (LR2) - Physical Details

SM132 - FREELANDER 2 (LR2) - Diagnostic Capabilities (Read Fault Codes)

This function is also supported by the Stand Alone Diagnostic capabilities of the Faultmate MSV-2 Extreme, which uses abbreviations, shown here in square type brackets [LIKE THIS] to allow sufficient information for lists of faults or fault code descriptions to be placed on the same screen.

The functionality of this ECU in respect of its strategy for detecting faults follows a standard known as ISO 14229 which far more sophisticated than most other methods.

The standard defines 2 byte usage for storing code values (up to 65536 possibilities) a third byte for a lookup of the nearly 100 fault causes (Sub Type information) of 256 possible, open circuit, etc, another byte is used to indicate a fault status. when a status is set Permanent [PERM], Pending [PEND], Intermittent [INT] or Historic [HIST]. There are also a number of counters for each possible fault code to count fails and passes for each associated test for them, count of number of test performed for each code, fails since code detected Etc. This Count keeping feature allows for faults or their status & request to be removed or downgraded after pre set passes first caused them to exist in the first place.

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

One of the status bits allocated to each possible code is a test state bit. This bit defines if the self diagnostic test associated with a particular code has been performed by the vehicle system control unit or not, since the last time the fault memory was cleared. This feature actually means that after clearing the fault code memory, every single possible fault code that could be stored is in fact stored with a associated status of not tested [NTDTC]. Many will disappear straight away because most tests for them will occur immediately and they will pass, however some tests may require the vehicle to be driven or warmed up before their conditions for running are valid. Of course any test which fails leaves the fault listed but changes the status to a normal tested trouble code [DTC]

This feature obviously 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 did not run yet, passed or failed.

To reduce the amount of text on the screen we have put buttons that only show any stored freeze frame 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 [DTC]: 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 [NTDTC]: 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. Most Not Tested codes [NTDTC] have no status, but some are listed along with Permanent [PERM] status'.

SM132 - FREELANDER 2 (LR2) - 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. This function is also supported by the stand alone diagnostic capabilities of the Faultmate MSV-2 Extreme

SM132 - FREELANDER 2 (LR2) - Diagnostic Capabilities (Settings)
The settings for nearly all ECU's comprise of 11 pieces of numerical information related to hardware and software versioning, various manufacturers part numbers, Vin number and current Network status. However some of the Main ECU's also contain a very special block of Data called a CCF (Car Configuration File). This block of data defines the configuration for all systems in the entire vehicle. It is broken down into literally hundreds of configurable settings which are then shared across the vehicles CAN network in real time. 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. It is interesting to note that the Manufacturers IDS system has a back up copy of the original "as Built" CCF data for every single vehicle manufactured by them, supplied on each CD ROM. In this way the IDS system can, if the disk they have is later than the vehicle) compare the read from Vehicle CCF against the original and easily see any changes to the configuration. They can also restore the vehicle configuration back to "As Built". Sadly the Configuration file only holds settings for options in the vehicle that the manufacturer wishes to be available to it's dealers or other IDS owning users. Typically therefore it is still possible to alter some configuration of specific ECU's directly and go beyond the dealer possibilities. We intend to concentrate specifically in providing this sort of capability in the future. The Instrument Pack also holds service interval data in resect of how many days, kilometres or litres of fuel to next service due reminder which is provided for reading and edit.

SII Settings
The Instrument Pack contains a function called the Service Interval Indicator which can remind the vehicle owner / driver when the vehicle requires a service or inspection. to accomplish this, it holds information in respect of, when the vehicle was last serviced, what the odometer reading was, and how many days, kilometres or litres of fuel are to be counted to next service required warning. The SII system can be configured in different ways to suit different markets and it can even be disabled completely.
  • Current Odometer (KM): This is the current odometer value stored in the Instrument pack which is stored in Kilometres. This may vary from the displayed value on the Instrument Packs own display due to the odometer offset value. (the bit the dealers can hide on delivery). This value is read only and so cannot be altered
  • Current Odometer (Miles): This is a value derived directly from Current Odometer (KM) value and is converted to display here as Miles for convenience. This value is read only and so cannot be altered.
  • SII service fuel consumption (litres): This is the amount of litres of fuel that can be consumed before the next service required warning event is triggered due to over limit for fuel usage. When the fuel usage SII feature is used and what value is assigned is controlled by the Instrument pack.
  • SII consumed litre count: This is a count value showing the amount of litres of fuel that have been used since last service reset was performed. This value can be altered.
  • SII service distance (km): This is the amount of Kilometres that can be travelled before the next service required warning is triggered due to over limit for distance travelled. The warning may trigger earlier however, by the amount of Kilometres set in the Service reminder Threshold (Km). When the distance elapsed SII feature is used and what value is assigned is controlled by the Instrument pack.
  • SII service distance (Miles): This is a read only value which is calculated directly from the SII service distance (km), and is shown here only for convenience.
  • Early alert limit (km): A value that when used in conjunction with the value shown in the SII elapsed days count plus this value is equal to or greater than the value in the SII service distance, a service reminder will appear after the ignition is switched on.
  • Early alert limit (Miles): This is a value drived directly from the Early alert limit (km) value and is converted to display here as Miles for convenience. This value is read only and so cannot be altered.
  • Last service (km): A read only copy of the Odometer value in Kilometres when the last service reset was performed.
  • Last service (Miles): This is a read only value which is calculated directly from the Last service (km), and is shown here only for convenience.
  • Last service odometer value (km): The odometer value when the last service was performed. This value can be adjusted.
  • Last service odometer value (Miles): This is a read only value which is calculated directly from the Last service (km) and is shown here only for convenience.
  • SII service time (days): This is the amount of days that can pass before the next service required warning is triggered due to time passed. The warning may trigger earlier by the amount of Days set in Service reminder Threshold (Days). This value is usually fixed by an IDS or other system according to a market lookup table and typically remains unchanged, but you can alter this figure as desired.

  • SII elapsed days count: Amount of days elapsed since the last service reset, this can be altered as desired.
  • Early alert limit (days): A value which when applied in conjunction with the SII elapsed days count value, the SII service time (days) and the SII Early Alert limit status, causes driver alerts to be issued whenever the ignition is switched on.
  • Last service (days): Days elapsed since last periodic service reset.
  • Last service type: shows if the last service type was an Oil Change, Inspection or periodic.
  • SII Driver Alerts: Indicates if the service interval early warning function is enabled or disabled. Acts like a master on off switch to the entire SII / Service Interval Indicator system.
  • Periodic inspection display: Indicates if the periodic inspection display Driver alert function is enabled or disabled. When enabled the Driver will briefly be reminded of the day values leading towards a service reminder alert at every ign on.
  • Remaining distance display: Indicates if the remaining distance display Driver alert function is enabled or disabled. When enabled the Driver will briefly be reminded of the distance values leading towards a service reminder alert at every ign on.

    • Car Configuration Data
  • The Car Configuration data file now has Read/Write capability. Please note that most settings are set as Undefined and at this time cannot be changed.