Concerns About DTC Processing Using SDD (SSM48757)

CONCERNS ABOUT DTC PROCESSING USING SDD

TECHNICAL SERVICE BULLETIN

ISSUE

Users report that SDD is unreliable at reading/clearing some DTC's from the vehicle after repairs are completed, and in some cases, they report codes are removed from the DTC "event" screens, while codes still exist within the vehicle.

Users report this can be confirmed using IDS classic or alternate diagnostic tools.

CAUSE

While there is no evidence that SDD is actually failing to clear/display codes under normal circumstances, temporary communications issues may be occurring undetected when users are executing the SDD functions to Clear and Re-Read DTC's.

SDD is not empowered with a mechanism to alert the user when a partial communications failure occurs during these processes, therefore it is possible the DTC's may not appear to clear or re-display properly.

Content

SOLUTION

Until further notice, SDD users are hereby advised to modify their DTC re-read process as follows.

1. IMPORTANT:  Never use the "Re-Read Diagnostic Trouble Codes" option on the Recommendations Tab.
2. When it is required to re-read DTC's from the vehicle, SDD users must always use the Data Collect process that is provided on the Network Summary display found on the "Session" tab.
3. After a successful Data Collect process has ensured all vehicle systems have responded, select the "events" tabs to review current DTC's

For details on where to manually execute a Data Collect process, please refer to the attached SDD screen image. Users that find SDD is unable to correctly read or clear DTC's even when implementing this protocol are urged to contact the JLR Technical HelpLine for assistance, and submit an EPQR with session files collected using the IDS File Import Tool v5.1