Porsche 911 UK Enthusiasts Online Community Discussion Forum GB

Welcome to the @Porsche911UK website. Register a free account today to become a member! Sign up is quick and easy, then you can view, participate in topics and posts across the site that covers all things Porsche.

Already registered and looking to recovery your account, select 'login in' and then the 'forget your password' option.

PIWIS hell - Mileage increasing but no speedometer!

geordiepingu

New member
Joined
3 Mar 2024
Messages
12
Hi all

On this episode of f*** around and find out...

The story goes that a particular coding attempt failed (errored out) and I've been fighting the good fight since, when trying to re-code some features for PCCM+ in development mode. I've since deleted all codes, reprogrammed the gateway for good measure, re-coded from scratch by comparing with an old vehicle analysis log in PIWIS and now have the following REALLY bizarre issue.

If I turn the steering very fast or roll the car backwards or forwards, my odometer begins to clock up extremely rapidly. The speedometer - both analogue and digital stay at 0mph or 0kmh. PSM detects movement in the wheel speed sensors and reports what seems to be reasonably accurate.

Once the odometer starts, it will continue clocking up while the ignition is on. If I turn the key off then on, it continues clocking. To stop, I have to reset the unit by pulling the fuse (F1 Row B if memory serves - or maybe C, it's a 15 ampere) or disconnect the battery.

I've spent the past day reducing codes down to a known error with my door handle and still scratching my head where I am going wrong with this. For a while I thought the steering control module was knackered until I got rid of the codes - perhaps it still is - all sorts of CAN codes for being unable to read drive and comfort of the module. Seems to have disappeared however and all functions on the wheel and stalks are working correctly.

The tachometer, fuel gauge, temps and pressures work fine, as do the lights and display when tested.

Has anybody got some advice on where to start?

Many thanks
 

Attachments

I've never come across that before
must be a wiring fault

just bad timing with the PCCM+ changes
 
I think it's likelier I've bricked a module if I'm perfectly honest
 
I think you'll need a great specialist with PIWIS (and decent hourly rate).
Chances of an OPC fixing it at less than the cost of a new 992 v slim.

Did you take an image of the original settings for gateway and all control modules?

From memory that's Iain's (DeMort) top tip for coding.
 
I have some new findings, in that it looks like there's speed being picked up by the PSM CU (control unit), but not being distributed over CANBUS. When the car rolls, not even the convertible top or the climate control gets a speed signal. Presumably this lack of signal when the front CU and PSM CU detect movement is causing chaos to a few other CUs.

I've isolated out the front CU, DME, rear CU, park assistant, steering control modules to find I still get the mileage issue. Naturally taking the fuse out for the instrument cluster and then subsequently replacing it makes it stop, until I roll the car again (get any wheel speed in any of the inputs). I did also try a gateway from another vehicle without coding or programming it to see if the issue can be replicated - and unfortunately it can. I did code the unit with a new VCI - not trusting my old one given what's gone on - and unfortunately same issue.

I saw a diagram somewhere that described how the PSM deduces wheel speed and sends it on to the bus - it may have been from a chap diagnosing his tiptronic unit on rennlist or planet 9, but hell if I can find it again. It would be useful to double check with an oscilloscope and my CAN bus dumping tools to make sure the PSM CU is not sending out a signal before I just try and replace it. I did pull the PSM CU and of course it meant I had no issues with the cluster, but then of course, nothing was getting vehicle speed!

I should also add that I've had my scope on and CANBUS dumper to see if there's any dodgy signals or shorts to ground in the CAN Drive circuit (albeit with the PSM module unplugged...) and without further specification or workshop documentation, that doesn't show any obvious signs of anything wrong - no packet loss/malformed packets or shorts to ground pulling the signal down.

TL;DR: No more fault codes, my educated guess is I've had bad timing and done something in on the PSM CU. Would appreciate any documents (rather than just PIWIS wiring diagrams) that could help me with my diagnosis. Many thanks
 

Attachments

  • Screenshot 2024-07-28 182507.png
    Screenshot 2024-07-28 182507.png
    58.7 KB · Views: 10
Had a bit of time to play this evening and got the rear wheels in the air on jack stands. I managed to simulate the beginnings of a drive cycle and debug the CANBUS drive circuit to see what was going on. Looks like the above is a red herring as the convertible CU gets the vehicle speed from an analog source anyway. Everything is getting an accurate vehicle speed readout on CANBUS upon inspection.

Drive cycle managed to narrow down a code when I induced a "PSM failure" by making it think the two front-wheel speed sensors were faulty by being stationary. C202 from the instrument cluster - Display signal implausible from PSM... No errors from the gateway.

I did manage to try a known good PSM CU by plugging that in without plumbing it in with the same result.

Fault finding not showing issues for a C202 and wiring diagram suggests that gateway must transform and re-publish this to the instrument cluster.
Screenshot 2024-08-01 195104-1.png

So my next steps will be to debug and get the scope out on the CAN display lines to the instrument cluster while I've got vehicle speed and see what happens, and double check the gateway has the PSM coded in etc. If there's nothing obvious then I'll be exploring the possibility of grabbing another instrument cluster to test

Any insights to this point appreciated
 
Hi everyone

Hopefully this thread helps someone. I replaced my instrument cluster and coded it to the car, it is working a treat now. The mileage was corrected by a VDO specialist to match what the rest of the car is, so I'm very happy.

Still perplexed as to what got corrupted in the original cluster, I am inclined to send it away to be repaired so I can have a spare sat on the shelf, or sell it in the future. No matter how many times I went through the development menu or the managed instrument cluster coding, I could not resolve it.

Tl;dr, problem solved for not much money.

For reference to the CAN debuggers out there, I used the following resource to determine the codes to look for (thank you whoever debugged the instrument cluster before).

GitHub - superman22x/Porsche-997-and-987-Gauge-Cluster-Operator: This code is designed to be used with the Macchina M2 (Arduino Due based). It uses OBD PID requests to run the gauge cluster in the Porsche. Tested with GM 6.2L LT1 swapped Porche 997.
For reference - wheels speeds are at 0x24A.
 

Trending content

Forum statistics

Threads
127,189
Messages
1,478,704
Members
52,890
Latest member
e28m5
Back
Top