Hey Andy,
It seems you are doing everything right so it comes down to whether:
- Torque sleep is just not working
- Torque sleep is working but other consumption factors are hiding or minimizing the benefit you see relative to your pre .139 numbers (and relative to EV trip planner)
Besides your own numbers and analysis, the numbers Tesla provided also indicate virtually no improvement so I understand your concern.
Exactly!
As there are so many variables involved it makes it hard to prove to Tesla (particularly if you're working through various "middlemen"). One thing I wondered was whether you had tried to duplicate Lolachampcar's description of when and how the car switches into torque sleep. Others's have described how the energy usage changes when the rear motor drops out. If you were to do a flat run, warm battery, range on, heat off (temporarily) and have your wife do the necessary steps while you are videoing the dash along with before and after consumption figures. My understanding is that the change in energy usage should be very noticeable and comparable to the behavior described by others on the forum. Obviously if it seems to be working from this point of view, you are still left with questions; however, if it doesn't behave as expected you have some more ammunition to push Tesla service.
That's a good idea, and if it comes to that, I guess I'll have to try that. I'm hoping I won't need to, though. At this point I don't think I've really had the attention of anyone at Tesla who would really understand the issue and be able to give me an answer yet. I think the engineer who my initial inquiry was passed on to just checked the logs, saw that torque sleep was enabled, and responded with the figures, and then the rep just passed that information along. I doubt the engineer understood that I had already been logging trips and already feared there was an issue with torque sleep not functioning properly, etc. I think I'll have a much better feel for how Tesla is going to react when I hear back next time. That should give me a pretty good idea of how much "proof" I'm going to have to provide that something other than what is expected is going on.
If I am going to try to video torque sleep either happening or not happening, I'm not sure exactly how I'd go about that. For example, would I just get on the highway, set the TACC for, say 60 or 65, video the dash as we get up to speed, and then continue videoing the dash as I hopefully see a drop in energy consumption when the back motor drops out? My concern would be that if I see no drop in consumption, how do I know whether I'm seeing torque sleep not happening, as opposed to having seen torque sleep having kicked in very quickly just as the cruising speed was reached? Does that make sense?
Similarly, I might hear the back motor drop out, but not hearing it doesn't prove torque sleep isn't happening.
I guess what I'm saying is I think this test could prove that torque sleep is working, but I don't see how it could prove that it isn't, at least the way I envision doing the test. Perhaps there's a better way to do it that would allow for it to show if torque sleep isn't working, and I'm just not seeing it, or not understanding what you mean. If so, please explain it to me, as I very well may need to do this.
Thanks!
Also, even if I find out this way that torque sleep is working at times, that wouldn't be a complete answer, because I'd still wonder if it were working as frequently as it should be.
Does that make sense?
