SDD (Symptom Driven Diagnostics)  

SDD is the latest development by JLR in vehicle diagnostics. Designed to be easy to use and extremely efficient in fault finding. Conventional diagnostic systems read fault codes and offer them to the end user. It is then upto the the end user to analyse the codes and find the vehicle fault from the data that has been provided.

SDD instead asks the end user the fault with the vehicle and progresses to analyse the fault codes and offers the solution to fix the vehicle on a relevance to likely ratio.

Should you wish to intervene and only see the fault codes then this option is open to the end user but keep in mind, SDD was developed to recommend the repairs.

Alongside diagnostics the service functions allows vehicle and module programming and vehicle customisation.

A selection of what can be done with SDD:

• Fault Code Reading / Resetting analysing for repairs
• Service Lights
• Read / Clear / Reset Air bag Light codes
• Read / Clear / Reset ABS Light codes
• Programming Modules
• Clearing adaptions
• Programming personalisation like ride height or folding wing mirrors.
• DPF Regeneration
• Activate pumps for brake bleeding
• Adjust vehicle heights
• Program new DSC units

• Making SDD effective when selecting Vehicle symptoms for your Jaguar & Land Rover

  SDD is designed to link DTCs and provide recommendations based on Customer Facing and/or the most significant symptoms. Do not try to short-cut or refine the customer’s reported symptoms based on expected failures. If the primary or most obvious Customer Facing symptom is an MIL or message center warning, those symptoms MUST be included in your symptom selection inputs using SDD. While it might seem logical when selecting ‘Air Suspension is inoperative’ that there is really no need to select the symptom ‘Message center warning’, it is important to do so. Otherwise SDD may exclude DTCs or recommendations that relate to failures known to trigger a warning message or MIL. Be sure to select any additional symptoms observed during a road test in addition to the most obvious symptoms and customer reported info. Altering the selected symptoms adjusts the filtering of the DTCs. Selecting fewer symptoms makes the filter ‘coarser’ while selecting more symptoms makes the filter ‘finer’.

  • If very few or no DTCs and recommendations are

  listed, try restricting your symptom selections to Level 3 in the symptom tree.

  • If too many DTCs or recommendations are listed, try

  selecting symptoms to Level 4 or 5, using care not to select an inaccurate symptom.

  • To be sure that you are only working with your

  intended symptom list: open the ‘Selected Symptoms’ drop down box at the upper right portion of the Symptom Selection tab to review all currently selected symptoms. Avoiding Common SDD Symptom Selection Errors Powertrain > Engine system > Starting system > Start-stop system: Note that the Start-Stop System is a fuel conserving technology used on diesel vehicles sold in other markets. This is not associated with the ‘Start Button’ used to actuate the ignition on Smart Key equipped vehicles. Warning Lamps, Status Lamps, and Message Center Use care when entering symptoms related to customer complaints of MIL lights and warnings. When a light and a message are reported or observed, both of these symptoms must be included. When viewing the symptom categories within the Electrical > Instrument Cluster section, there are 3 classes of ‘driver information’ symptoms:

  • Warning Lamps (red)
  • Warning Messages (in Message Center)
  • Status Lamps (yellow)

  While it is easy to distinguish between a Warning Message and a Warning Lamp that is currently active, if the problem is intermittent, the service writer must determine through careful questioning of the customer if a warning lamp, warning message, or both were displayed. Also, not every MIL is considered a Warning Lamp since some indicators on the instrument cluster are used to indicate the status of a system. Examples of Status Lamps include the Passenger Seat Occupancy Status Lamp and the TPMS Status Lamp. Using the Passenger Seat Occupancy Status Lamp as an example: this light is only used to indicate the status of the passenger seat. When lit, it simply indicates that the SRS system has determined that based on the current inputs, the passenger restraints will not be deployed. It does not mean the system has detected a failure that requires a driver warning. For this reason, the lamp is classified as a Status Lamp. Similarly, the amber TPMS indicator is used to inform the driver that the tire pressure requires attention. While this light may remain lit when a system malfunction exists, it is considered a Status Lamp since its primary function is to inform the driver of the tire pressure status. Recommendation: When selecting SDD symptoms for lamps that are primarily considered a Status Lamp, but are also known to have a secondary function as a Warning Lamp, be sure to select the symptoms under both categories in the symptom selection map.

  New Diagnostic Process

  IDS has been updated with the goal of providing a clear diagnostic strategy and tool navigation path to the technician. With Symptom Driven Diagnostics (SDD), the technician is able to begin the diagnostic process by identifying the specific symptoms of a customer concern using Symptom Maps incorporated into the

  SDD software. A diagnostic strategy can then be structured around only the DTCs that are relevant to those symptoms. SDD can also provide links to other service information to support the diagnostic process.

  Symptom Maps

  Symptom Maps are incorporated into the SDD software, and allow the technician to target DTCs and diagnostic routines based on a specific set of symptoms. Symptom Maps are organized by major vehicle system as follows:

  • Module Communications Network
  • Chassis
  • Powertrain
  • Electrical
  • Body

  Maps are then further structured by System and Sub-System details to provide lists of possible symptoms at 2 levels.

  Symptom Maps are used by SDD in conjunction with DTCs. In order to ensure the best possible recommenda- tions to achieve FRFT repairs,

  the technician must input ALL vehicle symptoms that match the customer concern.

  The Integrated Diagnostic System (IDS) core architecture dates from 1999 and incorporates elements going back as far as 1995. In the meantime,

  vehicle technology has become more complex and the number of vehicle variants has increased.

  Current vehicle systems support up to 4,000 different Diagnostic Trouble Codes (DTCs), which increases the complexity of diagnostics.

  The technician now needs to diagnose systems, not merely individual components.

  Without a clear strategy for a repair process, a technician faced with up to 40 DTCs at the start of an IDS session can easily lose confidence in the diagnostic tool.

  Feedback data from dealerships shows inconsistent methods of fault diagnosis with under utilization of the IDS capabilities.

  This has resulted in high ‘No Fault Found’ repair rates, difficulty in achieving Fixed Right First Time (FRFT) repairs, and an increase in the time that a customer’s vehicle is off the road.

  Requirements:

  O/S.:  Windows 7 SP1
  Acrobat Reader 10
  Internet Explorer 8 or 9
  Hard Drive: 60 GB of available space

  Conflicts:
  SDD can’t be installed on the same PC with Ford/Mazda IDS and other programs that derived from Ford IDS.