Piwi diagnostic program for Porche Taykan

[carlos vilarinho]

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.

Shug was looking at information while I had time at the airport, it may have nothing to do with the situation of my windshield wipers not working or it may have everything to do with it... just for information, as soon as I get home I will diagnose the car again and post the printscreens here?

Sponsored

 

[whitex]

Shug was looking at information while I had time at the airport, it may have nothing to do with the situation of my windshield wipers not working or it may have everything to do with it... just for information, as soon as I get home I will diagnose the car again and post the printscreens here?

This video shows you the kind of diagnosing you'll be doing. Your challenge is you have a lot of issues, so no easy way to know which connections to diagnose first. In this case the guy was diagnosing a LIN bus, there are also CAN buses, FlexRay, and Ethernet buses, in addition of course to power wires and tradition control wires (like the tail lights, 13V means ON, 0V means OFF), as well as analog control signals (proportional to the voltage). If you assume your issues were all caused by a common cause, there is a good chance that once you find one damaged wire, other wires in the same spot of vicinity will also be damaged, so you can fix them without having to diagnose. As I said a while back, you have your work cut out for you. I hope you find the issue sooner than later, as checking every single interconnect in the car like this will take a very long time.

 

[Shug]

Carlos,

PIWIS is really clever at identifying faults, but you do have to interpret.

Here is an example where something is unplugged.

My suggestion is that you use PIWIS to work on the communications between modules first and not get into things like your wipers, since that may connected with the lack of communication between modules.

 

[carlos vilarinho]

Carlos,

PIWIS is really clever at identifying faults, but you do have to interpret.

Here is an example where something is unplugged.

My suggestion is that you use PIWIS to work on the communications between modules first and not get into things like your wipers, since that may connected with the lack of communication between modules.

Hi Shug and white ,I apologize for not being able to publish the errors here today, because I previously missed a plane in Copenhagen which delayed the publication of the diagnosis a little….I think the images are good this way?,After deleting the errors, these were the entries that remained!!!

 

[Shug]

Carlos,

There seems to be only one Gateway error, the error code U116C00 isn't telling me much when I google it.

I would have a go at Automatic coding on that error if it will allow.

If that is an option check for errors again after the Automatic coding.

After that it would be the BCM errors to look at, unless of course you can see a higher error to try?

 

[carlos vilarinho]

Carlos,

There seems to be only one Gateway error, the error code U116C00 isn't telling me much when I google it.

I would have a go at Automatic coding on that error if it will allow.

If that is an option check for errors again after the Automatic coding.

After that it would be the BCM errors to look at, unless of course you can see a higher error to try?

yes I also couldn't find anything related to this error...!! Ok can you give me instructions on how I can move forward with auromatic coding for this error... after finishing the automatic coding on this error I will do an error diagnosis again, to see if it resolved or not? if it continues! yes most of the errors here are associated with the BCM1 module

 

[Shug]

Highlight the error you want to work on, select the coding program tab, select Automatic coding then it will be F12 from memory

 

[carlos vilarinho]

Highlight the error you want to work on, select the coding program tab, select Automatic coding then it will be F12 from memory

ok I'll select this error and I'll do automatic coding on it with a bit of luck without the error the error is rectified, I'll run this and ?? I'll send you the result….

 

[carlos vilarinho]

Highlight the error you want to work on, select the coding program tab, select Automatic coding then it will be F12 from memory

I did the error diagnosis again, deleted the errors and in the entries I selected the Gatweay error and clicked on program coding, selected automatic coding and then F12 from memory and the result it gave me was this one that I leave the screen shots, I couldn't continue with the automatic coding …. Could there be a way for this to not give an error?...probably by going straight to the gatweay module in the first one in extendent edentifications and selecting gatweay and automatically coding the module instead of just doing it on error...

 

[Shug]

Am guessing that is not the fault that needs corrected Carlos.

The message tells you that PIWIS could not read the Gateway.

Suggest you try the BMS faults until you find whatever is causing the issues.

Once the actual fault is found, the rest of the errors will hopefully disappear at the same time.

 

[carlos vilarinho]

Am guessing that is not the fault that needs corrected Carlos.

The message tells you that PIWIS could not read the Gateway.

Suggest you try the BMS faults until you find whatever is causing the issues.

Once the actual fault is found, the rest of the errors will hopefully disappear at the same time.

So you suggest I start with the BSM errors and do automatic coding one by one… is that it???

 

[Shug]

CONTROL UNIT FOR BATTERY MONITORING, PART NUMBER: 9J1915234AM

PART 9J1915234AM | CONTROL UNIT FOR BATTERY MONITORING

This is the part that you were unable to communicate with

 

[Shug]

Yup,

Just have to try whichever one looks like it might be more suspect.

Automatic coding just reprograms the units with the correct programme, so if it is not broken, you will see no differences.

Working your way through them should get you to the broken one and any linked errors will then disappear.

 

[carlos vilarinho]

CONTROL UNIT FOR BATTERY MONITORING, PART NUMBER: 9J1915234AM

PART 9J1915234AM | CONTROL UNIT FOR BATTERY MONITORING

This is the part that you were unable to communicate with

So now I apologize for my ignorance, but what does battery control have to do with me trying to perform automatic coding to a gateway error…..???

 

[carlos vilarinho]

Yup,

Just have to try whichever one looks like it might be more suspect.

Automatic coding just reprograms the units with the correct programme, so if it is not broken, you will see no differences.

Working your way through them should get you to the broken one and any linked errors will then disappear.

ok it seems interesting to me and it also seems like a good way to get to the error, so instead of going from error to error I could try to do automatic coding in the entire module….??? In this case BSM 1

Sponsored