Source reference 10167434
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
PIP5601A ・ information ・ for GM vehicles in general
Applies to
All models, model years 2000 - 2020.
the passage
All All 2000 - 2020 All All All All
Fault
Customers complain of 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
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 file of the concern.
Review the Pico file and use it to help determine the root cause or component.
the passage
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 vibration frequency observed.
the passage
Repair the vehicle using Pico information along with any published information relevant to the vibration frequency observed.
Caution
Attempting a vibration repair without knowing the frequency is compared to repairing a check engine light without knowing the stored DTC.
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.
12-03-10-001B is a generic document on the possibility of tire to rim orientation and of 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 blower motor, brake pulsation or shudder on turns do not require a Pico file.
the passage
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 Oscilloscope Diagnostic Kitを使用して、車両を効果的に診断する必要があります。整備士はPico Oscilloscopeを使用しながら車両を走行させ、データを記録する必要があります。データが記録された後、関心事の根本原因を決定するためにそれを確認する必要があります。修理の試みが関心事をより良くしたが排除されなかった、またはまったく影響がなかった場合、General Motors Technical Assistance Centerから支援を要請している場合は、別のPicoファイルを記録してコンピューターに保存してください。新しいPico Oscilloscopeデータが保存された後、データをGeneral Motors Technical Assistance Centerにメール送信し、件名行に「Vibration」「Business Associate Code」およびVehicle Identification Numberの最後の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
- 10167434
- Received by source
- 2019-11-12
- Incident date
- Unknown
Open original text and sourceOpen the provider's page (external)
