Source reference 10113416
Manufacturer communication — 2006 GMC YUKON DENALI XL
Relation to the target vehicle
- The source's vehicle field includes the trim.
- Model year
- Match 2006 — Source vehicle field
- Model
- Match YUKON DENALI XL — Source vehicle field
- Trim
- Match Denali — Source vehicle field
What the manufacturer’s document says
PIP5338A ・ information ・ for GM vehicles in general
Applies to
The model table lists all brands and models, model years 2000 - 2017.
the passage
Model Years: VIN: Engine: Transmissions: from to All All 2000 - 2017 All All All All
Fault
For effective vibration diagnosis the Pico Oscilloscope Diagnostic Kit with NVH (P/N 733-CH-51450) was sent to all US and Canadian dealers.
the passage
To be effective in diagnosis the Pico Oscilloscope Diagnostic Kit with NVH (P/N 733-CH-51450) was sent to all US and Canadian dealers.
Finding the cause
Steps to confirm (in the document’s order)
Drive the vehicle to verify the condition and record a Pico data file of the concern, then save the file to the computer.
the passage
1: Drive the vehicle to verify condition AND record a Pico data file of the concern. Save the file to computer for possible use later.
Review the Pico file and use it to help determine the root cause or the component.
the passage
2: Review that Pico file and use that information to assist in determining root cause or component.
Correction
Repair
Repair the vehicle using the Pico information together with any published information relevant to the observed vibration frequency.
the passage
3: Repair the vehicle using Pico information along with any published information relevant to the vibration frequency observed.
Caution
Just as a CEL is not repaired without knowing the stored DTC, a vibration cannot be repaired effectively without knowing its frequency.
the passage
We wouldn't attempt to repair the CEL without knowing the DTC stored, same can be said for vibrations. Without knowing the frequency we are just spinning our wheels in attempting to repair.
The Pico file requirement is for vehicle level vibration complaints; component level vibrations such as blower motor, brake pulsation or shudder on turns do not require a Pico file.
the passage
NOTE: This is for vehicle level vibration complaints, component level vibrations ie: blower motor, brake pulsation or shudder on turns type concerns do not require a Pico file.
Compiled by reading the full text of the document; each point stands on the passage shown. Check the document itself, linked below, before working on a vehicle.
Stated content
Communication summary
本予備情報通知は、診断および修理が最も難しい不具合の一つである振動に関する苦情について、技術者に情報を提供します。技術者は、車両を効果的に診断するためにPico示波器診断キットを使用する必要があります。技術者はPico示波器を使用しながら車両を運転し、データを記録してください。データが記録されたら、不具合の根本原因を判断するため見直す必要があります。修理を試みた結果、不具合がより良くなったが完全には解決しなかった場合、または全く効果がなかった場合、およびGeneral Motors技術援助センターからの援助を要求している場合は、別のPicoファイルを記録してコンピューターに保存してください。新しいPico示波器データが保存された後、そのデータをGeneral Motors技術援助センターにメール送信してください。件名行に「Vibration」「Business Associate Code」および車両識別番号の末尾8桁を含めてください。 Machine translation (unreviewed)
This Preliminary Information communication provides information to the technician about vibration complaints that are one of the most challenging complaints to accurately diagnose and repair. Technician will need to use Pico Oscilloscope Diagnostic Kit to effectively diagnosis vehicles. Technician should drive the vehicle will using the Pico Oscilloscope to record data. After the data is recorded it should be reviewed to determine the root cause of the concern. If a repair attempt made the concern better but not eliminated or had no affect at all, and are requesting assistance from General Motors Technical Assistance Center record another Pico file and save it to the computer. After the new Pico Oscilloscope data has been saved email the data to General Motors Technical Assistance Center in the subject line include “Vibration” “Business Associate Code” and the last 8 of the Vehicle Identification Number.
Go to this passage in the original
Source
- Source
- NHTSA Manufacturer Communications
- Source reference
- 10113416
- Received by source
- 2017-08-15
- Incident date
- Unknown
Open original text and sourceOpen the provider's page (external)
