Tesla Powertrain Diagnostics ("TPD") v1.1.46

Toyota Rav4 EV Forum

Help Support Toyota Rav4 EV Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Video about to check the ability to reprogram a Tesla system using the Tesla Powertrain Diagnostics program - Service Version 1.1.46.
 
If I understand correctly, this video demonstrates TPD 1.1.46 going through the motions of updating firmware on Tesla modules, but not finding any for which a newer firmware version was found (from firmware-release-1.3.101.tar).

Is the below a summary of functional differences between the older TPD 1.1.42 -- which requires a subscription or "other means" to activate -- and the newer TPD 1.1.46, which does not require the additional steps (from your previous post upthread)?

TPD 1.1.46
  • Cannot clear BMS_w043*
  • Does not display battery info:
    • serial number
    • date of mfgr (age)
    • total discharged amount in kWh
  • No Views|Vehicle Information (->Hardware Configuration) option
Are their other known deficiencies of 1.1.46 as compared to .42 ?

* = Is this a code associated with a failed HV Battery contactor?
 
Last edited:
If I understand correctly, this video demonstrates TPD 1.1.46 going through the motions of updating firmware on Tesla modules, but not finding any for which a newer firmware version was found (from firmware-release-1.3.101.tar).

Is the below a summary of functional differences between the older TPD 1.1.42 -- which requires a subscription or "other means" to activate -- and the newer TPD 1.1.46, which does not require the additional steps (from your previous post upthread)?

TPD 1.1.46
  • Cannot clear BMS_w043*
  • Does not display battery info:
    • serial number
    • date of mfgr (age)
    • total discharged amount in kWh
Are their other known deficiencies of 1.1.46 as compared to .42 ?

* = Is this a code associated with a failed HV Battery contactor?
Yes, there is at least one more drawback. The announcement of his demonstration is made at the end of the video.

The inexplicability and incompleteness of these parameters Battery Serial #xx is annoying.
Perhaps they were trying to achieve something like this, but they couldn’t do it...
https://alflash.com.ua/2019/to_rav4ev/briks_data.png
briks_data.png


Note.
Code
https://alflash.com.ua/2019/to_rav4ev/bms_w023s.png
bms_w023s.png

it is especially unpleasant in that it (aka permanent code) is not erased either by manipulating the ignition on/off, or by Techstream, or by disconnecting the 12V battery.
And I won’t be surprised that Tesla, in an attempt to take revenge on Toyota, could exclude not only the possibility of erasing it, but also the possibility of reading it...
 
Last edited:
Last edited:
If I understand correctly, this video demonstrates TPD 1.1.46 going through the motions of updating firmware on Tesla modules, but not finding any for which a newer firmware version was found (from firmware-release-1.3.101.tar).
...
p.s. To be specified.
In this vehicle, back in 2018, I installed the latest/final version of teslas software 1.3.101.
This video was made only to test/demonstrate the reprogramming capabilities using TPD v.1.1.46.
 
--- NO SUPPORT HERE ---
--- PM ONLY ---


I've written a "Tesla Powertrain Diagnostics (“TPD”) for Toyota RAV4 EV, v1.1.42 “simplified” installation" recipe. And put it elsewhere.

Feedback indicates that this can be installed on WinXP, W7, W8.x, W10. 32-bit or 64-bit.

I have personally tested it working on W10 installations only.

It is recommended to install this setup on a dedicated “garage” laptop, one that never connects to the internet, and especially never allows Windows to apply an update or patch. If there’s a major software environment change (such as a major OS update), or a significant hardware change (SSD, mainboard, or CPU), the program will fail to load . . . forever, until another license key is obtained. Which is intentionally painful.

Yes, if you change the HDD or SSD, this program must be re-licensed.
If you run the installer again, it must be re-licensed.
If you change it, it breaks. You are warned.

---

Installing and using TPD 1.1.46 is far easier and cheaper, but as outlined above .46 won't do everything that .42 will do, and for those situations it might be worth the effort & expense for you to dedicate a laptop and cable to TPD 1.1.42, and if you're in one of those situations . . .

This way.

--- NO SUPPORT HERE ---
--- PM ONLY ---
 
For others following along, the document -- which contains 43 pages -- calls itself:

Tesla Powertrain Diagnostics RAV4 – Service
Software User Manual

But, according to the footers, it was printed in 2018 -- long before 1.1.46 and the new mystery parameters -- and its audience is a Toyota dealer technician using a Techstream hardware appliance (hardened laptop). The first 27 pages is only the TOC plus installation instructions for getting TPD installed onto the Techstream laptop. The pages 28-42 include some very basic information such as how to prepare a Log File to send to TIS via email, because the process that Toyota techs were used to using via Techstream doesn't work (for example, they have you turn off the TS appliance's Wi-Fi, in order to generate an error message faster, so you can go on with manually locating a Log File to email it manually).

It has a long-winded section on setting the TS appliance's IPv4 address &c. which is all unnecessary for non-Toyota-dealer environments.

It appears to me to be a document designed to reduce the workload on TIS support people who had to field calls about how a Tech could get TPD working from scratch on the hardware they are guaranteed to have in their shop; how to arrange the Perspectives, and send a Log File. Not much else is in there, and calling it a "User Manual" requires bearing in mind the target audience for the document.

Which is why I stated, '"User Manual" -- which it isn't"' above.

It does, however, mention that bit about BMS_w023, and its relationship to sagging 12v, which is definitely useful information to me :D.
 
For me, the main facts are that Tesla has removed the ability to erase/clear the undocumented BMS_w023 code and I fear that its “smart guys” have blocked the ability to read this code.
At the first opportunity I will try to check this. And what I'm not saying is that removing the configuration option cost Arlin and me additional wasted time. I already wrote about the _w115 code earlier.
Therefore, I am not inclined to blindly trust everything written by Tesla saboteurs for the RAV4EV.
Adding a menu Battery Serial# that is not described anywhere is also a sign of sabotage in relation to the RAV4EV.

Perhaps, when you are faced with a constant and indelible message “Check EV System...” with absolutely no any fault codes in the Tesla system, perhaps we will return to this topic...

1/2 off. There is a keygen that allows you to determine the activation time of the program (from 2 to 365 days, by the number of times the program is turned on, etc.) :) )
 
Last edited:
Hi Everyone I tried to connect to the Tesla OBD port today as my onboard charger quit. I diagnosed it as a fuse. But wanted to connect and check the codes. But it will not show me the Realtek PCIe port on my PC when trying to set the network configuration. I checked my cable. I tried with the car on not ready. And I tried with the car on in Ready mode. Neither will work. I tried with TPD 1.1.42 and I figured maybe 1.1.42 expired so I tried TPD 1.1.46 I didn't remove 1.1.42 before trying 1.1.46. neither work. Any suggestions?
 
For me, the main facts are that Tesla has removed the ability to erase/clear the undocumented BMS_w023 code and I fear that its “smart guys” have blocked the ability to read this code.
At the first opportunity I will try to check this. And what I'm not saying is that removing the configuration option cost Arlin and me additional wasted time. I already wrote about the _w115 code earlier.
Therefore, I am not inclined to blindly trust everything written by Tesla saboteurs for the RAV4EV.
Adding a menu Battery Serial# that is not described anywhere is also a sign of sabotage in relation to the RAV4EV.

Perhaps, when you are faced with a constant and indelible message “Check EV System...” with absolutely no any fault codes in the Tesla system, perhaps we will return to this topic...

1/2 off. There is a keygen that allows you to determine the activation time of the program (from 2 to 365 days, by the number of times the program is turned on, etc.) :) )
Today, when remote diagnosing RAV4EV in Tennessee, another idiocy of version 1.1.46 "surfaced".
In the Gateway cloning menu, the option to not save useless heavy log files (more than 200 megabytes each) disappeared. As a result, I had to download hundreds of MB, not about two. And not less than five minutes, but several hours!
https://alflash.com.ua/2019/to_rav4ev/clons_comp.png
clons_comp.png


Update. I will tell you about another bug in this vehicle which I encountered for the first time after successful diagnostics of more than 150 RAV4EVs, in a separate thread.
 
Last edited:
Hi Everyone I tried to connect to the Tesla OBD port today as my onboard charger quit. I diagnosed it as a fuse. But wanted to connect and check the codes. But it will not show me the Realtek PCIe port on my PC when trying to set the network configuration. I checked my cable. I tried with the car on not ready. And I tried with the car on in Ready mode. Neither will work. I tried with TPD 1.1.42 and I figured maybe 1.1.42 expired so I tried TPD 1.1.46 I didn't remove 1.1.42 before trying 1.1.46. neither work. Any suggestions?
  1. Is the network card working?
  2. Correct cable pinout?
  3. Is TCP/IP setup correct?
  4. Is the configuration complete?
  5. Color of the ball in the lower left corner?
  6. Screenshot of the window with menu blocks when connected?
We can watch it together using AnyDesk...
 
  1. Is the network card working?
  2. Correct cable pinout?
  3. Is TCP/IP setup correct?
  4. Is the configuration complete?
  5. Color of the ball in the lower left corner?
  6. Screenshot of the window with menu blocks when connected?
We can watch it together using AnyDesk...
Cable is good. Its the one you and I used before and I used a DMM to double check its good. I I can also triple check. But the TPD 1.1.42 said the licence was good until May 29 so should I just remove it?
 
Cable is good. Its the one you and I used before and I used a DMM to double check its good. I I can also triple check. But the TPD 1.1.42 said the licence was good until May 29 so should I just remove it?
As far as I know,
a) versions 1.1.42 and 1.1.46 have the same method/way of communicating with the Tesla system;​
But I'm sure that the reason for the problem with connecting to the car is something else.
Question. What has changed since the time when there was no problem with diagnostics? https://www.myrav4ev.com/threads/er...problems-with-re-flash.2645/page-3#post-31176
 
Back
Top