11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHE-gas troubleshooting
Reported or suspected cause
on the ground or the wiring/connections
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
So, that means that your issue is on the Ground or the wiring/connections....
Leading evidence: 'on the ground or the wiring/connections' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'on the ground or the wiring/connections' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Replace when pressing the pedal all the way' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Used pedals r not that expensive ir hard to swap out.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Actuated the pedal a few times and the pedal value drops to 0% and does't change when pressing the pedal all the way to the floor.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
All this data can help shed some light on the failure before actual testing of the components begins..
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I was just going by the codes only, and giving you a place to start testing as the usual Fault Tree Diagnostic for this ( or any Sensor ) is the to Test the Sensor, If OK then test the wiring, if OK then condemn the DME ..
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I was just going by the codes only, and giving you a place to start testing as the usual Fault Tree Diagnostic for this ( or any Sensor ) is the to Test the Sensor, If OK then test the wiring, if OK then condemn the DME ..
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I was just going by the codes only, and giving you a place to start testing as the usual Fault Tree Diagnostic for this ( or any Sensor ) is the to Test the Sensor, If OK then test the wiring, if OK then condemn the DME ..
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
11 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T031046Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
2001 Carrera, when I start the car it immediately goes full throttle. Hooked up a scan tool and got codes p1219, p1577, and p1578. The "Pedal Value" is reading 38.78% with no pressure on the pedal. Actuated the pedal a few times and the pedal value drops to 0% and does't change when pressing the pedal all the way to the floor. However, the voltage on Pedal encoder potentiometer 1 and 2 do change.
Does this pretty much diagnose a bad gas pedal sensor?
No Throttle
Full Throttle:
Have u looked to see if the electrical connection is in good shape? Used pedals r not that expensive ir hard to swap out. Usually u dont see failures in the padal but anything is possible.
yes, connection is fine. Are you familiar with how this works? The actual gas pedal actuates, by steel cable, a mechanism that converts it to an electrical signal, so the actual gas pedal doesn�t have anything in it to go bad.
Those codes indicate a problem on BOTH Potentiometer 1 and Potentiometer 2 ..... But BOTH Pots will not have failed at the same time, that is theoretically almost impossible. So, that means that your issue is on the Ground or the wiring/connections....
If the wiring and connections all test out OK then the DME is at fault...
The pedal Pot 1 and Pot 2 do not output the same voltage value, Pot 2 is HALF the voltage of Pot 1.. this is on purpose and each is used to confirm the accuracy of the other using a pre-determined Map. When one value strays from the predicted Map it sets a fault code goes into limp mode with 30% Max throttle available...
I was just going by the codes only, and giving you a place to start testing as the usual Fault Tree Diagnostic for this ( or any Sensor ) is the to Test the Sensor, If OK then test the wiring, if OK then condemn the DME ..
IF you want more fuel for thought there is " extended fault memory" that is available in PIWIS ( not sure if lesser tools can show this ) .. that has a plethora of info like for each code there is a sub-category that can be Signal Implausible ( plaus) or above limit value ( max) or below limit value ( min ) along with other info at the time of the fault codes, like speed, hours, temps, ect , and also available in "freeze frame data) ...
All this data can help shed some light on the failure before actual testing of the components begins..
Also you can just throw some parts at it starting with Pedal assembly, then wiring harness, then DME .. ( not my way of fixing something but some people find success in this ...lol )
This is a source reference. Confirm exact model applicability in the original material.
