7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFault Code P1691
Leading reported evidence
Reconnect unit
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 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 · Original poster
Reconnected unit to harness and got the same eror.
Leading evidence: 'Reconnect unit' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check continuity along 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 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
Only thing you can do is trace the wire back and check continuity along the way.
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
Did they change your DME when you added the supercharger?
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.
7 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: 20261026T165820Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I keep getting this fault code (every time I drive the car). I reset it and the next time I start the car...it comes right back. If anyone has any ideas, I would appreciate guidance.
Thanks
P1691 says there is no connection between the MIL and DME. Only thing you can do is trace the wire back and check continuity along the way.
Did they change your DME when you added the supercharger? Or perhaps pinch a wire near the DME?
They soldered in a new chip Proprietary GIAC tuned Motronic Control Unit. I get the Check Engine Light when this error occurs. It started out intermitently when I got the car back and now is on every day. Starts as a pending DTC and then goes to Check Engine Light. I have been having various fault codes such as P1123 and P1125 and P1539. Now I simply get this fault code and none of the others. All systems seem GO, Fuel Trim normal...Oxygen Sensors rapidly responding, MAF fine. A little rough idle (hunting) but nothing serious. I have to carry my laptop with me everyday just to turn off the light.
When I say other systems are normal,,,this is based on EVO telling me they are normal. MAF reads around 6.50 at idle (up or down 20) Long Term fuel trim is 85 on both banks under heavy load, The only question in my opinion is the Short Term Fuel Trim. Bank 2 ALWAYS is more positive than Bank 1. i.e. if bank 1 reads -1.5, bank 2 will read about +1.5. If Bank 1 reads -15 then Bank 2 reads around -13. Bank 2 is always about 3 percentage points more positive than Bank1. The only exception to this is when I let up on the gas and both readings go to 0.
Took a look at the connection and wires of the control unit to see if anything was obvious. Wires seemed undisturbed. Reconnected unit to harness and got the same eror. For fun...I banged on the alluminum cover with my knuckles and restarted the car. NO ERROR. Now...although I have been getting the P1691 EVERYTIMES I start the car and I am not getting them now doesn't isolate the problem yet. I'll drive it awhile more before comming to that conclsion.
I suppose if the tapping did in fact fix the problem...there must be a bad solder joint or other connection in the unit.
Well...that didn't last long. All the faults showed up again.
Pending DTC's:
p1539
p1123
p1125
p1691
I wonder is the p1691 is the cause off all the others. Bank 1 Sensor out of range and Camshaft Adjustment Bank 2 Short? I'll probably have to send the Control Unit back to EVO and have them fix it.
This is a source reference. Confirm exact model applicability in the original material.
