Manufacturer communication — 2006 GMC YUKON

ReferenceReporter type: ManufacturerEQUIPMENT:OTHER:OWNERS/SERVICE/OTHER MANUAL

Relation to the target vehicle

The source's vehicle field says Yukon; whether it is an XL is not stated.
The trim (Denali) is not stated.

Model year: Match 2006 — Source vehicle field
Model: Unknown YUKON — Source vehicle field
Trim: Unknown

What the manufacturer’s document says

PIP5601B ・ information ・ for GM vehicles in general

Applies to

Applies to all 2000 - 2024 models.
the passage
All All 2000 - 2024 All All All All

Fault

Vehicle vibration under any of various driving conditions.
the passage
Some customers may complain of vehicle vibration under any of various driving conditions.

Finding the cause

Possible causes

Vibration could be caused by many various components and conditions.
the passage
Vibration could be caused by many various components and conditions.

Steps to confirm (in the document’s order)

Drive the vehicle to verify the condition and record a Pico data file of the concern.
the passage
Drive the vehicle to verify condition AND record a Pico data ﬁle of the concern.

Correction

Repair

Repair the vehicle using the Pico information along with any published information relevant to the vibration frequency observed.
the passage
Repair the vehicle using Pico information along with any published information relevant to the vibration frequency observed.

Caution

Just as a check engine light is not repaired without knowing the stored DTC, a vibration should not be repaired 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.
Bulletin 12-03-10-001B is a generic document about tire to rim orientation and the tire slipping on the rim.
the passage
12-03-10-001B is generic just to make dealers aware of the possibility of tire to rim orientation and tire slipping on the rim.
Component level vibrations such as a 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 ﬁle.

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 Oscilloscope Diagnostic Kitを使用する必要があります。技術者はPico Oscilloscope を使用しながら車両を運転してデータを記録すべきです。データが記録された後、懸念の根本原因を特定するために見直されるべきです。修復の試みが懸念をより良くしたが排除されなかった場合、または全く効果がなかった場合、およびGeneral Motors Technical Assistance Centerからの支援を要求している場合は、別のPicoファイルを記録しコンピュータに保存してください。新しいPico Oscilloscope データが保存された後、General Motors Technical Assistance Centerにメール送信し、件名に「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: 10249980
Received by source: 2024-02-12
Incident date: Unknown

Open original text and source Open the provider's page (external)