Audi Q7 4.2TDI błąd
Audi Q7 4.2TDI błąd
Jest problem a zarazem potrzeba w jego rozwiązaniu bo samochód nie jeździ od dobrych kilku miesięcy. Czy jest ktoś w stanie ogarnąć co to za błąd brzmi on mniej więcej tak: ingerencja momentu obrotowego skrzyni biegów a jego kod to P2545 samochód przechodzi w tryb awaryjny i nara cześć pa nie jade dalej
Sprawdzanie szczelności układu podciśnienia (PW)
może taki?
5593 - Torque Management Request Input Signal A: Implausible
P2545 00 [032] - Open or Short to Ground
Indicator
This code indicates that a torque management request input signal malfunction has been detected in the PCM or one of the other supporting control modules. These control modules may include (but are not limited to) the transmission control module, the body control module, the antilock brake control module, the instrument panel control module, the fuel injection control module, the turbo control module, the anti-theft module, the cruise control module, the traction control module, proximity alert module, and the climate control module.
Code Set Parameters
In the event of a torque management request input signal malfunction, a trouble code will be stored and a service engine soon lamp will be illuminated. Some models require multiple drive cycles (as many as 8) with a failure in order for the service engine soon lamp to be illuminated and others will activate it on the initial failure.
Symptoms
Symptoms may include drivability issues, harsh shifting, decreased fuel economy, the engine may stall or run roughly at idle, poor acceleration, a stored trouble code, and possibly an illuminated service engine soon lamp. If this code is stored, and a service engine soon lamp has not yet been illuminated, the code may be shown as pending.
Common Causes
Unlike most other PCM codes, the most likely cause of this code being stored is a defective driver in the PCM (or other related controllers) or a poor electrical connection. Other causes may include corroded, open, or shorted wiring or connectors in the CAN Bus harness, a loose control module ground strap or broken ground wire, the CAN bus may also be defective.
Common Misdiagnosis
Symptoms and stored codes that are present as a reaction to a communication failure are often misdiagnosed and repaired as the cause of the problem. Obviously, this leads to an unsuccessful repair. Engine misfire codes, lean exhaust codes, fuel injector codes, and virtually any other drivability or transmission code that is accompanied by a controller communication code can potentially be a pitfall for misdiagnosis. Follow the rule that says to diagnose codes in the order in which they are stored and you will improve you chances for a successful diagnosis. Utilize freeze frame data to help you determine which codes were stored first.
Diagnosis
In an effort to improve automatic transmission shift feel and promote component longevity, the transmission control module may request that the PCM reduce effective engine RPM and torque during certain shifting conditions
When the PCM receives a request of this type, it responds by retarding ignition timing and inputting a signal to the transmission control module to indicate that the task has been successfully accomplished
If the PCM is unsuccessful in reducing the degree of torque produced by the engine, a failure message is input to the transmission control module, a code is stored, and a malfunction indicator lamp is illuminated. Torque reduction requests and failure messages are conveyed between controllers via the controller area network or CAN
CAN represents a communication bus that allows multiple microcontrollers to communicate with one another without the need for a host computer
It is a message based protocol originally designed for automotive use
The CAN bus network is actually a complex conglomeration of wiring harnesses and connectors used as a pipeline of information shared between two or more automotive control modules
These controllers control virtually every electrical function of the vehicle, with the PCM being the primary controller
Control modules receive input data from various sensors and emit output signals to system components and other control modules
For example: The PCM receives an input signal from the vehicle speed sensor
This signal is systematically forwarded to affected control modules that utilize the data to accomplish various other tasks
The cruise control module uses the data for speed control purposes, the traction control system uses the data to regulate vehicle traction control strategy, and the anti lock brake controller compares vehicle speed from the PCM with data inputs from individual wheel speed sensors to operate the anti lock braking system. Several tools will be instrumental in attempting to successfully diagnose this code
A suitable OBD-II scanner (or code reader) and a digital volt/ohmmeter will be most helpful in trying to perform a successful diagnosis
Begin with a visual inspection of all wiring and connectors
Repair or replace damaged, disconnected, shorted, or corroded wiring, connectors, and components as necessary
Always retest the system after repairs are completed to ensure success. If all system wiring, connectors, and components (Including fuses) appear to be in normal working order, connect the scanner (or code reader) to the diagnostic connector and record all stored codes and freeze frame data
This information can be extremely helpful in diagnosing intermittent conditions that may have contributed to this code being stored
Continue by clearing the code and operating the vehicle to see if it returns
This will help to determine whether or not the malfunction is intermittent
After the codes are cleared, test drive the vehicle to see if the code returns
If the code fails to immediately return, you may have an intermittent condition
Intermittent conditions can prove to be quite a challenge to diagnose and in extreme cases may have to be allowed to worsen before a correct diagnosis can even be attempted
Unlike other diagnostic codes, this type of code can sometimes be best left to a professional simply because of the bulk of circuitry involved
An experienced technician with a specialized scanner (Autohex or Tech II) may be able to determine the general area of the malfunction much more rapidly and easily than someone using a code reader and a digital volt ohmmeter
Disconnecting and testing every single pin of the CAN bus could prove to be extremely time and cost prohibitive
Additionally, some type of memory saving device must be installed, lest the PCM and other controllers lose their memory and require reprogramming
A specialized diagnostic CAN scanner will show pin values and control module operation without risking a meltdown
It can accurately diagnose computer and circuitry problems by monitoring vehicle operation while the vehicle is being operated
To diagnose this type of code using a digital volt ohmmeter would entail probing thousands of circuits, independently
One misplaced probe could destroy expensive control modules and require that the vehicle be totally reprogrammed. At the most, you may attempt to perform a continuity test after all control modules are disconnected, and this could literally require 40-hours or more, depending upon the vehicle
Some applications are equipped with up to 18 separate control modules. If you choose to tackle this monumental task, begin with a careful visual inspection of all system circuitry, connectors, and fuses
Control module ground circuits should be tested for continuity with battery ground
These types of codes are frequently caused by defective or disconnected system grounds
An auxiliary ground cable can be helpful in diagnosing system ground discrepancies
Engine and transmission ground cables, straps, and wires are sometimes left dangling after repairs are performed
Look for loose or corroded electrical connectors that may increase circuit resistance and cause these types of codes to be stored. Obtain a CAN bus system wiring diagram and/or pin out value chart, then use the digital volt ohmmeter to test continuity between individual controller connectors
Compare your findings with the manufacturer's referenced values and repair open or shorted circuits as required
It is often much more frugal to replace defective wiring rather than attempting to remove it from the complex web of wiring harnesses.
5593 - Torque Management Request Input Signal A: Implausible
P2545 00 [032] - Open or Short to Ground
Indicator
This code indicates that a torque management request input signal malfunction has been detected in the PCM or one of the other supporting control modules. These control modules may include (but are not limited to) the transmission control module, the body control module, the antilock brake control module, the instrument panel control module, the fuel injection control module, the turbo control module, the anti-theft module, the cruise control module, the traction control module, proximity alert module, and the climate control module.
Code Set Parameters
In the event of a torque management request input signal malfunction, a trouble code will be stored and a service engine soon lamp will be illuminated. Some models require multiple drive cycles (as many as 8) with a failure in order for the service engine soon lamp to be illuminated and others will activate it on the initial failure.
Symptoms
Symptoms may include drivability issues, harsh shifting, decreased fuel economy, the engine may stall or run roughly at idle, poor acceleration, a stored trouble code, and possibly an illuminated service engine soon lamp. If this code is stored, and a service engine soon lamp has not yet been illuminated, the code may be shown as pending.
Common Causes
Unlike most other PCM codes, the most likely cause of this code being stored is a defective driver in the PCM (or other related controllers) or a poor electrical connection. Other causes may include corroded, open, or shorted wiring or connectors in the CAN Bus harness, a loose control module ground strap or broken ground wire, the CAN bus may also be defective.
Common Misdiagnosis
Symptoms and stored codes that are present as a reaction to a communication failure are often misdiagnosed and repaired as the cause of the problem. Obviously, this leads to an unsuccessful repair. Engine misfire codes, lean exhaust codes, fuel injector codes, and virtually any other drivability or transmission code that is accompanied by a controller communication code can potentially be a pitfall for misdiagnosis. Follow the rule that says to diagnose codes in the order in which they are stored and you will improve you chances for a successful diagnosis. Utilize freeze frame data to help you determine which codes were stored first.
Diagnosis
In an effort to improve automatic transmission shift feel and promote component longevity, the transmission control module may request that the PCM reduce effective engine RPM and torque during certain shifting conditions
When the PCM receives a request of this type, it responds by retarding ignition timing and inputting a signal to the transmission control module to indicate that the task has been successfully accomplished
If the PCM is unsuccessful in reducing the degree of torque produced by the engine, a failure message is input to the transmission control module, a code is stored, and a malfunction indicator lamp is illuminated. Torque reduction requests and failure messages are conveyed between controllers via the controller area network or CAN
CAN represents a communication bus that allows multiple microcontrollers to communicate with one another without the need for a host computer
It is a message based protocol originally designed for automotive use
The CAN bus network is actually a complex conglomeration of wiring harnesses and connectors used as a pipeline of information shared between two or more automotive control modules
These controllers control virtually every electrical function of the vehicle, with the PCM being the primary controller
Control modules receive input data from various sensors and emit output signals to system components and other control modules
For example: The PCM receives an input signal from the vehicle speed sensor
This signal is systematically forwarded to affected control modules that utilize the data to accomplish various other tasks
The cruise control module uses the data for speed control purposes, the traction control system uses the data to regulate vehicle traction control strategy, and the anti lock brake controller compares vehicle speed from the PCM with data inputs from individual wheel speed sensors to operate the anti lock braking system. Several tools will be instrumental in attempting to successfully diagnose this code
A suitable OBD-II scanner (or code reader) and a digital volt/ohmmeter will be most helpful in trying to perform a successful diagnosis
Begin with a visual inspection of all wiring and connectors
Repair or replace damaged, disconnected, shorted, or corroded wiring, connectors, and components as necessary
Always retest the system after repairs are completed to ensure success. If all system wiring, connectors, and components (Including fuses) appear to be in normal working order, connect the scanner (or code reader) to the diagnostic connector and record all stored codes and freeze frame data
This information can be extremely helpful in diagnosing intermittent conditions that may have contributed to this code being stored
Continue by clearing the code and operating the vehicle to see if it returns
This will help to determine whether or not the malfunction is intermittent
After the codes are cleared, test drive the vehicle to see if the code returns
If the code fails to immediately return, you may have an intermittent condition
Intermittent conditions can prove to be quite a challenge to diagnose and in extreme cases may have to be allowed to worsen before a correct diagnosis can even be attempted
Unlike other diagnostic codes, this type of code can sometimes be best left to a professional simply because of the bulk of circuitry involved
An experienced technician with a specialized scanner (Autohex or Tech II) may be able to determine the general area of the malfunction much more rapidly and easily than someone using a code reader and a digital volt ohmmeter
Disconnecting and testing every single pin of the CAN bus could prove to be extremely time and cost prohibitive
Additionally, some type of memory saving device must be installed, lest the PCM and other controllers lose their memory and require reprogramming
A specialized diagnostic CAN scanner will show pin values and control module operation without risking a meltdown
It can accurately diagnose computer and circuitry problems by monitoring vehicle operation while the vehicle is being operated
To diagnose this type of code using a digital volt ohmmeter would entail probing thousands of circuits, independently
One misplaced probe could destroy expensive control modules and require that the vehicle be totally reprogrammed. At the most, you may attempt to perform a continuity test after all control modules are disconnected, and this could literally require 40-hours or more, depending upon the vehicle
Some applications are equipped with up to 18 separate control modules. If you choose to tackle this monumental task, begin with a careful visual inspection of all system circuitry, connectors, and fuses
Control module ground circuits should be tested for continuity with battery ground
These types of codes are frequently caused by defective or disconnected system grounds
An auxiliary ground cable can be helpful in diagnosing system ground discrepancies
Engine and transmission ground cables, straps, and wires are sometimes left dangling after repairs are performed
Look for loose or corroded electrical connectors that may increase circuit resistance and cause these types of codes to be stored. Obtain a CAN bus system wiring diagram and/or pin out value chart, then use the digital volt ohmmeter to test continuity between individual controller connectors
Compare your findings with the manufacturer's referenced values and repair open or shorted circuits as required
It is often much more frugal to replace defective wiring rather than attempting to remove it from the complex web of wiring harnesses.
Tutaj masz co trzeba sprawdzić. Wcale nie dotyczy to silnika
These control modules may include (but are not limited to) the transmission control module, the body control module, the antilock brake control module, the instrument panel control module, the fuel injection control module, the turbo control module, the anti-theft module, the cruise control module, the traction control module, proximity alert module, and the climate control module.
These control modules may include (but are not limited to) the transmission control module, the body control module, the antilock brake control module, the instrument panel control module, the fuel injection control module, the turbo control module, the anti-theft module, the cruise control module, the traction control module, proximity alert module, and the climate control module.
sprawdz ten czujnik walu, przynajmniej wypnij go i wepnij ponownie... w ogole bym powypinal wszystkie mozliwe wtyczki, przeczyscil jak sie da i wpial znowu, wywalil blad i probowal odpalic...
widzialem na ruskich forach, ze czasami ludzie maja ten blad pare razy w roku i nic sie nie jebie jakos konkretnie...
widzialem na ruskich forach, ze czasami ludzie maja ten blad pare razy w roku i nic sie nie jebie jakos konkretnie...