Piwi diagnostic program for Porche Taykan

[whitex]

Coding changes settings/configuration. Automatic coding codes are based on a bunch of global settings such as country/region code, road rules to use, present hardware, etc.

AFAIK, programming installs software (whatever software PIWIS has cached, typically latest from Porsche if using it online). Not sure whether programming uses global settings to decide anything. I never did any programming myself.

While coding may be worth a try, unless someone swapped in ECU's from some other Taycan into this one, or recoded things incorrectly, or an ECU somehow lost its settings, all the ECUs should be coded to work together. If there is missing communications between ECUs, it's most likely a physical wiring issue, or one of the ECU's failed (e.g. if an ECU was was damaged somehow).

Sponsored

 

[carlos vilarinho]

As we mentioned before, this is where it gets complicated, and you get into debugging computer systems. Different people have different approaches. If it was me personally, I'd start with all the interconnectivity, beginning with the Gateway, as it is the central "switchboard" for all the ECUs talking to each other. I'd investigate all Gateway communications or bus errors and try to resolve them first. If a main connection to the gateway (COMFORT CAN 2) is broken from BCM1, it's likely you will get all warning lights associated with what BCM1 is responsible for, because the status of all these functions cannot be retrieved. If the gateway has multiple COMFORT CAN 2 errors, that would mean it's likely an issue on the Gateway side, if only BCM1 is not responding but other ECUs like Air Conditioning are, then perhaps the issue is on the BCM1 side. Fixing Gateway->BCM connection could fix all BCM1 related issues in one fell swoop.

Below is the best overview diagram of all ECU's I've come across so far - might be helpful to you (sorry, never found a higher res of this picture anywhere on the net). If you got a PPN account, you can browse through all the ECUs and their interconnections, though last I looked it was not always quick or intuitive.

PS> Not sure why you'd need to recode (the car should have had all of its ECUs coded to match in the first place), but you can also recode ECUs to see if anything changes. Not sure you want to reprogram (vs. recode) any ECUs, since your PIWIS likely has old versions of firmwares cached, so you might create mismatches in the system.

As you can see in the photos of the errors, I have more errors connected to BCM 1 than actually connected to the Gateway….(….Fixing the Gateway->BCM connection can fix all the problems related to BCM1 at once….), I ask how and what do you think I can do to fix this connection between the Gateway and the BCM, for example, what will I have to do to start…..?????…. remove all the plastic seats etc… out of the car, dismantle the car inside, remove the Dashboard outside too and check all the connections of all the modules inside the car outside and the electrical cables between them…..???? Or I don't know how I can check with Piwi and if it is possible to find out which modules are working well and which ones have an error and be able to identify the problem and fix the problem and how to fix the problem…

 

[carlos vilarinho]

Lots of good info from Whitex.

You need to decide where to start with either automatic coding or Automatic programming.

I am not clear on what the difference is between them, but you will not harm something if it is already working correctly and go through Automatic coding.

The Gateway appears to me to be the higher issue you are facing here since I think the Gateway is the communications master for all the units, but happy to hear back from others on this point.

So the procedure is to highlight the error you want with a single click and the error will go blue.

Then click on the Coding programme tab and select Automatic coding.

My guess is that this will not work on any of the lower level faults, but as soon as you find the highest level fault that will reprogramme the highest unit that is failing to communicate with the rest of the system, most of the faults you are seeing will disappear.

I would again ask you to post clear screen shots, we are trying to help you, you should do your best to help us help you.

Shug I'll do it this way as soon as I have two minutes, I'll run the program again on the car and capture the screens instead of photos and then post them here, because these photos with the brightness are not easy? I'm very grateful for your help and availability! Yes, I agree with you Shug and with the wither we can start there, do automatic coding starting at the gateway, now that will change something in the module because as whitex said before, my PIWIS doesn't have the updated cached firmwares..., for sure.

(PS> Not sure why you'd need to recode (the car should have had all of its ECUs coded to match in the first place), but you can also recode ECUs to see if anything changes. Not sure you want to reprogram (vs. recode) any ECUs, since your PIWIS likely has old versions of firmwares cached, so you might create mismatches in the system.)

 

[Shug]

I cannot tell you why you'd need to recode the ECU's other than they have somehow become corrupted.

There is no guarantee this will work.

Remember that if you have to change any modules, they will require component protection removing and your PIWIS cannot do this, so for now all you can do is to use the tools at hand.

Obviously there is a lack of understanding on the work done to your car before you purchased it, so there may be a break in a wire or a plug not seated, but at least you have checked all the fuses, so the lack of comms seems to me to be from one of the modules, it might be the PCM.

There is also a routine on the dashboard that will allow you to reset the PCM, I think It is on YouTube, but that is another easy thing to do, you just have to press a couple of buttons on the centre of the dashboard.

 

[carlos vilarinho]

Coding changes settings/configuration. Automatic coding codes are based on a bunch of global settings such as country/region code, road rules to use, present hardware, etc.

AFAIK, programming installs software (whatever software PIWIS has cached, typically latest from Porsche if using it online). Not sure whether programming uses global settings to decide anything. I never did any programming myself.

While coding may be worth a try, unless someone swapped in ECU's from some other Taycan into this one, or recoded things incorrectly, or an ECU somehow lost its settings, all the ECUs should be coded to work together. If there is missing communications between ECUs, it's most likely a physical wiring issue, or one of the ECU's failed (e.g. if an ECU was was damaged somehow).

So I think it's worth trying the coding, you won't lose anything, I'm also almost 100% sure that none of the modules were replaced by another one from another Taykan or something similar! Could you then give me guidance on coding the Gatweak, if nothing changes, then I'll have to disconnect the batteries again and take everything out of the car including the Dashboard and check all the physical wiring and connections to the modules... or remove the modules and check them one by one... something to be done so that the modules don't have any connections between them... as for seeing if the module is broken... I don't know if there's any way to see through the piwi….

 

[whitex]

As you can see in the photos of the errors, I have more errors connected to BCM 1 than actually connected to the Gateway….(….Fixing the Gateway->BCM connection can fix all the problems related to BCM1 at once….), I ask how and what do you think I can do to fix this connection between the Gateway and the BCM, for example, what will I have to do to start…..?????…. remove all the plastic seats etc… out of the car, dismantle the car inside, remove the Dashboard outside too and check all the connections of all the modules inside the car outside and the electrical cables between them…..???? Or I don't know how I can check with Piwi and if it is possible to find out which modules are working well and which ones have an error and be able to identify the problem and fix the problem and how to fix the problem…

This is where things get complicated. You have dozens of ECU's interconnected through hundreds of cables, each with a bunch of wired in them. Yes, you could check each one of them by pulling out the interior and inspecting all the harnesses, however that is essentially stripping and rebuilding the car. The fist step in checking wiring is to check connectors and pins on both ends, make sure no bent pins, or torn wiring, or simply a connector not seeded correctly (I would also visually inspect the ECUs they plug into for any visible damage). Beyond that, you can check continuity of wiring without pulling the whole wire out (sometimes easier done with two people), similar to fuse continuity except you check whether pin X of connector 1 is connected to pin Y of connector 2, per wiring diagram. Only if you find a fault, you'd pull out a wire to look for a physical problem. However, there are so many connectors in the car, it would be a huge amount of work. The trick is to look at the PIWIS errors, then wiring, and try to deduce where the error might be. For example, if you have 4 modules connected in a chain:
A-->B-->C-->D
If only the A-->B connection is faulty, module A may still scream it cannot talk to B, and it cannot talk to C, and it cannot talk to D, and B might complain it cannot talk to A, and C cannot talk to A - from that you can guess that perhaps it's A-->B that is broken.

This is not an exact science, with step by step instructions. This is more like electronics detective work - requires some skill, some luck, and perseverance. There is a reason why Porsche would not attempt this - there is no bulletin that tells them the exact complete steps to do this. You may get lucky, and find one burned wire or ECU which solves most if not of your issues, or you might spend a ton of time looking. As @Shug mentioned, your biggest issue is you really don't know the complete history of what happened to the car, so you have no indicators that would allow you to narrow your search - your car could have an issue anywhere. I am not trying to discourage you, but this was discussed at the very beginning of this thread, Taycan is a giant distributed computer with hundreds of cables interconnecting dozens of computers. The large number of errors you are getting either that there is one fault that is in a shared path or shared ECU, or the car has so many independent problems (less likely, but possible). There is a possibility someone before you already spent time trying to fix it, failed, so they sold it to the next person for a seemingly low price.

I hope this works out for you.

 

[carlos vilarinho]

This is where things get complicated. You have dozens of ECU's interconnected through hundreds of cables, each with a bunch of wired in them. Yes, you could check each one of them by pulling out the interior and inspecting all the harnesses, however that is essentially stripping and rebuilding the car. The fist step in checking wiring is to check connectors and pins on both ends, make sure no bent pins, or torn wiring, or simply a connector not seeded correctly (I would also visually inspect the ECUs they plug into for any visible damage). Beyond that, you can check continuity of wiring without pulling the whole wire out (sometimes easier done with two people), similar to fuse continuity except you check whether pin X of connector 1 is connected to pin Y of connector 2, per wiring diagram. Only if you find a fault, you'd pull out a wire to look for a physical problem. However, there are so many connectors in the car, it would be a huge amount of work. The trick is to look at the PIWIS errors, then wiring, and try to deduce where the error might be. For example, if you have 4 modules connected in a chain:
A-->B-->C-->D
If only the A-->B connection is faulty, module A may still scream it cannot talk to B, and it cannot talk to C, and it cannot talk to D, and B might complain it cannot talk to A, and C cannot talk to A - from that you can guess that perhaps it's A-->B that is broken.

This is not an exact science, with step by step instructions. This is more like electronics detective work - requires some skill, some luck, and perseverance. There is a reason why Porsche would not attempt this - there is no bulletin that tells them the exact complete steps to do this. You may get lucky, and find one burned wire or ECU which solves most if not of your issues, or you might spend a ton of time looking. As @Shug mentioned, your biggest issue is you really don't know the complete history of what happened to the car, so you have no indicators that would allow you to narrow your search - your car could have an issue anywhere. I am not trying to discourage you, but this was discussed at the very beginning of this thread, Taycan is a giant distributed computer with hundreds of cables interconnecting dozens of computers. The large number of errors you are getting either that there is one fault that is in a shared path or shared ECU, or the car has so many independent problems (less likely, but possible). There is a possibility someone before you already spent time trying to fix it, failed, so they sold it to the next person for a seemingly low price.

I hope this works out for you.

whitex what can I say is exactly that….., to the point and I think I have courage and perseverance and I think that with your help I will find the cat, and I am sure that with you and Piwi we will get there…. I have been much further and I did not give up, so… we have also reached some conclusions, as you said…. (A-->B-->C-->D
If only the A-->B connection is faulty, module A may still scream it cannot talk to B, and it cannot talk to C, and it cannot talk to D, and B might complain it cannot talk to A, and C cannot talk to A - from that you can guess that perhaps it's A-->B that is broken….) …let's do it, tell me where I have to start and I will do it until we can find the cat, one thing is certain the problem with the car is inside….as a last resort, if i have to remove everything from the car out and check cable by cable, module by module, there will have to be ……!!!!

 

[carlos vilarinho]

whitex what can I say is exactly that….., to the point and I think I have courage and perseverance and I think that with your help I will find the cat, and I am sure that with you and Piwi we will get there…. I have been much further and I did not give up, so… we have also reached some conclusions, as you said…. (A-->B-->C-->D
If only the A-->B connection is faulty, module A may still scream it cannot talk to B, and it cannot talk to C, and it cannot talk to D, and B might complain it cannot talk to A, and C cannot talk to A - from that you can guess that perhaps it's A-->B that is broken….) …let's do it, tell me where I have to start and I will do it until we can find the cat, one thing is certain the problem with the car is inside….as a last resort, if i have to remove everything from the car out and check cable by cable, module by module, there will have to be ……!!!!
[/

 

[carlos vilarinho]

Today I'm going to do another diagnostic of the car's errors, I'll take a screenshot and publish it here?

 

[Shug]

Here is how you reset the PCM, I suggest you do this before the next PIWIS investigation.

taycan reset pcm - Google Search

 

[carlos vilarinho]

Here is how you reset the PCM, I suggest you do this before the next PIWIS investigation.

taycan reset pcm - Google Search

 

[carlos vilarinho]

Here is how you reset the PCM, I suggest you do this before the next PIWIS investigation.

taycan reset pcm - Google Search

Hi Shug and Whitex,

I won't be able to share screenshots of the errors today because I unfortunately missed a plane. I'll be back tomorrow and upload the screenshots so we can review them together.

I wanted to take this opportunity to thank you both again for your incredible support and willingness to help me with this. I really appreciate everything you've done. I know this process isn't easy, and a fix like this definitely requires your expertise and knowledge, especially since I'm still learning and don't have a lot of experience in this area.

Thanks again - it means a lot to me. I'm learning a lot from you both too! ?

 

[carlos vilarinho]

Shug today during the afternoon when I was at the foot of the car I took the opportunity and reset the PCM with two fingers in the upper right corner of the display, after the reset it didn't seem like anything had changed... anyway I did it... and when I do the diagnosis again tomorrow I will do the PCM reset again first

 

[carlos vilarinho]

Shug today during the afternoon when I was at the foot of the car I took the opportunity and reset the PCM with two fingers in the upper right corner of the display, after the reset it didn't seem like anything had changed... anyway I did it... and when I do the diagnosis again tomorrow I will do the PCM reset again first

Another thing I noticed is that my AC in the ventilation is working without any problem...and I have a horn...

 

[Shug]

Communication between modules is the job of the PCM, so will be interesting to see if PIWIS tells you a different story when you look tomorrow.

Sponsored