waidy
Well-known member
SeaMonster, thanks for logging the failure events.SeaMonster said:With respect: I do not know the deep down cause of the timer charge failures, but I DO know how to reproduce them. I have a spreadsheet that has every single charge for 8 months. It also charts many external factors to enable it to show correlations (or lack thereof). I have talked directly with Toyota techs. (I spoke with them again last night, twice. Not the dealer, Toyota.) Toyota has confirmed some of those behaviors that I listed and you claimed were false. I have pursued many theories (some mine and some Toyota's) to see if they correlated. Some did, some did not. Toyota instrumented my car with recording devices (talking to both the Toyota and Tesla OBD connectors) and had me go through my regular routine for several weeks recording diagnostic data and using my externally observed data to correlate that with.
Additionally, I have now had a Rav4 EV rental for more than 30 days (while mine was in the shop) and I have reproduced many/most of these failure behaviors with that car as well.
So tell me. Why do you say there is no pattern? Is that based on a well documented analysis? Or is that just your opinion? I can show you patterns. Real actual patterns. Yes, I have no idea where a broken line of code is or which subroutine(s) or components are in need of repair. But I can show you behavior that will reproduce a timer failure 100%. And I can show other behaviors that will reproduce it less than 100%, but statistically more often than just chance.
So let's take this down a notch. The path forward is to find useful data and provide that to Toyota. I encourage everyone to take careful notes. Theories are great for forums, but not for notes. Record facts only and as much as you can. Use your theories to help you decide what raw data to collect. As others have noted, software is deterministic and given the same inputs will always produce the same outputs. (Yes, i know there are exceptions to that, but basically it is true.) The issue here is that there are many inputs and these need to be observed and recorded and isolated as best possible. I will be talking to Toyota again today and my message is that they need to engage the community to help them, and they need to communicate more. (Of course Toyota is huge and I am just talking to one guy. But it's a start.)
Peace!
I wonder if you would, next time if you talk to the tech, ask the tech to put probes on the input/output wires of the ECU and BMS units, then create the events and capture the wave forms to help to debug the problem. They must have a logic diagram (if not logic diagram, a block diagram) to further identify the area of fault.