Problematic RAV4EV without Tesla's codes

[alflash]

An inexplicable situation with this RAV4EV, which has no fault codes in the Tesla system*
https://alflash.com.ua/2019/to_rav4ev/no_codes.png

but in the Toyota system there is a non-erasable code P312f
https://alflash.com.ua/2019/to_rav4ev/p312f.jpg

https://alflash.com.ua/2019/to_rav4ev/p312f.png

What are the versions of the possible reasons for this situation?

* The vehicle is/can charging, Ready mode is available and it can move.

 

[hokiematt]

That is very unusual. Do you have the ability to record a CAN log file (ASCII text preferred) from the Tesla port, and either post or send via DM?

 

[alflash]

That is very unusual. Do you have the ability to record a CAN log file (ASCII text preferred) from the Tesla port, and either post or send via DM?

Thank you for your attention to my first thread.
Unfortunately, I don't have the ability to record a CAN log.
1. The car is in Tennessee, and I live in Ukraine.
2. I do not have software to record such log files.

 

[alflash]

The problem was solved.
The report is a little later.

 

[alflash]

Since the full report is delayed, then quick. The problem of the impossibility of fully reading the codes was caused by this deliberate deterioration of capabilities in the program v.1.1.46 *.

NASTF and CARB (?) have every reason to begin to investigate the reasons for the deterioration of diagnostic capabilities.

*Link.

 

[asavage]

You mentioned the inability of .46 to erase BMS_w023 six months ago; does that lack relate to the issue in this thread?

 

[alflash]

Yes, then I discovered Tesla's provocation - removing the ability to erase the BMS_023 code.
And the bug in this vehicle allowed me to prove that version 1.1.46 does not show the presence of this code when it exists.
In other words, the Tesla system informed the Toyota system about the permanent BMS_023 code. And the Toyota system initiated the Check EV System message, иbut version 1.1.46 skimp this code.
.

 

[asavage]

Aha! Yes, that's a BIG issue to find with .46, Thanks.

 

[alflash]

Aha! Yes, that's a BIG issue to find with .46, Thanks.

Ok,
I've had at least 10 customers whose cars only needed the BMS_w023 code cleared. And once it was cleared, it never showed up again.

https://proxy.imagearchive.com/543/543294d4ea1ce5808296b1b78ef2ba7d.png

Tesla Description. "BMS_w023 / BMS_w023_SW_Contactors_Open_HWOC
Alert Description: This alert is used as a counter to record the number of hardware overcurrents (HWOC) detected by the battery management system (BMS).
Update. Curiously, version 1.1.46 similarly ignores the DI_w115 code, the description of which is also not in the RM of this RAV4EV model.


Totally off topic. Scammers sell version 1.1 42 for almost $500  https://motorstate.com.ua/ustanovka-programmy-toyota-rav4-ev-electric-tesla-diagnostic-software

 

[asavage]

I gave $300 for a working crack of .42 a couple of years ago, and am satisfied that I received good value, but the setup is fragile. Then I bought the cracking software, so I can re-crack .42 when it breaks.

Was I scammed? Maybe. I had a need, I paid, I got value.

What surprises me is that two other sources for cracked .42 want USD$500 and $1000 . . . for software that is only useful on a handful of cars that aren't worth that much.

Overall, .46 is easier to deal with.

---
I've updated the TPD 1.1.46 thread with your info above (BMS_w023, DI_w115).

 

[alflash]

As I cannot, unfortunately, update the first post in this thread . . . this from another thread . . .

TPD 1.1.46 has at least two limitations, as compared to the older, harder-to-install 1.1.42:

• It no longer has an option to clear BMS_w023
• It does not show DI_w115

With your permission, I will make an addition and correction.
1. In version 1.1.46, not only is the ability to clear the BMS_w023 code removed, but this version also does not read/see this code.
2. The ability to read the DI_115 code by this version is still unknown.
But on the RAV4EV of one of my clients, it happens several times a month.

I'll try to check. It remains to check/confirm the capabilities of the test control of the executive mechanisms of the cooling system
https://alflash.com.ua/2019/to_rav4ev/pump_tools.png​

Although this can be done by dozens of owner-users v.1.1.46

 

[asavage]

1. In version 1.1.46, not only is the ability to clear the BMS_w023 code removed, but this version also does not read/see this code.​

I've updated my post there to reflect this.

2. The ability to read the DI_115 code by this version is still unknown.​

Also updated.
My own dealing with DI_w115 was confirmed by .42, so I also cannot confirm if .46 will display this error.

But on the RAV4EV of one of my clients, it happens several times a month.

I'll try to check. It remains to check/confirm the capabilities of the test control of the executive mechanisms of the cooling system​

I have been unable to find the use of the Pump Tool Utility, so far.

 

[alflash]

...
I have been unable to find the use of the Pump Tool Utility, so far.

Today I managed to check the capabilities of the active test "Activate pump and valve" in some modes of RAV4EV (QEA38).
I suppose that this is another fake that Tesla is doing.
I hope to finish the test tomorrow.

 

[alflash]

Another information sabotage from Tesla.
In TDS version 1.1.46, hints about possible causes, for example, of these error codes are excluded.
Compare
https://alflash.com.ua/2019/to_rav4ev/d0005cause.png

vs.
https://alflash.com.ua/2019/to_rav4ev/d0005cause46.png

 

[alflash]

Perhaps you will be interested in fragments of remote diagnostics of RAV4EV in California with this relatively new program Toyota GTS+, which replaced the well-known Techstream soft

 

[asavage]

Does GTS+ still call the TPD program, to perform Tesla-specfic tasks?

 

[alflash]

Does GTS+ still call the TPD program, to perform Tesla-specfic tasks?

I have never seen and, as a result, have never used such an opportunity. Please show/describe how Techstream (TS) can call/run the TDS program. What button in TS should I press to open the TDS program.
I have not found such an opportunity in GTS.

Unfortunately, but GTS+, like Techstream, can "communicate" only with Toyota systems and knows very little about Tesla and can do very little. And they do not use Ethernet* for diagnostics.
https://alflash.com.ua/2019/to_rav4ev/ev_scan_data.gif

https://alflash.com.ua/2019/to_rav4ev/codes.png

*Toyota ISTA and TDS software are used to diagnose some Toyota models via Ethernet.
And various other cables, for example
https://alflash.com.ua/2019/to_rav4ev/bmw_cable.jpg (not compatible with TDS)

 

[asavage]

My mistake: I had forgotten that TS does not directly call TDP; I suppose that I read a PDF on how to perform some procedure, which stated to "stop using TS, now use TDP" or similar words, and in my head I connected TS & TPD together.

The screenshot you posted above, in the field "SOC", that appears to be reflecting what TPD calls "User Display State of Charge".



---

For our old vehicles, is there an advantage to using GTS+ instead of even a very old TechStream? I don't think new firmware versions are going to become available.

 

[alflash]

My mistake: I had forgotten that TS does not directly call TDP; I suppose that I read a PDF on how to perform some procedure, which stated to "stop using TS, now use TDP" or similar words, and in my head I connected TS & TPD together.

The screenshot you posted above, in the field "SOC", that appears to be reflecting what TPD calls "User Display State of Charge".

View attachment 1257

---

For our old vehicles, is there an advantage to using GTS+ instead of even a very old TechStream? I don't think new firmware versions are going to become available.

In addition to the main task - determining the cause of the malfunction and eliminating it with the only currently legal Toyota tool, it was interesting
a) to check the capabilities of version 1.1.46 to reprogram the Tesla system;
b) to check the condition of Toyota RAV4EV systems;
c) to Show the "connection of times": diagnostics of RAV4EV of venerable age and relatively fresh/new software.

p.s. Note.
Outdated firmware (1.3.79) of Tesla ECUs is not the cause of "Firmware Version Mismatch" error codes.