16 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSpeed sender voltage
Leading reported evidence
Check on a constant speed drive
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
Figured I had a wonky wheel speed sender so pulled out the ol PIWIS and checked on a constant speed drive.
Leading evidence: 'Check on a constant speed drive' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust "tacho" (speedometer) curve' (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 · Original poster
I completely disconnected the clutch and brake switches to take them out of play but realized they don�t have anything to do with it.
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
This came out of the blue, and has been tested/confirmed on both of my PIWIS systems.
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.
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
(E-Mode) to adjust the "Tacho" (speedometer) curve.
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.
16 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: 20261027T064914Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Here�s a fun one. My speedometer said I was doing 25 mph in my driveway. No way that was true. At all. Stopped, put in reverse and the speedometer immediately went to 6 mph as soon as I started moving. Same thing going forward.
Figured I had a wonky wheel speed sender so pulled out the ol PIWIS and checked on a constant speed drive. Wheel speed sensors are all close and match my phone gps speed but my speedometer is reading crazy high.
I completely disconnected the clutch and brake switches to take them out of play but realized they don�t have anything to do with it.
Is the speed sender monitoring voltage the output from the ABS module that the instrument cluster turns into the speedometer speed? Should it read 0 at a stop?
This came out of the blue, and has been tested/confirmed on both of my PIWIS systems.
The ABS tells the instrument cluster the vehicle speed via CAN. On Tiptronics, the TCU sends the speed to the instrument cluster via CAN. Perhaps something wonky in the ABS other than a wheel speed sensor?
Interesting problem. I cut and paste and put this in ChatGPT and this is what it said.....what I find is that ChatGPT can be correct, but many times it is not, even though it acts like it knows everything. It usually good for a test plan or in the case when I have an issue with my computer or phone, I find it's pretty much spot on with its troubleshooting.
Skip to content
Chat history
You said:
I have a 2003 Porsche 911 (996). Here’s a fun one. My speedometer said I was doing 25 mph in my driveway. No way that was true. At all. Stopped, put in reverse and the speedometer immediately went to 6 mph as soon as I started moving. Same thing going forward. Figured I had a wonky wheel speed sender so pulled out the ol PIWIS and checked on a constant speed drive. Wheel speed sensors are all close and match my phone gps speed but my speedometer is reading crazy high. I completely disconnected the clutch and brake switches to take them out of play but realized they don’t have anything to do with it. Is the speed sender monitoring voltage the output from the ABS module that the instrument cluster turns into the speedometer speed? Should it read 0 at a stop? This came out of the blue, and has been tested/confirmed on both of my PIWIS systems.
ChatGPT said:
This
is
a fun one—and you’ve already done the right diagnostics. Short answer:
the ABS system is doing its job; the instrument cluster is lying.
Let’s walk through it cleanly and tie it back to how the 996 actually works.
How vehicle speed works on a 996 (important baseline)
There is no standalone vehicle speed sensor
on a 996.
Vehicle speed is
calculated in the ABS/PSM control unit
using all four wheel speed sensors.
That calculated vehicle speed is sent to:
Instrument cluster (via CAN bus)
DME
Tiptronic (if equipped)
Cruise control logic
So yes:
The speedometer is driven by a CAN message from the ABS module
, not by a direct sensor or voltage signal.
What
should
happen
At a dead stop:
ABS wheel speeds = 0
ABS calculated vehicle speed = 0
Speedometer =
0 mph
There is
no legitimate operating mode
where:
The ABS reports 0 mph
And the cluster displays 6–25 mph
That rules out wheel speed sensors, brake switch, clutch switch, or ABS logic.
Why your PIWIS results are the smoking gun
You confirmed:
All four wheel speed sensors agree
ABS vehicle speed matches GPS
Speedometer is wildly high and non-zero at a stop
That definitively proves:
The error is downstream of the ABS module—inside the instrument cluster.
What is actually failing (very common on 996)
1️⃣ Speedometer stepper motor failure (MOST likely)
The 996 cluster uses
stepper motors
for:
Speedometer
Tachometer
Fuel
Temp
When the speedo stepper fails, it can:
Stick above zero
Drift upward with movement
Never return to zero
Jump when direction changes (forward ↔ reverse)
Your symptoms are textbook:
25 mph sitting still
6 mph as soon as you move
No correlation to actual speed
This happens
suddenly
, exactly as you described.
2️⃣ Cluster internal logic / EEPROM offset (less common)
Possible but rarer:
Corrupted calibration data
CAN interpretation offset
Usually this also causes:
Odometer mismatch
Other gauge weirdness
Faults stored in the cluster
Stepper motors fail
far more often
than EEPROMs.
What it is
not
❌ Wheel speed sensors
❌ ABS module
❌ Brake or clutch switches
❌ Wiring to ABS
❌ CAN bus failure (you’d have multiple systems acting up)
How to confirm 100% before pulling the cluster
Use PIWIS:
In Instrument Cluster → Actual Values
Look for:
Vehicle speed (from CAN)
Compare it to:
ABS vehicle speed
GPS
If PIWIS shows
correct speed
inside the cluster but the needle is wrong →
bad stepper motor, guaranteed
.
You can also:
Run
gauge sweep / actuator test
If the speedo doesn’t return cleanly to zero or overshoots → confirmed.
Fix options (from best to worst)
✅ Best: Replace speedometer stepper motor
Requires cluster removal and disassembly
Motor is inexpensive
Many electronics shops specialize in Porsche clusters
Keeps odometer coding intact
⚠️ Acceptable: Cluster rebuild service
Typical cost: $150–300
They replace all steppers and reflow solder joints
Often lifetime warranty
❌ Worst: Used cluster swap
Odometer mismatch
Immobilizer issues
Coding headaches
Not recommended unless you know exactly what you’re doing
Bottom line
Yes
, the ABS outputs vehicle speed digitally over CAN
Yes
, speed should be
0 mph at a stop
Your ABS system is healthy
Your instrument cluster speedometer stepper motor has failed
If you want, I can:
Walk you through cluster removal (996-specific tips)
Recommend reputable rebuilders
Explain how to bench-test the speedo motor
Help interpret PIWIS cluster live data
This is a classic 996 gremlin—but thankfully a very solvable one.
ChatGPT can make mistakes. Check important info.
Interesting chat GPT answer! And I mostly agree.
I did dig out my old Tiptronic cluster but ran out of time to get it hooked up and test. Hopefully I can report my updated findings soon�
I do have a feeling the cluster is okay and possibly the output from the ABS module is weird. Or somewhere between the two.
Troubleshooting is fun!
Cheers for the suggestions.
Tried my other cluster and it�s reading just as high. I�ve re toggled the speed sensor A input back to tiptronic and then back to manual, doubt that will do anything�.
Looks like more troubleshooting and data logging with PIWIS before I try a new ABS module (just the plastic part).
Assuming no tire size changes can be made on the 996 like newer 911�s?
Still piddling. The 911 is on the lift now, the Panamera is below it, and the e30 is being driven. Everyone knows something is wrong if the e30 is out on the road
I haven't driven it yet with the module unplugged, would the speedo even register if I did that?
The PIWIS II (more stable than my PIWIS III) has come back out to diagnose and will get serious in engineering mode. I have a feeling it's something in the ABS/PSM module or it's coding?
Edited to add some more fancy AI data
On the Porsche 996, the ABS/PSM module is the primary source of vehicle speed data, which it transmits to other modules. If the actual values from your wheel speed sensors (WSS) are correct in the PIWIS live data, the ABS module is processing the signals accurately, but the
Instrument Cluster
is likely misinterpreting the resulting speed signal.
You cannot "recalibrate" the speed output directly within the ABS/PSM module itself to fix a display error; instead, you must recode how the
Instrument Cluster
translates that incoming signal.
1. Correct the Cluster Coding (Standard Mode)
The instrument cluster uses specific "K-numbers" (pulses per kilometer) or tire circumference settings to calculate speed. If these are set for the wrong model (e.g., a Boxster vs. a 911), you will see a significant linear error.
Navigation:
Use PIWIS to enter the
Instrument Cluster
module.
Coding:
Select
Modify Coding
(or Customer-Specific Settings).
Verification:
Ensure the
Tire Size
or
Model Type
(e.g., 911 C2 vs. C4) is set correctly. A 15% error often indicates the cluster thinks the car has much larger tires than those currently fitted.
2. Adjust Speed Mapping (Engineering/Development Mode)
If standard coding is correct but the error persists, you can use PIWIS in
Engineering Mode
(E-Mode) to adjust the "Tacho" (speedometer) curve.
Curve Adjustment:
Navigate to
Instrument Cluster
->
Coding
->
Manual Coding without MCR Rules
.
X/Y Mapping:
Locate the speedometer mapping table (often labeled as "Tacho" or "Speedo"). You will see a table of X (Input Speed) and Y (Displayed Speed) values.
Calibration:
If the speedometer reads 15% high, you can manually lower the Y values to match the X values (e.g., if X is 100, set Y to 100 instead of 115).
3. Hardware Checks
Module Mismatch:
Verify the ABS/PSM module part number is correct for your VIN. Using a module from a different 996 variant (e.g., Turbo vs. Carrera) can lead to signal frequency mismatches.
Cluster Source:
If the cluster was swapped from another car (common in Boxster-to-996 upgrades), it may require a "full write" of the correct 996 software version to synchronize the speed signal correctly.
These technical guides explain how to recode your Porsche 996 instrument cluster using PIWIS to correct speedometer and coolant temperature readings:
Back to messing with this, no resolution yet.
Does the dme have anything to do with the canbus signal calculation that the instrument cluster sees? Or is the speedometer signal directly from this hunk of plastic and metal knows as the ABS module?
I�m seeing conflicting answers.