![]() This means That the ECU did not fail the test that cause the fault code to be logged, but then it did not pass any test either, in essence it does not yet know if there is a problem in that circuit or not. This feature actually means that after clearing the fault code memory, every single possible fault code that could be stored by each ECU is in fact stored right from the beginning but with a associated status of being a not tested Diagnostic Trouble code. This bit defines if the self diagnostic test associated with, or that would cause a particular code to be logged, has been performed by the vehicle system control unit or not, since the last time the fault memory was cleared. Not tested fault codes : One of the status bits in this status byte that is allocated to each possible code is a test state bit.Tested fault codes : This function is like the traditional fault code memory in that any faults shown here have been tested and have failed.In addition another byte is used to indicate the faults status, Ie Permanent, Pending, Intermittent or Historic. However our system translates the entire code to readable text, including the detail. These 2 Byte code meanings are by definition quite basic with a third byte then being used to provide additional further detail in the form of a lookup of nearly 100 possible fault causes of 256 possible, EG open circuit, Short to Battery, Out of Range, too high, out of range too low, implausible value etc, This last byte value is sometimes described as being added to the previous five digit code, giving a resultant seven digit code. These translate to a 5 digit codes that are prefixed with a letter, P, B, U, C that groups each fault respectively into Powertrain, Body, Chassis and Network related. The ISO 14229 standard defines Fault codes, which it calls DTC's (Diagnostic Trouble Codes) as 2 byte code values / meanings (up to 65536 possibilities). It therefore requires some understanding to use and interpret correctly, but is far more informative and helpful in helping properly fix any problem in a vehicle. It is one of the very first vehicles to support this new standard and as such not all ECU's fully support all its features or get it exactly right. The functionality of each of this vehicles ECU's in respect of its strategy / methodology for detecting, recording and reporting faults follows the format of a new and very advanced industry standard known as ISO 14229. In some cases Abbreviations are used to save space on the LCD display of the EXTREME, in which case the abbreviation we use is shown in capitals within square brackets The Reading Fault codes ability of this software module is also supported by the Stand Alone Diagnostic capabilities of the Faultmate MSV-2 Extreme. ![]() ![]() SM136 - 2010 RANGE ROVER - Diagnostic Capabilities (Read Fault Codes) SM136 - 2010 RANGE ROVER - Physical Details Vehicle makes, models and variants known or believed to be using this vehicle system, required diagnostic lead and degree of known compatibility. SM136 - 2010 RANGE ROVER - Known Fitments Rear Ventilation & Heating Control Module This BUS is not connected to the diagnostic socket but is connected to the Medium speed CAN BUS through the main Audio Head Unit which again acts as a gateway. However the ECU’s related to information or entertainment that might additionally have to exchange video or audio data use a special fibre optic bus called the MOST BUS. ![]() 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. A fault in any one ECU or its removal often has knock on effects in the others, with them storing bus error or missing node fault codes. This allows them to interact with each other at high levels of interdependency, sharing information vital to their operation. The electronics of the 2010 Range Rover code named 元22 are comprised of around 25 separate ECU’s (nodes) which are all interconnected by high speed communication Busses. SM136 - 2010 RANGE ROVER CAN BUS NETWORK - System Overview 2010 RANGE ROVER (SM136) SM0136 - 2010 RANGE ROVER CAN BUS NETWORK - System Help file ![]()
0 Comments
Leave a Reply. |