boredcleaner
Well-known member
Mine failed last night.
If my theory is correct - that the 31st bug causes the Next Departure to jump to the 1st, then you did not actually see the bug. However, I'm often wrong. Just ask my wife.yblaser said:My car actually charged successfully last night, but only because of the firmware bug that causes it to start way too early. In this case just before midnight.
miimura said:If my theory is correct - that the 31st bug causes the Next Departure to jump to the 1st, then you did not actually see the bug. However, I'm often wrong. Just ask my wife.yblaser said:My car actually charged successfully last night, but only because of the firmware bug that causes it to start way too early. In this case just before midnight.
Well, that's very disappointing. Do you know if you have the firmware mentioned by Sheldon Brown?TonyWilliams said:Mine failed to charge. It would have started after midnight on July 31.
I have updated firmware from when they last worked on my car (which is frequently!).
miimura said:Well, that's very disappointing. Do you know if you have the firmware mentioned by Sheldon Brown?TonyWilliams said:Mine failed to charge. It would have started after midnight on July 31.
I have updated firmware from when they last worked on my car (which is frequently!).
miimura said:If my theory is correct - that the 31st bug causes the Next Departure to jump to the 1st, then you did not actually see the bug. However, I'm often wrong. Just ask my wife.yblaser said:My car actually charged successfully last night, but only because of the firmware bug that causes it to start way too early. In this case just before midnight.
I did however experience what I think is a different timer bug. I plugged in on 29th and car started charging immediately even though the timer was set.
The easiest way to tell if the car is actually charging is to look at the EVSE. I see you have the EVB40, so you just look at the Yellow light. The car can only be drawing power from the EVSE if the Yellow light is on or blinking.eschatfische said:I did however experience what I think is a different timer bug. I plugged in on 29th and car started charging immediately even though the timer was set.
Are you sure it was actually charging? Ours will occasionally make the full "charging noises" for 20-30 seconds after being plugged even if the charge timer is set. However, the LEDs above the charge connector still blink the charge timer pattern (#1 and #2 blinking back and forth) instead of the charging pattern (#1 blinking and #2 off if the batteries are charging and below half strength, #1 solid and #2 blinking if the batteries are charging and above half strength), and then things go back to normal 30 seconds later. No idea what it's doing there.
eschatfische said:I did however experience what I think is a different timer bug. I plugged in on 29th and car started charging immediately even though the timer was set.
Are you sure it was actually charging? Ours will occasionally make the full "charging noises" for 20-30 seconds after being plugged even if the charge timer is set. However, the LEDs above the charge connector still blink the charge timer pattern (#1 and #2 blinking back and forth) instead of the charging pattern (#1 blinking and #2 off if the batteries are charging and below half strength, #1 solid and #2 blinking if the batteries are charging and above half strength), and then things go back to normal 30 seconds later. No idea what it's doing there.
Anyway i noticed that occasionally the entune app fails and I get a "Charge Failure Notification - our systems indicate that your RAV4 EV failed to begin charging ...", if a try again via entune it works, so its not a persistent HW failure. I wonder if this "charge failure" is the same culprit behind the delayed charge failure, but because it is not initiated via entune it does not send a notification?
adjackson3 said:We have no leverage
Enter your email address to join: